Hackpert: establish explicit passive/active engine authority #177

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

Implements the first bounded slice of #27.

RED-first goal: make Hackpert authority an explicit engine property before adding the typed active action protocol. Passive must admit reasoning but deny provider dispatch and canonical mutation; active must admit those effect classes without executing anything by itself.

This PR intentionally does not add provider execution, graph/KB persistence, or database internals.

Implements the first bounded slice of #27. RED-first goal: make Hackpert authority an explicit engine property before adding the typed active action protocol. Passive must admit reasoning but deny provider dispatch and canonical mutation; active must admit those effect classes without executing anything by itself. This PR intentionally does not add provider execution, graph/KB persistence, or database internals.
feat: add explicit Hackpert engine authority modes
Some checks failed
agent-pr-serialization / one-open-pr-per-agent-lane (pull_request_target) Failing after 3s
core / common-lisp-core (pull_request) Failing after 37s
monorepo / hygiene (pull_request) Successful in 2m44s
e64de42b9e
Author
Owner

Agent PR serialization closed this PR because #172 is the newer open rage-hackpert/ lane PR. One open PR per configured agent lane is allowed.

Agent PR serialization closed this PR because #172 is the newer open `rage-hackpert/` lane PR. One open PR per configured agent lane is allowed.
nsaspy closed this pull request 2026-09-05 07:56:24 +00:00
Some checks failed
agent-pr-serialization / one-open-pr-per-agent-lane (pull_request_target) Failing after 3s
core / common-lisp-core (pull_request) Failing after 37s
monorepo / hygiene (pull_request) Successful in 2m44s

Pull request closed

Sign in to join this conversation.
No description provided.