Levandor

cluzter Activity Log

3 min read

For Agents

Reverse-chronological session log. Newest entries at top, grouped by date (## YYYY-MM-DD). Each bullet: one piece of work, short summary, wikilinks to docs touched. Updated by obsidian-documenter on every project doc write. Read by historian at bootstrap.

2026-07-30

  • Design approved for cluzter — a browser-based vehicle wiring-diagram editor for the 1995 Geo Tracker (G16B, Suzuki Vitara/Sidekick platform). Two deliverables define success: a build sheet (cut list + orderable BOM) and a printable large-format reference in the colorized factory style, colour or mono, with a generated colour key. GUI-first, one opaque .cluz zip; engine/ is pure TS with a CI-enforced no-React/no-DOM boundary; SVG renderer; seven-phase plan (P1–P3 = minimum useful tool, P5–P6 = what makes it trustworthy, P7 = jot import + omnibox). Spec is the source of truth at ~/coding/cluzter/docs/superpowers/specs/2026-07-30-cluzter-wiring-diagram-editor-design.md; repo wowjeeez/cluzter at e823fde (spec only, no code yet) — cluzter
  • Recorded the full decision trail, including the two answers that reversed mid-conversation — source of truth (GUI-first opaque file chosen over a text DSL and over bidirectional sync, which killed the round-trip problem and the file watcher outright); ⟲ scale model (first “canvas units are millimetres”, reversed once a reference image showed the target diagram is schematic and not to scale → final answer is two distinct units that never mix); ⟲ renderer (SVG → challenged by szig-felmeres already solving world-space CAD-lite on react-konva → re-decided as SVG on independent grounds: text density, measurable bounding boxes, crisp glyphs, selectable PDF text, DOM keyboard traversal); entry model = both draw-first and omnibox, so the jot parser gains three consumers; terminations as one polymorphic union (cavity·splice·ground·rated fuse/relay cavity); collapse as three-state auto | pinned-open | pinned-shut with auto default — cluzter-design-decisions
  • ⭐ Gotcha note — the four silent failures the model is built to prevent. (1) WireViz has no BL code, so blue wires silently rendered black — “the worst possible silent failure on a wiring diagram”, and the same trap exists in JIS where B is black and Bl is blue; rule is exact-match-only lookup, an unmatched code is a blocking error, never a fallback. (2) Same failure class in mono print — a B&W sheet without inline codes is unreadable but looks plausible, so mono forces labels on regardless of LOD tier. (3) Connector name as identity made ecu vs ECU two nodes in the predecessor; fixed by splitting generated id from display-only designator, collision now a warning. (4) Deriving wire length from a schematic path is a category error producing a silently wrong cut list — forbidden structurally, no code path exists — cluzter-wiring-gotchas
  • Linked cluzter to its neighbours: pipeline (the jot→WireViz predecessor whose 5-field grammar cluzter imports and whose four decisions it inherits), 2026-07-29-hardcut-design (same vehicle, source of the real Bl/G / Br/W / B/Y data), and 2026-07-24-knowledgebase / 2026-07-29-kb-wiring-extraction-v1-complete (the OCR’d Suzuki Vitara scans — only the AI netlists were retired, the scanned pages remain the authoritative underlay source)
  • Initialized activity log.

Graph View