# The bounded process figure

Target length: under 1,450 words, quote apparatus included.

## Source and inspection

The controller rendered model.png and data-structure.html from the model registers, propositions and table after account.md was written. Render version 22d1db6ab878791ec8f0f54d7aa0797e0fe0ef9a6c06d1feac91f5eaa4aedc4d. The native image inspection found legible, uncropped box text and the correct endpoints and proposition tags. No source relation needed repair. The source table was read through the gateway after render.

The raster is a two-column lattice of bounded process pairs, not a complete mediating process chain. Its vertical order is graph layout, not time. In particular the upper position of `P08` does not mean printing precedes proposing a mark. The mechanism explanations below supply the missing middle; actual effects on survival, agreement and delivered prints remain unknown.

## External clock, part of the figure

| Observation panel | Imposed terminus | Observation panel |
|---|---|---|
| Live placement at or before hour73; public proposals, contribution, adjustment, care and disputes | HOUR73: PLACEMENT STOPS | After73 through97; critical accounts, venue consolidation, valuation and pending display work |

This textual clock annotation belongs beside the raster in the composite figure. The renderer's box graph itself has no clock band; the caption supplies it without inventing a causal element or a node in the immutable model. `P07` also has a live completion report and `P08` a live banner proposal. The panels do not imply that all valuation began after73 or that closure caused a print. No arrow crosses this table's terminus.

## Boxes, relations and mechanisms

Use every standing source box, named exactly as model/elements.jsonl: `P01` proposing a recognizable mark; `P02` committing a contribution; `P03` revising how contributions meet; `P04` proposing, refusing or repairing terms of reach; `P05` watching, cleaning and restoring; `P06` setting participation terms; `P07` presenting and valuing achieved work; `P08` pursuing display; `K01` reported interference; `K02` disputed reach/costs; `K03` event traffic obstructing ordinary use. These shortened descriptions identify boxes, not replacements for their source wording.

Draw `A01/N01` from `P01` to `P02`: the proposed object gives an answering helper an identifiable target. It is recorded order, not a quantified recruitment effect. Instance `E-03` has these individually cited endpoints:
> Voorstel om op /r/place een grote Nederlandse vlag te tekenen

`c0052`; r/thenetherlands; uZQPvcOWTSuYwIXkYPLI+K5Gj5o=; hour1.8233333333333333; item `62ms9a`; thread `62ms9a`; offsets0-61; cite7183.

> Ik ga je meehelpen daar!

`c0053`; r/thenetherlands; MEPLY9ggUfl88Div+nViLWE/gaE=; hour2.116388888888889; item `dfnro19`; thread `62ms9a`; offsets0-24; cite7185.

Draw `A02/N02` from `K01` to `P03`: reported interference reopens how contributions meet and supplies a reason to request targeting or layout changes. The arrow establishes the remedy attempt. The quoted instances in `E-05` are:
> Help mee met paarse tekst! We zijn te veel aan het corrigeren om verder te komen!!

`c0074`; r/thenetherlands; GvQZVsiP84Jlq6JA3RPQaKU78xE=; hour7.031944444444444; item `dfo6ie2`; thread `62n832`; offsets200-282; cite7375.

> Dan blijven we niet onszelf de hele tijd overschrijven en kunnen we gericht Oranje en zwarte tegeltjes blijven leggen.

`c0232`; r/thenetherlands; ZlC8lJC2xd8GeO4rAskLnH5UdNY=; hour23.148611111111112; item `dfozsqf`; thread `62t1k7`; offsets89-207; cite7187.

Draw `A03/N03` from `K02` to `P04`: disagreement redirects one contributor's claimed repair effort. Instance `E-13` is:
> I'm trying to help with your flag, seeing how I didn't agree with the expansion at the western border.

`c0240`; r/thenetherlands; aAiOEeyzNb5zHul5t7g6DzFipe8=; hour47.053333333333335; item `dfq9mee`; thread `62t1k7`; offsets0-102; cite7195.

Draw `A04/N04` from `K03` to `P06`: invoking ordinary use gives the routing act a jurisdictional reason. Instance `E-14` is:
> Please use /r/PlaceNL or /r/Cirkeltrek or https://discord.gg/S4VPhdk for these requests so this subreddit can still be used normally.

`c0349`; r/thenetherlands; WwFof85S1CVdowkWg2YobOuHH7I=; hour48.56861111111111; item `dfqdgi8`; thread `630kj1`; offsets0-133; cite7197.

Every arrow is quote-supported. The registers contain no dated transition-array support, so no elapsed interval or measured transition is drawn. Calling `A02`, `A03` and `A04` transitions describes their stated connections; it does not turn them into instrument-measured event transitions. All remain fair, bounded links. No arrow carries a dimension-level shared mechanism.

`P05`, `P07`, `P08` remain visible and disconnected. Do not join care to survival or achievement to the print. No dated loop is registered. Versions with and without theorised arrows are identical because no theorised arrow is admitted to model/arrows.jsonl. The excluded conjectures stay in prose rather than gaining new arrow IDs or dotted support they do not have.

## Coverage annotation

The following are quote-support code inventories, never community counts, prevalence or effect sizes. Each uses the closed coded frame0 through97 inclusive; neither endpoint contains a code. The exact matched IDs are `A01`:`c0052`,`c0053`; `A02`:`c0074`,`c0232`; `A03`:`c0240`; `A04`:`c0349`.

`A01`: {"mode":"coverage","unit":"codes","n":2,"denominator":{"unit":"codes","n":414,"of":"closed coded record, hours0 through97 inclusive"},"receipt":7367}.

`A02`: {"mode":"coverage","unit":"codes","n":2,"denominator":{"unit":"codes","n":414,"of":"closed coded record, hours0 through97 inclusive"},"receipt":7369}.

`A03`: {"mode":"coverage","unit":"codes","n":1,"denominator":{"unit":"codes","n":414,"of":"closed coded record, hours0 through97 inclusive"},"receipt":7371}.

`A04`: {"mode":"coverage","unit":"codes","n":1,"denominator":{"unit":"codes","n":414,"of":"closed coded record, hours0 through97 inclusive"},"receipt":7373}.

These measurements belong in the figure legend, not arrow thickness. Sampling units in the source arrows remain episodes and are not mixed with these code counts.

## What the figure leaves out

Every admitted arrow has a proposition, so none was dropped for lack of one. The graph leaves out the unsupported hypotheses that friendliness caused cooperation, planning caused the final image, appeals caused peace, alarms caused survival, celebration caused printing, or bots caused a measured gain. No claim that a universal problem was solved is drawn. `t06` and `t10` remain contextual, with the latter's banner idea explicitly preserved in the table and `P08` evidence. Venue rule enactment, jokes, alarm, pride and moral criticism have different registers; the diagram cannot show their phrasing or every variation. The production residue, reuse permission and obtaining analysis remain named in the account rather than joined by invented arrows.

The first table display exposed literal HTML break markup. The source now uses straight quote marks and parenthesized attribution; every quote and placement is unchanged. The controller rerendered the same model graph with that corrected table, and its final image and source table were inspected before confidence.

Close validation required explicit tier headings and quote-local code/hour attribution in the table. That source-only correction was rerendered and inspected before the unchanged confidence judgments were resubmitted.