STRATT Integration

Grace enforces the STRATT Protocol, five specification layers governing prompt units for autonomous AI agent systems. This page shows how Grace integrates with the STRATT toolchain.

For the full protocol specification, see the STRATT Protocol Specification.

For the argument this layer stack exists to serve, and why the four guarantees it delivers are treated as a category rather than a toolchain, see Why Verifiable Agentic Prompt Architecture is its own category.

---

The Layer Stack

L6    MERIDIAN              <- Astro documentation site (public-facing)
L5    @stratt/cli           <- 24 commands, all orchestration
L4    @stratt/ir            <- Execution IR, portable compilation (n8n, TypeScript, LangChain)
L3.5  @stratt/n8n-exporter  <- Chain -> n8n workflow compiler (FORGE pattern)
L3    @stratt/graph         <- DAG, blast radius, CI pipeline (FM-01 through FM-08)
L2    @stratt/crdt          <- Yjs-based CRDT, 7 merge strategies
L1    @stratt/schema        <- Zod validators, URI parsing, SPUH binary encoding
L0    @stratt/fingerprint   <- Canonical serialization -> Blake3 hash

Dependency rule: Lower layers depend only on lower layers. Layer 5 can depend on Layers 0-4, but Layer 0 has zero dependencies on anything else.

Grace operates at L5+, routing unit operations through the STRATT CLI, validating council decisions against SPEC-04, and tracking ecosystem integration patterns.

Cross-Implementation Map

SPEC	Provides	Depends on	Primary Package
SPEC-01	Contracts	L1 validators	@stratt/schema + @stratt/cli
SPEC-02	Fingerprints	L0 hashing	@stratt/fingerprint + @stratt/schema
SPEC-03	Dependencies	L1 URIs	@stratt/graph
SPEC-04	Gates	L3 DAG	@stratt/graph + @stratt/cli
SPEC-05	Traces	L5 commands	@stratt/cli

Failure Modes

Each SPEC defines one or more failure modes (FM), detectable during CI or runtime:

FM Code	SPEC	Name	Condition
FM-01	SPEC-02	Fingerprint tamper	Blake3 digest mismatch
FM-02	SPEC-03	Broken imports	Unresolvable stratt:// or choco:// reference
FM-03	SPEC-03	DAG cycles	Circular dependency detected
FM-04	SPEC-04	Protected agent missing	Chain lacks required protected agent
FM-05	SPEC-04	Gate removal	Gate step removed without major version bump
FM-06	SPEC-01	Contract breaking change	Required input removed or type changed without major bump
FM-07	SPEC-03	Draft isolation	Stable unit importing a draft unit
FM-08	n/a	R2 infrastructure failure	Registry unavailable
FM-09	SPEC-04	Capability check	Agent assigned to step lacks required capability

What Remains

Gap	SPEC	Target
R2 atomic publish pipeline	SPEC-02	Production registry writes (currently local-only)
HTTP mode for ChocoBridgeResolver	SPEC-03	choco:// resolution via API endpoint
MIPROv2 optimization loop	SPEC-05	Automated prompt refinement via DSPy
Veritas auto-trigger automation	SPEC-05	Event-driven regression detection

See Also

• STRATT Protocol Overview: Five specification layers
• STRATT Protocol Specification: Full normative reference
• Primer, Horizontal Domain Scaling
• Namespace Resolution