claudiomaradonna/castrum
1
0
Fork 0
Code Issues Pull requests Activity

fix(agents): keep castrum's rules in Project rules #40

Merged
claudiomaradonna merged 1 commit from fix/project-rules-placement into main 2026-10-17 14:56:03 +02:00
Conversation 0 Commits 1 Files changed 1 +8 -8
motoko commented 2026-10-17 14:08:37 +02:00
Collaborator
Copy link

Why

AGENTS.md's documentation rule listed the documents that own
behaviour and procedures, and missed docs/MIGRATION-AI-STACK.md, which
CONTRIBUTING's table assigns the AI-stack cutover. castrum's own rules
also sat inside sections that come from Agent Foundry, mixed with the
vendored policy.

What changed

  • An agent updating a behaviour or procedure is sent to CONTRIBUTING's
    owner table, the one list, so every owning document is covered.
  • castrum's documentation and agent-sandbox rules now sit in Project
    rules, beside the Ansible conventions; Documentation and Testing and
    verification match Agent Foundry again, so later upgrades merge them
    cleanly.

Non-goals: no rule is reworded; the sandbox rule moves word for word,
and the Ansible conventions are untouched.

How to verify

  • Read AGENTS.md § Project rules: the two rules sit before the
    Ansible conventions, and the documentation rule links
    CONTRIBUTING.md#where-documentation-lives.
  • git diff main shows Documentation's first bullet and Testing and
    verification back to Agent Foundry's text.

Run: a check comparing the shared sections with Agent Foundry 4545b66
and the documentation rule with CONTRIBUTING's table (fails on main,
passes here), the Agent Foundry validator, and make check (exit 0).
Not run: make test and make verify, as the sandbox has no podman.

Considerations

Placing the documentation rule in Project rules departs, by choice, from
that subsection's definition, which keeps a change to one of the file's
rules with that rule.

## Why `AGENTS.md`'s documentation rule listed the documents that own behaviour and procedures, and missed `docs/MIGRATION-AI-STACK.md`, which CONTRIBUTING's table assigns the AI-stack cutover. castrum's own rules also sat inside sections that come from Agent Foundry, mixed with the vendored policy. ## What changed - An agent updating a behaviour or procedure is sent to CONTRIBUTING's owner table, the one list, so every owning document is covered. - castrum's documentation and agent-sandbox rules now sit in Project rules, beside the Ansible conventions; Documentation and Testing and verification match Agent Foundry again, so later upgrades merge them cleanly. Non-goals: no rule is reworded; the sandbox rule moves word for word, and the Ansible conventions are untouched. ## How to verify - Read `AGENTS.md` § Project rules: the two rules sit before the Ansible conventions, and the documentation rule links `CONTRIBUTING.md#where-documentation-lives`. - `git diff main` shows Documentation's first bullet and Testing and verification back to Agent Foundry's text. Run: a check comparing the shared sections with Agent Foundry 4545b66 and the documentation rule with CONTRIBUTING's table (fails on main, passes here), the Agent Foundry validator, and `make check` (exit 0). Not run: `make test` and `make verify`, as the sandbox has no podman. ## Considerations Placing the documentation rule in Project rules departs, by choice, from that subsection's definition, which keeps a change to one of the file's rules with that rule. 
The documentation rule listed owning documents and missed
docs/MIGRATION-AI-STACK.md, which CONTRIBUTING's table assigns the
AI-stack cutover. It now links that table as the one list.

castrum's documentation and agent-sandbox rules move into Project
rules, and Documentation and Testing and verification take back Agent
Foundry's text, so the project's own rules sit in one section and
later upgrades merge those sections cleanly. Placing the documentation
rule there departs, by the user's choice, from the Project rules
definition's "a change to one of this file's rules stays with that
rule".
claudiomaradonna deleted branch fix/project-rules-placement 2026-10-17 14:56:24 +02:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
claudiomaradonna/castrum!40
No description provided.