Core Directive: Strictly adhere to the absolute visual, structural, and execution invariants of the 0rk ecosystem.

mindmap
  root((📜 SSOT BIBLE))
    🪜 STEPS & STYLE
      No duration est
      Heading format
      Only 3-word max
    🧜 MERMAID & LINKS
      No init theme tags
      Quote edge labels
      Shortest path link
    🧠 MEMORY & VERIFY
      memory_summary first
      Grounded facts check
      End-to-end correctness

1. 🪜 Steps

  • Time Tracking Invariant: NEVER include time duration estimates (hours, weeks). Use phase checklists (Phase 1/3, - [ ] Task).
  • Heading Structure: Formatted strictly as: ## [Number]. [Emoji] [1-3 Words Title] (e.g., ## 1. 🧭 Mission).
  • Fuse Rule: Collapse long headings to 1-3 words and explain in a single-line note beneath.
  • Frontmatter Bounds: Use only created, modified, or published keys. Use aliases for moved paths.

2. 🧜 Navigation

  • Mermaid Init Rule: NEVER use %%{init}%% directives. Delete any found to preserve dark/light theme adaptability.
  • Label Quotes Invariant: Always quote edge labels (-->|"Trigger"|) and node texts containing special characters.
  • Shortest Basename Links: Link markdown files by basename ([omp](https://omp.0rk.de/omp)) and folders by path ([[skills/gurus|Docs]]).
  • Canvas Placement: .canvas files must live as navigation children under parent directory indexes, named simply canvas.
  • No Dummy Links: Real URLs only. Secrets become env variables.

3. 🧠 Verification

  • Verify before trusting: Always read memory_summary.md first, but treat it as heuristics; verify facts in code/run history.
  • Stale Curation: Rewrite memory if it disagrees with verified repository files.
  • Complete Gates: Verification must prove end-to-end functional behavior, compile checks, and check constraints before completion.