mathiasandClaude Opus 5
99fb969d27
TestAtlasJSON_ServesAtlasWithGeneratedCIStage demanded STAGE 06 contain the
job names parsed from the embedded cd.yml (guard/check/build/deploy). But when
the forge is reachable, the handler deliberately REPLACES those nodes with the
latest real run — live per-job status, which is the whole point of that overlay.
So the test passed on a laptop with no route to Gitea and failed inside CI,
where the overlay works as designed:
CI stage missing generated job "guard"
(got map[Detect unsubstituted template:true Lint / Test / Vet:true
▶ run #62 · running:true])
It went red on a commit that touched only atlas.json — a test that depends on
whether the network is reachable will eventually fail on someone innocent, and
did.
The endpoint test now asserts the shape it serves — STAGE 06 exists, is
populated by whichever source won, and every node has a title. The
deterministic assertion already exists where it belongs, in
TestBuild_OverlaysCIStageNodesFromWorkflow, which feeds Build a fixed workflow
and never touches the network.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_011PL5XcG68SvQqz3vGVbWbf
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.