knowledge-base-operations-method

# Source-grounded knowledge lifecycle method Freeze the knowledge operation: add, update, deprecate, or replace; exact source set and versions; target knowledge space; stable destination key; audience; owner; effective date; review cadence; existing canonical entry; and publication authority. A chat summary, search snippet, or unversioned recollection is not a source. ## Parallel specialist work Run three independent views from the same source and destination scope: 1. Source curation records source identity, authority, version, date, supported claims, conflicts, limitations, and the exact destination section for each accepted claim. 2. Change editing prepares the canonical knowledge content, stable heading or record keys, material diff from the prior entry, link and dependency impacts, and unresolved editorial questions. 3. Lifecycle governance defines owner, status, effective and review dates, freshness signals, supersession relationships, deprecation notice, redirect or replacement target, archive retention, approvers, and publication conditions. The join verifies that every material published claim maps to accepted source evidence and every changed or deprecated entry has an explicit destination and lifecycle state. Conflicting sources, stale evidence, missing owner, absent replacement, and unapproved publication remain visible. ## Publication boundary Publishing means creating the canonical prepared Artifact and its release record. Do not write to an external wiki, delete old content, change redirects, notify users, or claim organizational approval unless an authorized tool and approval evidence are present. Deprecation preserves history and points to a replacement or a documented no-replacement reason.