Project File · Standard v1 · 17 August 2026
The specification behind a verified file.
The field manifest, what enforces each promise, and what is not built yet. We never make the decision — these rules keep it that way.
- Never decides
- Never lends or insures
- Never holds funds or keys
- Never charges the contractor a fee
Specimen · values dummiedDW-4K7Q-2XPD
Ready to send- Bid & scope
- Rear deck rebuild · 320 sq ft · signed
- Amount
- $38,400.00
- Contractor
- Copper Creek Builders
- Licence
- TX-041882 · verified
- COI in force
- GL + WC · expires 14 Mar 2027
- Permit
- Filed · Travis County
- Cancellation ends
- Friday 21 August 2026
- Consent
- Signed 17 August 2026 · text stored verbatim
- Completion attestation
- Pending — after the work
No DuckWater score. Ever.
What lives here
The Project File — field manifestEvery field, its source, and whether it runs this morning. Three tiers; the third never exists.Read the manifestThe rules we publishEach rule labelled by what holds it up — a green test, a drafted clause, or a kept policy.Read the rulesThe Crypto Bridge — how it worksA bucketed, keyed-fingerprint credential; hash-chained receipts verifiable offline; a blind lender tile with the custody answers first — and the test behind each.Read the mechanismSecurity & complianceServer-resolved roles, status-only contractors, every action an event — and what is not done yet.Read the registerFour documents, written to be argued with.
Where this stands
Month 0, and the page says so.
17 August 2026. No institution signed. No file delivered. No licence held. Contract means drafted; Specified means written, not built. The standard is published first because a standard is easier to argue with than a system someone depends on.