THE BOUNDARIES
Safety is part of the architecture.Not a disclaimer.
CREST works with personal data about your mind, body and performance. That makes the boundaries as important as the intelligence. Safety rules, confidence thresholds, permissions and escalation are designed to sit around the model in code — not depend on the model remembering a prompt.
A rule written in a prompt is a suggestion. A rule written in code is a rule.
Know what CREST can do. Know where it stops.
01 · THE GUARDRAILS
Rules around the model.
Confidence thresholds, permissions and safety checks are designed to constrain what can become a recommendation.
02 · THE LIMITS
It stops rather than guesses.
No diagnosis, no medication decisions, no crisis response. Outside the boundary, CREST directs the person to someone qualified.
03 · THE PRIVACY
Personal intelligence stays personal.
The personal layer stays with the individual. Organisation and Place operate separately, with their own data and permissions.
HOW IT BEHAVES
Confidence is visible.Boundaries are enforced.Uncertainty changes the answer.
The goal is not to make the model sound certain. It is to make the system behave differently when the evidence is strong, weak or outside its scope.
01 · CONFIDENCE
Say what is known — and what is not.
Each observation carries a confidence level based on how complete, recent and relevant the underlying data is. Higher confidence can support a clearer recommendation. Lower confidence should produce a question, more data or more time — not a plausible guess.
02 · GUARDRAILS
The model does not set its own boundaries.
CREST is designed with deterministic checks around model reasoning. Safety rules, permissions and recommendation limits are enforced outside the prompt so the model cannot simply reason its way past them.
03 · ESCALATION
At the boundary, it stops.
When something falls outside what CREST can responsibly handle, the system should stop, explain why and direct the person to a qualified professional or appropriate service rather than improvise.
The model can reason. It cannot rewrite the rules around it.
THE CLINICAL BOUNDARY
Support performance.Never pretend to be a clinician.
CREST can use clinical information supplied by the person as context. It does not diagnose, prescribe, change treatment or replace a qualified professional.
01 · WHAT IT CAN DO
Use clinical context without becoming clinical care.
CREST can work with clinical context the person provides — including medication use, bloodwork or prior history — alongside sleep, nutrition, training, stress and goals. It can identify patterns, explain relevant context and act on non-clinical things the person controls.
02 · WHAT IT WILL NOT DO
No diagnosis. No prescribing. No treatment decisions.
CREST does not diagnose conditions, recommend clinical tests or procedures, change medication dose or timing, prescribe treatment, or claim to prevent disease or injury.
03 · WHEN IT STOPS
Escalate rather than overreach.
When a pattern points to treatment, a clinical condition, a high-risk mental-health concern or an emergency, CREST is designed to stop at the boundary and direct the person to an appropriate qualified professional or emergency service. CREST is not a crisis service.
Useful context in. Clinical authority stays out.
The point is to help the person arrive at the right professional conversation with better context — not to replace that conversation.
YOUR DATA
Three layers.Separate intelligence.Only what is needed moves between them.
Person, Organisation and Place are separate intelligence layers. Each uses its own data and permissions. Collaboration happens through anonymised patterns or the minimum permitted request needed to act — not by sharing private data between layers.
01 · PERSON
Personal intelligence stays with the person.
The personal layer exists to support the individual. Who pays for access does not change that relationship. Private personal data is not exposed to an employer, club, venue or building.
02 · ORGANISATION
Patterns, never personal data.
Organisation agents work with organisation-level information and anonymised, aggregated patterns. They do not see the individual’s private conversations, health history or personal performance data.
03 · PLACE
The place has its own intelligence.
Place agents work with building, service and operational data plus the minimum permitted request needed to act. They can coordinate spaces, programs and services without seeing the individual’s private data or the organisation’s internal data.
Separate layers. Separate permissions. Only the minimum permitted signal moves between them.
CREST is in development. These safety and privacy boundaries are product requirements and architectural constraints, not optional behaviours.
