ditc B3 edit-pass: app parts + scaffold + first deploy (310 + 320 + 330) #5
Loading…
Reference in a new issue
No description provided.
Delete branch "ditc-b3"
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?
B3 edit-pass per the program contracts (EDIT-PASS-template + COMMON-ditc), pages 310/320/330 sequential, one author.
Pages
doc_type/requires: [your-tenant]/introduces: [working copy, repo, manifest, shape, release, "release tag"].requires: [app-parts, pick-tenant],introduces: [scaffold].origin); reassurance "being careful, not broken" struck, mechanism kept; all four headings → claim form;requires: [scaffold],introduces: [deploy, channel, stable, "the checks", "the runner"]. Runner auto-restore + dry-run trust content kept verbatim.Glossary: +
working copy(defined_in: app-parts), +scaffold(defined_in: scaffold).Integration (2nd commit): 110/120 used "working copy" before its defining page — FIRST-USE/CONCEPT fail on 110:115/120:79 once 310 registers the term. Reworded to the plain description ("the copy that you and your assistant edit"); meaning unchanged; the term's first use now lands on 310 per the page map.
Gates (all green, coordinator-verified): build-docs --no-coverage --draft 0; check-prose --manual ditc clean (exit 0); check-lockstep --synthesize 0 fail (15 warn/18 skip unchanged); build-docs --draft 0; armada check-prose.sh exit 0 per page (310/320/330).
Read: the Operator reads 330 (per the batch table). Do not merge until that read lands.
The B3 batch registers 'working copy' in the glossary (defined_in: app-parts), which activates FIRST-USE/CONCEPT on the B1 pages' earlier colloquial uses. Reworded to the plain description ('the copy that you and your assistant edit'); meaning unchanged. Assisted-by: deepnet:synthetic/hf:zai-org/GLM-5.3-Flash