D6 ยท Forming: the retelling
Retell the whole model with its forms inside it
D6 brings the population model and the branch accounts into one explanation. A reader should be able to move from a broad idea to an organizational form, then to a community, and see what each level adds.
Where this stage starts
C5 supplied the earlier account of the whole model. The return to communities tested and revised that model in D1 to D3. D4 proposed shared forms, and D5 wrote their accounts. D6 starts from those records, including unresolved cases and the proposals left by the branch accounts.
What the aggregator does
The aggregator works through the model's aggregate dimensions. For each part, it says what each form does there: adds local detail, restricts the claim to certain conditions, replaces a way of doing the work, or leaves it unchanged. The explanation names the evidence and the communities for each difference.
The best examples come with a weak fit. If members of one form disagree, the aggregator considers whether this is ordinary local variation, unresolved evidence or a possible further distinction. It cannot invent a subform to remove the awkward case.
The whole account is then rewritten with those differences inside it. The figure shows where forms differ within the model; a list of clusters beside an unchanged diagram does not meet the task. The account also explains the communities that needed no adaptation and those the model could not explain, and it assumes no common history for either set.
Evidence that coordination continued or ended comes from the records, and silence is reported as silence. Canvas information can show an outcome, but any part it plays in interpretation is declared.
There is a firm limit: the D3 model and the D4 tree stay fixed. A new idea found while writing goes into a separate proposal, without the validation the earlier model received. Applying it would need a further return to the affected communities.
What the next stage receives
E1 receives the integrated retelling, its evidence links and a separate list of unvalidated proposals. It can audit what the completed run supports and keep ideas produced at the end apart from claims tested during the return.
What the output files contain
Markdown files hold prose; JSONL files hold one structured record per line.
The integrated explanationretelling-D6.md
retelling-D6.md tells the model with the organizational
forms inside it. It links common processes, patterned differences and
local cases, and it keeps the limits found earlier.
How forms change particular model elementsfractal-D6.jsonl
fractal-D6.jsonl records, for each element and branch,
whether the branch specifies, restricts, replaces or leaves the element
untouched, with evidence. "Fractal" here names this movement between
levels of explanation; the file holds no mathematical measure.
The final explanatory figurefigure-D6.md
figure-D6.md contains renderable diagram text and a
legend. It shows the relationships described in the retelling, including
where forms differ.
New ideas kept separate from tested claimsproposals-D6.jsonl, amendments-D6.jsonl
proposals-D6.jsonl records new ideas with their
evidence, the affected communities and an unvalidated status.
amendments-D6.jsonl stays empty: no new model amendment is
applied here.
Decisions, handoff and interview briefnotes-D6.md, handback-D6.md, out/interview/D6b.md
notes-D6.md explains judgments and responses to D5's
suggestions. handback-D6.md summarizes the handoff.
out/interview/D6b.md records what the aggregator would want
a reviewer to ask at the close.
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 2 legs
D6a: dimension. Repeats: yes. Interview point: -.D6b: telling and figure. Repeats: no. Interview point: end.
Source versions and hashes identify the exact technical documents reproduced here.