AgEvidenceInvestor Evidence Room
Technical Reference ↗GitHub ↗
Review through
OverallInvestmentTechnologyScienceNeutral
Independent review · registry

Independent claim register

One row per load-bearing claim. Status comes from an evidence record; nothing is hand-waved into green.

12 claimsStrict status vocabularyFalsifier required
Vocabulary

What each status is allowed to mean

The words validated, verified and proven are not used here unless a precise meaning is stated. They collapse distinct forms of validity.

Built
The artefact exists and can be inspected. Says nothing about use.
Demonstrated
It has been made to work under conditions AgEvidence controlled.
Externally observed
Someone outside AgEvidence saw or used it without our involvement.
Paid
Money changed hands for it.
Repeated
It happened a second time without redesigning the core.
Independently reproduced
A third party reconstructed the result from the published package.
Supported
Argument and indirect evidence, no direct observation.
Proposed
A designed intention with no evidence yet.
Open
Not yet tested; the decisive observation has not been made.
At risk
Evidence is trending against the claim.
Falsified
The falsifier fired. The claim is retired or rewritten.
Board

Claim → status → falsifier → next test

ClaimDomainStatusNext decisive testGate
Thin-waist architecture can generalisearchitectureOpenThree materially different upstream systems emitting through the same primitives.G2
Rust verification is portablearchitectureDemonstratedExternal reconstruction by a reviewer using only the published package.G4
Python integration can remain thinarchitectureOpenOne external developer team, no support channel, measured.G2
Rails implements the recurring operational workflowcommercialDemonstratedOne paid deployment carried through a second evaluation cycle.G5
Scientific validity stays separated from integrityscienceProposedStructured interpretation study with external reviewers.—
One evidence chain can serve two usesarchitectureOpenOne chain, two destinations, no source rework.G3
Funded agtech will paycommercialOpenOne named startup pays for readiness or deployment.G5
The second deployment is cheapercommercialOpenInstrument deployment hours from the first engagement onward.G6
Open core strengthens distributioncommercialSupportedTrack self-hosting adopters and their conversion behaviour.—
Portfolio-assisted heterogeneous validation accelerates proofcommercialProposedRun one portfolio and one external integration in parallel and compare hours.—
The protocol can survive without the SaaSgovernanceBuiltCold-start the core from published artefacts alone, with no company resources.—
The company survives a failed next financinggovernanceOpenCompare headcount additions against gate completion at month 6 and month 12.—
Status notes

Why each claim sits where it sits

Thin-waist architecture can generaliseOpen

Designed and exercised against synthetic fixtures. No independent production integrations.

Rust verification is portableDemonstrated

Deterministic verifier runs against fixture bundles in a clean environment.

Python integration can remain thinOpen

Internally demonstrated. No external developer has integrated unassisted.

Rails implements the recurring operational workflowDemonstrated

Internal product path demonstrated end to end. Recurring external use and willingness to pay are open.

Scientific validity stays separated from integrityProposed

Designed into the model. Empirical test of user behaviour is open.

One evidence chain can serve two usesOpen

Architecturally supported, never demonstrated with two real destinations.

Funded agtech will payOpen

Market research and pricing work only. No invoiced instance.

The second deployment is cheaperOpen

No second deployment exists.

Open core strengthens distributionSupported

Argued from precedent in adjacent categories. Untested here.

Portfolio-assisted heterogeneous validation accelerates proofProposed

Structurally plausible. Discounted by relatedness until an external integration exists.

The protocol can survive without the SaaSBuilt

Architecturally testable today; stewardship arrangements are not yet executed.

The company survives a failed next financingOpen

Depends on execution and on hiring being gated to proofs rather than to the vision.

Independent review

Everything in this room

Claim status board

Every load-bearing claim should have one row and one status.

Built means an artifact exists. Demonstrated means the company has made it work under controlled conditions. Paid means money changed hands. Repeated means the result happened again without redesigning the core. Independently reproduced means a third party reconstructed the result from the package. Supported, proposed, open, at risk and falsified should remain equally explicit.

The board exists to prevent polished narrative from upgrading evidence.

Reading through Overall

The native reading. Claim status, evidence burden, proof gates, falsifiers, contradictions, capital-to-proof, governance, downside, and explicit reasons to stop or narrow the thesis.