Tip: select any text on this page to bring up the Ask tooltip and question the Synedrix OS assistant about it.
What Human Interface is
Human Interface is the layer where a person meets the system: it captures human intent, carries approval requests to a reviewer and back, and gives operators a surface to watch what a governed multi-agent system is doing. Dashboards, admin panels, operator APIs, and any command UI a human starts, reviews, or blocks work through, not the workflow logic that acts on a decision, and not the policy logic that decides whether an approval is required in the first place.
This layer stays deliberately generic. It renders and routes intent and decisions; it does not interpret them. The moment a click or a form submission needs to become a task graph, a policy check, or durable state, responsibility passes to Orchestration and, from there, to Governance & Controls.
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
- Dashboards
- Admin panels
- Operator APIs
- Approval surfaces
- Command UIs
Does not own
- Domain logic execution
- → Domain Pack Layer
- Tool adapters
- → Tool Abstraction Layer
- Memory internals
- → Memory & Data Layer
Interfaces with
The other layers this one exchanges work, state, or decisions with, and why.
Orchestration
a human-initiated action is handed off as a routed, sequenced step; this layer does not decompose or schedule work itself.
Observability
dashboards and operator panels consume Layer 10's logs, traces, and metrics; they display execution health, they don't compute it.
Governance
approval surfaces exist because Layer 9 requires a human decision at a checkpoint; this layer is the channel that decision travels through.
Current specification depth
Unlike most other layers, Human Interface has no dedicated deep-dive specification; its authoritative definition is the layer taxonomy entry. Orchestration and Governance & Controls carry most of the adjacent detail a reader might expect to find here: approval routing mechanics live in the Orchestration & Runtime Strategy and in the HITL Gateway Agent's own definition, not in a Human Interface spec.
OS agents at this layer
Layer principles that apply
- Shared before specific: a dashboard or approval surface built for one domain pack's needs should still be a reusable OS-layer capability wherever the underlying concern isn't actually domain-specific.
- Controls before execution: an approval surface routes a human decision into governance; it must never become a shortcut around it.
Human Interface questions, answered
Short, citable answers drawn from this page.
What is the Human Interface layer in Synedrix OS?
Human Interface is layer 1 of the twelve-layer Synedrix OS architecture, in the "Human and intent surface" group. Where a person meets the system. It renders and routes; it does not decide.
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.