Repository navigation
Describe issue phases, planning, and relationships #88
Description
Once the issue guidance has an OKF Process subtree, it needs concise pages that explain how an issue evolves through the existing workflow, when planning introduces Why/How/What detail, and how native relationships distinguish containment from order.
Request
Add Lifecycle, Planning, and Relationships pages under Issues/Process/, and reduce the universal Format page to rules shared by every type. Link to Workflow for phase definitions rather than restating it.
Acceptance criteria
- Lifecycle maps issue-body, type, readiness, and relationship changes onto Capture, Refine, Plan, Build, Review, Ship, and Operate
- Workflow remains the sole owner of phase definitions
- Planning explains progressive Why/How/What decomposition without duplicating spec/design ownership
- Relationships defines native sub-issues as containment and progress
- Relationships defines native blocked-by/blocking edges as execution order
- Ready siblings without dependency edges are explicitly eligible for parallel execution
- Manual
Parent:,Blocked by:, child-link lists, and list-order sequencing are rejected as duplicate sources of truth - Format contains only universal issue rules and routes type-specific guidance to the Types subtree
- Process index, links, lint, clean build, CI, and Copilot review are green
Technical decisions
Phase ownership: Workflow.md defines the phases. Lifecycle states only what happens to issues as they pass through them.
Planning altitude: Epic carries strategic Why and outcome-level What; PBI carries delivery-level How and bounded What; Task/Bug carries the concrete deliverable and implementation decisions. Each child still explains its local purpose and acceptance criteria.
Native relationships: GitHub relationships are authoritative. Prose records rationale, never a second relationship graph.
Implementation plan
Process pages
- Add Lifecycle with phase-specific issue evolution and gates
- Add Planning with Why/How/What decomposition rules
- Add Relationships with containment, sequence, and parallelism rules
- Reduce Format to universal rules and type-page routing
Validation
- Verify Process index and all internal links
- Run documentation checks, CI, and the Copilot review loop
Activity
MariusStorhaug commentedon Jul 25, 2026
Implemented the Process-page scope in commit
e1d9e60and opened the draft pull request. Lifecycle, Planning, Relationships, and the reduced universal Format page are now present. Validation remains open while navigation is added and the parallel Types targets are serialized from the live default branch.MariusStorhaug commentedon Jul 25, 2026
Completed final validation after integrating PR #93 into PR #94 as requested. Merge commit
f077ba3added the canonical type targets; review fixesb872f08and2c3d91bclarified delivery-leaf ownership, Process metadata, and PBI wording. Documentation indexes update and check cleanly, all links resolve, the clean Zensical build reports no issues, Build/Links/Lint CI pass, every review thread is resolved, and the fresh Copilot round at 23:37:10Z produced zero new comments.MariusStorhaug commentedon Jul 25, 2026
Reopened the final validation checklist after the user-directed merge of PR #93 into PR #94. The combined branch is green and Copilot-clean, but #94 remains draft until #93 independently merges and live
mainabsorbs the Types scope. Final Process-only validation, CI, and review will run again after that reconciliation.MariusStorhaug commentedon Jul 25, 2026
Generated-index rationale: updating
Process/index.mdfrontmatter so navigation describes lifecycle, planning, and native relationships necessarily changes the generated Process row inIssues/index.md. Both changes are in2c3d91b; the parent-row edit is generated integration, not an independently authored scope expansion.📖 [Docs]: Issue planning and relationships are defined (#94)
MariusStorhaug commentedon Jul 26, 2026
Final combined validation completed at
b2a1f37: the branch is based on liveorigin/mainf3aede8; documentation indexes update and check without drift; all internal links resolve; the clean Zensical build reports no issues; exact-head Build, Links, and Lint CI are green; all review threads are resolved; and the explicit Copilot round at 23:59:57Z is clean with zero comments. The issue is reopened so PR #94 remains the authoritative closing event.MariusStorhaug commentedon Jul 26, 2026
PR #94 merged as squash
f156c3658969b03250c8af79a452649106aa5df3. This manual close corrects a race where the final validation update reopened the issue immediately after GitHub had closed it for the merge.