agent-conduct

You can enforce governance rules across multiple agents by applying centralized hard rules during charter creation and code reviews, which prevents charter drift and ensures consistent behavior. This validates no agent-name dependencies exist.

Hard rules in squad agent governance are universal compliance checks like the Product Isolation Rule and Peer Quality Check. You need them when managing multiple agents to prevent hard-coded references and ensure consistent peer reviews.

To prevent hard-coded agent name references in CI pipelines and tests, implement automated validation checks that scan configurations and product code. This ensures no agent-name dependencies exist before merging.

Yes, you can use centralized governance checks for peer reviews across different squads. The rules apply universally across any squad context to support consistent compliance checks and prevent duplicated governance logic.

To apply the Product Isolation Rule during charter development, load the governance rules into the squad context and reference them. This implements the rule as a guardrail alongside the Peer Quality Check.