db-tests-prag

The groupant beside tools/db/tests/prag.rs in the Mova repository: what the code computes, what it never does, how to go back from its outputs, its invariants, cost and checks.

Facts

Implementation material. A Mova code model describes this code at one source revision: partial models, finite checks and their stated scope. It is not a reviewed general exposition, and its labels are shown as written, never raised.

Components

component	label	where
approximant	partial	approximant
ast	partial	`syntax.json`
cost	partial	invariant-and-cost
descriptant	present	descriptant
invariant	partial	invariant-and-cost
tests	bounded checks partial scope	tests

Obernants

The typed relations around the forward model: the behaviour complement (what the code never does), the reverse reconstruction (every input compatible with an output) and specialised views.

id	type	label	where
`behavior_complement`	behavior_complement	partial source derived model	behavior_complement
`reverse_reconstruction`	reverse_reconstruction	partial source derived model	reverse_reconstruction
`prag_fixture_identity`	prag_fixture_identity	partial source derived model	prag_fixture_identity
`negative_control_scope`	negative_control_scope	partial source derived model	negative_control_scope
`null_trace_observation`	null_trace_observation	partial source derived model	null_trace_observation
`executable_dependency`	executable_dependency	partial source derived model	executable_dependency

Model text

descriptant

Pragmatic database fixture and assertions

Legacy integration fixture initializes temp DB, loads two sentences, migrates, inserts pragmatic labels and checks view values, then rejected duplicate/missing/invalid-bit/header attempts preserve counts. New representation check only parses TEXT into two CoNLL sentences, checks nine header columns and byte roundtrip.

Prospective epoch — 2026-10-31

Full source was reviewed before edits; external prospective.md records API states, failure order and predicted checks. Production prefix remains byte-identical; test additions are isolated cfg(test)/test items.

Observed epoch — 2026-10-31

2026-10-31 wave31: 16 selected target/name cases passed twice debug and twice release with identical sorted outcomes; six compiled source-behavior mutants failed assertions, exact bytes restored and positive checks passed. Evidence scope is only the named helpers/fixtures. External receipt directory: $MOVA_DATA/runs/octopus-wave31-store-2026-10-31. No DuckDB integration, production loader/corpus, training or GPU run.

Retained limitations

No SQL evaluation was substituted with a mock process. Missing DuckDB is a dependency gap, not passing database evidence. Partial syntax has no macro expansion/name resolution/types; Rust helpers and fixtures do not prove all models.

approximant

Pragmatic database fixture and assertions forward relation

Domain

Finite valid-UTF8 inputs, representable counters/IDs, available memory; filesystem fixtures confined to owned temporary root. SQL semantics are conditional and unexecuted. Subject is the source and SHA256 bound in manifest; fragment applies only to declared byte range.

Approximation limits

Categorical parsing, exact identity, transactional effects and resource errors have no useful percentage approximation metric here. No executable surrogate is claimed. Future profiles, if justified, may use only 1%, 2%, 5%, 10% with a defined metric/reference/domain.

models

Pragmatic database fixture and assertions typed model catalog

Observation is one call/trace in the declared scope. Operators below are partial source-derived relations; complement is a proposed inner exclusion relation, reverse an outer compatible-antecedent relation retaining ambiguity. No universal proof follows from finite checks. Each oracle is the relevant named helper check below when it reaches the behavior; remaining SQL/effect cases are source review or proposed real-CLI checks.

behavior_complement

Fixture-only success excludes malformed CoNLL/changed ID/header-width observations covered by assertions; it cannot exclude SQL constraint bugs. Legacy intended relation excludes count growth after rejected loads, but remains unexecuted.

Domain/assumptions: Finite valid-UTF8 inputs, representable counters/IDs, available memory; filesystem fixtures confined to owned temporary root. SQL semantics are conditional and unexecuted. Subject is the source and SHA256 bound in manifest; fragment applies only to declared byte range.