Skip to content

Fit Rubric

Use this rubric to decide whether a candidate deserves deeper research. It is not a market score. It measures whether Merkle-authenticated peer state changes the trust model enough to justify the complexity.

Score each question 0, 1, or 2.

Questions

  1. Multi-peer truth
  2. 0: one authority owns almost all relevant facts
  3. 1: one main authority plus acknowledgements
  4. 2: two or more peers each own necessary facts

  5. Statefulness

  6. 0: one-shot signed messages are enough
  7. 1: some updates matter
  8. 2: evolving state and old states both matter

  9. Negative claims

  10. 0: only positive statements matter
  11. 1: some absence or revocation matters
  12. 2: exclusion is central

  13. Selective disclosure

  14. 0: full disclosure is fine
  15. 1: privacy is useful
  16. 2: verifiers usually need only a slice of each peer's state

  17. Composed outcome

  18. 0: one proof decides the result
  19. 1: multiple proofs help
  20. 2: the final result is inherently derived from several peer proofs

  21. Dispute or audit pressure

  22. 0: low stakes, low replay value
  23. 1: moderate
  24. 2: disputes, audits, or delayed settlement are common

  25. Why signatures alone fail

  26. 0: a signed blob would do
  27. 1: signatures work, but awkwardly
  28. 2: committed state is materially better

  29. Certification ladder

  30. 0: verified facts are consumed once
  31. 1: some derived claims can be reused
  32. 2: certified derived facts naturally become reusable building blocks

Interpretation

  • 0-6: bad fit
  • 7-10: maybe
  • 11-13: strong fit
  • 14-16: excellent fit

Before advancing a candidate, pair the score with:

  • a one-sentence value proposition
  • the safest software role
  • the main legal, governance, or operational risk
  • the infrastructure layer needed: signed roots, witness feed, metadata anchoring, or scripted claim-history anchors

Shortcut

If a protocol is:

  • multi-peer
  • stateful
  • composed

then it is worth serious investigation.