#>coordination
roles records funding release rhythm

group work with handles

A small team can become an economy when the work has clear roles, records, and circulation.

Coordination means turning chat, attention, and ideas into artifacts people can point at, fund, improve, preserve, or ship. The point is not to end the conversation; it is to give the conversation a shape it can keep moving through.

Use this when

interest needs to become roles, records, funded work, release rhythm, or a shared next action. A good handoff keeps the current process visible.

What it protects

the difference between chat momentum, actual commitment, revisable agreement, and shipped artifact. Midprocess states are where that difference becomes legible.

What it can become

a consensus card, work sprint, public request, membership path, research brief, or RPG production loop. Each of those can be screenshot, shared, and carried forward.

#>project_rule

Coordination Rule

Every project should produce one of four things, but the route there is usually messier than the final object suggests:

  1. A public artifact.
  2. A useful record.
  3. A funded offer.
  4. A reusable method.
^role_cards

Role Cards

Illustrators

Visual identity, cards, characters, diagrams, covers.

Musicians

Sound, atmosphere, TikTok audio, release identity.

Librarians

Archives, tags, records, source ladders, references.

Farmers / Gardeners

Grounding, food systems, metaphors, real-world care.

Security Researchers

Trust, verification, abuse prevention, provenance.

Learning Scientists

Skill paths, lessons, onboarding, comprehension.

Novelists

Narrative arcs, lore, voice, world continuity.

Software Engineers

Site systems, local storage, cards, automation, tools.

@growth_loop

Attention To Coordination

  1. Publish an insight, ask, offer, or proposal.
  2. Turn it into a Local Proof Card.
  3. Screenshot it.
  4. Share it to TikTok, group chat, DMs, or notes.
  5. Link back to /now/ or /cards/.
  6. Convert interest into support, membership, commission, or collaboration.
  7. Archive the card as a reference.
  8. Keep a screenshot of the midprocess state that taught you something.