Cross-language Conformance Status
This page is generated from the committed TeaQL Conformance dashboard at
27f0999f8854. The snapshot was captured on
2026-09-28 from committed repository ref
origin/main; uncommitted design drafts are deliberately
excluded.
This is a capability and evidence snapshot, not a package-version table or a support-lifetime promise. Use Latest Versions for current generator and package coordinates, and Support Lifecycle for the distinction between tested and supported combinations.
How to read the status marks
| Mark | Meaning |
|---|---|
● | The current approved design is implemented for this cell |
◐ | The target design has been approved, but this cell is still migrating from an older or incomplete design |
○ | Planned capability; target contract is not yet implemented |
— | Not claimed or deliberately unsupported |
N/A | Intentionally not applicable |
✅ | Executable evidence passed for the stated version and environment |
⚠ | Executed with an open failure, skip, or material qualification |
❌ | Executed and failed |
UNVERIFIED | Source or design may exist, but retained execution evidence is absent |
Runtime execution rows use a second, deliberately separate vocabulary:
| Mark | Meaning |
|---|---|
| PASS | Retained executable evidence exists in the runtime repository |
| PARTIAL | The basic scenario passes, but part of the stated core contract is missing |
| GAP | The runtime does not implement the capability |
| UNVERIFIED | An implementation may exist, but retained executable evidence is absent |
Design marks such as ● and execution results such as PASS or ✅
answer different questions. A market tier also does not turn an unverified
capability into a verified one.
Language market tiers
| Market tier | Runtimes | Public positioning and operating policy |
|---|---|---|
| Tier 1 | Java, Rust, TypeScript | Lead languages in public campaigns, examples, reference applications, routine regression, release verification, and roadmap investment |
| Tier 2 | Swift, Python, .NET, Go | Supported cross-language runtimes; maintain semantic compatibility and published artifacts, with deeper examples, provider validation, and new investment driven by user or customer demand |
Tier 1 identifies the languages used most often in campaigns, examples, and routine release verification. Tier 2 runtimes remain supported cross-language targets; the tier does not weaken the shared semantic contract.
Runtime core capabilities
| Capability | Java | Rust | TypeScript | Swift | Python | .NET | Go |
|---|---|---|---|---|---|---|---|
| Runtime setup and provider wiring | PASS | PASS | PASS | PASS | PASS | PASS | PASS |
| Passive, composable Runtime Module installation | PASS | PASS | PASS | PASS | PASS | PASS | PASS |
Context-scoped explicit ensureSchema / ensure_schema | PASS | PASS | PASS | PASS | PASS | PASS | PASS |
SQLite soundex() registration during ensureSchema | PASS | PASS | PASS | PASS | PASS | PASS | PASS |
| Idempotent Default Domain Root bootstrap | PASS | PASS | PASS | PASS | PASS | PASS | PASS |
| Idempotent constant creation and reconciliation | PASS | PASS | PASS | PASS | PASS | PASS | PASS |
| Portable optimistic ID-space allocation | PASS | PASS | PASS | PASS | PASS | PASS | PASS |
| Aggregate-root Business ID Generator | PARTIAL | PARTIAL | UNVERIFIED | UNVERIFIED | UNVERIFIED | UNVERIFIED | UNVERIFIED |
| Business ID keyed permutation V1 + golden vectors | PASS | PASS | UNVERIFIED | UNVERIFIED | UNVERIFIED | UNVERIFIED | UNVERIFIED |
| Context-bound Round-Trip References | GAP | GAP | GAP | GAP | GAP | GAP | GAP |
| Q API: basic typed filter/order/projection/list query | PASS | PASS | PASS | PASS | PASS | PASS | PASS |
| Q API: typed page result | PASS | PASS | PASS | PASS | PASS | PASS | PASS |
| Q API: typed forward-relation loading | PASS | PASS | PASS | PASS | PASS | PASS | PASS |
| Mutation API: audited create | PASS | PASS | PASS | PASS | PASS | PASS | PASS |
| Mutation API: fully loaded audited update | PASS | PASS | PASS | PASS | PASS | PASS | PASS |
Mutation API: markForDeletion + atomic mixed graph save(context) | PASS | PASS | PASS | PASS | PASS | PASS | PASS |
| Entity Mutation Ledger isolation | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
| Optimistic version check and authoritative returned version | PASS | PASS | PASS | PASS | PASS | PASS | PASS |
| E API: typed scalar evaluation | PASS | PASS | PASS | PASS | PASS | PASS | PASS |
| E API: typed forward-relation traversal | PASS | PASS | PASS | PASS | PASS | PASS | PASS |
| E API: loaded-null versus not-loaded distinction | PASS | PASS | PASS | PASS | PASS | PASS | PASS |
| Checker runs before provider/SQL mutation | PASS | PASS | PASS | PASS | PASS | PASS | PASS |
| Checker returns a structured field-specific location | PASS | PASS | PASS | PASS | PASS | PASS | PASS |
| Fix participates in the normal save lifecycle | PASS | PASS | PASS | PASS | PASS | PASS | PASS |
| Mandatory audit intent on mutation | PASS | PASS | PASS | PASS | PASS | PASS | PASS |
| Mandatory Comment and Purpose on query | PASS | PASS | PASS | PASS | PASS | PASS | PASS |
These rows summarize retained executable behavior for the shared runtime lifecycle. Provider-specific depth and released-package verification remain separate evidence dimensions.
Query capability alignment
| ID / capability | Java | Rust | TypeScript | Swift | Python | .NET | Go | TFP v1 |
|---|---|---|---|---|---|---|---|---|
QRY-P01 equality and inequality | ● | ● | ● | ● | ● | ● | ● | ● |
QRY-P02 set and negative set | ● | ● | ● | ● | ● | ● | ● | ● |
QRY-P03 ordered comparison | ● | ● | ● | ● | ● | ● | ● | ● |
QRY-P04 between | ● | ● | ● | ● | ● | ● | ● | ● |
QRY-P05 contains and negative contains | ● | ● | ● | ● | ● | ● | ● | ● |
QRY-P06 starts/ends and negative forms | ● | ● | ● | ● | ● | ● | ● | ● |
QRY-P07 known/unknown | ● | ● | ● | ● | ● | ● | ● | ● |
QRY-P08 boolean true/false/unknown | ● | ● | ● | ● | ● | ● | ● | ● |
QRY-P09 provider-aware sounding-like | ● | ● | ● | ● | ● | ● | ● | ◐ |
QRY-R01 forward relation matching | ● | ● | ● | ● | ● | ● | ● | ◐ |
QRY-R02 constant semantic predicates | ● | ● | ● | ● | ● | ● | ● | ◐ |
QRY-R03 reverse relation matching | ● | ● | ● | ● | ● | ● | ● | ◐ |
QRY-S01 typed projection and ordering | ● | ● | ● | ● | ● | ● | ● | ◐ |
QRY-S02 group-by and portable aggregates | ● | ● | ● | ● | ● | ● | ● | ◐ |
QRY-S03 relation count and portable statistics | ● | ● | ● | ● | ● | ● | ● | ◐ |
QRY-X01 per-parent Top-N relation semantics | ● | ● | ● | ● | ● | ● | ● | ◐ |
QRY-X02 continuous pagination | ● | ● | ● | ● | ● | ● | ● | ◐ |
QRY-X03 retained ID-set pagination | ● | ● | ● | ● | ● | ● | ● | ◐ |
QRY-F01 typed relation Facet API | ● | ● | ● | ● | ● | ● | ● | ● |
QRY-F02 Facet filter semantics | ● | ● | ● | ● | ● | ● | ● | ● |
QRY-F03 Facet result carrier | ● | ● | ● | ● | ● | ● | ● | ● |
The language columns describe the generated native API families. The TFP column describes the portable wire subset and may intentionally lag native runtime APIs.
Generated workspace targets
| Runtime | Library/core | Console application | Web/server | App/mobile |
|---|---|---|---|---|
| Java | java-lib-core | java-app-console | java-web-spring-boot, java-web-micronaut, java-web-quarkus | — |
| Rust | rust-lib-core | rust-app-console | rust-web-axum, rust-web-topcoat | — |
| TypeScript | typescript-lib-core | typescript-app-console | typescript-web-hono | typescript-app-expo |
| Swift | swift-lib-core | swift-app-console | — | — |
| Python | python-lib-core | python-app-console | python-web-fastapi | — |
| .NET | dotnet-lib-core | dotnet-app-console | dotnet-web-aspnet | — |
| Go | golang-lib-core | golang-app-console | golang-web-gin | — |
A listed target is selectable generator output. It becomes verified only after its generated workspace passes the relevant build and runtime gates.
TeaQL Federal Protocol roles
| TFP role/evidence | Java | Rust | TypeScript | Swift | Python | .NET | Go |
|---|---|---|---|---|---|---|---|
| Client | — | — | ● | ● | ● | — | — |
| Server endpoint | ● | ● | — | — | — | ● | ● |
| Executable role conformance | ● | ● | ● | ● | ● | ● | ● |
| Retained cross-language execution evidence | ● (TS client) | ● (TS client) | ● (Java/Rust) | ● (Rust) | ● (Java/Rust) | — | — |
Client and server roles are intentionally separate. Cross-language execution evidence is narrower than the existence of a client or endpoint implementation.
Refresh procedure
From the site repository, with a local conformance checkout available:
npm run sync:conformance -- --source ../teaql-conformance --ref origin/main
npm run check:conformance-snapshot
The sync command defaults to git show HEAD:README.md. When a checkout has
local work, maintainers may pass an already fetched committed ref such as
--ref origin/main; working-tree drafts are never read. Review the source
commit and generated diff before publishing.