ᚲ.com

K09 · bounded executable evidence infrastructure

Continuous-Assurance Scheduler Exports

Direct answer

K09 generates 6 inspectable schedule exports but operates no public scheduler or monitor.

Stable record
K09-PAGE-SCHEDULER-EXPORTS
Claim status
VERIFIED PROJECT IMPLEMENTATION
Last reviewed
Research cutoff
Source type
GOVERNED PROJECT KNOWLEDGE
Currentness
Current for release 2.1.0; external sources require periodic revalidation.
Correction state
No unresolved public correction recorded for this release.
Machine record
Static JSON record
Authority and disclosure boundary. K09 publishes static tools, synthetic fixtures, source-derived event records, signed offline imports, non-certifying traces, redacted procurement structures, and public/protected partition schemas. It does not perform live monitoring, reveal protected topology or credentials, decide awards, certify facilities, authorize operations, or prove factual truth from a signature.

External schedule definitions

State transition example

Each schedule defines a freshness window, missed-observation state, exception expiry, degraded claim state, repair, and retest. An external owner-operated observer must produce a signed evidence bundle; the static site never runs the schedule or accepts an observation automatically.

Export formats

Each record has a machine JSON export, a cron line, a systemd service template, and a systemd timer template under /exports/k09/. Templates contain no credentials and are not installed by this release.