Main operating surface for the isolated OC Platform universe.
Workspace is the current working context for this page family. It does not explain the whole universe again. It keeps the active mainline, current boundary state, current progression lane, blockers, and review and handoff surfaces in one place while routing deeper reading into the dedicated family entry and detail pages. For new projects, the default mainline is OC Native New Project Bootstrap. For existing projects, use Existing Project Compatibility Path as the non-default compatibility route.
No active mainline is currently stored.
The workspace remains in shell state until a boundary session is initialized.
The default still-open node remains the current workspace baseline.
Closure remains open until a progress state is explicitly set.
Start a new project on OC
Start a new OC-native project from zero. This is the default mainline for developers who do not already have a project and want to move from Bootstrap Intake to Bootstrap Scaffold, then to the first Native API Deliverable, then into First Build Assembly, and then into the minimum execution package read surface at First Implementation Package inside one OC-native route family.
Read the current OC Platform surfaces
Use this block to read the current OC Platform universe after the default new-project mainline above. Start from the family that matches the state, surface, or question you need to inspect instead of trying to read the whole universe at once.
Current boundary panel
This upper panel is a compact workspace boundary summary. Boundary Detail, Export Detail, and Verification Detail explain source-of-truth, core anchors, supporting fields, and readiness interpretation in more exact terms.
Risk and blocker surface
No live boundary persistence yet
Boundary state is still absent until boundary initialization is explicitly triggered.
Verification state surface is still shell-level
Verification and continuation surfaces still remain at the first state-surface layer and have not advanced into live execution behavior.
Patch surface remains shell-level
Patch surface remains intentionally observe-only until the route family and page family are stable.
Artifact family review surfaces are now present
Artifact family now includes separate read surfaces for detail, review, and handoff, but no live review decision or commit-boundary handoff action is active in this batch.
Current execution progress lane
Workspace shows the current isolated lane wording. The detail truth pages below explain whether each lane is reading a live session value or still relying on fallback shell wording.
This lane is a current truth snapshot only. It reflects the present isolated session reading moment and should not be interpreted as durable cross-session truth.
Workspace keeps only a compact issuance-readiness overview here. Boundary Detail, Export Detail, and Verification Detail remain the single-source pages for the deeper ladder interpretation.
Current action console
These actions set or clear current OC Platform workspace state for bounded platform operation and review. They do not touch existing CLARIXO runtime, evidence, or audit chains.
Current closure summary
Export basis source: missing · mode: basis source still missing
Verification anchor source: missing · mode: anchor-empty preparation
Use Boundary Detail, Export Detail, and Verification Detail for readiness interpretation and blocking-condition explanation.
Current artifact read surface
The current artifact surface remains the present OC Platform route family, workspace state, and related page-family surfaces that stay separate from existing CLARIXO execution paths.