Field Manual

How to read, test, and challenge this work.

This site is a public evidence field. It gives claims, artifacts, boundaries, and counterexample routes first. The private execution systems, customer data, and commercial orchestration remain protected.

Inspect Evidence Submit a Counterexample View Systems

Evidence has a shape visual showing structured proof paths.

Reader Routes

Choose the weakest useful entry point.

Do not begin by agreeing with the thesis. Begin with the part you can inspect, reproduce, or break.

Role First move Useful output Do not start with

Researcher Open one evidence card and inspect the claim boundary. A sharper theorem, failure condition, or baseline. Grand narrative.

Engineer Run a minimal artifact or inspect a schema. A reproduction issue, patch, or runnable demo note. Private execution systems.

Decision maker Read the public/private boundary and the Systems page. A bounded pilot question. Claims of full automation.

Critic Submit a bounded counterexample. A repairable attack on formula, data, baseline, reproduction, or boundary. Personal judgment.

Read the claim

Every public claim should state what it asserts, what variable it measures, and what would count as a failure.

Inspect the evidence

Look for DOI records, datasets, code, manifests, negative results, and provenance before judging the idea.

Check the boundary

A mature claim states what it does not prove. Boundary errors are treated as repair work, not marketing.

Attack precisely

Useful attacks target formula counterexamples, data leakage, stronger baselines, reproduction gaps, or over-broad claims.

Public / Private

The public layer is generous. The execution layer is protected.

Public materials include protocols, evidence maps, minimal schemas, preprints, public datasets, synthetic or fully redacted public-safe sample traces, negative results, and counterexample routes. Private materials include financial execution details, customer data, live logs, private agent orchestration, and commercial scheduling.

public: claim + schema + toy artifact + DOI + attack route
private: customer data + live execution + orchestration + protected logs

If a claim cannot be supported without exposing private material, the public claim should be narrowed rather than the protected system disclosed.

Minimum Trust Loop

What a serious demo should prove.

Step System behavior User sees Metric

Goal Receives a bounded task. The system asks for constraints, not blind authority. scope clarity

Evidence Builds an action envelope. Thesis, falsifier, missing proofs, and receipts. envelope completeness

Restraint Refuses action when proof is incomplete. A no-go reason and repair queue. no-go clarity

Delivery Produces a report or next-step work order. A usable artifact, not a vague answer. first useful artifact time

Operating Rule

Strong claims are welcome here only when their boundaries, artifacts, and attack routes are visible.

This is the posture for research, product, and community: verifiable first, private where necessary, repairable when wrong.