THE INVERSION REGISTRY

PROJECTS GRADUATE
BY EVIDENCE.

Not a portfolio of logos. A public maturity ledger. Each project answers what we were told, what failed underneath it, what was inverted, and where the proof currently stops.

EXPERIMENT → TOOL → VERIFIED → RELEASE CANDIDATE → TRUE 1.0

Showing all 5 projects.

KEY ZERO · TOOL

Inversion Excursion

The cognitive inversion: make inherited frames visible enough to examine before optimizing inside them.

What were we told?: The frames you inherit are reality itself.
What was wrong?: A cage is hardest to leave when it is mistaken for the shape of the world.
What did we invert?: Before a person can use a key, they have to see the cage.
Where is the proof?: The public interactive book itself.

RELEASE CANDIDATE · SECURITY GATE BLOCKED

CAPT

The sovereignty inversion: keep authority, evidence, continuity, recovery, and provider choice around a replaceable model.

What were we told?: Useful AI lives inside a vendor session.
What was wrong?: The provider becomes the hidden owner of state, execution boundaries, and failure history.
What did we invert?: The model became replaceable; the human control boundary became durable.
Where is the proof?: 30/90-day evidence, exact-head tests, governance, and blocked release controls.

VERIFIED

Human Metadata

The human-data agency inversion: identity metadata whose methods, evidence, confidence, contradiction, and limitations remain inspectable.

What were we told?: Human metadata is disposable exhaust or somebody else’s profile.
What was wrong?: Interpretation loses agency when it is detached from provenance and the human it describes.
What did we invert?: Turn metadata into a provenance-aware graph and evidence-linked narrative.
Where is the proof?: Human Metadata Atlas, deterministic contracts, and canonical test runner.

TOOL

Flock You

The surveillance inversion: a provocation turned into an on-device counter-surveillance tool that helps the person being watched watch back.

What were we told?: Surveillance infrastructure is something ordinary people are observed by.
What was wrong?: The asymmetry itself becomes power when detection and evidence are inaccessible.
What did we invert?: Put local detection, mapping, and evidence preservation in the user’s hand.
Where is the proof?: Android source plus active field dogfooding. TOOL does not mean every heuristic is independently verified.

RELEASE CANDIDATE

SynSync

The neuroacoustic inversion: programmable signal paths, safety metadata, and inspectable public modules instead of a black-box wellness skin.

What were we told?: Neuroacoustic experiences are playlists or static meditation content.
What was wrong?: The signal chain, safety metadata, provenance, and public/private boundary disappear behind content.
What did we invert?: Expose the engine and proof surface while preserving the deeper protocol moat.
Where is the proof?: Five public modules, FrankenCAPT bridge, local verification, and an explicit pre-release signing sequence.