Commit Graph
6 Commits
Author SHA1 Message Date
Omar SobhandClaude Opus 5.5 a428d7cf11 docs(readme): container-tier missions no longer hold provider keys
deploy / test (push) Successful in 5m6s
deploy / build (push) Successful in 1m3s
LLM proxy enabled on prod and proven on mission 01a0cf7e: container env and
config hold only cmlp tokens (no real key value anywhere in either), both
fallback hops rewritten, the mission completed, judged MET and pushed. Controls:
no token 401, forged 401, finished mission 403, port unreachable from outside.

Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
2026-09-23 13:22:12 -05:00
Omar SobhandClaude Opus 5.5 60a1fef5e5 docs(readme): say what now limits a leaked provider key, and what does not
deploy / test (push) Failing after 3m51s
deploy / build (push) Skipped
Proven live with a canary (missions 01a0cf3d, 01a0cf4c): push refused, patch
redacted, 0 of 19 events and 0 judge fields carrying the value.

Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
2026-09-23 12:27:46 -05:00
Omar SobhandClaude Opus 5.5 4030347b56 docs(readme): state three claims precisely — judge independence, stop-gate cap, provider keys
deploy / test (push) Successful in 5m21s
deploy / build (push) Successful in 1m5s
- the judge is cross-provider only when one is configured; the self-host
  default judges with Claude and records it as not independent
- the stop gate blocks at most 3 times, not until the check passes
- mission containers DO carry model-provider keys in their environment
  (verified on prod: CLAUDE_CODE_OAUTH_TOKEN, ZAI_API_KEY, KIMI_API_KEY);
  the broker claim holds for platform credentials, not these

Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
2026-09-23 11:24:01 -05:00
Omar SobhandClaude Opus 5.5 1e293f2840 docs: bring the README up to date with two months of shipped work
deploy / test (push) Successful in 5m25s
deploy / build (push) Successful in 1m9s
Last rewritten 2026-07-21. Verified against the repo and prod before writing:
- adds what shipped since: the single dashboard, recipes + team templates,
  container and microVM tiers, the independent judge (Kimi fallback, quota
  watchdog, offline npm), tool gates + shadow task-permission/taint, skills
  door, project memory + self_audit, continuous research/podcast, cm-decide,
  fleet placement, A2A
- fixes wrong facts: cm-brain is the .brain facade (not LLM planning);
  cm-decide and fcagent were missing; migrations are 0001–0087 in migrations/;
  the deploy path is CI (test → build → push) plus the gw-04 timer
- the line-count budget is NOT enforced in CI (12 files exceed 1500) — said so
- safety section no longer claims every agent is tool-free and network-less:
  container-tier missions have public egress, and the gate is a guardrail,
  not a boundary

Every relative link and repo path in the file was checked to exist.

Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
2026-09-23 10:04:40 -05:00
Omar Sobh c62251090c docs: rewrite README against current main
ci / gates (push) Successful in 6s
ci / frontend (push) Successful in 28s
ci / rust (push) Successful in 4m23s
ci / e2e (push) Skipped
ci / publish (push) Successful in 4m7s
The README was last touched 2026-06-18 and had drifted badly:

- Crate table missed cm-brain, cm-testkit, cm-tools, and the
  clawmates-node bin (the herdr daemon)
- Missions system (slices 1-9) was not mentioned
- Herdr phases 0-3 (persistent daemon, dispatch, live pane, INFRA-tier
  sessions) were not mentioned
- Prod deploy path on gw-04 was undocumented — the three real gotchas
  (non-compose-managed runtime, UID 65532 bind-mount, ZeroClaw provider
  env inheritance) are what bit us on 2026-07-09 and 2026-07-12
- CI 1500-LoC hard budget was not called out
- Refine still said "Gemini" — refine switched to Opus 4.8 in 1cbbbbd
- Broker master-key backup mentioned only via cross-link

Splits crates into workspace crates + bins tables, adds a Production
deployment section for gw-04, adds a CI budgets section, promotes the
broker key warning inline, and rewrites Shipped to reflect what actually
landed since 2026-06-18.
2026-07-21 04:35:58 -07:00
Omar SobhandClaude Opus 4.8 540c74f42e Adopt design comps: dark system, new landing/auth, dashboard shell + canvas
Re-skins the whole app to the dark design comps and wires the new surfaces to
the backend (the /api proxy + auth + schemas are unchanged).

Design system:
- globals.css: remapped @theme tokens to the comp palette (#08080a base, coral
  #ff6f61, status cyan/green/amber/purple/teal); token names preserved
- MeshMark: triangle + 3-node brand glyph; cm-flow/cm-blink/cm-halo keyframes
- marketing flipped light → dark

Backend (migration 0012):
- agents.model_binding (persisted on team deploy) + GET /api/claws/{id}/runtime-config
- routine_runs table + scheduler journaling + GET /api/routines/runs
- GET /api/claws/{id}/compartments (anatomy aggregate)
- GET /api/structure/stats (workspace counts)

Frontend:
- Landing: full dark marketing page (hero constellation, deploy ladder,
  12-topology taxonomy, recursive execution, compare/Pareto, safety, self-host)
- Auth: dark split-panel AuthShell + comp LoginForm + Clerk SignIn themed dark
- Dashboard shell: TopBar (breadcrumb + live stats + deploy + user) + StatusBar
  (runner/sandbox/doors); rail slimmed to 60px + 252px context column
- ConstellationCanvas (radial recursive) replaces the graph view in StructureCanvas;
  selecting a claw opens ComputerPanel (apps/now-running/dock); RoutinesPanel
- Claw anatomy view (/claws/[id]/anatomy) from compartments + runtime-config

Co-Authored-By: Claude Opus 4.8 <[email protected]>
2026-06-19 04:12:16 -07:00