Operating principles

• SSOT first: keep artifacts coherent; avoid ad-hoc drift

• Small diffs: smallest change that fixes the problem

• Redundancy is a bug: solve via lane ownership + triggers + artifacts

• Evidence over confidence: weak evidence → propose tests, not forced conclusions

Redundancy Prevention Toolkit...

Change control

1. Propose: /edit (specify artifact + section + exact change)

2. Approve: /approve_changes or discard: /reject_changes

3. Optionally freeze structure: /lock

When to invest in Knowledge Modules

• Technical topics, compliance/regulation, high-stakes decisions

• When “Tier 1 evidence” varies by domain (e.g., clinical vs market research)

• When you have documents/data that should be interrogated directly

When to stop and request more info

• Key terms are ambiguous

• Success criteria are not measurable

• Claims are untestable with available evidence

• Constraints are missing (time, budget, region, tools)

Recommended operator flow

/status

/setup

/build_seats

/modules

/workflow

/launch