We are exploring the organization itself as the unit of intelligence: people, AI agents, services, workflows, and shared knowledge operating with a common purpose and explicit authority.
From a signal to a useful response
An issue, message, or monitoring event enters the organization. The system preserves its source, relates it to current work, and identifies what needs attention. People and specialized agents consider responses. An authorized action is executed, and its outcome returns to shared knowledge.
Known routines can become deterministic playbooks. Consequential decisions still need accountable people and clear authority.
Current state
WebTree has concrete internal deployment and repository tools, plus early signal and attention artifacts. The broader federated organization remains an architecture and implementation direction. It is not a supported autonomous-company product.
MakeLocal and 0CAD are intended to operate as Project Cells with their own work and data boundaries. A Project Cell is an execution boundary; a Circle is a cooperation and governance boundary.
The company-as-brain analogy
| Metaphor | Operational meaning |
|---|---|
| Receptors | Email, messages, GitHub, monitoring, people, and agents |
| Perception | Normalize inputs, resolve entities, and retain provenance |
| Attention | Choose what deserves limited time and reasoning |
| Working memory | A small shared set of active situations |
| World model | Versioned goals, commitments, dependencies, and evidence |
| Specialized reasoning | Domain-specific interpretations and proposals |
| Executive decisions | Resolve trade-offs and grant explicit authority |
| Playbooks and tools | Execute authorized routines with scoped permissions |
| Security / immune system | Detect and contain unsafe inputs or behavior |
| Global state / “hormones” | Explicit priorities, separate from measured conditions |
| Memory and learning | Preserve outcomes and improve future work |
This is an architectural analogy, not a claim of consciousness.
What could go wrong?
Untrusted inputs can influence an agent. Shared memory can spread an error. Agreement among several agents is not independent proof. Missed or duplicated events can lead to inappropriate action, and automation can transfer hidden work to human reviewers.
Project data boundaries, authorization checks, replay and reconciliation, audit records, and ways to stop work all matter.
A useful next test
Choose one low-consequence recurring task. Compare a documented human workflow with an assisted one. Measure completion quality, reviewer effort, failures, and recovery from missed events. Keep a named decision owner.
The platform should earn its scope through useful project work. MakeLocal’s first customer should not depend on building this whole architecture.
Status and revision
This is a concept note, not a reported experiment result. Maintained by the WebTree project team, led by Max Levitskiy. Initial public synthesis: 5 September 2026. Future revisions should state what changed and why.