ditc B1 edit-pass: About + Your tenant (000 + 120) #4
Loading…
Reference in a new issue
No description provided.
Delete branch "ditc-b1"
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?
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):
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].##headings (explanation shape); the boundary's recoverability consequence kept verbatim. Frontmatter:doc_type: explanation,requires: [what-hosting-does],introduces: [tenant, app, user, operator].assistantentry'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)
tools/build-docs.py --no-coverage --drafttools/check-prose.py --manual ditctools/check-lockstep.py --manual ditc --synthesizetools/build-docs.py --draftcheck-prose.sh --registry src/ditc/glossary.yaml src/ditc/000-about.mdassumptions_linePASS (exactly one assumptions line in the first 15 body lines);ttfufPASS (first payoff line 7)check-prose.sh ... src/ditc/120-your-tenant.mdassumptions_lineSKIP verified on 000-about.md (the front page carries the line);opinion_floorPASS (1 marker);ttfufPASS (first payoff line 5)Term ledger
assistantintroduced here (About row per the page map, glossarydefined_in: about); prose otherwise common knowledge. No later-page term used before definition.tenant, app, user, operator(all fourdefined_in: your-tenant); usesplatform(105),hosting,web address(110),assistant(000) — allrequires:ancestors. Mechanical CONCEPT agrees (0 fails).Decisions the Operator may want to see
requiresomitted on 000 (dispatch saidrequires: []). 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.introduces: [tenant, app, user, operator]— the dispatch named three; the page definesusertoo ("You are the **user") and the glossary saysdefined_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).In practicegrounded 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.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