Nebula Decision Guide
Documentation debt becomes operational debt.
Missing documentation usually surfaces as slower onboarding, repeated questions, fragile deployments, inconsistent incident response, and knowledge trapped with one person.
Diagnostic questions
- Could a new engineer deploy or roll back without asking the original author?
- Are system boundaries and dependencies documented?
- Do APIs, MCP tools, credentials, and operational ownership have clear references?
- Are incident, hotfix, and recovery steps written and testable?
- Can business operators understand what happens when automation fails?
When a paid engagement makes sense
Use a documentation sprint when the missing knowledge is known but needs to be turned into a coherent package of runbooks, SOPs, architecture docs, specifications, or operating handbooks.
Scope Technical Documentation Sprint — $500Scope policy
← Back to all decision guidesThis guide is educational. A paid engagement begins only after payment and scope verification. It does not imply access to unfinished Nebula software, supplier-dependent products, or regulated services.