C3 · Model: literature
Put the model into conversation with theory
C3 asks what existing research helps explain, challenges or has already said about the model. Literature is a source of comparison and criticism, not a template into which every observation must fit.
Where this stage starts
C2 has built a model from the community material and tested its successive tellings against cases. The aggregator also has its initial expectations. Keeping that record makes it possible to distinguish ideas brought to the study from ideas developed during it.
What the aggregator does
The aggregator begins with literature that could contradict the model. When a published explanation differs, it asks what causes the difference: a different setting, a real disagreement about how organizing works, or different terms for similar processes. It names evidence that could distinguish these possibilities and leaves the question open when the record cannot decide.
Related work can then sharpen mechanisms and concepts. A borrowed idea must earn its place by explaining the material, not merely by giving the account a familiar theoretical name. The aggregator records which sources it actually opened and which it recalls but has not verified. A remembered citation cannot carry the same evidential weight as a checked source.
The stage also compares its broader themes with four organizing problems: dividing tasks, assigning them, providing rewards and handling information. That comparison helps a reader locate the model in organization theory. It does not require every theme to fit one of the four. Material left outside the framework may be part of what the study contributes.
Literature can prompt another look at a community or a change to the model. Those changes need an evidence trail. Earlier formulations remain available, and findings affected by a revision are reconsidered. The aggregator also returns to its original expectations and states what the analysis changed.
What the next stage receives
C4 receives the current model, its relationship to existing explanations, and unresolved disagreements. A version list makes clear which files are current, preventing a later stage from accidentally combining incompatible versions of the account.
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 comparison with literatureliterature-C3.md, findings.jsonl
literature-C3.md explains agreements, contradictions and
conceptual links, with checked sources distinguished from unverified
recollections. findings.jsonl connects relevant claims to
that literature record.
The organizing-problem comparisonmapping-C3.jsonl
mapping-C3.jsonl maps broader themes to the four
organizing problems where justified. It also preserves what does not
fit, so the comparison does not silently narrow the model.
Changes to the explanationmodel/arrows.jsonl, model/history.jsonl, model-C3.md, structure-C3.md, concept-C3.md
model/arrows.jsonl records current relationships;
model/history.jsonl records changes and reasons. When
needed, model-C3.md, structure-C3.md and
concept-C3.md provide complete successor accounts rather
than disconnected patches.
Which version to readmanifest-C3.txt, notes-C3.md, tier_history.jsonl, scheme_v2.jsonl, assignments_final.jsonl
manifest-C3.txt identifies which accounts have
successors and which earlier files still apply. notes-C3.md
explains choices and remaining questions. If the coding structure
changes, tier_history.jsonl, scheme_v2.jsonl
and assignments_final.jsonl record the change and its
consequences for placements.
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
C3a: contradicting shelf. Repeats: no. Interview point: -.C3b: resembling shelf. Repeats: no. Interview point: -.C3c: the four problems. Repeats: no. Interview point: end.
Source versions and hashes identify the exact technical documents reproduced here.