One artifact model, honest by construction.

The artifact record

This is the shape the browser builders write today into stub_artifacts_v1, and the shape the hosted service will store. The fields that matter most are the ones that refuse to lie.

• source_class: user_supplied today; employer_attested and issuer_integrated only with the proof behind them.
• authority_status: draft or generated. issuer_verified needs a signed issuer response.
• transferability: not_applicable for everything except tickets, which are unknown until an issuer says permitted_by_issuer.
• financial_status: unpaid or payment_self_reported today; payment_recorded only from a signed processor event.
• content_digest: SHA-256 of the canonical JSON of the inputs, recomputed on every version.

artifact:
  id: "inv_7q4m2xh9pl"
  tenant_id: "local-browser"
  kind: "invoice"          # event_ticket | keepsake | pay_statement
                           # | remittance_voucher | check_fill | invoice | receipt
  version: 2
  source_class: "user_supplied"
  authority_status: "generated"
  transferability: "not_applicable"
  financial_status: "payment_self_reported"
  content_digest: "sha256:3f0a91c2d4e5…"
  history:
    - version: 1
      digest: "sha256:91c2d4e5b6a7…"
      status: "generated"
  created_at: "2026-10-27T13:04:11Z"

Planned v1 API

Versioned under /v1, standardized machine error codes with safe user messages, idempotency keys on every write, request-size limits, schema validation and audit logs. Public credentials are never downloadable by id alone. Ships with the business pilot, to pilot businesses first.

Every "authorized" reference below is a placeholder for a real signed relationship, not a claim that one exists.

POST   /v1/auth/sessions
GET    /v1/me
POST   /v1/orgs
POST   /v1/orgs/{id}/verify
GET    /v1/templates?kind=ticket
POST   /v1/artifacts/drafts
PATCH  /v1/artifacts/{id}/draft
POST   /v1/artifacts/{id}/preview
POST   /v1/artifacts/{id}/finalize
GET    /v1/artifacts/{id}
POST   /v1/artifacts/{id}/download-session
POST   /v1/events
POST   /v1/events/{id}/tickets/issue
POST   /v1/tickets/{id}/check-in
POST   /v1/invoices
POST   /v1/orders
POST   /v1/webhooks/payments/{provider}