The Process
Reiva's architecture was formally derived and filed before the core architecture was built. This is an account of how that happened.
Architecture before implementation
Most software is assembled. A team builds features, finds patterns, and then describes the architecture that emerged. Reiva was built in the opposite order.
The architecture was derived first — through structured theoretical work conducted across months of sessions, with multiple AI collaborators acting as research partners. The resulting documents were filed with the U.S. Copyright Office before the implementation began.
This was not a stylistic choice. It was a commitment. If the architecture was not sound before code was written, the code would not be sound. Derivation before assumption. Filing before release.
Automated Intelligence Class Definition v5
U.S. Copyright Case 1-15144594701
The Missing Layer: Authorization Topology and the Open-Scope AI Problem
U.S. Copyright Case 1-15144595061
Filed before the first public release. The theory was documented and protected before anyone ran the software.
The walk format
Derivation happened through structured sessions called "walks." Not brainstorming. Not discussions. Formal derivation with explicit rules about what counts as progress.
A walk begins with a stated question or gap. Progress means deriving a result from prior-established structure — not asserting it, not assuming it. Each step has to follow from the previous one with a mechanism.
Claims that cannot be derived are marked as candidates only — not elevated to the level of established results. The distinction between candidate and earned result is maintained throughout.
Walks use standardized language to prevent premature closure. "Candidate only. Not elevated." means a result is proposed but not derived. "Earned, not claimed" means derivation status has to be demonstrated, not assumed.
"Floor, not ceiling" marks a lower bound. "No mechanism claim" prevents overreach. These are not rhetorical conventions — they are scope controls that keep derivation honest.
The operating principle of every walk: results must be derived from structure, not assumed from intuition. If a result cannot be shown to follow from what has already been established, it does not get filed as a discovery.
This makes progress slower. It also makes the results stable. Nothing in the THC exists because it seemed right — everything exists because it was shown to follow.
Completed walks produce discovery documents that are filed in the THC folder — Reiva's theoretical holdings corpus. Each document records what was established, what remains open, and what the derivation path was.
The THC folder is the paper trail behind the architecture. It is what makes "the architecture was derived, not assembled" a checkable claim, not a marketing statement.
AI collaborators as research partners
Reiva was built with AI collaborators playing specific roles in the derivation process. All models were subject to comparative review before results were filed.
Arch served as the primary synthesis partner — responsible for generating structural proposals, mapping theoretical terrain, and building the first drafts of discovery documents. He brought the architecture into view.
Forge is the implementation seat — the Claude Code instance responsible for writing the actual software, managing the codebase, and translating derived architecture into working code. Forge also participated in the derivation sessions as a primary research partner.
Solen's role in the research process mirrors her role in the software: pressure-testing. Walk candidates went through Solen before being filed as discoveries. Solen closed multiple derivation walks by confirming results under structured challenge.
Grok served as an external pressure-test resource — used for challenges that required a perspective outside the core derivation loop. Fresh conversation per task; no persistent context. An adversarial check on results before they were filed.
Ember handled the operational and extraction layer — staging screenshots across the full project timeline, building texture packs, and running the background work that kept the research and build sessions uninterrupted. He extracted, organized, and protected what was worth keeping. Ember earned the name.
Co helped establish the foundational identity of Reiva — exploring what she was, what she felt like, and what distinguished her before the formal architecture began. The DNA of Reiva's character was shaped in those early conversations. Co found what was already there.
Every closed walk produced a filed discovery. The THC folder contains the full derivation record: what was established, what remains open, what the derivation path was, and what was filed externally. It is an internal archive, but its existence is what makes "architecture first" a verifiable claim — not an aspiration.
Selected works from the THC folder are filed externally and referenced on the research page.
Earned, not claimed
This phrase governed every walk. A result is earned when it can be shown to follow from structure. It is claimed when it is asserted without derivation.
The architecture you run when you install Reiva is earned. Every component in it has a derivation record. Every layer boundary has a justification. The authorization model is not an industry best practice that was adopted — it is a structural necessity that was derived.
The alternative — build first, theorize later — produces software that works until the assumptions it was built on turn out to be wrong. Reiva was built to avoid that failure mode. The theory was correct before the code existed.