Add replayable Hackmode and dynamic tool actors #202

New issue

Open

opened 2026-09-17 00:00:33 +00:00 by nsaspy · 0 comments

nsaspy commented

2026-09-17 00:00:33 +00:00

Owner

Implement a product-runtime actor layer over Hackmode's existing typed capability/provider API.

Requirements:

keep Sento as the local Common Lisp execution backend;
define a first-class hackmode actor plus one dynamic actor per registered tool/provider;
tool actors expose typed target shape, argument/options schema, produced asset types, examples, and runtime availability;
actor/tool creation, registration, invocation, completion, failure, and state transitions are event sourced and replayable;
self-register Hackmode and generated tool actors through the canonical StarIntel Server actor/service registry contract rather than creating a parallel registry;
surface every generated tool actor from Hackmode for list/describe/run operations;
use StarLang portable actor/service/lifecycle semantics where useful without making the full compiler a runtime requirement;
support Kali Linux as the baseline execution environment and model a broad advanced security-tool catalog through capability detection rather than hard-coded workstation assumptions;
map existing Hackpert tool definitions and target classification into target-shape/tool mappings;
coordinate any protocol additions through star-spec/StarLang, including target-shape macros, example targets, plugin metadata, and generated language bindings.

The StarIntel event-source dependency is being moved to Tek9 under starintel-server#192; this actor layer should target that replay contract.

Implement a product-runtime actor layer over Hackmode's existing typed capability/provider API. Requirements: - keep Sento as the local Common Lisp execution backend; - define a first-class `hackmode` actor plus one dynamic actor per registered tool/provider; - tool actors expose typed target shape, argument/options schema, produced asset types, examples, and runtime availability; - actor/tool creation, registration, invocation, completion, failure, and state transitions are event sourced and replayable; - self-register Hackmode and generated tool actors through the canonical StarIntel Server actor/service registry contract rather than creating a parallel registry; - surface every generated tool actor from Hackmode for list/describe/run operations; - use StarLang portable actor/service/lifecycle semantics where useful without making the full compiler a runtime requirement; - support Kali Linux as the baseline execution environment and model a broad advanced security-tool catalog through capability detection rather than hard-coded workstation assumptions; - map existing Hackpert tool definitions and target classification into target-shape/tool mappings; - coordinate any protocol additions through star-spec/StarLang, including target-shape macros, example targets, plugin metadata, and generated language bindings. The StarIntel event-source dependency is being moved to Tek9 under starintel-server#192; this actor layer should target that replay contract.