Understand your workspace

Start with the project

Your active project is usually the most useful place to work. It contains the current objective, durable decisions and handoff. Load the relevant project rather than asking an agent to read the whole vault.

Community standard layout

The standard Community profile includes the following structure. Lean, custom and minimal profiles can omit domains.

KOS-Learning/
  AGENTS.md
  CONTEXT-POLICY.md
  me.md
  memory.md
  handoff.md
  CODEX.md / CLAUDE.md / GEMINI.md  (selected adapters)
  00 - System/
  01 - Business/
  02 - Projects/Active/
  03 - Personal/
  04 - Hobbies/
  05 - Knowledge/
  06 - Inbox/
  07 - Daily/
  08 - Templates/
  09 - Attachments/
  99 - Archive/

Community’s working profile is me.md at the vault root. Do not copy a path from somebody else’s customized workspace.

Pro and custom roles

Pro can use supported custom role locations. Ask the role resolver instead of assuming a numbered folder:

pwsh -NoProfile -File "$Vault/scripts/Get-KOSRolePaths.ps1" -Root $Vault -Role projects

Set $Vault to your installed Pro vault. Use the returned location for project commands.

Keep authority clear

Root instructions tell an agent how to find context. Project memory stores approved durable facts. The handoff stores current execution state. Templates help create consistent records but are not completed project context. Installation records belong to their installer; do not hand-edit them to suppress errors.

Organize incrementally

Capture new information in the appropriate inbox or project. Promote useful facts after review. Keep one authoritative record for a decision and link to it from other notes. Large moves and folder renames should be planned with link and role checks.