ditc B6 edit-pass: Troubleshooting + Reporting + Retire (810 + 820 + 830) #9

Merged

jsutter merged 2 commits from ditc-b6 into main

2026-09-22 05:50:27 +00:00

jsutter commented

2026-09-22 05:49:15 +00:00

Owner

B6 edit-pass batch (ditc program)

One author pass over the three Chapter-8 pages. Edit-pass contract: program/ditc-contracts/EDIT-PASS-template.md + COMMON-ditc.md; audit disposition rows 810-troubleshooting, 820-reporting, 830-retire. Rebased onto current main (2bf4428) after B3–B5 landed during the pass; re-verified end-to-end on the new base.

Per page

810-troubleshooting — "the app's papers" pinned to the manifest everywhere (lede, table, body, procedure, svg label, aria-label, figcaption, summary); "The reads cost nothing:" struck, mechanism kept; the repeated reassurance sentence ("the platform being careful, not the page being broken") struck — 330 carries the canonical instance; six topic headings → imperatives; DeepNet-side restore points kept prominent.
820-reporting — two topic headings → imperatives; trust rules kept verbatim (strip-before-send; the checks stop deploys by design).
830-retire — three topic headings → imperatives; the data question kept prominent (now lede + inline gloss + heading + WARNING + Before-you-begin + ASK); irreversibility framing verbatim; procedure steps moved to the ask voice.

Frontmatter (lockstep R8 concept closure)

810: requires [first-deploy, your-tenant, app-parts, promote-rollback, pick-tenant]; introduces [logs]
820: requires [troubleshooting]; introduces [feedback report, feedback widget]
830: requires [secrets, troubleshooting]; introduces [destroy, the data question]

Glossary

Landed the data question (defined_in: retire). retire stays an ordinary verb (610 uses "retire the secret" first; common-knowledge rule).

Gates (all green on the rebased branch, re-run by the coordinator)

gate	result
tools/build-docs.py --no-coverage --draft	exit 0
tools/check-prose.py --manual ditc	clean
tools/check-lockstep.py --manual ditc	exit 0 (0 fail; 46 terms; CONCEPT green on all three)
tools/build-docs.py --draft	exit 0
armada check-prose.sh --registry src/ditc/glossary.yaml (per page)	exit 0 ×3

Edit-pass delta (body): 810 ±0, 820 ±0, 830 −2 lines. Evaluator pass: Q8 none, Q9 none on all three.

Operator reads page 810 in full for this batch (the one-page-per-batch review). Plan-gate approval recorded PENDING for ditc-b6 until that read.

## B6 edit-pass batch (ditc program) One author pass over the three Chapter-8 pages. Edit-pass contract: program/ditc-contracts/EDIT-PASS-template.md + COMMON-ditc.md; audit disposition rows 810-troubleshooting, 820-reporting, 830-retire. Rebased onto current main (2bf4428) after B3–B5 landed during the pass; re-verified end-to-end on the new base. ### Per page - **810-troubleshooting** — "the app's papers" pinned to the manifest everywhere (lede, table, body, procedure, svg label, aria-label, figcaption, summary); "The reads cost nothing:" struck, mechanism kept; the repeated reassurance sentence ("the platform being careful, not the page being broken") struck — 330 carries the canonical instance; six topic headings → imperatives; DeepNet-side restore points kept prominent. - **820-reporting** — two topic headings → imperatives; trust rules kept verbatim (strip-before-send; the checks stop deploys by design). - **830-retire** — three topic headings → imperatives; the data question kept prominent (now lede + inline gloss + heading + WARNING + Before-you-begin + ASK); irreversibility framing verbatim; procedure steps moved to the ask voice. ### Frontmatter (lockstep R8 concept closure) - 810: requires [first-deploy, your-tenant, app-parts, promote-rollback, pick-tenant]; introduces [logs] - 820: requires [troubleshooting]; introduces [feedback report, feedback widget] - 830: requires [secrets, troubleshooting]; introduces [destroy, the data question] ### Glossary - Landed `the data question` (defined_in: retire). `retire` stays an ordinary verb (610 uses "retire the secret" first; common-knowledge rule). ### Gates (all green on the rebased branch, re-run by the coordinator) | gate | result | |---|---| | tools/build-docs.py --no-coverage --draft | exit 0 | | tools/check-prose.py --manual ditc | clean | | tools/check-lockstep.py --manual ditc | exit 0 (0 fail; 46 terms; CONCEPT green on all three) | | tools/build-docs.py --draft | exit 0 | | armada check-prose.sh --registry src/ditc/glossary.yaml (per page) | exit 0 ×3 | Edit-pass delta (body): 810 ±0, 820 ±0, 830 −2 lines. Evaluator pass: Q8 none, Q9 none on all three. **Operator reads page 810 in full for this batch** (the one-page-per-batch review). Plan-gate approval recorded PENDING for ditc-b6 until that read.

jsutter added 2 commits

2026-09-22 05:49:15 +00:00

ditc 810+820+830: B6 edit-pass — papers pinned to the manifest, reassurance struck, imperative headings 627964c27c

Troubleshooting (810): "the app's papers" pinned to the manifest everywhere
(lede, table, body, procedure step, svg label, aria-label, figcaption,
summary); "The reads cost nothing:" struck with the mechanism kept ("each one
looks and answers, and none of them changes anything"); the repeated
reassurance sentence ("the platform being careful, not the page being
broken") struck from the symptom table — 330 carries the canonical instance;
six topic headings now imperatives (Run the four reads / Read the app's
manifest / Read the logs / Read the history / Read the tenant's services /
Match the symptom to the first read); DeepNet-side restore points kept
prominent.

Reporting (820): two topic headings now imperatives (Collect visitor reports
through the form / Report the tool itself); trust rules kept verbatim
(strip-before-send, the checks stop deploys by design).

Retire (830): three topic headings now imperatives (See what destroy removes
/ Settle the data question first / Rehearse the removal); the data question
kept prominent — heading, WARNING callout, Before-you-begin bullet, ASK
prompt — and now glossed inline at first use (the landed glossary term);
irreversibility framing verbatim; procedure steps moved to the ask voice;
"the rehearsal is where the cheap mistakes stay" tightened to the mechanism.

Frontmatter per lockstep R8 (concept closure): requires [first-deploy,
your-tenant, app-parts, promote-rollback, pick-tenant] / [troubleshooting] /
[secrets, troubleshooting]; introduces [logs] / [feedback report, feedback
widget] / [destroy, the data question].

Edit-pass contract: program/ditc-contracts/EDIT-PASS-template.md +
COMMON-ditc.md; audit disposition rows 810-troubleshooting, 820-reporting,
830-retire.

Assisted-by: author:synthetic/hf:moonshotai/Kimi-K3

ditc glossary: land 'the data question' — the B6 retire edit pass owns the deciding sentence 5f689a26b6

Page map row 8.3 names the data question among 830's introductions; the
entry glosses the decision (what survives the removal and where its restore
points live — settled with your operator before you destroy anything).
Retire itself stays an ordinary verb per the common-knowledge rule — 610
uses "retire the secret" before the page.

Assisted-by: deepnet:synthetic/hf:zai-org/GLM-5.3-Flash

jsutter merged commit 143f750cb2 into main

2026-09-22 05:50:27 +00:00

jsutter referenced this pull request from a commit

2026-09-22 05:50:27 +00:00

Merge pull request 'ditc B6 edit-pass: Troubleshooting + Reporting + Retire (810 + 820 + 830)' (#9) from ditc-b6 into main

No reviewers

No labels

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

deepnet/ditdocs!9

No description provided.

Rows
Columns