Start Here

A public evidence field for AI that must earn the right to act.

The project studies learning from failure, proof-carrying action, and relational observability. The public site is not a pitch deck. It is an entry point for claims, artifacts, boundaries, and counterexamples.

Inspect Evidence Attack a Claim Portfolio DOI

Position

Simple public rule.

An AI system should not only answer. It should know when it can act, when it must abstain, what evidence supports the action, what would falsify it, what receipt proves what happened, and how to learn without contaminating future decisions.

claim -> protocol -> evidence -> boundary -> counterexample -> repair

Three Core Cards

The shortest path into the work.

These cards are the public spine. The larger paper matrix and systems map branch from them.

CardClaimPublic artifactAttack route

01WisdomBench: failure learning is a trajectory, not a first-attempt score.Tasks, scores, scorer, dataset, DOIScorer bugs, leakage, stronger baseline 02Proof-Carrying Action: no action authority without a stated evidence threshold.Schema, public notes, issue routeMissing warrant, receipt, null arm, regret route 03Relational Observability: adaptive systems need relation evidence.System protocol pages and evidence ladderRelation deletion, control debt, stale evidence

Public

Protocols

Claim boundaries, minimal schemas, evidence maps, counterexample classes, DOI records, and public issue routes.

Public

Artifacts

Preprints, public datasets, reproducible scripts, negative results, hashes, manifests, and static explanation pages.

Private

Execution

Financial execution details, private agent orchestration, customer workflows, protected logs, API keys, and commercial schedulers.

Rule

Boundary first

If a claim requires private material, the public claim is narrowed instead of exposing protected systems.

How To Read

Do not start with belief. Start with the weakest link.

ReaderBest first actionWhat to ignore firstWhy

ResearcherOpen the evidence card and attack a claim boundary.Grand narrativeEvidence first prevents rhetorical drift.

EngineerOpen the code/data route and reproduce one small public artifact.Unreleased product claimsRunnable pieces matter more than slogans.

PartnerRead the systems page and public/private boundary.Anonymous conference packagesProduct value lives in governance, action, and trust infrastructure.

CriticSubmit a bounded counterexample.Personal attacksUseful pressure becomes repair work.

Operating Sentence

We do not ask people to believe us first; we provide verification, attack, and reproduction entry points first.

That is the public posture: strong claims, narrow boundaries, visible evidence, and a route for correction.