# GovOPlaN Ops Codex Guide

## Documentation Contract

- Treat documentation as part of every behavior change. Update this module's manifest-driven `DocumentationTopic` contributions for affected user and administrator behavior.
- Keep feature content here; `govoplan-docs` projects it without importing Ops internals.
- Maintain a static user/admin baseline and run `/mnt/DATA/git/govoplan/tools/checks/check-manifest-shapes.py` after behavior or manifest changes.

## Scope

This repository owns the GovOPlaN operations module seed: runtime health,
deployment profile visibility, worker split assumptions, sizing assumptions,
maintenance readiness, and operator-facing status surfaces.

## Boundaries

- Depend on kernel contracts from `govoplan-core`.
- Do not import feature-module internals.
- Expose integration through manifests, API routes, permissions, and typed DTOs.
- Keep destructive operator actions in core safety-controlled workflows.

## Local Workflow

Use Gitea issues as the canonical backlog and state log. Focused verification is
still driven from `/mnt/DATA/git/govoplan-core` for cross-repository behavior.