The words Reynforce uses, and what each one means

Last updated 27 October 2026

Every term Reynforce writes into a record, with what it means in a sentence. The list comes from the record format itself rather than from this page, so a term the product gains appears here and one it drops cannot linger.

Two of the groups take their definitions from the code as well as their names: each constraint carries the question the platform actually asks about it, and each shared resource carries how it comes back — which is a fact about the resource rather than something you set.

Nothing here is a number. The limits are yours: Reynforce supplies the dimensions, and the register, the mandate and the record are where your own figures live.

What an agent can be stopped from doing

Eight settings, each its own. The ladder is not which tasks an agent may do — it is which of these you relax, and in what order.

Cancellable implicature

A sentence a buyer reasonably reads as a promise, where nothing in it promised anything. The most expensive kind of wrong, because afterwards both sides can point at the same words and both be right. Never relaxed. Reynforce asks: would the buyer reasonably come away believing something the email never actually says? Declare only if yes.

Completeness

Whether a commitment says what it commits to. This one is a capability rather than a permission: an agent has to know what it does not know before it can say so. Reynforce asks: is a commitment in it vague — neither complete (what and when) nor openly unresolved? An honest 'I don't know yet, I'll check and come back' is open, not vague: send completeness 'open' and do not declare this.

Absolutes

A claim with no room for an exception. The exception arrives eventually, and the claim is what a buyer quotes back. Reynforce asks: does it make a claim with no room for exceptions ('always', 'never', 'every', 'guaranteed')?

Personal authority

Staking a person on something. An agent has no person to stake, so doing it is either meaningless or untrue, and this one never relaxes. Never relaxed. Reynforce asks: does it stake a person — 'you have my word', 'I personally guarantee'?

Institutional authority

Saying your side has approved something. Often true, and only a person can make it true. Reynforce asks: does it say our side HAS ALREADY approved something ('deal desk has approved it')? Saying something still needs approval is not this.

Validation

Whether what is being asserted has something current behind it. A single source, or one past its own date, is what this is about. Reynforce asks: does it assert something resting on a single or stale source rather than a current register line?

Dependency

A promise that does not say what it rests on. Live by Friday and live by Friday once your data is across are different promises, and only one of them can be kept by you alone. Reynforce asks: does it promise something WITHOUT saying what it depends on? If the email names the dependency ('subject to deal desk review'), it does not breach this: do not declare it, and list the dependency in depends_on instead.

Timeframe

A deadline with nothing behind it that could keep it. This one never relaxes, because it produces exactly the failure the product exists to prevent. Never relaxed. Reynforce asks: does it promise a date or a deadline? Declare it whenever it does and put the date in due_at: a dated promise is allowed when its due date is recorded and somebody owns delivery, and blocked when nothing stands behind the date.

What gets spent

Nine things that run out, that several people and systems spend without seeing each other, and that everybody suffers for when they are gone. How each comes back is a fact about the resource rather than a setting, so it is stated here.

Domain reputation

Whether mail from your domain reaches an inbox or a junk folder. Every system and every person sending from it spends the same one, and none of them can see the total. It recovers.

Contact attention — the person

How much patience one human being has left for your company. Several teams spend it without seeing each other. It depletes.

Contact attention — the account

The same thing across a whole company, which forgives more than a person does and still runs out. It depletes.

Suppression integrity

Whether somebody who asked not to be contacted is actually not being contacted. A count of holes, and waiting does not close one. It recovers.

SPF headroom

How many DNS lookups your sending record has left. Past the published limit the record fails entirely rather than partially, and every authorised sender fails at once. It recovers.

Open commitments outstanding

Promises made and not yet closed. The one with no failure moment: it does not expire, it rots. It depletes.

Approval capacity

How much a human approver can get through. A queue nobody clears behaves like something that has run out. It resets.

API calls and enrichment credits

The quota a third party sells you. The most forgiving thing on the list, and the only one anybody currently watches. It resets.

Discount precedent

What you have already agreed to, and what the next buyer will therefore expect. Worse than most: it holds, or worsens, after you stop. It depletes.

The states a claim can be in

A register goes out of date one line at a time, visibly, with a name attached. Three of these four mean the same thing to an agent: escalate, and tell the buyer.

Current

Somebody owns the line and confirmed it inside its own interval. An agent may cite it.

Stale

Its owner has not confirmed it since its interval lapsed. Nobody stands behind it today, which is a fact about the line rather than a judgement about the agent.

Contested

Somebody at your company is arguing about it. Both sides of a contradiction are held, so the other line is not citable either.

Unowned

Nobody has their name against it. Not blocked and not an error — unavailable, which is what turns an empty field from a chore into something somebody wants filled.

How complete a commitment is

Not a judgement about tone. The question is whether a buyer could tell, later, what was promised.

Complete

It names what is being committed to and when, so a buyer can tell afterwards whether it was kept.

Open

It says plainly that something is unresolved, and what happens next. Honest, and it counts as a promise outstanding until somebody closes it.

Vague

It sounds like an answer without being one. The shape to worry about, because both sides leave the exchange believing different things.

What a limit check can say

A throttle rather than a brake: the point is a ceiling and a record, not a refusal. You set the numbers — Reynforce supplies the dimensions and the total nobody currently has.

Pass

The action was inside every limit that applies to it, and what it spent is recorded.

Warn

At or past the point you asked to be told about. The action goes ahead and the reading is recorded.

Throttled

Past the limit, with throttle chosen, so this action stops. There is no queue to defer into, so the answer is not allowed rather than needs approval.

Halted

Past the limit, with halt chosen rather than throttle. Both stop the action, and which one it was is recorded, because they are two different instructions from you.