Early Bird Feedback Protocol

Objective

Bring outside human judgment into Idea Ledger while observations are still inexpensive to act upon. Early users are testers and adversarial collaborators, not a validation audience.

Capture format

  • IDE# — proposed improvement or alternative.
  • QUE# — ambiguity, concern, missing information, or unresolved behavior.
  • DEC# — challenge to, support for, or consequence of a design decision.
  • Add PRJ:idea-ledger so the finding can be routed consistently.

Include the action being attempted, expected behavior, observed behavior, and consequence when those details apply. Preserve the tester's exact wording as the Source Record; any triage summary remains a separate Snapshot.

Review sequence

  1. Capture the finding without demanding that the tester classify it perfectly.
  2. Check whether it duplicates or relates to existing Idea Cards.
  3. Attach associations rather than merging away distinct Source Records.
  4. Record a Result for resolved questions or create a Decision Card for a chosen direction.
  5. Update Project Memory only after a change is accepted.
  6. Retain rejected findings and their reasoning; rejection is part of project history.

Questions for adversarial testing

  • What did the system assume that the user did not say?
  • Where was authorship or provenance unclear?
  • What could cause loss of trust?
  • Where did capture interrupt thought rather than preserve it?
  • What became harder to rediscover after capture?
  • Which terminology implied more certainty than the information justified?
  • What privacy or permission boundary was missing?

Access boundary

Do not share the v0 master access key broadly. Until individual identities exist, collect findings through facilitated sessions or an explicitly controlled intake process that records the tester's identity and consent without exposing the private Ledger.