33god-projects

name

33god-projects

description

Create, wire, and maintain 33god/DeLoNET projects. Covers PJangler/CommonProject bootstrap, repo-local `.project.json`, Hermes PM provisioning requests (sentinel duties fold into the PM heartbeat), mise/.env.op, BMAD, Hindsight/Bloodbank hook wiring, and project-scoped hook + skill fan-out adoption. Use when running `pj init`, `pj hermes-agent --yes`, or `mise run init-project`; adding a PM; wiring mise/op inject; installing BMAD; configuring hooks; or adopting `.agents/local.json`, `defer_to_global`, and `hooks.master.json`. Do NOT use for developing pjangler (project-jangler), generic fan-out mechanics (agent-config-fanout), fleet updates/backfills (agent-fleet-operations), live Plane issues, Bloodbank schemas, or host conventions.

33god Project Creation & Wiring

Every 33god/DeLoNET repo is assembled by pjangler out of two copier templates it vendors as submodules under ~/code/33GOD/pjangler/templates/:

• CommonProject (templates/commonproject) — the base skeleton: .project.json, mise.toml, .mise/scripts/, BMAD, the ticket board.
• hermes-agent-template (templates/hermes-agent) — the Hermes PM role provisioned into agents/hermes/pm/ (unified single-PM model — the retired scrum-master's sentinel duties run on the PM heartbeat).

.project.json at the repo root is the single source of truth for project + board identity. There is one ticket board per repo; every agent binds to it.

Operating Principles

• .project.json is canonical. Board binding (ticket_provider block), repo_path, project_slug, and the agents map live there. Plane bindings require plus a live identifier/board id; never persist or reintroduce a separate .