Use this page for Ptah product, workflow, database-support, and compatibility
terms. Where a dense table cannot carry a definition, the same entry appears as
an inline ⓘ: focus it with Tab or tap it, and press Esc to
dismiss.
Definitions come from one source, docs/site/src/glossary.ts, so the same term
cannot come to mean two things on two pages.
desired-schemadesired-schemaThe schema state Ptah is asked to reach, assembled from one or more schema sources before it is compared with a database.core/schemamodel/types.go
the state a workflow is trying to reach
schema-sourceschema-sourceOne input that contributes to a desired schema, such as Go annotations, HCL, YAML, SQL, a database, or an external loader.core/schemasource/schemasource.go
one input contributing to that state
migration-directorymigration-directoryAn ordered set of migration files plus its integrity metadata. Ptah plans, validates, applies, and rolls back the directory as history.migration/migrationfile
ordered migration history and its integrity metadata
revisionrevisionThe migration history state recorded in the target database: which version was applied, when, and with which integrity metadata.migration/migrator/revision_table.go
applied migration state recorded in the database
driftdriftA difference between the desired schema and the state Ptah reads from the target database.migration/schemadiff
a difference between desired and live state
dev-databasedev-databaseA disposable database Ptah may reset and replay into while materializing schema state or planning a change. It is not the migration target.migration/internal/shadowdb
a disposable database used to materialize or plan state
shadow-databaseshadow-databaseA disposable database used to verify that migrations reproduce the intended schema and that rollback behaves as planned.migration/shadow
a disposable database used to verify migrations and rollback
throwaway-databasethrowaway-databaseA database supplied specifically for destructive tests or examples, with no state the operator needs to preserve.cmd/schema
a database created for destructive tests or examples
measuredmeasuredThe row was executed against a server on this exact release line, and the answer here is what that server said.core/platform/capability/capability_measured_lines_test.go
the capability matrix
a ✅ looks the same whether a server on that line answered or the value came from the line below
carriedcarriedNo server on this line answered for the key. The value is inherited from the preset the line resolves to, and the reason is recorded beside it.core/platform/capability/capability_measured_lines_test.go
the capability matrix
as above, from the other side
certifiedcertifiedA release line the capability probe runs against on every pull request, so its preset is checked by a server rather than by a paragraph.internal/capabilityprobe/cells.go
the release-line table
the level is a word; what earns it is a probe run
best-effortbest-effortA release line Ptah supports without a server in the probe matrix. Its preset is transcribed from measurement rather than re-measured on every run.internal/capabilityprobe/cells.go
the release-line table
reads as a hedge, and is a statement about who re-measures it
legacy-testedlegacy-testedA release line past its upstream end of life that Ptah still tests. End of life lowers the support level, not the behavior.internal/capabilityprobe/cells.go
the release-line table
end of life lowers the level, not the behavior
known-incompatibleknown-incompatibleA release line with a named technical incompatibility. Upstream end of life by itself does not make a line incompatible.core/platform/capability/support.go
the release-line policy
the incompatibility has to be named rather than inferred from age
dialectdialectThe SQL and database family Ptah parses and renders for. A dialect selects a family; capabilities decide which constructs one target accepts.core/platform/constants.go
commands, schema sources, and engine guides
a family name does not state every target capability
capabilitycapabilityA measured or declared property of a database target that gates one schema construct or behavior independently of the dialect name.core/platform/capability/capability.go
plans and server profiles
each key answers one behavior independently
release-linerelease-lineA version family Ptah declares as one support and capability measurement cell, such as PostgreSQL 17 or MySQL 8.4.internal/capabilityprobe/cells.go
generationgenerationOne immutable identity for an embedding model, preprocessing contract, target layout, and the vectors produced under that contract.cmd/inference
one embedding contract and the vectors produced under it
candidate-generationcandidate-generationA generation being prepared, backfilled, indexed, and verified while queries still read the active generation.cmd/inference
the generation being built while queries use another
cutovercutoverThe explicit, digest-approved state transition that moves the query pointer from the active generation to a verified candidate.cmd/inference
the approved transition of the active query pointer
conformanceconformanceExternal measurement of Ptah against a pinned comparison surface. Registered commands or internal tests alone are not conformance evidence.stokaro/ptah-atlas-conformance
measurement against a pinned external surface
contourcontourOne measured corpus of the conformance repository, with its own report and its own budget file: the offline fixtures, the live round-trip, the Atlas CE differential, the migrate runtime, and the CLI surface. Each is gated on its own.stokaro/ptah-atlas-conformance: gaps.md, gaps-live.md, gaps-diff.md, gaps-migrate-runtime.md, cli-surface.md
one independently reported conformance corpus
regression-budgetregression-budgetA gate that fails when a report exceeds the committed budget for its contour, or when a waiver no longer matches a finding. Green means nothing regressed, not that the contour is covered.stokaro/ptah-atlas-conformance: make budget, gap-budget.txt
the merge gate for one contour’s known findings
full-conformancefull-conformanceA gate that regenerates its report and fails if any non-OK observation remains, waived findings included. It is the yardstick rather than the merge gate.stokaro/ptah-atlas-conformance: make gate, .github/workflows/full-conformance.yml
the zero-finding yardstick rather than the merge budget
This is the case the affordance is most likely to break, so it is exercised
here rather than assumed. The table below is five columns wide and scrolls
horizontally on a phone; every cell in the last column carries a term. The
exampledb rows are fictional and do not state current Ptah support.
Dialect
Line
Support
Probe
Note
exampledb
99.1
certifiedcertifiedA release line the capability probe runs against on every pull request, so its preset is checked by a server rather than by a paragraph.internal/capabilityprobe/cells.go
every pull request
measured on this linemeasuredThe row was executed against a server on this exact release line, and the answer here is what that server said.core/platform/capability/capability_measured_lines_test.go
exampledb
98.0
legacy-testedlegacy-testedA release line past its upstream end of life that Ptah still tests. End of life lowers the support level, not the behavior.internal/capabilityprobe/cells.go
every pull request
measured on this linemeasuredThe row was executed against a server on this exact release line, and the answer here is what that server said.core/platform/capability/capability_measured_lines_test.go
exampledb
97.0
best-effortbest-effortA release line Ptah supports without a server in the probe matrix. Its preset is transcribed from measurement rather than re-measured on every run.internal/capabilityprobe/cells.go
none
carried from 98.0carriedNo server on this line answered for the key. The value is inherited from the preset the line resolves to, and the reason is recorded beside it.core/platform/capability/capability_measured_lines_test.go
exampledb
96.0
known-incompatibleknown-incompatibleA release line with a named technical incompatibility. Upstream end of life by itself does not make a line incompatible.core/platform/capability/support.go
none
carried from 97.0carriedNo server on this line answered for the key. The value is inherited from the preset the line resolves to, and the reason is recorded beside it.core/platform/capability/capability_measured_lines_test.go
Add it to docs/site/src/glossary.ts, then use <GlossaryTerm term="…" />. A
term with no entry there is a build error rather than a silent blank, so a
typo cannot ship as an empty tooltip.
