What it does
Not wired into request handling in this release. The decision engine exists as a library and is used by the policy-as-code checker, but the server does not call it when it authorises a request.
How it works
The engine answers decide(policy, subject, action, resource, context) with allow or deny and reasons. It denies by default, applies tenant isolation first, refuses stale device or workload claims, consults residency placement, requires a declared purpose for personal data, lets an explicit deny beat any allow, and treats a missing or unparsable attribute as a denial. It reuses the row-level security language for record predicates. A pre-read variant answers allow, deny or depends-on-record before any record is fetched.
Today the engine runs inside kynetra policy check, where it judges the access section of a policy file against probe requests. Request handling in the server uses collection role rules, row-level policies and the permission overlay instead.
Limits
- Not reachable as a request-time authoriser in this release.
- Purpose-based access is available today through row-level policies that call auth.purpose() with the X-Kynetra-Purpose header.
Evidence
- On this siteAvailable now: row-level security
- Tests58 library tests exist (default deny, tenant isolation, purpose, stale claims, deny precedence, pre-read decisions); none run through the server
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
This is not available in the preview. Request a preview to discuss the current scope.