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
.piapps.
Local-first. Cloud-optional. No vendor lock-in.
Picache + installed agent harnesses.
Your own browser desktop.Sakura Streaming Protocol
Intent saved before effects.
Uncertain work waits for review.
Scoped access
Other peer machines.
Anywhere in the world.
Durable offers and replies.
01 / 05Use your tools. Keep control of what runs.
Schematic + order
Your specification.
Your capability ceiling.
Product layer
one vendor agentEdits its goal copy.
Cannot see hidden scenarios.
Hidden finish line
Separate copies. Scoped capabilities.
Try it
independent branchYou make the decision.
Your gate
Merge the checked work.
Pack for review
App + _evidence, signed together.
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>.jsonand 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 secondAlso 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.
Get early access.
Test buildsHelp shape cherry π. Sign up to download and test upcoming builds.
Check your inbox.
Follow the link in your cherry π email to confirm your signup.
Requested one already? Use that email. We limit confirmation emails to one every 15 minutes. Check spam if it’s missing.
Unsubscribe at any time. Email privacy