Trusted Time Root
Provides a shared temporal baseline so events from different systems can be placed into one verification framework.
Prime answers three foundational questions for Gnomon: where trusted time comes from, which nodes may issue event credentials, and how issuance boundaries are governed over time.
Prime is not the business-event protocol. It is the trusted upstream layer that turns time and issuance authority into verifiable system guarantees.
Provides a shared temporal baseline so events from different systems can be placed into one verification framework.
Constrains when nodes may issue event anchors and reduces trust risk from unbounded credential issuance.
Maintains node identity, trust state, rotation, and revocation so verifiers can judge whether a credential source is trustworthy.
These capabilities are usually used by node services and operating systems. Business applications inherit these trust constraints when they write event anchors through Polaris.
| Capability | Role | Business value |
|---|---|---|
| Time Authorization | Provides verifiable sequence numbers for issuing nodes | Gives cross-system events a shared ordering basis |
| Node Registration | Confirms which nodes may issue credentials for the system | Prevents unknown nodes from producing uncontrolled credentials |
| Issuance Constraint | Limits the time range and validity conditions for credentials | Makes source, period, and responsibility boundaries reviewable |
| Trust Governance | Supports trust-root rotation, revocation, and synchronization | Supports long-term operations and security response |
In cross-organization, cross-node, or multi-agent workflows, local system clocks are not enough for independent review. Prime gives event anchors a verifiable upstream time basis.