ARDR: reconcile StarIntel observability semantics and exporter boundaries #184

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

Research transaction

Issue-backed ARDR transaction for the observability program seeded by:

lost-rob0t/starintel-server#46 — metrics/tracing/audit/diagnostics
lost-rob0t/starintel-server#121 — structured logging event contract
lost-rob0t/starintel-server#128 — optional OTLP/OpenObserve export
lost-rob0t/star-lang#49 — StarLang runtime/actor observability hooks

Canonical Org artifacts

roam/research/star-server/STAR-RESEARCH-052-observability-correlation-audit-contract.org
roam/design/star-server/STAR-SERVER-051-observability-correlation-audit-contract.org

Lifecycle:

research: READY_FOR_DESIGN
design: DESIGN_READY_FOR_OPERATOR_REVIEW

Approval state:

research conclusion: APPROVED by explicit operator comment on starintel-server#46, referencing research commit 0b5ac74a36c5b6500df7fb494253ed225a0ab2b5
architecture/design: PENDING
implementation: PENDING / AWAITING_OPERATOR_IMPLEMENTATION_APPROVAL
publication: PENDING until the exact-main publication workflow succeeds

Decision boundary

Research approval authorizes advancement to design only. It does not approve the design and does not authorize implementation. Do not expose this work to RAGE until operator implementation approval exists in the canonical approval workflow.

Key reconciliation

The provider-neutral semantic contract owns typed observation context, events, metrics, spans, and audit records. Structured logging/syslog/OTLP/OpenObserve are downstream projections/adapters. StarLang owns actor/runtime instrumentation semantics. The OTLP/OpenObserve configuration seed must use the canonical data-only deployment configuration + secret-reference boundary rather than treating executable init Lisp as ordinary configuration.

## Research transaction Issue-backed ARDR transaction for the observability program seeded by: - `lost-rob0t/starintel-server#46` — metrics/tracing/audit/diagnostics - `lost-rob0t/starintel-server#121` — structured logging event contract - `lost-rob0t/starintel-server#128` — optional OTLP/OpenObserve export - `lost-rob0t/star-lang#49` — StarLang runtime/actor observability hooks ## Canonical Org artifacts - `roam/research/star-server/STAR-RESEARCH-052-observability-correlation-audit-contract.org` - `roam/design/star-server/STAR-SERVER-051-observability-correlation-audit-contract.org` Lifecycle: - research: `READY_FOR_DESIGN` - design: `DESIGN_READY_FOR_OPERATOR_REVIEW` Approval state: - research conclusion: **APPROVED** by explicit operator comment on `starintel-server#46`, referencing research commit `0b5ac74a36c5b6500df7fb494253ed225a0ab2b5` - architecture/design: **PENDING** - implementation: **PENDING / AWAITING_OPERATOR_IMPLEMENTATION_APPROVAL** - publication: **PENDING** until the exact-main publication workflow succeeds ## Decision boundary Research approval authorizes advancement to design only. It does **not** approve the design and does **not** authorize implementation. Do not expose this work to RAGE until operator implementation approval exists in the canonical approval workflow. ## Key reconciliation The provider-neutral semantic contract owns typed observation context, events, metrics, spans, and audit records. Structured logging/syslog/OTLP/OpenObserve are downstream projections/adapters. StarLang owns actor/runtime instrumentation semantics. The OTLP/OpenObserve configuration seed must use the canonical data-only deployment configuration + secret-reference boundary rather than treating executable init Lisp as ordinary configuration.

nsaspy referenced this issue

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

DESIGN_READY_FOR_OPERATOR_REVIEW: OpenRouter Analytics collector + reconciliation #198