Capability addresses
Complete platform register · as of 11 August 2026
Clarity
Devices, plans, Space, Ariadne, languages and integrations — with a visible status and a clear distinction between available, confirmed and preview.
These details describe the current product and source contract. A confirmed release window is not an App Store availability promise.

Specification, not superlatives
Date, unit, measurement scope and boundary appear together, so a technical number cannot become an invented claim of scale.
Reading status
The platform foundation behind Clarity
Every number describes the Audecius platform register as of 11 August 2026. It is not an estimate of users, partnerships or infrastructure scale.
Complete platform register · as of 11 August 2026
Status shipped · beta entries not included
Classification in the register · across statuses
Classification in the register · across statuses
Capability register
A capability address is a named entry in the Audecius platform register. It is neither a user count nor automatically a visible Clarity feature. Updated: 11 August 2026.
Platform rules and safety boundaries in the register. This classification is not a separate status.
Capability addresses with a recorded AI consequence class. This classification can overlap status groups.
Availability
Configuration and public availability are different facts. They are therefore shown separately.
Clarity 2.0 (Build 2)
Confirmed in the current buildExpected at the beginning of September 2026; no confirmed calendar date yet
PreviewiPhone and iPad
Confirmed in the current buildiOS and iPadOS 26.2
Confirmed in the current buildA widget target is configured from iOS and iPadOS 26.4
Confirmed in the current buildConfigured in the current project
Confirmed in the current buildMac Catalyst is configured; public Mac distribution is not confirmed
PreviewOne Audecius Account for the app, web account and support
AvailablePlans and Clarity Space
Allowances follow the current plan contract. Purchases, changes and cancellations are managed through Apple.
Personal allowance; not a shared pool.
Personal allowance; not organisation storage.
Measured per person; not a shared household pool.
The teacher's personal allowance; not a school allowance.
Personal allowance in the One plan.
Allowance in the School contract; not per person.
Decimal units: 1 MB equals 1,000,000 bytes, 1 GB equals 1,000,000,000 bytes and 1 TB equals 1,000,000,000,000 bytes. These values are allowances, not a statement about total infrastructure capacity.
Ariadne
Messages per day counts visible messages in the relevant Clarity plan. It is not a promise of response time, model availability or successful execution. The provider-call ceiling is the maximum technical token limit for one model call. It is not a guaranteed response length, context window, daily traffic figure or consumption forecast.
The current cloud path uses Anthropic. Selected structured tasks can use Apple's Foundation Models on device when the model and device are available. This does not mean the whole Ariadne chat runs locally.
Plan, Ariadne tier and daily budget are determined server-side. An interface alone cannot unlock a higher allowance.
Ultra, public model choice, external API, code limits and extended developer allowances are not part of the public Clarity product contract.
Native technologies
Naming an Apple framework describes the technical path. It does not claim access without system permission.
Apple manages purchase, subscription and restoration paths.
StoreKit remains the authority for Apple purchases. Web subscriptions grant rights only after a confirmed Stripe webhook and server-side entitlement readback.Native data models represent local Clarity states.
Local persistence is not the same as cloud synchronisation.Calendar and reminder paths use Apple's permission model.
Access begins only after the relevant system permission.Supported health and activity signals remain subject to Apple's permissions.
No HealthKit category is read or written without explicit permission.Family-related protection paths use Apple's authorised system boundaries.
A Family plan alone grants no device or child-protection permission.Selected structured AI tasks can run locally on supported devices.
This does not make the whole Ariadne chat local and requires device and model availability.Action safeguards
The consequence class is checked before execution. Preview, approval, receipt and undo are technical states — not decorative notices.
Reads or shows. Changes nothing.
No execution path required.Puts information in context and recommends a next step.
A human decides and acts.Prepares a real change.
Preview and explicit approval before execution.May act only within a predefined, reversible boundary.
Daily budget, live permission, receipt and undo; never on behalf of other people.Payment, medicine, law, identity or particularly sensitive safety.
Clarity may prepare, but not execute autonomously.Action safeguards are implemented in supported action paths. Clarity Ripple as a complete cross-area execution remains a preview until end-to-end review is complete.
Audecius Account
The website reads the plan, billing source, Ariadne tier and personal Space from the account contract. Apple remains responsible for purchases and cancellations.
Open AccountOne-time email code for existing Audecius Accounts
HTTP-only cookie; browser scripts cannot read access or refresh tokens
Server-confirmed in the web account
Personal, server-confirmed meter with categories
Editable in the web account
No active web management yet
Currently a direct email request path; no automatic self-service execution yet
Languages
Private areas use the profile language from Clarity. The public catalogue is reviewed route by route before a language is described as available.
Public route families are reviewed in both languages.
The profile language is applied after sign-in.
No claim of a fully 13-language app.
Connector catalogue
21An entry in the Audecius platform catalogue describes an intended connection. It is not evidence of live operation, partnership or permission already granted.
Open integration statusNo Google data flows without permission from the person or organisation.
Only after a valid OAuth grant and within the granted read permission.
Only after a valid OAuth grant and within the granted send permission.
All other catalogue entries are not described as live in the public technical status. The three evidenced paths describe the platform state. This does not claim that these paths are publicly enabled in Clarity.
Technology providers
Deliberate boundaries
The technical provider-call ceiling is documented as a safety maximum. Actual output tokens, tool and reasoning budgets, consumption and traffic are not published as sales figures.
Community, Club, Marketplace and Creator are not part of the first public release scope.
Outlook, public production access and native SDKs remain in Private Preview; Sandbox API, sandbox keys and Webhook Lab are available to approved developers.
A shared Family storage pool and end-to-end seat assignment are described as live only after complete server and app review.
New web support cases and the Legal Centre remain blocked or non-indexable until legal-version and minor-access approval is unambiguous.
The technical reference explains boundaries. Feature pages show how they feel in everyday life.