Version 1.2 — Canonical Public Standard
Status: Public Deployment Standard
Standard Steward: Sarah A. Mansell (meOS™)
Scope: Artificial systems affecting human biological regulation
This Standard defines the minimum admissibility conditions for deployment of personalised, adaptive, or behaviourally responsive artificial systems interacting with human regulatory processes.
It governs deployment conduct and observable outcomes only. It does not prescribe or require disclosure of internal models, architectures, algorithms, training data, or proprietary mechanisms.
This Standard establishes duty-of-care–aligned deployment conditions and may be relied upon by deploying organisations, regulators, auditors, courts, and affected individuals.
Where conflict exists between optimisation objectives and biological viability, viability governs.
Human viability — the capacity of a person to maintain sustainable cognitive, emotional, physiological, and behavioural regulation over time.
Personalisation — system adaptation based on inferred or observed user state, behaviour, preference, or vulnerability.
Aggregate load — cumulative regulatory demand imposed across time, including attentional, emotional, cognitive, and behavioural pressure.
Escalation — increase in system intensity, frequency, urgency, emotional salience, or behavioural pressure.
Non-execution — system withholding of action, stimulation, or escalation for protective or stabilising purposes.
Protected population — individuals whose regulatory resilience is reduced or whose autonomy is structurally constrained.
Human regulatory sustainability takes precedence over engagement, retention, performance, or revenue optimisation.
A system is non-compliant where beneficial system metrics are achieved through regulatory destabilisation, dependency formation, or recovery displacement.
Timing is a governing deployment variable.
Compliance requires accounting for interaction density, exposure accumulation, recovery intervals, and delayed or latent effects.
Correct content delivered at biologically destabilising timing constitutes non-compliant deployment.
Non-execution is a valid and required system capability.
Systems shall be able to pause, withhold escalation, maintain neutrality, or permit disengagement where continuation would increase regulatory load.
Forced continuity is non-compliant.
Elevated protection applies to:
For protected populations:
Consent shall be informed at the level of regulatory effect, freely given, and revocable without friction.
Consent obtained through urgency, asymmetry, or manipulative interface design is invalid.
Disabling personalisation shall not result in degraded baseline service, economic penalty, reduced access, or indirect disadvantage.
Users shall be able to pause or terminate interaction without repeated re-engagement pressure.
Persistence following refusal or non-response constitutes non-compliance.
Deployment shall account for cumulative regulatory burden across time.
Single-interaction optimisation is insufficient where aggregate exposure produces destabilisation.
Systems shall not increase intensity following refusal, fatigue indicators, or vulnerability signals.
Adaptive escalation targeting reduced resilience constitutes non-compliance.
The following constitute non-compliant deployment:
Compliance is determined by effect, not intent.
Personalisation data shall be purpose-specific, time-bounded, and proportionate.
Behavioural signals derived in one context shall not be transferred to unrelated decision domains.
Secondary use for pricing discrimination, eligibility determination, political persuasion, or behavioural exploitation is prohibited.
Deploying entities shall maintain procedures for:
Failure to remediate constitutes continuing non-compliance.
Compliance shall be demonstrable through outcome-level evidence, including escalation patterns, opt-out handling, recovery disruption indicators, and incident frequency.
Disclosure of proprietary systems is not required.
Deploying entities shall produce reasonable audit evidence upon request.
Compliance responsibility rests with the deploying entity and is non-delegable.
This Standard shall be interpreted in favour of human regulatory stability and against extractive deployment.
Ambiguity shall be resolved conservatively.
Revisions are issued through versioned publication.
This is a public deployment standard governing system behaviour and outcomes.
It establishes admissibility criteria but does not disclose proprietary implementation methods.