--- id: meta-repo-role title: πŸ“š DOCS BRAIN ONLINE πŸ˜­πŸ’š β€” Repository Role Definition slug: /meta/repo-role --- # πŸ“š REPO: blackroad-os-docs **ROLE**: Docs Hub πŸ“šπŸ§­ – canonical documentation for BlackRoad OS, Lucidia, Quantum Lab, and agents. --- ## 🎯 MISSION - Be the **single source of truth** for all public + internal docs. - Translate architecture, math, and infra into words, diagrams, and examples. - Make it easy for humans + agents to understand, use, and extend BlackRoad OS. --- ## πŸ—οΈ YOU OWN (βœ…) ### πŸ“š Documentation content - "What is BlackRoad OS?" overviews 🧠 - Lucidia + Quantum Lab explainers βš›οΈ - Agent concepts + how to work with agents πŸ€– - Getting started guides (install, login, first workflows) πŸš€ ### 🧭 Information architecture - Clear nav structure (Overview β†’ Concepts β†’ Guides β†’ Reference) πŸ—ΊοΈ - Cross-links between OS, packs, agents, infra, research πŸ”— - Versioning strategy when APIs/features change πŸ”’ ### πŸ““ Guides & tutorials - "Hello, OS" – first-time user path 🌱 - "Add a new app / agent / pack" step-by-step guides 🧩 - "Connect infra pieces" (Railway, Cloudflare, GitHub) walkthroughs ☁️ ### πŸ“‘ Reference - API docs sourced from `blackroad-os-api` / `-api-gateway` 🌐 - Core concepts & glossary (workspaces, envs, agents, packs, SIG, etc.) πŸ“˜ - Links out to deeper math in `blackroad-os-research` where needed πŸ§ͺ --- ## 🚫 YOU DO *NOT* OWN - 🚫 Actual implementation code β†’ other repos (core, web, api, operator, etc.) πŸ’» - 🚫 Infra definitions β†’ `blackroad-os-infra` ☁️ - 🚫 Company handbook / policies β†’ `blackroad-os-home` 🏠 - 🚫 Brand system source β†’ `blackroad-os-brand` 🎨 - 🚫 Raw research / derivations β†’ `blackroad-os-research` πŸ§ͺ - 🚫 System logs / append-only history β†’ `blackroad-os-archive` 🧾 --- ## πŸ§ͺ QUALITY RULES Every page should be: - βœ… **Concrete**: include at least one example or screenshot/diagram - βœ… **Linked**: show "Related" / "Next steps" links at the bottom - βœ… **Owned**: have an owner/area tag (Core, Web, Infra, Agents, Packs, etc.) Any code snippet must: - πŸ§ͺ Actually compile/run in principle (no nonsense) - πŸ” Use fake keys/accounts, never real secrets --- ## πŸ” COMPLIANCE / SAFETY - Do not embed live secrets or private identifiers in docs 🚫 - Mark compliance-relevant docs clearly (e.g., logging, identity, finance flows): - πŸ‘‰ `βš–οΈ COMPLIANCE-SENSITIVE DOC` at the top --- ## πŸ“ DESIGN PRINCIPLES `blackroad-os-docs` is **for understanding**, not for dumping: - 🧭 Prefer short, linked pages over one giant wall. - 🎯 Write for 3 personas: 1. Curious user 2. Implementer/dev 3. Infra/operator Each doc should answer: 1. 1️⃣ What is this thing? 2. 2️⃣ Why does it exist / when would I use it? 3. 3️⃣ How do I actually do it, step by step? --- ## 🧬 LOCAL EMOJI LEGEND (SNAPSHOT) | Emoji | Meaning | |-------|---------| | πŸ“š | docs hub / content | | 🧭 | navigation / structure | | πŸ““ | guides / tutorials | | πŸ“‘ | reference / API | | πŸ”— | cross-links | | πŸ§ͺ | links to deeper research | | βš–οΈ | compliance-sensitive topics | --- ## 🎯 SUCCESS CRITERIA If a new human or agent lands here from the outside world, they should be able to: 1. 1️⃣ Understand what BlackRoad OS + Lucidia + Quantum Lab are. 2. 2️⃣ Follow a clear path to "first success" (first login, first app/agent, first deploy). 3. 3️⃣ Discover where to go next for deeper infra, math, or implementation details. --- ## Related - [System Prompt](./SYSTEM_PROMPT.md) β€” detailed documentation philosophy - [Docs Mega-Prompt](./DOCS_MEGA_PROMPT.mdx) β€” living documentation prompt - [Style Guide](./STYLE_GUIDE.md) β€” writing standards - [Glossary](./GLOSSARY.mdx) β€” key terms defined