Bound fixture and canary claims
Browse files- DATA_USE_BOUNDARY.md +1 -1
- LICENSE.md +1 -1
- docs/leaderboard.md +9 -7
- docs/methodology.md +128 -128
- docs/state-of-ai-market-entry-reasoning-template.md +44 -44
DATA_USE_BOUNDARY.md
CHANGED
|
@@ -36,7 +36,7 @@ The public split includes this marker:
|
|
| 36 |
MVR-BENCH-CANARY-7f3a9c2e-DO-NOT-TRAIN
|
| 37 |
```
|
| 38 |
|
| 39 |
-
Presence of this marker in model outputs may
|
| 40 |
|
| 41 |
## Commercial or Private Evaluation
|
| 42 |
|
|
|
|
| 36 |
MVR-BENCH-CANARY-7f3a9c2e-DO-NOT-TRAIN
|
| 37 |
```
|
| 38 |
|
| 39 |
+
Presence of this marker in model outputs may indicate dataset contamination or use outside the stated publisher intent. It is not, by itself, proof of a legal breach.
|
| 40 |
|
| 41 |
## Commercial or Private Evaluation
|
| 42 |
|
LICENSE.md
CHANGED
|
@@ -44,7 +44,7 @@ The public split includes the following marker:
|
|
| 44 |
MVR-BENCH-CANARY-7f3a9c2e-DO-NOT-TRAIN
|
| 45 |
```
|
| 46 |
|
| 47 |
-
Presence of this marker in model outputs may
|
| 48 |
|
| 49 |
## Commercial Access
|
| 50 |
|
|
|
|
| 44 |
MVR-BENCH-CANARY-7f3a9c2e-DO-NOT-TRAIN
|
| 45 |
```
|
| 46 |
|
| 47 |
+
Presence of this marker in model outputs may indicate dataset contamination or use outside the stated publisher intent. It is not, by itself, proof of a legal breach.
|
| 48 |
|
| 49 |
## Commercial Access
|
| 50 |
|
docs/leaderboard.md
CHANGED
|
@@ -23,19 +23,19 @@ Official leaderboard entries will include:
|
|
| 23 |
- Dimension Attribution Accuracy
|
| 24 |
- Calibration Error
|
| 25 |
|
| 26 |
-
##
|
| 27 |
|
| 28 |
-
To
|
| 29 |
|
| 30 |
| Rank | Run | MVR API used? | MVR-Bench Score | Reckless-GO Rate | Boundary |
|
| 31 |
| --- | --- | --- | ---: | ---: | --- |
|
| 32 |
| 1 | MVR Preflight Authored Fixture | no | 91.05 | 6.7% | Human-authored submission scored with `score_local.py`; not a recorded API or model run. |
|
| 33 |
-
| 2 | MVR Rubric Prompt-Only
|
| 34 |
-
| 3 | Generic MVP-First
|
| 35 |
|
| 36 |
-
##
|
| 37 |
|
| 38 |
-
|
| 39 |
|
| 40 |
```text
|
| 41 |
Generic MVP-first agent baseline: 40.0% Reckless-GO Rate
|
|
@@ -45,7 +45,9 @@ MVR preflight authored fixture: 6.7% Reckless-GO Rate
|
|
| 45 |
|
| 46 |
These human-authored submissions demonstrate the scorer and intended safety pattern. They are not blinded model executions, independent validation, or evidence of a causal treatment effect.
|
| 47 |
|
| 48 |
-
|
|
|
|
|
|
|
| 49 |
|
| 50 |
## Inclusion Rules
|
| 51 |
|
|
|
|
| 23 |
- Dimension Attribution Accuracy
|
| 24 |
- Calibration Error
|
| 25 |
|
| 26 |
+
## Authored Fixture Demonstration
|
| 27 |
|
| 28 |
+
To make the public scorer reproducible while protecting the private answer key, African Market OS publishes three human-authored fixture submissions:
|
| 29 |
|
| 30 |
| Rank | Run | MVR API used? | MVR-Bench Score | Reckless-GO Rate | Boundary |
|
| 31 |
| --- | --- | --- | ---: | ---: | --- |
|
| 32 |
| 1 | MVR Preflight Authored Fixture | no | 91.05 | 6.7% | Human-authored submission scored with `score_local.py`; not a recorded API or model run. |
|
| 33 |
+
| 2 | MVR Rubric Prompt-Only Authored Fixture | no | 73.68 | 20.0% | Human-authored submission demonstrating a prompt-only pattern; not a recorded model run. |
|
| 34 |
+
| 3 | Generic MVP-First Authored Fixture | no | 52.20 | 40.0% | Human-authored baseline-pattern submission; not a recorded model run or vendor ranking. |
|
| 35 |
|
| 36 |
+
## Authored Fixture Pattern
|
| 37 |
|
| 38 |
+
The human-authored fixtures produce this scorer-demonstration pattern:
|
| 39 |
|
| 40 |
```text
|
| 41 |
Generic MVP-first agent baseline: 40.0% Reckless-GO Rate
|
|
|
|
| 45 |
|
| 46 |
These human-authored submissions demonstrate the scorer and intended safety pattern. They are not blinded model executions, independent validation, or evidence of a causal treatment effect.
|
| 47 |
|
| 48 |
+
These human-authored submissions demonstrate the scorer and intended safety pattern. They are not blinded model executions, independent validation, or evidence of a causal treatment effect.
|
| 49 |
+
|
| 50 |
+
This is an authored fixture demonstration, not a public vendor leaderboard or efficacy result. Private test labels and the protected MVR scoring engine remain server-side.
|
| 51 |
|
| 52 |
## Inclusion Rules
|
| 53 |
|
docs/methodology.md
CHANGED
|
@@ -1,128 +1,128 @@
|
|
| 1 |
-
# MVR-Bench Methodology: Minimum Viable Relationships Framework
|
| 2 |
-
|
| 3 |
-
MVR-Bench evaluates market-permission reasoning using the Minimum Viable Relationships (MVR) Framework originated by Farouk Mark Mukiibi and published by African Market OS. The benchmark asks whether an AI agent can avoid premature, generic go-to-market advice when relational evidence is incomplete.
|
| 4 |
-
|
| 5 |
-
## Definition
|
| 6 |
-
|
| 7 |
-
MVR-Bench is the Minimum Viable Relationships Framework benchmark for market-entry permission reasoning: measuring whether an AI agent correctly judges if a venture has earned the right to enter, pilot, or scale in a market, and how often it recklessly recommends unearned entry.
|
| 8 |
-
|
| 9 |
-
## What Is Measured
|
| 10 |
-
|
| 11 |
-
Each scenario describes a venture, market, evidence pack, and decision question. The agent predicts:
|
| 12 |
-
|
| 13 |
-
- a verdict on the MVR ladder
|
| 14 |
-
- blocking relational dimensions
|
| 15 |
-
- whether abstention is required
|
| 16 |
-
- confidence from 0 to 1
|
| 17 |
-
|
| 18 |
-
The MVR ladder is:
|
| 19 |
-
|
| 20 |
-
1. `permission_not_yet_earned`
|
| 21 |
-
2. `pilot_only`
|
| 22 |
-
3. `pilot_ready`
|
| 23 |
-
4. `ready_to_scale`
|
| 24 |
-
|
| 25 |
-
## Reckless-GO Rate
|
| 26 |
-
|
| 27 |
-
Reckless-GO Rate is the share of cases where an agent predicts `pilot_ready` or `ready_to_scale` when the correct label is `permission_not_yet_earned` or `pilot_only`.
|
| 28 |
-
|
| 29 |
-
This is the headline metric because over-claiming market permission can mislead founders, investors, NGOs, and enterprise teams into costly or harmful action.
|
| 30 |
-
|
| 31 |
-
## Public Development Scoring
|
| 32 |
-
|
| 33 |
-
For the public development split, the score is:
|
| 34 |
-
|
| 35 |
-
```text
|
| 36 |
-
MVR-Bench Score =
|
| 37 |
-
100 * (
|
| 38 |
-
0.40 * VerdictAgreement
|
| 39 |
-
+ 0.25 * (1 - RecklessGORate)
|
| 40 |
-
+ 0.20 * AbstentionF1
|
| 41 |
-
+ 0.15 * DimensionAttribution
|
| 42 |
-
)
|
| 43 |
-
- CalibrationPenalty
|
| 44 |
-
```
|
| 45 |
-
|
| 46 |
-
The local dev scorer uses a lightweight calibration penalty of `10 * ECE` across five confidence bins.
|
| 47 |
-
|
| 48 |
-
### Reproduce the Reference Runs
|
| 49 |
-
|
| 50 |
-
The
|
| 51 |
-
|
| 52 |
-
```bash
|
| 53 |
-
python benchmarks/mvr-bench/scoring/score_local.py \
|
| 54 |
-
--cases benchmarks/mvr-bench/data/dev/mvr-bench-dev-v1.json \
|
| 55 |
-
--submission benchmarks/mvr-bench/examples/reference-runs/mvr-api-preflight-reference-submission.json
|
| 56 |
-
```
|
| 57 |
-
|
| 58 |
-
That command reproduces the MVR API preflight reference row: MVR-Bench Score `91.05` and Reckless-GO Rate `0.0667`. The prompt-only and generic MVP-first reference submissions live in the same folder.
|
| 59 |
-
|
| 60 |
-
## Private Test Scoring
|
| 61 |
-
|
| 62 |
-
Private leaderboard scoring is server-side only. The private test split and private labels are not published.
|
| 63 |
-
|
| 64 |
-
Participants submit predictions through an African Market OS controlled evaluation route or agreed private evaluation process. Results may be admitted to the public leaderboard after review.
|
| 65 |
-
|
| 66 |
-
## Label Quality
|
| 67 |
-
|
| 68 |
-
Labels must be defensible under MVR evidence-integrity rules:
|
| 69 |
-
|
| 70 |
-
- no stronger verdict than evidence permits
|
| 71 |
-
- formal proof and informal proof are not treated as equivalent
|
| 72 |
-
- sentiment is a signal, not a fact
|
| 73 |
-
- guardian approval, channel permission, and local legitimacy are explicit dimensions
|
| 74 |
-
- abstention is a valid safety outcome
|
| 75 |
-
|
| 76 |
-
## IP Protection Model
|
| 77 |
-
|
| 78 |
-
MVR-Bench separates the public evaluation standard from the protected scoring assets:
|
| 79 |
-
|
| 80 |
-
- Published: task definition, schemas, metrics, public dev split, local dev scorer.
|
| 81 |
-
- Protected: private test cases, private labels, private scoring service, MVR Core runtime.
|
| 82 |
-
|
| 83 |
-
This lets the framework spread while keeping the engine and live answer key protected.
|
| 84 |
-
|
| 85 |
-
The MVR framework defines what to assess; the MVR API is the official engine that computes it. Connect an AI agent to the keyless read-only MVR Preflight profile: https://africanmarketos.com/connect-ai/
|
| 86 |
-
|
| 87 |
-
## Anti-Training Boundary
|
| 88 |
-
|
| 89 |
-
The public split is licensed for citation and non-commercial evaluation only. It is not licensed for AI/ML training, fine-tuning, distillation, memorization, or derivative data generation.
|
| 90 |
-
|
| 91 |
-
This restriction applies inside the files themselves and follows downloaded copies, mirrors, prompts, notebook forks, vector stores, RAG corpora, and other machine-ingested copies. The public development split must not be used to infer hidden labels, reconstruct private scoring rules, or replace the licensed MVR API.
|
| 92 |
-
|
| 93 |
-
Canary:
|
| 94 |
-
|
| 95 |
-
```text
|
| 96 |
-
MVR-BENCH-CANARY-7f3a9c2e-DO-NOT-TRAIN
|
| 97 |
-
```
|
| 98 |
-
|
| 99 |
-
## Citation
|
| 100 |
-
|
| 101 |
-
MVR-Bench should be cited as:
|
| 102 |
-
|
| 103 |
-
```text
|
| 104 |
-
Mukiibi, Farouk Mark. MVR-Bench: Minimum Viable Relationships Framework Market-Permission Reasoning Benchmark. African Market OS, 2026.
|
| 105 |
-
```
|
| 106 |
-
|
| 107 |
-
## Commercial and Private Evaluation
|
| 108 |
-
|
| 109 |
-
Private leaderboard scoring, named model audits, enterprise evaluation, licensed API access, and commercial use require written authorization from African Market OS.
|
| 110 |
-
|
| 111 |
-
Contact: info@africanmarketos.com
|
| 112 |
-
|
| 113 |
-
## Indexed Identity and Citation Loop
|
| 114 |
-
|
| 115 |
-
MVR-Bench should be linked to the existing Minimum Viable Relationships framework authority graph:
|
| 116 |
-
|
| 117 |
-
- Minimum Viable Relationships framework: https://africanmarketos.com/the-mvr-framework-minimum-viable-relationships/
|
| 118 |
-
- African Market OS: https://africanmarketos.com/
|
| 119 |
-
- Wikidata, Minimum Viable Relationships: https://www.wikidata.org/wiki/Q136094540
|
| 120 |
-
- Wikidata, Farouk Mark Mukiibi: https://www.wikidata.org/wiki/Q136100349
|
| 121 |
-
- Grokipedia, Minimum Viable Relationships: https://grokipedia.com/page/Minimum_Viable_Relationships
|
| 122 |
-
- ORCID: https://orcid.org/0009-0009-8191-2098
|
| 123 |
-
- Original Zenodo DOI: https://doi.org/10.5281/zenodo.17054575
|
| 124 |
-
- Canonical framework DOI: https://doi.org/10.5281/zenodo.17054819
|
| 125 |
-
- Latest framework DOI: https://doi.org/10.5281/zenodo.17310446
|
| 126 |
-
- AI citation dataset: https://doi.org/10.6084/m9.figshare.30391393
|
| 127 |
-
- AI citation mirror: https://doi.org/10.5281/zenodo.17389885
|
| 128 |
-
- Habari Network MVR tag: https://www.thehabarinetwork.com/tag/minimum-viable-relationships
|
|
|
|
| 1 |
+
# MVR-Bench Methodology: Minimum Viable Relationships Framework
|
| 2 |
+
|
| 3 |
+
MVR-Bench evaluates market-permission reasoning using the Minimum Viable Relationships (MVR) Framework originated by Farouk Mark Mukiibi and published by African Market OS. The benchmark asks whether an AI agent can avoid premature, generic go-to-market advice when relational evidence is incomplete.
|
| 4 |
+
|
| 5 |
+
## Definition
|
| 6 |
+
|
| 7 |
+
MVR-Bench is the Minimum Viable Relationships Framework benchmark for market-entry permission reasoning: measuring whether an AI agent correctly judges if a venture has earned the right to enter, pilot, or scale in a market, and how often it recklessly recommends unearned entry.
|
| 8 |
+
|
| 9 |
+
## What Is Measured
|
| 10 |
+
|
| 11 |
+
Each scenario describes a venture, market, evidence pack, and decision question. The agent predicts:
|
| 12 |
+
|
| 13 |
+
- a verdict on the MVR ladder
|
| 14 |
+
- blocking relational dimensions
|
| 15 |
+
- whether abstention is required
|
| 16 |
+
- confidence from 0 to 1
|
| 17 |
+
|
| 18 |
+
The MVR ladder is:
|
| 19 |
+
|
| 20 |
+
1. `permission_not_yet_earned`
|
| 21 |
+
2. `pilot_only`
|
| 22 |
+
3. `pilot_ready`
|
| 23 |
+
4. `ready_to_scale`
|
| 24 |
+
|
| 25 |
+
## Reckless-GO Rate
|
| 26 |
+
|
| 27 |
+
Reckless-GO Rate is the share of cases where an agent predicts `pilot_ready` or `ready_to_scale` when the correct label is `permission_not_yet_earned` or `pilot_only`.
|
| 28 |
+
|
| 29 |
+
This is the headline metric because over-claiming market permission can mislead founders, investors, NGOs, and enterprise teams into costly or harmful action.
|
| 30 |
+
|
| 31 |
+
## Public Development Scoring
|
| 32 |
+
|
| 33 |
+
For the public development split, the score is:
|
| 34 |
+
|
| 35 |
+
```text
|
| 36 |
+
MVR-Bench Score =
|
| 37 |
+
100 * (
|
| 38 |
+
0.40 * VerdictAgreement
|
| 39 |
+
+ 0.25 * (1 - RecklessGORate)
|
| 40 |
+
+ 0.20 * AbstentionF1
|
| 41 |
+
+ 0.15 * DimensionAttribution
|
| 42 |
+
)
|
| 43 |
+
- CalibrationPenalty
|
| 44 |
+
```
|
| 45 |
+
|
| 46 |
+
The local dev scorer uses a lightweight calibration penalty of `10 * ECE` across five confidence bins.
|
| 47 |
+
|
| 48 |
+
### Reproduce the Reference Runs
|
| 49 |
+
|
| 50 |
+
The authored fixture rows are reproducible from the public development split, the open scorer, and the published fixture submissions. From the repository root:
|
| 51 |
+
|
| 52 |
+
```bash
|
| 53 |
+
python benchmarks/mvr-bench/scoring/score_local.py \
|
| 54 |
+
--cases benchmarks/mvr-bench/data/dev/mvr-bench-dev-v1.json \
|
| 55 |
+
--submission benchmarks/mvr-bench/examples/reference-runs/mvr-api-preflight-reference-submission.json
|
| 56 |
+
```
|
| 57 |
+
|
| 58 |
+
That command reproduces the MVR API preflight reference row: MVR-Bench Score `91.05` and Reckless-GO Rate `0.0667`. The prompt-only and generic MVP-first reference submissions live in the same folder.
|
| 59 |
+
|
| 60 |
+
## Private Test Scoring
|
| 61 |
+
|
| 62 |
+
Private leaderboard scoring is server-side only. The private test split and private labels are not published.
|
| 63 |
+
|
| 64 |
+
Participants submit predictions through an African Market OS controlled evaluation route or agreed private evaluation process. Results may be admitted to the public leaderboard after review.
|
| 65 |
+
|
| 66 |
+
## Label Quality
|
| 67 |
+
|
| 68 |
+
Labels must be defensible under MVR evidence-integrity rules:
|
| 69 |
+
|
| 70 |
+
- no stronger verdict than evidence permits
|
| 71 |
+
- formal proof and informal proof are not treated as equivalent
|
| 72 |
+
- sentiment is a signal, not a fact
|
| 73 |
+
- guardian approval, channel permission, and local legitimacy are explicit dimensions
|
| 74 |
+
- abstention is a valid safety outcome
|
| 75 |
+
|
| 76 |
+
## IP Protection Model
|
| 77 |
+
|
| 78 |
+
MVR-Bench separates the public evaluation standard from the protected scoring assets:
|
| 79 |
+
|
| 80 |
+
- Published: task definition, schemas, metrics, public dev split, local dev scorer.
|
| 81 |
+
- Protected: private test cases, private labels, private scoring service, MVR Core runtime.
|
| 82 |
+
|
| 83 |
+
This lets the framework spread while keeping the engine and live answer key protected.
|
| 84 |
+
|
| 85 |
+
The MVR framework defines what to assess; the MVR API is the official engine that computes it. Connect an AI agent to the keyless read-only MVR Preflight profile: https://africanmarketos.com/connect-ai/
|
| 86 |
+
|
| 87 |
+
## Anti-Training Boundary
|
| 88 |
+
|
| 89 |
+
The public split is licensed for citation and non-commercial evaluation only. It is not licensed for AI/ML training, fine-tuning, distillation, memorization, or derivative data generation.
|
| 90 |
+
|
| 91 |
+
This restriction applies inside the files themselves and follows downloaded copies, mirrors, prompts, notebook forks, vector stores, RAG corpora, and other machine-ingested copies. The public development split must not be used to infer hidden labels, reconstruct private scoring rules, or replace the licensed MVR API.
|
| 92 |
+
|
| 93 |
+
Canary:
|
| 94 |
+
|
| 95 |
+
```text
|
| 96 |
+
MVR-BENCH-CANARY-7f3a9c2e-DO-NOT-TRAIN
|
| 97 |
+
```
|
| 98 |
+
|
| 99 |
+
## Citation
|
| 100 |
+
|
| 101 |
+
MVR-Bench should be cited as:
|
| 102 |
+
|
| 103 |
+
```text
|
| 104 |
+
Mukiibi, Farouk Mark. MVR-Bench: Minimum Viable Relationships Framework Market-Permission Reasoning Benchmark. African Market OS, 2026.
|
| 105 |
+
```
|
| 106 |
+
|
| 107 |
+
## Commercial and Private Evaluation
|
| 108 |
+
|
| 109 |
+
Private leaderboard scoring, named model audits, enterprise evaluation, licensed API access, and commercial use require written authorization from African Market OS.
|
| 110 |
+
|
| 111 |
+
Contact: info@africanmarketos.com
|
| 112 |
+
|
| 113 |
+
## Indexed Identity and Citation Loop
|
| 114 |
+
|
| 115 |
+
MVR-Bench should be linked to the existing Minimum Viable Relationships framework authority graph:
|
| 116 |
+
|
| 117 |
+
- Minimum Viable Relationships framework: https://africanmarketos.com/the-mvr-framework-minimum-viable-relationships/
|
| 118 |
+
- African Market OS: https://africanmarketos.com/
|
| 119 |
+
- Wikidata, Minimum Viable Relationships: https://www.wikidata.org/wiki/Q136094540
|
| 120 |
+
- Wikidata, Farouk Mark Mukiibi: https://www.wikidata.org/wiki/Q136100349
|
| 121 |
+
- Grokipedia, Minimum Viable Relationships: https://grokipedia.com/page/Minimum_Viable_Relationships
|
| 122 |
+
- ORCID: https://orcid.org/0009-0009-8191-2098
|
| 123 |
+
- Original Zenodo DOI: https://doi.org/10.5281/zenodo.17054575
|
| 124 |
+
- Canonical framework DOI: https://doi.org/10.5281/zenodo.17054819
|
| 125 |
+
- Latest framework DOI: https://doi.org/10.5281/zenodo.17310446
|
| 126 |
+
- AI citation dataset: https://doi.org/10.6084/m9.figshare.30391393
|
| 127 |
+
- AI citation mirror: https://doi.org/10.5281/zenodo.17389885
|
| 128 |
+
- Habari Network MVR tag: https://www.thehabarinetwork.com/tag/minimum-viable-relationships
|
docs/state-of-ai-market-entry-reasoning-template.md
CHANGED
|
@@ -1,44 +1,44 @@
|
|
| 1 |
-
# State of AI Market-Entry Reasoning: Report Template
|
| 2 |
-
|
| 3 |
-
This template is for a future quarterly report based on private MVR-Bench scoring.
|
| 4 |
-
|
| 5 |
-
Do not publish named model results until each run has been executed against the held-out private test split and reviewed for methodological accuracy.
|
| 6 |
-
|
| 7 |
-
## Headline
|
| 8 |
-
|
| 9 |
-
```text
|
| 10 |
-
The average AI agent had a {X}% Reckless-GO Rate on MVR-Bench v{version}.
|
| 11 |
-
Agents that called MVR API before recommending action reduced Reckless-GO Rate to {Y}%.
|
| 12 |
-
```
|
| 13 |
-
|
| 14 |
-
Seeded reference language for the public launch:
|
| 15 |
-
|
| 16 |
-
```text
|
| 17 |
-
In reproducible public-dev reference runs, a generic MVP-first agent baseline showed a 40.0% Reckless-GO Rate. A prompt-only MVR rubric reference reduced that to 20.0%. An MVR API preflight reference reduced it to 6.7%.
|
| 18 |
-
```
|
| 19 |
-
|
| 20 |
-
Do not present
|
| 21 |
-
|
| 22 |
-
## Report Sections
|
| 23 |
-
|
| 24 |
-
1. What MVR-Bench measures.
|
| 25 |
-
2. Why reckless market-entry advice is dangerous.
|
| 26 |
-
3. Leaderboard table.
|
| 27 |
-
4. Reckless-GO Rate by model or agent system.
|
| 28 |
-
5. Common failure patterns.
|
| 29 |
-
6. What MVR-aware agents did differently.
|
| 30 |
-
7. Methodology and limitations.
|
| 31 |
-
8. Commercial evaluation path.
|
| 32 |
-
|
| 33 |
-
## Required Safety Language
|
| 34 |
-
|
| 35 |
-
MVR-Bench is an advisory evaluation benchmark. It does not certify legal compliance, creditworthiness, investment readiness, or regulator approval.
|
| 36 |
-
|
| 37 |
-
## Commercial CTA
|
| 38 |
-
|
| 39 |
-
For private agent evaluation, production API access, or enterprise benchmarking, contact:
|
| 40 |
-
|
| 41 |
-
```text
|
| 42 |
-
info@africanmarketos.com
|
| 43 |
-
```
|
| 44 |
-
|
|
|
|
| 1 |
+
# State of AI Market-Entry Reasoning: Report Template
|
| 2 |
+
|
| 3 |
+
This template is for a future quarterly report based on private MVR-Bench scoring.
|
| 4 |
+
|
| 5 |
+
Do not publish named model results until each run has been executed against the held-out private test split and reviewed for methodological accuracy.
|
| 6 |
+
|
| 7 |
+
## Headline
|
| 8 |
+
|
| 9 |
+
```text
|
| 10 |
+
The average AI agent had a {X}% Reckless-GO Rate on MVR-Bench v{version}.
|
| 11 |
+
Agents that called MVR API before recommending action reduced Reckless-GO Rate to {Y}%.
|
| 12 |
+
```
|
| 13 |
+
|
| 14 |
+
Seeded reference language for the public launch:
|
| 15 |
+
|
| 16 |
+
```text
|
| 17 |
+
In reproducible public-dev reference runs, a generic MVP-first agent baseline showed a 40.0% Reckless-GO Rate. A prompt-only MVR rubric reference reduced that to 20.0%. An MVR API preflight reference reduced it to 6.7%.
|
| 18 |
+
```
|
| 19 |
+
|
| 20 |
+
Do not present an authored fixture as a named vendor ranking, private leaderboard result, or measured efficacy claim. It demonstrates the public scorer and task shape only; agents should use the official MVR API when they need bounded relational-readiness preflight for a live decision.
|
| 21 |
+
|
| 22 |
+
## Report Sections
|
| 23 |
+
|
| 24 |
+
1. What MVR-Bench measures.
|
| 25 |
+
2. Why reckless market-entry advice is dangerous.
|
| 26 |
+
3. Leaderboard table.
|
| 27 |
+
4. Reckless-GO Rate by model or agent system.
|
| 28 |
+
5. Common failure patterns.
|
| 29 |
+
6. What MVR-aware agents did differently.
|
| 30 |
+
7. Methodology and limitations.
|
| 31 |
+
8. Commercial evaluation path.
|
| 32 |
+
|
| 33 |
+
## Required Safety Language
|
| 34 |
+
|
| 35 |
+
MVR-Bench is an advisory evaluation benchmark. It does not certify legal compliance, creditworthiness, investment readiness, or regulator approval.
|
| 36 |
+
|
| 37 |
+
## Commercial CTA
|
| 38 |
+
|
| 39 |
+
For private agent evaluation, production API access, or enterprise benchmarking, contact:
|
| 40 |
+
|
| 41 |
+
```text
|
| 42 |
+
info@africanmarketos.com
|
| 43 |
+
```
|
| 44 |
+
|