Governance & compliance

Protected system records

Stops a caller of the ordinary data routes from reading or rewriting the records the server uses to control itself.

Available in previewEngine edition 5f8ea3af

What it does

The server keeps its own control state as records in the same engine: the audit key and checkpoint, role bindings, residency and security policies, organisation membership projections, API token verifiers, approvals, queues and more. The generic read and write routes refuse these kinds under every tenant spelling, and the refusal does not depend on whether the target exists.

How it works

One classification in the engine decides which record kinds are write-protected, and which of those are also hidden from reads, listings, searches, the operator console and the change feed. The generic routes (entities, transactions, table inserts and upserts, collection records, imports and the transaction envelope) consult it before any lookup. A refused write returns the same typed error whether the target is present, absent or unreadable, so the response says nothing about what sits at the id. Trusted subsystems write their own records through guarded engine calls that stay open to them.

A test scans the source tree and fails when a new record kind is introduced without being classified, so a new subsystem cannot add an unprotected kind silently. Reserved id ranges, for queue, control-plane and managed-database ids, are refused on their own before any record lookup.

Where you reach it

  • HTTPApplies to POST /v1/entities, POST /v1/transactions, /rest/v1/:table, /v1/collections/:name/records and the import paths

Limits

  • Protection applies to the generic data routes. Credentials with platform authority, and the trusted code paths of the server itself, still write these records through their own routes.
  • The classification is maintained by hand and checked by a test that scans source text. It is a guard rail and not a proof.

Evidence

  • On this siteSecurity overview
  • Tests92 tests across the guards (forged role bindings and policies refused, reserved ids refused uniformly, audit key and checkpoint unreadable, outbox and approval rows protected, every record kind in the workspace classified)

Test coverage is listed as present in the engine repository at this edition. This page does not report test results.

KynetraDB is in private preview

Request a preview to try this against your own workload.