ARDR: P1 StarIntel concrete adapter extraction behind typed runtime ports #189
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#189
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?
Scope
Bounded ARDR research transaction seeded by
lost-rob0t/starintel-server#41after complete relevant open-backlog enumeration.Research the current StarIntel Server coupling between application/domain behavior and concrete HTTP, RabbitMQ, CouchDB, Valkey, scheduler/timer, actor, and process-global mechanisms. Reconcile the design with the already-created #39 side-effect-free core boundary and #40 explicit runtime/service-call/typed-port architecture.
Concrete owner/problem
Owner:
lost-rob0t/starintel-server, P1 issue #41.Current server remains one serial
:starintel-gserverASDF system whose dependency closure includes cl-couch, cl-rabbit, Sento, Clack/Hunchentoot, Ningle, Dexador, lparallel, and other concrete runtime libraries. Some application services already use injected functions, and the lease subsystem already has a backend-neutrallease-storeprotocol. The research should preserve those good seams and determine the smallest dependency-ordered adapter extraction rather than perform a big-bang package rewrite.Dependencies
Output
Persist/update canonical Org research and design under the existing star-server project/index. Include source-backed findings, bounded implementation handoff, RED-first targets, adversarial review, dependencies, and unresolved questions.
Approval boundary
Research may become
READY_FOR_DESIGNand design may become ready for operator review. Implementation authorization remains PENDING / operator-only. This issue, publication, or machine review cannot authorize implementation.