MB782 introduces short-content-v3 to production without granting it
permanent public authority. The package joins #i/o in observe, alongside
Quotes, Channel Activity, Factoids and Playful, which all remain enabled/on.
The first !short request runs behind the curtain. Because the package is in
observe and has no historical fallback, it must produce no IRC reply. Its KV
repository must also remain byte-for-byte unchanged. This proves that shadow
execution neither leaks output nor creates a cache or counter as a side
effect.
The policy then opens a tightly bounded on window. The messenger may perform
one mediated HTTPS request to GitHub’s public API, read the repository name and
return exactly:
MB782-mediabot_v3
The endpoint, JSON path, prefix, language, cache lifetime and output limit are all typed policy values. The proof accepts one response, one repository revision and one increment of the served counter—nothing more. 🪟
The window closes immediately and policy returns to observe. The pilot then
restores the short-content repository exactly to its original bytes and file
mode, or removes the temporary file if none existed. Quote and factoid tables
are separately snapshotted and must not change.
The complete ledger entries for Quotes, Channel Activity, Factoids and Playful are fingerprinted before the pilot. Their grants, policies and typed settings must remain byte-for-byte equivalent throughout.
Acceptance comes only after a production restart. short-content-v3 must
return enabled/observe with one command, complete permissions and zero
failures. The four established packages must return enabled/on unchanged, and
the restored repository and business tables must still match their original
snapshots.
If any barrier fails, MB782 moves the new package through policy off, disable
and unload, then restores the repository snapshot. The existing production
portfolio never moves. The final marker is sent only after Mediabot has
rejoined #i/o and every ward has been checked. 🔐✨
You must be logged in to reply.