# R4 dynamic model, pass 3 Target length: under 1,000 words of main prose, followed by the apparatus. ## Claim and puzzle r/norge's public record shows people making contributions usable, answering practical requests, regulating where discussion appears, negotiating or fighting over room, and disputing what can be done in their associated name. Those achievements do not establish one organization with an accepted goal or authority. The puzzle is how linked action is possible while the reach of the collective remains unsettled. The candidate explanation is local and partial. One set of responses corrects a mistaken reading of work; another works on the venue where people can gather; a moderator-backed destination becomes a post-routing rule. These concrete mechanisms are more directly evidenced than a general account of how every territorial outcome was decided. The model does not claim the smallest public exchanges caused all the large drawings. ## How the local responses work People propose objects and make outlines, proportions and templates usable in `P01`. Interference can occur even among people defending the same emblem (`K01`). Acknowledging misrecognition in `P02` can lead to a stated adjustment in `P03`, retained as `A01`. The apology about white pixels and the Russian-heart reply explicitly join an old reading to a new intention. The later solidarity warning at hour 71.48777777777778 did not cause the earlier apology at 71.2525. These are not measurements of changed pixel behaviour. A known Sami project can lose despite help and specifications, so this mechanism does not settle deliberate opposed goals. Difficulty organizing or following talk (`K02`) is itself made into a practical task: request, offer or open another gathering place (`P04`, `A02`). A Discord request receives an invitation, a large collection thread is replaced, and the successor group receives a qualified offer of a public subreddit. The offer is not a completed maintained venue. This relation rests on explicit reason-giving and linked replies; its negative test outside those episodes remains weak. Where a collection destination is backed by post-governance authority (`K04`, `R01`), it is then invoked in redirects and reported removals (`P05`, `A03`). That is narrower than control over the drawings. The Oslo travel-post redirect positively shows targeting can go wrong. Voluntary Discord invitations do not establish equivalent enforcement. Renewed venue work shows that gathering is not a permanent solution. ## Spatial claims and what challenges the explanation Taking, defending and accommodating space in `P06` coexist with evaluation of collective purpose and standing in `P07`. The timed Greece call and invoked Crusader Kings agreement support practical planning; denial of whole-subreddit support and of official Discord standing limit attributing those decisions to everyone (`C01`). The main thread's uncoded context contains still stronger planning claims, but those remain qualifications rather than new closed codes. Disagreement does not refute episode-specific command. The Sami loss and contested Texas relocation are the largest challenges. The former defeats sufficient design clarity or early support as an explanation of preservation. The latter leaves incompatible accounts of consent, site choice and command. The model can retain the pressure, assistance, dissent and reports without pretending it has resolved which people prevailed or why. It does not explain every survival difference. These are substantive residues, not room for an extra all-purpose construct. ## Closure and what remains Original placement closes at hour 73 (`K03`); invitations to another canvas do not reopen it. Recounting, credit, regret and explanation in `P08` continue alongside practical post regulation and successor recruitment in `P09`. No retained passage attributes continuation to praise, so recognition is not drawn as its cause. The last observed practical offer remains `c0271` at hour 93.86194444444445, not a proved end elsewhere. The R2 gateway aftermath result is 17/64 distinct coded items strictly after 73, share 0.265625, receipt 1767. Its numerator mixes post governance and successor coordination, not drawing alone. Reports about the flag and Kvikk Lunsj are bounded kept outcomes; the Sami drawing is lost and last plans remain unfinished. No image or linked record was inspected. ## Elements and ranges All elements below matter to the question of becoming able to act, settling a purpose, returning to a practical problem, or what remains. Processes are named for what they do, not national subject matter. `P08` and `K03` are deliberately undimensioned. No whole-room leader role is invented. Every element's range is explicit; a standing status does not make that range universal. ### `P01`: Proposing and specifying a usable next contribution to a shared drawing. Kind: process. Tier: `T4-001`. Dimension: `D01`. Range: From a named proposal or outline to a maintenance template; excludes proof that instructions were followed or projects finished. Evidence: `c0073`, `c0074`, `c0139`, `c0142`. Since R4-pass-1; status standing. ### `P02`: Reclassifying an apparent attack as a repair or intended drawing. Kind: process. Tier: `FP-02`. Dimension: `D01`. Range: A respondent revises a mistaken interpretation; excludes knowing opposition to another project's presence. Evidence: `c0019`, `c0160`, `c0231`. Since R4-pass-1; status standing. ### `P03`: Committing to adjust a contribution after acknowledging the intended work. Kind: process. Tier: `T4-001`. Dimension: `D01`. Range: Stated individual intention to stop undoing or to help; not independently verified pixel placement or whole-room compliance. Evidence: `c0019`, `c0160`. Since R4-pass-1; status standing. ### `P04`: Proposing, creating or renewing a place to gather participation. Kind: process. Tier: `T4-003`. Dimension: `D01`. Range: A request, offer or announced creation with implementation distinguished; includes collection threads and Discord, not evidence of sustainable uptake. Evidence: `c0095`, `c0096`, `c0136`, `c0258`, `c0270`, `c0271`. Since R4-pass-1; status standing. ### `P05`: Redirecting posts and proposals into designated participation venues. Kind: process. Tier: `T4-003`. Dimension: `D01`. Range: Subreddit directions, locks and reported removals; includes misclassification and successor-post redirects, not control of canvas placers. Evidence: `c0082`, `c0186`, `c0199`, `c0273`, `c0292`. Since R4-pass-1; status standing. ### `P06`: Asserting, defending or negotiating room for adjoining projects. Kind: process. Tier: `T4-002`. Dimension: `D02`. Range: Territorial mobilization, permission, agreements and relocation offers; execution, consent and representative authorization are distinct. Evidence: `c0003`, `c0145`, `c0146`, `c0152`, `c0097`. Since R4-pass-1; status standing. ### `P07`: Questioning or defending collective purposes and claimed standing. Kind: process. Tier: `T4-004`. Dimension: `D02`. Range: Opposed evaluations and authority claims; not proof that dissent constrained work or that a unified verdict emerged. Evidence: `c0058`, `c0229`, `c0197`, `c0300`, `c0264`. Since R4-pass-1; status standing. ### `P08`: Recounting and acknowledging the effort and results of finished work. Kind: process. Tier: `T4-005`. Dimension: none. Range: Pride, credit, loss, retrospective explanation and disagreement after original placement; excludes current recruitment and consensus. Evidence: `c0246`, `c0247`, `c0267`, `c0256`, `c0281`. Since R4-pass-1; status standing. ### `P09`: Recruiting participants to continue pixel work on successor occasions. Kind: process. Tier: `T4-003`. Dimension: `D01`. Range: Explicit post-closure invitations and claimed continuation, not durable group identity or observed completion on the successor. Evidence: `c0289`, `c0268`, `c0293`. Since R4-pass-1; status standing. ### `K01`: Some participants treat an ongoing pixel change as damage to defend against. Kind: condition. Tier: `T4-001`. Dimension: `D01`. Range: Mistaken-threat instances; the same pattern cannot be assumed for deliberate opposition such as removing a known Sami project. Evidence: `c0017`, `c0019`, `c0160`, `c0231`. Since R4-pass-1; status standing. ### `K02`: Participants identify difficulty organizing or following event participation. Kind: condition. Tier: `T4-003`. Dimension: `D01`. Range: Fragmented or excessive discussion and inaccessible overview; not all event talk or every new platform mention. Evidence: `c0095`, `c0079`, `c0258`, `c0270`. Since R4-pass-1; status standing. ### `K03`: Placement on the original canvas is unavailable after hour 73. Kind: condition. Tier: `T4-005`. Dimension: none. Range: Instrument setting boundary corroborated by an ended-event report; successor canvases are a different occasion, not a reversal of this closure. Evidence: `c0162`. Since R4-pass-1; status standing. ### `K04`: An event-post collection rule is backed by subreddit locking or removal. Kind: condition. Tier: `T4-003`. Dimension: `D01`. Range: A moderation rule applied to posts in this subreddit; not an equivalent power over Discord or independent pixel placers. Evidence: `c0136`, `c0082`, `c0273`, `c0292`. Since R4-pass-1; status standing. ### `R01`: Subreddit moderators regulating where event-related posts may appear. Kind: role. Tier: `T4-003`. Dimension: `D01`. Range: Authority to announce locks and report removals; not an accepted office directing every participant's drawing. Evidence: `c0136`, `c0082`, `c0292`. Since R4-pass-1; status standing. ### `C01`: The observed local coordination does not establish accepted representation of everyone associated with the flag or subreddit. Kind: claim. Tier: `T4-004`. Dimension: `D02`. Range: A bounded inference about public attribution and available evidence, compatible with effective command in particular off-platform campaigns. Evidence: `c0229`, `c0197`, `c0254`, `c0300`, `c0145`. Since R4-pass-1; status standing. ## Grounded view and view with theorized additions Without theorized relations, the model retains only `P02` to `P03` via `A01`, `K02` to `P04` via `A02`, and `P04` to `P05` via `A03` under `K04`. The other ranged elements describe supported activity, conditions and attribution limits without claiming an established dependence between them. With theorized additions, the view would also connect `P04` to `P06` through command (`A04`), `P07` back to `P06` through restraint (`A05`), and `P08` to `P09` through motivation (`A06`). Those additions are explicitly excluded from the grounded view; no figure should draw them as supported arrows. ## Arrow register All included arrows are fair, not strong. The model relates presences and observed/stated responses, not amounts. Source quotes supply the instances; no fabricated interval or transition measurement is added. The mechanisms and their failure observations were written before strength judgments in the diary. Comparisons are theoretical sampling within the already read case, not held-out validation. Episodes can overlap in source items, so a second episode label is not an independent replication. ### `A01`: An admitted mistake can change an intended contribution, without settling everyone's goal. Route: `P02` to `P03`. Included; transition; fair; bounded. Mechanism: Revising a mistaken interpretation removes that respondent's stated reason to resist, allowing an explicit commitment to the intended work instead. Fails if: The respondent acknowledges the intended work but says the same reason still warrants undoing it, or the alleged change is only another person's later attribution. Grounding: The retained words name an earlier mistaken reading and an intended adjustment in the same quoted turn. Full Russian-heart context confirms the news-related apology and preceding request. Would be disconfirmed by a respondent acknowledging the intended repair yet explicitly continuing the same opposition. Boundary: Applies to acknowledged misrecognition in the respondent's stated intention, not deliberate opposition to a known project or verified pixel compliance. Negative check: counterexample. Mechanism failure present: false. No connection base-rate test was performed; base_rate_beaten=null is unavailable, not a failed or passed statistical test. These are episode/quote claims, not prevalence. Sampling: `E-09`: Known Sami work still faced opposition and loss; test the stronger idea that explanation or recognition secures support. Result: fails. `E-17`: An apparent Void attack is reclassified as Kvikk Lunsj; seek a stated change of the warning author's contribution. Result: not testable. Counterexample response: E-09 defeats the general cooperation claim: a known, specified project can still lose. Retain the narrower misrecognition-to-intention transition witnessed in E-02/E-18. E-17 proves reclassification but leaves the warning author's later action untestable; do not turn its completion report into that missing link. ### `A02`: Difficulty following participation can become work on another gathering place. Route: `K02` to `P04`. Included; transition; fair; standing. Mechanism: An expressed organizing or overview problem supplies a practical reason to request, offer or open a new gathering place. Fails if: A venue response is shown to be independent of the stated organizing difficulty, or a purported creation is only a link with no request, offer or creation report. Grounding: c0258 explicitly says a new thread is made because the old one is large and confusing. E-05 and E-20 supply practical requests with creation or qualified offer replies. The links support local responses, not a general sufficiency claim about every burden. Boundary: An observed practical response can be a proposal or qualified offer. No claim that every difficulty receives an answer or that the offered venue is implemented or sustained. Negative check: not-addressed. Mechanism failure present: not-addressed. No connection base-rate test was performed; base_rate_beaten=null is unavailable, not a failed or passed statistical test. These are episode/quote claims, not prevalence. Sampling: `E-13`: A drawing proposal receives venue redirection without a claim that a new venue is needed; distinguish routing from venue creation. Result: not testable. `E-15`: Discord is criticized; test whether authority complaints can be treated as the same burden-to-new-venue mechanism. Result: not testable. Counterexample response: The maintenance-limited offer rules out equating a practical response with a finished solution. Retain the expressed-problem to proposal/creation relation; implementation remains open. Comparisons outside supporting episodes do not expose a clean absence test, so negative_check is not-addressed and strength remains fair. ### `A03`: A gathering destination becomes a routing rule where post governance can enforce it. Route: `P04` to `P05`. Included; order; fair; bounded. Mechanism: A designated collection venue supplies a destination that moderators and participants can invoke when routing or removing separate event posts. Fails if: The cited enforcement predates the announced destination, invokes an unrelated rule, or only a voluntary invitation is present without a post-routing act. Grounding: The collection-thread announcement provides a destination and announces locking; a later moderator says posts created after it were removed. Repeated later directions show implementation of that post policy. These are statements of sequence and enforcement, not proof of successful concentration or pixel control. Boundary: Requires the moderator-backed event-post rule K04, with R01's post authority. Direction can misclassify content and does not establish compliance or authority over pixels. Negative check: counterexample. Mechanism failure present: false. No connection base-rate test was performed; base_rate_beaten=null is unavailable, not a failed or passed statistical test. These are episode/quote claims, not prevalence. Sampling: `E-05`: An opened Discord is a venue without an established equivalent removal rule; test whether all venue creation entails enforcement. Result: fails. `E-13`: The paperclip proposal tests whether the designated collection venue is used as a concrete redirection destination. Result: holds. `E-20`: Successor-game recruitment tests whether the legacy collection policy continues beyond the original event. Result: holds. Counterexample response: The voluntary Discord comparison defeats automatic enforcement after any venue creation. The Oslo false positive defeats perfect targeting, and later overview requests defeat guaranteed accessibility. Bound the relation to an implemented subreddit post rule, retaining its error rather than generalizing it into command. ### `A04`: Venue concentration might produce accepted territorial direction. Route: `P04` to `P06`. Excluded/theorized; transition; thin; candidate. Mechanism: A concentrated venue might settle a target and synchronize participants in a coherent territorial campaign. Fails if: Targets remain opposed, participants act outside the venue's decisions, or a public command cannot be linked to accepted execution. Grounding: Timed targets, agreements and raw planning claims make Discord-directed campaigns plausible, but the closed quoted evidence does not trace accepted command and compliance for the whole flag effort. Boundary: Only an unverified campaign-level explanation, not an absent mechanism. Negative check: counterexample. Mechanism failure present: not-addressed. No connection base-rate test was performed; base_rate_beaten=null is unavailable, not a failed or passed statistical test. These are episode/quote claims, not prevalence. Sampling: `E-10`: Relocation and invasion-related statements coexist with limited-control claims; test unified command. Result: not testable. `E-16`: An appeal receives opposed replies and denied whole-room support. Result: fails. Counterexample response: Neither universal follows. Keep the command alternative as plausible for particular campaigns, exclude the unsupported venue-to-unified-direction arrow from the grounded model, and retain positive planning evidence alongside disputed scope. ### `A05`: Criticism might restrain territorial action. Route: `P07` to `P06`. Excluded/theorized; transition; thin; candidate. Mechanism: Public criticism might make an expansion target unacceptable and restrain a later territorial push. Fails if: Participants continue the criticized action despite understanding the objection, or no later decision is observed. Grounding: Objections and concrete restraint appeals exist, but the retained record does not trace their effect on a subsequent territorial decision. Boundary: Missing causal response is not evidence that criticism never mattered. Negative check: counterexample. Mechanism failure present: not-addressed. No connection base-rate test was performed; base_rate_beaten=null is unavailable, not a failed or passed statistical test. These are episode/quote claims, not prevalence. Sampling: `E-09`: Protection requests coexist with the Sami drawing's loss. Result: fails. `E-21`: A takeover proposal receives a refusal; seek a demonstrated stopped campaign. Result: not testable. Counterexample response: Neither is supported. Preserve the objections and the specific loss; a refusal without an observed later decision cannot establish restraint. Exclude the causal arrow. ### `A06`: Recognition might sustain successor participation. Route: `P08` to `P09`. Excluded/theorized; transition; thin; candidate. Mechanism: Public recognition might motivate participants to continue the practice on a successor canvas. Fails if: Continuation is attributed to another reason or remains unlinked to recognition; temporal adjacency alone is insufficient. Grounding: Recognition and successor invitations both occur after closure, but no retained quote says recognition induced that continuation. Boundary: A theorized incentive relation; no claim of absence or effect size. Negative check: not-addressed. Mechanism failure present: not-addressed. No connection base-rate test was performed; base_rate_beaten=null is unavailable, not a failed or passed statistical test. These are episode/quote claims, not prevalence. Sampling: `E-19`: Pride, credit and regret might explain continued participation; look for an attributed link. Result: not testable. `E-20`: Explicit continuation permits a test for the reason it occurs. Result: not testable. ## Checkable supporting words These quotations are purposive instances from the stated code ranges, not counts of agreement or evidence of all participants. Each arrow's support field in arrows.jsonl contains the exact same words without citation markup. `c0019` (yyeho3aXXxo24H1uSUcBLdKqY74=; hour 15.328611111111112; item `dfoohkj`; thread `62no9u`; offsets 0-63): > Beklager, jeg trodde jeg fikset vandalisme! Hvitt skal det bli. `c0160` (Jhuu6Y0pD42LotuSTwXxChjsZig=; hour 71.2525; item `dfru7fg`; thread `62w0bf`; offsets 50-102): > trodde det var en invasjon, jeg skal hjelpe istedet. `c0258` (freiiiNBDp1P6SCJ1bvR0IObNXY=; hour 77.08777777777777; item `639l4l`; thread `639l4l`; offsets 57-188): > Då har /r/place tatt kvelden (på formidaggen) og sidan den forige samletråda er ganske so stor og uoversikteleg so lagar me ein ny. `c0095` (c5ZCFXU9DpDTwQjL7JuR5wU0ods=; hour 26.176111111111112; item `dfp7et6`; thread `62ubjk`; offsets 0-30): > vi må organisere oss. Discord? `c0096` (9KRUJg+2ZMUZpnMk09E4YZy2uM4=; hour 26.449444444444445; item `dfp838m`; thread `62ubjk`; offsets 0-32): > gjort > https://discord.gg/s6ww7V2 `c0270` (BOGYwwFWxjIgZoukXNTEXCqYegU=; hour 93.84; item `dftcfuv`; thread `639l4l`; offsets 0-98): > Kan vi få en sub opp for det? Kan ikke følge med på discorden, hadde vært greit å ha litt oversikt `c0271` (H44NSGSu69HZJNlqgtBI8W2LjzE=; hour 93.86194444444445; item `dftci3b`; thread `639l4l`; offsets 0-95): > Kan sikkert lage noe, men har nok litt lite kompetanse om hvordan vedlikeholde subredditer osv. `c0136` (L6kr5bqyfyFwi3yj29qSG59uoqM=; hour 30.456666666666667; item `62w0bf`; thread `62w0bf`; offsets 112-266): > Derfor er det nå opprettet en samletråd. Alle poster som er på /r/Norge om /r/place, vil bli låst 01:00, slik at de naturlig kan forsvinne ut av forsiden. `c0082` (XzuZ4yOYindnL+L7QH817Oui5y8=; hour 43.96944444444444; item `dfq4ci4`; thread `62tflm`; offsets 100-171): > klikket jeg akkurat "Remove" på alle tråder opprettet etter samletråden `c0292` (XzuZ4yOYindnL+L7QH817Oui5y8=; hour 92.51; item `dft98ay`; thread `63dfa5`; offsets 0-37): > Fjerna. Bruk samletråden om /r/place `c0199` (EA1r+K5p/lVBLesLhCFRrKOPN+I=; hour 52.95388888888889; item `dfqpgp8`; thread `632725`; offsets 0-89): > Bruk [samletråden](https://www.reddit.com/r/norge/comments/62w0bf/rplace_samletr%C3%A5d/) ## Artefact arguments for the three best-supported relations For `A01`, the coding may have selected especially memorable apologies and hidden failures. The changed-intention words occur within the participant's own turn, not merely the coder's label, which supports the local interpretation. Selection prevents prevalence or a general explanation-to-cooperation law. `E-09` and `E-17` preserve two different limits. For `A02`, practical venue replies may have been easier to code than ignored requests. The explicit because-old-is-unwieldy creation statement in `c0258` separates one mechanism instance from coder topic co-occurrence. The qualified final offer and the not-addressed negative check prevent an inference that the mechanism reliably resolves venue problems. For `A03`, a moderator repeatedly announcing the same rule can inflate apparent connection. The later report of removal and concrete redirects show acts invoking the destination rather than only repeated labels. They do not prove a clean front page, correct targeting, or obedience from placers. Sampling episodes overlap and are not independent campaigns. ## Dynamics, recurrence and loops No complete dated feedback cycle is retained; model/loops.jsonl is empty. A creation followed by later renewed difficulty and replacement is a recurrence. It does not show that creation itself caused renewed difficulty, and would need that missing link to become a loop. Likewise criticism and further expansion do not by themselves establish escalation feedback. Hour 73 is irreversible for original placement. Post redirection can cross it, accounts describe past work, and new recruitment changes the occasion. The prior's temporal brackets remain 0, 73 and 97; no inferred causal break is inserted from an edited OP timestamp. No loop uses incomparable calendar-day labels. ## Dimension projection and support mass The arrows run between typed elements, not between entire bundles or dimensions. All three included relations lie inside `D01`, but reclassification, venue response and rule enforcement do not abstract into one causal mechanism of that dimension. No aggregate arrow is inferred. `D02` is a descriptive part of the structure whose dynamic dependence on the capacity dimension is ungrounded here, not a proved causal condition or irrelevant remainder. Mass means distinct supporting code IDs on included arrows. The unit is codes, the population all 302 live codes in hours [0,97), and boundary ID sets at 0 and 97 are empty. It is ID coverage only. The gateway computed the internal `D01` set as 11/302, receipt 4671, and the empty cross-dimension/`D02` sets as 0/302, receipt 4674. The latter is measured emptiness of this model's support register, never absence of interaction in the community. There are no multiple coder placements, so results with and without doubles are identical. | Dimension | Incoming across dimensions | Outgoing across dimensions | Internal support | With/without doubles | |---|---:|---:|---:|---| | `D01` | 0 | 0 | 11 | identical | | `D02` | 0 | 0 | 0 | identical | Internal record: {"mode":"coverage","unit":"codes","n":11,"denominator":{"unit":"codes","n":302,"of":"all live r/norge codes in hours [0,97)"},"receipt":4671}. Empty-set record: {"mode":"coverage","unit":"codes","n":0,"denominator":{"unit":"codes","n":302,"of":"all live r/norge codes in hours [0,97)"},"receipt":4674}. These fingerprints must not be read as importance or effect sizes. ## ungrounded relationships `A04`, `A05` and `A06` remain outside the model for the specific missing connections described above. Planning claims support the possibility of command, not its accepted scope or compliance. A refusal supplies an objection, not a demonstrated halted campaign. Praise and continuation coexist after closure, not an attributed incentive effect. The most expected but ungrounded relationship is concentration in Discord producing one accepted collective direction. The case has strong reasons to distinguish actual command in particular pushes from representation of all people associated with an emblem. Excluding that arrow does not prove independent copying. Nor does excluding criticism-to-restraint imply that diplomacy never worked. ## looked-for-and-not-found The direct coded readings and targeted full collection-thread, object, correction and successor-venue contexts did not supply a complete coded decision/compliance chain for a single accepted whole-room command. Raw planning statements and invoked agreements are the strongest contrary material, so the absence is weak and limited to the retained public record, not Discord's unseen decisions. No cited instance connects recognition to successor participation. The source says people continue and invites more, but does not attribute that choice to thanks or credit. No completed maintenance outcome is supplied for the final subreddit offer. Neither null licenses saying that motivation or implementation did not exist elsewhere. No dated within-case chain supports a complete feedback loop. Edited posts, repeated vocabulary and similar calls do not supply the missing causal return. The positive Oslo mismatch limits targeting; its actual algorithm is not in the record. A failure to infer that algorithm is not a null result about whether moderation acts. ## Unused material and confidence limits The original coder themes `t06` (joking through April Fools and the canvas) and `t09` (pointing at r/place without organising more) are not installed as topic-derived model elements. Their combined 23/302 code footprint is coverage receipt 2994 from R3, with the same [0,97) window and empty boundary lists. This does not declare joking or attention irrelevant: `FP-03` retains interactional register as a caution against reading war language literally. All other coder themes enter whole or through the complete split of `t07`; optional names do not decide them. The model should fail as a sufficient account where acknowledged identity does not remove opposed purposes, where venue offers cannot become usable access, or where a post rule lacks authority over the action being explained. The first is positively illustrated by the Sami case; the second remains open in the final offer; the third forbids converting subreddit enforcement into pixel command. These are limits in the model's own terms, distinct from record size and missing source bodies. Findings `F-001`, `F-002`, `F-003` and `F-004` hold the scoped interpretations append-only. The independent critic returned no enumerated errors and one alternative partition, answered in notes-R4.md. That return is not an acceptance verdict. Pass 3 retains the scoped model, with the four episode residues, and makes no novelty claim.