feat(telos): add @decocms/telos goal-pursuit agent core

[pedrofrxncx]

Summary

Adds @decocms/telos — a small, standalone, domain-agnostic core for agents that pursue a fixed goal. One agent per tenant observes a world, measures it against a goal it did not choose, and acts to close the gap until none is left.

The design keeps the goal and the striving rigorously separate, so an agent can never quietly rewrite its own purpose (the names come from Aristotle's two movers — see the package README for the full intro):

• UnmovedMover<T> — the goal: frozen, versioned, per-tenant target data. Behaviorless; never mutated, never acts.
• GoalLedger<T> — append-only succession of goal versions (installing a new version is the only way a goal changes).
• Eudaimon<S,T,G> — the agent: observes, measures, deliberates, acts — pursuing the current goal but never authoring it.
• Domain<S,T,G> — the one extension point: how to perceive a world, judge it, and act in it.
• Deliberator — swappable reasoning: ruleDeliberator (offline, deterministic) or aiDeliberator.

What's included

• core.ts — UnmovedMover, the GoalLedger/Domain/Action/Deliberator ports, EventBus, Eudaimon, wire(). Depends only on zod — never the AI SDK.
• InMemoryGoalLedger + inMemoryBus — swappable defaults.
• ruleDeliberator (offline) and aiDeliberator (exported at @decocms/telos/ai; ai is an optional peer dep, model is injected).
• Runnable examples/ (storefront + content-calendar on the same core) and co-located unit tests.

Architecture: two causes, kept apart

the world moved        →  state.changed  →  Eudaimon.pursue()     (the agent reacts)
an authority decides   →  goal.updated   →  GoalLedger.install()   (a new fixed star)

The agent reacts to state.changed; a new goal arrives only via goal.updated, which only an authority emits. The agent is never on the goal-setting path.

Scope / impact

Additive and inert. Nothing in the codebase imports it yet — the existing agent loop and apps/mesh are untouched. The package is self-contained and extractable to its own repo (deps: zod; optional peer: ai).

Testing

• bun test packages/telos — 10 pass (frozen mover, ledger succession, pursuit, causal separation, deterministic convergence to a fixed star + re-pursuit of a raised goal).
• bun run --cwd packages/telos check (tsc), bun run lint, bun run knip — all green.
• bun run --cwd packages/telos example — converges as expected (ledger history: v1 -> v2).

knip.jsonc gains one entry marking ai as the intentional optional peer (mirrors the existing mesh-sdk → sonner precedent).

---

Summary by cubic

Adds @decocms/telos, a small, domain‑agnostic core for fixed‑goal agents, and wires it into Mesh with a Postgres goal ledger, durable onboarding, a recurring pursuit loop, and a live home card. On signup we install a deterministic, fixed org goal and stream research, thoughts, and suggestions; Decopilot and user agents carry a telos (charter + guard) resolved from per‑agent goals, and pursuit now runs continuously for the enduring goal.

• New Features

  • Core: UnmovedMover (adds source), GoalLedger (adds anchor()), Eudaimon, Domain/Action, Deliberator (rule or optional @decocms/telos/ai), Telos<T> (charter/guard/measure for existing agents), applyAction, VetoError; bus adds eudaimon.action.vetoed and PursuitContext.vetoed().
  • Durable runtime + Mesh: bootTelos() migrates/builds the @decocms/telos/postgres store and registers capabilities; shared, rate‑limited DBOS queue via initTelosDbos(); onboarding installs a fixed Goal (buildStudioGoal()) on user.signup and runs background research (Firecrawl + OpenRouter) to propose facts; pursuit runs immediately and on a schedule with a heartbeat and never “finishes”; user‑only actions surface as goal.suggestion and cache per org; live thoughts stream via SSE (goal.thought) and cache per org; fact edits debounce a goal re‑fit; orgActivity pub/sub nudges pursuit.
  • UI + API: home TelosGoalCard shows suggested next steps, live thoughts, per‑tool connection status, and one‑click install buttons (use-install-app); GET /api/:org/telos-goal returns { goal, facts, suggestion, thought, progress, status }; POST /api/:org/telos-facts/:id confirms/rejects facts; SSE notifications (telos.goal.installed, telos.facts.updated, telos.goal.suggestion, telos.goal.thought).
  • Agents: Decopilot resolves an agent telos from a per‑agent goal (tenant agent:<id>); the charter is added to the system prompt and tools are guarded via guardTools from @decocms/telos/daimonion; new agents seed their telos from their instructions on create.

• Refactors

  • Telos storage is self‑managed: replaced Mesh migrations/adapters with bootTelos(), removed legacy onboarding ledger/facts wiring, added a telos SSE pool and client hooks, and updated knip.jsonc to ignore the optional ai peer.
  • Removed the previous catalog module; tool targets come from the fixed Goal and registry data (targets now support optional appName and icon). Improved guardTools types and cleaned telos agent imports; expanded packages/telos/README.md with an integration guide. Removed the old goal‑progression capability; pursuit is continuous against the enduring goal.

^{Written for commit b9be9c1. Summary will update on new commits.}