multi-artifact-governance-principle-embedding

Context

When embedding a critical governance principle (like plain-language-first or jargon-early detection), do not rely on a single artifact or checklist. Instead, embed the principle into multiple complementary artifacts so that even if one gets skipped, outdated, or misunderstood, the principle survives in the others.

Iteration 001 (feature 007) discovered this pattern when codifying the governance-acronym detection rule (three-or-more governance acronyms in lead without plain-language paraphrase). The rule was embedded in:

1. Coordinator prompt (T001): Plain-language guardrail + examples showing how to lead with human terms
2. Handoff template (T002): Concrete copy-paste patterns demonstrating plain-language-first structure
3. Governance checklist (T005): Soft-warning check operationalizing the detection rule
4. Soft-validator design (T006): Pseudo-code and algorithmic definition of the detection logic

This four-artifact redundancy ensures that:

• Agents reading only the prompt get the guardrail and examples
• Reviewers reading only the template see validated patterns
• Governance reviewers reading only the checklist get the detection rule
• Implementers reading only the validator design get the algorithmic definition

No single document path leads to the principle being skipped.

Patterns

• Map the principle to its owners. Identify which roles (agents, reviewers, implementers, governance) interact with the principle. Embed guidance in artifacts those roles naturally read.
• Separate implementation guidance from detection rules. Agents need to understand "how to do it" (prompt + template). Governance tools need to understand "how to detect violations" (checklist + validator). Both groups benefit from the same principle but consume different artifact forms.
• Use redundancy strategically. Don't duplicate word-for-word. Instead, express the principle at different levels of abstraction:
  • Prompt: Plain human guidance with examples ("Do not open with three or more acronyms without first explaining them")
  • Template: Concrete copy-paste patterns showing compliant and non-compliant forms
  • Checklist: Operationalized check ("Count governance acronyms in lead. If ≥3 and no paraphrase, flag as soft warning")
  • Validator design: Algorithmic definition with pseudo-code and edge cases
• Verify coverage before governance publication. Before closing an iteration, search for the principle across all artifacts. Verify it appears in at least 2-3 independent artifact types. Single-artifact principles are fragile.
• Document the multi-artifact strategy in the feature spec or plan. Make explicit that "this principle is embedded in X, Y, Z artifacts" so future maintainers know which documents to update if the principle needs refinement.