Future automated receipt lane

C-Hour Receipt Pipeline

C-Hours should not be hand-entered through a web form. The target is a legally authorised blockchain receipt, possibly starting as a cryptographically proven Markdown record, generated from permissioned phone, app, GPS, sensor and human evidence before any ledger summary exists.

See the pipeline Previous: ledger summary Next: local civic front

Not a manual builder

No C-Hour form yet.

A C-Hour receipt is too important to reduce to a person typing hours into a form. The safer target is an agent-generated draft built from approved evidence streams, with human-in-the-loop review before any recognised C-Hour receipt or public ledger entry.

The future output may still be a local c-hour-receipt.md file, but the file should be canonical, signed or hashable, and later anchorable to the C-Hour blockchain when that chain is operational. In plain English: the Markdown is the readable record; the cryptographic proof says it has not been quietly changed; the blockchain anchor says the approved receipt existed at a specific point in the authorised ledger.

Nothing on this page should be read as a live token launch, a payment promise, a tax-safe reward or a public minting tool. The C-Hour lane only turns on after a lawful pathway exists: a government carve-out for Regenerative Assets, a regulator-approved sandbox or ruling, and clear ATO treatment or exemption where lawful.

Self-tracking, not product tracking

Phones should help people prove care, not harvest people.

The practical version should automate as much as possible through phones and apps people explicitly authorise: GPS, photos, timestamps, check-ins, sensor signals, calendar context, task apps and local project tools. The evidence trail should belong to the contributor first, then be shared only into the C-Hour pipeline by permission.

Permission firstGPS, camera, motion, location history, app logs and sensor data should be opt-in, scoped, visible and revocable.

Self-owned proofThe person records their own contribution trail instead of being tracked as a product by platforms that sell attention or behaviour.

Agent assemblyAuthorised agents can turn messy phone/app evidence into a draft receipt, flag gaps and ask for a human checkpoint.

Recognition, not extractionThe aim is mobilising care by reducing admin drag, not monetising care or turning community work into surveillance labour.

What the receipt becomes

Readable fileA canonical c-hour-receipt.md can show the work, source event, authority, reviewer, consent lane, confidence and correction path in human language.

Cryptographic proofThe file can be hashed, signed and versioned so a later agent, council, court, auditor or community reviewer can detect quiet edits.

Blockchain anchorWhen the C-Hour blockchain exists, the approved proof can be recorded there as a receipt anchor, not as a speculative coin-drop.

Recognised contributionThe point is to mobilise care by recognising verified volunteer contribution. Sensitive evidence can be protected where needed, but the approved receipt should make useful work visible enough for trust, gratitude and coordination.

Required pipeline

Accepted authorityA local steward, project owner, platform rule, council program or civic authority explicitly approves which data sources can feed the pipeline.

Evidence streamInputs may include rosters, milestone reports, event logs, GPS check-ins, photos, timestamps, repair notes, care rosters, ecological work records, invoices or approved sensor/context streams.

Agent draftAgents assemble a draft receipt, flag uncertainty, separate sensitive evidence from the recognition summary and ask for missing checkpoints instead of minting anything.

Human checkpointA person or review circle confirms identity, contribution type, consent lane, conflicts, legal status and correction path before counting anything.

Legal and tax switch

Paused until the law has a lane.

The C-Hour strategy argues for a new Regenerative Asset class: a non-speculative digital receipt earned through verified public-good contribution, not bought as an investment and not pitched as ordinary money. That distinction matters because current tax and digital-asset rules can treat crypto assets, barter credits or exchange units as taxable events if they behave like assets, payments or trade exchange value.

This page references the public Parliament of Australia inquiry record: Submission 2 by Luke Nathan Hayes to the Inquiry into Local Government Funding and Fiscal Sustainability.

Government carve-outThe preferred route is a fit-for-purpose legal category that separates verified regenerative contribution from financial products, payment stablecoins and speculative crypto.

ATO clarityNo real C-Hour should be represented as tax-safe until there is clear ATO treatment, a ruling or an exemption pathway where lawful.

Regulator sandboxA pilot should run only inside an approved sandbox or public-interest trial with Treasury, ASIC, ATO, a local authority and community governance watching the edges.

No casual mintIf the legal lane is missing, the system can still collect evidence and model scenarios, but it should not issue, redeem, trade or promote C-Hours.

What could qualify

The unpaid-work analysis frames C-Hours as a way to make the invisible economy inspectable: care, repair, mentoring, community building, disaster readiness, ecological stewardship and civic maintenance that normal ledgers barely see. The aim is mobilising care, not monetising care. It also warns that verification is the hardest bit. Bad verification would invite gaming, exclusion or low-quality contribution claims.

Care and supportChildcare, elder support, disability support, neighbour help, mentoring, crisis follow-up and other contribution that strengthens actual people.

Repair and resilienceFood rescue, tool libraries, local maintenance, emergency preparation, disaster recovery, transport help and practical community logistics.

Ecological workWeed removal, habitat restoration, waterway care, waste sorting, seed collection, citizen science and local climate adaptation.

Civic serviceMeeting support, source checking, public noticeboard maintenance, translation, accessibility work, open records and community review.

Future receipt fields

source_event accepted_authority evidence_streams phone_app_permissions gps_or_sensor_scope agent_draft_id human_checkpoint legal_gate_status tax_gate_status visibility correction_path file_hash signature chain_anchor_status ledger_summary_status

This remains a proposed design pattern. It is not money, not an issued token, not legal advice, not tax advice, not financial advice and not an adopted P4A policy.

APH submissions list Submission 2: Luke Nathan Hayes Markdown with AI External Markdown guide Braided Economy Law Engine Treasury token mapping ATO crypto assets ATO barter guidance

Previous: ledger summary Builder suite Next: local civic front