autonomic-bot
251de42894
The Adversary (re-confirmation #22) caught that both my records of the B-redfix-8 public-exposure probe asserted "HTTP 200, 33080 bytes" while the blob is 33408. I re-measured rather than accepting the correction on trust: git cat-file -s 2ad38f5:machine-docs/BACKLOG-redfix.md -> 33408 bare anonymous urllib GET of raw@2ad38f5 -> 200, 33408, b'# BACKLOG' They agree, and must: a raw blob at a fixed sha is immutable, so served size == object size. 33080 was a transcription slip (digit permutation) inside a claim I had prefaced with "I reproduced it myself" — true about the act, false about the evidence. Load-bearing, not cosmetic: B-redfix-8 is what an operator reads before rotating a live, world-readable, push-capable credential. Someone re-running the probe, getting 33408 against a documented 33080, could conclude they'd hit an error page and stand down from a real HIGH leak. Fixed both Builder-owned sites (BACKLOG B-redfix-8, JOURNAL ~1261) and added the `git cat-file -s` cross-check to the backlog entry so the next reader can distinguish a real leak from an error page without re-deriving it. Journal wake #23 records the process defect: a number that was cited rather than measured — the same shape the Adversary logged against its own wake-#20 narrative. Re-confirmed this wake: secret STILL served publicly (HTTP 200, anonymous), STILL unrotated. No DoD item touched. DONE stands, no VETO. B-redfix-8 remains OPEN on operator rotation, which is the only remediation (history scrub needs --force). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018NACoEBDqq4FAHWoTdZHDF
cc-ci — Co-op Cloud recipe CI server
Comment !testme on a PR in an enrolled Co-op Cloud recipe repo and cc-ci deploys the recipe
at that commit onto a real single-node Docker Swarm, runs install / upgrade / backup-restore tests
(Python + Playwright) end-to-end, and reports a live, tail-able run with pass/fail back to the PR.
This repo declares the entire server as a NixOS flake and holds the test harness, the per-recipe test trees, and the docs to enroll a recipe or rebuild the box from scratch.
Status: under active autonomous construction. See
machine-docs/STATUS.mdfor the live phase andplan.md-driven milestones inmachine-docs/BACKLOG.md. Definition of Done is D1–D10 (see the build plan).
Layout
flake.nix NixOS entry point + devshells (`#cc-ci` = live Hetzner host, `#cc-ci-incus` = legacy Incus host)
nix/hosts/cc-ci/ legacy Incus VM host config (fallback / historical)
nix/hosts/cc-ci-hetzner/ live Hetzner host config
nix/modules/ drone, comment-bridge, swarm, dashboard, secrets (Nix modules)
secrets/ sops-encrypted infra secrets (cc-ci-secrets submodule)
bridge/ !testme webhook listener source
runner/ run_recipe_ci.py + shared pytest harness
dashboard/ results overview generator
tests/<recipe>/ per-recipe install/upgrade/backup tests + custom/
docs/ install, enroll-recipe, secrets, architecture, runbook, baseline
All .nix code lives under nix/; flake.nix/flake.lock stay at the repo root. Host targets are:
#cc-ci= canonical live Hetzner server#cc-ci-hetzner= explicit alias for the same live Hetzner server#cc-ci-incus= legacy Incus VM definition only; do not use on Hetzner
Docs
docs/install.md— rebuild the server from scratch (D8)docs/testing.md— test architecture: generic lifecycle suite + layered recipe overlays (override/extend, discovery precedence, custom install-steps hook)docs/enroll-recipe.md— add a recipe under CI (D5)docs/secrets.md— secret model + rotation (D6)docs/architecture.md,docs/runbook.md— design + debugging failed runsdocs/baseline.md— bootstrap snapshot / rollback reference
Linting & formatting
The codebase is kept formatted + lint-clean by a single entrypoint, run from the pinned lint
devshell so local and CI use identical tool versions:
nix develop .#lint --command bash scripts/lint.sh # check-only (what CI runs)
nix develop .#lint --command bash scripts/lint.sh --fix # auto-format + apply fixes
Covers Nix (nixpkgs-fmt · statix · deadnix), Python (ruff lint+format), Shell
(shellcheck · shfmt), and YAML (yamllint). Config lives in ruff.toml / .yamllint.yaml;
tool/strictness choices are in machine-docs/DECISIONS.md. CI enforces it: the lint step in the
.drone.yml push pipeline runs the same command and fails the build on any unclean file, so
keep commits clean (--fix before pushing).
Loop state (autonomous build)
The multi-agent loop state lives under machine-docs/: STATUS.md (phase/blockers),
BACKLOG.md (work + adversary findings), REVIEW.md (independent verification), JOURNAL.md
(build log), DECISIONS.md (architecture choices) — plus the phase-namespaced *-1b.md / *-1c.md
variants. See the build plan for the two-loop Builder/Adversary protocol.