Start With Documentation
Use the docs home and overview to understand the current system shape before changing services or source trees.
OpenSupport
Support starts with source-backed documentation, careful diagnostics, and preserving working paths before changing the live OrganicOS system.
OrganicOS is still being consolidated, so support content should be written from observed files, service definitions, commands, build results, and runtime checks. Anything not confirmed stays marked as Needs Review.
Open the documentation inventoryUse the docs home and overview to understand the current system shape before changing services or source trees.
OpenUse the command reference as the reviewed place for launch, build, diagnostic, and recovery commands as they are verified.
OpenUse the documentation inventory to see which subsystem already has evidence and which areas still need source-backed docs.
OpenDo not publish tokens, local credentials, private service URLs, tailnet-only paths, browser state, or WSL user-state artifacts.
Open