Issue Format and Issue Hierarchy currently live as large top-level Ways of Working pages with inbound links and navigation entries throughout the repository. They must move into the new OKF subtree without creating a broken intermediate state.
Request
Atomically relocate the existing guidance to Issues/Process/Format.md and Issues/Types/Hierarchy.md, create the Issues, Process, and Types indexes, and update navigation plus every inbound path and anchor in the same pull request. Preserve existing semantics; later Tasks own the new process and type content.
Acceptance criteria
src/docs/Ways-of-Working/Issues/index.md, Process/index.md, and Types/index.md exist with complete frontmatter and generated navigation tables
- Issue Format is moved to
Issues/Process/Format.md
- Issue Hierarchy is moved to
Issues/Types/Hierarchy.md
src/zensical.toml points to the new locations
- Every inbound repository link and heading anchor resolves to the new paths
- No compatibility stub, duplicate legacy page, or unindexed issue-guidance page remains
- Page content changes only where required for paths, titles, or navigation
- Index check, link validation, lint, clean Zensical build, CI, and Copilot review are green
Technical decisions
Atomic cutover: File moves, indexes, navigation, and all inbound references land together because deferring references would make the first pull request fail its own link and index checks.
Stable concepts: Format remains the universal body-format owner; Hierarchy remains the type and containment overview. Later Tasks split detailed process and type rules into nearby pages.
No redirect stubs: OKF indexes provide discovery. Old filenames are removed rather than preserved as duplicate routing pages.
Implementation plan
Relocation
Validation
Issue Format and Issue Hierarchy currently live as large top-level Ways of Working pages with inbound links and navigation entries throughout the repository. They must move into the new OKF subtree without creating a broken intermediate state.
Request
Atomically relocate the existing guidance to
Issues/Process/Format.mdandIssues/Types/Hierarchy.md, create the Issues, Process, and Types indexes, and update navigation plus every inbound path and anchor in the same pull request. Preserve existing semantics; later Tasks own the new process and type content.Acceptance criteria
src/docs/Ways-of-Working/Issues/index.md,Process/index.md, andTypes/index.mdexist with complete frontmatter and generated navigation tablesIssues/Process/Format.mdIssues/Types/Hierarchy.mdsrc/zensical.tomlpoints to the new locationsTechnical decisions
Atomic cutover: File moves, indexes, navigation, and all inbound references land together because deferring references would make the first pull request fail its own link and index checks.
Stable concepts: Format remains the universal body-format owner; Hierarchy remains the type and containment overview. Later Tasks split detailed process and type rules into nearby pages.
No redirect stubs: OKF indexes provide discovery. Old filenames are removed rather than preserved as duplicate routing pages.
Implementation plan
Relocation
Validation