📄️ Contract profiles and promotion ladder
Authority note: this page now governs knowledge interoperability profiles only. Operational evidence such as run records, bundle manifests, lifecycle status, retries, and environment capture remains producer-owned pending a separate operational-evidence authority. See ADR-0006.
📄️ Knowledge contract compatibility
This page explains the compatibility rules enforced by kb-interop.v1-rc1. The machine-readable fixtures and release inventory are authoritative; this page is the human guide.
📄️ Stable IDs and naming rules
Authority classification: the universal derivation and hash guidance on this page is legacy shared guidance and a possible producer-local reference, not a required algorithm in KB interoperability v1. The normative v1 shared rule is explicit reference preservation below. Producer-owned versioned contracts retain authority over source, record, artifact, and fallback-hash derivation. See ADR-0006.
📄️ Manifests and integrity rules
Authority classification: artifact-level identity, portable provenance, finalized payload bytes, and checksum rules are normative knowledge-interoperability concerns. Run lifecycle, staging implementation, atomic promotion mechanics, retries, rollback, and operational status history are legacy shared guidance / deferred operational extraction, not requirements of the machine-readable KB interoperability release. See ADR-0006.
📄️ Run records (operational guidance)
Authority classification: candidate operational contract / legacy shared guidance. This page does not define a normative schema in the KB knowledge-interoperability release. Producer repositories retain their current run-record shapes until a separate operational-evidence authority is approved. Knowledge contracts may carry opaque runid or runrecord_ref values without importing this shape. See ADR-0006.
📄️ Error taxonomy (operational guidance)
Authority classification: candidate operational contract / legacy shared guidance. These classifications and stop rules remain useful pipeline guidance, but they are not universal requirements of the KB knowledge-interoperability release. Producers retain local operational error and lifecycle contracts pending a separate operational-evidence authority. See ADR-0006.
📄️ Observability indexes (operational guidance)
Classification: candidate operational contract / legacy shared guidance. Observability indexes, UI run status, and rebuild operations are outside kb-interop.v1-rc1. Producers may retain these shapes locally; Knowledge Profile 1 does not require them.