Comps, credit, and the cage: governing cash-equivalent authority

Comps are the value operators watch most closely. They are not the only value crossing the floor — and the desks that handle the rest deserve the same governance.

A comp is cash-equivalent value: a free suite, a loss rebate, free play. But so is a marker drawn at the table, a credit line extended to a premium player, and front money deposited at the cage. All of it moves value through many hands, fast, often at hours when the senior authority is asleep. The comp desk is usually the one operators govern with real rigour. The credit desk and the cage are too often left to spreadsheets and standing habit.

CompWarden's AEGIS platform closes that gap. It is the comp authority engine — and the same delegation-of-authority model that governs a comp governs a marker, a credit line, and a cage transaction, under one matrix and one ledger.

The shared problem

Comps, credit, and cage transactions look like different jobs run by different teams. Underneath, they pose one question. Each moves cash-equivalent value out of the building, and each passes through several people before it settles. Every one of them needs an answer to the same thing, at the moment it happens: "Is this authorised, right now, by someone who holds the limit?"

Issuance systems record that value moved. They rarely check, in the moment, that the person moving it held the authority to. A marker approved above a host's limit, a credit line extended without the right sign-off, a cage disbursement no one can later tie to an approver — each is the same failure the comp desk already knows well, on a different desk. The value is real. The authority is assumed.

Extending the authority model to credit

Credit is the clearest case. Who can extend a credit line, or approve a marker, up to what limit, is a delegation-of-authority question — the same shape as a comp. AEGIS resolves it against a live org chart: the requester's role, the transaction type, the dollar limit, the patron checks.

If the request sits within the requester's authority, it clears on the spot. If it exceeds that limit, it escalates automatically up the reporting line until it reaches someone whose authority covers it — no side channel, no verbal approval that vanishes by morning. The rules are the matrix: role, type, limit, and what happens on exceed. The credit desk runs on the same model as the floor, not a parallel one improvised per shift.

The cage under the same ledger

The cage is where cash-equivalent value physically settles, and where an unaccountable movement is hardest to reconstruct after the fact. Under AEGIS, a cage transaction is governed like any other: checked against the matrix, escalated when it exceeds authority, and sealed to the same immutable audit trail as every comp and credit decision.

That trail is hash-chained and anchored into immudb — a store the platform itself cannot alter. Each sealed decision carries its ledger anchor and the matrix version in force when it was made. The result is that cash-equivalent movement is provable end to end: not a set of desk logs that have to be cross-referenced by hand, but one record that holds.

One matrix, consistent limits

The quiet cost of governing each desk separately is drift. A comp policy in one spreadsheet, a credit policy in another, cage limits in a third — each edited by a different owner on a different day, none of them the single source of truth. Limits diverge. Nobody can say with confidence which version was in force last Tuesday.

Governing comps, credit, and cage under one delegation-of-authority model removes that. A single, versioned matrix defines who can move value and how much, across every desk. Change a limit once and it applies everywhere it should, with the change itself recorded. When Audit asks what the rule was on a given night, the answer is the matrix version stamped on the decision — not a reconstruction.

Why it matters for compliance

What auditors and regulators want is not more logs. It is an unbroken, tamper-evident record of who was allowed to move value, and who did. When comps and credit sit on the same ledger, that record spans the value that leaves the building rather than stopping at the desk that happened to be governed well.

An answer of ~5ms at the point of decision is what keeps that governance from slowing the floor; a hash-chained, anchored trail is what makes the record stand up afterwards. The compliance case is not that AEGIS adds oversight to credit and cage. It is that oversight stops being desk-by-desk goodwill and becomes one provable service.

For the fuller shape of the model, see the delegation-of-authority matrix for casino comps and building a defensible audit trail for comp approvals. The security model behind the ledger is documented in full.