Skip to content

Research: causal jurisdiction carrier discriminator RC1 — terminal - #84

Draft
camerontjs-dot wants to merge 6 commits into
integration/cal-pipeline-c2-ingress-20260915from
research/causal-jurisdiction-carrier-discriminator-rc1-20260918
Draft

camerontjs-dot wants to merge 6 commits into
integration/cal-pipeline-c2-ingress-20260915from
research/causal-jurisdiction-carrier-discriminator-rc1-20260918

Conversation

@camerontjs-dot

@camerontjs-dot camerontjs-dot commented Sep 18, 2026

Copy link
Copy Markdown
Owner

Terminal disposition

SUPPORTED_EXTERNALLY_BOUND_CAUSAL_JURISDICTION_CARRIER_RC1.

Exact evidence:

  • Decision parent b1bcc33e...
  • exact C2 authority b42c827a...
  • pre-candidate head 2ed3e750..., run 35363219456
  • exact candidate fdfd7307...
  • decisive run 35363332966, job 105659688779

Weak unbound caller routing is falsified as authority.

The externally digest-bound manifest:

  • preserves ordinary support -> existing generic CLEAR;
  • routes explicit-source-causal-assertion support to dedicated_causal_required;
  • emits no generic causal CLEAR through the gate;
  • rejects all 10 relabel/stale/binding/missing controls.

RC0 #83 remains preserved as evaluator-invalid.

This demonstrates bounded external-carrier sufficiency and weakens the need for immediate Contract C widening, but does not choose a production architecture or manifest issuer.

No maintained source, Contract C, production policy, Authorization, execution, merge, or release.

@camerontjs-dot camerontjs-dot changed the title Research: causal jurisdiction carrier discriminator RC1 Research: causal jurisdiction carrier discriminator RC1 — terminal Sep 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant