mathiasandClaude Opus 4.8
60cc8894a2
Closes the UX sprint's authored layer. #3 Horizontal-scroll blindness → an always-visible "PIPELINE" overview rail: 9 colour-coded chips (00 Notice → 08 Learn) showing the whole shape at a glance, each click-to-scroll to its stage. First-timers now see the arc + that more exists. #4 Real gate glyph — 🔒 on the two checkpoint transitions (human @04, CI @06), desktop spine + mobile rows. #5 Reconcile legend with Plain: decorative node pills hidden in Plain, so colour is reserved for live status (green/amber/coral) — exactly what the legend keys. (#6 attached chips/grammar: the question-vs-statement label mix is meaningful — decisions vs milestones — kept; SVG chip background skipped as low-value.) New Stage.short (guarded by JSON validity via existing tests). build/vet/lint(0)/ test green; desktop Plain screenshot-verified. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
cad-atlas
A visual atlas of the Continuous Agentic Development (CAD) workflow — from a captured signal to a deployed k3s pod.
One screen, reel-style: Signals → TELOS → Strategic session → Spec/Oath → Human gate → agentsquad → CI → CD → pod, looping back to TELOS. It renders the CAD audit chain, which doubles as the regulated-industry audit artifact.
The CAD audit chain is the visualization data. Phase C renders it once and serves two masters: observability + compliance.
Phases
- A — static hero viz (current): self-contained
internal/web/static/cad-atlas.html, served at/. SVG spine, animated pulse, dashed feedback bus, replay/slow-mo. - B — generated-from-source: render from brain docs + workflows + infra manifests (no drift).
- C — live trace viewer: hydrate from the
assessor-loopledger +session_log+ Gitea run API + Flux events.
Quickstart
task check # lint + vet + test (CI gate)
task run # → http://localhost:8080
Context
Full project context, the 9-stage workflow, the three governance gates, the dogfooding model, and all brain deep-links + external references live in .context/PROJECT.md. Any clean agent session should read that first (brain_get <path> for the linked notes).
Governance (dogfooded)
This repo is built through the workflow it depicts: dispatch-allow-enabled, build increments governed by a var-go Oath in their spec issues. Bootstrapping honesty: the Oath is defined but cmd/vargo-gate is not yet wired into this repo's CI — advisory until it is. See PROJECT.md.