33god Projects

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 state: linked plus a live identifier/board id; never persist ticket_provider.board_url or reintroduce a separate .plane.json.
• One board per repo. The PM owns it; the sentinel pass on the PM's heartbeat watches the same board. Board name = the project name (no role suffix); identifier = slug[:4] uppercased.
• Agent config uses generated base-plus-delta state. PJangler creates a real ~/.hermes/profiles/<repo>-pm/ directory. Its generated config.yaml merges the fleet base with its real, override-only config.delta.yaml; repo-local agents/hermes/pm/runtime/ is ignored local state, not a profile symlink or nested runtime repository.
• mise is mandatory and uniform. Every repo gets the same mise.toml contract.
• Repository ignores stay small and portable. CommonProject preserves an existing .gitignore and adds only repo-owned secret/local-projection rules. Machine-wide backup, editor, and client-CLI patterns stay in the effective global ignore; .agents/ is the only canonical agent-config tree in Git.
• Agents are memory- and event-wired by default. Hindsight recall/retain + Bloodbank emit/consume are part of provisioning. Machine-global Hindsight scripts live in one folder (~/.agents/hooks/hindsight), and machine-global Bloodbank lifecycle hooks invoke one publisher (~/.agents/hooks/bloodbank/publish.py --client <agent> --hook <event>).
• Hooks and skills fan out from the repo, per-dev. A repo that adopts the project-scoped agent layer commits one hooks SSOT + one skill manifest (.agents/skills.json, declaring packs[] and/or skills[]) and lets mise enter run provision-packs.py then sync-skills.py to securely install them into each dev's six supported local CLIs (see references/project-scoped-hooks.md; pack mechanics → agent-config-fanout references/skill-packs.md).
• Templates are version-locked. pjangler runs the vendored submodule unless PJANGLER_HERMES_TEMPLATE overrides it for template development.

Route by intent

The standard lifecycle (at a glance)

1. CommonProject  →  mise run init-project        # repo skeleton + Plane board + .project.json + BMAD
2. pj hermes-agent --yes                          # one PM, real profile, repo board
   └─ sentinel duties ride the PM heartbeat timer (no separate scrum-master)
3. mise trust && direnv-style `enter`             # links AGENTS.md, op-injects .env.op → .env

Cross-cutting rules

• AGENTS.md is the source of truth; CLAUDE.md and GEMINI.md are symlinks to it.
• Secrets live in .env.op (1Password references); mise enter runs op inject -i .env.op > .env. Never commit .env.
• Client-specific roots such as .claude/ and .codex/ are generated local projections, not canonical project state. Never add repo unignore rules for them; edit .agents/ and regenerate.
• No code changes in a hermes-managed repo without an active ticket on the repo board (ALLOW_NO_TICKET=1 is the emergency bypass).
• Board creation is outward-facing — confirm before running provisioning that hits a live workspace.
• Manifest mutation is transactional: malformed .project.json aborts byte-unchanged, and one lock spans read/validate/live board check-or-create through atomic replacement.
• Seal target/nested-repo, fleet-registry, profile, and systemd state before a PM deploy; verify them directly afterward and require the rerun to converge. The full evidence contract is in agent-fleet-operations references/pm-deployment.md.

Out of Scope

• Developing pjangler itself → project-jangler.
• Generic agent-config fan-out engine (master/lock/dialect renderers) → agent-config-fanout.
• Hermes fleet-wide updates, template backfills, fleet self-checks → agent-fleet-operations.
• Plane live issue operations → project-lifecycle.
• Bloodbank event schema naming / topology → bloodbank-integration.
• General DeLoNET host conventions → delonet-conventions.
• Gitignore simplification and tracked-ignored parity → gitignore-maintenance.
• Hindsight API usage / bank routing mechanics beyond agent-hook wiring → hindsight.
• BMAD workflow execution (PRD, stories, dev-story, sprint) → the bmad-* skills/agents.