The institution for proof-carrying intelligence.
Not a prettier agent demo. A complete boardroom, workshop, diligence, and operating environment for turning consequential objectives into inspectable proof, governed authority, reusable capability, and measurable second-mission lift.
Open-ended in what work may be attempted. Bounded in what authority the result may earn.
bounded intent
evidence work
Chronicle gate
validated skill
typed roots
earned improvement
From AI output to proof-carrying capability.
A complete, cinematic, interactive masterclass for executives, boards, technical leaders, validators, researchers, capital partners, and public institutions. Learn the GoalOS proof loop, operate a mission, inspect authority gates, simulate governed recursive self-improvement, verify a Merkle commitment, and leave with a partner-ready proof mission.
GoalOS separates generation from authority, evidence from memory, exploration from promotion, and private intelligence from public proof.
A masterclass that adapts to the room.
The content, recommended path, exercises, and facilitator cues adjust to the time available. Completion is stored only in this browser.
Learn the institution, not just the interface.
Each module has a decision question, a mechanism, an exercise, and a concrete output. Use the checkboxes to track progress; the chosen mode filters the recommended path.
The proof-to-capability loop.
Open-ended work may be attempted. Authority is earned only when evidence survives the next gate. A failed gate returns the run to Proof Debt rather than contaminating memory.
Move one objective from uncertainty to justified action.
The flagship deliverable is a Governed Decision State: claims, evidence, verification, risk, action, memory, and rollback.
Every authority transition emits an inspectable artifact.
Mission Contract, Proof Debt, AGI Jobs, ProofBundles, Evidence Docket, attestations, Chronicle decision, skill passport, and root packet.
Compounding is a controlled second-mission experiment.
Mission 1 creates a candidate capability. Mission 2 tests whether it improves fresh held-out work under equal constraints.
Build and run a Partner Proof Mission.
Start empty. Freeze a mission. Turn unsupported claims into proof work. Produce an Evidence Docket, a Chronicle decision, a scoped capability, and a root-verifiable future-mission prior.
Govern recursive self-improvement.
RSI is useful only when exploration and outcome authority remain separated. Simulate the deterministic invention loop, Evidence Contact Index, baseline discipline, Move-37 handling, persistence gates, drift control, and rollback.
Exploration is allowed. Outcome authority is mechanical.
Run the gate to discover whether the candidate earns a probe, repair cycle, rejection, or promotion.
Verify committed proof state.
Build domain-separated leaves, a sorted-pair Merkle tree, an inclusion proof, and a graph epoch root. Then change one character and watch the commitment fail.
Make the business value legible.
GoalOS optimizes the shortest defensible path from uncertainty to action, not report length. Use the value model as a framing device—not as a claim of objective truth.
Cost + Risk + Latency + Proof Debt
Illustrative mission-value index
See what a second-mission test looks like.
The chart below is a synthetic regression fixture useful for engineering and teaching. It is not a public benchmark win, external field result, or proof of general intelligence.
points vs fresh control
Illustrates the pass criterion: a Chronicle-admitted skill should measurably improve fresh held-out work.
points vs raw memory
Tests whether governed, scoped capability outperforms simply feeding prior text back into the system.
Design the partnership around a real proof.
Choose the partner archetype and GoalOS will generate the contribution model, first mission, governance boundary, scorecard, and 30-60-90 path.
Ask the institution, not just the model.
The built-in coach is deterministic and offline. It answers from the GoalOS doctrine and the current lab state. An optional OpenAI-compatible endpoint can be configured in memory for live model assistance; no key is stored.
Can the room distinguish capability from authority?
The quiz is deliberately practical. A partner who passes should be able to spot overclaim, design a proof mission, and explain why RSI requires more than self-generated text.
Complete the questions and score the masterclass.
Partner-ready threshold
80% or better, plus one concrete Proof Mission with a named reviewer and explicit claim boundary.
Engineering-ready threshold
Explain the state machines, hard invariants, typed roots, replay path, challenge flow, and rollback conditions.
RSI-ready threshold
Show baseline advantage, executed evidence, deterministic replay, stress persistence, drift control, and gated promotion.
Watch authority change—not merely content appear.
Move through six scenes. Each scene states the partner question, the system move, the authority actually earned, and the claims that remain blocked.
Convene five institutional minds around one decision.
A local deterministic council reads the live mission state. It produces distinct recommendations from mission, evidence, governance, RSI, and partnership perspectives. A user-configured endpoint remains optional.
Awaiting the first convening.
Freeze a real mission or use the default partner objective, then ask the council to identify the smallest credible proof path.
See how the institution behaves when something goes wrong.
Prestige comes from fail-closed behavior. Simulate evidence failure, validator conflict, scope drift, tampering, delayed outcomes, or unauthorized settlement.
A failure is not erased. It becomes inspectable evidence, a challenge record, and a restriction on future authority.
Explore broadly. Promote narrowly. Preserve every consequential reason.
This advanced laboratory generates a deterministic candidate frontier, applies ECI, baselines, replay, risk, persistence, drift, and Move-37 rules, then packages the selected candidate as an auditable dossier.
Make the ambition impressive by making the evidence boundary impossible to miss.
Inspect maturity, challenge the thesis, and open the supporting corpus. The system distinguishes architecture, local reference evidence, independent validation, live authority, and field outcomes.
What exists—and what remains gated.
Questions a serious partner should ask.
Leave with a board-ready founding charter—not vague enthusiasm.
Define contribution, authority, artifacts, scorecard, kill criteria, privacy, Mission 2, and the 30-60-90 operating cadence. Export the result as Markdown or JSON.
Partner Charter
Complete the inputs and generate a board-ready charter covering mission, roles, authority, artifacts, scorecard, kill criteria, privacy, rollback, and Mission 2.
Bring one consequential objective.
Leave with proof.
Nominate one reviewer. Freeze one bounded mission. Produce one Evidence Docket. Admit only what survives Chronicle. Then test whether the resulting capability improves the next mission.