Skip to main content
The simple agreement is the smallest complete agreement JSON artifact in these docs. Use it to inspect or adapt the full artifact shape before validating and deploying with the SDK.

When to use this example

Use this example when you want a complete agreement with minimal branching, or when you need a straightforward starting point for a genuinely linear workflow. For a broader lifecycle with more states, event types, and branching behavior, use Complex Agreement.

What to notice before the canonical agreement JSON

Before reading the JSON, notice:
  1. participant address variables marked with subtype: "participant"
  2. rendered content that uses the same variables
  3. a short set of lifecycle states
  4. inputs that correspond to signature and acceptance events
  5. transitions that move the agreement forward with minimal branching

Agreement lifecycle

The diagram below shows the states and transitions defined by this agreement’s execution object. Use it to understand the workflow before reviewing the full JSON artifact.

Canonical agreement JSON

The following code block is the complete deployable agreement JSON for this example.
simple-agreement.json