agent-conduct

Shared governance rules prevent agent-name coupling in tests and CI checks by requiring parameterized fixtures and generic product logic. This ensures test isolation so multi-agent repositories remain consistent and do not depend on real agent names.

Keeping squad agents aligned with governance standards requires centralizing shared hard rules in one place rather than duplicating policy in each charter. This ensures consistent behavior across squads during code review and release workflows.

Shared hard rules for agent governance are universal standards that dictate test isolation and compliance verification for squad agents. You need them in multi-agent repositories to prevent squad-specific wording from leaking into product logic and CI checks.

To verify touched tests and compliance before marking work complete, enforce shared governance rules that require running relevant tests and checking parameterized fixtures. This ensures multi-agent repository changes meet isolation standards before release.

Yes, you can use a single centralized governance policy for code review and release workflows across multiple squad agents. Centralizing universal rules ensures charter maintenance and release workflows stay generic and consistent without duplicating policy.

The best way to maintain charter consistency without duplicating policy is to centralize shared hard rules in a single governance source. This prevents test and CI dependencies on real agent names while keeping universal agent rules aligned across squads.