AENET.cloud PUBLIC GATEWAY
K.PUBLIC.GATEWAY
system-detail K.PUBLIC.SYSTEM

public-time

Public Time

The public time service of AENET Cloud Public. It serves canonical UTC with an explicit quality, and never claims atomic verification without a verified atomic source.

Status: active Last updated: 2026-08-16

System ID

public-time

Status

active

Architecture layers

  • L4 Public Service

Inputs

  • Server clock (UTC)
  • Optional external sync (not yet verified)

Outputs

  • Time API responses with quality
  • UI time-rail ticks

Public interfaces

  • GET /api/v1/time

Security boundary

Read-only time service. It exposes only the current time and its quality — never internal clocks, never core time, never identity.

Data direction

Server clock → time service → API/UI. Read-only.

What

Give the public site and API a truthful, canonical time source with an explicit quality label (SERVER_UTC today).

Why

Public content needs one canonical time that is honest about its own accuracy. Public Time solves this with SERVER_UTC as the only truthful quality until an atomic source is verified.

How

Server clock → time service → API/UI. Read-only.

  • Serve GET /api/v1/time
  • Return canonical UTC timestamps
  • Expose an explicit quality (SERVER_UTC, never faked ATOMIC_VERIFIED)
  • Degrade gracefully on sync failure
  • Support the UI time rail (server UTC + monotonic client clock)

Example

The UI time rail ticks with SERVER_UTC and GET /api/v1/time returns canonical time with a quality field.

Inputs

  • Server clock (UTC)
  • Optional external sync (not yet verified)

Outputs

  • Time API responses with quality
  • UI time-rail ticks

Dependencies

aenet-cloud-publicpublic-api

Lifecycle

  • SERVER_UTC (current)
  • EXTERNAL_SYNC (future)
  • ATOMIC_VERIFIED (future, only when verified)

Use cases

  • The UI shows a live UTC time rail
  • Developers read canonical time through the API
  • Build metadata uses canonical UTC timestamps

Limitations

  • atomicVerified: false — the only truthful quality is SERVER_UTC
  • No atomic source is claimed until verified
  • Never fakes precision

Questions people ask

These questions are answered by the content on this page.

  • What is AENET Public Time?
  • What time quality does AENET expose?
  • Is AENET time atomic-verified?
  • How does the public time API work?

Evidence

Verified states only — nothing on this page is a prediction.

  • contracts/public-time-source.contract.json
  • server/services/time-service.js
  • server/routes/api-v1.js
  • docs/TIME_DISCIPLINE.md

Next step