LISH: expose Hackpert expert controls in hm-expert #179

New issue

Open

opened 2026-09-05 02:02:51 +00:00 by nsaspy · 0 comments

nsaspy commented

2026-09-05 02:02:51 +00:00

Owner

Outcome

Make hm-expert a real operator shell for the existing Hackpert expert engine, not only a generic LISH entry point.

Build on #14, #24, #27, #29 and the CLI/LISH packaging work in #175. Reuse the existing typed inspection and expert APIs; do not create a second expert controller, state store, executor, or database.

First control surface

Expose LISH commands or a coherent expert command group for at least:

current expert/run status;
authority mode (passive / active);
reasoning strategy (symbolic / direct where represented by the current runtime);
objective/spec satisfaction and blockers;
current plan / step;
action admission history, including rejection reason;
budget state;
strategy transition history;
available/selected extension information.

Where the runtime already has a typed Common Lisp function, the LISH command must be a thin adapter over that function rather than a parallel implementation.

Architecture

LISH is presentation/control; Hackmode Common Lisp APIs remain first-class.
Keep passive/active authority unchanged.
No direct Tek9 mutation from shell adapters.
No raw Prolog shell escape.
Provider execution, when intentionally exposed later, must use the canonical typed provider/effect boundary.
Prefer a dedicated shell adapter system/module if that avoids coupling the core expert engine to LISH.
Coordinate with #175 instead of duplicating its launcher/flake work.

Acceptance proof

hm-expert starts successfully with the packaged LISH runtime from #175 or its reconciled successor.
A deterministic fixture expert run can be inspected from LISH.
Status output reports operation/run identity, authority, reasoning strategy, objective state, and budget state from typed runtime objects.
Plan/action/transition inspection is available without reparsing prose.
Direct Common Lisp invocation and the corresponding LISH command return equivalent typed information.
Inspection commands cause zero provider dispatches and zero canonical mutations.
nix flake check or the repository's packaged check surface exercises the expert-shell load path.

Fence

Do not edit database persistence internals. Do not replace or duplicate #175's CLI/flake implementation; consume it or stack cleanly on it.

## Outcome Make `hm-expert` a real operator shell for the existing Hackpert expert engine, not only a generic LISH entry point. Build on #14, #24, #27, #29 and the CLI/LISH packaging work in #175. Reuse the existing typed inspection and expert APIs; do not create a second expert controller, state store, executor, or database. ## First control surface Expose LISH commands or a coherent `expert` command group for at least: - current expert/run status; - authority mode (`passive` / `active`); - reasoning strategy (`symbolic` / `direct` where represented by the current runtime); - objective/spec satisfaction and blockers; - current plan / step; - action admission history, including rejection reason; - budget state; - strategy transition history; - available/selected extension information. Where the runtime already has a typed Common Lisp function, the LISH command must be a thin adapter over that function rather than a parallel implementation. ## Architecture - LISH is presentation/control; Hackmode Common Lisp APIs remain first-class. - Keep passive/active authority unchanged. - No direct Tek9 mutation from shell adapters. - No raw Prolog shell escape. - Provider execution, when intentionally exposed later, must use the canonical typed provider/effect boundary. - Prefer a dedicated shell adapter system/module if that avoids coupling the core expert engine to LISH. - Coordinate with #175 instead of duplicating its launcher/flake work. ## Acceptance proof 1. `hm-expert` starts successfully with the packaged LISH runtime from #175 or its reconciled successor. 2. A deterministic fixture expert run can be inspected from LISH. 3. Status output reports operation/run identity, authority, reasoning strategy, objective state, and budget state from typed runtime objects. 4. Plan/action/transition inspection is available without reparsing prose. 5. Direct Common Lisp invocation and the corresponding LISH command return equivalent typed information. 6. Inspection commands cause zero provider dispatches and zero canonical mutations. 7. `nix flake check` or the repository's packaged check surface exercises the expert-shell load path. ## Fence Do not edit database persistence internals. Do not replace or duplicate #175's CLI/flake implementation; consume it or stack cleanly on it.

nsaspy referenced this issue

2026-09-05 02:16:53 +00:00

agent-zero: restore two Hackmode development workers #180