mountain-nomad-bc/pacify-x/govern-knowledge-refinery

Govern Knowledge Refinery

1. Inventory the full source with portable relative paths, byte/hash bounds, rejected symlinks, and redacted secret finding codes. Use the existing non-extracting archive inventory before any archive extraction.
2. Treat license detection as evidence requiring review, never as an automatic legal decision.
3. Extract candidates into existing PACIFY-X artifact/task/capability contracts. Record malformed structured inputs separately; do not silently downgrade them to generic text.
4. Compare identifiers, aliases, structured fields, mechanisms, inputs/outputs, failure modes, invariants, conflicts, negative applicability, evidence, validation, and graph neighborhood.
5. Assign exactly one of DUPLICATE, ENRICH, VARIANT, CONFLICT, SUPERSEDE, NOVEL, or REVIEW to each candidate. Abstain to REVIEW for close targets or insufficient confidence.
6. Produce exactly one merge action per decision. Merge plans are proposals and perform no canonical writes.
7. Audit graph endpoints, duplicate/self edges, provenance state, dependencies, supersession cycles, orphans, and suggested-edge review state.
8. Reuse canonical capability routing for retrieval simulation, dependency closure, negative matches, authority, safety, budgets, and deterministic tie-breaking.
9. Calibrate only on separated train and holdout corpora. Reject weight proposals that degrade holdout objectives or forbidden-hit controls.
10. Stage an approved, hash-bound proposal inside the commissioned project. Canonical apply remains the isolated project control-plane and release-gate responsibility.
11. Preserve all source, plan, review, graph-diff, test, and rollback evidence. Never hard-delete.

Read runtime contract before admitting, classifying, calibrating, or staging knowledge.