SignalClaw — built & proven vs in design Two horizontal bands on a cream field. The upper band, solid viridian border, holds seven solid capability tiles: store, grade, compound, retrieve, roll up, govern, erase — the domain-agnostic core, built and proven with about 1,600 tests and commit-enforced architecture rules. The lower band, dashed muted border, holds two dashed tiles: the capture surface and domain packs — in design, not built. A legend explains solid means built and proven, dashed means in design. SIGNALCLAW · HONEST STATUS What is built — and what is not yet Foundation built and proven; the capture layer is in design. Drawn that way on purpose. BUILT & PROVEN THE DOMAIN-AGNOSTIC CORE store grade compound retrieve roll up govern erase ~1,600 tests · 9 commit-enforced architecture rules · tenant-isolated · append-only audit · right-to-erasure built in Compounding memory benchmarked well under budget. IN DESIGN · NOT BUILT capture surface where the work gets captured domain packs go-to-market first Connects to nothing today — by design, until the capture layer ships. solid — built & proven dashed — in design, not built PARKED · FINISHABLE · NOT FAILED SignalClaw Status: foundation built · capture layer in design.

What is built — and what is not yet. The solid band is the domain-agnostic core, built and proven: store, grade, compound, retrieve, roll up, govern, erase — about 1,600 tests behind it, nine commit-enforced architecture rules, tenant isolation, and right-to-erasure built in. The dashed band is what is honestly in design and not built: the capture surface and the first domain packs. SignalClaw is parked, not failed — the foundation waits with its proof intact.