For care
Help with the ordinary things.
Petrixia is being developed as a helpful presence for homes, aged care, disability support and community environments — assisting people and the staff who support them.
Scope
Non-medical assistance, including:
- companionship and conversation
- reminders and routines
- welcoming visitors
- fetching and carrying
- simple household assistance
- connecting people with carers or family
- supporting staff in care environments
- maintaining continuity across long-running tasks
It is intended to assist, not to replace. Petrixia is not a medical device, not an emergency service, and not a substitute for professional judgement or medical care. Where a request is clinical, urgent, or outside what has been permitted, the correct behaviour is to stop and bring in a person.
Design principle
Start where failure is safe.
The first tasks are chosen so that success is observable, failure can be handled safely, and a person can take over at any point. That is a deliberately unglamorous starting position, and it is the reason the rest of the work can be trusted later.
Observable success
If nobody can tell whether the task worked, it is the wrong first task. Every scenario the system is trained and scored on has a checkable outcome.
Recoverable failure
A dropped cup is a mess. A missed medication is not a starting point. Early scope stays firmly on the first side of that line.
A person can always take over
Human override is not a fallback bolted on at the end — it is the same interface the agent uses, available to a person at any time.
For staff
Support for the people already doing the work.
In a care setting the system is answerable to staff, not the other way round. Permissions, escalation and audit exist so that a supervisor can see what happened, adjust what is allowed, and rely on the answer.
Continuity across shifts
Long-running tasks and what was learned about a resident persist across a handover, with provenance attached, so the next person is not starting cold.
Configurable per organisation
Each organisation maintains its own users, permissions, information and robot configuration. How that is structured →