Keep remote service publication records in step

The shared DWP status page is the reference for the latest recorded deployment and public verification. It describes retained observations, not continuous availability. Explorer's guides contain a dated, receipt-backed observation and link to that shared page. Do not maintain another unqualified “current deployment” paragraph in Explorer.

Why the wording drifted

The 0.6.0 implementation and local checks were committed in Explorer. Later hosting and public SDK observations were recorded in DWP. Explorer's guide, service README and changelogs retained their earlier preparation wording. The existing documentation gate required a documentation change, but did not check that the factual release claim agreed with the receipts.

Release and verification are different

OKF+ makes domain knowledge and selected evidence inspectable. Ask OKF assembles bounded evidence; MCP carries it to a compatible client. An AI interprets that evidence under separate controls. Source preparation, assembly, delivery, interpretation and any authorised action remain separate responsibilities.

Record a subsequent publication

For the 0.8.0 graph candidate, first pin vendor/graph-evidence/admission.json to the reviewed DWP producer commit. An ordinary build must pass without the candidate override. Stage the exact reviewed Explorer source, then copy the assured Worker and receipt into the separate Sites checkout. Verify the Worker digest before packaging; the publication archive carries those exact bytes. Declare capabilities: ["mcp"] in the preserved hosting manifest. This provisions or refreshes the owner's native plugin at /mcp; anonymous SDK verification uses the identical /graph/mcp handler. Test actual native tool discovery and invocation separately from the SDK route. Preserve the public audience and every earlier deployment and failure receipt.

  1. Retain the new hosting and public-client receipts in DWP. Preserve failed attempts. Use DWP's status generator and check to update the shared page; its receipt census rejects an overlooked later deployment or observation.

  2. Keep an unmatched deployment labelled as awaiting verification. Preserve source, engine, deployed runtime and verifier identities separately.

  3. Preserve the 25 September 2026 observation in its existing dated directory. The 14 November 2026 observation has its own receipts and immutable DWP commit. To add a later observation, copy only approved public receipts into a new dated directory and record their exact DWP commit, paths, byte counts and SHA-256 digests. Update the generator's declared receipt location and paths and pinned source commit in the same reviewed change.

  4. Refresh the marked blocks, then compare their inputs to the original Git objects. Neither command contacts the service or calls a model:

    uv run --locked python scripts/check_remote_release_docs.py --write --dwp-root /path/to/okf-dwp
    uv run --locked python scripts/check_remote_release_docs.py --dwp-root /path/to/okf-dwp
    uv run --locked python -m unittest tests.test_remote_release_docs -v
    
  5. Update both changelogs. Run ordinary protected review and publication checks. Pull-request CI and Pages reject edited receipt-derived blocks, missing markers, inconsistent identities and the former unscoped deployment wording.

Frozen candidate files and failed receipts keep their original wording and meaning. The documentation checker admits retained receipt bytes and checks their coherence; it does not rerun the public requests or independently attest the hosting platform. Changes made outside the declared receipt directories still require review. No automated check can guarantee arbitrary prose remains correct or that an unrecorded deployment has been documented.