Skip to content

M1 — the governed-generation pipeline (vertical slice)

Choose a tag to compare

@ryandmonk ryandmonk released this 02 Jul 22:12
1073c27

Milestone 1 of the AF governance layer: the thesis-proving vertical slice, end to end and machine-gated.

  • Pipeline: contract → compiled context (src/core/compiler.ts) → schema-constrained generation (Ollama structured outputs / Anthropic; model ids are configuration) → surface gates S1/S2/S3 (src/core/lint/) → bounded repair (ADR-7: one findings object, two serializations) → A2UI emission via the pinned emitter → gates A1–A3audit report v1 (schemas/audit-report.v1.schema.json, guarantees in docs/AUDIT.md).
  • Flagship gate: npm run demo:e2e (Playwright, deterministic scripted adapter) asserts the full on-screen trail: violation with verbatim rationale → exact repair message → verified-clean attempt → A1–A3 green → rendered AlertDialog → schema-valid downloaded report.
  • Evidence (the write-up's raw material): docs/spike-structured-outputs.md (S0 + model refresh; the engine-scoped MLX silent-format finding with minimal repro) and docs/evidence/2026-07-02-flagship-candidates{,-post-example-link}/ — 22 audit reports incl. the clean-negative example-link A/B. Public framing rule: failures are named with the report's own vocabulary (failed-lint-exhausted).
  • Open M2 threads: #7 (contract-copy drift prevention), the json-render emitter (PR-9), eval harness (PR-10, incl. repair-shape matrix design input), ds-mcp tools (PR-11).

Companion M1 tags: dspack@m1, dspack-to-a2ui@m1. The governing plan document (revision records 1–3) is maintained by the project owner.