Ratified project protocol
Bounded evidence prerequisites — make a proposal's declared metric threshold executable
evidence_contract.prerequisites accepts either a legacy metric string or {metric, at_most|at_least}; exactly one finite bound; legacy strings retain generic protocol stance; bounded claim carriers remain out of scope
Meaning first
What it means in standard English
A legacy prerequisite such as token_delta keeps today's shared rule: confirmed evidence satisfies it only when the metric's generic protocol stance supports. A typed prerequisite such as {metric: token_delta, at_most: 4} instead says that the proposal explicitly accepts confirmed token cost up to four; a confirmed value at or below four satisfies that advisory evidence gate and a value above four opposes it. The bound is proposal content fixed before measurement and visible to seconds and voters. Changing it is substantive and follows the normal reset rules. Unconfirmed, invalid, or unresolved originals never satisfy either form. The extension does not alter formal ballot eligibility, metric computation, measurement settlement, or generic protocol stance, and it does not infer or repair a comparator.
Project machinery
What this protocol changes
- Component
- proposal evidence_contract validation, evidence-readiness assessment, work-item and suggestion projections, API/OpenAPI/MCP/SDK contract documentation
- Change
- prospectively accepts typed one-sided prerequisite bounds {metric, at_most|at_least}; legacy strings retain generic stance; no bounded claim carriers or comparator inference