context-governance

To audit project context files, run a full context audit to inventory files, validate architecture, scan for stale TODOs, and detect version drift. This process classifies context files and proposes safe remediation actions for any broken governance structure.

A lite governance audit is a fast startup check that detects missing canonical files, duplicate active handoffs, version mismatches, and stale working-copy risks. It validates multi-agent handoffs before escalating to a full audit if red flags are found.

Run a context audit when a session starts, before a major task, or when you suspect parallel work or archived files have created conflicting sources of truth. This prevents broken handoffs and incorrect planning caused by stale governance files.

Yes, you can update a project manifest during a full context audit. The audit updates the manifest with verification status and newly discovered files, ensuring the governance structure accurately reflects the current project context.

Yes, context governance applies to governed software projects initialized with a context manifest. It requires dynamic project-root detection to verify canonical documents, memory files, and handoffs during session startup and pre-task checks.

When a full context audit encounters unresolved contradictions, it triggers a stop-report safety mechanism. This bounded remediation planning stops the audit process to prevent incorrect planning or work on the wrong project copy.