Modalities and governed ecosystem¶
Unison grows through independently maintained modality adapters and capability packages connected by common contracts. Voice, visual, Braille, sign, tactile, switch, AAC, haptic, BCI, and future teams can develop in parallel while preserving person-level authority and semantic continuity.
Common integration point¶
Every modality adapter contributes evidence of intent and composes governed semantic outcomes. Platform services retain identity, consent, policy, incident state, capability authority, and physical actuation decisions.
A signed capability declaration identifies supported devices, languages, features, data paths, assurance, interruption, confirmation, recovery, offline behavior, compatibility, maintainers, software inventory, and evidence. The orchestrator selects eligible adapters for the person, intent, device, and context.
Read the modality integration contract.
Current engineering foundation¶
- Semantic outcomes carry meaning, provenance, uncertainty, privacy state, actions, confirmation, cancellation, retry, and recovery.
- Intent routing accepts modality evidence through governed channel and orchestration boundaries.
- Speech supports local streaming foundations, captions, interruption, and content-minimized operational evidence.
- Visual software supports semantic composition, keyboard operation, contrast, reflow, zoom, and reduced motion.
- Braille, sign, and BCI components provide experimental software contracts and simulation evidence in their owning repositories.
- Model routing and capability packages enforce disclosure, location, cost, risk, compatibility, signature, and revocation policy.
Qualification path¶
An adapter progresses through declared experimental capability, software evidence, representative hardware, cross-modal continuity, adversarial validation, participatory evaluation, incident readiness, and a published compatibility profile.
Braille, sign, switch, AAC, haptic, BCI, robotics, and spatial-control support depends on the hardware matrices, maintenance ownership, incident procedures, and participatory evidence appropriate to each capability. Simulation provides engineering evidence and a foundation for physical qualification.
Independent contribution¶
Modality teams own their language, device, interaction, performance, and maintenance expertise. The platform contract gives every team the same route into intent, identity claims, policy context, semantic outcomes, confirmation, and recovery.
New adapters declare assurance, privacy, metadata, retention, cancellation, fallback, compatibility, provenance, and support ownership. Signed packages and revocation protect the ecosystem as implementations and maintainers evolve.