Repository navigation
Docs: complete the audience-split education layer (docs/wikis/) #401
Description
Summary
standards had no education layer beyond the QUICKSTART-*.adoc setup guides and no wiki mirror. A scaffold landed in #398 (docs/wikis/ with Users / Developers / Maintainers tracks + a machine manifest, following the k9-svc/*/docs/wikis/ pattern). This issue tracks completing it into a full learning resource — "beyond mere setup and basic run-through."
Remaining work
- Write each track's core-concept prose (replace the
TODOmarkers indocs/wikis/{users,developers,maintainers}/index.adoc). - Decide hosting: forge-hosted wiki (synced out from
docs/wikis/) vs in-repo only. - Add a glossary (A2ML, K9, RSR, CRG, contractile, innervation, 6a2).
- Add per-track worked examples (adopt a repo / write a Hypatia rule / cut a standards change).
- Keep the machine mirror (
docs/wikis/0.2-AI-MANIFEST.a2ml) in step as tracks grow.
Refs
- docs(wikis): scaffold audience-split education layer (Users/Developers/Maintainers) #398 (scaffold PR)
docs/wikis/README.adoc
Why
The dev/maintainer/user split exists only at quickstart depth; the deeper "engage fully with the materials" layer is scattered across EXPLAINME.adoc, the ADRs, the policies, and .claude/CLAUDE.md. This organizes it into an audience-segmented path.
Activity
hyperpolymath commentedon Aug 25, 2026
2026-08-25 — all three audience wikis exist and all three still carry TODOs
docs/wikis/users/index.adoc(6 TODOs) ·developers/index.adoc(7) ·maintainers/index.adoc(5) ·README.adoc(2).Structure done, content outstanding.
recurringlabel is documentary intent — nothing in this repo regenerates or reopens it (verified: zerogh issue create|reopenmatches across.github/,scripts/,tools/,tasks/,hooks/).Verified 2026-08-25.
hyperpolymath commentedon Aug 27, 2026
Next step (re-verified 2026-08-27): the #398 scaffold is present and untouched — 5 files carrying 20 TODO markers (README 2, developers 7, maintainers 5, users 6), and no glossary exists anywhere under
docs/. Every checkbox unticked.→ Prose authoring: three track indexes + a glossary, from the existing skeletons. Medium. One embedded owner call: forge-wiki vs in-repo hosting — recommend in-repo (wikis are invisible to the registry/scorecard machinery and to clones).
hyperpolymath commentedon Sep 30, 2026
RULING D135 (2026-09-30T14:11Z) · scope: estate · basis: owner (direct answer, selector)
OWNER TEXT: "should be using a berrywiki for standards, and then your recommendation when moved to that" — standards docs move to a berrywiki (metadatastician/berrywiki, hierarchical notebook over the GitHub wiki); once moved: single source of truth, optional one-way sync, no Pages/Jekyll (D24)
surface: #787 (comment)
The open question in this issue is answered by the ruling above; future agents should act on it rather than re-ask.