Module Map

Enter bijux-gnss-infra through the repository object being interpreted. The crate contains several filesystem-facing subsystems, but each has a distinct contract: registered input, run footprint, persisted artifact, experiment variation, provenance, or reference comparison.

flowchart TD
    caller["command, test, or tool"]
    api["curated infra API"]
    inputs["datasets and sidecars"]
    runs["run identity and records"]
    inspect["artifact inspection"]
    variation["overrides and sweeps"]
    provenance["hashing and provenance"]
    reference["reference alignment"]

    caller --> api
    api --> inputs
    api --> runs
    api --> inspect
    api --> variation
    api --> provenance
    api --> reference

Choose A Repository Route

question	owning subsystem	what belongs there
How does a registry entry become a normalized capture?	Dataset registry	entry parsing, registry loading, and relative-location resolution
Which raw-IQ metadata source wins, and what must it contain?	Raw-IQ metadata	sidecar loading, source precedence, cross-source agreement, and required-field validation
How is an execution named and placed?	Run directories and identity and run identity	deterministic identity, output and resume precedence, and typed locations
What execution context survives after a run?	Persisted run records	reports, manifests, history, artifact headers, and build metadata
What provenance is needed for comparison or replay?	Run provenance and provenance hashing	replay scope, front-end context, config identity, Git state, and feature inventory
How is an existing JSONL artifact interpreted?	Artifact inspection	kind detection, explanation, schema policy, payload diagnostics, and sequence checks
How does declared experiment variation become receiver configuration?	Override application, experiment records, and sweep expansion	typed mutation, accepted parameter policy, and Cartesian case expansion
How are persisted solutions paired with reference epochs?	Reference alignment adapter	repository-facing alignment and empty-result refusal
How does a command establish the standard footprint and artifact header?	Run preparation	composition of existing infra contracts, not command policy

Public Boundary

The curated infra API is the only downstream entrypoint. The crate boundary keeps the subsystems private and prevents callers from depending on internal layout.

Small coordinate parsing support lives in the infrastructure parser, but a new parser belongs there only when it serves a repository contract rather than a product format.

Boundary Tests

• Dataset code owns identity and metadata interpretation, not signal quality.
• Run layout owns placement and context, not receiver outcomes.
• Artifact inspection owns post-run diagnostics, not producer correctness.
• Overrides own typed application, not receiver defaults or command policy.
• Reference alignment owns pairing, not navigation accuracy.

Use Integration Seams for cross-package questions and Run Footprint Contracts before changing persisted run behavior.