Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
37 changes: 37 additions & 0 deletions docs/RELEASE_OPERATIONS.md
Original file line number Diff line number Diff line change
Expand Up @@ -100,3 +100,40 @@ Run `python3 -B -S tools/research_delivery.py --help` for the specification and
bounds. Verification checks archive custody; it does not execute evidence or
certify its scientific claims. Link original execution receipts and unchanged
predecessor deliveries rather than duplicating their complete payloads by default.

### Destination-audience preflight

Archive verification establishes byte custody. Before any upload, registration
or message carrying delivery metadata, separately establish who can receive
that particular write and whether its complete contents are authorized there:

1. Read current sharing evidence for the exact receiving file, folder or register,
or verify the message audience. Include applicable inherited and published
access. Check the archive destination and each metadata destination separately;
names, previous registrations and source readability are not audience evidence.
Do not change sharing to make the check pass.
2. Bind the observation and its time to that destination and the proposed outgoing
fields in the existing appropriately private custody record. Recheck after a
destination, sharing or payload change, or a delay that makes the observation
stale. If the audience cannot be established, pause only that write and report
the missing evidence; continue unrelated work.
3. Inspect every outgoing field, including notes, titles, embedded links and
formulas. For a public register, normally use reviewed public artifact/event
IDs, hashes, byte counts, scientific-effect labels and already-public source,
run or artifact links. Do not copy a private handoff wholesale. Keep private
locator IDs, URLs, paths and access-bearing links out unless their exact
publication to that audience is separately authorized under the applicable
rules. Preserve the existing
[owner-authorized metadata scope](../governance/OP-PRIVACY-20260927.md#current-owner-authorized-publication-scope).
4. Keep the private locator mapping and raw permission details in a separately
verified, appropriately restricted custody record. Public records receive only
permitted references or a neutral private-custody marker; a marker does not
claim that readers can retrieve the private bundle.
5. After writing, read back only the affected output or range, including its links
and notes, and compare with the screened outgoing contents. Preserve original
hashes, source identities, scientific labels and historical evidence. Do not
broaden the check into unrelated register rows or private files.

This is a publication procedure, not installed runtime enforcement or a new
permission grant. The offline delivery helper and register identity checks do
not verify live sharing. A successful byte check cannot replace this preflight.
17 changes: 17 additions & 0 deletions governance/OP-PRIVACY-20260927.md
Original file line number Diff line number Diff line change
Expand Up @@ -86,3 +86,20 @@ The [repair pickup](https://github.com/d6g8k5htny-coder/main/issues/307#issuecom
records this exact scope; the earlier
[email-only hold supersession](https://github.com/d6g8k5htny-coder/main/issues/275#issuecomment-6051694172)
remains part of its provenance. Historical owner quotations above are unchanged.

## Destination-specific publication checks

Cloud storage is not inherently private. The historical Drive/Dropbox
description above is not evidence of every object's current audience. Before an
authorized upload, registration or message, check the exact receiving destination
under the [release preflight](../docs/RELEASE_OPERATIONS.md#destination-audience-preflight).
Checking an archive folder does not check a separate register receiving its
metadata. This bounded read does not authorize unrelated Drive/Dropbox searches,
cleanup or sharing changes.

Withhold private file or folder identifiers, locator URLs, source paths and
access-bearing links from public destinations unless their exact publication to
that audience is separately authorized under the applicable rules. An unknown
audience pauses only that write. The existing owner-authorized public metadata
exceptions above remain valid; do not reopen them solely because of this check.
Neither source readability nor this procedure grants new publication authority.
8 changes: 8 additions & 0 deletions governance/OP-WORKFLOW-20260930.md
Original file line number Diff line number Diff line change
Expand Up @@ -162,6 +162,14 @@ predecessor deliveries by immutable ID/hash; copy their payloads only when neede
for a self-contained reproducibility package. Preserve exact source bytes,
historical failures, review scope and required original execution receipts.

Before publishing or registering a delivery, apply the
[destination-audience preflight](../docs/RELEASE_OPERATIONS.md#destination-audience-preflight).
Verify each receiving destination separately, including the register or message
that receives metadata. A private archive does not establish a private register.
Check outgoing fields against that destination's current audience and existing
authorization. An unknown or unverifiable audience pauses only the affected
write; continue unrelated work.

Freeze the inventory after inputs stabilize and verify membership and bytes.
Use [the reusable delivery builder](../tools/research_delivery.py) with an explicit
file list and expected identities; its `build` and `verify` commands validate
Expand Down
Loading