Skip to content

docs(rfc): flip RFCs 0040, 0041, 0042 to accepted — maintainer sign-off #663

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jensholdgaard merged 2 commits into from
Jul 27, 2026
Merged

docs(rfc): flip RFCs 0040, 0041, 0042 to accepted — maintainer sign-off #663

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
17f2c1f
docs(rfc): flip RFCs 0040, 0041, 0042 to accepted — maintainer sign-off
jensholdgaard Jul 27, 2026
dd4a6d9
docs(rfc): sync the roadmap open-items Perses bullet to accepted
jensholdgaard Jul 27, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 7 additions & 1 deletion docs/rfcs/0040-datafusion-operator-instrumentation.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
---
rfc: 0040
title: DataFusion → OTel operator instrumentation — the query span as an operator tree
status: green
status: accepted
Comment thread
coderabbitai[bot] marked this conversation as resolved.
author: Jens Holdgaard Pedersen <jens@holdgaard.org>
drafting-assistance: Claude
created: 2026-07-25
Expand All @@ -11,6 +11,12 @@ superseded-by: —

# RFC 0040 — DataFusion → OTel operator instrumentation

> **Status: `accepted` (2026-07-28, maintainer sign-off).** Terminal. No
> thesis-gate applies, so `validated` is vacuous (precedent: RFC 0008) and
> `green` was the last verification stage; the flip records maintainer
> approval of the design as binding. The `ourios-df-otel` crate remains
> deliberately extractable for upstream.
>
> **Status: `green` (2026-07-25).** All six §5 acceptance criteria are
> implemented and pass: RFC0040.1 (operator span tree, transitively parented to
> the query span), RFC0040.2 (real, non-inverted wall-clock bounds), RFC0040.3
Expand Down
9 changes: 8 additions & 1 deletion docs/rfcs/0041-dashboard-datasource-plugins.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
---
rfc: 0041
title: Dashboard datasource plugins — Ourios as a Grafana / Perses source
status: green
status: accepted
author: Jens Holdgaard Pedersen <jens@holdgaard.org>
drafting-assistance: Claude
created: 2026-07-25
Expand All @@ -11,6 +11,13 @@ superseded-by: —

# RFC 0041 — Dashboard datasource plugins

> **Status: `accepted` (2026-07-28, maintainer sign-off).** Terminal. No
> thesis-gate applies (`validated` vacuous, RFC 0008 precedent). The
> RFC0041.5 recorded deferral survives acceptance unchanged — the `latest`
> e2e leg and wire-level `sum` land in the plugin repository when the next
> server release ships typed columns (tracked there, not by reopening this
> RFC). The Grafana datasource remains an ungated follow-up.
>
> **Status: `green` (2026-07-27, maintainer flip).** RFC0041.1–.4 and the
> .6 capstone are verified — the plugins shipped in
> [`ourios-perses-plugin`](https://github.com/jensholdgaard/ourios-perses-plugin)
Expand Down
6 changes: 5 additions & 1 deletion docs/rfcs/0042-typed-numeric-promotion.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
---
rfc: 0042
title: Typed numeric attribute promotion (RFC 0022 amendment)
status: green
status: accepted
author: Jens Holdgaard Pedersen <jens@holdgaard.org>
drafting-assistance: Claude
created: 2026-07-26
Expand All @@ -11,6 +11,10 @@ superseded-by: —

# RFC 0042 — Typed numeric attribute promotion (RFC 0022 amendment)

> **Status: `accepted` (2026-07-28, maintainer sign-off).** Terminal. No
> thesis-gate applies (`validated` vacuous, RFC 0008 precedent);
> RFC0042.9's live verification on real spend was the closing evidence.
>
> **Status note (2026-07-27, green):** RFC0042.1–.8 landed across the
> implementation slices (#649 writer, #650 config, #651 scan +
> no-coercion adapter, #652 predicates + aggregation, #653 compaction
Expand Down
21 changes: 11 additions & 10 deletions docs/roadmap.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -216,9 +216,9 @@ captured by B1/B2 (see `benchmarks.md` §2 / §7).
| 0037 | GenAI / structured-event log support | `green` |
| 0038 | Self-tracing (OTel traces for Ourios itself) | `green` — request-scoped spans on ingest, query, MCP and sweep (never per-record); traces configured through the **universal** `OTEL_*` env vars, not bespoke config |
| 0039 | Inbound trace-context propagation | `green` — all four §5 arms; the caller's trace continues across the ingest spawn and into `/mcp`, and the caller's sampling decision governs |
| 0040 | DataFusion operator instrumentation | **`green`** — `ourios-df-otel` walks a finished `ExecutionPlan` and backdates one span per operator from `BaselineMetrics`; build-vs-adopt was spiked both ways before committing (`datafusion-tracing` drops every operator span on multi-partition plans). `accepted` is a maintainer flip |
| 0041 | Dashboard datasource plugins (Grafana / Perses) | `green` (2026-07-27) — three plugins shipped in `ourios-perses-plugin` (PRs #1–#6); RFC0041.6 FinOps dashboard committed (`examples/perses/`, #661) and rendered from the live capture; RFC0041.5 partial by recorded deferral until the next server release; Grafana an ungated follow-up |
| 0042 | Typed numeric promotion (RFC 0022 amendment) | **`green`** (2026-07-27) — all nine §5 incl. RFC0042.9 verified on live spend (`sum(attr.cost_usd)` = 35.28 USD over MCP from the typed column); `accepted` is a maintainer flip |
| 0040 | DataFusion operator instrumentation | **`accepted`** (2026-07-28) TERMINAL — `ourios-df-otel` walks a finished `ExecutionPlan` and backdates one span per operator from `BaselineMetrics`; build-vs-adopt was spiked both ways before committing (`datafusion-tracing` drops every operator span on multi-partition plans) |
| 0041 | Dashboard datasource plugins (Grafana / Perses) | **`accepted`** (2026-07-28) TERMINAL — three plugins shipped in `ourios-perses-plugin` (PRs #1–#6); RFC0041.6 FinOps dashboard committed (`examples/perses/`, #661) and rendered from the live capture; RFC0041.5's recorded deferral tracks in the plugin repo until the next server release; Grafana an ungated follow-up |
| 0042 | Typed numeric promotion (RFC 0022 amendment) | **`accepted`** (2026-07-28) TERMINAL — all nine §5 incl. RFC0042.9 verified on live spend (`sum(attr.cost_usd)` = 35.28 USD over MCP from the typed column) |
Comment thread
coderabbitai[bot] marked this conversation as resolved.

**Crates — all twelve product crates are implemented** (`ourios-core`,
`-config`, `-miner`, `-wal`, `-parquet`, `-ingester`, `-querier`,
Expand Down Expand Up @@ -274,13 +274,14 @@ and the shipping milestone that followed (WAL, wire endpoints, DSL,
auth, S3, Helm — the whole §5 table below except Perses) is
substantially done. What's actually open:

- **The Perses plugins** — RFC 0041 is `green` (2026-07-27): all three
plugins shipped in `ourios-perses-plugin`, the RFC0041.6 dashboard is
committed in this repo and verified rendering. What remains is
RFC0041.5's recorded deferral (the `latest` e2e leg + wire-level
`sum`, unblocked by the next server release) and the Grafana
datasource as an ungated follow-up.
- **RFC 0040 → `accepted`** — a maintainer flip; the ladder is `green`.
- **The Perses plugins** — RFC 0041 is `accepted` (2026-07-28,
terminal): all three plugins shipped in `ourios-perses-plugin`, the
RFC0041.6 dashboard is committed in this repo and verified rendering.
What remains is RFC0041.5's recorded deferral (the `latest` e2e leg +
wire-level `sum`, unblocked by the next server release, tracked in
the plugin repo) and the Grafana datasource as an ungated follow-up.
- ~~RFC 0040 → `accepted`~~ — done (2026-07-28), alongside RFC 0041 and
RFC 0042: all three flipped `accepted` on maintainer sign-off.
- Scattered §7/§9 open items on already-`green`/`validated` RFCs (e.g.
the recurring D1/D2 soak cadence now that the harness has shipped
(§9.19/§9.23), RFC 0021's phase 2 gated on upstream DataFusion 55,
Expand Down