🔮 OMP Hub

Transform verbose session transcripts, raw codebases, or complex implementation logs into ultra-condensed, high-density, emojified developer cheat sheets.

1. 🎯 Quick Start Dashboard

flowchart LR
    A[<b>INPUT SESSION</b><br/>• Chat logs<br/>• Code bases<br/>• Build logs] --> B[<b>CLEANSING</b><br/>• Strip chat<br/>• No filler<br/>• Facts only]
    B --> C[<b>REFLECTION</b><br/>• Extract API<br/>• Map CLI<br/>• Gotchas]
    C --> D[<b>CONDENSATION</b><br/>• Layout tables<br/>• Emoji anchors<br/>• Compact code]

2. 🧼 Cleansing

• Conversational pleasantries: Strip “Hello”, “Sure”, “Let me help you with”, “As you can see”, and meta-dialogue.
• Context scaffolding: Remove long paragraphs explaining why a tool or library is designed a certain way; keep only the direct application.
• Unused boilerplate: Delete generic setups or verbose explanation blocks.

3. 🧠 Reflection

Extract these core elements and group them by developer intent:

4. ⚡ Condensation

Pack maximum information in minimum space. Prefer structural density over paragraphs.

Gotchas & Caveats

• Warning: Never suppress compiler/linter warnings to bypass test suites.
• Trap: Avoid using global state variables across SSR boundaries in Svelte 5.
• Rule: All path variables in plugins must be absolute.

Side-by-Side Comparatives

5. 🎨 Formatting

Use emojis consistently as visual anchors for rapid scanning:

6. 🔍 Self-Verification Checklist

Before saving, verify the cheat sheet against these rules:

• No paragraph exceeds 2 sentences.
• All commands are copy-pasteable and grouped.
• File paths are exact and absolute where required.
• No fluff words (e.g. “basically”, “essentially”, “just”, “simply”).
• Formatted correctly with appropriate markdown syntax.

7. 🔗 Related

• Skills

Hardcore scrape, recursively research, and obsessively loop to grab all knowledge about any topic, then compress it into 100% loss-less semantic developer guides.

1. 🎯 Quick Start Dashboard

flowchart LR
    A[<b>INPUT SPEC/TOPIC</b><br/>• Tool / Stack<br/>• FOSS Library<br/>• Raw Content] --> B[<b>HARDCORE GRAB</b><br/>• Web search<br/>• Repo read<br/>• Issue/PR]
    B --> C[<b>OBSESSIVE LOOP</b><br/>• Cross-ref<br/>• Verify<br/>• Deepen]
    C --> D[<b>KURBY DIGEST</b><br/>• Strip bloat<br/>• Keep core<br/>• Density 100%]

2. 🔍 Hardcore Grabbing

• Recursive Search: Use web_search and read tools to grab docs, spec sheets, and FOSS repositories.
• Local Discovery: Map workspace dependencies (package.json, Cargo.toml) and environment configs (.env*).
• Diverse Sources: Target developer wikis, RFCs, GitHub issues, and discussion threads.

3. 🌀 Research Loop

• Perpetual Looping: Avoid stopping at the first search page. Retrieve deep pages and cross-reference contradictory sources.
• Fact Verification: Verify command parameters, API changes, and environment limits against live codebase files.
• Traversing Deprecations: Identify legacy paths, active forks, and pending breaking changes in issue lists.

4. ✂️ Kurby Compression

• Bloat Elimination: Delete conversational pleasantries, introductory guides, meta-dialogues, and verbose explanations.
• Semantic Preservation: Condense text while retaining all parameters, configurations, types, and traps.
• Environment Scope: Isolate and keep only what applies directly to the target operating system, tooling, and constraints.

5. 🎨 Formatting

6. 🔍 Self-Verification Checklist

Before finalizing any digested content, verify against these rules:

• No paragraph exceeds 2 sentences.
• 100% of core information is retained in condensed format.
• No fluff words (e.g. “actually”, “basically”, “simply”, “obviously”).
• Visual landmarks are applied consistently.

7. 🔗 Related

• Skills

1. 🎯 Core Principle

The LLM Wiki is a persistent, compounding personal knowledge base compiled once and kept current by an LLM-in-the-loop. Unlike traditional Retrieval-Augmented Generation (RAG) which rediscovers knowledge per query, the LLM Wiki synthesizes information, tracks contradictions, establishes cross-references, and integrates new context directly into structured, interlinked markdown pages.

The human curates sources and directs the domain constraints; the agent summarizes, cross-references, directories, and audits consistency.

2. 🗂️ Layout

A standard LLM Wiki resides at a designated directory (defaulting to ~/wiki) with the following hierarchy:

wiki/
├── SCHEMA.md           # Domain conventions, taxonomy, tag constraints, page thresholds
├── index.md            # Alphabetical content catalog grouped by type with one-line summaries
├── log.md              # Chronological record of all updates, rotated at 500 entries
├── raw/                # Layer 1: Immutable source material
│   ├── articles/       # Web articles, text scrapes
│   ├── papers/         # PDFs, ArXiv documents
│   └── transcripts/    # Meeting transcripts, interviews
├── entities/           # Layer 2: Subject profiles (people, organizations, models)
├── concepts/           # Layer 2: Subject topics (techniques, mathematical formulations)
├── comparisons/        # Layer 2: Side-by-side matrices and evaluations
└── queries/            # Layer 2: Filed syntheses of complex user questions

📥 Layer 1: Raw Sources

Raw source documents are immutable. The agent reads from but never writes to this directory. Each source receives frontmatter mapping its origins:

---
source_url: https://0rk.de/article
ingested: YYYY-MM-DD
sha256: <body-hash>
---

The SHA256 digest is calculated over the raw markdown/text body (excluding the frontmatter) to detect content drift or duplicate ingestion.

📄 Layer 2: Wiki Pages

Wiki pages contain synthesized knowledge written in markdown with standard YAML frontmatter:

---
title: Page Title
created: YYYY-MM-DD
updated: YYYY-MM-DD
type: entity | concept | comparison | query
tags: [tag1, tag2]
sources: [raw/articles/source-file.md]
confidence: high | medium | low
contested: false
contradictions: []
---

📐 Layer 3: Schema

Contains the domain definition, tag taxonomy, and page-creation thresholds. It governs what tags are allowed and what topics warrant page creation.

3. ⚙️ Core Operations

📥 Ingest Pipeline

When ingesting new material:

1. Source Capture: Save the raw document into raw/ under a lowercase, hyphenated slug. Prepend the origin URL and compute its body SHA-256. If a document with the same URL already exists, verify the hash. Skip if identical; flag drift and overwrite if changed.
2. Entity & Concept Extraction: Identify key subjects that meet the Page Thresholds (appearing in 2+ sources or central to one).
3. Index Scan: Search index.md and check the filesystem to locate existing pages for the extracted subjects.
4. Write/Update Pages:
   • For new subjects, create files in their respective directories. Ensure at least two outbound [[wikilinks]] link them to existing pages.
   • For existing subjects, integrate the new facts. Bump the updated date.
   • If claims conflict, follow the Conflict Policy: do not silently overwrite. Detail both perspectives with dates and sources, mark contested: true, add the conflicting page to the contradictions list, and log the conflict.
5. Navigation Update: Append new pages to index.md and document the action inside log.md.

🔎 Query Flow

When resolving user questions:

1. Orientation: Read SCHEMA.md, index.md, and the last 30 lines of log.md.
2. Search: Execute regex search for keywords across the wiki directory.
3. Synthesis: Synthesize a comprehensive answer, citing relevant pages using wikilinks (e.g., [[transformer-architecture]]).
4. Filing: For highly complex or side-by-side syntheses, create a page under queries/ or comparisons/ to save the work.

4. 🧭 Navigation

• index.md: Tracks every page sorted alphabetically within sections corresponding to their type (Entities, Concepts, Comparisons, Queries).
• Scale Rules:
  • Split a section when it exceeds 50 entries.
  • Generate a _meta/topic-map.md grouping pages by theme when total entries exceed 200.

5. 🔍 Lint & Audit

The agent must programmatically audit the vault using a script or command to report on:

1. Orphans: Pages with zero inbound wikilinks.
2. Broken Links: Wikilinks pointing to non-existent target files.
3. Index Gaps: Wiki pages present in the filesystem but missing from index.md.
4. Schema Compliance: Frontmatter validation and tags not declared in SCHEMA.md’s taxonomy.
5. Staleness: Pages updated >90 days ago that reference active subjects.
6. Contradictions: Pages with contested: true or unresolved conflicts.
7. Size Limits: Pages exceeding 200 lines (candidates for splitting).

6. 🔗 Related

• Skills

Complete, zero-fluff reference guide for Quartz 5, a fast, modular, TypeScript/YAML-configured static site generator optimized for publishing digital gardens and Obsidian vaults.

1. 🚀 Quick Start

Essential CLI Commands

• Initialize project: Create a new Quartz workspace in the vault directory:

  npx quartz create

• Local development: Launch a local hot-reloading preview server:

  npx quartz build --serve

• Compile static files: Build optimized production HTML/CSS/JS assets to public/:

  npx quartz build

• Configuration validation: Run typechecks and code formatter checks:

  npm run check

Deployment Configuration

• Multi-Platform Target: Quartz builds static files that can be hosted on GitHub Pages, Cloudflare Pages, Netlify, or Vercel.
• Build Settings: Use the following standard configurations in host pipelines:
  • Build Command: npx quartz plugin install && npx quartz build
  • Output Directory: public
• Sitemap & RSS: Set baseUrl in quartz.config.yaml to configure feed sitemaps and XML paths correctly.

2. 🔧 Configuration

• Primary settings: Site-wide properties (theme colors, locale, fonts, and active plugins).
• JSON Schema: Supported editors validate syntax and catch formatting mistakes dynamically.

Configuration Template

# quartz.config.yaml
configuration:
  theme: "light"
  locale: "en-US"
  baseUrl: "ssot.0rk.de" # Root domain for feeds
 
layout:
  groups:
    toolbar: # Custom flexbox container
      direction: row # Flex direction
      gap: 0.5rem # Item spacing
  byPageType:
    canvas:
      template: minimal # Render frame override for Obsidian .canvas files
    content:
      template: default # Fallback layout frame
 
plugins:
  - source: github:quartz-community/explorer
    enabled: true
    layout:
      position: left # Section placement (left/right/beforeBody/afterBody/footer)
      priority: 100 # Priority order (higher numbers render higher up)
    options:
      title: "Navigation"
  - source: github:quartz-community/latex
    enabled: true
    layout:
      position: beforeBody
      priority: 50
    options:
      renderEngine: katex

Advanced Customization (quartz.ts)

• TypeScript Merging: Code-based configuration logic, plugins callbacks (sorting/filtering), and customizations are written in quartz.ts.
• Precedence rule: Programmatic rules in quartz.ts take precedence and merge directly with values in quartz.config.yaml.

3. 📦 Dependencies

System Requirements

• Runtimes: Requires Node.js v22+ and npm v10.9.2+ to support core ESM and plugin API execution.
• Module Sync: Restore all plugins listed in project configuration:

  npx quartz plugin install --from-config

Plugin Management CLI

• Add External Plugin: Install community-authored plugins directly from GitHub repositories:

  npx quartz plugin add <github-url>

• Dependency Updates: Resolve lockfile or fresh clone issues by updating all plugins:

  npx quartz plugin install --latest

Core Plugin Pipeline Stages

4. 💡 Best Practices

• Build Optimization: Disable computationally expensive emitters like GraphView to accelerate compilations in large vaults.
• Obsidian Link Format: Use clean Markdown relative links or native Wikilinks ([[VaultNote]]) for reliable link resolution.
• Asset Management: Keep images and attachments in a centralized vault folder to ensure path mappings build without errors.

5. 🚨 Gotchas & Warnings

• V4 Configuration Migrations: Version 4 utilizes TypeScript configs (quartz.config.ts); version 5 enforces quartz.config.yaml.
• Option Nesting Gotchas: Ensure option properties are nested under the options: block in your YAML, or Quartz will silently ignore them.
• C# Collision: Do not confuse Quartz SSG (Obsidian publishing) with the Quartz.NET scheduling library.
• Slow Builds: Speed up builds in heavy environments using the concurrency flag:

  npx quartz build --concurrency 8

• Failed Deployments: Outdated Node/npm engines are the leading cause of setup dependency errors in production environments.
• Nginx Clean URL 404s: Quartz references internal pages with clean URLs (e.g. /specs/omp), but emits them as .html files (e.g. /specs/omp.html). To prevent 404 routing errors, ensure the Nginx config has the .html fallback enabled:

  location / {
      try_files $uri $uri/ $uri.html =404;
  }

6. 🔍 Research

• Quartz Syncer: Obsidian companion plugin that pushes vaults and resolves/exports Dataview queries to static formats.
• Canvas Rendering: Core layout supports direct visual parsing and responsive display of Obsidian .canvas maps.
• Official Documentation: Quartz SSG Official Site
• Source Code: jackyzha0/quartz

llms.txt gives Large Language Models and AI agents a clean, curated, machine-first map of a site’s content — a table of contents written for inference, not browsers. It sits beside its cognitive-filesystem siblings SKILL.md, AGENTS.md, and the lingo glossary.

1. 🧬 Anatomy

Canonical skeleton of a compliant llms.txt, top to bottom — clean Markdown in a fixed order.

# Site/Project Name
 
> Blockquote containing a short, descriptive context summary.
 
Detailed project descriptions and usage guidelines go here.
 
## 2. Navigation Group Heading
 
- [Link Name](https://ssot.0rk.de/target): Optional description text separated by a colon.
- [Additional Link](/local-path): Description details.

3. 🚀 Deployment

Serve raw text files from the domain root.

• Location: Host at the root of the target domain:
  • https://ssot.0rk.de/llms.txt — streamlined navigation and high-level table of contents.
  • https://ssot.0rk.de/llms-full.txt — optional full-text compilation of all target documents.
• Static Serving: Drop the raw text files directly into the public or content directories of static site generators (Quartz, Docusaurus, VitePress).

4. 📦 Tooling

• WordPress: integrate via SEO plugins (e.g. Yoast, AIOSEO).
• CI/CD: generate dynamically during builds with project crawlers or custom scripts.

5. 💡 Best Practices

• Jargon-Free Language: keep descriptions simple and direct for optimal LLM context parsing.
• Clean Markdown: avoid complex HTML tags or styles so scrapers stay compatible.
• Unambiguous Paths: use absolute URLs or root-relative paths for reliable link resolution.

6. 🚨 Gotchas

• Not an Official Protocol: major AI platforms do not commit to parsing llms.txt automatically.
• Complementary to Robots: llms.txt guides attention but never replaces the permission controls in robots.txt.
• Token Optimization: keep llms.txt high-level and offload full text to llms-full.txt to minimize token overhead.

N32G031-based vape → pocket console. Novo 6 · Raz TN9000 · Kraze HD7K & clones.

graph LR
    A["🔓 OPEN<br>Teardown + clean<br><i>spudger, IPA+gloves</i>"]
    B["🔌 CONNECT<br>USB-C SWD tap<br><i>CC1=SWDIO, CC2=SWCLK<br>3.3V ONLY!</i>"]
    C["📥 DUMP<br>OpenOCD flash<br><i>0x08000000<br>64KB MCU, 1MB SPI NOR</i>"]
    D["🎨 MOD<br>RGB565 bitmaps<br><i>80×160 px, big-endian<br>Pillow</i>"]
    E["📤 FLASH<br>SPI/SWD write<br><i>TL866 / CH341A<br>flashrom</i>"]

    A -->|"⏱️"| B -->|"⏱️"| C -->|"⏱️"| D -->|"⏱️"| E

    style A fill:#4a9,color:#fff
    style B fill:#49a,color:#fff
    style C fill:#69c,color:#fff
    style D fill:#e9973f,color:#fff
    style E fill:#a882ff,color:#fff

🧤 GLOVES MANDATORY · 🔋 DISCONNECT BATTERY FIRST

🧠 HW Overview

graph TD
    HW["📋 HW SPECS"]
    MCU["🧠 MCU<br>N32G031K8Q7<br>ARM Cortex-M0 · 48MHz<br>64KB Flash · 8KB SRAM"]
    SCR["📺 Screen<br>0.96″ 80×160 IPS TFT<br>ST7735S or GC9107<br>4-wire SPI"]
    FLS["💾 Flash<br>GT25Q80A 8Mbit (1MB)<br>bitmaps, puff counters, config"]
    CEL["🔋 Cell<br>13450 Li-ion ~1700mAh<br>UNPROTECTED · puncture = 🔥"]
    COI["⚡ Coil<br>N-ch MOSFET driver<br>latch HIGH = fire hazard ☠️"]

    HW --- MCU
    HW --- SCR
    HW --- FLS
    HW --- CEL
    HW --- COI

    style HW fill:#69c,color:#fff,stroke:#357,stroke-width:2px
    style CEL fill:#f44,color:#fff,stroke:#a00,stroke-width:2px
    style COI fill:#f80,color:#fff,stroke:#a50,stroke-width:2px

1. 🛠️ Teardown

🔥 PULL GENTLY: Do NOT puncture the 13450-size 1700mAh lithium-ion battery! Puncture = Thermal runaway = fire.

🧤 E-liquid has nicotine (toxic and absorbs through skin!). Use 99% Isopropyl Alcohol to clean the logic board and wear nitrile gloves!

2. 🔌 SWD Tap

The USB-C SWD Hack: Hardware engineers often wire the SWDIO and SWCLK debug lines directly to the unused CC1/CC2 pins on the USB-C port!

graph LR
    subgraph USB["🔌 USB-C Port"]
        CC1["CC1"]
        CC2["CC2"]
        GND_U["GND"]
        VBUS["VBUS 5V"]
    end
    subgraph PRB["🔬 Debug Probe"]
        SWDIO["SWDIO"]
        SWCLK["SWCLK"]
        PGND["GND"]
    end
    subgraph MCU["🧠 N32G031"]
        PA13["PA13"]
        PA14["PA14"]
    end

    CC1 -->|"data"| SWDIO -->|"debug"| PA13
    CC2 -->|"clock"| SWCLK -->|"debug"| PA14
    GND_U -->|"common"| PGND
    VBUS -.->|"LETHAL"| PA13

    style VBUS fill:#f44,color:#fff,stroke:#a00,stroke-width:3px
    style CC1 fill:#4a9,color:#fff
    style CC2 fill:#49a,color:#fff
    style PA13 fill:#6a6,color:#fff
    style PA14 fill:#6a6,color:#fff
    style SWDIO fill:#4a9,color:#fff
    style SWCLK fill:#49a,color:#fff

# USB-C Debug Accessory Mode: CC1→SWDIO | CC2→SWCLK | GND→GND
# ⚠️ 3.3V ONLY — 5V probe = dead MCU | Need breakout + 5.1kΩ pull-downs
openocd -f interface/stlink.cfg -f target/n32g031.cfg \
  -c "init; halt; dump_image fw.bin 0x08000000 0x10000; exit"
# Got 0xFFFFFFFF? → FMC read-protection ON 🔒 → chip-erase (loses factory FW)
# Alt: SRAM injection via ISP (BOOT0 pin) or UART bootloader

3. 📥 FW Extraction

flowchart TD
    A(["🔬 Connect SWD"]) --> B{"halt + dump?"}
    B -->|"got data"| C["📊 Ghidra/IDA"]
    B -->|"0xFF..."| D{"🔒 FMC Locked"}
    D -->|"nuke it"| E["💣 Chip Erase"]
    D -->|"bypass"| F["💉 SRAM Inject"]
    D -->|"alt"| G["📡 UART Boot"]
    E --> H["⚠️ Factory FW Gone"]
    H --> I(["📤 Flash Custom"])
    F --> J["🔓 RAM Bypass"]
    G --> J
    J --> C
    C --> K["🗺️ Locate Bitmaps"]

    style A fill:#4a9,color:#fff
    style D fill:#f44,color:#fff,stroke:#a00,stroke-width:3px
    style H fill:#f80,color:#fff
    style E fill:#fa0,color:#000
    style I fill:#4c9,color:#fff
    style K fill:#69c,color:#fff

🔒 FMC Lock? If the memory dump gives you endless 0xFFFFFFFF, the Flash Memory Controller (FMC) is locked. You’ll need SRAM injection via ISP mode or a Whole Chip Erase (destroys factory firmware forever).

4. 🎨 Display Mod

Pixel Format: RGB565 — 16-bit color (5 bits Red, 6 bits Green, 5 bits Blue) stored in big-endian layout. 🌈

flowchart LR
    A(["🖼️ PNG"]) -->|"Pillow"| B["📐 80x160"]
    B -->|"convert"| C["🎨 RGB565"]
    C -->|"pack BE"| D["📦 out.bin"]
    D -->|"desolder"| E["🔧 SSOP Adapt"]
    E -->|"program"| F["💾 TL866/CH341A"]
    F -->|"resolder"| G(["✅ Custom LCD"])

    style A fill:#69c,color:#fff
    style C fill:#e9973f,color:#fff
    style D fill:#a882ff,color:#fff
    style G fill:#4c9,color:#fff

# PNG → RGB565 binary (big-endian!) — flash to GT25Q80A via TL866/CH341A/flashrom
from PIL import Image; import struct
img = Image.open('custom.png').convert('RGB').resize((80,160))
open('out.bin','wb').write(b''.join(
    struct.pack('>H',((r>>3)<<11)|((g>>2)<<5)|(b>>3))
    for y in range(160) for x in range(80) for r,g,b in [img.getpixel((x,y))]))

5. 🖥️ LCD Init

sequenceDiagram
    participant MCU as MCU
    participant LCD as LCD

    rect rgb(68, 207, 110, 0.1)
        Note over MCU,LCD: Reset Phase
        MCU->>LCD: SWRESET 0x01
        Note over LCD: 150ms wait
        MCU->>LCD: SLPOUT 0x11
        Note over LCD: 500ms wait
    end

    rect rgb(83, 223, 221, 0.1)
        Note over MCU,LCD: Config Phase
        MCU->>LCD: COLMOD 0x3A 0x05 (RGB565)
        MCU->>LCD: MADCTL 0x36 (orientation)
        Note right of MCU: Bit3 = RGB/BGR swap
        MCU->>LCD: CASET 0x2A (col range)
        MCU->>LCD: RASET 0x2B (row range)
    end

    rect rgb(168, 130, 255, 0.1)
        Note over MCU,LCD: Activate Phase
        MCU->>LCD: DISPON 0x29
        MCU->>LCD: RAMWR 0x2C + pixels
    end

SWRESET(0x01) → SLPOUT(0x11) → COLMOD(0x3A,0x05=RGB565) → MADCTL(0x36) → DISPON(0x29)

• 🔄 Red/blue swapped? XOR MADCTL with 0x08 (bit 3 toggles RGB↔BGR). Don’t rewire.
• ⬛ Black border/offset? Set CASET(0x2A)/RASET(0x2B) — try _colstart=0x01 or 0x1A.
• 🔲 GC9107 blank? Must send unlock 0xFF→0xA5 before any command. Init may start 0xFE/0xEF/0xEB.

6. 👾 Custom FW

graph TD
    subgraph SDK["📚 Community SDKs"]
        A["ColorLCDVape-RE"] -->|"memory maps"| C["⚡ Custom FW"]
        B["Vaporware SDK"] -->|"display API"| C
        D["RAZ-RE"] -->|"HW pinouts"| C
    end

    C -->|"compile"| E["🔧 arm-gcc"]
    E -->|"flash"| F["📤 SWD Write"]
    F --> G(["🎮 Pocket Console"])

    subgraph SAFE["🚨 Safety Critical"]
        C -->|"must have"| H["⏱️ Timer ISR"]
        H -->|"kills"| I["🔌 MOSFET Off"]
        C -->|"must have"| J["📊 ADC Watch"]
        J -->|"triggers"| K["🔋 LVC Cutoff"]
    end

    style H fill:#f44,color:#fff,stroke:#a00,stroke-width:3px
    style J fill:#fa0,color:#000,stroke:#a50,stroke-width:2px
    style G fill:#4c9,color:#fff
    style I fill:#f44,color:#fff
    style K fill:#fa0,color:#000

⚠️ THE COIL OF DEATH: If you write your own C code and your MOSFET pin latches HIGH by accident, your coil will melt, the pod will catch fire, and the battery will vent. ALWAYS code a strict hardware-timer-backed thermal cutoff limit! ⏱️🚨

🛡️ Safety Pattern

// MANDATORY: hardware-timer-backed coil cutoff — main loop bugs CANNOT override
#define MAX_FIRE_MS 10000   // 10s hard ceiling
#define MIN_VBAT_MV 3000    // 3.0V low-voltage cutoff
 
void init_safety(void) {
    GPIO_ResetBits(GPIOA, COIL_PIN);              // default: coil OFF
    TIM_SetAutoReload(TIM3, MAX_FIRE_MS);          // ISR kills MOSFET
    TIM_ITConfig(TIM3, TIM_IT_Update, ENABLE);
    ADC_AnalogWatchdogThresholdsConfig(ADC1, 0xFFF, MIN_VBAT_MV);
}

📦 Deps & Tools

🚨 Gotchas

🏗️ Full Architecture

graph TB
    subgraph L1["🔓 Physical"]
        A["📦 Device"] -->|"pry open"| B["🔧 Teardown"]
        B -->|"99% IPA"| C["🧹 Clean"]
    end

    subgraph L2["🔌 Debug"]
        C -->|"expose CC"| D["🔌 USB-C Break"]
        D -->|"3.3V"| E["🔬 SWD Probe"]
        E -->|"connect"| F["💻 OpenOCD"]
    end

    subgraph L3["📥 Extract"]
        F -->|"halt"| G{"🔒 FMC?"}
        G -->|"unlocked"| H["💾 MCU 64KB"]
        G -->|"locked"| I["💣 Erase"]
        I -->|"blank MCU"| J["🆕 Fresh"]
        F -->|"SPI read"| K["💾 Flash 1MB"]
    end

    subgraph L4["🎨 Mod"]
        H -->|"disasm"| L["🔬 Ghidra"]
        K -->|"extract"| M["🖼️ Bitmaps"]
        M -->|"Pillow"| N["🎨 RGB565"]
        N -->|"program"| O["📤 Flash SPI"]
    end

    subgraph L5["👾 Custom OS"]
        L -->|"understand"| P["📝 Write FW"]
        P -->|"safety!"| Q["🚨 ISR Guard"]
        Q -->|"deploy"| R(["✅ Done"])
    end

    style I fill:#f44,color:#fff,stroke:#a00,stroke-width:2px
    style Q fill:#f80,color:#fff,stroke:#a50,stroke-width:2px
    style A fill:#69c,color:#fff
    style R fill:#4c9,color:#fff
    style G fill:#f44,color:#fff

🗺️ Visual workflow map: NovoModCanvas →

Pitch: Replace two fragmented knowledge systems with a single, isolated Quartz 5 instance at w.0rk.de.

📊 Visual Migration Map: Interactive Canvas →

1. ⚠️ Problem

Two knowledge bases, two build systems, zero cross-linking.

2. 💡 Solution

A 3rd isolated Quartz 5 instance — separate from ssot.0rk.de (specs) and quartz.0rk.de (showcase).

1. ⚙️ Quartz 5

• Obsidian [[wikilinks]] — wiki already uses them
• Full-text search (Pagefind) — wiki has none
• Graph view — visualize knowledge connections
• Canvas support — visual mind maps (this pitch is one)
• Consistent stack — same tooling as SSOT
• llms.txt generation — AI-agent-navigable

2. 🛡️ Why Isolated

• SSOT = technical specs (how to build things)
• w.0rk.de = knowledge (what things are, research, entities)
• Different audiences, update cadences, content schemas
• Independent deploy cycles, no cross-contamination

3. 🗂️ Taxonomy

quartz-wiki/content/
├── architecture/          ← llm-wiki architecture/ (7 cognitive layers)
│   ├── identity-anchors/
│   ├── mutable-memory/
│   ├── orchestration/
│   ├── capabilities/
│   ├── autonomic/
│   ├── spec-driven/
│   └── swarm-alignment/
├── topics/                ← llm-wiki topics/ (13) + wiki concepts/ merged
│   ├── cs2docs.md
│   ├── docskurby.md
│   ├── quartz5.md
│   ├── skill-xray.md
│   ├── discord-omp-plugin.md
│   ├── svelte-5-*.md
│   ├── transformer-architecture.md  ← from wiki concepts/
│   └── ...
├── entities/              ← wiki entities/ (research-grade profiles)
│   └── karpathy-llm-wiki.md
├── research/              ← llm-wiki research/ + evolving/ merged
│   ├── research-automation.md
│   └── evolving/
├── raw/                   ← wiki raw/ (source archive)
│   ├── articles/
│   ├── papers/
│   ├── transcripts/
│   └── assets/
├── reference.md           ← llm-wiki-reference.md (system cheatsheet)
└── index.md               ← unified homepage

Total: ~31 pages (28 from llm-wiki + 3 from wiki, with concepts folded into topics).

4. 🪜 Pipeline

1. 🔄 Post-Migration

• llm-wiki.0rk.de → 301 redirect to w.0rk.de
• wiki.0rk.de → 301 redirect to w.0rk.de
• Hugo repo archived, wiki directory superseded

5. ⚙️ Infrastructure

# /etc/nginx/sites-enabled/w.0rk.de
server {
    listen 443 ssl http2;
    server_name w.0rk.de;
 
    root /home/dv/quartz-wiki/public;
    index index.html;
 
    location / {
        try_files $uri $uri/ $uri.html =404;
    }
 
    # certbot --nginx -d w.0rk.de
    ssl_certificate /etc/letsencrypt/live/w.0rk.de/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/w.0rk.de/privkey.pem;
}

1. 🌐 DNS

Add w.0rk.de A/AAAA record pointing to same server IP as other *.0rk.de domains.

6. 🌐 Landscape

7. 📊 Effort

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.