Skip to content

feat(pubpunk): require resolved connector refs for write handoff #84

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
t3chn merged 1 commit into from
May 20, 2026
Merged

feat(pubpunk): require resolved connector refs for write handoff #84

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
48 changes: 43 additions & 5 deletions crates/punk-eval/src/lib.rs
View file
Open in desktop

Large diffs are not rendered by default.

157 changes: 157 additions & 0 deletions crates/punk-mod-pubpunk/src/lib.rs
View file
Open in desktop

Large diffs are not rendered by default.

40 changes: 22 additions & 18 deletions docs/modules/pubpunk-workspace-instructions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -131,21 +131,22 @@ Host runtime.

The current publish receipt preflight packet can then carry explicit receipt
target, storage, operation-evidence, idempotency, rollback, error, adapter
invocation receipt, connector profile, channel, and payload refs into the
existing Module Host side-effect receipt writer preflight model. This remains a
preflight chain only. It does not write receipts, persist operation evidence,
publish, invoke adapters, run policy engines, invoke gate, read draft bodies,
collect metrics, or activate PubPunk or Module Host runtime.
invocation receipt, connector profile resolution, connector profile, selected
connector strategy, channel, and payload refs into the existing Module Host
side-effect receipt writer preflight model. This remains a preflight chain
only. It does not write receipts, persist operation evidence, publish, invoke
adapters, run policy engines, invoke gate, read draft bodies, collect metrics,
or activate PubPunk or Module Host runtime.

The current publish receipt write handoff packet can then carry explicit
preflight, receipt writer, target-path, receipt-bytes, operation-evidence,
adapter invocation receipt, connector profile, channel, and payload refs into
the existing Module Host first active local receipt writer. PubPunk still does
not read files or write receipts itself. The smoke evidence writes exact
caller-provided bytes only to an explicit temporary `.punk/runs` target through
the already-existing host writer, and does not invoke adapters, publish, mutate
event logs, persist operation evidence, write gate/proof authority, or claim
acceptance.
adapter invocation receipt, connector profile resolution, connector profile,
selected connector strategy, channel, and payload refs into the existing Module
Host first active local receipt writer. PubPunk still does not read files or
write receipts itself. The smoke evidence writes exact caller-provided bytes
only to an explicit temporary `.punk/runs` target through the already-existing
host writer, and does not invoke adapters, publish, mutate event logs, persist
operation evidence, write gate/proof authority, or claim acceptance.

The current publish operation evidence handoff packet can then carry explicit
publish receipt write handoff, receipt writer result, operation-evidence target
Expand Down Expand Up @@ -411,10 +412,12 @@ For the current code slice, the publish receipt write handoff packet blocks:
path/storage policy, or operation-evidence persistence refs;
- missing receipt target, storage, target path, receipt bytes,
operation-evidence, idempotency, rollback, error, adapter invocation receipt,
payload, channel, or connector profile refs;
payload, channel, connector profile resolution, connector profile, or
selected connector strategy refs;
- receipt target path refs outside `.punk/runs`;
- payload, channel, connector profile, adapter invocation receipt, or receipt
bytes refs not present in the allowed source refs;
- payload, channel, connector profile resolution, connector profile, selected
connector strategy, adapter invocation receipt, or receipt bytes refs not
present in the allowed source refs;
- missing required instruction refs;
- unsafe instruction, allowed-source, workspace, packet, path, or token-cost
refs;
Expand All @@ -424,9 +427,10 @@ For the current code slice, the publish receipt write handoff packet blocks:
or acceptance claims;
- raw post bodies or privacy policy that allows raw/private payloads;
- missing expected receipt fields, especially `side_effects`,
`host_validation`, `adapter_invocation_receipt`, `operation_evidence`,
`publication_receipt`, `receipt_bytes`, `receipt_target_path`, and
`receipt_write_result`.
`host_validation`, `connector_profile_resolution`,
`connector_profile_ref`, `selected_connector_strategy`,
`adapter_invocation_receipt`, `operation_evidence`, `publication_receipt`,
`receipt_bytes`, `receipt_target_path`, and `receipt_write_result`.

These checks are advisory readiness checks only. They prepare refs for the
existing Module Host first active local receipt writer. PubPunk does not read
Expand Down
43 changes: 26 additions & 17 deletions docs/modules/pubpunk.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -71,9 +71,10 @@ and expected-receipt refs before it can project host receipt-writer preflight
refs.
The publish receipt write handoff packet requires explicit preflight, receipt
writer model, target path, receipt bytes, operation-evidence, adapter
invocation receipt, connector profile, channel, payload, and expected-receipt
refs before it can project handoff refs for the existing Module Host first
active local receipt writer. The publish operation evidence handoff packet
invocation receipt, connector profile resolution, connector profile, selected
connector strategy, channel, payload, and expected-receipt refs before it can
project handoff refs for the existing Module Host first active local receipt
writer. The publish operation evidence handoff packet
requires explicit receipt write handoff, receipt writer result, receipt storage,
receipt target, receipt path, receipt bytes, operation-evidence target path,
operation-evidence bytes, operation-evidence write result, idempotency,
Expand Down Expand Up @@ -117,13 +118,14 @@ or activate runtime behavior.

The current smoke evidence also proves the first publish receipt write handoff:
a ready PubPunk packet projects explicit preflight, receipt writer, target path,
receipt bytes, operation-evidence, adapter invocation receipt, connector,
channel, and payload refs into the existing Module Host first active local
receipt writer. The writer writes exact caller-provided bytes only to an
explicit temporary `.punk/runs` target. This evidence does not invoke adapters,
publish, run policy engines, invoke gate, mutate event logs, persist operation
evidence, write proofpacks, claim acceptance, or activate PubPunk or Module Host
runtime behavior.
receipt bytes, operation-evidence, adapter invocation receipt, connector
profile resolution, connector profile, selected connector strategy, channel,
and payload refs into the existing Module Host first active local receipt
writer. The writer writes exact caller-provided bytes only to an explicit
temporary `.punk/runs` target. This evidence does not invoke adapters, publish,
run policy engines, invoke gate, mutate event logs, persist operation evidence,
write proofpacks, claim acceptance, or activate PubPunk or Module Host runtime
behavior.

The current smoke evidence also proves the first publish operation evidence
handoff: a ready PubPunk packet projects explicit receipt writer result,
Expand Down Expand Up @@ -424,25 +426,32 @@ It must provide:
- adapter invocation receipt ref;
- payload ref;
- channel ref;
- connector profile resolution ref;
- connector profile ref;
- allowed source refs covering payload, channel, connector profile, adapter
invocation receipt, and receipt bytes refs;
- selected connector strategy ref;
- allowed source refs covering payload, channel, connector profile resolution,
connector profile, selected connector strategy, adapter invocation receipt,
and receipt bytes refs;
- instruction refs;
- `request_publication_receipt_write` capability;
- metadata-only privacy policy;
- expected receipt fields including `side_effects`, `host_validation`,
`adapter_invocation_receipt`, `operation_evidence`, `publication_receipt`,
`receipt_bytes`, `receipt_target_path`, and `receipt_write_result`;
`connector_profile_resolution`, `connector_profile_ref`,
`selected_connector_strategy`, `adapter_invocation_receipt`,
`operation_evidence`, `publication_receipt`, `receipt_bytes`,
`receipt_target_path`, and `receipt_write_result`;
- optional token-cost ref.

When ready, the packet can project only
`PubPunkPublishReceiptWriteHandoffRefs` for the existing Module Host first
active local side-effect receipt writer. The PubPunk packet does not write a
receipt, read receipt bytes, persist operation evidence, invoke an adapter,
publish externally, call a policy engine, invoke gate, read draft bodies,
collect metrics, or activate PubPunk or Module Host runtime behavior. The
current smoke case uses the projected refs to call the already-existing Module
Host writer against an explicit temporary `.punk/runs` target only.
collect metrics, or activate PubPunk or Module Host runtime behavior. Direct
adapter, channel, payload, or connector profile refs are not enough to bypass
connector profile resolution. The current smoke case uses the projected refs to
call the already-existing Module Host writer against an explicit temporary
`.punk/runs` target only.

## Current publish operation evidence handoff packet

Expand Down
Loading
Loading