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.
Where this stage starts
C1 has supplied the third-order themes, the fourth-order themes and their evidence. The aggregator can return to a community's coded threads whenever an interpretation needs checking. It reads them as the community coder sealed them, never the raw download. Literature on how to conduct the analysis is available; comparison with substantive theories comes in C3.
What the aggregator does
The aggregator works on three linked products. A coding structure shows how participant evidence supports each level of themes, up to the aggregate dimensions. A concept account states what the analysis adds and what it cannot yet explain. The model links the ideas through conditions, actions and consequences.
Each arrow in the model makes a claim: when one thing happens, another follows, through a stated process. Two themes that appear together do not show that process. A feedback loop needs evidence of a cycle unfolding in time. Relationships that remain conjectures are marked apart 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 call for a narrower claim, a different relationship, a new distinction or an explicit limit. Each change is recorded when it happens, with the evidence that caused it.
The criteria for preferring a later model are declared before these rounds. A fresh critical reader also examines the developing account. The aggregator answers the criticism and runs every prescribed check, however finished the story reads.
What the next stage receives
C3 receives a model built through comparison with cases, its earlier versions and a record of unresolved material. It can compare the explanation with published theories and still trace how the model arose from this collection.
What the output files contain
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 keeps 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 fourth-order themes;
dimensions.jsonl records the aggregate dimensions that
group them. structure.md explains how evidence leads up to
ideas. concept.md states the conceptual contribution;
model.md explains the model; within_case.md
examines it within cases.
Each telling and the cases it metmodel/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 keeps the reply.
_questions/<slug>.md holds questions that need a
ruling. findings.jsonl and tier_history.jsonl
keep claims and category changes. If categories change,
scheme_v2.jsonl and assignments_final.jsonl
are updated.
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.
Show how the stage is divided into its 4 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.