Layer1Labs is raising seed funding — $1–1.5M on a SAFE, seeking a lead investor. Talk to us →
Reference Manual · ChronoHive · ChronoFabric

Chronoc Reference Manual

The full reference for the Chrono target and the chronoc compiler: the language subset, the intrinsics and manifest, the compiled specification, and the execution contract — for both the software engine and the hardware tier.

Version 1.0 · October 27, 2026 · PDF · 27 pages · Layer1Labs Silicon Inc.

Key figures

CSP1

the compiled specification’s format — versioned and sectioned, CRC-32-checked, and validated in full on every read; a rejected read loads nothing

The compiled artifact

1,563 bytes

the compiled specification in the worked example — 12 operations in a single schedule step, from the TrafficGrid program printed in full on the How It Works page

Worked example — TrafficGrid

v0.13.0

the Lingua Franca language baseline the Chrono subset is pinned to; the pinned compiler build is chronoc 0.1.0

Language baseline — pinned

3 layers

the intrinsic profiles model — a specification-owned core profile, named and versioned domain profiles, and namespaced application extensions; an engine claims a profile by passing its conformance battery

Profiles — adopted model

What it covers

  1. How to read this manual
  2. The system in one chapter
  3. Architecture, end to end
  4. Why Chrono is not ordinary Lingua Franca
  5. The language subset: what a Chrono program may contain
  6. From program to schedule
  7. The compiled specification (.cspec, format CSP1)
  8. Intrinsics and the effector manifest
  9. Execution: the kernel contract
  10. Extensibility: imports, packages, and libraries
  11. Integration: the software engine (ChronoHive)
  12. Integration: the hardware tier (ChronoFabric)
  13. Conformance and portability
  14. Pins, versions, and provenance
  15. Worked example: TrafficGrid

Basis

This manual assembles the Chrono target as published across the Layer1Labs site and its documents: the architecture as the pages state it, the format and execution contract as the public developer documentation specifies them, and the worked example exactly as it runs in the traffic demo. It makes no new claims, and its depth limit is the site’s own — interfaces and contracts in full, with no implementation internals.

The manual is candid about status. The intrinsic profiles model it describes has been adopted as the design and is being implemented; the manual marks which of its rules are in force and which are adopted and still landing. Everything else it states as reference is the behavior of the pinned toolchain — Chapter 13 records every pin.