Generating Aptivs.
Every Aptiv reaches the shard library by one of two roads: assimilated from something that already exists, or authored directly as intent. Both roads converge on the same governed artifact.
Assimilation: any workaround (an agent skill, an API schema, an ERP integration, a workflow node, a standards document, even legacy code) is ingested through an eight-phase pipeline and resolved into an Aptiv Spec. Direct Synergy: a Creator describes intent in plain language and Synergy® resolves it directly, with AI-Proposed, By Industry, Use Case Plan, and Discovery variants along the way.
GenAI proposes. Synergy® resolves. Every Aptiv Spec must trace to a real source: zero fabrication tolerance.
Five artifacts, one grammar
Whatever the source, generation resolves to the same small set of governed artifacts:
- Aptiv Spec: the sourced, cited fact-file the Assimilator produces from any workaround. Every claim cites the source field it came from.
- Aptiv Record: a Spec that has cleared the pipeline and been registered into the shard library with a name, domain, posture, and a live Meaning Surface of typed inputs and outputs.
- Aptiv Script: the declarative, generative source Synergy® reads to regenerate the Aptiv's view and behavior on demand.
- Placeholder Aptiv: a synthetic mock generated on demand (for example when a Creator clicks View Aptiv) to preview structure and behavior. Unlike a Spec, it isn't derived from any workaround or existing code.
- Elevate: a separate SDK path (Import, Detect, Wrap, Combine & Deploy) that scans real existing code, data, or toolchains and wraps them without rewriting, so the original code remains the execution layer while the Aptiv layer governs it. Elevate runs alongside the Assimilator, not as one of its eight phases.
The Assimilator pipeline
Eight phases. Thirteen LLM Agents. Two embedded deterministic analyzers that sit inside the pipeline but run no model at all, so they aren't counted toward the agent total.
| Phase | What runs | Output |
|---|---|---|
| 01 · Source-Grounded Extraction | 5 LLM Agents, parallel | REQ / CON / ACT / DEF / POL findings |
| 02 · Adversarial Critique | 4 LLM Agents, sequential | CRD / AMB / GAP / OVR findings |
| 03 · Synthesis | 1 LLM Agent | confirmed_findings + aptiv_candidate_map |
| 04 · Normalization | Embedded analyzer · deterministic | Normalized candidate fields |
| 05 · Validation Gates | Embedded analyzer · deterministic | Structural + completeness pass/fail (5 gates) |
| 06 · Aptiv Spec Generation | 1 LLM Agent | Draft Aptiv Spec |
| 07 · Ensemble Construction | 1 LLM Agent | Governance-coordinated ensemble output |
| 08 · Deduplication | 1 LLM Agent | NEW / MERGE / CONFLICT disposition |
The five Validation Gates (Phase 05) are: no hard blockers (some overridable by the Creator), required Spec fields present, no fabrication findings, at least 60% of candidates at confidence threshold, and every finding source-referenced. Anything that fails routes to human review before it can advance.
The eight phases above run once, when a source is first ingested into an Aptiv Spec. The Health Monitor is a separate, continuous workflow: it re-scores Aptivs already living in the shard library against a 100-point rubric and routes anything under 75% to a Repair Agent. It does not run the pipeline above; it audits the pipeline's output after the fact.
Two roads in
Assimilation is the bottom-up road: bulk, source-grounded, built for the backlog of work an organization already has. Paste any workaround and the eight-phase pipeline extracts, critiques, synthesizes, normalizes, validates, generates, ensembles, and deduplicates the Spec. Elevate covers the special case of existing codebases: scanned and wrapped rather than rewritten, as a separate path alongside the pipeline.
Direct Synergy is the top-down road: a Creator expresses intent directly. Synergy® routes it through Direct Synergy, AI-Proposed (Single or Multi-GenAI Composite, Chaperoned Aptiv, or Multi-Aptiv Ensemble), By Industry, the Use Case Plan Builder, Custom Use Cases, or Aptiv Discovery, whichever path fits how bounded, how large, or how likely-to-already-exist the intent is.
Both roads produce the same trust-certified .wv Aptiv. The
path shapes how Synergy® gets there, not what it can produce.
Grounding and governance
An Aptiv Spec is marked UNGROUNDED: structural validity only until its cited sources are verified against the underlying system. Generation isn't the finish line: an Aptiv is scanned, re-scored, and re-verified on an ongoing cadence, the same way any Aptiv already in the library can be re-run through the Health Monitor at any time.
See Aptiv Types & Composition for what an Aptiv is once it's generated, Elevate for wrapping existing code specifically, and Trust Certification for how grounding state is verified and maintained over time.