records people can point at
Local Proof Cards
Screenshot-native receipts for asks, offers, pledges, references, and decisions. Read a card, or scroll the rooms.
A Local Proof Card is a small, readable record you can keep. It can describe what someone needs, what someone offers, what a group agreed to, what a project is asking for, or what insight should be remembered. Its strongest form binds four things: the claim or input, the conditions and prior state, the evidence for what changed, and the next authorized state.
The card stays useful as a screenshot, a copied seed, a link, or a later archived record. No wallet required. No platform lock-in required. The first version is local, readable, and shareable. The screenshot matters because it freezes a state without pretending the process is over.
a claim, ask, offer, scene note, funding request, or learning milestone needs a durable handle.
context, authorship, sequence, and the difference between “someone said this” and “this is true.”
a screenshot, prompt packet, membership artifact, consensus record, RPG recap seed, or research citation. It can also become a prompt for the next pass through the work.
Card Types
Ask Card
We need $___ by ___ for ___.
A concrete request with measurable terms and clear accountability.
Offer Card
I can provide ___ for ___.
A visible capacity or skill ready for collaboration without platform lock-in.
Pledge Card
I intend to support ___ with ___.
A public intention honoring recurring continuity or financial backing.
Consensus Card
This is what the group currently agrees to.
A shared coordinate preventing conversational drift and forgotten agreements.
Reference Card
This insight, source, or decision should be easy to cite later.
A stable anchor for research notes, math proof cards, and architecture records.
Membership Card
This person joins as observer, supporter, contributor, or collaborator.
A role handle connecting human practice with the garden and studio ecology.
What A Card Does
A card makes a claim and binds it to a visible state. A screenshot preserves it. Evidence records the declared consequence. A URL or seed lets someone revisit it. A later version can supersede it. Between those states is where a lot of useful understanding happens.
These are NFT-like in the narrow sense that each card is a distinct object with its own context. They are not speculative assets. They are local records first.
Keep The Record Honest
A card is not proof that a claim is true. It is proof that a claim was made in a readable form at a specific moment. A verification receipt may support the relation or refuse it; evidence for a nearby proxy should not be used to rescue the wrong claim.
If a card changes, make a new version. Do not silently overwrite the record.
Screenshot To Consensus
Consensus does not mean everyone agrees forever. It means the group has a visible reference point for what is being proposed, supported, questioned, blocked, revised, or archived.
Draft
A proposal exists. No agreement yet.
Supported
Enough people support moving forward.
Concerned
People agree partly but have notes.
Blocked
Someone names a concrete reason not to proceed.
Revised
A new version replaces the old one.
Archived
No longer active, but preserved.
Screenshot the card before the conversation spreads out. The card gives the group one thing to point at.