ditc B1 edit-pass: About + Your tenant (000 + 120) #4

Merged
jsutter merged 2 commits from ditc-b1 into main 2026-09-22 04:58:33 +00:00
Owner

Batch B1 (pages 000 + 120) — edit pass, read page 000 for the Operator read

Two pages of the B1 batch under the EDIT-PASS contract (program/ditc-contracts/EDIT-PASS-template.md + COMMON-ditc.md; audit disposition rows 000-about and 120-your-tenant):

  • 000-about (front page): one vocabulary assistant (prose, figure label, aria-labels, summary); reader definition + the Operator-confirmed positive literacy line in the first 15 body lines; reading-process narration dropped, adjacent mechanisms kept; marketing coda and reassurance struck; 'undo a mistake with one command' kept (trust content). Frontmatter: doc_type: guide, introduces: [assistant].
  • 120-your-tenant: the five names (tenant, app, user, operator, assistant) each defined once and crisply; four claim-form ## headings (explanation shape); the boundary's recoverability consequence kept verbatim. Frontmatter: doc_type: explanation, requires: [what-hosting-does], introduces: [tenant, app, user, operator].
  • Glossary (integration commit): the assistant entry's plain now avoids defining the term with the term itself; the About row's own comment names the About edit pass as owner of the defining sentence. Tenant/app/user/operator plains already match 120's defining sentences.

Gate results (all green)

Gate Result
tools/build-docs.py --no-coverage --draft exit 0 — KNOWN_KEYS validates the new frontmatter
tools/check-prose.py --manual ditc clean, exit 0
tools/check-lockstep.py --manual ditc --synthesize exit 0 — ditc 0 fail (000: CONCEPT SKIP by design; 120: MESSAGE SKIP informational)
tools/build-docs.py --draft exit 0
armada check-prose.sh --registry src/ditc/glossary.yaml src/ditc/000-about.md exit 0 — assumptions_line PASS (exactly one assumptions line in the first 15 body lines); ttfuf PASS (first payoff line 7)
armada check-prose.sh ... src/ditc/120-your-tenant.md exit 0 — assumptions_line SKIP verified on 000-about.md (the front page carries the line); opinion_floor PASS (1 marker); ttfuf PASS (first payoff line 5)

Term ledger

  • 000: assistant introduced here (About row per the page map, glossary defined_in: about); prose otherwise common knowledge. No later-page term used before definition.
  • 120: introduces tenant, app, user, operator (all four defined_in: your-tenant); uses platform (105), hosting, web address (110), assistant (000) — all requires: ancestors. Mechanical CONCEPT agrees (0 fails).

Decisions the Operator may want to see

  1. requires omitted on 000 (dispatch said requires: []). The empty list's presence activates the CONCEPT gate with a zero-ancestor set — 5 unfixable fails (ditc, platform, user, app, preview: an About page must name its own tool and the platform). Absence is the designed exemption — dito/scribe About pages ship without it and FIRST-USE covers the front page. Tool-side carve-out alternative possible; flagged.
  2. introduces: [tenant, app, user, operator] — the dispatch named three; the page defines user too ("You are the **user") and the glossary says defined_in: your-tenant, so the ledger carries all four. assistantcannot ride on 120 (glossarydefined_in: about` per page-map row 0; the build hard-fails).
  3. 'locked drawer' kept on 120 — pinned to OpenBao in the once-parentheses form and matched to the glossary's own registered plains (610 back-reference verified). COMMON-ditc lists it among metaphors to replace; replacing it here would split page vs registry vocabulary. Registry-wide rename = its own change.
  4. Armada gate remedies per the spec's own text: imperative-led opener sentences (ttfuf 'moving one sentence up clears it') and one In practice grounded stance sentence on 120 (opinion_floor 'one grounded sentence clears it', copying 110's landed shape).

Next batch finding

105 (pilot, landed pre-gate) still fails the armada gate on opinion_floor (zero markers) — same class as this batch's 120; its cleanup belongs to 105's own later pass. 110 (landed) passes clean.

## Batch B1 (pages 000 + 120) — edit pass, read page **000** for the Operator read Two pages of the B1 batch under the EDIT-PASS contract (program/ditc-contracts/EDIT-PASS-template.md + COMMON-ditc.md; audit disposition rows 000-about and 120-your-tenant): - **000-about** (front page): one vocabulary `assistant` (prose, figure label, aria-labels, summary); reader definition + the Operator-confirmed positive literacy line in the first 15 body lines; reading-process narration dropped, adjacent mechanisms kept; marketing coda and reassurance struck; **'undo a mistake with one command' kept** (trust content). Frontmatter: `doc_type: guide`, `introduces: [assistant]`. - **120-your-tenant**: the five names (tenant, app, user, operator, assistant) each defined once and crisply; four claim-form `##` headings (explanation shape); the boundary's recoverability consequence kept verbatim. Frontmatter: `doc_type: explanation`, `requires: [what-hosting-does]`, `introduces: [tenant, app, user, operator]`. - **Glossary** (integration commit): the `assistant` entry's plain now avoids defining the term with the term itself; the About row's own comment names the About edit pass as owner of the defining sentence. Tenant/app/user/operator plains already match 120's defining sentences. ## Gate results (all green) | Gate | Result | |---|---| | `tools/build-docs.py --no-coverage --draft` | exit 0 — KNOWN_KEYS validates the new frontmatter | | `tools/check-prose.py --manual ditc` | clean, exit 0 | | `tools/check-lockstep.py --manual ditc --synthesize` | exit 0 — ditc 0 fail (000: CONCEPT SKIP by design; 120: MESSAGE SKIP informational) | | `tools/build-docs.py --draft` | exit 0 | | armada `check-prose.sh --registry src/ditc/glossary.yaml src/ditc/000-about.md` | **exit 0 — `assumptions_line` PASS** (exactly one assumptions line in the first 15 body lines); `ttfuf` PASS (first payoff line 7) | | armada `check-prose.sh ... src/ditc/120-your-tenant.md` | exit 0 — `assumptions_line` SKIP verified on 000-about.md (the front page carries the line); `opinion_floor` PASS (1 marker); `ttfuf` PASS (first payoff line 5) | ## Term ledger - 000: `assistant` introduced here (About row per the page map, glossary `defined_in: about`); prose otherwise common knowledge. No later-page term used before definition. - 120: introduces `tenant, app, user, operator` (all four `defined_in: your-tenant`); uses `platform` (105), `hosting`, `web address` (110), `assistant` (000) — all `requires:` ancestors. Mechanical CONCEPT agrees (0 fails). ## Decisions the Operator may want to see 1. **`requires` omitted on 000** (dispatch said `requires: []`). The empty list's presence *activates* the CONCEPT gate with a zero-ancestor set — 5 unfixable fails (ditc, platform, user, app, preview: an About page must name its own tool and the platform). Absence is the designed exemption — dito/scribe About pages ship without it and FIRST-USE covers the front page. Tool-side carve-out alternative possible; flagged. 2. **`introduces: [tenant, app, user, operator]`** — the dispatch named three; the page defines `user` too ("You are the **user`") and the glossary says `defined_in: your-tenant`, so the ledger carries all four. `assistant` cannot ride on 120 (glossary `defined_in: about` per page-map row 0; the build hard-fails). 3. **'locked drawer' kept on 120** — pinned to OpenBao in the once-parentheses form and matched to the glossary's own registered plains (610 back-reference verified). COMMON-ditc lists it among metaphors to replace; replacing it here would split page vs registry vocabulary. Registry-wide rename = its own change. 4. Armada gate remedies per the spec's own text: imperative-led opener sentences (ttfuf 'moving one sentence up clears it') and one `In practice` grounded stance sentence on 120 (opinion_floor 'one grounded sentence clears it', copying 110's landed shape). ## Next batch finding 105 (pilot, landed pre-gate) still fails the armada gate on `opinion_floor` (zero markers) — same class as this batch's 120; its cleanup belongs to 105's own later pass. 110 (landed) passes clean.
About (000): helper→assistant everywhere (prose, figure label, aria-labels,
summary); reader definition + the Operator-confirmed positive literacy line
in the first 15 body lines; reading-process narration dropped, mechanisms
kept; marketing coda and reassurance struck; 'undo a mistake with one
command' kept. Frontmatter: doc_type guide, introduces [assistant].
requires deliberately OMITTED — an empty requires: list activates
check-lockstep's CONCEPT gate with a zero-ancestor set (5 unfixable fails:
ditc, platform, user, app, preview); absence is the designed exemption
(all three manuals' About pages ship without it; FIRST-USE covers the front
page).

Your tenant (120): the five names each defined once and crisply; four
claim-form headings; frontmatter doc_type explanation, requires
[what-hosting-does], introduces [tenant, app, user, operator].

Armada gate remedies per check-prose-spec (ttfuf 'moving one sentence up
clears it'; opinion_floor 'one grounded sentence clears it', 110's landed
shape): imperative-led opener sentences on both pages; one 'In practice'
grounded stance sentence on 120.

Edit-pass contract: program/ditc-contracts/EDIT-PASS-template.md +
COMMON-ditc.md; audit disposition rows 000-about, 120-your-tenant.

Assisted-by: author:synthetic/hf:moonshotai/Kimi-K3
The entry defined the term with the term itself ('the AI assistant that...');
About's defining sentence avoids that, and the glossary comment at the
assistant row names the About edit pass as the owner of the defining
sentence. Tenant/app/user/operator plains already match 120's defining
sentences.

Assisted-by: deepnet:synthetic/hf:zai-org/GLM-5.3-Flash
Sign in to join this conversation.
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!4
No description provided.