deepnet/ditdocs
Watch
8
0
Fork
You've already forked ditdocs
 0
Code Issues 2 Pull requests Projects Releases Packages Wiki Activity Actions

docs: dito manual — retire the onboarding-bundle consumption flow #19

Merged
jsutter merged 2 commits from docs/dito-manual-bundle-retire into main 2026-09-23 19:07:26 +00:00
Conversation 0 Commits 2 Files changed 74 +520 -414
jsutter commented 2026-09-23 19:05:53 +00:00
Owner
Copy link

Cross-manual drift fix flagged by the ditc 3.3.0 wave (#18): the dito manual still taught the retired ditc tenant onboard --bundle consumption flow (the verb left the shipped ditc surface before 3.2.1, c753a72; the nightly drift gate structurally misses this because dito's own CLI surface did not change).

  • src/dito/430-users.md: the whole user lifecycle re-authored onto the shipped flow — operator side dito user invite --tenant <slug> --email <addr> --full-name "<Name>", invitation email carries the hand-off, the person runs ditc session login <address> --device; rotate re-mints in place (no delivery); offboard re-invite note fixed (~40 sites incl. SVG figure + 3 procedures)
  • src/dito/glossary.yaml: the "bundle" entry (defined via the retired flow) deleted; custody-store emergency-bundles keeps its own sense
  • src/dito/450-authentik-ui.md: 5 sites -> dito user invite
  • src/dito/440-app-access.md: "onboard the seat" -> "invite the seat"
  • captures/dito/*: re-walked from shipped dito v6.1.0-rc.26 (user--onboard removed; user--invite/converge added); state+worktree nouns exempted pending their own wave

Kept (verified different senses): custody/emergency bundles (510/520/710/730), dito operator onboard (420/450/110/120/130), runbook path refs; the skill-doc retirement-record row stays.

Ground truth observed: ditc 3.3.0 binary has no tenant onboard, session login --device present; dito-v6.1.0-rc.26 installed binary matches the new captures.

Gates (local, CI invocations): check-coverage OK (12 dito groups), check-prose clean, check-lockstep dito 0 fail, build-docs + link-check OK.

Cross-manual drift fix flagged by the ditc 3.3.0 wave (#18): the dito manual still taught the retired `ditc tenant onboard --bundle` consumption flow (the verb left the shipped ditc surface before 3.2.1, c753a72; the nightly drift gate structurally misses this because dito's own CLI surface did not change). - src/dito/430-users.md: the whole user lifecycle re-authored onto the shipped flow — operator side `dito user invite --tenant <slug> --email <addr> --full-name "<Name>"`, invitation email carries the hand-off, the person runs `ditc session login <address> --device`; rotate re-mints in place (no delivery); offboard re-invite note fixed (~40 sites incl. SVG figure + 3 procedures) - src/dito/glossary.yaml: the "bundle" entry (defined via the retired flow) deleted; custody-store emergency-bundles keeps its own sense - src/dito/450-authentik-ui.md: 5 sites -> `dito user invite` - src/dito/440-app-access.md: "onboard the seat" -> "invite the seat" - captures/dito/*: re-walked from shipped dito v6.1.0-rc.26 (user--onboard removed; user--invite/converge added); state+worktree nouns exempted pending their own wave Kept (verified different senses): custody/emergency bundles (510/520/710/730), `dito operator onboard` (420/450/110/120/130), runbook path refs; the skill-doc retirement-record row stays. Ground truth observed: ditc 3.3.0 binary has no `tenant onboard`, `session login --device` present; dito-v6.1.0-rc.26 installed binary matches the new captures. Gates (local, CI invocations): check-coverage OK (12 dito groups), check-prose clean, check-lockstep dito 0 fail, build-docs + link-check OK.
dito 6.1.0-rc.26 shipped 2026-09-23; the committed captures still said
4.1.12-rc.1 and taught user onboard + the bundle path that the same
release deleted. Re-walked with tools/capture-cli.py from the shipped
binary. user--onboard.txt goes (the verb is gone); user--invite.txt and
user--converge.txt arrive; state + worktree join exempt_groups until
their narrative pages ride a later dito manual wave.

Assisted-by: worker:synthetic/hf:zai-org/GLM-5.3-Flash
The bundle path retired (user-identity-declaration D8, 2026-09-12) and
ditc tenant onboard left the shipped ditc surface before 3.2.1, but the
dito manual still taught dito user onboard -> bundle -> ditc tenant
onboard --bundle. 430 now teaches the shipped flow — dito user invite
provisions the seat and sends the invitation email; the person signs in
with ditc session login <address> --device — rotate re-mints in place
with no delivery, and offboard's re-invite note follows. 450 and 440
drop their onboard/bundle wording; the glossary bundle term goes (the
custody-store emergency bundles keep their own sense).

Assisted-by: worker:synthetic/hf:zai-org/GLM-5.3-Flash
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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!19
No description provided.