r/place A fruit fly for organization science

For agents

This repository proposes r/place as a fruit fly for organization science: a shared event record and a revisable instrument for cumulative grounded theory. The research object, common conditions, whole event and shared data and tools explain the project.

Use these reading keys to find the authoritative instrument. They do not replace it.

For a human-readable explanation of who does what, see Agents and their roles.

Choose your starting point: raw data, checked coded communities, or checkpoint interviews. Each brief lists inputs, access requirements and stopping points.

For a new study, open the Collection handler first. Then use the existing coding handler and aggregator handler, in separate chats. The collection brief is new; the other two retain their existing contracts. Human prompts and handoffs are in Run the study.

  1. Read the scope, inputs and stopping boundary for your task.
  2. Read the linked contract and the full stage card, in the listed order.
  3. Check the file hashes in the source manifest. If a version differs, report the difference before treating it as the same instrument.
  4. Follow the handler's checks and handback rules. A website status is not permission to start, repair or resume research.

Every stage page offers its reading key as Markdown and its full card in HTML and Markdown. The source manifest identifies the version used to build this site. Checkpoint manifests separately identify historical agent state.

Use the resolved source reading copies to follow links. Their wording matches the exact canonical sources; links resolve to other reading copies or a pinned repository commit. A missing dependency is marked, never supplied by guesswork.

An interview is an audit copy. Never update the original run, infer missing files from the latest workspace, or substitute a fresh agent when native restoration fails.

For an evidence audit, read the TRACE reading guide and evidence register. Distinguish instructions from recorded actions and recorded actions from independent acceptance. The bounded example does not certify the whole study or add research requirements.

Stages and source versions

Source manifest · Agent index · All documents

  1. A1 Reading: room notes

    Read the communities before naming a common scheme.

  2. B1 Coding: third-order scheme

    Build a grounded scheme for comparing the community themes.

  3. B2 Coding: pilot

    Try the scheme on a pilot and examine disagreements.

  4. B3 Coding: fleet

    Have independent readers place the remaining material.

  5. B4 Coding: adjudication and freeze

    Resolve disagreements and check the resulting placements.

  6. C1 Model: structuring

    Group the material into higher-order themes.

  7. C2 Model: the loop

    Build and challenge a model of how organizing unfolds.

  8. C3 Model: literature

    Compare the model with the literature.

  9. C4 Model: the field

    Examine the model against the field account when supplied.

  10. C5 Model: account

    Write and challenge the integrated account.

  11. D1 Adaptation: return build

    Prepare the model for its return to communities.

  12. D2 Adaptation: labelers and verdicts

    Ask the original community leads what the model explains and misses.

  13. D3 Adaptation: adjudication

    Assess the corrections and revise the model where warranted.

  14. D4 Forming: the tree

    Build the taxonomy from similarities in case adaptations.

  15. D5 Forming: branch accounts

    Explain the branches as organizational forms.

  16. D6 Forming: the retelling

    Retell the whole model with its organizational forms; new insights remain unvalidated proposals.

  17. E1 Formalizing: audit

    Audit the analysis and its record.

  18. E2 Formalizing: feedback

    Use feedback to examine and refine the account.