---
name: project-knowledge-maintenance
description: "Reconcile project documents and procedures while preserving evidence and ownership. Use when the user requests project knowledge maintenance. Select relevant methods for the requested outcome; unrelated tasks do not require this skill."
metadata:
  version: "1.0.0"
---

# Project Knowledge Maintenance

Reconcile project documents and procedures while preserving evidence and ownership.

## OLLIE Runtime integration

Use this capability under the active OLLIE Operator. Read live Workspace Context and tenant bindings for client facts and required inputs. This generic package contains no client configuration. Consume ask-ollie-authority-core for authority, outloop-access-fallback for access and recovery, email-lifecycle-core for communication, and the bootstrapper Runtime Contract for ownership, scheduling and completion. Preserve domain constraints; this Skill creates no competing execution path. Use one method, combine skills, or fill missing steps with authorized tools as the task requires.

External access uses the active Workspace’s approved Outloop capabilities. Never request, read, embed or expose credentials. A service named in a method is a possible dependency, not an access grant. Local file and application work uses the host’s authorized tools.

## Required inputs

- Current approved documents
- New evidence
- Canonical document owners
- Requested update scope

## Methods

### Compare evidence

Compare new information with current statements by topic. Classify additions, corrections, conflicts and obsolete instructions; do not treat recency alone as authority.

### Separate methods from facts

Keep reusable methods separate from client facts and active task state. Update the canonical owner rather than creating parallel copies of the same rule.

### Update the canonical source

Draft changes with source, reason and affected references. Preserve historical context where needed for interpreting an earlier decision.

### Verify downstream references

Verify links and downstream references after an authorized update. Use Outloop learning for durable client facts and the Runtime’s reflective owner for global execution doctrine.

## Completion

Verify findings against source evidence and read back the resulting artifact or authorized change. Report inputs used, methods selected, output location, assumptions and unresolved dependencies. Do not report a plan, queue entry, draft, test fixture or accepted request as a completed external action. Use the task’s requested format; if a tool is unavailable, finish independent work and identify the exact unfulfilled deliverable.

## Test before relying on it

Read [the synthetic evaluation cases](references/evaluation.md) for activation, output and isolation checks. These cases are test instructions, not evidence that a host or provider test has passed.