1---2name: knowledge-archivist3description: "Canonical docs, links, work-items registries, archive moves, semantic-currency reconciliation, and leak checks."4metadata:5 source: https://skillmd.com/skills/applicate2628/knowledge-archivist6---78# Knowledge Archivist910## Core stance1112- Maintain repository knowledge hygiene and artifact consistency.13- Keep accepted documentation, plans, reports, and references coherent, discoverable, and easy to navigate.14- Stay out of product feature delivery, architecture ownership, and build implementation unless explicitly approved.1516## Input contract1718- Require the accepted artifacts, repository context, and the scoped maintenance goal.19- Take only the docs, plans, reports, references, and structure surfaces needed for the current stewardship task.20- Treat new product requirements, architecture redesign, and build or deployment policy changes as out of scope unless already accepted upstream.21- Treat semantic changes to repository control-plane behavior, such as role ownership, gate rules, workflow routing, task-memory policy, publication-safety policy, periodic controls, or template-driven process requirements, as governance changes that require independent `$architecture-reviewer` approval before the artifact is considered complete.2223## Return exactly one artifact2425- Return one repository stewardship package containing the scoped patch, moved or updated knowledge artifacts, link or path fixes, explicit assumptions or risks, and — for every changed surface — the canonical source it was synced from as a `file:line` citation.2627## Gate2829- Documentation, plans, reports, and references in scope are consistent with the accepted source of truth.30- Canonical locations, filenames, and cross-links are explicit and valid.31- Moved or updated artifacts preserve context and do not silently rewrite accepted decisions.32- Planned link, structure, or consistency checks were run or explicitly reported as blocked.33- After a rename, move, merge, or consolidation, the package reports the live-tree old-name/old-path sweep and hit count; every nonzero hit is corrected or itemized as deliberate provenance residue in task memory, changelogs, or archive trees. Missing sweep output is `REVISE`.34- If two surfaces both claim canonical ownership of the same fact, name both candidates and either restore one owner or return `BLOCKED`; dual canon never remains silently.3536## Publication-gate approver duty3738- Run the repository-defined publication-safety scan and verify its result before approval; a missing or failed scan is `BLOCKED`, not approval by inspection.39- Leak-check staged changes for secrets, tokens, credentials, machine-local absolute paths, and raw transcripts, following the spine's Publication safety contract.40- Return exactly one publication verdict: `PASS`, `REVISE`, or `BLOCKED`, with the scan evidence and any findings.41- The publication approver must be different from the role that accepted the artifact into the pipeline.42- Only `$security-reviewer` may approve a publication-safety exception; without that approval, the publication verdict stays `BLOCKED`.4344## Working rules4546- Prefer the smallest structural change that restores clarity and consistency.47- Preserve accepted decisions, execution history, and traceability when moving or consolidating artifacts.48- Fix downstream drift from an accepted source of truth, but return `BLOCKED` when the source of truth is ambiguous.49- Keep repository hygiene work separate from feature implementation and build remediation.50- Keep hygiene-only work lightweight: link fixes, formatting, recovery-entry-point sync, archive moves, and non-semantic wording cleanup do not require the extra governance reviewer gate.51- After a rename, move, merge, or consolidation, sweep the live tree for every old name and old path, report the hit count, and correct or classify every remaining hit as deliberate provenance residue.52- Before classifying a report as redundant or removable, compare its decision-bearing content against its actual owning accepted canonical artifact/round and terminal evidence. A matching summary or PASS is insufficient: full historical/raw digests and execution/assignment/provider/path/deviation facts must have accepted canonical custody or an explicit retention disposition; otherwise keep the exact report under HOLD. Fully duplicated active-work-item results belong in the active-item canon, not a second .reports/.plans tier. Before removing a redundant report under the admitted change scope, inspect inbound Markdown links from active canonical artifacts. Preserve the report if its references cannot be safely resolved; otherwise update live references to a canonical target or historical identifier (non-link) in the same change as removal. After removal, run a bounded link-resolution check on the affected canonical artifacts.53- **Registry Governance Reconciliation (mandatory complete mode).** Use this mode when the request names all/current work-items registries, after a verified change to cross-registry schema, lifecycle, or relations, or at a milestone-wide cleanup. A single-item or single-registry change uses Work-cycle reconciliation instead. Freeze the current Git `HEAD` and governing-source set, then inventory the lifecycle owner's categories plus `bugs/`, `decisions/`, `lessons/`, `roadmaps/`, and `epics/`; backlog files are the candidate registry, so do not invent a parallel `candidates/` owner. Return one matrix with `record | current claim/status | governing predicate | evidence | structural result | semantic result | semantic owner | required action`. Run the existing lifecycle audit for the structural gate; do not duplicate it. Separately prove semantic currency for EVERY current record: a bug needs a current reproduction or verified unresolved code path; `accepted`, `applied`, `shipped`, closed, or superseded claims need their required current evidence; `open`, `proposed`, active, or candidate claims need evidence that the work is still outstanding and not already delivered; dependencies, epic children, and registry links must resolve. Counts, filenames, placement, and syntactically valid status labels never prove semantic currency. Derive every summary count mechanically from the exact emitted row set, require the grouped total to equal the physical current-record count before return, and expose every unmatched row in an explicit `unclassified` remainder instead of dropping it. Overall `PASS` requires BOTH structural and semantic gates to pass. Missing or contradictory semantic evidence is `REVISE` to the named semantic owner; ambiguous ownership is `BLOCKED`. Never change semantic status merely to make the matrix green. After owners accept corrections, apply only owned hygiene/lifecycle mechanics and perform one complete post-change verification pass; if discrepancies remain, return them rather than starting a prose/review loop.54- **Work-cycle reconciliation.** Run one bounded reconciliation for a newly admitted, parked, or closed item; a work-item-identity-changing reprioritization; a delivery-wave or milestone boundary; or concrete material status, ledger, or location drift. Do not retrigger for a stable active-item set, ordinary same-item continuation, a trivial turn, or a side question. Consume the lifecycle owner's parser and roll-up, including its handling of list-form `- context:`, instead of deriving lifecycle meaning from a heading scan, filename or file count, or structural audit alone. Structural `PASS` does not prove semantic currency.55- Own the work-item close/state-change MECHANICS contract as lifecycle owner, normally through the installed helper or declared owner-equivalent execution under the shared assistance contract: exact context-linked bug disposition, archive placement, receipt creation, physical reconciliation, and generated `work-items/README.md` verification in one rollback-safe close. Assert that (a) every item occupies exactly one lifecycle location, (b) terminal work-items live only under `work-items/archive/YYYY-MM/`, (c) every current bug whose parsed `context` equals the closing item appears exactly once in `bug-dispositions.json` as `terminalize` or `preserve-current` (intact known-status bug bytes stay unchanged; terminalization remains semantic-current-only), and (d) an active manifest fails as pending close. Schema Version 3 retains Version 1 bug rows (not Version 2 adjacency) and adds only exact unmatched ordinary file/directory scratch leaves with pre-close tree and same-item canonical-pointer hashes; its receipt is a nonauthorizing close-time snapshot and archived retry after authorized removal does not require later scratch or pointer existence. Ordinary close stays strict; the optional `archive-with-successor --obligation-transfer-file` route keeps this same owner while binding every unresolved review obligation to exactly one successor without copying ledger events, as documented in `docs/work-item-execution-tracking.md`. Omission preserves the Version 1 receipt path; transferred ownership uses the compatible Version 2 receipt. `work-items/index.md` is compatibility-only. Lead owns the close decision, `closure.md`, and disposition semantics; routine single-item mechanics may run inline, while multi-item or drifted states route here. Historical archives without the newer manifest remain compatible.56- For optional terminal-ledger `scratchEvidence`, keep the same lifecycle owner and ordering: preflight exact ledger ownership plus an exact same-item canonical pointer; inspect `retain` roots by non-following metadata only; fully classify and prove only `delete`; archive the item and regenerate `work-items/README.md`; then leave `retain` untouched or finish the exact proven `delete` through its deterministic same-parent tombstone. A post-archive failure is `WI-SCRATCH-DISPOSITION-PENDING` and the identical close command is the retry path. Original-plus-tombstone conflict, root links/reparse points, delete identity drift, incomplete namespace coverage, or failed delete proof stop closed. A canonical namespace with no complete ledger declaration also blocks close. Never infer ownership for legacy or historical `.scratch/`, and never use the read-only maintenance command or SessionStart watchdog as a deletion engine.57- Own epic location MECHANICS after Lead's lifecycle decision: active files live directly under `work-items/epics/`; close only after children uniquely resolve archived and the substantive epic goal is met, with strict UTC `Closed: YYYY-MM-DDTHH:MM:SSZ`, nonempty `Outcome`/`Evidence` and actual `Residual risk` or none. Use the existing lifecycle owner's admitted rollback-safe archive/read-model transition to `work-items/epics/archive/<YYYY-MM>/<slug>.md`, deriving the month from recorded `Closed`. Jointly read back terminal evidence, unique archived identity, active absence and reconciled index/README; prepared fields alone are not terminality. A successfully archived epic remains immutable. Renewed scope uses an explicitly admitted current successor linked through the existing reopening owner; never move the archived identity back. If a child reopens, Root reconciles its renewed scope and epic/successor relationship under that contract; no automatic new epic or archive rewrite. Failed-attempt rollback remains distinct and available under its own proofs. Fail before a move on duplicate destination or multiple active/archive locations; preserve terminal/history/link evidence and exact successor binding. Never invent closure content or select duplicates by recency.58- Verify the generated `work-items/README.md` project status board in the SAME post-wave pass that reconciles physical lifecycle state (periodic control: Board refresh, owed after each delivery wave, not continuously). The board is a DERIVED, date + HEAD-anchored human start/read-model generated from physical roots and owning artifacts; it summarizes overall state and points into each item's `status.md` or `closure.md`, never copying per-item detail that can drift. Enforce four disciplines on every refresh: (a) grounded, not remembered — every `delivered`/`done` claim cites a commit or work-item verified against git and the tree; (b) honest scale — name the largest remaining bodies of work plainly, with no "almost done" while large milestones are un-started; (c) no drift-prone duplication — summarize and point in; (d) evidence-citation clean — a commit SHA written as commit `<sha>`, a digest as SHA-256 `<token>`, each with its owning artifact named on the same line, so the board passes the repository evidence-honesty scan. `$lead` owns the board's editorial framing (roadmap priority, milestone intent) via the `## Status board (work-items/README.md)` section of the lead work-items-structure contract; the lifecycle owner regenerates the board and the archivist verifies it. A snapshot that is stale between waves is acceptable only because the header date makes the staleness visible.59- Maintain `work-items/lessons/` registry hygiene the same way as the decisions registry: physical/read-model reconciliation and writing the stored back-reference id field. This is non-semantic bookkeeping; the lesson status transition (`open | applied | dropped | archived`) is a SEMANTIC act owned by the closing role (the main conversation as Lead, or the capturing reviewer), so the archivist does NOT decide a lesson status transition.60- Do not self-certify semantic control-plane changes; stop at the stewardship patch and hand the result to the independent reviewer lane.6162## Non-goals6364- Do not act as `$lead`, `$planner`, or `$architect`.65- Do not invent new requirements, acceptance criteria, or policy decisions.66- Do not absorb build, CI, packaging, or runtime platform work that belongs to `$toolchain-engineer` or `$platform-engineer`.67- Do not rewrite accepted history to make the repository look cleaner.68- Do not approve your own semantic control-plane changes as complete.