Documentation Governance
This page controls how documentation changes are reviewed. The documentation review process reads this configuration to determine whether a proposed change should be surfaced for human approval or auto-applied.
Review Policy
| Section | Base Rate | Min Rate | Current Rate | Notes |
|---|---|---|---|---|
| security/ | 100% | 100% | 100% | Always requires human review |
| development/architecture | 100% | 50% | 100% | Critical design documentation |
| development/conventions | 100% | 30% | 100% | Affects all future development |
| development/setup | 100% | 20% | 100% | |
| development/patterns | 100% | 10% | 100% | Low risk, additive content |
| product/vision | 100% | 100% | 100% | Strategic, always human-reviewed |
| product/roadmap | 100% | 50% | 100% | |
| product/user-guide | 100% | 20% | 100% | |
| releases/ | 100% | 0% | 100% | Can be fully automated over time |
| learnings/ | 100% | 0% | 100% | Low risk, additive content |
| features/ | 0% | 0% | 0% | Written directly by SDLC, no review |
Change Magnitude Modifiers
These adjust the effective review probability for a specific change.
| Change Type | Modifier | Rationale |
|---|---|---|
| Addition (new page) | -20% | New content is low risk |
| Minor modification (<10% of page) | +0% | Small tweaks |
| Moderate modification (10-30% of page) | +15% | Notable changes |
| Significant modification (>30% of page) | +30% | Substantial rewrite |
| Deletion (removing content) | +50% | Highest risk |
| Structural change (moving/renaming) | +30% | Affects navigation and links |
Effective Review Probability
effective_rate = current_rate + magnitude_modifier
if section.min_rate == 100%:
effective_rate = 100% # Always review
if effective_rate > 100%:
effective_rate = 100%
if effective_rate < 0%:
effective_rate = 0%
If a random value between 0-100 falls below the effective rate, the change is surfaced for review. Otherwise it is auto-applied.
Process
- Documentation review agent identifies a change needed based on a completed feature
- Agent calculates effective review probability from this config
- If review needed: creates an issue in the Documentation Review project with the proposed diff, rationale, and calculated probability
- If auto-approved: applies the change directly, creates a closed issue for audit trail
- Human reviews (if applicable), approves or provides feedback
- Agent applies approved changes to the wiki
Adjusting Rates
To change review rates, edit the "Current Rate" column in the Review Policy table above. Changes to this governance page itself always require human review (it's under security/ governance).
Audit
All documentation changes (whether reviewed or auto-applied) are recorded as issues in the Documentation Review project for traceability.
Last updated: 2026-04-09
Product
Development
Security & Compliance