Life of a request

Every click in an App is a call to its API, and every call becomes one Action. Leaseline declares a Lease Noun; follow one renewal from the button to the invoice.

The clickCopy Anchor Link

Ines Duarte manages leases for Harbor Residential. She opens the lease for Unit 5C, 76 Harbor Way, which ends on 2026-11-05, and presses Renew. The button is the form for Lease.renew, compiled from the Verb's inputs: 12 months, rent up 3%.

The App sends the same call any other client sends. Harbor Residential's property software makes it too:

curl -X POST https://api.leaseline.app/leases/lease_4loEed1JG4/renew \
  -H "Authorization: Bearer $LEASELINE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"months":12,"increase":0.03}'

Who mayCopy Anchor Link

Three checks run before anything changes, in this order:

1. The key or the session belongs to Harbor Residential's Tenant, and so does the lease. No query crosses Tenants.
2. Ines Duarte holds the manager Persona, whose Role has the Permission to call Lease.renew.
3. Harbor Residential's portfolio plan holds an Entitlement to Lease.renew with no cap.

A failed check returns a refused Action naming the check, and nothing else happens. On a capped plan, the refusal names the plan that lifts the cap.

The ActionCopy Anchor Link

The Verb's Function runs, moves the lease from renewing to renewed, and records one Action: done. The Action keeps who acted, for whom, through which Interface, with which key, and at which Version of the definition.

{
  "api": "https://api.leaseline.app",
  "lease": {
    "$id": "https://api.leaseline.app/leases/lease_4loEed1JG4",
    "$type": "Lease",
    "unit": "Unit 5C, 76 Harbor Way",
    "endsOn": "2027-11-05",
    "status": "renewed"
  },
  "action": {
    "$id": "https://api.leaseline.app/actions/act_br07HsG8MG",
    "operation": "Lease.renew",
    "status": "done"
  }
}

A person's click and an Agent's call leave the same record. Only by and via differ.

What followsCopy Anchor Link

The Action's Event, Lease.renewed, fans out to everything that waits on it:

A refused or failed call never reaches a Meter, so it never reaches an Invoice.

NextCopy Anchor Link

The App lifecycle covers how a change to the App itself goes live.