DESIGN_READY_FOR_OPERATOR_REVIEW: explicit StarIntel library API and typed runtime ports #190
Labels
No labels
bug
design
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
research
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
nsaspy/starintel-auto-research#190
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Design-review transaction for Auto-Research #193 and
lost-rob0t/starintel-server#40.The canonical design will preserve the existing
star.runtimelifecycle authority and the #39 pure-core boundary while defining an explicit public Common Lisp runtime/application contract, request context, typed ports, compatibility-default behavior, and an incremental path away from singleton globals.The first proposed realization remains pure/fake-backed and dependency-ordered behind #39's core boundary. Full simultaneous live multi-runtime support is not to be claimed until concrete singleton actor/HTTP/resource ownership is actually removed.
Architecture/design review and implementation authorization remain PENDING / operator-only. Design readiness, this issue, publication, or machine review does not authorize implementation.