Platform
Context is the thing that keeps getting lost
Human-services systems lose context every time a person crosses an organisation, a piece of software or a funding boundary. Sonic is the layer that holds it.
Why context is lost
Every system is complete on its own terms
A care platform, a clinical system, a finance platform and a funding portal each hold a true and partial account of the same person. None of them is wrong. None of them is enough.
Boundaries are where meaning drops
A referral carries a record. It rarely carries the reasoning, the risk history or the agreements that made the record make sense.
Migration is not the answer
Replacing every operational system in a sector is neither practical nor desirable. The systems are not the problem; the space between them is.
Human journeys outlast systems
Providers change, software changes, funding changes and organisations evolve. The person's history, context and progress should continue with them.
Architecture
The Sonic context and intelligence layer
The person at the centre. The systems they move between around them. Context preserved across every interaction.
A person sits at the centre of the Sonic context and intelligence layer, which holds human context, business context, intelligence, evidence, connectivity and compliance. Around it sit the systems a person crosses: disability, aged care, health, families, providers, business systems, government, and funders and insurers. Sonic preserves context between those systems rather than replacing them.
Sonic infrastructure
- Human context
- AI intelligence
- Connectivity
Disability
Supports and outcomes
Aged care
Quality and wellbeing
Families
Continuity and peace of mind
Business systems
Client systems and operations
Government
Policy, funding and commissioning
Funders and insurers
Utilisation, risk and outcomes
Providers
Programs and service delivery
Health
Clinical and community care
AI personas
Nelly
AI intelligence supporting the person throughout their journey.
Grace
AI intelligence helping organisations support the person.
The four pillars
What the layer actually does
Human Context
Longitudinal goals, needs, supports, relationships, decisions, risks, budgets, preferences and outcomes, held as a continuous record of a person rather than as one organisation's file.
- Goals and needs tracked over years, not service periods
- Relationships and supports as first-class information
- Decisions and their reasoning, kept together
- Risk and preference history that travels with the person
Business Context
Gives authorised organisations the context and decision evidence relevant to the person they support, helping them identify gaps, risks, changes and next steps.
- Relevant human context available to authorised teams
- Decision evidence and reasoning kept together
- Risks, gaps and changes surfaced as they emerge
- Suggested next steps and improvements
Intelligence
AI that understands the context around the person and their connected journey, so what it surfaces is relevant, timely and explainable.
- Understands the role, situation and point in the journey
- Surfaces patterns, risks, gaps and next-best actions
- Supports people to make decisions rather than making decisions for them
- Retains the context and reasoning behind important recommendations
Connectivity
APIs and integration services that let Sonic sit alongside existing systems. Nobody is asked to migrate in order to participate.
- API-first design across the platform
- Integration rather than platform replacement
- Context contributed and consumed by existing systems
- Clear role boundaries between participating organisations
Intelligence
Two assistants, two jobs
Sonic does not claim that AI makes decisions on anyone's behalf. Both assistants work with structured context to help people make better-informed decisions.
Nelly
Person-facing intelligence
Nelly helps people understand their circumstances, goals, funding, supports and risks, and turns that context into guidance and next actions.
Grace
Business-facing intelligence
Grace interprets the person’s authorised context to identify gaps, risks, changes, evidence and next actions relevant to the support being delivered.
Keeping the person-facing and business-facing assistants separate is a deliberate design choice. They serve different people, work from different views of the same context and support different responsibilities.
Architecture detail
How the architecture fits together
One continuous human context, intelligence for both sides, and connectivity across existing systems.
- Human Context Layer
- The core infrastructure that preserves structured context around the person across organisations, systems, providers and funding changes.
- Nelly & Grace
- Two AI intelligence layers working from the same underlying human context: Nelly for the person, Grace for authorised organisations supporting them.
- Decision Evidence
- Preserves the context, reasoning, risks and evidence surrounding important decisions so they remain understandable and explainable over time.
- Sonic Connect
- Connects Sonic to existing systems through APIs, integrations and browser-assisted workflows, allowing authorised context and evidence to move without requiring platform replacement.
- Standards Packs
- Configure sector-specific terminology, rules, evidence requirements and workflows without rebuilding the underlying Human Context Layer.
Future portability
Built to adapt across sectors
Disability, aged care, health, veterans and other human-service systems have different rules, workflows and terminology. Sonic is designed so those differences can be configured without rebuilding the underlying platform.
New standards, same foundation
Sector-specific obligations, evidence requirements and terminology are applied through configurable Standards Packs.
Different workflows, common structure
Each sector works differently, but the need to understand actions, decisions, risks, evidence and outcomes is shared.
Human context that can continue
People often move across services, providers and funding systems. Their goals, history and context should be able to continue with them rather than starting again.
Partnership
Talk to us about integration
If you run a platform, a service network or a funding programme, there is usually a defined first use case worth testing.