Commitery

Core concepts

Commitery works because each commitment has a fixed record, objective proof requirements, protection windows, and a charge that can happen only at the end of the failed-commitment flow.

These docs explain the product in plain language. The Creator Terms, Payment Terms, and other legal documents control if there is a conflict.

The mental model

A commitment is not a reminder and not an instant payment. It is a checkout-backed agreement that says: if this specific goal is not shown to be completed under these specific proof requirements, this specific amount may later be charged.

  • The user first creates the agreement: goal, amount, deadline, proof deadline, proof scope, payment authorization, and withdrawal notice.
  • The user then tries to complete the goal and upload proof.
  • Commitery reviews only against the agreed proof scope.
  • A charge is possible only after a failed verdict survives the dispute and withdrawal safeguards.

The fixed record

The fixed record is what makes the system fair. Once checkout is complete, the core terms should not shift underneath the user.

  • Deadlines define when the goal must be done and when proof must be uploaded.
  • Proof scope defines what evidence counts.
  • Payment method storage makes a later conditional charge technically possible without an upfront charge.
  • The amount and payment authorization define the maximum conditional charge for that commitment or routine cycle.

The protection windows

A failed review outcome is not the same as a charge. Two protection windows sit between a failed verdict proposal and money moving.

  • The 48-hour dispute window lets the user challenge a failed verdict proposal.
  • The 14-day withdrawal period lets eligible consumers withdraw from the commitment contract.
  • If either window cancels or reverses the failed outcome, no commitment amount is charged.

Money only moves at the end

Commitery saves a payment method at checkout, but the commitment amount is not charged there. The charge happens only if the failed-commitment path reaches the end.

  • No charge at checkout.
  • No charge while proof review, dispute, or withdrawal can still change the outcome.
  • A customer invoice is issued only after a charge succeeds.
  • Creator allocations can exist only after an attributed failed commitment is successfully charged.

How the concepts connect

The practical sequence is: create a draft, check out, complete the commitment, upload proof, receive a verdict, resolve any dispute or withdrawal issue, and only then handle a possible charge.