Integrative architecture & delivery — the rare combination
systems · program · design
One abstraction proved by instances; a multi-repo program; AI directed as a coordinated teammate; and the design to present it all.
- Abstract systems design — unified the whole stack under one operation (the reconcile), demonstrated across 15+ organs: the same loop is accountability’s spine, security’s gate, provenance’s witness, and creativity’s novelty-criterion — cross-domain abstraction rarely arrived at, and harder to ship.
- Program management — a multi-repo superproject under spec → plan → build: an ecosystem map and registry across ~100 logical projects, release engineering across many packages, every claim tracked to its receipt.
- AI as a coordinated engineering teammate — architected and built solo by directing multi-agent systems (parallel agents for discovery, review, construction) at a scale and breadth one person could not otherwise reach — architecture, integration, and every verified claim kept first-party. Directing AI at this level is itself a discipline.
- Design & front-end — designed and hand-built the portfolio itself: a zero-dependency design system (semantic HTML / CSS / JS, WebGL, a live in-browser generative engine), proof-carrying and accessible — the presentation is a worked artifact, not a template.
The accountability spine — flagship
public · tested
A composable stack that runs one loop — perceive → gate → act → verify → witness.
- EMET — the witness. Re-derives a file's bytes and answers MATCH / DRIFT / UNVERIFIABLE, never trusted. 19/19 conformance across three independent language implementations (Python · Rust · Node).
- coherence-membrane — the read-gate. Turns a model's state-blindness into witnessed, re-derivable observations across an organ family (visual · raw · region · structured · audio · caption). Zero dependencies; 868 tests; PyPI.
- proof-surface — the write-gate. A default-deny, fail-closed authorization contract: expiring least-privilege grants, work-record receipts, delegation chains rooted in a real human with monotonic scope attenuation. Stdlib-only; 258 tests; PyPI.
- accountable-surface — the loop. A model perceives natively, acts only on an allow, and re-perceives to confirm. MCP server + filesystem/web/command effectors, inert until authorized; 201 tests, including a 39-test adversarial integrity suite (forge a digest, manufacture a grant, escape a bound — each refused).
- accountable-engine — the bilateral critic: the same evidentiary standard turned on the operator, not only the machine.
Release & agent toolkit — shipping discipline
- 6 packages published to PyPI — proof-surface, public-surface-sweeper, repo-proof-index, model-provenance-validator, workspace-repo-map, quanta-color — with a wider ring of release-safety and agent tools public on GitHub (secret-redact-io, release-surface-scanner, provenance-sensorium, proof-surface-report, agent-routing-kit, context-curator-lite, workflow-harness-lite, gpu-trace-validator, and more). → the toolkit page says exactly which is which.
Security & platform — private; by capability
- A C++23 integrity / anti-cheat framework (~3,000 tests across ~59 modules) — detecting tampering, evasion, and manipulation by understanding exactly how they are done.
- An agent-orchestration / capability platform — scoped, expiring, witnessed authority at scale; the production foundation the public accountability organs were extracted from.
- Binary reverse-engineering, instrumentation, and red-team research across the stack — repurposed inward, to make the accountability platform self-accountable by adversarial construction.