Jadpo is experimental and not ready for production. These docs follow the compiler's main branch as of 5 Nov 2026. What's built · Install 0.3.0

ReferenceErrors

Errors Configuration · rule

`type.temporal_clock_invalid`

Clock time is not written HH:MM.

Area 10, Configuration; not declinable; the next step is usually the agent's.

example

type ShopDay = CalendarDate {}type Opening = ZonedTime {}function opening(day: ShopDay) -> Opening {    return Opening(temporal.resolve(day, at: "9:30", zone: Zone.utc, dst: Dst.later))}

jadpo checkcheck failed: 1 error, 1 file

error "9:30" isn't a clock time

--> main.jadpo:6:46

  |6 |     return Opening(temporal.resolve(day, at: "9:30", zone: Zone.utc, dst: Dst.later))  |                                              ^^^^^^ not `HH:MM`

reason: temporal.resolve's at: is a clock time written HH:MM, or HH:MM:SS with seconds, each part two digits, from 00:00 to 23:59.
next: Write the time with two-digit hours and minutes, such as "09:30" (agent)
rule: type.temporal_clock_invalid
help: https://jadpo.dev/docs/errors/type.temporal_clock_invalid

Markdown for agents: /docs/errors/type.temporal_clock_invalid.md.Built from Jadpo main at aee2e8f.