Trust must be designed in

A support network must be useful without becoming intrusive.

Free access should not mean hidden surveillance, unrestricted AI decisions, insecure router sharing or unclear responsibility. The network needs visible rules and auditable human control.

Core trust principles

Privacy, control and accountability from the beginning.

Purpose limitation

Access, telemetry and personal information are used only for clearly stated support, security and evaluation purposes.

Data minimisation

Anonymous access is preferred for general resources. Identifiable accounts are introduced only when a real support need justifies them.

Human approval levels

Informational guidance may be automated; sensitive sharing, external actions and high-impact decisions require authorised people.

Transparent status

Users can see whether content is local, whether the device is online and whether any information is waiting to be shared.

Independent testing

Network isolation, accessibility, security, support wording and incident handling should be reviewed beyond the core build team.

Exit and deletion

Partners need a safe shutdown path, and users need understandable controls for removing locally stored personal information.

Human-control model

Four levels of action

LevelExampleRequired control
L1 — InformationExplain a coping exercise, lesson or checklist.Can run locally with clear boundaries and sources.
L2 — Reversible local actionSave a plan or mark a lesson complete.User confirmation and easy undo/delete.
L3 — External or sensitive actionShare progress, contact a service or upload information.Explicit informed approval and visible recipient.
L4 — High-impact actionSafeguarding, medical, legal, eligibility or emergency decision.Authorised human professional; 4P3X AI™ supports but does not decide.
Kyzel Kreates™ emblem
Responsible public positioning

Say exactly what exists.

  • 15 existing support App foundations have been built across the ecosystem.
  • This showcase is a working installable and offline-capable demonstration platform.
  • The free-access network is a proposed partnership and pilot model.
  • No provider, council or public organisation should be described as participating until a written agreement exists.
  • No App should be described as a replacement for qualified human support.
Future foundation governance

Public benefit needs independent controls.

Before TH3 4P3X F0UND4T10N™ can operate formally, the plan requires a suitable legal structure, independent oversight, transparent financial controls and clear separation from commercial activity.

Independent governance

Trustees or directors should include suitable safeguarding, education, finance, legal, technology and lived-experience perspectives.

Financial separation

Foundation money, restricted grants and commercial Kyzel Kreates™ income must be recorded and controlled separately.

Published accountability

Annual reporting should explain funding, delivery, evidence, complaints, incidents, limitations and the difference between pilots and proven impact.

4P3X AI™ boundary

Supportive, not independent.

4P3X AI™ is a human-directed co-building and guidance system. It must not be described as conscious, alive, legally independent or able to own or control the planned Foundation.

Public claims boundary

No hidden exaggeration.

The network is not presented as a nationwide operational internet service, the Foundation is not presented as registered, and support Apps are not presented as clinically certified unless evidence is available.

View all status boundaries