Public Boundary Review Skill
Public pages should explain the useful thing without exposing the private scaffolding that helped produce it.
The public boundary review is the skill that separates those two layers. It keeps RomeoRaven pages readable, useful, and safe to publish.
When To Use It
Use this review before any page moves from draft, preview, or working material into public launch surfacing.
It is especially important when a page came from:
- project notes
- service or site work
- multi-system coordination
- private task records
- generated drafts
- screenshots, route checks, or operational proof
- any content that names tools, hosts, paths, people, or internal labels
Review Checks
- Reader purpose: Can a visitor understand why the page exists without knowing the private project history?
- Private details: Remove credentials, private hosts, machine labels, private paths, internal issue numbers, and internal-only tool references.
- Useful translation: Replace private scaffolding with the public pattern: what changed, why it mattered, and what method is reusable.
- Route exposure: Check whether the page appears in navigation, homepage sections, Explore, latest sections, search, tags, related cards, or the sitemap.
- Link safety: Make sure every public link lands on a public route. Draft, admin, preview-only, and local-only pages should not be required for a public reader.
- Rendered review: Check the actual page after build. A page can pass Markdown review and still fail because a card, title, tag, or footer link exposes the wrong thing.
What To Remove Or Translate
| Private working detail | Public-safe replacement |
|---|---|
| Machine names or private hostnames | “workstation”, “server”, “preview host”, or no mention at all |
| Local file paths | The public route, artifact name, or a short description |
| Internal task IDs | The public outcome or decision |
| Raw operational commands | The user-facing result, unless the command is itself the lesson |
| Chat-only context | A short explanation that stands on its own |
Done Standard
A page passes when it answers three questions cleanly:
- What is the public point?
- What private context has been removed or translated?
- Where should the reader go next?
If those answers are not clear, the page needs another shaping pass before it belongs in launch surfacing.