Link different.

A multi-layered harness architecture for
Governed Workspace Environments (GWE)

One Hermetic Portable Binary. Terminal TUI. Web GUI. Runs anywhere.
Terminals, tools, and agents in one layered workspace.
Work together across machines with P2P and SSH.
Give agents clear permissions and review what comes back.
Durable work. Recover without blind retries.
Extend your workspace with .pi apps.

Local-first. Cloud-optional. No vendor lock-in.

Your machine LOCAL WORKSPACE

Terminal TUI

Picache + installed agent harnesses.

Web GUI

Your own browser desktop.Sakura Streaming Protocol

PermissionsYou decide what runs.

ConfinementCode has boundaries.

LedgerWork leaves a record.

Durable by design.

Intent saved before effects.
Uncertain work waits for review.

Record retained

P2P · SSHPaired identities
Scoped access

Your other machines.
Other peer machines.

Anywhere in the world.

Direct connections.
Durable offers and replies.

Traverse the networkEXPERIMENTAL

Cellar Door · terminal worldsCherrytop · infinite canvases

01 / 05Use your tools. Keep control of what runs.

cherry πworkspace harnessrecords · ceilings · grants · checks

SPEC

Schematic + order

Make a shared task board.

Skeleton + guide▣ Private scenarios

Your specification.
Your capability ceiling.

BUILD

Product layer

Confined builderACP

one vendor agent

edit → public check ↺

Edits its goal copy.
Cannot see hidden scenarios.

egress proxy → vendor

CHECK

Hidden finish line

▣ Harness-only scenarios

One candidate ↓ isolated checks

staticcallasksrowspageprogram

Separate copies. Scoped capabilities.

Pass tied to exact inputscandidate × schematic × scenarios

↶ Outcomes return to the builder

TRY

Try it

independent branch

Own data · no install · no agent token. Close to clear data and grants.

ChairRead-only review.
You make the decision.

Your gate

Current pass requiredmissing / failed / stale → blocked

Merge the checked work.

PACK

Pack for review

Run the finish line again

App + _evidence, signed together.

Review shelf → install separately

Run record + ledgerCeiling, verdicts and receipts.Outside the builder’s box

01 / 06Add a starter. Run your order into a product layer.

Technical details & what’s next

Stores and authority

Starters → editable schematic: /zip/schematics/ → <layer>/.cherrypi/schematics/<name>/. Loaded as data; function and require are refused. Run refuses before making anything if the builder has no ACP entry, git is missing, the folder exists, or delegated acceptance is requested.
Product layer: A git repo seeded from the skeleton. The builder gets a goal copy, the ceiling and guide, never a scenario.
Run + verdicts: <state>/factory/runs/<id>.json and the ledger. The harness reads the ceiling from here. The newest 20 verdicts bind candidate source, schematic and scenario-set digests.
Try + shelf: factory/tries/<product>/ holds a candidate with its own tables. factory/shelf/ holds signed .pi files; their evidence is inside the signed scope: order, schematic and digests, every result, goals, and whether the builder ran confined.

Boundaries that matter

Each check’s temporary candidate: subject holds only the contribution’s capability, bounded by the run’s ceiling. Own-table asks run on the copy; other asks are stubbed or refused. Grants end when checking ends.

Scenarios check static validity and capability ceilings; verb/tool answers; permitted or forbidden host asks; table rows; HTTP page responses; and pane programs driven by keys, ticks and resizes.

The public check loads the app in-process with temporary tables and touches no state root. Hidden program scenarios drive keys, ticks and resizes and check that the frame fits.

Try panes are local and carry no picache token. Closing a Try ends its grants and deletes its data. Startup clears leftover check folders and candidate grants that do not belong to an open Try.

A builder launched without confinement could read operator files. The evidence records whether it ran confined. Injected keys are built, but not on by default.

Planned · not built

Examiner · writes order-specific scenarios in a separate boxWatchdog · code checks first, model judgement second

Also planned: issue intake, several builders on one order, repository import, packed schematics, delegated acceptance and acting ahead.

Observe mode and related issue-routing ideas remain proposals for the operator.

Built mechanisms; only a stand-in builder has exercised the flow. A real vendor builder’s end-to-end run is still pending.