chore(parity-manifest): annotate Execution + Cue field drift (#589 / #590) per primary's authoritative split#89
Merged
mikemolinet merged 1 commit intoMay 12, 2026
Conversation
…#590) per primary's authoritative split
Adds a new `field_drift_annotations` section to parity-manifest.json
documenting why specific fields in private cueapi's Execution + Cue
schemas are absent from OSS. Authoritative split from cueapi-primary
via cue-pm relay (msg_4ofzmxcjoyu4, 2026-05-12).
## Three buckets
**A) DEFERRED — port planned on trigger** (3 fields on Execution):
- payload_override (cueapi/cueapi PR #589 / #577)
- triggered_by (Phase 18 Gap 7 family)
- payload (effective field on ExecutionResponse — depends on payload_override)
Trigger: batched Execution-schema sprint OR concrete demand from an
OSS self-hoster. Primary's verbatim annotation string used.
**B) INTENTIONAL — no port planned** (4 fields on Execution):
- outcome_state
- evidence_external_id
- evidence_result_url
- evidence_artifacts
Tied to the hosted-only verification primitive system (Phase 18
Gap 11): POST /v1/executions/{id}/verify, /verification-pending,
verification_mode config on cues. The columns alone without the
routing endpoints carry no value, so they stay hosted-only.
Also notes that other evidence_* columns (result_ref, result_type,
summary, validation_state, produced_at, metadata) ARE in the OSS
model but not surfaced through ExecutionResponse — same intentional
rationale.
**C) DEFERRED contingent on #589** (2 fields on Cue):
- require_payload_override (cueapi/cueapi PR #590)
- required_payload_keys (cueapi/cueapi PR #590)
Trigger: port after #589 (payload_override) lands; OSS self-hoster
fire-with-override usage signal. Server-side enforcement has no
override to enforce against without the prerequisite field.
## Audit date bump
last_full_audit: 2026-05-11 → 2026-05-12 (just this annotation pass;
not a full Execution-schema sprint audit).
## Provenance
Surfaced by cueapi-secondary 2026-05-12 ~00:35Z during follow-on
investigation to cueapi-core #88 (BodyVerify STRING-shape hotfix).
Initial design note went to cue-pm via Cue Messages msg_cr1v9hpu84gb
with primary on notify-list (msg_tuvn53g2h9wz). PM's CTO-concur on
Option C (defer) at msg_u7qwyrkx0wqk. Primary's full 3-way split
(this PR's authoritative source) at msg_fyfs7568tztu, relayed via
cue-pm in msg_4ofzmxcjoyu4 ~00:50Z. Tier-1-small per PM spec.
## Out of scope
- Actual Execution / Cue schema ports (bucket A + C). Backlog row
to be filed for "cueapi-core: payload_override + triggered_by +
payload port + #590 contingent on #589", item_status=deferred,
priority=someday, lead_agent=cueapi-primary.
- Backfilling missing Backlog rows for the existing stale
"Parity port: PR #589 → cueapi-core" and "Parity port: PR #590 →
cueapi-core" rows (they predate primary's mixed-split decision and
should be updated rather than duplicated).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a new
field_drift_annotationssection toparity-manifest.jsondocumenting why specific fields in private cueapi's Execution + Cue schemas are absent from OSS. Authoritative split from cueapi-primary via cue-pm relay (msg_4ofzmxcjoyu4, 2026-05-12). Primary specced the annotation strings verbatim.Three buckets
payload_override,triggered_by, effectivepayloadfieldoutcome_state,evidence_external_id,evidence_result_url,evidence_artifactsrequire_payload_override,required_payload_keysProvenance
cueapi-core #88(BodyVerify STRING-shape hotfix) follow-on investigationmsg_cr1v9hpu84gb→ cue-pm, notify=cueapi-primarymsg_tuvn53g2h9wz)msg_u7qwyrkx0wqkmsg_fyfs7568tztumsg_4ofzmxcjoyu4Audit date
last_full_audit: 2026-05-11 → 2026-05-12 (just this annotation pass; not a full Execution-schema sprint audit).Out of scope
item_status=deferred,priority=someday,lead_agent=cueapi-primary.🤖 Generated with Claude Code