49 lines
2.4 KiB
Markdown
49 lines
2.4 KiB
Markdown
# Domain-Typed Pipeline Completion Record
|
|
|
|
## Status
|
|
|
|
Implemented on 2026-07-17.
|
|
|
|
This file is a concise historical record. Current behavior is owned by
|
|
[Architecture](../policy/architecture.md),
|
|
[Configuration](../config.md), [Operations](../operations.md),
|
|
[Pipeline Internals](../internal/pipeline.md),
|
|
[Module Internals](../internal/modules.md),
|
|
[LLM Runtime Internals](../internal/llm.md), and the durable
|
|
[integration contracts](../integrations/). The accepted decisions remain in
|
|
[ADR-0002](../adr/0002-linear-pipes-and-filters-pipeline.md),
|
|
[ADR-0003](../adr/0003-typed-interfaces-with-two-zone-data-model.md), and
|
|
[ADR-0004](../adr/0004-package-modules-by-domain.md).
|
|
|
|
## Delivered
|
|
|
|
- Production extensions use domain-first packages and package-family
|
|
registrars without changing selectable module or validator keys.
|
|
- Source units and chunks carry canonical engine-owned provenance using
|
|
`source.SourceRef`; workspace checkpoints use schema v2.
|
|
- Artifact lanes keep one domain-owned Go type through extraction, merge,
|
|
normalization, and typed validation.
|
|
- Artifact codecs own stable schema-aware checkpoint, debug, and output
|
|
serialization; generic representation validators consume serialized views.
|
|
- Resolution verifies artifact-kind, codec, typed variant, capability,
|
|
reference, validator, and option compatibility before source work.
|
|
- Preparation constructs the full run-local implementation set and injects one
|
|
shared scheduled LLM client.
|
|
- Extraction uses bounded chunk-first, lane-second dispatch. Lane continuations
|
|
are also bounded, public results are deterministic, and framework failures
|
|
cancel undispatched work without treating rejections as errors.
|
|
- Maintained D&D payloads, logical output paths, prompt and schema identities,
|
|
default validators, warnings, rejections, and manifest provenance remain
|
|
covered by compatibility tests.
|
|
|
|
## Completion Evidence
|
|
|
|
Focused tests cover durable compatibility, typed resolution and preparation,
|
|
codec boundaries, checkpoint invalidation, debug recording, bounded scheduling,
|
|
reverse completion, cancellation, rejection, retries, and independent extract
|
|
worker and provider-call limits. Maintained example configurations and input are
|
|
validated and exercised by the CLI test suite.
|
|
|
|
Repository validation is defined in [Development](../development.md). The Go
|
|
race suite requires a CGO-capable toolchain in the execution environment.
|