Skip to content

Where lumnik stands

beta. lumnik no longer grows surfaces. Between the v1.6.2 tag (7 September 2026) and this page's last revision (13 September 2026): 59 pull requests, 243 commits, 126 of them fixes — and no new subsystem. The twenty-one additions all closed doors that were already open: a run can be cancelled, a run names the endpoint each row came from, an abstention names the door that can answer. What is not here is not here on purpose, and the page that owns each gap says so in its own words.

What we do not know yet: nobody outside this team has run lumnik in production.

That paragraph is checkable, which is why it is written that way — the evidence is one command:

git log v1.6.2..HEAD --no-merges --pretty=%s \
  | sed -E 's/^([a-z]+)(\(.*\))?:.*/\1/' | sort | uniq -c | sort -rn

beta is only the word sitting on top of that count. The word is the part that goes away first.

What is deliberately not there

Every line below is a decision, not a backlog entry. Each is already declared where it belongs — on the page for the surface that has it — and this table only gathers them, so the boundary can be seen at once instead of met one page at a time.

Surface What is not there Declared in
GraphQL mutations, subscriptions, schema-introspection discovery, persisted queries, query batching, per-endpoint header overrides, on_error: warn GraphQL — Not yet supported
REST mode: api_cursor — declaring it today behaves like full; per-endpoint headers, which belong at spec.headers REST
SOAP SOAP 1.1 envelopes only — a service that requires SOAP 1.2 (application/soap+xml) is refused SOAP
Kafka (Pro) JSON only — no Avro, Protobuf or Schema Registry; one topic per connector, no filtering by key or header; no mapping block, so no hooks at ingestion; no pre-flight test; SASL/SCRAM, mTLS and OAuth Kafka — Limitations
Transformers validate-row after split-row, and aggregator on a csv-file run — both refused at lm apply, with the arithmetic reason Transformers
Events REST-, GraphQL- and SOAP-ingested tables are event-silent — the respiration rides jdbc, CSV and kafka ingestion How lumnik breathes
Chat declared status aliases feed the dormancy watch and the chat's background knowledge, not the chat's SQL or a view's filters — the chat matches the literal values in the column How lumnik breathes
Workflows the dormancy sweep reads a workflow's whole observation ledger with no LIMIT and no batching, and the transition journal's retention is unbounded — both on purpose in v1 Workflows
PWA decisions are not bounded by métier — the tab shows the whole tenant's, and says so in its own footer The métier PWA
SCIM (Pro) no /Groups; no bulk, sorting, etags or changePassword; no pagination beyond the two eq filters; not the full PATCH path grammar; no /Schemas or /ResourceTypes SCIM — Not supported
Identity SAML-only IdPs are not supported by direct trust — front them with a broker and point lumnik at the broker Bring your own IdP
Encryption rotating the master key. Rotating one secret's value is supported, and stamps rotated_at RLS and encryption

Twelve surfaces, twelve decisions. Two of them — Kafka and SCIM — are not gaps at all but the shape of the paid build; The two editions draws that boundary properly.

What is not finished

These are different in kind from the table above: started, known, and not yet closed. They are on this page because you may meet them.

  • Some refusals answer with a bare status and no body. Malformed input is correctly rejected, but a handful of doors return the status alone — the refusal is right, the explanation is missing. Being swept door by door.
  • A few conflict refusals do not name what holds the name. A 409 can tell you a name is taken without telling you which integration took it. Most now name it; the rest are on the list.
  • The live event tail is best-effort, and says so here rather than in a footnote. An event's id is assigned at INSERT but only becomes visible at COMMIT, so a long transaction can commit a lower id after a higher one — and a live poll can miss the late arrival. That is acceptable for a live view, which is what it drives; durable delivery is the consumer-position model's job. Closing the window (overlap, then dedup) is a separate change, not yet built.
  • lm secret rm leaves a tombstone rather than deleting the row. Whether it should be a real delete is an open product decision, not an oversight — the tombstones are unbounded and the stored value stays decryptable, which is exactly why the decision is still open.

What we do not know yet

Everything above is knowledge — either a decision we made or a defect we can name. This section is the absence of knowledge, and it is the honest reason the word beta sits at the top.

lumnik has been deployed, driven end to end, and hammered hard — by the people who wrote it. No outside team has stood it up against their own ERP. That is the one thing no amount of bug-fixing replaces: the first defect an outsider finds will be one we could not have predicted, because the ones we could predict are already in the two lists above.

If you are that outsider, the guided path is three half-days, and it is the fastest way to hand us a defect we have never seen.

When the word goes away

Two things have to be true, and neither of them is a version number:

  1. What is not finished is empty.
  2. Someone outside this team has run lumnik in production.

Then beta disappears from the top of this page and the sentence underneath it stays. Nothing is renamed and no tag is re-pointed — published tags are immutable here by policy, so the version stream only ever moves forward. The word going away is the announcement.

See also