CONTROL FRONTIER · WORKFORCE API PLANNED

Two clocks. One traceable decision.

Effective time describes when a fact applies; recorded time describes when it became known.

Effective-dated history

Use half-open intervals [effectiveFrom,effectiveTo). A retroactive correction appends a revision; it does not erase the earlier known state. Queries use both at and knownAt. Existing relationship and appointment history are foundations; employee attribute history remains proposed. The first complete workforce release must include it.

Fact effective:   [2026-01-01 ─────────── 2026-06-01)
Recorded version: 2026-06-10 — original observation
Correction:       2026-07-02 — new recorded revision

At 2026-03-01, knownAt 2026-06-15 returns the original observation. A later knownAt can return its correction.

Release status

The guides and API reference describe the reviewed design. Workforce API operations and complete integration remain proposed. Existing application capabilities are source-verified, not a public availability guarantee.

Continue

Explore the API design reference →