ditc B4 edit-pass: Channels + Promote/rollback + Checks/approval (410 + 420 + 430) #7
Loading…
Reference in a new issue
No description provided.
Delete branch "ditc-b4"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
B4 edit-pass batch (ditc program, implementation-plan row B4). Three pages, one author dispatch (Kimi-K3, contract EDIT-PASS-template + COMMON-ditc), frontmatter + glossary pre-landed by the dispatcher.
What changed
Gates (independently re-run by the dispatcher, all green)
build-docs --no-coverage --draft = 0 · check-prose --manual ditc = clean · check-lockstep --manual ditc --synthesize = 0 fail (15 designed FRESHNESS warns) · build-docs --draft = 0 · armada check-prose.sh --registry per page = 0, zero FAIL rows.
Merge order — read before merging
Branches from main
b01234b(pre-B3, pre-B5). Merge the pending src/ditc batches first (#5 ditc-b3, #6 ditc-b5); this PR touches 310–330/510–710 in no way, but #5, #6, #7 all append to src/ditc/glossary.yaml — tea shows no conflicts against current main; re-check after each merge and if a glossary hunk conflicts, ditc-b4 rebases onto the updated main and the battery re-runs before merge. Post-merge of all three, re-run the battery once on main (combined CONCEPT walk).Merge blocked — the Operator reads page 430 for this batch
Per implementation-plan row B4 (Operator-read page: 430) and the batch decision 5 (one page per batch, Operator reads in full). This PR stays unmerged until that read; the plan-gate approval is recorded PENDING on the realm audit chain.
410-channels (explanation): both topic headings to claim form ("Two rules split one tag set between the two addresses"; "A testing deploy leaves the real address alone"); opener tightened — 'every change deserves a rehearsal' struck, payoff line landed in the first body lines; rc-tag wording aligned to the glossary plain ('the ending asks that the candidate be tried first'); the two CAUTIONs (shared real data; the sign-in refusal) stay verbatim; one 'In practice' stance sentence (armada opinion_floor, the landed 110/120 shape). 420-promote-rollback (how-to): all three headings to imperative ("Promote the tested change to the release"; "Put the previous release back with one command"; "Read what shipped, and when") — the audit's 'already one imperative' resolves to the ### To … procedure headings, which keep their form; 'has earned its place' and 'calm by design' struck; 'a rollback is a pause, not a place to stay' struck, its mechanism sentence kept; the rollback-restores-code-only NOTE stays verbatim. 430-checks-approval (explanation): all four headings to claim form ("A Block finding stops the deploy before anything moves"; "An accepted finding passes by name and lands on the record"; "An app that sends data out waits for two yeses"; "One command keeps the manifest and its copied fact block in step"); the papers/description-sheet/two-sheets metaphor family → the manifest (the glossary's own name); 'principles' kept — the scaffold's product name; both aphorism codas struck ('not a scolding', 'never a shrug'), mechanisms kept; the T2 two-yeses approval case survives whole — audited trust content; the --ack WARNING stays verbatim; summary reworded where the metaphor carried it. Frontmatter (dispatcher-landed, gate-verified): 410 requires [first-deploy, app-parts, your-tenant, pick-tenant] — the superset resolves the vocabulary whose chapter-3 requires-edges belong to the pending B3 batch (map-exact [first-deploy] evidenced 25 CONCEPT fails); 420/430 requires [channels] per the map. 410 introduces [testing] (build forces introduces ⊆ defined_in-this-page; 'stable' is defined_in first-deploy — map divergence recorded, no glossary re-point). New glossary entries: check finding, T2 app (both defined_in checks-approval). Gate battery: build --no-coverage --draft / check-prose --manual ditc / lockstep --synthesize / build --draft all exit 0 (0 fail, 15 designed FRESHNESS warns, 18 SKIP); armada check-prose.sh --registry exit 0 per page, zero FAIL rows. Site artifacts (htdocs/*, provenance.json) stay uncommitted — site regen is the automated-deploy flow. Edit-pass contract: program/ditc-contracts/EDIT-PASS-template.md + COMMON-ditc.md; audit disposition rows 410-channels, 420-promote-rollback, 430-checks-approval; trust content per audit line 46. Assisted-by: author:synthetic/hf:moonshotai/Kimi-K3