OrganicOS Documentation
This documentation section is the working knowledge base for OrganicOS.
OrganicOS is being documented from the live system, existing project notes, source trees, service definitions, runtime checks, and cleanup plans. The docs should explain what exists now without exposing private credentials, private endpoints, or unfinished release artifacts.
Read First
Section titled “Read First”- OrganicOS Overview explains the current system model.
- OrganicOS Evolution Map explains how the project grew into the current environment.
- Repository Map tracks the public GitHub profile and local source cleanup.
- GitHub Cleanup Plan defines the publishing and redaction path.
- Public Release Boundary defines what can be published and what must stay private.
- Documentation Inventory lists the subsystems that still need source-backed docs.
Current Documentation Standard
Section titled “Current Documentation Standard”The Portal should be useful to visitors, future contributors, and the project owner without pretending the whole system is already packaged.
Use these rules for every page:
- Prefer source-backed claims over memory or assumptions.
- Mark unfinished or unverified sections as
Needs Review. - Keep private runtime details, credentials, tokens, local-only endpoints, and preserved user state out of public release material.
- Separate current working behavior from future-facing vision.
- Link back to the repository map and cleanup plan when a page depends on source-control state.
Sections
Section titled “Sections”Concepts
Section titled “Concepts”Concept docs explain what OrganicOS is, why it exists, how the layers fit together, and how the vision differs from a normal desktop assistant.
Operations
Section titled “Operations”Operations docs cover setup, cleanup, release preparation, redaction, diagnostics, and the steps needed to keep the live system recoverable.
Reference
Section titled “Reference”Reference docs map repositories, commands, services, subsystems, and documentation gaps. Reference pages should be updated only after inspecting the relevant source or runtime evidence.