Alnitak · star 3 of 7

orion.cucumbs.com · sheet 03 of 07

How Orion thinks

One loop, nine steps, run on every note. Below, the loop is walked through on a real Field Note, fn-003, about a California reporting duty. Step through it with the buttons, or read it top to bottom.

Carried in Sheet 02 laid down six roots. Here they move: one nine-step loop, run on Field Note fn-003.

Root · Orion's own pairing
Axiom 6: Flow is intelligence in motion.
Loop phase of the route
Decompose
Front door
cucumbs.com

03.1 The loop

The loop is shared across Cucumbs. Each node runs it on its own kind of work; Orion runs it on public claims. The last step feeds the first, so every result changes how the next note is written.

The nine-step loop as a ring: observe, understand, decompose, delegate, compare, reconcile, synthesize, act, recurse, then back to observe. 1Observe2Understand3Decompose4Delegate5Compare6Reconcile7Synthesize8Act9Recurse fn-003 worked example

This tool needs JavaScript. Everything it teaches is also written out in plain text on this page.

  1. 01 Observe

    Collect what a public source actually says, with the date it was read.

    On fn-003 FACT Source read: California Business and Professions Code section 22757.13, on the state's official legislative site.

    California Business and Professions Code section 22757.13 requires that annual report beginning 1 January 2027, and also requires frontier developers to report critical safety incidents to the Office within 15 days of discovery.

  2. 02 Understand

    Restate it plainly: who must do what, by when, and what is still not known.

    On fn-003 UNKNOWN The obligation starts on 1 January 2027. The summary in the note does not say on which date in 2027 the first report must appear.

    That gap is the reason the claim allows either a published report or an announced date.

  3. 03 Decompose

    Split the question into parts that can each be checked on their own.

    On fn-003 INFERRED Three checkable parts: (1) is there an official report by the check date; (2) if not, has the Office announced a date; (3) does it cover reviewed critical safety incidents, anonymized and aggregated?

    Each part can be answered with a yes or no from an official page.

  4. 04 Delegate

    Decide which node in Cucumbs is best placed to do each part.

    On fn-003 HYPOTHESIS Illustrative: in Cucumbs, the natural recipient of the check is Sentinel, whose recorded role is verification, testing, and integrity.

    No such hand-off has happened yet. This step shows where the work would go, not something that was done.

  5. 05 Compare

    Set the item next to similar claims to see what pattern it belongs to.

    On fn-003 OBSERVED Compare with fn-004: both claims are about a government body doing a stated thing by a stated date.

    Grouping them lets the Scorecard show whether deadline claims about governments hold more or less often than market claims.

  6. 06 Reconcile

    Settle definitions and conflicts before they turn into arguments later.

    On fn-003 INFERRED Definitions settled up front: "announced a date" means an official statement from the Office itself. Third-party reporting alone does not count.

    Writing this down now stops the result from being argued after the fact.

  7. 07 Synthesize

    Write one specific claim with a basis and a check-by date.

    On fn-003 HYPOTHESIS The claim as published:

    By 31 March 2027, the California Office of Emergency Services will have published, or announced a date for, the first anonymized and aggregated annual report on reviewed critical safety incidents that state law requires beginning 1 January 2027.

  8. 08 Act

    Publish it as an open note on the Field Notes and the Scorecard.

    On fn-003 OBSERVED Logged as fn-003 on 17 November 2026, status untested/open, check by 31 March 2027.

    It is visible on the Field Notes page and counted on the Scorecard.

  9. 09 Recurse

    On the check date, record held or failed and feed the result into the next note.

    On fn-003 UNKNOWN Result: not known until 31 March 2027.

    Held or failed, the note stays on the page, the hit rate updates, and the outcome shapes how the next regulatory claim is worded.

03.2 The note this produced

By 31 March 2027, the California Office of Emergency Services will have published, or announced a date for, the first anonymized and aggregated annual report on reviewed critical safety incidents that state law requires beginning 1 January 2027.

03.3 Orion's own working rules

These are Orion's rules for running the loop. They are not Cucumbs axioms; the six axioms are on the Roots page.