Implementation Guides¶
Choose an alpha implementation path and use ACGP-6 as the authoritative source for claim and badge semantics.
Implementation Paths¶
- Claimable now: Standard
- Optional additive badge: Regulated Controls Badge
- Non-conformant runtime mode: Dev Mode
Claim scope
Standard is the only active claimable profile in alpha. Regulated Controls Badge is additive, and Dev Mode is a non-conformant runtime mode.
Implementation Steps¶
Follow these guides in order:
Step 1: Write Your First Blueprint¶
- Blueprint Usage — author policy in blueprints and evaluate it through GovernanceSteward
Step 2: Connect to Your Framework¶
- Integration Walkthrough — end-to-end from install to verification
Step 3: Reach Standard Conformance¶
- Implementing Conformance — full profile implementation
Step 4: Production Hardening¶
- Error Handling — intervention and exception handling
- Intervention Execution Mode — active/passive execution semantics, downgrade handling, and HITL implications
- Observability — metrics, trust debt, audit exports
- Security Hardening — transport, signing, access control
- Performance Tuning — latency optimization
- Troubleshooting — common issues and solutions
Optional: Runtime Governance Contracts Extension¶
- Implementing Runtime Governance Contracts — per-action risk/latency negotiation
Choosing your starting point
graph TD
A[Need governance?] -->|Yes| B{What's your goal?}
A -->|No| Z[No ACGP needed]
B -->|Learning/Development| D[Dev Mode Quickstart]
B -->|Production deployment| C{Need performance SLAs?}
C -->|Yes, different latency per risk| E[Standard Quickstart]
C -->|No, uniform latency OK| F{User-facing?}
F -->|Yes| G[Standard Recommended]
F -->|No, batch jobs| H[Dev Mode acceptable]
Claim Routing¶
Use these guides to implement the runtime. For claim wording, badge scope, and non-claimable Safety-Critical material retained in alpha docs, defer to ACGP-6.
Getting Help¶
- Join Discord for real-time support
- Read contribution guidance
- Report Issues