Hackpert: establish explicit passive/active engine authority #134

Closed

nsaspy wants to merge 2 commits from rage-hackpert/27-engine-authority-mode into master

nsaspy commented

2026-09-04 20:37:21 +00:00

Owner

Implements the first bounded slice of #27.

RED-first acceptance: Hackpert engine authority must be explicit. Passive admits reasoning but denies provider dispatch and canonical mutation; active admits those effect classes, while execution itself remains for the later typed active action protocol.

Evidence:

RED commit: 920784a566
GREEN head: e64de42b9e
exact-head core workflow: success
exact-head monorepo workflow: success

No provider executor, Tek9/database internals, graph persistence, or KB persistence are added here. Closes no parent tracker; #27 remains open for the typed action/state-delta protocol and active orchestration loop.

Supersedes draft PR #38, which was closed only because the ready-for-review connector mutation failed.

Implements the first bounded slice of #27. RED-first acceptance: Hackpert engine authority must be explicit. Passive admits reasoning but denies provider dispatch and canonical mutation; active admits those effect classes, while execution itself remains for the later typed active action protocol. Evidence: - RED commit: 920784a566f4f5d271fc22578fbf65c985e93708 - GREEN head: e64de42b9e07072bfc00cdeef2695577fb76e4eb - exact-head `core` workflow: success - exact-head `monorepo` workflow: success No provider executor, Tek9/database internals, graph persistence, or KB persistence are added here. Closes no parent tracker; #27 remains open for the typed action/state-delta protocol and active orchestration loop. Supersedes draft PR #38, which was closed only because the ready-for-review connector mutation failed.

nsaspy added 2 commits

2026-09-04 20:37:21 +00:00