C5 ยท Model: account
Write the whole account and expose its weak points
C5 turns the model into an explanation a reader can follow from beginning to end. Writing is the test here: if the parts cannot form one account, a diagram cannot repair that.
Where this stage starts
The aggregator has the model built in C2, its comparison with the literature from C3, and the comparison with the Field account from C4, where supplied. Version records name the accounts that apply. The cases and the evidence behind each concept stay available for checking.
What the aggregator does
First, the aggregator writes continuous prose. It works down from the population account to communities and back up from selected communities to the account. This exposes claims that sound persuasive in general but fail to explain what particular participants did.
The aggregator tries different visual arrangements and asks what explanatory work each construct and relationship does. Removing a box or arrow should have a stated consequence; one whose removal changes nothing is decoration. Cases that resist the account are named and considered, and the model does not add an improvised exception each time it meets contrary evidence.
Claims about relationships become explicit propositions, each with its mechanism, evidence and rival explanations. Three fresh readers then examine the account and the cases. Their task and the author's own claims are recorded before their answers arrive. The aggregator replies and keeps the results, including criticism that remains unresolved.
The final explanation traces participant words through first-order codes and themes to the aggregate dimensions. It states where the account may apply and what this curated collection cannot establish. It also records expectations for the coming return to communities before seeing their answers.
What the next stage receives
D1 receives a frozen model and a readable account. Freezing names one exact version for the test; it makes no claim that the version is true. The next stages give that model back to the community coders and examine where it fits, needs local detail or needs correction.
What the output files contain
Markdown files hold prose; JSONL files hold one structured record per line.
The account and its developmentaccount.md, sketches.md, account_passes.jsonl, prose-test-C5.md
account.md is the integrated explanation.
sketches.md keeps the alternative figures.
account_passes.jsonl records successive passes;
prose-test-C5.md records what the prose test exposed.
Explicit claims and independent readingspropositions.jsonl, author_claims.jsonl, RETURN-C5.md, readers-C5/, notes-C5.md
propositions.jsonl states testable relationships.
author_claims.jsonl keeps the author's claims written
before comparison. RETURN-C5.md and three packets define
the reader tasks; readers-C5/ keeps their responses.
notes-C5.md records the aggregator's answers and remaining
doubts.
Evidence, figure and scopedata_structure-C5.md, figure-C5.md, implications-C5.md
data_structure-C5.md links evidence to concepts and to
each higher level. figure-C5.md draws the model and marks
which relationships are grounded and which are conjectured.
implications-C5.md states implications, limits and
expectations for the return.
Revision history and the fixed test versionfindings.jsonl, tier_history.jsonl, model/history.jsonl, scheme_v2.jsonl, assignments_final.jsonl, handback-C5.md, run_manifest.json, out/_closes/model-C5.sha256
findings.jsonl, tier_history.jsonl and
model/history.jsonl keep claims and changes. If coding
changes, scheme_v2.jsonl and
assignments_final.jsonl are updated.
handback-C5.md records the handoff;
run_manifest.json records the setup.
out/_closes/model-C5.sha256 names the exact frozen model
that D1 must use.
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
C5a: pass. Repeats: yes. Interview point: -.C5b: readers build. Repeats: no. Interview point: -.C5c: readers check. Repeats: yes. Interview point: -.C5d: table, model and figure. Repeats: no. Interview point: end.
Source versions and hashes identify the exact technical documents reproduced here.