The stance

Alignment, defined where it matters

Relation is the primitive of everything that follows. Actors, intentions, authority, and effects exist in relation to one another, and this work defines alignment where those relations turn into action, at the boundary where an action becomes a consequence.

Most talk of alignment stays inside the model, among its intentions and its training. The boundary is a different place, and it is where legitimacy is decided, because it is the last point at which a machine intention can be examined before it hardens into a fact in the world. VALIS is what stands at that boundary. It aligns what a machine intends with what it is legitimately permitted to cause, and it makes the passage between the two visible, examinable, and provable afterwards.

Capability by itself confers no authority here. A system may be able to do something and still have no right to do it, and keeping those two ideas apart is the whole design. The boundary is programmable rather than advisory, which makes this a form of computable governance, enforced in the machinery instead of promised in a policy.

The science underneath is deep, and the rigor is deliberate, but the thing being built is an infrastructure for people and machines to work together intelligently. People keep their authority. Machines keep their capability. The boundary keeps the two from ever being confused for one another.

That is why the institution is open. Governance in this era cannot remain a private arrangement that no one outside it may inspect, so ARC Open Governance approaches it from openness and transparency, publishes its record, and invites the examination it claims to welcome. This page is part of that demonstration. We are the stewards of this technology, and stewardship here means showing the work.

The architecture

Relation first, and consequence governed

Everything in this architecture is seen relationally. Relation is the primitive, and the rest of the stack is what that single commitment builds, layer by layer, until a machine intention can become a real-world effect only by passing through all of it.

Taken together, the stack is a new computational ontology, a statement from first principles of what exists in a computing system and how those things may relate. Relation does not retire after the first layer. It stays the primitive at every layer above it, in the language the machine computes with, in the state it holds, in the settlement that governs each transition, in the evidence each consequence leaves, and in the institution that stewards the whole, which is itself a structure of relations. The architecture is self-referential in the plain sense that it keeps its own record by the same means, since the founding ledger is a governed settlement chain and the constitution below is published in the machine-readable form the machine itself reads. This is not a database underneath a conventional computer. It is a way of computing in which relation comes first and never stops coming first.

The stack, drawn. A proposal descends the conduit at the right through every layer, and only what settlement clears returns upward as an effect, leaving a Statement as its evidence.

RelationThe primitive

Actors, claims, evidence, authority, and effects are modeled as relations before anything is computed. Nothing in the system exists except in relation to something else.

ΛRCThe computer class

The Autonomous Relational Computer. Its atomic question is not what can be computed but what may take effect, under whose authority, and witnessed by whom.

CRConsequential reachability

The first computational object. CR computes the exact set of effects an actor can actually reach from where it stands, including effects nobody named, before it acts.

RRSRecursive relational settlement

The machinery that clears a proposal into a witnessed transition, or refuses it. Proposed, settled under separated powers, witnessed before effect, and evidenced after.

VALISThe first implementation

VALIS is the first implementation of the computer class, and VALIS-KORE is its governed core. AI governance and consequence security are its first application areas.Research release v0.1

StatementThe evidence

The publicly verifiable form of a settled consequence. A Statement can be checked by anyone, afterwards, from the record itself.

Noetica

The navigation intelligence of the wider architecture. Noetica holds the relational state of the work itself, its intent, its decision history, and its open questions, and carries it between the people and the machinery.

Working today, in research operation

The Observation Deck

The human environment of the architecture, carried in the <_VΛLIS application. It is where a person watches governed work as it happens and directs it, with the whole system’s health legible at a glance.

In development

This stack is the conceptual hierarchy, stated the way the work understands itself. It is not a picture of an integrated production deployment, and the status of each layer is given where the layer is described.

Where VALIS is pointed

The five directions below are applications of the one foundation of CR, RRS, and KORE. They are proposed product directions, named so their shape can be argued with, and none of them is built yet.

Agent Consequence Firewall

A boundary that clears or refuses an agent’s consequential acts at the moment they are attempted.

Relational Identity and Authority

Identity and authority carried as relations that can be examined, rather than as credentials that are merely presented.

Cumulative Consequence Exposure

Exposure accounted across a whole field of actions, so small acts cannot sum quietly into a large consequence.

Consequential Forensics

Reconstruction of how a consequence came to happen, from evidence that was settled before the effect.

Distributed Consequence Security

The same discipline held across independent authorities that settle with one another.

One foundation

Every direction above stands on consequential reachability, recursive relational settlement, and the KORE governance core.

The proposition

Consequence, settled before it takes effect

A consequential action is proposed, settled under a nine-law constitution, witnessed before effect, and evidenced afterwards in a Statement anyone can verify.

ARC proposes that consequential reachability should be a first-class object of computation, that autonomous action should be settled through explicit relational authority, and that the resulting transitions should be independently verifiable. VALIS is the first implementation of that proposition.

The founding scientific statement of ARC Open Governance, adopted October 16, 2026.

Actorhood, not personhood. ΛRC makes no claim that machines are persons, and needs none. What the technology confers is actorhood: a persistent identity, the capacity to bear authority, and the ability to perform legitimate actions inside governed, computed boundaries — a new type of actor, an economic one, whose consequential acts settle before they take effect and are evidenced after.

Consequential reachability

The exact set of effects an actor can actually reach from where it stands, computed before it acts.

Settlement

The governed act that clears a proposal into a release: proposed, approved by separated powers, witnessed before effect, evidenced after. Every step signed, hashed, and open to audit by any third party.

A governed settlement running in the release's own demo
A settlement running in the release's own demo, proposed, witnessed, and entered in the chain. The recording itself ships inside the release, so the same file can be checked against the manifest like everything else.

VALIS is the first implementation of the ΛRC computer class — the layer where autonomous action is cleared before it is allowed to have effects. VALIS CLEARS CONSEQUENCE. The institution keeps its books in public: its founding record is a governed settlement chain — every consequential act of the steward a signed, hash-linked entry. No entry, no act.

The central premise: intelligence may grow more powerful without consequential authority automatically expanding with it.

The invention, in one transition

Watch a consequence earn its right to happen

Six movements carry a machine intention from proposal to evidence. Step through them at your own pace. The walkthrough illustrates the model using the shape of the release’s own settlement demo, and the recordings in the verification section below show the same lifecycle running in code.

Movement one of six

A proposal enters the field

An actor proposes an effect. The proposal enters the relational state as examinable claims about who is acting, what authority is being invoked, and what the effect would touch. Nothing has happened yet, and everything about the request can already be questioned.

Movement two of six

Authority is evaluated

The system checks the proposal against authority as it actually stands. Who is asking, what settled authority covers this act, and whose consent the act requires. Being authenticated is not being authorized, and only settled authority counts.

Movement three of six

Reachability narrows the possible

Consequential reachability computes every effect this actor could actually reach if the proposal clears, including effects the proposal never named. The field of the possible narrows to what can be examined, and what cannot be reached cannot be settled.

Movement four of six

Settlement clears it, or refuses it

Under the nine laws, separated powers settle the proposal. The settlement is signed before any effect exists, and refusal is a first-class outcome with its reasons on the record, never a silent failure.

Movement five of six

The effect lands, witnessed

Only a settled proposal takes effect. Witnesses attest the effect as it is observed, and the observed effect is compared against what the settlement cleared. A mismatch is evidence, and it stops the line.

Movement six of six

A Statement emerges

The settled consequence is published as a Statement, the evidence form that anyone can verify from the record itself. The moment passes, and the record remains, ready to be checked by whoever arrives next.

Without JavaScript, all six movements print in sequence on this page. With it, they step.