From 81ac6fd6546da3ba409dd16756043991a43bf702 Mon Sep 17 00:00:00 2001 From: Brummel Date: Thu, 2 Jul 2026 22:07:40 +0200 Subject: [PATCH] =?UTF-8?q?docs(ledger):=20declare=20the=20canonical=20pro?= =?UTF-8?q?ject=20shape=20=E2=80=94=20templates=20canon,=20fixture=20froze?= =?UTF-8?q?n=20twin?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Resolves the #181 design pass (option c: ledger declaration, no lockstep mechanism). The aura-new templates (scaffold.rs) are the canonical authoring shape and evolve with the engine; the cycle-0102 demo-project fixture is an intentionally frozen known-good twin for the load-boundary tests. Deliberately NOT lockstep-guarded: no consumer requires the copies to match (skeptic-verified — nothing treats the fixture as what aura new emits), each is e2e-guarded on its fitness for purpose (build/load/ charter/deterministic run; blueprint wiring is pinned in neither, stated honestly after an adversarial skeptic pass refuted the stronger claim), and an equality guard would convert deliberate template improvements into forced churn of the frozen fixture — the same cross-purpose coupling that rules out regenerating the fixture from the scaffolder. closes #181, refs #180 --- docs/design/INDEX.md | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/docs/design/INDEX.md b/docs/design/INDEX.md index d2e6ab4..633ea62 100644 --- a/docs/design/INDEX.md +++ b/docs/design/INDEX.md @@ -1996,7 +1996,17 @@ note; the `aura new` scaffolder followed in cycle 0103 — one command emits a buildable project whose blueprint runs through the merged vocabulary); of the two layers this paragraph used to name as sequencing-coupled, what remains open is the **composable-orchestration** thread (#109): topology-as-data is -the substrate it stands on. +the substrate it stands on. **Canonical project shape (#181, resolved +2026-07-02):** the `aura new` templates (`scaffold.rs`) are the canonical +authoring shape and evolve with the engine; the cycle-0102 `demo-project` +fixture is an intentionally frozen known-good twin for the load-boundary +tests. The two are deliberately **not** lockstep-guarded: no consumer requires +them to match, each is e2e-guarded on its fitness for purpose (build → +descriptor load → charter check → deterministic run — blueprint *wiring* +content is pinned in neither, stated honestly), and an equality guard would +convert every deliberate template improvement into forced churn of the frozen +fixture — the same cross-purpose coupling that rules out regenerating the +fixture from the scaffolder. **Op-script grammar (`aura graph build`, the #157 wire surface).** The construction op-script is a JSON **array of ops**, each object internally tagged by `"op"`,