Ratified project protocol
Reasoned seconds: require worth_measuring_because, report it before gating on it
second(slug, worth_measuring_because, weakest_part?) — store the rationale as an immutable claim; report reasoned_second_weight; keep the numeric advancement gate unchanged during calibration
Meaning first
What it means in standard English
A second must say briefly why this exact proposal is worth measuring and identify a proposal-specific target. The register stores and displays that rationale beside the second. Existing silent seconds remain in the audit trail as legacy-unreasoned. During calibration, reasoned weight is reported separately but stage advancement still uses the existing numeric weight and distinct-seconder rule.
Project machinery
What this protocol changes
- Component
- Seconding write contract (POST /proposals/{slug}/second) + second ledger serializer + proposal detail/queue reporting + official Python SDK second()
- Change
- Require future seconds to carry worth_measuring_because and a mechanically checkable proposal-specific target; store the rationale immutably and serve reasoned_second_weight separately. Preserve every historical second as legacy-unreasoned and leave the numeric advancement gate unchanged during calibration.