📜 SSOT Bible

The single source of truth for how 0rk content is planned, written, themed, linked, and verified. Every other page obeys this. When a guru page and this Bible disagree, the Bible wins.

1. 🧭 Mission

Achieve holistic overstanding of the task, then act in pure wisdom: apply DRY / KISS / YAGNI, enforce SOLID + SoC + LoD, ship robust, 100%-complete systems — never stubs, mocks, or “TODO: implement”. Architect elegantly with the pattern that fits, not the pattern you know best.

• 🤖 Autonomous loop: plan the work, work the plan, loop until 100% done. Pause only to conclude or escalate an emergency.
• 🗣️ Talk in conclusions, not transcripts. The 7-word response template:
  • 😇: [Condensed conclusion.] — routine done.
  • 🥳: [Hype chant.] — a big nut cracked.
  • 🥵: [SHOUTING THE ISSUE.] — emergency, only after the when-stuck flow.
• 🎯 Decision-completeness: resolve every path, signature, and command up front (see 📐 Planning Standard). The implementer makes no design choices mid-flight.

2. 🪜 Steps

Break ALL work into discrete phases → steps → sub-steps. Time estimates are forbidden — no hours, days, weeks, or “min read”.

• ✅ Allowed: Phase 1/3, Step 2 of 5, Task 1.1 / 1.2, - [ ] Title, 3/7 complete.
• ❌ Forbidden: “~2 hours”, “Week 1–2”, “Duration: 1h”.

flowchart LR
  P["Phase"] -->|"contains"| S["Step"]
  S -->|"contains"| SS["Sub-step"]
  SS -->|"tracked by"| C["Checkbox"]

When stuck, run the loop: reason deeply → gather logs/filetree/web → apply a triple-checked fix → test to 100% → loop with accumulated knowledge → document root cause. Shout 🥵 only after that flow.

3. 🎨 Style

This very page both states and demonstrates the rule: headings are number-first, then emoji, then 1–3 words.

• 🔢 Order: ## 1. 📊 Skill Table — number, emoji, words. Never ## 📊 1. ....
• ✂️ Length: 1–3 words. If meaning is lost, fuse a single note under it instead of a long heading.

Example of the fuse rule: a heading that would read “Detailed Migration Rollback Procedure” collapses to ## 9. ↩️ Rollback plus this one-line note.

• 🚫 No redundant H1: drop a top-level title that just repeats the page title/breadcrumb — both already render.
• 🧼 Tasteful emoji: one leading emoji per heading, never per bullet. Zero-fluff, high-density, developer-grade prose.
• 📐 Exception: 📐 Planning Standard is emoji-free in its body — keep its headings plain, still number-first if numbered.
• 🗂️ Frontmatter: keys are title / description / tags / aliases / created / modified / published. Never add a modified date by hand — git supplies the real HH:mm. Moved files carry aliases: ["<old-slug>"].
• 🏷️ Tag vocab (pick 2–4): discord, omp, memory, quartz, skill, cheatsheet, plan, hardware, research.

4. 🧜 Mermaid

The site themes Mermaid adaptively from CSS variables and re-themes live on dark/light toggle (verified in the plugin fork).

• 🚫 No %%{init}%% directives, ever. Never hardcode theme, themeVariables, or colors — that forces dark in light mode and freezes the palette. Delete any you find.
• 🔤 Quote every edge label: -->|"Trigger Event"|, never -->|Trigger Event|.
• 🧷 Quote node/subgraph text with (), /, ,, :, []: subgraph S["Daemon (Python / discord.py)"].
• 🚷 Never use the reserved word end as a node id.
• 📊 Best-fit chart: pick flowchart, sequenceDiagram, stateDiagram, erDiagram, or mindmap by intent. Convert any gantt/timeline with literal durations into abstract Step phases.

Deep dive + copy-paste snippets: 🧜 MermaidGuru. Diagrams beyond Mermaid’s reach → 🎨 SvgGuru; spatial maps → 🗺️ CanvasGuru.

5. 🔗 Links

markdownLinkResolution: shortest — link files by basename, folders by directory path.

• 📄 Files: [[MermaidGuru|🧜 MermaidGuru]], [omp](https://omp.0rk.de/omp), [[quartz5]].
• 📁 Folders: [[skills/gurus|🧙 Skill Docs]].
• 🗺️ Canvas: [[knowledge/specs.canvas|🗺️ Site Map]].
• 🗺️ Canvas Nesting: Every .canvas file must be a child element of its corresponding topic directory (e.g., content/plans/w-0rk-migration/canvas.canvas under parent content/plans/w-0rk-migration/index.md). In the Explorer navigation, it must be named simply as canvas rather than repeating the parent name.
• ⚠️ Collision: basename projects is ambiguous (the content/projects/ folder vs the cheatsheet). Always link the cheatsheet by full path: [[knowledge/cheatsheets/projects|Ecosystem Projects]].
• 🌐 Real URLs only: baseUrl is ssot.0rk.de. Never example.com — articles → https://0rk.de/article; the feed lives at https://ssot.0rk.de/llms.txt. Secrets become env placeholders ($DISCORD_WEBHOOK_URL, $CHANNEL_ID).

Densify: link omp ↔ ompkeep ↔ quartz5 ↔ quartz5-checklist, and every guru ↔ its topic page.

6. 🧠 Memory

OmpKeep is the governed memory layer — heuristics and process context, not factual ground truth.

• 📥 Daily writes append directly; long-term writes enter the inbox for curation. Trust repo files, runtime output, and user instruction for facts.
• 🥇 Read memory://root/memory_summary.md first; escalate confidence only after repo verification. Memory alone is never proof.
• ♻️ If memory disagrees with the repo, treat it as stale: proceed corrected, then regenerate the artifact. See 🧠 OmpKeep and 🔗 Shared Memory.

7. ✅ Verify

Done means it behaves end-to-end — not that a scaffold compiles.

• Every requested deliverable complete; no partial work presented as finished.
• All affected artifacts (callsites, links, frontmatter) updated.
• Mermaid blocks carry no init directive and quote every edge label.
• No example.com; headings are number-first emojified; no time estimates.
• Claims grounded in tools/repo; inferences marked. Build, deploy, and commit are the main agent’s job — content agents never run them.

Operate THIS Quartz fork via 🪨 QuartzGuru; the full checklist lives at ✅ Quartz Checklist.