Skip to content

Side B · Reference Pressings

Codebase Archive

Not a storefront. These are retained engineering references: enough architecture, artifacts, and limitations to show how Toledo approaches a class of problem. No inventory counters, transfer promises, or checkout links.

Scope a comparable system See the wider proof ledger →
  1. 01 Security Education · reference build TallySec Teach security in the language of finance Read capability note →
  2. 02 Compliance Automation · reference build ComplyCrawl Compliance-first web automation toolkit Read capability note →
  3. 03 AI Infrastructure · reference build AegisTwin Event-driven agent runtime with governance and replay Read capability note →
ARCHIVE NOTE / 001 NOT FOR SALE

How to read this shelf

Proof is narrower than a promise.

  1. 01

    Inspect the artifact. Demos, public source, sample output, and repeatable tests count.

  2. 02

    Read the boundary. A reference build is not a production guarantee, certification, or client outcome.

  3. 03

    Scope the new system. Comparable work receives its own discovery, threat model, ownership terms, and acceptance tests.