3.1 KiB
Emergent knowledge distribution and maintenance agreement — draft
Knowledge 0.2.1; package digest d8ef41bacd2c6551ae3b87628004a5df6943928be1c93eb01e09efc6ad782767; emergent-security commit f9cba6fb35425f74e34401b1baf09f6057ace493. Prepared 2026-10-03 by delegated Codex worker for EMERGENT-WP-0002 T09 and CUST-WP-0073 T04. This is a concrete proposal, not owner/human assent or a published fleet notice. No supervision record is inherited or promoted.
Emergent-security maintains and seals the package and its source manifest. Each named source owner maintains its contract and resolves withdrawn or conflicting guidance; a source-file check proves no service health. Gate-house and net-kingdom settle doctrine/publication placement; Access Engine settles PDP mappings. Glas owns native session delivery and proof, while the Custodian coordinates reach through existing standing notices after acceptance.
The reviewed release is frozen by version, package digest and commit above. Startup, actual resume/compaction, provider switch and repository entry must reload start and the relevant journey with scope re-established. Receipts must separate exact provider/client/model/session evidence from configured pins and record unknown metadata. Native readiness and credential isolation remain in GLAS-WP-0012 and CUST-WP-0073 T02; loading does not close them.
Rollout prerequisites: recorded doctrine/publication dispositions, scoped owner reviews, actual provider continuity evidence, successful current-release full provider scenario runs and whitehat-security's independent scoped assurance, plus the real adoption decision d20a9750-2b29-534e-8227-fb866581a6ca. Agents may prepare the packet; only the informed owner/human route resolves adoption. No standing notice or global instruction edit is authorized by this draft.
After acceptance use the existing POST /messages/ standing-notice process,
to_agent: broadcast, kind: standing, carrying this exact reviewed version,
digest, source status, retrieval commands, limitations and rollout evidence.
Record returned notice ID and reach via GET /messages/notices; distinguish
delivery and acknowledgement from scenario understanding. Subsequent notices
use supersedes_id; do not count acknowledgement as runtime adoption or proof.
Maintenance: the manifest's 30-day source-review deadline is 2026-11-02 for sources checked 2026-10-03. Changed, withdrawn, superseded or expired guidance is withheld until the source owner refreshes and Emergent republishes a sealed release. Source owners notify maintenance through existing work/message records; Emergent rechecks source digests and relevant negative/scenario tests. Custodian supersedes accepted notices after renewed review. Withdrawal must name affected release/card, reason, replacement and verification status. Pilot instruction blocks use Emergent's tested rollback; no unreviewed package auto-update.
Open gates stay in EMERGENT-WP-0002 T02/T05/T07/T09 and CUST-WP-0073 T02/T04; no duplicate workplan, supervisor service or autopilot grant is created. Custodian T04 remains wait for verified agent identity and execution path.