Clarity technology
Technology that knows its limits.
Clarity connects native sources, a server-confirmed account and a five-level safety runtime. Every helpful action begins with provenance, context and a clear boundary.
Built for verifiable decisions
Context in. Control stays.
Sources, permissions and execution are treated as separate technical states, so assistance never becomes silent authority.
Updated 11 August 2026
A capability address is a named entry in the Audecius platform register. It is neither a user count nor automatically a visible Clarity feature.
Capability register
Every route. With its real status.
Shipped, beta, in progress and planned together form the complete register. Safety & Law and AI are classifications and may overlap status groups.
Shipped
Recorded with the status shipped in the register.
Beta
Implemented, but not yet counted as reliably available.
In progress
Recorded as in_progress in the register; not an availability promise.
Planned
Recorded as planned in the register; not yet shipped.
Safety & Law
Platform rules and safety boundaries in the register. This classification is not a separate status.
AI-related
Capability addresses with a recorded AI consequence class. This classification can overlap status groups.
From a source to a receipt
From signal to receipt.
A source does not become an action directly. Provenance, relevance, role, a plan preview and the question of who may decide all come first.
Control path
SourceCalendar
The source remains visible on the proposal.
Capability Runtime
A boundary is code. Not just copy.
Permission, consequence class, daily budget and live approval are checked again at the point of execution. A rejected action receives a receipt too.
C0 to C4
Responsibility rises with impact.
Observe
Reads or shows. Changes nothing.
No execution path required.
Technical control contractSuggest
Puts information in context and recommends a next step.
A human decides and acts.
Technical control contractAfter your approval
Prepares a real change.
Preview and explicit approval before execution.
Technical control contractWithin your boundary
May act only within a predefined, reversible boundary.
Daily budget, live permission, receipt and undo; never on behalf of other people.
Technical control contractHuman only
Payment, medicine, law, identity or particularly sensitive safety.
Clarity may prepare, but not execute autonomously.
Technical control contractThe safety runtime is implemented in the current source contract. Clarity Ripple remains a preview as a complete, cross-domain product story until end-to-end verification is complete.
Native Apple technologies
Close to the system. Clear about permission.
A technology's role is described separately from its boundary. The presence of a framework does not grant Clarity access.
StoreKit
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.SwiftData
Native data models represent local Clarity states.
Local persistence is not the same as cloud synchronisation.EventKit
Calendar and reminder paths use Apple's permission model.
Access begins only after the relevant system permission.HealthKit
Supported health and activity signals remain subject to Apple's permissions.
No HealthKit category is read or written without explicit permission.Family Controls
Family-related protection paths use Apple's authorised system boundaries.
A Family plan alone grants no device or child-protection permission.Foundation Models
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.Ariadne in your Clarity plan
Two limits. No invented number.
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.
AI routes and limitsConnector catalogue
21entries. Three evidenced Google routes.
An entry in the Audecius platform catalogue describes an intended connection. It is not evidence of live operation, partnership or permission already granted.
All integrationsGoogle OAuth
No Google data flows without permission from the person or organisation.
Google Calendar
Only after a valid OAuth grant and within the granted read permission.
Gmail
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
Every detail. No small print.
Version, devices, plan limits, languages, account routes and known boundaries are documented in a single technical reference.