docs: ship itd-80 through the intent-lifecycle pipeline (dogfood) - #27
Merged
Conversation
The acceptance test for itd-80's own slice: itd-80 driven drafts->planned-> shipped by the machinery it specifies, not by hand. Live cycle on the on-main pipeline (PRs #22/#24/#26): abcd intent plan itd-80 -> mints spc-2 (spc-1 reserved by itd-3 skipped), links, moves drafts->planned abcd spec close spc-2 -> reconcile ships itd-80 planned->shipped, parks OWED review rcp-1c213fa02f85 abcd intent review ingest -> machine fidelity audit written to ## Audit Notes; re-ingest is a verified no-op Rollup 6 MET / 1 MET_WITH_CONCERNS / 0 NOT_MET / 0 INCONCLUSIVE. The one concern (ac-3): the review request references the delivered diff as host-supplied rather than abcd-captured — a deliberate adr-25 transport-agnostic divergence. Adds the spc-2 native spec record (closed). record-lint green throughout (spec_lifecycle cross-check on the new spc-2<->itd-80 link passes). Assisted-by: Claude:claude-opus-4-8
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The acceptance test for the whole slice. itd-80 — the intent that specifies the intent-lifecycle pipeline — was driven
drafts → planned → shippedby that pipeline itself, on the on-maincode (PRs #22 / #24 / #26). Not a hand-edit; the machinery did it.The live cycle
The audit (machine-generated, in itd-80's
## Audit Notes)Rollup 6 MET · 1 MET_WITH_CONCERNS · 0 NOT_MET · 0 INCONCLUSIVE, every verdict carrying a cited
file:linepointer, plus a honoured/diverged/missing gap audit and pinned provenance (verifier + rubric/prompt hashes + input attestation). It's an honest audit, not a rubber stamp — ac-3 is MET_WITH_CONCERNS: the review request references the delivered diff as host-supplied rather than abcd-captured, a deliberate adr-25 transport-agnostic divergence.Contents
drafts/ → shipped/with its populated## Audit Notes.spc-2native spec record added (inspecs/closed/); thespec_lifecyclecross-check on the newspc-2 ↔ itd-80link passes.make preflight+make record-lintgreen throughout.Definition of done — met
itd-80's own acceptance criteria are satisfied by the delivered pipeline, verified through the pipeline. The intent-lifecycle slice (Phases 1–5) is complete.
Minor follow-up (not blocking)
The ingest appends the audit below the intent template's
<Empty until intent moves to shipped/…>placeholder rather than clearing it, leaving redundant text above the audit. Cosmetic; candidateiss-N— the ingest could strip the placeholder when it writes the first verdict.Assisted-by: Claude:claude-opus-4-8