Skip to content

RFC-035: Mediation Vector Profile — A Validity-Aware Measurement Model for Domains of Concern — 20. Summary

AIGP SpecificationRFC-035: Mediation Vector Profile — A Validity-Aware Measurement Model for Domains of Concern › 20. Summary

← 19. Security and Safety Considerations · Section index · 21. References →

20. Summary

The Mediation Vector Profile is a validity-aware measurement model for a Domain of Concern. It is not a list of scoring fields — it is an empirical measurement claim, and it carries the obligations that measurement claims have carried in science for a century.

It treats the concern as a construct (Cronbach & Meehl), validity as an argument rather than a number (Messick), every variable as measurement-typed with declared permissible operations (Stevens), every variable as derived from a concern question (GQM), every value as provenance-bound (W3C PROV), and every verdict as a warranted argument (Toulmin).

It is organized as a four-layer profile — Construct, Evidence, Measurement, Calculation — and it borrows the four-state variable model from the Master Evidence Graph, connecting each state to an AIGP primitive: ANTICIPATE (anticipated), RECORD/TRACE (actual), D-DNA (evidenced), FEEDBACK (perceived).

The gap calculus produces signals that demand verdicts without asserting conclusions — preserving the principle that governance makes evaluation possible without making quality true. Validity is argued in the profile, not assumed by the protocol.

20.1 The Series

RFC Question It Answers
RFC-034 What is the Domain of Concern?
RFC-035 How do we validly measure concern variables? (this document)
RFC-036 How do we calculate concern posture from the measured vector?
RFC-037 Who or what may observe, render verdicts, and calibrate the result?
RFC-038 How are reusable Domains of Concern registered and versioned?

The core scientific move that defines this RFC:

A concern vector is an empirical measurement claim. Therefore RFC-035 must define validity, admissibility, provenance, measurement type, uncertainty, and warranted use — not just fields and weights.



← 19. Security and Safety Considerations · Section index · 21. References →