OC Platform Universe

A bounded AI agent development universe inside CLARIXO.

Agents are built on OC as an autonomous engineering substrate, constrained by CLARIXO’s embedded LLM-side and User-side protection boundaries, and validated by humans against real-world artifacts.

Enter Workspace Open Mainlines Open Exports Open Patches Open Verifications Open Artifacts
This universe is embedded inside CLARIXO but physically isolated in route, page, and page-family space. It is not a general product landing page. It is the universe entry for bounded agent development and family routing.
How this universe works

Build on OC. Protect with CLARIXO. Validate with humans.

The platform fixes the development mode itself. OC runs the autonomous engineering loop, CLARIXO provides the dual-sided protection boundary, and humans remain at the level of real-world validation and final correction.

Layer 1

OC autonomous engineering substrate

Boundary initialization, export-first discipline, exact binding, self-verification, and mainline continuation live here.

Layer 2

CLARIXO dual-sided protection

LLM-side protection constrains execution before consequence. User-side protection preserves evidence after behavior enters the real world.

Layer 3

Human reality validation

Humans do not remain inside every intermediate patch step. They inspect real artifacts, correct direction, and make final decisions.

Entry paths

Enter the universe through a clear page family

Home explains the universe. Workspace runs the current mainline. The remaining page family isolates each operating surface into its own route space.

Execution entry

Workspace

Open the main operating surface to see the active task lane, current boundary state, current progression shell, and family routing entry points.

Open Workspace
Mainline view

Mainlines

Use Mainlines to review the current route family for mainline-level state, still-open nodes, and future checkpoint flow.

Open Mainlines
Export view

Exports

Use Exports to enter the export-side progression family, then move into Export Detail for source-of-truth reading and readiness ladders.

Open Exports
Patch view

Patches

Use Patches for the patch-family entry surface, then move into Patch Detail for deeper patch-posture reading without activating a real patch engine.

Open Patches
Verification view

Verifications

Use Verifications to enter the verification family, then move into Verification Detail and Verification Action surfaces for readiness interpretation.

Open Verifications
Artifact view

Artifacts

Use Artifacts to inspect the reality-facing artifact family, including detail, review, and handoff-side surfaces.

Open Artifacts
Platform constitution

These rules define the universe before deeper automation is connected

Boundary first
Every task begins with boundary initialization before any autonomous engineering step is allowed to begin.
Export first
No patch should exist without the latest exact original and a stable binding basis.
Patch hard rules
Patch is not a convenience action here. It is a state-changing constitutional action.
No continuation without closure
The platform should not continue merely because no error is visible. Closure judgment comes before continuation.
Human reality check
No real-world release is treated as complete until a human validates the resulting artifact or behavior.
Current protected flow

The universe already fixes the flow before deeper logic arrives

Boundary Scope, evidence, verification, and human triggers are fixed first.
OC grounding Task intent is grounded into a mainline and still-open node.
Export Exact current state is surfaced before modification.
Patch + verify Bound modifications and closure testing sit inside OC.
LLM-side protection Consequential continuation remains reviewable before execution.
User-side protection Behavior is retained as evidence after it reaches the real world.
Human check Reality validation and final correction remain with humans.
Latest cycle

Batch 1 currently establishes the universe shell

No live bounded cycle is registered yet. This first batch creates the isolated route family, core entry pages, and page shells needed before boundary persistence, export logic, patch logic, and verification loops are connected in later batches.

Go to Workspace View Verification Family