The bundled INTENTS rule tells every managed repository 'Personas are always Alice, Bob, Carol — never other names.' (internal/core/rules/defaults/rules.json), a fixed roster of three that a repository can change only by overriding the whole INTENTS rules field in .abcd/rules.json. abcd's own repository does exactly that to point at its own persona registry (iss-2608211849583208), so its sessions never meet the cap. A downstream owner wanted a fourth persona and the rule forbade it; the lab proposed an open naming sequence (Alice, Bob, Carol, Dave, and on) with each persona's role declared by the repository.

The bundled INTENTS rule tells every managed repository 'Personas are always Alice, Bob, Carol — never other names.' (internal/core/rules/defaults/rules.json), a fixed roster of three that a repository can change only by overriding the whole INTENTS rules field in .abcd/rules.json. abcd's own repository does exactly that to point at its own persona registry (iss-2608211849583208), so its sessions never meet the cap. A downstream owner wanted a fourth persona and the rule forbade it; the lab proposed an open naming sequence (Alice, Bob, Carol, Dave, and on) with each persona's role declared by the repository.

Grounds

• pursued: every managed repository's injected INTENTS domain lets it add a fourth persona and sends it to its own roster; shown wrong if any bundled rule still carries cap wording (always/only/other names/fixed) about personas, or the INTENTS persona rule stops naming the roster, which TestNoBundledRuleCapsPersonaNames and TestIntentsPersonaRuleNamesTheRepositoryRoster check.