Detailed health, visitor journeys, access-network evidence, and seeded-link tools are owner intelligence. This surface must stay behind console authentication and future Thing/passkey grants.
Boundary
Public story lives at cyos.iopublic
Telemetry lives hereprivate
Console reads require audit laternext
loading
Checking Thing session
Detailed site, Shell, Operator, and projection-store health requires console:read or telemetry:read. Public health remains coarse at /api/health.
Create named Studio and reBe links for selected recipients. These links carry owner-supplied intent and should stay private until the recipient receives them.
Recipient activation modelThis creates an owner-side seed for one intended person. When that link is first opened, the invite id, browser footprint, and supplied context can be associated with the recipient journey in the owner projection. Later, when the recipient creates their own Thing/Realm, that pre-provisioned context should become a granted projection rather than owner-controlled identity.
Every detailed read should become a Chronicle eventaudit
Sub-network graph
The target graph is owner-to-recipient-to-colleague propagation: who arrived, which sites and sections they saw, and what forwarded networks are forming. This stays private because it is operational intelligence.