How It Works
The Engine
Cushi is built around one simple structure.
An activity made up of required tasks
Acknowledged before the tasks are carried out
Version controlled
Recorded
Work does not fail because people try to do the wrong thing.
Work fails because guidance is assumed, not acknowledged.
Instruction Flow
We focus on practical, task-oriented onboarding lessons that your team can immediately apply, ensuring they hit the ground running and deliver results from day one.
When the activity changes, a new version is created.
Previous versions remain recorded.
Create authorised activity
Acknowledgement Flow
Before tasks can be marked complete, the activity must be acknowledged.
Acknowledgement is mandatory before task completion.
Cushi Records
Activity name
User identity
Version number
Time of acknowledgement
Acknowledgement records are immutable once created.
Activity acknowledgement confirmation
Version Control
When guidance changes, Cushi creates a new version.
When guidance changes, Cushi creates a new version.
When guidance changes, Cushi creates a new version.
Version history view
Record and Export
Before tasks can be marked complete, the activity must be acknowledged.
Acknowledgement is mandatory before task completion.
Export screen
Security & Boundaries
Records are encrypted in transit and at rest.
Hosting is located in Australia where required.
Multi tenant separation protects organisational data.
Role based permissions control access.
Cushi.app
Cushi.app is where activities are created, acknowledged, versioned, and recorded. It does not manage risk. It records acknowledgement before execution.
Version history view
For Smaller Teams
A small association can define one activity.
Members acknowledge it before carrying out tasks.
The record is stored.
Clarity replaces assumption.
For Larger Organisations
Larger organisations may manage many activities.
Acknowledgement must be distributed.
Records must be traceable.
Cushi supports structured acknowledgement.
Compliance assessment remains the responsibility of the organisation.
Start
Start with one activity that carries consequence. Define it. Version it. Require acknowledgement. Record it.
Hostile Audit – How It Works
No compliance claims are made.
Acknowledgement is defined as recorded confirmation, not comprehension.
Mandatory acknowledgement before task completion is clearly stated.
Version history permanence is stated.
Immutability of acknowledgement records is stated.
Export capability is stated without overstating format or integration.
Boundaries are clearly defined.
No claim of enforcement outside system workflow.