cogni-dao/cogni / .claude/skills/node-wizard-expert
node-wizard-expert
VerifiedUse when designing, debugging, or operating the Cogni node formation wizard, node formation PRs, submodule-pinned node repos, child image builds, node deploy calls, or AI-assistant launch handoffs. Route launch execution and E2E proof to node-wizard-scorecard.
Node Wizard Expert
Route the work through operator-architect first; this skill adds the node formation wizard rules on top of it.
Primary Pointer
For any live throwaway-node launch, start with
node-wizard-scorecard. This skill is the
orientation layer; the scorecard is the execution and proof layer.
First Recall
Before changing node-wizard launch behavior, recall the operator knowledge block:
node-launch-handoff—https://cognidao.org/knowledge/node-launch-handoffakash-cicd-pareto-scope—https://cognidao.org/knowledge/akash-cicd-pareto-scope
That block is the evolving handoff contract for personal AI assistants launching a newly birthed node. Treat it as the operator-owned playbook; refine it when the launch process changes instead of duplicating long runbooks in the wizard UI.
North-star birth contract — do not normalize the current gap
akash-cicd-pareto-scope is mandatory for any formation design or review. The
target acceptance contract is:
Spawn -> repo + immutable bundle -> passive ephemeral candidate proof
-> same digest in production -> canonical hostname exact-SHA proof
-> close candidate -> return production-live node
- Production is generation-1 activity authority. Candidate-a validates but never creates a competing activity ledger; preview is absent at birth.
- The node is born Akash-native with one deployment/placement group per
(node, environment)workload bundle. App-tier sidecars share that group. - Shared generic substrate remains pooled; do not create a Temporal worker, database, queue, or model gateway per node by default.
- A shared-runtime scope is the cheaper starting product when a community does not need unique executable code. It is not a sovereign node.
Today formation emits candidate-a only and missing placement still defaults to k3s. Treat that as the critical implementation gap, not the intended lifecycle.
Ground Truth
.claude/skills/node-wizard-scorecard/SKILL.md- https://cognidao.org/knowledge/node-baas-substrate-model — node-as-a-service architecture + substrate model (read for the substrate-gaps work)
https://cognidao.org/knowledge/node-secret-materialize-phaseshttps://cognidao.org/knowledge/run-node-formation-wizardhttps://node-template.cognidao.org/knowledge/node-ci-sovereigntyscripts/ci/reconcile-edge-caddy.remote.sh·scripts/ci/reconcile-node-substrate.sh— the substrate lane (edge + per-node DB/secret reconcile)nodes/operator/app/src/features/nodes/launch-pack.tsnodes/operator/app/src/app/api/v1/nodes/[id]/launch-pack/route.ts.claude/skills/conductor-worktree-setup/SKILL.mdscripts/conductor-worktree-setup.shscripts/ci/sync-node-template-fork-pr.sh
Operating Rule
Today the wizard mints and publishes birth facts, then hands launch execution to
an AI assistant through the launch pack. Keep CI, GHCR, flight, Argo, and
/version state derived from their source systems rather than duplicating saved
wizard state. The north-star assistant flow must drive the full saga above and
return a production-live node; a generated PR or candidate deployment is only
progress, never successful Spawn completion.
Recent launch-path finding: generated parent birth PRs for throwaway nodes are
not progress by themselves. Progress is a scorecard row moving from blocked to
pass without privileged manual bridge work. A child commit without a child
sha-<child-sha> GHCR image is a blocker, not a deployable pin.
DNS is automatic; edge is automatic-but-fragile (known gap). A wizard-born node's public host (<node>-<env>) has its A-record upserted by reconcile-node-dns.sh (catalog-driven) and its edge Caddy route written by the flight's node-substrate job (reconcile-edge-caddy.remote.sh). DNS is reliable; the edge is NOT yet reliably hands-off — see the substrate-gaps table below (a freshly-flighted node can be Argo-Healthy and serve in-cluster yet return external 000 because Caddy's running config didn't pick up the new site). Canon: https://cognidao.org/knowledge/operator-pipeline-contract Axiom 21 DNS_IS_RECONCILED_PER_ENV; operational detail in the dns-ops skill. A fresh-flight NXDOMAIN is usually negative-cache (dig <host> +short @1.1.1.1); a fresh-flight external 000 with DNS resolving + pod Healthy is the edge-reload gap (bug.5031), not DNS.
Substrate E2E is NOT yet hands-off — gaps + heal recipes
The first real production node launch (beacon, 2026-06-16) proved the control plane (formation, flight dispatch, RBAC) works, but the substrate plane (DB + edge + secrets + preview lease) has gaps that each needed manual intervention — nothing self-healed. Treat these as known failure modes until the linked work lands. Architecture spec: node BaaS substrate model.
| Gap | Symptom | Heal recipe (manual, until fixed) | Fix |
|---|---|---|---|
| Edge not reloaded | node Argo-Healthy + serves in-cluster, but <slug>-<env>.cognidao.org → external 000 | on the VM: docker exec <edge-caddy-container> caddy reload --config /etc/caddy/Caddyfile --adapter caddyfile | bug.5031 / PR #1697 (reload+verify, hash gated on success) |
| Doltgres DB missing | pod Init:CrashLoopBackOff; migrate-doltgres FATAL database "knowledge_<slug>" does not exist | on the VM: docker exec -e PGPASSWORD=<doltgres-pw> <doltgres-container> psql -h 127.0.0.1 -U postgres -c 'CREATE DATABASE knowledge_<slug>;', then kubectl delete pod <crashlooping-pod> | bug.5033 (add doltgres DB-create to the substrate lane next to the Postgres one) |
| Preview = single GLOBAL lease | preview deploy queues forever; deploy/preview review-state: reviewing on a stale/unrelated sha | commit unlocked to deploy/preview/.promote-state/review-state, then gh workflow run flight-preview.yml -f sha=<main-head> | bug.5032 (per-node preview lease, mirror candidate-a) |
| No LLM backend | node deploys but POST /chat/completions times out | provision the node's LiteLLM/model secret | (gap — graph exec unusable until wired) |
| Launch agent flounders | fresh agent hunts .env.cogni, 401s recalling the knowledge block | register first (/contribute-to-cogni) → save token → then recall | bug.5030 / PR #1695 |
| Can't track flight | dev hangs on a hand-rolled watcher | poll candidate /version for buildSha==sourceSha (authless); never watch GH Actions | task.5021 (operator flight-status API) |
| "pin" PR stalls | chore(node): pin <slug> PR sits open, not auto-merged | merge it (operator merge-authority) → triggers flight-preview | task.5022 (auto-bump+merge source_sha, rename pin→bump) |
Production heal needs prod read/SSH (owner-gated; "never SSH prod" is the default — a one-off prod data fix needs explicit owner authorization and a captured follow-up bug). Pareto fix: make the substrate lane idempotent + verify-and-heal (DB + edge + secrets) so none of these need a human — bug.5033 + PR #1697 are the first two. Note: work-item IDs (bug.503x) currently collide with in-code bug refs (e.g. bug.5031 is also the Grafana datasource-drift class in committed docs) — confirm against the work API before citing.
Current production substrate lever: after the declarative fix is merged, call POST /api/v1/deploy/infra-reconcile {nodeId:<operator-node-id>, env:"production"} with the agent Bearer key. Production-promoter RBAC temporarily authorizes the operator GitHub App as a two-phase bootstrap bridge; story.5028 owns the least-privilege split to production_infra_promoter → can_reconcile_production_infra after the lever has deployed that OpenFGA model. The route preserves the deployed app pin and accepts no caller SHA/ref/workflow/mode. Candidate uses its test App and env-scoped test parent only; production uses its production App and parent. This is for the shared state/edge substrate only. Wizard-born node apps remain Akash compute workloads—create/replace/scale them through the compute API, never by extending this shared-VM lever. Do not ask the owner to click GitHub Actions or perform normal production SSH changes; only an RBAC approval may require them.
Repo Ancestry Rule
Wizard-minted nodes must be named forks of node-template, not GitHub template-generated repos. Template generation copies a snapshot without shared git history, so agents cannot fetch node-template and merge future template updates. The publish path should call GitHubRepoWriter.forkFromTemplate, wait for the forked main, commit only the regenerated .cogni/repo-spec.yaml identity on top, and pin that identity commit as the operator submodule gitlink.
If a same-named repo already exists, reuse it only when it is a fork of the configured NODE_TEMPLATE_OWNER/node-template; otherwise fail closed and repair the repo lineage explicitly.
Fast Repair
When a minted test-node fork lags behind cogni-test-org/node-template, refresh
its existing PR branch with:
PR_TITLE='ci: sync <slug> node CI' \
scripts/ci/sync-node-template-fork-pr.sh cogni-test-org/<slug> <branch>
This is the repeatable version of the manual test-cog repair: fetch the fork
PR branch, merge the current test-org template, auto-resolve the known stale
ci.yaml image-name conflict in favor of the template, run the node workflow
invariant, push, and print the PR/check links.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |