Runnable Foundation

The first open wedge is governed authority before execution.

ARE Foundation turns the discipline into a small runnable path: register an actor, issue scoped authority, evaluate scope and policy, then return public-safe proof basics.

Open foundation repo Read public boundary

S0 / S1

The foundation proves the base primitive.

The public implementation starts deliberately small. Identity, scoped authority, policy checks, and proof-before-execution are the reusable base before higher-stage governance appears.

01 / Register

Register an actor.

Give the agent or service a known identity inside the foundation boundary.

02 / Scope

Issue scoped authority.

Bind the actor to explicit action and resource limits before it can request work.

03 / Check

Evaluate scope and policy.

Test the proposed action through the authority path instead of trusting capability.

04 / Proof

Return public-safe proof.

Keep the result inspectable with executed=false and no protected payloads.

Developer Path

A small stack should be easy to run and hard to overclaim.

Foundation is for local evaluation and integration experiments. It is designed to answer the first authority questions without exposing the commercial operator system.

Public developer loop

make up
make smoke
make pressure
make gate

The smoke path keeps customer action execution out of scope and returns proof basics with executed=false.

Boundary

Open foundation does not mean the whole platform is open.

The split is intentional. The discipline stays citable. The foundation stays runnable. The commercial platform carries the richer operator experience and higher-stage governance.

It does not execute customer actions by default.

It does not include Command Center, visual RAG, BYOPolicy UX, or Live Pulse.

It does not bundle governance-strata internals or S2-S6 adaptive stages.

It is a local developer and evaluation foundation, not a production certification.

Discipline