sensor.bytes

Version: 1.0.0 baseline
Status: Offline-first engineering prototype
Primary record contract: HYPERSENSOR_WAVE_V1

Purpose

sensor.bytes is a local software foundation for versioned sensor records,
measurement metadata, payload integrity checks, and a verifiable JSON Lines
event history.

It supports the Hyper Architecture as a proposed software model:

• Hypertext — identifiers and references
• Hypermedia — associated representations
• Hypersensor — measurement records and provenance
• Hypersignal — abstract signal and timing metadata
• HyperByte — encoding, validation, and integrity

These are project architecture concepts, not claims of compatibility with
an operational military data link or external system.

Evidence boundary

Records distinguish OBSERVED, DERIVED, SIMULATED, and VISUALIZED.

A passing software test demonstrates behavior for the test input and
conditions. A SHA-256 digest checks byte consistency against a digest; it
does not prove the identity of a sensor, authenticity of origin, or truth
of a measurement.

The included example uses synthetic data and is explicitly marked
SIMULATED.

Requirements

• Python 3.13 or a compatible Python 3 runtime
• No third-party packages required for the core code or test suite
• No live network or physical sensor required

Run locally

From the repository root:

PYTHONPATH=src python -m unittest discover -s tests -v

Run the synthetic example:

PYTHONPATH=src python examples/hypersensor_wave_example.py

Check that the schema is valid JSON:

python -m json.tool schemas/hypersensor-wave-v1.json

Package modules

• integrity.py — SHA-256 digest creation and comparison
• records.py — record creation, field validation, measurement checks,
  evidence classes, and payload validation
• timing.py — local stage-duration measurement using a monotonic clock
• ledger.py — local JSON Lines events and hash-chain verification
• schemas/hypersensor-wave-v1.json — versioned record contract
• docs/ — criteria, acceptance plan, traceability, and implementation limits
• tests/ — standard-library automated tests

Ledger limitations

The ledger is a local tamper-evident hash chain, not an immutable database.
It has no digital signatures, external witness, authenticated sensor
identity, or concurrent-writer coordination. Verification rejects an
incomplete final line; automatic crash recovery is not implemented.

The schema tests currently check selected contract invariants. They do not
execute a full JSON Schema Draft 2020-12 validator, so complete
schema/runtime parity remains unproven.

Engineering criteria

The independent baseline defines criteria C01-C08 in
docs/CRITERIA-FOUNDATION-V1.md. It draws on public discussion of integration,
timing, resilience, accountability, and degraded conditions, but is not a
government requirement, approved architecture, or endorsement.

See docs/REQUIREMENTS-TRACEABILITY-V1.md for current verification status
and outstanding evidence.

Scope exclusions

This prototype does not implement live telemetry, military network
integration, Link 16 protocol compatibility, hardware control, weapon
tasking, production key management, or operational deployment.