Public-safe docs: Examples use placeholders. Live fleet IDs, credentials, telemetry snapshots, harness evidence, and session chronology are maintained in operator-controlled handoff repositories — not on the public web.

About this article

• Audience: Operators reading public documentation
• Goal: Understand what is public vs private
• Type: Reference

Summary

Public Ghost Protocol docs describe product capabilities, architecture, and operator procedures using placeholders. They are not a live fleet status board.

What stays private

Category	Examples
Live fleet state	Device IDs, container instances, soak tables, telemetry samples
Credentials	Passwords, tokens, private keys, tunnel secrets
Harness evidence	Internal TAP logs, private CI artifacts, session chronology
Source control	Private firmware repositories and operator handoff files

Public surfaces

• This catalog (docs.ghostprotocol.us) — full operator documentation
• Marketing hub (ghostprotocol.us/docs) — curated public subset
• Capabilities (ghostprotocol.us/capabilities) — formal product claims

Next steps

• Architecture overview
• Quickstart
• Contact: info@ghostprotocol.us