enterprise-forge

Files (4)

• SKILL.md
• evals.json · evals/
• adversarial-lenses.md · references/
• mechanical-checks.md · references/

SKILL.md (first lines)

# Enterprise Forge

The forge exists to break optimistic assumptions before production does.

## Entry Rule

Run this after `enterprise-review`, not instead of it.

Before forge starts, run the agent-bound forge gate in [agent-stage-gates.md](../enterprise/references/agent-stage-gates.md).

For non-trivial, schema-sensitive, tenant-sensitive, money/order/inventory/invoice, or UI workflow changes, forge should be multi-agent when available: split schema/data, code execution, E2E/workflow, security/tenant, and headless UI attack lenses. If delegation is unavailable, run the same attack lenses sequentially.

## Required Workflow

1. Run the checks in [mechanical-checks.md](references/mechanical-checks.md).
2. Probe contract promises from a new angle.
3. Apply the lenses in [adversarial-lenses.md](references/adversarial-lenses.md).
4. Map every changed runtime file to code-level execution proof.
5. Trace every cross-layer behavior source-to-consumer, including edge cases from plan/contract.
6. Require live DB proof for schema/query/data claims and headless browser proof for UI/PDF/file/upload/rendered workflows.
7. Attack the repo gate matrix: PR body/delivery gate, no-new-mock guard, DB ownership gate, live-proof registry, and required CI mirrors.
8. Treat any CI-driven implementation pivot as a fresh forge target for the affected files; previous `FORGED` output does not cover code it never saw.
9. If a bug is found, append a new contract item and recycle it through TDD.
10. Re-run until no bugs remain or a circuit breaker fires.

## Safeguards

- maximum 5 recycle iterations
- bug count must decrease each round
- stop if the same class of failure repeats 3 times

## Output

Write a forge report under `docs/reviews/` with:

- mechanical check results
- new bugs and appended contract items
- recycle history
- final verdict: `FORGED`, `REJECTED`, or `CIRCUIT BREAK`

Record the forge report in the current agent session before moving to verification.

From anotherben/agentic-governance, MIT.

More from anotherben/agentic-governance