Architecture

Rules geography: shared reference clone, personal overlay fork, harness always-on slot, skill discovery junctions, machine files, and project AGENTS.md

Illustrated walkthrough: Harness-neutral architecture (layered deltas, rules-manager when the harness cannot stack).

  • agent-rules — portable rules + org layer (AGENTS.md, agents/, team skills) in the live team clone $AGENT_RULES_PATH

  • Personal overlay fork (optional) — profiles, personal tweaks, personal-only skills; not a HEAD-parity mirror of the template

  • devcentr-agent-rules — rules for when the Dev-Centr app acts on behalf of the user

  • harness.md — harness config on this user’s machine (discovery paths, chat behaviors)

  • machine.md — workstation facts; gitignored; never committed

On dev-centr/* work, org layer overrides personal portable rules where they conflict. See Org layer.

House org init (skill bootstrap-org, not a universal GitHub practice): satellite {org}/agent-rules repos are pointer overlays (AGENTS.md only). They must not git-submodule this tree. Shared updates: git pull in $AGENT_RULES_PATH clone — no wrapper repo changes required unless org policy differs.