Skip to content

spike: demonstrate RFC-0001 payload-integrity fallback#135

Open
binarylogic wants to merge 1 commit intomasterfrom
spike/rfc-0001-integrity-bypass
Open

spike: demonstrate RFC-0001 payload-integrity fallback#135
binarylogic wants to merge 1 commit intomasterfrom
spike/rfc-0001-integrity-bypass

Conversation

@binarylogic
Copy link
Copy Markdown

Why

This spike demonstrates one concrete principle from RFC-0001 (Edge Proxy Runtime Contract):

  • if transformed payload integrity is uncertain, do not forward risky mutated data
  • fallback to original payload behavior instead

RFC reference: https://github.com/usetero/rfcs/pull/1

What this spike changes

When a module returns a modified payload and recompression fails, the proxy now bypasses the modified payload and forwards the original request body unchanged.

Why this is useful

This is a small, isolated example of the runtime contract in action:

  • integrity over best-effort mutation
  • explicit safe fallback
  • no broad Theme 1 refactor

Validation

  • zig build test

@binarylogic binarylogic requested a review from jaronoff97 March 1, 2026 21:32
@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Apr 1, 2026

This PR is stale because it has been open for 30 days with no activity. Remove stale label or comment or this will be closed in 7 days.

@github-actions github-actions bot added the Stale label Apr 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Development

Successfully merging this pull request may close these issues.

1 participant