01Available now
System evidence
Source, schemas, policies, tests, version, and a reproducible reference run show how the machinery is designed to behave.
- — Open skill contract
- — Income-system schema
- — Request-to-Quote reference pack
Proof · evidence before status
Show the machinery. Verify delivery. Count economics after settlement.
Code proves a system exists. Acceptance proves work was delivered. Settled, cost-adjusted evidence is required before an income result becomes a public claim.
Three evidence layers
A demo is not a delivery. Revenue is not net income.
Each layer answers a different question and cannot substitute for the next.
02Per accepted engagement
Delivery evidence
Approved scope, acceptance checks, preview, decision log, handoff, and customer consent show what was delivered and accepted.
- — Approved scope
- — Verification bundle
- — Accepted handoff
03Only after settlement
Economic evidence
Settled receipts minus refunds, chargebacks, direct costs, tool costs, and attributed human time support an economic claim.
- — Settled receipt
- — Cost allocation
- — Measurement window and denominator
Current public evidence
System evidence—not customer income evidence.
These artifacts are inspectable now. No customer result or economic milestone is implied until the required delivery and settlement evidence exists and publication is approved.
Proof Guild milestones
Status earned from settled net evidence.
A milestone also publishes the measurement window, direct costs, refunds, attributed human time, evidence level, system version, and participant consent.
€1K Builder
€1,000 cumulative settled net receipts
€10K Builder
€10,000 cumulative settled net receipts
€100K System
€100,000 cumulative settled net receipts
€1M Portfolio
€1,000,000 cumulative settled net receipts
Milestone names define the future evidence standard. They do not state that a current member, customer, or system has reached them.