In modern software engineering, there is a systemic issue: documentation and product marketing frequently blur the line between intended features, architectural designs, and verified execution facts.
At Bennu Labs, we enforce a strict separation between ProductTruth and the Proof Layer. Publishing an architectural concept or describing a planned module does not imply the automatic existence of a live runtime or verified operational telemetry.
The ProductTruth layer defines how a product is designed, its functional scope, and its operational boundary. Conversely, the Proof Layer contains strictly snapshot-verified evidence (logs, telemetry, check states) captured directly from an operator or test environment.
This distinction prevents overclaims and ensures that engineering teams and buyers always perceive a clear boundary between planned functionality and proven capability.