First Flight Is a Refusal Until Someone Approves

A Phone Is Not Automatically Family

The remote vessel is one universal iOS and iPadOS app. It talks to the same engine children the Mac supervisor would start. It is not a second loop and not a public site. The first time a new device appears, the honest result is a refusal plus a log row that names the mesh identity. Nothing executes. Nothing attaches. The operator later writes an allow-row, or — only when a human is sitting on a serving terminal — answers a one-time prompt. Headless service does not grow the list by itself.

Spectate is the default. Spectate can see record-derived projections. That is real disclosure. Mutate is a separate, revocable bit. A first flight that landed as mutate because 'it is my phone' would be a story, not a gate.

Unknown is refused. A remote coding surface that auto-trusts the next device on the mesh is a mesh-wide root shell.

What This Quest Hides on Purpose

Install, signing, store channels, and device serial work live in swift-quest. Coordinates, service labels, and home-directory paths stay out of this page. The lesson is the admission order, not a travel guide. A first-flight screenshot that includes a host or a port is already the wrong artifact to keep in a public quest.

not on the mesh nothing to connect to on the mesh, unknown refusal frame + identity in the gateway log approved, spectate projections only — disclosure, no control approved, mutate operator-grade control — the risk the bit exists for

A Phone Is Not Automatically Family

What This Quest Hides on Purpose

Code

External links

Exercise

Progress

Comments 0