| name | enterprise-compound |
| description | Use when verified enterprise work or a resolved debugging session should be captured as searchable institutional knowledge with prevention guidance |
Enterprise Compound
Capture the lesson while it is still fresh.
Required Workflow
- Run the agent-bound compound gate in agent-stage-gates.md.
- Search for an existing related solution note.
- If none exists, create one under
docs/solutions/YYYY-MM-DD-<slug>.md.
- Use solution-template.md.
- Focus on retrieval and prevention, not storytelling.
Required Content
- the problem or decision
- the root cause or rationale
- the actual change
- the blast radius or related checks
- the prevention pattern
- tags that make the note searchable later
This stage is post-verification knowledge capture.
Proof Boundary Rule
- Carry forward the upstream proof boundary exactly as verified.
- Do not upgrade a prior
function-level, slice-level, or domain-level result into full-system.
- If the verified work still had unproven legs, keep the fail-closed posture explicit in the compound note.
- Do not use the solution note itself as evidence that unresolved enterprise scope is now closed.
