# Canonical Claim Boundary

This file defines the public boundary for the Mian Zhang / Ouroboros public
evidence field. It is intentionally stricter than a promotional page.

## Public Claims

### P02-C1
WisdomBench measures longitudinal learning from failure rather than only
single-shot task capability.

This does not prove human-like wisdom, universal agent reliability, or
deployment safety.

### PCA-C1
High-risk AI action should not earn action credit until warrant and receipt
closure exist.

This does not prove live trading profit, customer readiness, or universal
safety.

### P24-C1
Adaptive systems need relational observability: relations, constraints,
control debt, evidence half-life, and actionability gates.

This does not prove a universal theorem covering all adaptive systems without
independent traces.

### P20-C1
Physical AI should route degraded evidence to recovery or abstention rather
than direct action.

This does not prove detector SOTA, offensive autonomy, or real-robot
deployment certification.

### F1-C1
Trading is used as a high-risk testbed for proof-carrying action discipline,
not as a public claim of live profitability.

This does not prove live trading edge, alpha dominance, customer readiness, or
private execution quality.

## Public Evidence

Public evidence may include papers, datasets, public registries, demo routes,
redacted no-go summaries, schema notes, claim-to-evidence tables, and
counterexample routes.

## Not Public

The public evidence field does not disclose API keys, private finance
execution details, customer data, private agent orchestration, commercial
schedulers, anonymous conference packages, or private live trading logs.

## Valid Attacks

Useful attacks include formula counterexamples, data leakage, stronger
baselines, reproduction failures, over-broad claim boundaries, credit leaks,
authority leaks, and mismatches between claim scope and evidence scope.

## Invalid Attacks

Requests for private customer data, credentials, protected execution traces, or
anonymous conference packages are outside this public boundary.

## Repair Rule

If a public counterexample is valid, the route is repaired, narrowed, or marked
as blocked. Repair work does not automatically earn action credit.