ditc B7 edit-pass: Asking + the structured path (910 + 920) — final ditc batch #11

Merged

jsutter merged 3 commits from ditc-b7 into main

2026-09-22 06:04:17 +00:00

jsutter commented

2026-09-22 06:01:38 +00:00

Owner

Final ditc edit-pass batch: 910-asking (guide) + 920-structured-path (explanation). One author pass (Kimi-K3), dispatcher pre-land + review fix. Branch rebased onto main @ dfde52f after B2/B6/dito-pilot merged; full battery re-run green on the rebased head.

Pages

src/ditc/910-asking.md — opening carries the one-line ask with inline code (ttfuf payoff 57 → 4); The patterns, collected → Pick the pattern that fits; the coined term asking for outcomes defined at first use; ASK callout to house voice (no standalone "I").
src/ditc/920-structured-path.md — topic headings → claims; stance sentence (We chose four named steps over one-shot edits because…, opinion_floor); papers metaphor struck — the instruction page, the spec templates, the manifest; the audit's required link back to 105 (the meeting-to-deploy arc) added early; coined term the four steps defined at first use; ASK callout to house voice.

Frontmatter (pre-land, commit aa0b1cf): doc_type/requires/introduces/verified: ditc@3.2.0 per the page map + the CONCEPT closure. The map's verbatim requires (910→105, 920→910+105) fails the lockstep CONCEPT gate (19 findings — tenant/app/deploy/preview/logs/history are defined on pages the map row does not name); requires carries the pages whose glossary terms the prose actually uses — the same resolution B4 evidenced (25 findings there) and landed on main. introduces coins: asking for outcomes (defined_in asking), the four steps (defined_in structured-path); the step names themselves stay out of the glossary (000 already uses "plan" — FIRST-USE).

Gates — all green on the rebased head (main @ dfde52f + B7)

Gate	Command	Result
1	`python3 tools/build-docs.py --no-coverage --draft`	exit 0
2	`python3 tools/check-prose.py --manual ditc`	`prose: clean`, exit 0
3	`python3 tools/check-lockstep.py --manual ditc --synthesize`	exit 0 — 21 pages, 50 terms, 0 fail
4	`python3 tools/build-docs.py --draft`	exit 0
5	`check-prose.sh --registry src/ditc/glossary.yaml src/ditc/<page>.md`	910 exit 0 (ttfuf payoff 4/20); 920 exit 0 (ttfuf 3/20)

Merge order: every other ditc batch is merged (B1–B6, PRs #4–#9); this is the last ditc PR — nothing points forward.

Plan gate: PENDING — the Operator reads page 920 before merge (the final-batch read). Do not merge until that read.

Final ditc edit-pass batch: 910-asking (guide) + 920-structured-path (explanation). One author pass (Kimi-K3), dispatcher pre-land + review fix. Branch rebased onto main @ dfde52f after B2/B6/dito-pilot merged; full battery re-run green on the rebased head. **Pages** - `src/ditc/910-asking.md` — opening carries the one-line ask with inline code (ttfuf payoff 57 → 4); `The patterns, collected` → `Pick the pattern that fits`; the coined term `asking for outcomes` defined at first use; ASK callout to house voice (no standalone "I"). - `src/ditc/920-structured-path.md` — topic headings → claims; stance sentence (`We chose four named steps over one-shot edits because…`, opinion_floor); `papers` metaphor struck — the instruction page, the spec templates, the manifest; the audit's required link back to 105 (the meeting-to-deploy arc) added early; coined term `the four steps` defined at first use; ASK callout to house voice. **Frontmatter** (pre-land, commit aa0b1cf): `doc_type`/`requires`/`introduces`/`verified: ditc@3.2.0` per the page map + the CONCEPT closure. The map's verbatim `requires` (910→105, 920→910+105) fails the lockstep CONCEPT gate (19 findings — tenant/app/deploy/preview/logs/history are defined on pages the map row does not name); `requires` carries the pages whose glossary terms the prose actually uses — the same resolution B4 evidenced (25 findings there) and landed on main. `introduces` coins: `asking for outcomes` (defined_in asking), `the four steps` (defined_in structured-path); the step names themselves stay out of the glossary (000 already uses "plan" — FIRST-USE). **Gates — all green on the rebased head (main @ dfde52f + B7)** | Gate | Command | Result | |---|---|---| | 1 | `python3 tools/build-docs.py --no-coverage --draft` | exit 0 | | 2 | `python3 tools/check-prose.py --manual ditc` | `prose: clean`, exit 0 | | 3 | `python3 tools/check-lockstep.py --manual ditc --synthesize` | exit 0 — 21 pages, 50 terms, 0 fail | | 4 | `python3 tools/build-docs.py --draft` | exit 0 | | 5 | `check-prose.sh --registry src/ditc/glossary.yaml src/ditc/<page>.md` | 910 exit 0 (ttfuf payoff 4/20); 920 exit 0 (ttfuf 3/20) | **Merge order**: every other ditc batch is merged (B1–B6, PRs #4–#9); this is the last ditc PR — nothing points forward. **Plan gate**: PENDING — the Operator reads page 920 before merge (the final-batch read). Do not merge until that read.

jsutter added 3 commits

2026-09-22 06:01:38 +00:00

ditc 910+920: pre-land B7 frontmatter + glossary coins for the edit pass 1b84d15a60

doc_type/requires/introduces/verified per the page map and the CONCEPT
closure (map-verbatim requires fails 19 CONCEPT checks — same shape B4
evidenced; requires carries the pages whose glossary terms the prose
uses). Coins: 'asking for outcomes' (defined_in asking) and 'the four
steps' (defined_in structured-path) — the map's introduces concepts as
glossary terms; the four step names themselves stay out of the glossary
(page 000 already uses 'plan', which would fail FIRST-USE). One table
cell in 910 reworded ('the four steps of' -> 'the four-step path in')
to keep FIRST-USE green before the author pass.

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

ditc 910+920: B7 edit-pass — claim/job headings, early payoff, the 105 link-back b0cccfeccb

910: opening now carries the one-line ask with inline code (ttfuf 4 of 20),
'The patterns, collected' becomes 'Pick the pattern that fits', the ASK
callout moves to house voice, and 'asking for outcomes' defines at first use.
920: headings state claims, 'dropped papers' names the instruction page and
the spec templates, a stance sentence carries the opinion, the 105 link-back
lands, and the ASK callout moves to house voice.

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

ditc 920: review fix — 'the app's papers' becomes 'the manifest' f8559f5e95

The manual-wide one-vocabulary pass names the product's thing once;
430's landed phrasing owns 'the manifest and its copied fact block' —
the metaphor never replaces the name.

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

jsutter force-pushed ditc-b7 from f8559f5e95 to 5cdbb1836c

2026-09-22 06:03:37 +00:00

Compare

jsutter merged commit 80aa653529 into main

2026-09-22 06:04:17 +00:00

jsutter referenced this pull request from a commit

2026-09-22 06:04:18 +00:00

Merge pull request 'ditc B7 edit-pass: Asking + the structured path (910 + 920) — final ditc batch' (#11) from ditc-b7 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!11

No description provided.

Rows
Columns