Every Repository. One Standard.
Claudia keeps intent, dependencies, and decisions coherent across the repositories you own — the same practice, the same responsibility contract, and one scheduled Hermes manager for each.
What never varies
One Standard, Every Repository
Add a repository and it inherits the released practice — not a fresh negotiation each time. It keeps its own product, code, work, and knowledge.
One Practice, Every Repository
The same independent skills and the same delivery practice reach every managed repository through a verified exact release. A repository binds them to its own paths, commands, and preferences; it does not rewrite them.
One Responsibility Contract
The same human-owned floors, the same manager authority, and the same worker boundary apply everywhere. Repository preferences can delegate production release explicitly; they cannot lower a floor.
One Admission Rule
New unattended implementation starts only from an issue the owner has groomed and labelled ready. Attended work needs no such gate.
One Scheduled Manager per Repository
Hermes runs one scheduled repository manager job for each configured repository. Cadence, execution limits, and recovery are native to the runtime; the manager practice is Claudia’s.
One Record
Pull requests, issues, checks, review, merge, and closure live in each repository’s GitHub. Claudia reads across them for portfolio synthesis and never copies them into a second tracker.
One Knowledge Practice
Every repository carries its own brain/ corpus. Managers search it before deciding and write back what changed. Claudia keeps only the durable cross-repository facts that have no better home.
Who owns what
Responsibility, from the Assignment Up
A worker returns evidence. A repository manager finishes the objective. Claudia keeps the portfolio coherent. You keep the decisions that matter. A decision request names the choice, the evidence, and the consequence, and unrelated work continues.
Worker
Bounded assignmentA subagent, delegated builder or reviewer, or delegated Work session with a bounded assignment. Inspects, implements, tests, or reviews the assigned surface. May create or update the branch and pull request when its assignment includes that. Returns the head, evidence, findings, and decision needs to its manager.
Never merges, and never becomes the manager through a credential, tool, or session resume.
Repository manager
Attended or scheduledOwns one authorized objective from intake to native merge. Reads current GitHub, code, and knowledge before acting. Implements directly or delegates bounded work. Chooses checks and review depth from the actual risk. Confirms the exact head against the current base, then merges.
A human-started top-level task in Claude Code, Codex, or Cursor, or the repository’s one scheduled manager. Authoring the change does not demote it.
Claudia Orchestrator
Across repositoriesKeeps intent coherent across every repository you own. Cross-repository priorities, dependencies, and allocation. Reusable skills, preferences, and durable portfolio knowledge. Steers each repository manager with a bounded objective and links.
Does not copy repository work into a second tracker and does not decide product direction alone.
Human Operator
Consequential decisionsSets direction, decides what is ready, and keeps the consequential decisions. Product and portfolio direction. Grooms an issue and applies the ready label before unattended work starts. Answers decision requests in Slack or GitHub.
Direction, shared architecture, secrets, destructive action, production, spend, security floors, and public commitments never move to an agent.
One View Across the Whole Portfolio
Claudia reads across every repository’s GitHub and brain, synthesizes priorities and dependencies, and steers each repository manager with a bounded objective — inside the direction you have already set. Direction changes come back to you. See the contract it stands on.
Ready to Run Your Whole Portfolio?
One standard. Every repository. You stay in charge.