The identity gate (2026-10-20/26) gives no prompt without an identity drive, and the public must never get Zuse's. How does a visitor get a console?
The options, and what each costs
A demo identity: an ordinary, non-Zuse identity minted for the demo and attached to every session. The word-level ACL applies, so what visitors may run is chosen in ACL.4th. To check first: whether the v4 path gives a non-Zuse identity a console -- today's gate is written around Zuse.
An EMERGENCY_CONSOLE_ENABLED=1 build: ok> with no drive. Simplest, and the session is a throwaway VM with no network, but that console bypasses the ACL.
Recommendation
The demo identity: the visitor sees StarshipOS as it is meant to run, ACL and all. The prototype (the work items in this milestone) runs either way: the launcher takes an identity drive or not.
Where the ruling will be recorded
docs/fabric/FABRIC-3.md, the demo's section.
What waits on it
The image the demo serves, and the server deployment.
## The question
The identity gate (2026-10-20/26) gives no prompt without an identity drive, and the public must never get Zuse's. How does a visitor get a console?
## The options, and what each costs
1. **A demo identity**: an ordinary, non-Zuse identity minted for the demo and attached to every session. The word-level ACL applies, so what visitors may run is chosen in `ACL.4th`. To check first: whether the v4 path gives a non-Zuse identity a console -- today's gate is written around Zuse.
2. **An `EMERGENCY_CONSOLE_ENABLED=1` build**: `ok>` with no drive. Simplest, and the session is a throwaway VM with no network, but that console bypasses the ACL.
## Recommendation
The demo identity: the visitor sees StarshipOS as it is meant to run, ACL and all. The prototype (the work items in this milestone) runs either way: the launcher takes an identity drive or not.
## Where the ruling will be recorded
`docs/fabric/FABRIC-3.md`, the demo's section.
## What waits on it
The image the demo serves, and the server deployment.
rajames
added this to the Public demo terminal milestone 2026-11-06 19:21:56 +00:00
Ruled (Captain Bob, 2026-11-06): "Mint Zuse for demo console", and "Make the most recent of builds that's green the demo."
A Zuse of the demo's own -- a fresh pair, never anyone's real Zuse -- minted by demo/mint-zuse.sh (logs/20261106-192626: genesis minted; -192739: identity confirmed) and attached to every session with its writes discarded. The demo serves the latest build that passed acceptance: today master (run 153); later the nightly's StarshipOS.iso.
Built in 9e711563 (on StarForth-v4.0.0).
**Ruled** (Captain Bob, 2026-11-06): *"Mint Zuse for demo console"*, and *"Make the most recent of builds that's green the demo."*
A Zuse of the demo's own -- a fresh pair, never anyone's real Zuse -- minted by `demo/mint-zuse.sh` (`logs/20261106-192626`: genesis minted; `-192739`: identity confirmed) and attached to every session with its writes discarded. The demo serves the latest build that passed acceptance: today `master` (run 153); later the nightly's `StarshipOS.iso`.
Built in `9e711563` (on `StarForth-v4.0.0`).
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The question
The identity gate (2026-10-20/26) gives no prompt without an identity drive, and the public must never get Zuse's. How does a visitor get a console?
The options, and what each costs
ACL.4th. To check first: whether the v4 path gives a non-Zuse identity a console -- today's gate is written around Zuse.EMERGENCY_CONSOLE_ENABLED=1build:ok>with no drive. Simplest, and the session is a throwaway VM with no network, but that console bypasses the ACL.Recommendation
The demo identity: the visitor sees StarshipOS as it is meant to run, ACL and all. The prototype (the work items in this milestone) runs either way: the launcher takes an identity drive or not.
Where the ruling will be recorded
docs/fabric/FABRIC-3.md, the demo's section.What waits on it
The image the demo serves, and the server deployment.
Ruled (Captain Bob, 2026-11-06): "Mint Zuse for demo console", and "Make the most recent of builds that's green the demo."
A Zuse of the demo's own -- a fresh pair, never anyone's real Zuse -- minted by
demo/mint-zuse.sh(logs/20261106-192626: genesis minted;-192739: identity confirmed) and attached to every session with its writes discarded. The demo serves the latest build that passed acceptance: todaymaster(run 153); later the nightly'sStarshipOS.iso.Built in
9e711563(onStarForth-v4.0.0).