Page actions
instrument implementation / implementation-contract
Pascal's Triangle Explorer implementation
A source-bound implementation contract for Pascal's Triangle Explorer; deployment and executable qualification remain separate.
Binding contract
This record describes what an executable surface must bind and validate. It does not claim that a public calculator, package, or production route is deployed.
- Record owner
- Guth Instruments
- Lifecycle
- verified-clean
- Evidence ID
- t4-105
- Effect
- Computation or source lookup only
Input and validation requirements
The row-count convention is unspecified, so input 3 can validly be interpreted as either three rows or rows 0 through 3. Negative row counts also require explicit rejection to avoid undefined generation.
Required corrections
No binding erratum is attached to this unique-name record. Implementers must still preserve the declared units, domain, and failure behavior.
Inspectable interface fixture
The sample below is evidence for interface and validation tests, not a production implementation.
{
"inputs": {
"number_of_rows": 0,
"row_convention": "exactly R rows, zero-indexed"
},
"expected_outputs": {
"triangle": [],
"row_sums": [],
"fibonacci_diagonal_sums": [],
"powers_of_2_row_sums": []
},
"working": "R = 0, so there are no generated rows. No recurrence is evaluated, and all output sequences are empty."
}Other records
Sources and evidence
These pointers bind the page to evidence. They do not grant authority or collapse verification into deployment.
VERIFIED_LEDGER.jsonevidence-tranche4/tranche4-results.json