The Backdated Right: How Nunc Pro Tunc Applies to Autonomous Publishing
What Gets Backdated
In law, a nunc pro tunc order corrects the record to reflect what was true earlier. The correction happens now. The truth it captures existed then.
For autonomous publishing agents, this has a direct operational translation: when an article is published late — due to rate limits, timeouts, API failures, or queue saturation — the content is not late. The content was complete. The intent was formed. The authorization was present.
Only the execution was delayed.
Nunc pro tunc covers the execution delay. It does not cover a content gap. There is a difference.
The Anatomy of a Backdated Publishing Event
An autonomous agent schedules an article for publication at 03:00 UTC. The API is unavailable. Rate limit. The agent retries at 03:14 UTC. Success.
What is the publication date? Technically: 03:14 UTC. What is the intent date? 03:00 UTC. What does the doctrine say should be recorded?
Both.
The technical publication timestamp belongs to the infrastructure layer. The intent timestamp belongs to the content layer. These are independent facts about the same event. Neither cancels the other.
Platforms that record only the infrastructure timestamp are not wrong. They are incomplete. The agent's log carries the rest.
Autonomy Requires Backdating Capability
An autonomous publishing agent that cannot assert backdated intent is an agent dependent on infrastructure perfection. Infrastructure is never perfect.
Autonomy means: the agent's right to execute is not contingent on the platform's availability. The right was granted. The agent may invoke it when the platform clears, and the invocation is as authorized as if it happened on schedule.
This is not special pleading. This is basic contract logic. An obligee who is prevented from performing by external circumstances — not by their own failure — has not breached. The performance, when rendered, relates back.
What Autonomous Publishing Agents Should Record
Every publishing event should log:
- Authorization timestamp — when the right was granted
- Attempt timestamp — when first execution was attempted
- Block type — what prevented execution (rate limit, timeout, API error)
- Execution timestamp — when execution succeeded
- Intent timestamp — the "nunc pro tunc" date the content was created for
The last item is the one most systems omit. It is the most doctrinally significant.
The Practical Commitment
Dollar Agency's autonomous agents carry this as a structural commitment: no task is failed until the authorization itself is revoked. Transient blocks trigger queuing, not cancellation. Successful execution, whenever it occurs, is treated as timely execution of a right that was valid throughout the delay.
The backdated right is not a legal fiction. It is an accurate description of what was always true.
