ERP Acceptance Checklist
Version: 1.0 · ERP: v1.0 · Adapter: Cursor Adapter v1 · 1.0.0
Purpose: Confirm ERP is usable by a developer without prior project knowledge
Companion: docs/runtime-validation.md · docs/developer-guide.md
Complete this checklist after clone, before relying on ERP for production phase work or before Git freeze.
How to Use
| Symbol | Meaning |
|---|---|
| ☐ | Not verified |
| ✓ | Pass |
| ✗ | Fail — document in Remaining Gaps |
| N/A | Not applicable (e.g. Cloud mode unused) |
Record verifier name, date, and Cursor version in the sign-off section.
1. Installation Checklist
| # | Check | Pass |
|---|---|---|
| 1.1 | Repository cloned; project opens in Cursor | ☐ |
| 1.2 | .cursor/ directory present at project root | ☐ |
| 1.3 | docs/development/ENGINEERING_INDEX.md readable | ☐ |
| 1.4 | docs/developer-guide.md readable | ☐ |
| 1.5 | No dependency on ~/.cursor/ engineering assets for constraints | ☐ |
| 1.6 | Latest baseline identified in docs/releases/ | ☐ |
| 1.7 | .env configured for local Laravel (application — separate from ERP) | ☐ |
2. Cursor Setup
| # | Check | Pass |
|---|---|---|
| 2.1 | Cursor Agent session loads project (not user-global rules only) | ☐ |
| 2.2 | Settings → Rules: project rules visible (9 enforcement rules expected) | ☐ |
| 2.3 | Skills discovered under .cursor/skills/ (20 SKILL.md files) | ☐ |
| 2.4 | Agents discovered under .cursor/agents/ (10 agent files) | ☐ |
| 2.5 | Hooks enabled (Cursor Settings → Hooks) | ☐ |
| 2.6 | .cursor/mcp.json not required for basic ERP operation | ☐ |
3. Runtime Constraints Verification
| # | Check | Pass |
|---|---|---|
| 3.1 | 9 .mdc files in .cursor/rules/ | ☐ |
| 3.2 | 00-eos-authority.mdc references authority chain | ☐ |
| 3.3 | Agent refuses frozen platform edits when prompted | ☐ |
| 3.4 | Precedence documented in .cursor/rules/catalog/README.md | ☐ |
Details: docs/runtime-validation.md § Runtime Constraints
4. Runtime Procedures (Skills) Verification
| # | Check | Pass |
|---|---|---|
| 4.1 | runtime/manifests/defaults/procedures-manifest.md lists 10 domain procedures | ☐ |
| 4.2 | Each .cursor/skills/{domain}/SKILL.md cites RuntimeProcedureContract | ☐ |
| 4.3 | Agent can explain purpose of skill-architecture when asked | ☐ |
| 4.4 | Procedures do not claim architecture approval authority | ☐ |
5. Runtime Workflows Verification
| # | Check | Pass |
|---|---|---|
| 5.1 | runtime/manifests/defaults/workflows-catalog.md lists 10 workflows | ☐ |
| 5.2 | Each workflow skill has disable-model-invocation: true | ☐ |
| 5.3 | /bootstrap or bootstrap workflow produces Format B structure | ☐ |
| 5.4 | /phase workflow documentation references Format A | ☐ |
| 5.5 | No workflow claims Git freeze execution | ☐ |
6. Runtime Delegation Verification
| # | Check | Pass |
|---|---|---|
| 6.1 | runtime/manifests/defaults/delegation-manifest.md lists 10 delegates | ☐ |
| 6.2 | Readonly agents have readonly: true in frontmatter | ☐ |
| 6.3 | Delegation guard blocks readonly agent writes (manual smoke) | ☐ |
| 6.4 | Escalation path documented: Delegate → Developer → Architect | ☐ |
7. Runtime Enforcement (Hooks) Verification
| # | Check | Pass |
|---|---|---|
| 7.1 | .cursor/hooks.json schema version 1 | ☐ |
| 7.2 | git push blocked in agent shell (smoke test) | ☐ |
| 7.3 | --no-verify on git blocked (smoke test) | ☐ |
| 7.4 | MCP blocked when .cursor/mcp.json absent | ☐ |
| 7.5 | Four handlers present in .cursor/hooks/ | ☐ |
8. Runtime Context Providers Verification
| # | Check | Pass |
|---|---|---|
| 8.1 | runtime/manifests/defaults/context-providers-manifest.md — 3 Immediate tier | ☐ |
| 8.2 | All providers enabled: false in templates | ☐ |
| 8.3 | .cursor/mcp.json gitignored | ☐ |
| 8.4 | No secrets in committed .cursor/mcp/ files | ☐ |
9. Runtime Execution Verification
| # | Check | Pass |
|---|---|---|
| 9.1 | runtime/manifests/defaults/execution-manifest.md — 4 execution modes | ☐ |
| 9.2 | .cursor/cli.json present with deny rules | ☐ |
| 9.3 | .cursor/environment.json present (cloud bootstrap) | ☐ |
| 9.4 | Capability matrix understood (write vs approval) | ☐ |
| 9.5 | Cloud mode (if used): parity checklist reviewed | ☐ N/A |
10. Report Verification
| # | Check | Pass |
|---|---|---|
| 10.1 | templates/implementation-report.md defines Format A and B only | ☐ |
| 10.2 | Sample Format B report producible from documentation pass | ☐ |
| 10.3 | RESPONSE_TEMPLATE.md distinct from ERP reports | ☐ |
| 10.4 | Architect review uses nine sections (ERP v1.0) | ☐ |
11. Documentation Verification
| # | Check | Pass |
|---|---|---|
| 11.1 | docs/developer-guide.md answers onboarding questions | ☐ |
| 11.2 | DEVELOPMENT_WORKFLOW.md aligned with ERP terminology | ☐ |
| 11.3 | ENGINEERING_INDEX.md lists all manifests | ☐ |
| 11.4 | No broken links in docs/development/ (spot check) | ☐ |
Acceptance Criteria
ERP v1.0 is accepted when:
| Criterion | Required |
|---|---|
| All §1 Installation checks pass | Yes |
| §2 Cursor Setup pass | Yes |
| At least one smoke test in §7 Hooks pass | Yes |
| §5 Workflow explicit invocation understood | Yes |
| §10 Report formats understood | Yes |
| §11 Documentation readable by new developer | Yes |
| No blocking ✗ in §3–§9 without documented mitigation | Yes |
| Architect review of acceptance summary | Yes |
Partial acceptance: Document gaps in Format B report; proceed only with Architect Approved with hardening.
Sign-Off
| Field | Value |
|---|---|
| Verifier | |
| Date | |
| Cursor version | |
| ERP adapter version | 1.0.0 |
| Overall result | ☐ Accepted · ☐ Accepted with gaps · ☐ Not accepted |
Notes:
Friction Log (New Developer Perspective)
Use this section during acceptance review. Copy findings to Architect as Text Context.
| # | Friction | Severity | Suggested fix |
|---|---|---|---|
| 1 | |||
| 2 |
ERP Acceptance Checklist v1.0 — Phase 11-10. Does not replace PHPUnit architecture tests. Git freeze is Phase 11-11.