Skip to content

Relational orchestration: how work enters, gets stored, gets executed, and gets verified done in the relational machine context.

Relational Orchestration

RelationalOrchestration is Orchestration as implemented in a relational machine context — where work units are typed markdown entries and stores are locale context files.

Work storage

Work lives as markdown files. Two kinds of work files exist in every locale:

There is no separate state store — reading INBOX and PLANS gives the full picture.

Loop closure

Every locale has two loops that must stay closed:

Triage loop — INBOX messages → OperationItems in PLANS. Done when INBOX is empty or every message has a corresponding OperationItem.

Improvement loop — open OperationItems → completed OperationItems. Done when no open non-blocked OperationItems remain.

A loop is closed when its done condition holds. Stale OperationItems and unread INBOX messages are worse than ignorance — they actively misdirect.

Open questions

Relations

Ast
Date modified
Inbox
Relational universe
Locale
Relational universe
Output
Relational history fiber fixed layer
Plans
Relational universe