Platform

Known limits

Being explicit about limits is consistent with the whole thesis. Every product has them; few write them down.

Two servable types today. The live catalog is token.price (4 providers, anchored) and social.value (1 provider, single_source). Everything else is roadmap.

Consensus is not reachable on any current catalog type. token.price is anchored (a stronger, different guarantee) and social.value is capped at single_source (one provider, no measured L3 judge). So while the fan-out gate that would buy consensus for higher plans exists in code, it produces no observable difference between plans in production yet. There is no type for it to act on. That is a catalog limitation, not a bug, and it will change when a type with independent peers is provisioned.

What verification cannot catch. Two colluding sources that read the same upstream, in a type without an anchor, are indistinguishable from the truth, so Metera labels that datum single_source, never consensus, until independence is measured. It reports the lying rate as a confidence interval, not a point, because a rate reported as a point is not a measurement.

Roadmap, not present. The pieces marked roadmap here and on the token page do not exist yet and are never described in the present tense.