Integration Seams

Infrastructure crosses repository, receiver, signal, core, and command boundaries. Each seam must add typed repository meaning without taking ownership of the underlying science.

Trust Crossings

flowchart LR
    files["repository files and sidecars"]
    dataset["typed dataset"]
    profile["maintained receiver profile"]
    variant["typed variant"]
    context["declared run context"]
    footprint["deterministic run footprint"]
    artifact["persisted artifact"]
    review["inspection or reference review"]

    files --> dataset
    profile --> variant
    dataset --> context
    variant --> context
    context --> footprint
    footprint --> artifact
    artifact --> review

Seam Contracts

seam	accepted input	output and refusal
dataset registry	registered identity plus repository metadata	typed dataset with provenance, or a specific missing/invalid-field error
raw-IQ sidecar	explicit format, sample rate, intermediate frequency, offset, and timestamp context	validated metadata, or refusal to infer absent capture facts
override and sweep	maintained profile plus typed parameter names and values	deterministic variants, or rejection of unsupported mutation
run identity	command, profile, dataset, version, feature, and replay context	deterministic directories and provenance fingerprint, or invalid-context refusal
persistence	typed manifest, report, history, and artifact records	governed files with explicit schema versions, or visible write failure
artifact inspection	known artifact kind, payload version, and read policy	typed explanation or validation result, never silent acceptance
reference adaptation	persisted evidence and explicit reference context	comparison-ready values or a typed prerequisite failure

Implementation Owners

• Dataset resolution owns registry and sidecar trust.
• Typed overrides and sweep expansion own reproducible variants.
• Run layout owns identity, paths, persistence, records, and provenance.
• Artifact inspection owns schema policy and later review.
• Reference adaptation bridges evidence into comparison without owning scientific truth.

Boundary Failures

• Commands must not construct run paths or manifests independently.
• Receiver code must not discover datasets or write repository histories.
• Inspection must not repair invalid artifacts while reading them.
• Reference adapters must not invent truth, tolerances, or missing provenance.
• Convenience re-exports are not permission to move receiver or signal behavior into infrastructure.

The architecture guide maps these seams to package ownership, and the release guide defines compatibility for persisted behavior.