Skip to content

Crossings ​

Every frame names its crossing, the boundary where the decision reaches its recipient. A decision often crosses it only through something made from its evidence: metric lines become an incident's cause, a meeting becomes its minutes, a year of findings becomes a strategy. A crossing frame tests whether what the anchors said survives that making, with the maker inside the reading, and its verdict says whether the decision is carried across the boundary or cooled at it.


Two directions ​

A crossing changes the grain, and the locus moves with it. Which way a frame reads it depends on whether the artefact can be made again:

  • Out, through a maker that runs again: the frame's spans are the evidence on the near side, and a maker writes the artefact from each trial's body before a reader decides from it. Every trial changes the evidence before the maker sees it, so ablation asks whether the decision still moves when the maker never saw the anchors.
  • In, from an artefact made once: a poem already written, a report already filed, a dream told the morning after. Nothing can make it again from changed evidence, so a frame reads its lines as they are, with any battery, and each span names the exact text it crossed with in source.

The same holds upward: findings become a brief, and a brief a decision about a product's posture. Each step is a crossing of its own, and each can be tested where it happens; what a later step finds, Recoil carries back across them to the step that lacked it.


A frame that crosses out ​

Write it as any frame: the evidence on the near side is its spans, and the question the far side answers is its input. The frame's instruction and labels are the reader's, and its crossing names the artefact, such as "the cause section the commander reads".

The battery line names the maker, with its own instruction of what to write, and the reader, so the frame's hash names both. The crossing battery runs it, and Batteries holds that line, what each side sees and spends, and how to write a maker in Python. The crossing example writes one incident up two ways, as a cause section and as a status update.


What the verdict says ​

The categories read as they do for any frame, with the maker inside the reading:

  • Carried: what the anchors said reached the decision through the artefact, and the frame's checks held.
  • Cooled: the decision did not move without the anchors. Either the maker dropped what they said, or the reader never used it.
  • Unresolved: often openings from one side, and each opening names which.

A reader that refuses what it was given should return an opening, not a label: the opening names the side and the reason, while a refusal answered as a label sits in the baseline and leaves nothing for the trials to move. The reader sees the artefact and the input alone, so a reader that checks the making against the evidence needs the maker to carry that evidence in what it writes.

To tell a lossy maker from a reader that ignores the evidence, read the baseline's artefact on its own, in a frame of its own: its span is the artefact, its source is the SHA-256 the crossing's record kept, and its anchor is the artefact itself. If the reader moves there but not through the crossing, the maker lost it.


Provenance across the boundary ​

A span may name the text it crossed with: source holds that text's SHA-256 and, optionally, where it came from. The parser holds the span's text to the hash byte for byte, so a frame cannot quote what it did not receive, and a changed source is a changed frame:

json
{
  "id": "s2",
  "text": "The deploy shrank the connection pool.",
  "kind": "cause",
  "source": {
    "sha256": "<the SHA-256 of the text>",
    "from": "the incident's cause, as written"
  }
}

A crossing's records keep each artefact's SHA-256, so the next frame in a chain names the one it reads, and a reader of both can follow the evidence from one grain to the next.