No. It is a protocol proposal and profile framework.
No. A multi-profile client is possible, but one super-app is not required.
No. It removes the mandatory platform owner at the protocol layer. Payment, insurance, identity, moderation, support, escrow, and dispute providers may remain useful or required.
The agreement is directly between parties and no central platform is authoritative. Delivery may still use internet relays or servers.
No. Nearby networking may help verification and outages. Citywide discovery should initially use replaceable internet infrastructure.
Conceptually: different clients and providers interoperate through shared standards. CommonPact must also learn from email's spam, metadata, and concentration problems.
No protocol commission is required.
Yes, for transparent optional services.
No. PactRide remains self-contained. Alignment requires an adapter or explicit future version.
PactRental is a detailed draft. PactDelivery and PactFund are candidate concepts.
No. It is a pre-implementation research RFC.