01 / PUBLIC
A static website
This website serves information and local static assets. It has no customer-data API, daemon discovery, server pairing, payment integration or native bridge.
SECURITY / DESIGN INTENT
Authority stays
with the human.
The intended architecture separates proposals, trusted approval and execution. These boundaries still require complete product verification.
The intended trust boundaries
02 / LOCAL
A trusted decision
Privileged approval is reserved for trusted native review or a deliberate interactive CLI session on the paired Mac. Browser, AI, MCP and node sessions cannot mint approval.
03 / EXACT
One reviewed plan
The design binds approval to the complete immutable plan, including its target, ordered steps and hash. Changed or expired plans require a new review.
REVIEW IS A BOUNDARY
A request to review
is not approval.
A browser or AI client may eventually ask the local app to open a plan review. That request cannot create an approval grant. The trusted native or interactive CLI path must independently obtain and display the exact plan.
The intended Touch ID action uses biometrics without silently substituting a password. When biometrics are unavailable, the alternative is a deliberate switch to interactive CLI review on the paired Mac.
Connecting to a server, opening a panel or authenticating a session does not itself authorize deployment.
What remains unverified
Real daemon and node operation, SSH transport, license verification, native approval, recovery behavior and release packaging remain incomplete or unverified for product release. Local source checks cannot establish end-to-end security.
The intended architecture does not claim protection from a hostile process with control of the same local user account. No security audit or supported production deployment is claimed here.
Public-site data boundary
This site provides no forms and asks for no SSH addresses, credentials, keys, customer licenses or payment details. Its pages do not connect to a local daemon or customer infrastructure.
Public vulnerability reporting and support channels will be published when reviewed channels are available. Do not place secrets or customer payloads into public material.
Continue to the development overview →