§03-i Minerva — Semantic Binding — Inspector verification (property table)
Mars® Spec › §03-i Minerva — Semantic Binding › Inspector verification (property table)
4. Inspector verification (property table)
The following properties are externally observable by a qualified inspector without access to internal system state.
| Property | Observable indicator | Load-bearing |
|---|---|---|
| S1 Domain-aspect binding | Semantic-map artifact shows fields bound to map aspects, not only to ontology classes or free-text descriptions | Yes |
| S2 Aspect-keyed, fitness-scored query library | Library entries are keyed to domain aspects and carry sample-data fitness signals, not per-utterance NL→query pairs | Yes |
| S3 Multi-locus gap report | Gap report carries events at data, domain-model, KB, and specification loci, including cross-locus events | Yes |
| S4 Reverse-path through domain aspect | Request → aspect → semantic map + library → fitness-ranked selection; not direct request-to-query generation | — |
| S5 Substrate uniformity | Downstream artifacts are structurally identical across store kind, characterization representation, and federation topology | Yes |
| S6 Governed structural characterization | For a non-self-documenting source, characterization is produced by a domain-model-directed two-phase procedure, not by generic schema introspection | — |
| S7 Plural data source input | Semantic binding accepts multiple data sources simultaneously; semantic-map artifact and query library span all sources jointly | Yes |
| S8 Dual-contract admission | A data source is admitted if it satisfies the admission criterion appropriate to its client class: the connect/traverse/query contract (non-embedded) or the connect/encode/decode contract plus subchunk commitment (embedded); store type alone is not an admission criterion | Yes |
| S9 Non-embedded / embedded client class distinction | Non-embedded sources are accessed through a Pymnemon-conforming client (connect/traverse/query contract); embedded sources through an Impera-conforming client (connect/encode/decode + subchunk commitment); the two are structurally distinct and observably non-interchangeable | Yes |
| S10 Subchunk-level retrieval commitment | The embedded client returns the best-match subchunk, not the enclosing chunk; the returned span is narrower than the chunk and carries its own subchunk identifier; chunk-level retrieval is only used when declared explicitly | Yes |
| S11 KB traversal in query generation | Query library entries produced with KB traversal input carry KB-sourced contextual metadata (what/why/when/how) distinct from entries produced from domain mapping alone | — |
| S12 Simple-query composition | A set of single-table queries bound to one domain aspect may stand in for a composite query over the same tables; the library carries both strategies with distinct construction-strategy labels | — |
| S13 Time-gated query entry | A query entry carrying a temporal gate is refused as evidence when executed outside its declared gate; a time-gate-miss is recorded in the gap report | Yes |
| S14 Reverse-path activation record | A downstream verification operation that consumed query library entries carries a reverse-path activation record in its evidence component; the record names the activated domain aspect(s), selection rationale, and governing upstream versions | Yes |
| S15 Structural characterization procedure | For a non-self-documenting source, a two-phase structural inventory and upward interpretation produces the characterization; name-quality assessments and unresolved low-quality fields are recorded; unresolved fields emit data locus gaps | — |
| S16 Versioned upstream binding | Each semantic-map entry and query library entry carries the upstream domain-model version, data-source characterization version, and KB version (if applicable) from which it was derived; staleness is determinable by version comparison without re-derivation | Yes |