SynedrixOS
Layer 2 of 12

Goal & Intent

Turns what a business wants into something the system can plan against.

TIER
Human and intent surface
PLATFORM
No dedicated platform
OS AGENTS
None assigned
Position in the stack
01Human Interface
objectives and KPI targets originate from a human
02Goal & Intent
No dedicated platform
translate → structure
It structures intent; it does not execute or authorise it.
03Orchestration
the planner decomposes a structured goal into a task graph
Cross-cutting
09Governance & Controls
playbooks and KPI targets can encode constraints Layer 9 evaluates
Definition

What Goal & Intent is

Goal & Intent is the layer where a business objective becomes something the rest of the system can act on: a structured goal schema, an objective definition, a playbook, or a KPI target, not a paragraph of prose or a verbal instruction. Its job is translation, not execution.

This step matters because everything downstream (task decomposition, agent invocation, policy evaluation) depends on intent being expressed consistently rather than re-interpreted ad hoc at each layer. A goal that reaches Orchestration already structured is one it can plan against; a goal left as free text pushes interpretation work onto whichever layer happens to receive it first.

Boundary

What it owns, and what it does not

Every layer in the architecture has a non-overlapping responsibility. The boundary is as much a part of the design as the capability.

Owns

  • Goal schema
  • Objective definitions
  • Playbooks
  • KPI targets

Does not own

Domain-specific execution logic
→ Domain Pack Layer
Raw tool calls
→ Tool Abstraction Layer
Coordination

Interfaces with

The other layers this one exchanges work, state, or decisions with, and why.

Human interface

objectives and KPI targets originate from a human through Layer 1's surfaces before they're captured here in structured form.

Orchestration

a structured goal is the input Layer 3's planner decomposes into a task graph.

Governance

playbooks and KPI targets can encode constraints (thresholds, required approvals) that this layer stays coordinated with Layer 9 on.

Current state

Current specification depth

SPEC DEPTH

Unlike most other layers, Goal & Intent has no dedicated deep-dive specification; its authoritative definition is the layer taxonomy entry. Orchestration and Governance & Controls carry most of the adjacent detail: how a structured goal is decomposed into a task graph is specified in the Orchestration & Runtime Strategy, and any constraint a playbook or KPI target implies is evaluated by the Policy Guard Agent, not by a Goal & Intent spec of its own.

Agents

OS agents at this layer

NO AGENT AT THIS LAYER
No OS-owned agent operates natively at this layer. Goal schemas and playbooks are structured here but consumed by Orchestration's planning logic, most directly the Orchestrator Agent (os-agt-001), which decomposes a structured goal into a task graph.
Design rules

Layer principles that apply

  • Shared before specific: a goal schema or playbook structure usable by any domain pack belongs here as a shared OS primitive, not reinvented per pack.
  • Controls before execution: a playbook or KPI target implying an approval must still pass through Governance & Controls before the objective it describes is acted on.
Common questions

Goal & Intent questions, answered

Short, citable answers drawn from this page.

What is the Goal & Intent layer in Synedrix OS?

Goal & Intent is layer 2 of the twelve-layer Synedrix OS architecture, in the "Human and intent surface" group. Turns what a business wants into something the system can plan against.

What does the Goal & Intent layer own?

The Goal & Intent layer owns: Goal schema; Objective definitions; Playbooks; KPI targets.

What does the Goal & Intent layer not own?

The Goal & Intent layer does not own: Domain-specific execution logic (owned by Domain Pack Layer); Raw tool calls (owned by Tool Abstraction Layer).

The full reference page, with every canonical specification this layer touches, lives in the documentation repository, which is private while the platform is being built.

Follow the buildAll twelve layers

Back to the platform overview