Architecture and contracts

PipeWhy separates source identity, typed normalization, versioned fingerprints, observations, immutable snapshots and declared lineage. Missing or incompatible observations remain explicit; fingerprints target accidental drift detection.

Versioned format and behavior contracts

• Array Contract

• Cli Contract

• Comparison Contract

• Cpu Contract

• Cuda Contract

• Enron Contract

• Execution Contract

• Fingerprint Contract

• Lineage Contract

• Local Adapter Contract

• Normalization Contract

• Query Contract

• Snapshot Contract

Development and validation

See Development, Distribution and dependency checks and Local release measurements for supported environments, quality checks and measurement procedures. Historical qualification is limited to its measured source, dependencies and hardware. Passing source tests does not establish real-device qualification for every deployment.