Skip to content

Package Overview

bijux-gnss-infra exists to make repository-facing GNSS state typed, repeatable, and inspectable.

Its job is not to be "the place where repository things go." Its job is to own the repository contracts that more product-facing crates should consume instead of reimplementing.

Role Model

flowchart LR
    repo["datasets configs artifacts histories"]
    infra["bijux-gnss-infra"]
    consumers["gnss receiver nav testkit maintainers"]

    repo --> infra --> consumers

If the repository needs one stable interpretation of datasets, run identity, artifact persistence context, profile overrides, or provenance hashing, this is usually the crate that should own it.

The durable centers of gravity are:

  • dataset registry source for dataset lookup and entry parsing
  • raw-IQ metadata source for sidecar loading, sample metadata, and capture validation
  • run-layout source for run identity, directories, persisted records, and provenance capture
  • artifact inspection and validation-adapter source for repository inspection workflows
  • override, experiment, sweep, and hashing source for typed variation, override application, and provenance helpers

Boundary Verdict

If the work makes repository state more typed, reproducible, or auditable without becoming runtime or solver policy, it belongs here. If it starts deciding signal processing, navigation estimation, receiver scheduling, or command UX, it has crossed the boundary.

What This Package Makes Possible

  • commands and tests can rely on one dataset registry interpretation
  • persisted run footprints stay stable after the command that produced them is gone
  • experiment variation stays typed instead of becoming shell string handling
  • artifact inspection can happen after execution without re-entering runtime code

Tempting Mistakes

  • putting receiver defaults into overrides because they are "config related"
  • storing repository layout policy inside artifact payload definitions
  • making command semantics responsible for dataset resolution rules that should be shared everywhere

First Proof Check

Inspect curated public API source, dataset registry source, raw-IQ metadata source, run-layout source, receiver-profile override source, sweep source, and artifact-inspection source. Use the infra contract guide as the reader-facing map before trusting an ownership claim.