Thesis & writing
Thesis · 03Authority

Authority as a time-bound system

Authority is not a static property of identity. It is a time-bound claim that must remain replayable if it is to be trusted.

On this page

Treat authority as a static role assignment and one question goes unanswered: did this actor have the authority to perform this action at this exact point in time?

That separates two requirements: current authority and historical authority. Knowing who can act now does not establish who was entitled to act then.

At this moment

Valid authority —
Expired authority —
Broken chains —

Permitted

—

Denied

—

Delegated authority carries a scope and a validity period, not just a role name.

Carbon markets make this failure particularly visible. Authorisation of credits involves bounded approvals, delegated signing rights, multi-party verification, and audit obligations that stretch across jurisdictions and time. The actors change. The windows close. The records must survive scrutiny months or years after the fact.

That makes carbon a useful proving ground. But the underlying problem is not specific to carbon. It appears anywhere approvals, delegated rights, audit obligations, or regulated actions depend on who was entitled to act at a given moment. Financial settlement. Clinical trials. Procurement. Supply chain attestation. Government licensing. The domain changes. The failure mode does not.

Where real systems fail quietly

Not through dramatic compromise. Through ordinary continuation.

Here is one way it happens. A programme director delegates signing authority to a regional approver on 11 May. The delegation window closes on the 18th. On the 17th, the approver submits a budget approval. Valid. Two days later, a countersignature is submitted against that same approval. The delegation expired sixteen hours earlier. No replacement grant was issued.

The countersignature is recorded. The process moves forward. The funds are released. Three months later, an external audit asks for the authority chain behind the release. It does not exist. The delegation had lapsed. The countersignature was recorded under authority that had already expired. Nobody noticed because the system never checked.

That is a foreseeable failure when expiry is not checked at the point of action. A recorded approval and a valid approval are different things.

Event Stream

Authority State

The event happened. That does not mean it was valid.

Treating authority as a time-bound system changes what the model must represent. A grant is more than a relationship between two parties. It is a claim with a beginning, often with an end, sometimes with conditions, and sometimes with dependency on another grant above it.

The model has to account for turnover, substitution, emergency access, temporary delegation, absence, expiry and exception.

A current permission table leaves out a dimension that later review depends on.

Time.

1 May7 May14 May21 May28 May

A delegated action depends on the grants behind it, including their scope and expiry.

Authority is about accountability

When someone acts in a serious system, you need to know four things.

Who acted.
What they did.
When they did it.
Why they were entitled to do it then.

The fourth answer becomes difficult to recover when authority is not preserved with the action.

Sometimes because the answer is buried in emails. Sometimes because someone updated a group after the fact and the historical state is gone. Sometimes because the system was never designed to preserve the authority context of the action at all.

The gap matters because a recorded action does not establish that its actor was entitled to take it. That requires evidence of the authority in force at the time.

An internal dashboard can report the action.
An audit must examine its authority.
A dispute must examine the evidence.
Independent participants need a record they can check.

Action

Release funds for Project A

Actor: Sarah Malik Time: 21 May, 09:23

Authority worth trusting must be replayable at the moment it mattered.

What this demands from the architecture

Replaying preserved grants is not the same as inferring past authority from today's permissions. Our design commits to the former.

Authority must be versioned over time.
Delegation must be explicit, not implied.
Expiry must be a native condition, not a manual cleanup.
Revocation must be traceable.
Historical validity must be queryable at any past moment.

Actions that depend on authority must carry a reference to the authority state that made them valid at the time they were taken. Without that binding, the same action can look valid today and invalid tomorrow. That is not a trustworthy record. That is a moving interpretation.

Which brings the earlier distinction into sharp focus. A serious system must answer two separate questions.

Current authority: can this actor act now?

Historical authority: was this actor entitled to act then?

Answer the historical question with current permissions and the interpretation changes with every update.

Current authority

Temporary Approver

Invalid

Delegation window closed. No active grant.

Historical authority at 21 May, 09:17

Temporary Approver

Valid

Delegation active. Full chain to board authority intact.

The same actor. Two points in time. Different authority.

Current validity and historical validity are not the same question.

We are betting that more work will cross organisational boundaries and be delegated to agents. The authority behind that work must remain inspectable.

That is a requirement we are building around.

Preserve the authority to act, not just the fact that an action was recorded.

Carbon makes this failure easy to see because the actors, windows, and audit obligations are explicit. But the same structural problem appears wherever authority, money, risk, approvals, compliance, or machine actions depend on who was entitled to act at a specific moment. The domain changes. The failure does not.