feat(operations): centralize governed execution - #178
Merged
yaacovcorcos merged 3 commits intoAug 1, 2026
Merged
Conversation
yaacovcorcos
changed the base branch from
feature/scient-operation-authority-final
to
main
July 31, 2026 14:39
yaacovcorcos
changed the base branch from
main
to
feature/scient-operation-authority-final
July 31, 2026 14:39
This was referenced Jul 31, 2026
…scient-operation-executor-f1
Contributor
Author
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
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.
User effect
Scient now routes governed agent-gateway operations through one host-neutral executor instead of allowing each transport path to assemble authority, lifecycle, and outcome handling independently. Reads are released only after current authority is rechecked; writes preserve their transactional or revocation-fenced execution contract; irreversible external effects remain disabled until durable intent exists.
Why this layer
This is the smallest independently reviewable execution layer above draft PR #172's operation registry and authority model. It establishes the owned seam required before adapting Synara's external MCP, automation, browser, or annotation concepts. It does not expose a new external endpoint or enable any additional capability.
Provenance and disposition
Protected boundaries
Exact scope
82ecc2de13fd0a1d5a7c3b186afbda06dcf98d67(feature/scient-operation-authority-final, draft feat: establish Scient operation authority #172)83b60c3725b74684759fe58450c334b391120f45+717/-155Verification
apps/servertypecheck passed.git diff --checkpassed; publication worktree clean.Independent review
Exactly three non-author reviews certified this exact head:
All scoped findings were resolved in the append-only repair commit before recertification; no unresolved P0, P1, or P2 remains.
Rollback and limitations
Rollback is the removal of this isolated executor layer and restoration of the prior transport-local orchestration; it changes no schema or stored data. This draft depends on #172 and must not be accepted first. Durable receipts/idempotent restart reconciliation are intentionally delivered in the next independent draft; external MCP, automation, browser control, and scientific records remain disabled/unimplemented here.
Final alignment certification — 2026-08-01
This section supersedes any earlier publication-boundary wording.