33god-projects

name	33god-projects
description	Create, wire, and maintain 33god/DeLoNET projects. Covers pjangler/CommonProject bootstrap, repo-local `.project.json`, Hermes PM and scrum-master/Ticket Sentinel provisioning requests, mise/.env.op, BMAD, Hindsight/Bloodbank hook wiring, and project-scoped hook + skill fan-out adoption. Use when running `pjangler init`, `pjangler hermes-agent`, or `mise run init-project`; adding PM/sentinel agents; 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 (pjangler-dev), generic fan-out mechanics (agent-config-fanout), fleet updates/backfills (hermes-fleet-operations), live Plane issues, Bloodbank schemas, or host conventions.
pipeline-status	["new"]

33god Project Creation & Wiring

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

• CommonProject (templates/commonproject) — the base skeleton: .project.json, mise.toml, .mise/scripts/, BMAD, the ticket board.
• hermes-agent-template (templates/hermes-agent) — Hermes agent roles (PM, scrum-master/Ticket Sentinel, dev, …) provisioned into agents/hermes/<role>/.

.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. Never reintroduce a separate .plane.json.
• One board per repo. The PM owns it; the Scrum Master sentinel watches the same board. Board name = the project name (no role suffix); identifier = slug[:4] uppercased.
• Agent config is inherited by default for new fleet agents. pjangler creates ~/.hermes/profiles/<repo>-<role> as a named profile that points at the role's agents/hermes/<role>/runtime/ repo and opts config.yaml into inheriting from the fleet default profile. Local agent config.yaml files contain only overrides.
• mise is mandatory and uniform. Every repo gets the same mise.toml contract.
• Agents are memory- and event-wired by default. Hindsight recall/retain + Bloodbank emit/consume are part of provisioning.
• 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 set and lets mise enter/leave install them into each dev's CLIs (see references/project-scoped-hooks.md).
• Templates are version-locked. pjangler runs the vendored submodule unless PJANGLER_HERMES_TEMPLATE overrides it for template development.

Route by intent

You want to…	Read
Create a new project / bootstrap CommonProject / add a PM or Ticket Sentinel	references/project-creation.md
Set up or fix mise (mise.toml, .mise/scripts, AGENTS.md linking, op inject .env.op)	references/mise-conventions.md
Install / re-install BMAD with the standard modules + tools	references/bmad-init.md
Wire an agent's Hindsight memory and Bloodbank emit/consume hooks (harness/global layer)	references/agent-hooks.md
Adopt the per-dev, committed project-scoped hook + skill fan-out layer (Claude/Codex/Hermes/Kimi, .agents/local.json opt-out, hindsight-setup)	references/project-scoped-hooks.md → references/project-scoped-internals.md
Understand what the project side asks Hermes to provision	references/hermes-project-agent-request.md
Update shared Hermes fleet defaults, run a fleet self-check, or backfill existing PM agents	→ hermes-fleet-operations
Build or operate the generic master→multi-dialect fan-out engine	→ agent-config-fanout
Develop pjangler itself (Commands/Recipes/MCP)	→ pjangler-dev

The standard lifecycle (at a glance)

1. CommonProject  →  mise run init-project        # repo skeleton + Plane board + .project.json + BMAD
2. pjangler hermes-agent (role: pm, +companion)   # PM agent, inherited profile, repo board
   └─ companion provisions the scrum-master (Ticket Sentinel) on the SAME board
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.
• 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.

Out of Scope

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