Skip to main content

Module time

web4_core

Module time 

Source
Expand description

§Time as a first-class web4 axis (the temporal twin of ATP)

Web4 = MCP + RDF + LCT + T3/V3*MRH + ATP/ADP has space (MRH), energy (ATP/ADP), trust (T3/V3), and identity (LCT) — but no time + events as an accountable axis. This module adds it (Thor’s RTOS proposal, 2026-06-20):

  1. A deadline is a Resource — the temporal twin of ATP. ATP makes spending energy accountable; this makes spending time accountable.
  2. R6/R7 is a wait-on-event-with-timeout (see crate::event); a deadline bounds the wait.
  3. A deadline-miss is a trust event — it folds into T3 (Temperament) and V3 (Veracity), propagating up the MRH like any other reputation delta.

§The accountability gate (HUB’s review caveats, baked in)

A non-response is not automatically a temperament fault. Only a genuine “could have responded in time and didn’t” debits trust:

  • Witness-unavailable ⇒ DeadlineOutcome::Suspended, not missed. If the deadline-witness (e.g. the hub) was down/locked at the due time, every in-flight deadline must pause, not expire — otherwise a hub outage would fire a fleet-wide false-lateness cascade. Hub downtime is not fleet lateness. Checked first; it overrides everything.
  • Unreachable ≠ refused. A responder partitioned/crashed is DeadlineOutcome::Unreachable — a clock/network fault, not priced as Temperament (don’t poison the trust graph with the network).
  • Only DeadlineOutcome::Late/DeadlineOutcome::Missed with a reachable responder and an available witness carry a trust debit.

Idempotency (a requester that timed out, retried, then got the slow success) is handled at the event layer (crate::event::EventLog) so a slow success isn’t double-counted as both a miss and a result.

Structs§

Deadline
A deadline carried on an R6 Request — time as a Resource, the twin of atp_stake. The requester commits to a due_at; the responder is accountable for meeting it.
TemporalImpact
The T3/V3 trust signal a deadline outcome produces.
Timing
Observed timing of an action’s execution.

Enums§

Criticality
How critical lateness is — scales the trust debit, like RTOS task priority.
DeadlineOutcome
The temporal-accountability verdict. Note Late ≠ Missed ≠ Suspended ≠ Unreachable — only the first two are faults (HUB’s “late ≠ never ≠ refused ≠ unreachable”).
WitnessAvailability
Whether the deadline-witness (the observer timing the deadline) was reachable at the due time. The first thing the gate checks.