C2 · Model: the loop
Build an explanation and try to break it
C2 moves from categories to a model: an explanation of how organizing happens, under which conditions, and through which relationships. A model must do more than put the categories into a diagram.
Where this stage starts
C1 has supplied descriptive categories, broader themes and their underlying evidence. The aggregator can return to community records whenever an interpretation needs checking. Literature about how to conduct the analysis is available, but comparison with substantive theories comes in C3.
What the aggregator does
The aggregator works on three connected products. A data structure shows how participant evidence supports successively broader ideas. A concept account identifies what the analysis adds or cannot yet explain. The model connects the ideas through conditions, actions and consequences.
An arrow in the model therefore needs a claim: when one thing happens, another follows, because of a stated process. Two themes appearing together are not enough to establish that process. A feedback loop needs evidence of a cycle unfolding in time. Relationships that remain conjectures must be distinguished from those grounded in the record.
The aggregator writes the model as a whole story and reads it against named communities, including cases that challenge it. Can the story explain what those participants did? What does it leave out? A miss can require a narrower claim, a different relationship, a new distinction or an explicit limit. Changes are recorded as they occur, with the evidence that caused them.
The criteria for preferring a later model are declared before these rounds. A fresh critical reader also examines the developing account. The aggregator responds to that criticism and continues the prescribed checks rather than treating a polished story as a sufficient stopping point.
What the next stage receives
C3 receives a model built through comparisons with cases, its earlier versions, and a record of unresolved material. It can compare the explanation with published theories without losing sight of how the model arose from this collection.
What the output files contain
Open a file group for its purpose. These are descriptions of the stage’s outputs. Markdown files hold prose; JSONL files hold one structured record per line.
The model’s parts, relationships and changesmodel/elements.jsonl, model/arrows.jsonl, model/loops.jsonl, model/history.jsonl
model/elements.jsonl records claims and components;
model/arrows.jsonl records relationships.
model/loops.jsonl records grounded feedback cycles and can
be empty. model/history.jsonl preserves revisions and their
reasons.
The explanatory levelsfourth/fourth.jsonl, dimensions.jsonl, structure.md, concept.md, model.md, within_case.md
fourth/fourth.jsonl records the broader themes;
dimensions.jsonl records their most general groupings.
structure.md explains the evidence-to-idea structure.
concept.md states the conceptual contribution;
model.md explains the model; within_case.md
examines it within cases.
Each telling and its encounter with casesmodel/story-pN.md, story_rooms-pN.jsonl, saturation.jsonl
model/story-pN.md keeps each whole-model telling.
story_rooms-pN.jsonl records the cases tested against that
pass. saturation.jsonl records what changed across passes,
including unresolved material.
Criticism, questions and revisions to codingRETURN-C2.md, review-C2.md, _questions/<slug>.md, findings.jsonl, tier_history.jsonl, scheme_v2.jsonl, assignments_final.jsonl
RETURN-C2.md and its packet define the critical reader’s
task; review-C2.md preserves the reply.
_questions/<slug>.md holds questions needing a
ruling. findings.jsonl and tier_history.jsonl
preserve claims and category changes. If categories change,
scheme_v2.jsonl and assignments_final.jsonl
are updated accordingly.
The handoffnotes-C2.md, handback-C2.md, run_manifest.json
notes-C2.md explains decisions and responses to
criticism. handback-C2.md summarizes the state handed
forward. The run_manifest.json entry records the stage’s
setup.
Full stage description
Read the complete technical card for exact tasks, reading boundaries, checks and closing rules. The explanation above is a guide; the card holds the instructions.
How the stage is divided into legs
C2a: pass. Repeats: yes. Interview point: -.C2b: reviewer build. Repeats: no. Interview point: -.C2c: reviewer check. Repeats: no. Interview point: mid.C2d: closing pass. Repeats: yes. Interview point: -.
Source versions and hashes identify the exact technical documents reproduced here.