claudiomaradonna/castrum
1
0
Fork 0
Code Pull requests Activity

docs/readopt-agent-foundry-b67b136 #15

Merged
claudiomaradonna merged 2 commits from docs/readopt-agent-foundry-b67b136 into main 2026-09-29 19:26:08 +02:00
Conversation 0 Commits 2 Files changed 4 +67 -53
claudiomaradonna commented 2026-09-29 19:25:39 +02:00
Owner
Copy link

Why

castrum's agent policy credited agent-foundry a30376d, three commits
behind the source. Upstream now asks the user before any memory write,
moves every change onto its own branch in a worktree with an explicit
end-of-work choice, and adopts a full Conventional Commits rule. Comparing
the two files also turned up castrum rules that had gone stale or that
restate a rule stated elsewhere.

What changed

  • Memory writes need approval: the curator first proposes each record
    with its Memory-ID, action and full body, and writes only what the user
    approves (AGENTS.md, docs/LOCALRECALL.md).
  • Every change happens on a branch in .worktrees/<branch>, created from
    main, and ends with a choice to push, merge linearly, or leave the branch
    (AGENTS.md, the write-plan skill).
  • Upstream's Conventional Commits rule replaces castrum's shorter line; the
    lowercase-subject convention stays in CONTRIBUTING.md#commits.
  • Removed as stale or duplicated: the Local inference (LocalAI) section,
    which upstream dropped in 7afc526; the dependency-approval clause
    already in Engineering and security; the tenant note already in Project.
  • The Commands section links to CONTRIBUTING.md for the CI-runner note,
    the sandbox venv setup and the lint policy instead of restating them,
    and keeps the agent-only rule on reporting which gates ran.

Every vendored file (skills, both curator adapters, docs/LOCALRECALL.md,
.claude/settings.json) is byte-identical to the source; the README credit
reads 7e46402. No playbook or role changes.

## Why castrum's agent policy credited agent-foundry `a30376d`, three commits behind the source. Upstream now asks the user before any memory write, moves every change onto its own branch in a worktree with an explicit end-of-work choice, and adopts a full Conventional Commits rule. Comparing the two files also turned up castrum rules that had gone stale or that restate a rule stated elsewhere. ## What changed - Memory writes need approval: the curator first proposes each record with its `Memory-ID`, action and full body, and writes only what the user approves (`AGENTS.md`, `docs/LOCALRECALL.md`). - Every change happens on a branch in `.worktrees/<branch>`, created from main, and ends with a choice to push, merge linearly, or leave the branch (`AGENTS.md`, the `write-plan` skill). - Upstream's Conventional Commits rule replaces castrum's shorter line; the lowercase-subject convention stays in `CONTRIBUTING.md#commits`. - Removed as stale or duplicated: the Local inference (LocalAI) section, which upstream dropped in `7afc526`; the dependency-approval clause already in Engineering and security; the tenant note already in Project. - The Commands section links to `CONTRIBUTING.md` for the CI-runner note, the sandbox venv setup and the lint policy instead of restating them, and keeps the agent-only rule on reporting which gates ran. Every vendored file (skills, both curator adapters, `docs/LOCALRECALL.md`, `.claude/settings.json`) is byte-identical to the source; the README credit reads `7e46402`. No playbook or role changes. 
Ask the user before any memory write (the curator proposes, then writes
only approved records), work on a branch in .worktrees/<branch> and end
with a push, merge or leave choice, and take upstream's Conventional
Commits rule in place of castrum's own line.

Drop castrum rules that went stale or restate upstream: the LocalAI
section upstream removed in 7afc526, the approval clause that
Engineering and security already states, and the tenant note that
Project already carries.
The CI-runner note, the sandbox venv setup and the lint policy each have
a home in CONTRIBUTING.md; AGENTS.md now links to them and keeps only
the agent-only rule on reporting which gates ran.
claudiomaradonna deleted branch docs/readopt-agent-foundry-b67b136 2026-09-29 19:26:12 +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!15
No description provided.