Proof Cards

Proof cards are how I turn loose claims into reviewable packets.

They are not a public dump of private operator state. The private ledger lives in Plane and Mesh. This page is the public projection: the format, the publication boundary, and the first kinds of cards that can become public after review.

The operating rule is simple:

If a claim cannot say what was promised, what money meant, what evidence exists, and what remains private, it is not ready to be public proof.

Projection Levels

Private

The full internal card. It can include exact money, internal links, raw evidence notes, review dates, names, risk gates, event history, and operator context.

Private cards are for execution, not public credibility.

Public Candidate

An internal card that might become public later. It still should not render on the public web. The point of this state is review: redaction, consent, legal/accounting boundaries, and whether the card says enough to be useful.

Public Summary

A short public card with:

• title;
• stream;
• status;
• evidence state;
• claim;
• proof required;
• public caveat;
• last reviewed date.

This is enough for an index page without exposing raw operations.

Public Case Card

A reviewed card for a completed or mature loop. It can add redacted evidence, an outcome, amount bands, and links to public artifacts.

It still excludes private names, addresses, raw funding terms, internal operator links, private relationship notes, and anything that turns a proof packet into a public dossier.

Public Packet

The full public story, used only when consent and review are clear. This can name external parties, exact public URLs, and specific outcomes, but only when the people involved are meant to be part of the public record.

Public Template

A public proof card should answer six questions:

1. What need, request, or capacity was named?
2. What money label applied, if any?
3. What obligation did that create?
4. What evidence exists?
5. What stays private?
6. What changed, failed, or needs the next decision?

Useful fields:

Field	Public-safe meaning
Stream	The lane: consulting, Sitelayer, public proof, Winnipeg pilot, housing, workspace, or fenced risk.
Claim	The narrow thing this card is allowed to say.
Evidence state	Missing, partial, verified, or killed.
Proof required	What would make the claim stronger or close the card.
Public caveat	What this does not prove yet.
Privacy boundary	What was deliberately not exposed.
Next decision	Repeat, stop, change shape, seek review, or publish a case card.

Candidate Cards

These are candidate shapes, not claims that the proof already exists.

Obligation Layer Page

Stream: public proof.

Claim: the obligation-layer thesis has a public surface that explains the frame without exposing private operating state.

Proof required: live page, reviewed language, clear role-fit, links to the proof-card format, and no raw Plane or Mesh data exposed.

Public caveat: this proves the presentation layer, not that any local pilot or commercial loop has succeeded.

Software Delivery Proof

Stream: consulting and advisory.

Claim: a scoped engagement can turn a fuzzy workflow, agent-review problem, or operational risk into a written implementation sequence.

Proof required: request, scope, delivered artifact, acceptance or rejection, and any public case study only with permission.

Privacy boundary: repo names, internal incidents, private architecture, invoices, and client context stay private unless explicitly approved.

Sitelayer Callback Proof

Stream: Sitelayer product loop.

Claim: a real workflow can move from request to field context, work item, evidence, callback, and closeout.

Proof required: one closed loop with consented or anonymized evidence.

Public caveat: Sitelayer should be sold as a product and service, not as a public social experiment.

Grocery Demand Pilot

Stream: Winnipeg local pilot.

Claim: a small household demand signal may help a local grocer understand committed demand and measure whether costs or friction change.

Proof required: bounded participant group, store-facing commitment, pickup process, measured savings or non-savings, friction, and a repeat/stop decision.

Privacy boundary: household identities, spending details, and private store terms stay out of the public card.

Local Obligation Split

Stream: mutual aid / obligation splitting.

Claim: a named monthly obligation can be made less ambiguous by labeling the contribution, decision rule, disbursement, privacy boundary, and outcome.

Proof required: money label, target amount, contribution total, decision, disbursement, outcome, and conflict or recusal note where relevant.

Public caveat: no investment return, no guarantee, no implied insurance, and no vague community fund.

Related page: Trusted Obligation Bridge, the working note for private-network timing capacity, direct bill support, housing/sublet capacity, and public-safe proof.

Housing Gap Packet

Stream: housing / fenced risk.

Claim: some housing gaps are coordination problems around rooms, sublets, assignments, deposits, arrears, or vacancy risk.

Proof required: legal and lease review, consent path, amount and term, responsible party, move-in/move-out or payment evidence, and aggregate outcome.

Public caveat: this is not a rental marketplace, crisis-housing program, speculative property product, insurance product, or public record of vulnerable tenants.

Do Not Publish

No public card should expose:

• private names without consent;
• addresses, household details, tenancy details, arrears, safety concerns, or family context;
• private funding terms;
• exact internal operator links, task IDs, event history, or console state;
• legal, insurance, tax, investment, or securities claims that have not been reviewed;
• relationship graphs, influence rankings, private outreach strategy, or motive claims.

How To Use This

For a business or product team, a proof card can turn an engagement into a case receipt: what was requested, what was delivered, what changed, and what cannot be shared publicly.

For a local pilot, a proof card can keep a small test honest: what was the need, who had capacity, what money meant, what happened, and whether it should repeat.

For a funder or patron, a proof card can make support specific: fund a named artifact, pilot, or coordination cost without turning support into control, equity, debt, insurance, or upside.

For the public, proof cards are a way to see what is being tested without demanding access to private lives or private operations.

The broader map is the Obligation Layer. The consulting entry point is Working With Me.