Core
Envelope, event IDs, authorization, agreement, causality, claims, receipts, extensions.
CP/00 · OPEN COORDINATION LAYER
Protocol
over platform.
CommonPact documents a shared way for people and organizations to discover each other, negotiate privately, authorize the same terms, and keep portable evidence—without requiring one company to own every relationship.
COMMONPACT TOPOLOGYPRE-IMPLEMENTATION / NOT DEPLOYED
APPLICATIONSRide clientRental clientDelivery client
COREDiscoverAgreeProve
INFRASTRUCTURERelaysDirect channelsOptional services
No mandatory platform owner. No canonical backend. No protocol commission. No claim that infrastructure disappears.
01 / THE CURRENT FAILURE
Convenience became ownership.
Today a rider often needs Uber or Lyft to reach a driver. A renter needs a marketplace to reach an owner. A sender needs a logistics platform. The service may be useful, but it also becomes the unavoidable gatekeeper for discovery, ranking, terms, records, reputation, and fees.
CommonPact targets the mandatory owner—not every useful intermediary.
USERMANDATORY PLATFORMPROVIDER
USER CLIENTSHARED PROTOCOLPROVIDER CLIENT
02 / SYSTEM BOUNDARIES
One core.
Responsibilities stay visible.
The protocol authenticates statements and relationships between statements. Profiles carry domain meaning. Applications carry user experience. Accountable operators still own real-world duties.
Profiles
Roles, terms, lifecycle, proof, privacy, accessibility, legal and safety boundaries.
Clients
Interface, keys, matching, ranking, trust policy, export, disclosure, support integration.
Operators
Infrastructure, moderation, incidents, insurance, payment, compliance, human support.
03 / HUMAN JOURNEYS
The same coordination pattern.
Different physical worlds.
The core stays small because rides, rentals, deliveries, and donations do not share the same safety or legal meaning.
Request → private terms → pickup proof → ride receipt
PactRide remains the complete standalone source profile. Transport safety, insurance, accessibility, and emergency response stay ride-specific.
Availability → reservation → handoff → return evidence
PactRental tests persistent assets, possession, deposits, condition records, delayed damage, and external remedies.
Concept: custody may pass through several parties
Sender, courier, subcontractor, recipient, refusal, loss, return-to-sender, and address privacy still require domain research.
High-risk concept: money requires accountable custody
CommonPact must not pretend a protocol replaces processors, sanctions checks, tax records, fraud controls, or charity law.
04 / PACT LIFECYCLE
A pact is not a chat message.
- 01Discoverable
Publish a privacy-limited intent with expiry.
- 02Negotiating
Exchange complete proposed terms privately.
- 03Agreed
Required parties authorize the identical terms hash.
- 04Active
The profile-defined handoff or obligation begins.
- 05Completed
Required parties authorize one portable receipt.
Cancelled, aborted, disputed, and externally resolved states remain explicit. Arrival order never decides truth.
05 / PROFILE FAMILY
06 / CLAIM DISCIPLINE
The protocol can establish
- which key authorized an event;
- which complete terms were accepted;
- causal references and provenance;
- whether the required signer set authorized one receipt.
The protocol cannot establish
- legal identity, honesty, safety, or ownership;
- physical performance or hidden condition;
- payment finality, insurance coverage, or lawful operation;
- fair dispute resolution or a viable market.
07 / CURRENT STATUS
DOCUMENTED
The founder vision is complete.
The repository includes normative draft semantics, strict payload schemas, cryptographic fixtures, a complete PactRental documentation package, adoption and responsibility analysis, and automated validation.
UNPROVEN
The system is not built.
There are no independent implementations, production relays, operating marketplaces, legal approval, safety guarantee, payment custody, or funded deployment team.