Tool2026-06-30#integration

Every button needs a contract

Buttons are tiny contracts. Bad buttons imply writes that never happened, automation that is not wired, or authority the user does not have.

A good button tells the truth in the label, sends the user to the right surface, and leaves a source trail. A better button also exposes the public JSON or receipt behind the content.

This is why a learning notebook should make Try this actions real: copy the exercise, open the learning surface, and expose the source entry.

Aha moment

A button is a product promise. If the action is only copy, link, or read JSON, the label should say exactly that.

Try this

Audit three UI buttons and write what each one actually does, what it does not do, and what proof the user receives.

Open NotesEntry JSON

Watch for

  • Buttons that imply a write happened
  • Protected actions without PLATPHORM_API_KEY
  • No source link behind generated or instructional content