Full-Stack Integration — Five Claims, One Scenario
Every claim has already passed its own isolated test. That leaves a different, more important question: do the separately-built pieces actually cohere as one system when a realistic scenario runs through all of them at once, in the right order, with real data passed between them — not five components that each pass alone but have never actually touched each other's real output.
The scenario
A student ("subject-001") attempts to advance mastery of a prerequisite-gated topic. The action is mediated by RBAC (Claim 7), gated by a Constitutional Behavioral Unit (Claim 6) whose non-activation invariants include a live circuit breaker (Claim 3), which itself only fires if the underlying tensor write-path constraints (Claim 1) and the prerequisite DAG (Claim 2) permit it. Five claims, one real flow of data.
Run directly, first try, no bugs found
[Claim 2] arithmetic confirmed-mastery: NodeState.CONFIRMED_MASTERY [Claim 7] Verified token issued by designated verifier: INSTRUCTOR [Claim 3] Breaker state: BreakerState.MONITORING --- Attempt 1: everything healthy, should succeed --- Result: advanced DAG state: NodeState.CONFIRMED_MASTERY RBAC record: confirmed-mastery Tensor D (via propagation, Claim 1 fix): 0.95 --- Attempt 2: trip the REAL breaker, attempt again with a fresh token --- Breaker is now: BreakerState.SUSPENDED Correctly blocked end-to-end by the real breaker trip: CBU 'commit_geometry_mastery' denied: trigger=True, invariants_triggered=['circuit_breaker'] geometry_basics remains: NodeState.UNCONFIRMED (never advanced)
Why Attempt 2 is the real evidence
Attempt 1 shows the happy path — useful, but not the hard part. Attempt 2 is where cross-claim coherence
actually gets tested: a completely different topic (geometry_basics, not the one that tripped
anything), with its own valid prerequisite and its own freshly-issued, individually-valid token — should
succeed on its own terms. It's still correctly blocked, because the shared circuit breaker — the same object
reference passed into both Constitutional Behavioral Units — is tripped, and that shared state is what the
governance layer actually checks. That's real cross-component wiring, not five modules that each report
green in isolation.