Results
Follow one community from its evidence to its model, then see how the population model brings 705 communities together. These pages show the completed run and the records behind its claims.
PlaceNL example: one community
Start with the Dutch community's activity, codes and case account. Read its standalone local model, then follow the aggregator's first reading, its placement in the population's coding structure, and the comments it returned on two model versions. End with PlaceNL's place among the final organizational forms.
One incident shows why the return matters. Members agreed to add canal houses to their flag, but their own defence script erased them. Comparing such objections across communities changed the model's account of repair. The later recheck also exposed a limit to that revision.
Follow PlaceNL's journeyRead the repair-and-change example
Aggregator example: the population model
Explore the coding structure, the model and its narrative, and the six organizational forms. The comparison at the end shows every community's changes and codes, with the same dimension colours and normalized averages for each form.
An interim view from the wider event: C4
The Field agent read the central r/place forum and offered comments while its own analysis was still in progress. C4 used this interim view to qualify the community model and add tentative claims. The completed Field model will provide a further comparison; that check is still pending.
Read what C4 changed · Read the saved comparison · Interview the C4 analyst
The local model and the population model are separate analyses. Their labels and claims should be read within their own scope. Checks at the coding, composition and source levels distinguish completed work from planned comparisons. Checkpoint interviews let you question the saved analysts and compare their new answers with the original work.