System capabilities¶
Intent becomes useful work
Capabilities give orchestration a practical reach
Unison connects a person's intent to local tools, governed services, skills, models, and other agents. Each capability declares what it can do, what information it needs, and which controls apply.
The experience begins with the outcome¶
A person can ask Unison to prepare a meeting, investigate a household problem, organize records, or continue a longer project. The orchestrator resolves that intent into a plan and selects capabilities that fit the purpose, available context, current environment, and applicable policy.
The experience presents the useful result, its sources, uncertainty, pending choices, and any action that requires confirmation. Tool names and provider details remain available when they help a person understand or audit the work.
Capabilities have declared roles¶
Local tools
Inspect approved system state, work with scoped files, calculate exact values, and perform other operations on the personal node.
Connectors
Reach services such as calendars, email, household devices, and selected information providers through governed network routes.
Skills
Define repeatable procedures, required inputs, safety checks, evidence, and recovery for work that benefits from a consistent route.
Model services
Interpret novel requests, propose plans, transform information, and generate candidate outputs within the authority granted to the surrounding workflow.
Agent peers
Accept delegated work with an explicit purpose, data scope, capability set, time limit, and return contract.
Modality services
Translate evidence of intent and express semantic outcomes through conversation, visual presentation, Braille, sign, touch, and future interaction forms.
Capabilities provide operations and evidence. Identity, consent, policy, recipients, disclosure, incident state, and physical actuation remain with the platform services responsible for those decisions.
Connection follows person-level authority¶
When a capability needs an account, device, network route, or protected context, Unison presents the purpose, requested access, expected disclosure, retention, and available alternatives. The applicable person or operator can approve the grant allowed by policy.
Credentials live in an approved secrets service. Capability declarations carry references to credentials and context rather than secret values. Networked operations pass through policy and egress controls, and receipts record the provider, purpose, disclosure, result, and recovery state appropriate to the action.
Deterministic routes grow through use¶
Unison prefers a tested skill or exact tool when one fits the request. Governed inference supports novel work and composes capabilities when a complete route is not yet available. Repeated successful patterns can become proposals for a new or improved skill.
A proposal records the triggering intent, candidate procedure, required permissions, failure behavior, tests, and evidence. Review and versioning turn the useful pattern into a dependable shared capability while preserving a route for future requests that remain novel.
Failure remains part of the outcome¶
A capability reports partial results, timeouts, unavailable providers, uncertainty, and side effects in a form the orchestrator can reason about. The experience can then offer retry, substitution, cancellation, compensation, or a useful partial result while retaining the person's original intent.