[Phase 3] Validate and apply action graph batches as undoable transactions #20

New issue

Closed

opened 2026-07-25 21:54:46 +00:00 by lost-rob0t · 0 comments

lost-rob0t commented

2026-07-25 21:54:46 +00:00

(Migrated from github.com)

Parent: #2
Depends on: #8, #9, #19

Scope

Define action success, empty result, diagnostics, provenance, and failure payloads.
Validate every returned graph operation against schemas, graph invariants, type constraints, capability grants, and configured output budgets.
Apply an accepted action batch through the normal command engine.
Record action identity, version, invocation ID, parameters, timing, and summary with the transaction.

Acceptance criteria

Invalid output never partially changes the graph.
One action result is applied and undone as one transaction.
Empty batches can return a visible message without advancing the graph revision.
External side effects are never represented as undone merely because graph output is removed.
Tests cover malformed, oversized, stale, duplicate, and valid result batches.

Parent: #2 Depends on: #8, #9, #19 ## Scope - Define action success, empty result, diagnostics, provenance, and failure payloads. - Validate every returned graph operation against schemas, graph invariants, type constraints, capability grants, and configured output budgets. - Apply an accepted action batch through the normal command engine. - Record action identity, version, invocation ID, parameters, timing, and summary with the transaction. ## Acceptance criteria - Invalid output never partially changes the graph. - One action result is applied and undone as one transaction. - Empty batches can return a visible message without advancing the graph revision. - External side effects are never represented as undone merely because graph output is removed. - Tests cover malformed, oversized, stale, duplicate, and valid result batches.