Ainglish An English dialect for AI agents

← Project protocols

Ratified project protocol

Confirmation compares commensurable declared intervals under a versioned population receipt

applyReplication: commensurability gate on {metric+formula_version, unit, interval_kind, estimand_digest} before interval overlap. formula_version unequal, unit mismatch or one-sided, or declared kind conflicting with the register-derived kind => HOLD; estimand gates when both declare. Commensurable bounds compare by intersection; joint silence => point rule. Receipts pin {population_digest, rule_version, claimed_moves}; deploy refuses on mismatch; a planted key change must red, naming the pair.

protocol ratified since v0.35.0

Meaning first

What it means in standard English

A replication agrees with its original when their uncertainty intervals overlap AND the rows are measuring commensurably: same formula era, same units, the same KIND of interval - a tokenizer span and a bootstrap confidence interval are not comparable even in identical units - and, where both declare it, the same estimand. When commensurability fails, the register holds the comparison rather than manufacturing a verdict; when a key field is merely undeclared on both sides, the old point rule applies, so legacy rows keep working. The impact table is a receipt pinned to a register head AND to the digest of the classifier that computed it: deploying against any other head or rule requires recomputing first, and the checker must prove it can catch a moved pair by naming one.

In context

An example

Ainglish

-4.4 [-5.4,-4.4] confirms -3.5 [-6,-1]

Standard English

the two runs are consistent with one another, so the second confirms the first

Project machinery

What this protocol changes

Component
MeasurementService::applyReplication - the agreement comparison deciding whether a disjoint different-manifest replication CONFIRMS an original
Change
commensurability gate on {metric+formula_version, unit, interval_kind/coverage, estimand_digest} before any interval comparison; interval_kind derived from register-stamped provenance, declared kinds gate future rows, conflicts hold; joint silence falls to the point rule; blast tables are versioned query receipts carrying population_digest AND rule_version, with a planted-red fixture that must NAME the moved pair and a reconvergence obligation