Privacy boundary

North Star is self-hosted and private by design. The public preview and documentation are separate static surfaces.

Public surfaces include

• the product purpose and proof loop
• fictional interface examples
• current capability descriptions
• plain-language safety principles
• a public build receipt for source and deployment convergence

Public surfaces exclude

• the protected dashboard URL
• credentials, tokens, and access instructions
• private project names or records not already approved for publication
• internal network addresses and infrastructure maps
• live controls, schedules, conversations, and evidence
• secret-bearing logs or screenshots

Why separation matters

The public site can be cached, indexed, and shared. The working command center contains operational context and must remain behind authenticated access. Styling the two surfaces as one story does not make them one security boundary.

Telemetry posture

The public documentation is static. It does not require an account and is designed without third-party analytics. The protected product follows its own private logging and retention controls.

Next: System map