Every board pack becomes a mission with a lifecycle, an argument, a verdict, and a record. Here is the full path from upload to brief — and what's underneath it.
The council never presents a management assertion with the same weight as a verified number. Five grades travel with every finding, from intake to brief.
| Grade | Meaning | Example |
|---|---|---|
| Asserted | Stated in the materials, unverified | "Pipeline is strong going into Q4" |
| Observed | Directly present in a source document | The ARR definition changed between decks |
| Measured | Recomputed by the council from the underlying numbers | Implied burn contradicts the stated runway |
| Validated | Confirmed against independent or external evidence | The claimed contract matches the public filing |
| Refuted | Contradicted by the evidence — on the record | The "signed" partnership isn't in either party's disclosures |
BoardCouncil isn't a demo wrapping an API call. Each surface maps to a primitive of the Meta3Agents governed runtime — built, tested, and running real missions today.
Bring one real board pack; we'll return a graded, adversarially-tested pre-meeting brief — and you'll see the audit trail behind every finding.