aibdd-activity-granularity-rule-docs

To write Activity granularity rules without SOP drift, produce declarative invariant entries using testable “can/must/must not” statements, strictly separating decision rules from operational READ/WRITE/LOAD/DERIVE execution logic.

Granularity decision rules in BDD workflow governance are boundary-aware invariants for Actor and Step/Action granularity that define what is allowed, forbidden, or required, preventing conflicting instructions for downstream agents.

To split granularity rules from discovery content, extract only declarative invariants into a dedicated rule markdown file, ensuring upstream trace narratives and operational instructions remain outside the rule boundary.

Include counterexamples in granularity rule files only when a plausible violation exists, adding a tightly scoped # 反例 section with an optional expected compliant shape sentence to clarify the judgment boundary.

No, you must keep READ/WRITE/LOAD/DERIVE and other operational instructions out of Actor granularity rule files to ensure execution logic stays in SOP and downstream agents receive unambiguous decision rules.

To enforce spec quality for Activity boundary changes, update or split the granularity rule markdown files by providing declarative invariants and optional counterexamples, ensuring no SOP-like execution procedures are embedded.