TR-PINK-F-015 / Teal / Review draft

Request memory

Terminology revised · September 12 evidence

Later individual Teal rerun. The reported execution status is historical and is not a new test result.

TEAL LIBRARY RERUN  |  12 SEPTEMBER 2026  |  Michael Patrick Bangel
36
TEAL-RERUN-02-B002 | SCOPED_EXECUTION_VERIFIED
TR-PINK-F-015 / Request memory
IF
Invoke F-015 with exactly these inputs: rate: Real, bytes_per_request: Real, latency: Real. Real values use
finite decimal text; null remains unknown.
HOW
Source expression: M_request = lambda_hat * bytes_per_request * latency_hat. Current Bangel expression:
rate * bytes_per_request * latency. Require every input to be known. Require rate >= 0.0 and
bytes_per_request >= 0.0 and latency >= 0.0.
THEN
Emit the scoped calculation result. Missing inputs produce their specific PINK_MISSING_* HOLD; failed profile
checks produce PINK_DOMAIN. A false numeric predicate can occur in a PASS calculation receipt; it is not
permission.
CURRENT EVIDENCE
Fixture inputs {"rate": "10", "bytes_per_request": "100", "latency": "2"}; expected 2000. Result matched
through Bangel, admitted JP, the Bangel API, with validated receipt outputs. 3 missing-input cases and 0
supplied domain cases passed.
SOURCE DIMENSION
bytes
REMAINING REQUIREMENT
Complete the source-defined measurement/evidence contract, units and calibration bindings. Native C# and Hagar formula-ID
bindings remain unverified in this rerun.
SOURCE REFERENCES
D006 pp. 45,46; D011 pp. 35,36
Evidence: evidence/rerun/pink/F-015.json

Publication is pending owner review. White papers are excluded.