The Four Primitives

FirstPrinciples decomposition of the entire vision yields exactly four irreducible primitives. Everything else — monitoring, vision systems, UEC, agent harnesses — is an application built from these, not a separate component.

1. Entity

A universal node with Telos state. Every entity has the same 18-field state structure regardless of its type in the hierarchy. Types: person, team, department, division, company, workflow, resource.

Why irreducible: Remove this and there is no fractal structure. No node to address, no state to query.

2. Daemon

An API server bound to entities. Serves state, emits events on change, supports subscriptions. In the Cloudflare implementation, a “daemon” is not a long-running process — it is an addressable route with consistent state access through D1 and KV.

Why irreducible: Remove this and entities are not addressable. No API, no integration, no automation.

3. Workflow

A directed graph of typed steps (decision, action, tool, verification, gate) with typed executors (human, ai, hybrid, system). A workflow is itself an Entity — it has its own Telos state, goals, and metrics. Workflows can reference sub-workflows via subWorkflowId.

Why irreducible: Remove this and “companies are algorithms” has no structure. Business processes become untyped and untrackable.

4. Policy

An {subject, action, object, condition} -> allow/deny rule evaluated at the daemon level on every request. Deny-first. Role-based field filtering strips sensitive data before it reaches the caller.

Why irreducible: Remove this and there is no access control. A team member sees the same data as the CEO.

Everything Else Emerges From These Four

• “Unified Entity Context” = querying multiple daemons and aggregating
• “Vision system” = a workflow that reads the company vision entity and evaluates content
• “Monitoring” = a daemon subscribed to error events from other daemons
• “Agent harness” = the executor system for workflow steps of type ai
• “Resources” = entities of type resource