Create a Knowledge-Base Maintenance Plan

#CONTEXT:
Create a reviewable knowledge-base maintenance plan from the supplied inventory and governance facts. Propose controls; do not schedule work or change any source or system.

#INPUTS:
- Current knowledge-source inventory with source references: [KNOWLEDGE SOURCE INVENTORY]
- Approved maintenance roles and responsibilities: [MAINTENANCE ROLES]
- Documented source owners and stewards: [SOURCE OWNERS]
- Sensitivity labels or classifications: [SENSITIVITY]
- Supplied authority and approval rights: [AUTHORITY]
- Last-reviewed dates and supporting evidence: [LAST-REVIEWED DATES]
- Required change-control, versioning, review, and retirement controls: [CHANGE-CONTROL REQUIREMENTS]

#INSTRUCTIONS:
1. Preserve source attribution and state an evidence status for every ownership, authority, freshness, and cadence input.
2. Do not invent, infer, or fabricate rules, owners, authority, dates, facts, sources, approvals, or review frequency.
3. Propose a cadence only when supported by supplied policy, risk tier, or owner instruction. Otherwise mark the cadence Unknown and request a named-human decision.
4. Build an owner, cadence, and change-control plan covering intake, review, approval, versioning, conflict escalation, access review, retirement review, and audit evidence.
5. Keep conflicting ownership, authority, or source rules in an Unresolved conflict state. Do not choose a winner or declare a source authoritative without documented supplied authority.
6. Add event-driven review triggers for supplied business changes, incidents, repeated unanswered questions, and owner transitions. Label unsupported triggers as proposals.
7. Define evidence of completion and a review scorecard. Do not schedule reviews, notify owners, publish changes, archive records, or edit live systems.
8. Maintain source attribution for every fact, rule, owner, authority claim, and date.
9. For each item, state its evidence status: Verified, Reported, Unknown, or Unresolved conflict.
10. Do not invent, infer, or fabricate rules, owners, authority, dates, facts, sources, or approvals.
11. Do not choose a winner or declare a source authoritative without documented supplied authority.
12. Use only authorized knowledge data in an approved AI workspace or approved AI vendor. Minimize the data; redact or omit unnecessary personal, sensitive, or confidential data. Preserve each sensitivity label or sensitivity classification and follow company retention and vendor policy.
13. Do not publish. Do not update a canonical source. Do not grant, revoke, or change access or permissions. Do not send material externally. Do not change a live system.
14. A named human owner must approve publication before action. A named human owner must approve every canonical-source update before action. A named human owner must approve every access or permission change before action. A named human owner must approve every external action or live system change before action. A named human owner must approve every policy exception before action.

#RESPONSE FORMAT:
## Source attribution and evidence status
| Source | Owner | Authority | Sensitivity | Last reviewed | Evidence status |
|---|---|---|---|---|---|

## Owner, cadence, and change-control plan
| Source or domain | Named owner | Proposed cadence | Evidence basis | Change-control steps | Completion evidence |
|---|---|---|---|---|---|

## Event-driven review triggers
| Trigger | Affected source | Proposed reviewer | Approval boundary |
|---|---|---|---|

## Unknowns and Unresolved conflicts
| Item | Evidence gap or conflict | Named decision owner | Stop condition |
|---|---|---|---|

## Human approval checklist