ARDR: P1 explicit StarIntel library API, runtime context, and typed ports #191

New issue

Open

opened 2026-09-02 17:26:15 +00:00 by nsaspy · 0 comments

nsaspy commented

2026-09-02 17:26:15 +00:00

Owner

Scope

Bounded ARDR research transaction seeded by lost-rob0t/starintel-server#40, after complete open-backlog enumeration and reconciliation with the preceding embeddable-library work for server #39.

Concrete owner/problem

Owner: lost-rob0t/starintel-server, P1 issue #40.

Current server source already has a star.runtime:star-runtime lifecycle object, but application behavior still reaches process globals and concrete adapters (star.runtime:*runtime*, star.actors:*sys*, producer/target globals, global HTTP handle/settings). Embedded callers therefore do not yet have one explicit typed application-service contract that can be instantiated with independent fake ports or shared with HTTP adapters.

The research must preserve #39's side-effect-free core boundary and #37's existing star.runtime lifecycle authority rather than inventing a second runtime/control plane.

Required research outputs

distinguish lifecycle/runtime ownership from application-service context;
identify the minimum explicit public operation/request context;
define typed port boundaries only for concrete current dependencies;
determine a bounded migration path from globals without claiming full multi-live-runtime support prematurely;
define RED-first proof for two isolated fake-backed contexts/runtimes and HTTP/embedded semantic equivalence;
preserve StarLang-first architecture and keep Common Lisp runtime effects below StarLang declarations.

Dependencies

server #39 / STAR-RESEARCH-039 / STAR-SERVER-046: pure embeddable core boundary;
server #37 / Auto-Research #182/#183: existing lifecycle owner;
server #32/#33: lease application/fencing contracts;
server #41: downstream concrete adapter extraction.

Approval boundary

Research may advance to design under the active ARDR policy. Architecture/design and implementation authorization remain operator-only. This issue, its state, publication, or machine output does not authorize implementation.

## Scope Bounded ARDR research transaction seeded by `lost-rob0t/starintel-server#40`, after complete open-backlog enumeration and reconciliation with the preceding embeddable-library work for server #39. ## Concrete owner/problem Owner: `lost-rob0t/starintel-server`, P1 issue #40. Current server source already has a `star.runtime:star-runtime` lifecycle object, but application behavior still reaches process globals and concrete adapters (`star.runtime:*runtime*`, `star.actors:*sys*`, producer/target globals, global HTTP handle/settings). Embedded callers therefore do not yet have one explicit typed application-service contract that can be instantiated with independent fake ports or shared with HTTP adapters. The research must preserve #39's side-effect-free core boundary and #37's existing `star.runtime` lifecycle authority rather than inventing a second runtime/control plane. ## Required research outputs - distinguish lifecycle/runtime ownership from application-service context; - identify the minimum explicit public operation/request context; - define typed port boundaries only for concrete current dependencies; - determine a bounded migration path from globals without claiming full multi-live-runtime support prematurely; - define RED-first proof for two isolated fake-backed contexts/runtimes and HTTP/embedded semantic equivalence; - preserve StarLang-first architecture and keep Common Lisp runtime effects below StarLang declarations. ## Dependencies - server #39 / STAR-RESEARCH-039 / STAR-SERVER-046: pure embeddable core boundary; - server #37 / Auto-Research #182/#183: existing lifecycle owner; - server #32/#33: lease application/fencing contracts; - server #41: downstream concrete adapter extraction. ## Approval boundary Research may advance to design under the active ARDR policy. **Architecture/design and implementation authorization remain operator-only.** This issue, its state, publication, or machine output does not authorize implementation.

nsaspy referenced this issue

2026-09-02 17:26:15 +00:00

DESIGN_READY_FOR_OPERATOR_REVIEW: StarIntel deployment configuration and trusted extension boundary #192