Inputs
- Event timestamps and scheduling context
- Cadence configuration
- Decision and execution records
Operations
NTC
A temporal scheduler inside the control plane.
NiZiNG Temporal Controller — an in-process temporal scheduler and cadence controller. Not a causal validation engine.
Responsibility
What NTC is responsible for
NTC is an in-process temporal scheduler and cadence controller in the Control Plane, with ingress and status surfaces. It schedules and paces work. It is not a separate causal-DAG clock, and the reviewed ADAPTIVE mode is refused at startup.
Distributed systems disagree about time. NTC provides temporal scheduling and cadence inside the Control Plane so work can be paced and observed rather than relying on wall-clock assumptions alone.
The capability is presented as in progress because the reviewed evidence supports a scheduler, not a causal validation engine. The separate causal-DAG temporal clock described in some architecture material was not found, and live feedback behaviour was not demonstrated.
Lifecycle position
Where it sits in the governance lifecycle
Stage numbering is canonical across the site. Open the interactive lifecycle to see every component with responsibilities at each stage.
Decision
Coordinate policy, constraints and uncertainty.
Evidence and audit
Keep linked, ordered, reviewable records.
Verified capabilities
What is verified today
Capabilities are drawn from the product register. Each one is bounded by the limitations stated further down this page.
- In-process temporal scheduling and cadence control
- Temporal status and ingress surfaces
- Scheduler modes OBSERVE and SHADOW (do not change timers)
Outputs
- Scheduled/paced work
- Temporal status records
- Validation results where configured
Evidence and maturity
What the evidence supports
Maturity describes verified engineering evidence in a bounded environment. It is not a production-readiness statement.
Maturity note
The scheduler, cadence and status/ingress surfaces exist and are partially integrated. The current Control Plane controller reports configured=false, the console route returns 503 for it, ADAPTIVE mode is not eligible, and OBSERVE/SHADOW do not change timers.
Not production-qualified
This label describes verified engineering evidence only. No production deployment, certification, benchmark or customer outcome is claimed.
Evidence recorded
- NTC final report: scheduler/cadence implementation and mode eligibility.
- Capability audit 2026-11-03: NTC controller configured=false; console route 503.
- Known limitation 2: NTC_E2E_* fixtures and credentials unavailable.
Dependencies
- Control Plane
- audit ledger
Dependencies are stated as the product register records them. A dependency is not automatically production-qualified; see its own product or component page for its maturity and limitations.
Limitations
What this product does not do (yet).
Limitations are stated before the evaluation questions so they cannot be missed, downplayed or treated as future-work footnotes.
Limitations — read before evaluating
- Not a causal validation engine: no separate causal-DAG temporal clock was found.
- ADAPTIVE mode is not eligible; OBSERVE/SHADOW do not change timers, and live feedback was not demonstrated.
- The current Control Plane controller reports configured=false and the console route returned 503 in the reviewed deployment.
- No distributed-clock or consensus guarantee is claimed.
No capability on this page should be read as production qualification. If a limitation is material to your use case, it belongs in the evaluation scope — not after it.
Relationship to the platform
How it fits
NTC supplies the time dimension for decisions and evidence. It does not authorise actions; it makes the ordering of governed events reviewable.
Evaluation questions
- Which ordering guarantees are required for your workflow?
- How is a clock disagreement represented rather than hidden?
- Can temporal context be reconstructed for an audit?
Next step
Evaluate NTC against a real control problem.
Bring a system boundary, an action class and a failure mode. The first step is to agree what should be governed and what evidence would count.