Files
mathiasandClaude Opus 4.8 5c6a4ab232
CD / Detect unsubstituted template (push) Successful in 1s
CD / Lint / Test / Vet (push) Has been skipped
CD / Build & Import (push) Has been skipped
CD / Deploy via GitOps (push) Has been skipped
feat: Phase A — serve static CAD Atlas viz + self-contained context
Wire the reel-style CAD workflow atlas (signal→pod) as the served page via
go:embed. Fill PROJECT.md/README with the 9-stage workflow, three governance
gates (Ed25519 admission / dispatch-allow / var-go Oath), phase map A→C,
dogfooding model, brain deep-links and external references.

Fixes two template-go-web latent bugs surfaced by dogfooding:
- templ version skew: go.mod pinned v0.2.778 vs templ@latest generator
- .gitignore pattern *.templ.go did not match generated *_templ.go

Verified: go build · vet · golangci-lint (0 issues) · go test green.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-07-19 10:34:23 +02:00

29 lines
1.6 KiB
Markdown

# 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-loop` ledger + `session_log` + Gitea run API + Flux events.
## Quickstart
```bash
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`](.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.