PTV-SCF-0001 P1 — phase close
Date: 2026-08-12
Status: closed — countersigned 2026-08-12
Supersedes: none
Superseded-by: none — current
Phase: PTV-SCF-0001 P1 · Specification
Verification round: docs/decisions/2026-08-12-ptv-scf-0001-p1-verification-round.md (merged)
Precondition check
Section titled “Precondition check”Run in the G-03 shape (docs/PETROVA-GOLDEN-PROMPTS.md §4). All four must hold.
| # | Precondition | Verdict | Evidence |
|---|---|---|---|
| 1 | A verification-round record exists for this phase and is merged | PASS | 2026-08-12-ptv-scf-0001-p1-verification-round.md, merged as #260. |
| 2 | Every item that round surfaced carries an explicit classification | PASS | 14 items: 4 CLOSED, 2 IN-BUDGET, 8 DEFERRED. Classified in the round, not in this session — that is the round’s job and it has already run. |
| 3 | Every acceptance gate reads PASS, or has a recorded and merged waiver | PASS | Below. No waiver was used. |
| 4 | Every DEFERRED item has a named target in the next phase | PASS | Below. |
Precondition 3 — the two gates that failed the round
Section titled “Precondition 3 — the two gates that failed the round”The round recorded gates 3 and 4 as FAIL. Both now PASS, and neither was made to pass by changing what the gate asks.
| Gate | Round verdict | Now | What changed |
|---|---|---|---|
| Every DR traces to at least one SR | FAIL | PASS | PTV-DR-3104 gained its missing trace edge to PTV-SR-0009, logged as a diagram edit in SDD §“Amendment log”. Twelve of twelve authored DRs trace. |
| Every SR traces to root, or is reclassified | FAIL | PASS | The root set was ruled on and ratified as six enumerated premises (SDD §3.2, authority 2026-08-12-requirement-tree-root-set.md). Every SR traces. No relation was added, removed or invented — the tree’s edges are exactly as authored, and what changed is which requirements were understood to be premises. |
The distinction in that last row is the one that matters at a close. The gate was not weakened and no ceremonial edge was drawn; a wrong assumption in §3’s rationale — that the tree has exactly two roots — was corrected against evidence the gate itself produced. A gate that finds a defect in the baseline it is evaluating is a gate working correctly, and the correct response was a ruling with alternatives, not a waiver.
Gates 1, 2 and 5 passed in the round and are unchanged: estate.yaml parses, the
generator is deterministic across two runs and against the committed artefact, and
every requirement carries exactly one verification method — now including
PTV-SR-0015, admitted to the catalogue at §3.3 with verifymethod: test.
Precondition 4 — the deferred ledger
Section titled “Precondition 4 — the deferred ledger”Eight items, each with a named target. This is the ledger P2 consumes as input.
| Item | Target | What it is |
|---|---|---|
| F-04 | P2 | 35 of 40 registered slugs have no DR block. Allocation is a G1 act and wants a decision record. |
| F-05 | P2 | Domain module parts 3–5 unspecified for every generated slug; needs an owner per slug before it needs authoring. |
| F-09 | P4 | The six-requirement verification debt (PTV-VCRM-DEBT-01). Discharged by building PTV-CHK-0008/0009 against the canary. |
| F-11 | P5 | INV-3’s n8n axis is conforming by role, not by scope; the write refusal is inferred, and the negative test is P5’s. |
| F-12 | P3 | The scoped n8n credential is ambient in every interactive shell. Operator action. |
| F-13 | P4 | Both deployed surfaces serve a build-time snapshot of state/. |
| G4-impl | P2 | New, raised by the root-set ruling: gate G4 is asserted by CI in the SDD’s own mutation protocol and has no implementation. The trace graph lives in a mermaid block and is evaluated by reading it. |
| F-03 residual | — | Closed in this session, not deferred. Listed for completeness because the round deferred it pending the F-02 ruling, and the ruling landed. |
F-10 (SR-0015 uncountersigned) was classified IN-BUDGET by the round and is now discharged — the record was countersigned 2026-08-12 and the requirement is in the catalogue.
Decision
Section titled “Decision”P1 · Specification is CLOSED. All acceptance gates PASS on evidence, no gate was waived, and the deferred ledger is complete with named targets.
What was built
Section titled “What was built”estate.yaml— the projection source SDD §7.1 specified and §8.6 recorded as missing. Rings, domains, DR blocks, elements, every edge and its class, non-governance declarations, retirements.docs/diagrams/PTV-DWG-0002.mmd— the master, generated. Editing it is a projection-discipline violation and--checkrejects it.host/src/estate/generate.ts+ tests — gates G1, G2 and G3 as code. A fleet→repo edge cannot be expressed, and there is a test that tries.checks.yaml— 35 checks in one ID space, unifying M-01..19, N-01..11 and G-01..08. Coverage of all three source ID spaces asserted mechanically.docs/domains/— 40 modules plus an index, parts 1–2 sourced and parts 3–5 visibly absent.- SDD amendments: §8.6 discharged, §8.2 partially discharged, §8.8 (G2 admits INTERNAL), §3.2 (root set), §3.3 (PTV-SR-0015).
- Two ratified decision records: the automation-plane boundary and the requirement tree’s root set.
What was evidenced
Section titled “What was evidenced”host 225 tests · cli 635 tests · typecheck and build clean ·
estate:generate --check and domains:generate --check both current. Every gate
verdict in this record cites an artefact, not an assertion.
What was deferred, and where to
Section titled “What was deferred, and where to”The eight rows above.
What questions were raised
Section titled “What questions were raised”One was raised and answered within the phase: is PTV-SR-0003 a consequence, or
a third root? Answered — it is a premise, and so are three others.
One is raised and left open: gate G4 has no implementation. The SDD’s mutation protocol claims CI enforces trace-to-root; nothing does. P1 found six orphans by reading a mermaid block by hand, which is precisely the manual check the gate was supposed to have replaced. Targeted at P2.
Consequences
Section titled “Consequences”- P2 · Golden prompts as skills may open. Its entry criteria are unaffected by anything in the deferred ledger.
- The deferred ledger is P2’s input, per G-01 step 4. F-04, F-05 and G4-impl are P2-targeted and must appear in its scope.
- No milestone transition is recorded here; PTV-SCF-0001 is a scaffold, not a registered consumer phase, and its state lives in these records.
References
Section titled “References”docs/specs/2026-08-12-ptv-scf-0001-scaffold-rev-a.xml— P1 tasks and exit gate.docs/decisions/2026-08-12-ptv-scf-0001-p1-verification-round.md— gates as evaluated, and the friction ledger this record consumes.docs/decisions/2026-08-12-requirement-tree-root-set.md— the F-02 ruling.docs/decisions/2026-08-12-ptv-sr-0015-automation-plane-boundary.md— ratified.docs/PETROVA-SDD-BASELINE.md§3.2, §3.3, §8.8, amendment log.docs/PETROVA-GOLDEN-PROMPTS.md§4 — the G-03 shape this record follows.
Sign-off
Section titled “Sign-off”- Subagent: PTV-SCF-0001 P1 close (session 2026-08-12)
- Human: Alex Devarno (alex@devarno.com) — countersigned 2026-08-12, instructed in session; transcribed by the agent on explicit direction, not ticked on its own authority. Closes P1 on the gate verdicts and deferred ledger recorded above.