M0/M1: Add the orchestration retained-result foundation - #1510
Draft
Paul Lizer (paullizer) wants to merge 2 commits into
Draft
Paul Lizer (paullizer) wants to merge 2 commits into
Paul Lizer (paullizer) wants to merge 2 commits into
Conversation
Implement M0/M1 typed named outputs, strict completeness and bindings, authorized private retained-result readers, and lifecycle-fenced commits. Preserve production v1 execution, saved Analyze, workflows, and exact_records_v1 JSON behavior. Document foundation-only scope at version 0.261.125. Refs microsoft#1509 Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Paul Lizer (paullizer)
changed the base branch from
Development
to
paullizer-react-v2-ui
September 21, 2026 16:16
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
Comment on lines
+18
to
+34
| from functions_orchestration_result_contracts import ( | ||
| Completeness, | ||
| Coverage, | ||
| InputBinding, | ||
| InputSpec, | ||
| OutputSpec, | ||
| ProducerIdentity, | ||
| RecordColumn, | ||
| ResultContractError, | ||
| ResultRef, | ||
| StepBindings, | ||
| TaskResult, | ||
| canonical_digest, | ||
| validate_input_bindings, | ||
| validate_json, | ||
| validate_record, | ||
| ) |
Preserve resumed native attempt guards, atomically bind committed results to exact producer/input receipts, and admit bounded external provenance with current access callbacks. Preserve v1 result bytes and checkpoint fingerprints; leave version ownership and runtime/export integration to the parent. Refs microsoft#1509 Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
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
2 participants
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.
Scope
Refs #1509. M0 + M1 only: executable contracts and private retained-result infrastructure. This does not finish the Gather / Reason / Render epic or activate file rendering, new runtime scheduling, UI, or retries.
Intended base:
paullizer-react-v2-uiat1f6b444c1db3d97aaf0b6e004eed6345c6a859be. The implementation branch was explicitly fast-forwarded to that published prerequisite before any edits; Development is not the review baseline.Changes
exact_records_v1JSON protocol without treating prose/Compare asanalyze-final-v1.Production v1 plan/executor/RunContext/checkpoint behavior, existing fingerprints, standalone tools, workflows, rendering implementations, requirements, deployers, and release notes are unchanged. There are no new settings, routes, or user-facing controls.
Validation
Coverage includes two complete consumers after persistence/restart, a 30,000-row result exceeding 8 MiB, first/last records, Unicode/ordered schemas, pending/partial/invalid/unavailable states, source revocation/change/screening holds, exact lineage snapshots, corrupt counts/digests, missing final records, fake storage references, cross-attempt binding, cleanup/cancellation races, and zero facade file publication. One existing Pydantic deprecation warning remains. External storage/provider I/O is doubled; no live cloud/model work was performed.
Commit:
18fc08ac9dc21066a324afbdb499de523717be65.