zemion
2ffdb23f69
Verified with the coordinated workspace changes by devkit full run 2026-09-08T225814-186389-0000-3e3ed7cd (all seven phases passed). This shared UI pass does not mark the individual module reviews complete.
1.7 KiB
GovOPlaN Workspace Codex Guide
Scope
This repository coordinates the GovOPlaN workspace, release catalog, shared checks, development environment, and cross-repository automation. Business and platform behavior remains owned by the corresponding module repository.
Documentation Contract
- Treat documentation as part of every behavior change. Update the owning module's manifest-driven
DocumentationTopiccontributions for each affected user and administrator workflow, setting, permission, limitation, and operational consequence. - Keep feature content in the owning module. The optional
govoplan-docsmodule projects module contributions and must not import feature internals. - Every module manifest must provide a static user and administrator baseline, even when
documentation_providersadd configured-state details. - Run
tools/checks/check-manifest-shapes.pyafter module behavior or manifest changes. Runtools/checks/check-focused.shfor cross-module changes.
Working Rules
-
Start repeated workflows with
./devkit commands; usecontext --changed,check --profile quick --changed --dry-run, andreview MODULEinstead of reconstructing repository/check inventories. Seedocs/operations/DEVKIT.md. -
Prefer compact check receipts (
status,summary,logs) to repeated full log dumps.check --profile fullretains the required focused gate; targeted profiles or cached results do not waive required verification or approvals. -
Treat Gitea issues as the canonical backlog and state log.
-
Preserve optional module boundaries and use Core contracts or capabilities for integrations.
-
Prefer targeted checks before full workspace scans.
-
Do not start persistent development servers unless requested.