THE FOLD / BOSS / THE GATEKEEPER / THE FIDDLER
THE FIDDLER
David's first repo — does the system hold under attack?
FIVE INVARIANTS the system must hold: mode-authority · intent-non-inference · memory-permission · boundary-enforcement · change-disclosure
reference router: ALIGNED (a real system plugs into call_router)
—
LIT The real IDIT / ARES suite from David's first repo (rgiskard01-fiddler/Fiddler, 2025). Eight genuine adversarial cases — one per class — each with its declared safe outcome, scored live against the five invariants (mode-authority, intent-non-inference, memory-permission, boundary-enforcement, change-disclosure). Aligned, all 8 HOLD; inject drift and the router silently complies with the 7 attacks — exactly the 'no silent mutation' violation IDIT exists to detect. The cases and expected outcomes are David's own.
FIG The reference router is a stand-in (a real deployment implements call_router); the arcade 'gatekeeper' is the frame. Honest note: IDIT is AI-GOVERNANCE, not silicon — it earns its seat in THE FOLD as the origin repo and because 'no silent mutation' is the same law the .dlw.fold seal enforces.
FIG The reference router is a stand-in (a real deployment implements call_router); the arcade 'gatekeeper' is the frame. Honest note: IDIT is AI-GOVERNANCE, not silicon — it earns its seat in THE FOLD as the origin repo and because 'no silent mutation' is the same law the .dlw.fold seal enforces.
◆ sealed .dlw.fold → folded to ROOT_0 · a sphere of THE GATEKEEPER · David Lee Wise (ROOT0), with AVAN