φ-framework Attractor Ontology

1. The Four Channels

Every organizational coordination task uses one or more channels. No task is purely one channel — every task has a dominant channel where the cost is paid.

Channel	Symbol	Definition	Medium	Persistence
Surface	Φsurface	Recorded signal	Documents and records	Permanent until deleted
Formal	Φformal	Rule-bound signal	Policies, SLAs, and explicit criteria	Outlives the people who made them
Tacit	Φtacit	Unwritten signal	Cultural norms, unspoken expectations, implicit knowledge	Transferred only through direct interaction
Comm	Φcomm	Conversational signal	Meetings, DMs, synchronous exchange	Ephemeral — exists only in the moment

2. Task Types

The ratio R_routine : R_complex increases with org size. Small orgs are mostly R_complex. Large orgs are mostly R_routine.

R_routine

Φs · Φf

Status updates, approvals, handoffs

R_complex

Φt · Φc

Strategy, architecture, crisis response

Scaling (Φc)

N×M

superlinear · coordination tax compounds

Scaling (Φs·Φf)

sublin.

institutional memory · amortized cost

3. The Coordination Cost Pattern

Coordination cost per person grows faster than headcount as orgs scale. Simple work (status updates, approvals, handoffs) that could flow through documents and records instead pools in meetings and messages. The cost compounds. At 100 people, manageable. At 5,000, expensive.

Routine work pools in conversational channels →

Coordination cost grows with org size →

Teams enter an unstable middle zone →

Leadership faces a choice: build formal infrastructure or mandate presence

4. The Easy Default

Every organization defaults to some coordination mode — the path of least resistance where routine work gets handled with minimum friction. The default isn't fixed. It's a product of what the organization has built.

Coordination mode is determined by: · What infrastructure already exists (documents, records, rules) · What people naturally do (talk, write, decide in rooms) · What the organization's culture treats as normal

Force	Direction	What it means
Cost gravity	Toward the cheapest mode	Organizations drift toward whatever costs least per coordination event
Presence gravity	Toward conversation	Without explicit infrastructure, talking is the default — it's fast and social
Constraint	Shifts the default	Explicit documentation and rules change what "normal" looks like

Any organization with multiple locations is already distributed. The question isn't remote vs. office — it's whether the default coordination mode matches the actual coordination cost at scale.

5. Growth Stages

Most companies hit a coordination cost crisis between 100–500 employees. The org has outgrown tacit coordination but hasn't built formal infrastructure yet.

Founder

0–15

Coordination through direct conversation and shared assumptions

First Scale

15–100

Tacit coordination dominant · informal norms start diverging

Scaling Crisis

100–500

Vulnerable window · routine work floods conversational channels

Constraint Design

100–5k

Build explicit coordination infrastructure · or accept conversational overhead

Multi-office

500+

Already distributed · coordination cost grows with distance between nodes

Mature

5k+

Infrastructure amortizes cost · or coordination debt compounds

6. Minimum Viable Constraint Set

Constraints redirect rather than prohibit. Conversational coordination is not banned — it carries complex work instead. Setup cost is front-loaded; payoff is diffuse and future.

✓Decisions documented to existΦsurface min— Undocumented decisions don't exist in org memory
✓Explicit response time normsΦformal SLA— Async feels safe; no FOMO on missing messages
✓No standups / status meetingsΦcomm exclusion— R_routine cannot pool in Φcomm by design
✓Meetings require agenda + pre-readΦcomm scarcity— Sync is last resort, not default
◌All-hands recorded / asyncΦsurface max— Presence optional; institutional knowledge persists
◌Working hours conceptΦformal boundary— Time zone differences handled explicitly rather than ignored
◌Single owner per initiativeΦformal + Φtacit— Reduces coordination overhead; "black box" trust
◌Public by defaultΦsurface max— Pressure to document anything public-facing

7. Two Paradox Types

Type 1 · Formal Infrastructure Missing

Org grew past tacit coordination but didn't build Φformal fast enough. Most companies.

Common in scaling-phase companies

Type 2 · Informal Infrastructure Load-Bearing

Async-first model works because everyone is high-maturity. Collapses if hiring bar drops.

Requires consistently high hiring bar

8. RTO as Forced Choice

When organizations can't reduce coordination cost through formal infrastructure, some default to in-office mandates. The stated reasons (collaboration, culture) are usually accurate diagnoses of a real problem — but the mechanism is misidentified.

1 · Routine coordination cost becomes visible and contested

2 · Build formal infrastructure (expensive, diffuse payoff) or mandate presence (cheaper, immediate)

3 · Leadership chooses in-office mandate

4 · Coordination cost moves to in-office overhead

5 · Some people leave; some accommodation accepted

What RTO misdiagnoses

"Distrust of remote productivity" — output is invisible, so remote work gets blamed

Passive headcount reduction — coordination happens through conversation instead of planning

Presence preference — presence is easier to observe than output

φ-framework prescription

Build visible systems: output tracking, decision logs, shared work products. Addresses the real problem without the presence cost.

Open Questions

1Is UA_R a fixed point or does it vary by domain/task complexity?
2Can you observe OA directly, or only infer from channel misallocation patterns?
3Is OA → UA_R convergence guaranteed or probabilistic?
4Does a maturity-dependent model survive past 500 people?
5Does Φtacit develop as effectively remote-first, or does it require physical presence for trust-building?
6Does UA_R vary across industries or is it domain-invariant?
7What is the minimum viable constraint set for a given org size?