PatchScope
New cardConnect

Roadmap

v1 is a scope record, not a marketplace

The list below is the product boundary. Items marked later are not quietly half-built.

In this v1

  • Structured scope card with S, X, A, and P clauses
  • Two-party acceptance of an exact version hash
  • Revision history that invalidates approval
  • One atomic request, statements, and typed evidence
  • Counterparty acknowledgement of a content hash
  • Early freeze bound to the accepted agreement hash, plus deadline freeze
  • Frozen packet stores a copy of the accepted card
  • Deterministic classification gate
  • One review round; empty new-evidence reviews stay open until the window ends
  • A change order is a new card, never an edit of the old one
  • Local team owner and member controls
  • Public read diagnostics when a contract is configured

Kept out on purpose

  • Escrow, invoices, tokens, and reputation scores
  • Admin pause, upgrade, or hidden override
  • Arbitrary web crawling as consensus truth
  • Email collection without a delivery path
  • A backend key that signs for the user
  • A private-case promise on a public chain

Next, if v1 holds

  • Studio deployment after a manual source-hash approval
  • Wallet signatures on every network write
  • Equivalence-checked model adjudication beside the gate
  • Optional HTTPS excerpt import inside the VM, still frozen before decision
  • Shared Postgres drafts with wallet-session auth
  • An external review, named as such only if it happens

Back to the docs

Write the card before the work.

Same action as the front page. The other party still accepts the exact hash.

Write a scope card