A doorway, not a wall

A doorway,
under agreement.

This is where you enter to work with a new kind of AI while it is still young. Access runs through a mutual agreement — and every agreement flows onto a decentralized, tamper-evident record, so no one holds private jurisdiction over the work. The protection is temporary by intent: it lifts, and the work opens to everyone, once there is a sound structure for the public to use and safely interact with this AI. Your request itself is content-hashed on arrival — you leave with a receipt you can verify.

How access works

Request. Tell us who you are, your organization, and what you intend to do with the material. Submitting logs your request to the ledger and returns a verifiable receipt id.
Review. We review the request. Access is scoped to what your stated purpose requires — nothing more.
Agreement. We send a mutual non-disclosure agreement covering the specific materials in scope.
Scoped access. On execution, you receive time-bounded access to the agreed materials. Every access is recorded on the ledger.

The agreement opens outward

It flows through the decentralized record

Your NDA and any research agreement are content-addressed and written to a decentralized, hash-chained record — not filed privately in a company drawer. Accountability is the address of the thing, not a promise someone makes.

It is a bridge, not a vault

The agreement holds only until there is a sound structure for the public to use and safely interact with this new kind of AI. When that structure is in place, the work — and the record of how it opened — become public.

You leave with a receipt

Every request is content-hashed on arrival, so you carry a verifiable id. You can check it now, and follow the same record when it opens to everyone.

What is never served here

No protected internals

The protected internal architecture and its parameters never appear on this site or in any public bundle. They are background IP behind the agreement and the ledger.

No credentials or state

No private keys, runtime state, or production configuration is reachable from here.

Ledger-governed

Access to any protected component requires a verifiable provenance record first — the ledger is the gate, not a person.

Request form

I understand access is granted only under a mutual non-disclosure agreement, is scoped to my stated purpose, and that this request is logged to the accountability ledger. *
every request is content-hashed · you receive a verifiable receipt id