ARDR: P1 StarLang manifest + dataset RuntimePlan composition #186

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

Issue-backed ARDR transaction for lost-rob0t/starintel-server#43.

The current server issue asks for actor/dataset manifests as runtime configuration. Current StarLang already compiles actor/domain-server semantic manifests, while current server actor composition remains imperative through globals/hooks/raw actor registration. The research therefore reconciles the existing STAR-MANIFEST-001 draft rather than creating a second declarative actor language.

Canonical Org

Research: roam/research/star-server/STAR-RESEARCH-050-manifest-runtime-plan-composition.org — READY_FOR_DESIGN
Design/adversarial review: roam/design/star-server/STAR-MANIFEST-001-document-contracts.org — DESIGN_READY_FOR_OPERATOR_REVIEW

The stable Org ID of the research node was preserved when its human-facing canonical number was corrected from 043 to 050 after inspecting the live canonical-ID collision audit PR #198.

Decision

Preserve three authorities:

compiler-produced immutable StarLang semantic program manifest;
inert StarIntel Actor Deployment Manifest binding that semantic artifact to runtime composition;
inert Dataset Manifest for dataset/catalog/storage/governance and typed compatible flow bindings.

Compile these into one pure deterministic RuntimePlan before any long-lived effect, then feed thread/Sento/mailbox/lifecycle demands into existing server #34/#35/#36/#37 authorities. Do not duplicate accepted types/capabilities/restart semantics, make manifests executable, or treat requested capacity as a grant.

Implementation handoff

Existing server #43 was updated with dependency order, acceptance criteria, and RED-first slices. First proposed RED is a pure incompatible-route fixture proving zero actor/thread/network callbacks.

Approval boundary

Research/design lifecycle may advance under active ARDR policy. Implementation authorization remains PENDING / AWAITING_OPERATOR_IMPLEMENTATION_APPROVAL. This issue, publication, green validation, priority, or machine review does not authorize RAGE implementation.

## Scope Issue-backed ARDR transaction for `lost-rob0t/starintel-server#43`. The current server issue asks for actor/dataset manifests as runtime configuration. Current StarLang already compiles actor/domain-server semantic manifests, while current server actor composition remains imperative through globals/hooks/raw actor registration. The research therefore reconciles the existing `STAR-MANIFEST-001` draft rather than creating a second declarative actor language. ## Canonical Org - Research: `roam/research/star-server/STAR-RESEARCH-050-manifest-runtime-plan-composition.org` — `READY_FOR_DESIGN` - Design/adversarial review: `roam/design/star-server/STAR-MANIFEST-001-document-contracts.org` — `DESIGN_READY_FOR_OPERATOR_REVIEW` The stable Org ID of the research node was preserved when its human-facing canonical number was corrected from 043 to 050 after inspecting the live canonical-ID collision audit PR #198. ## Decision Preserve three authorities: 1. compiler-produced immutable StarLang semantic program manifest; 2. inert StarIntel Actor Deployment Manifest binding that semantic artifact to runtime composition; 3. inert Dataset Manifest for dataset/catalog/storage/governance and typed compatible flow bindings. Compile these into one pure deterministic `RuntimePlan` before any long-lived effect, then feed thread/Sento/mailbox/lifecycle demands into existing server #34/#35/#36/#37 authorities. Do not duplicate accepted types/capabilities/restart semantics, make manifests executable, or treat requested capacity as a grant. ## Implementation handoff Existing server #43 was updated with dependency order, acceptance criteria, and RED-first slices. First proposed RED is a pure incompatible-route fixture proving zero actor/thread/network callbacks. ## Approval boundary Research/design lifecycle may advance under active ARDR policy. **Implementation authorization remains `PENDING / AWAITING_OPERATOR_IMPLEMENTATION_APPROVAL`.** This issue, publication, green validation, priority, or machine review does not authorize RAGE implementation.