App Intents conformance — pre-WWDC 2026 posture

TL;DR: App Intents conformance is Hussh's pre-WWDC 2026 posture on Apple's developer framework: One conforms to App Intents to be a layer-citizen of Apple Intelligence rather than a competitor. Conformance, not competition, is the winning iOS-platform stance for a third-party agent. WWDC 2026 is the binary event that confirms or forecloses the position; three contingency responses are prepared.

Status as of 2026-05-10: see body.

Relations

Personal Operating Layer — the strategic thesis whose iOS execution path App Intents is.
One — the product whose intent surface gets defined.
Kai, Nav — the agents whose verbs become App Intents.
Apple frame — the design discipline that points to conformance over competition.
BYOA — the cross-platform commitment that hedges the iOS-platform-dependency.
MLX on One surfaces — the on-device-inference architecture that complements App Intents conformance.
Aha Moment — the v1-financial intent that exemplifies the surface design.
App Intents — WWDC 2026 Three-Outcome Tree — WWDC 2026 three-outcome tree

Why this matters

WWDC 2026 keynote is approximately five weeks out as of this page (target: early-to-mid June 2026). It is a binary platform event for One: the Personal Operating Layer thesis depends on iOS treating One as a layer-citizen-of-Apple-Intelligence, and the technical surface that makes that possible is App Intents and related Apple Intelligence developer APIs.

This page records Hussh's pre-WWDC posture, what conformance means in concrete engineering terms, and the contingency map for the three plausible WWDC outcomes.

What App Intents is

App Intents is Apple's framework for exposing app verbs to the system: Siri, Spotlight, Shortcuts, Apple Intelligence's personal-context surfaces, and the inter-app routing that lets a user ask the system to coordinate across apps that conform to the relevant intent shapes.

Architecturally, App Intents is the declarative API by which an app says: "I can do X for the user; here are the parameters I accept; here is the typed result I return." The system can then invoke the app's verb without the user opening the app, provided the app is conforming, the user has consented, and the surface invoking the verb has the right entitlements.

For Hushh, App Intents is the concrete mechanism by which One can be a layer under iOS rather than a destination the user opens.

What conformance means in engineering terms

Conformance to App Intents requires, scoped to v1:

A defined intent surface. What verbs does One expose? Examples plausible for v1: "Show my financial picture," "Surface today's fee leakage," "Open my consent log," "Summarize my inbox financial signal." Each is a typed App Intent with explicit parameters and explicit return shape.
Entity definitions. App Intents requires apps to declare the types the user might reference. Hushh entities at v1 plausibly include financial accounts, consent receipts, transparency log entries, and savings opportunities.
Privacy and consent semantics aligned to system primitives. Apple's framework enforces certain consent surfaces. PCHP is more stringent than these, but the system surfaces still need to be filled out correctly to ship.
Performance and reliability budgets. Intents that return slowly are demoted by the system. The Aha Moment sub-60-second target is also the App Intents surface budget.
No coupling to in-app UI for the verb result. Apple's framework rewards apps whose intents return typed values that the system can render in its own UI. Hushh's discipline: v1 intents should return clean typed results that compose into the system surface.

Why the position is conformance, not competition

Three reasons, in order of weight:

The math. Apple has the platform. Hussh does not. Competing for the system-level agent slot is a fight Hussh cannot win on iOS. Competing for being the third-party app the system invokes is a fight Hussh can win.
The thesis alignment. Personal Operating Layer is layer-not-destination. App Intents is exactly the API a layer-positioned app should embrace.
The user. A user whose system-level agent and whose personal-data layer cooperate gets a better experience than a user where the two contend. Hushh wins by making the cooperation real.

The three WWDC 2026 contingencies

Outcomes range from best to worst for Hussh, with concrete responses for each.

Outcome A — Apple ships an open App Intents / Apple Intelligence developer surface

Signal: new APIs that let third-party agents conform to system-level intents broadly; clear documentation; sample apps; explicit posture toward third-party agent diversity.

Hushh response: full conformance push. Engineering pivots to an App Intents-first surface for v1 verbs. Marketing posture: "One is the personal data and consent layer that makes Apple Intelligence work for you." Ecosystem partner narratives gain a clean iOS-native story.

Outcome B — Apple ships a constrained or favored-vendor App Intents surface

Signal: new APIs but with high entitlement bars, opaque review, or apparent favoritism toward Apple's own surfaces. Conformance possible but distribution uncertain.

Hushh response: dual-track. Conform to whatever surface ships, and simultaneously accelerate the cross-platform plan: web, Android, and BYOA cloud. The Personal Operating Layer thesis still holds; only the iOS-execution part gets harder.

Outcome C — Apple forecloses third-party agents at the OS layer

Signal: Apple Intelligence becomes a closed surface; no third-party verb invocation without Apple-mediated review and rate-limiting; or App Intents is absorbed into Apple-only flows.

Hussh response: material strategy change. The iOS-first plan changes to iOS-as-one-of-many. The wedge becomes BYOA on the user's terms, with cross-platform parity and explicit positioning that Hushh is the layer Apple will not provide.

What is not contingency-planned

The user value proposition does not change across all three outcomes. The user still owns their data, their consent, and their agents. The platform-side execution differs.
The PCHP protocol is platform-agnostic by design. It does not depend on Apple shipping anything in particular.
The Aha Moment surface ships regardless. Gmail-connect to 60-second financial picture works on web first if necessary.

Pre-WWDC engineering checklist

Things to do before WWDC 2026 keynote regardless of outcome:

Audit Hushh One's current intent surface against App Intents 2025-vintage docs. Identify the verbs that already exist in the product and would need to be exposed.
Design the v1 Hushh App Intents surface on paper. What verbs, what entities, what privacy strings. Six to ten verbs is the right ballpark.
Build a thin App Intents conformance demo: even one verb, end-to-end, working in the Shortcuts app. Useful as a platform-partner meeting artifact, parallel to the hu_ssh prototype.
Stay quiet publicly. WWDC announcements should be the surface that updates this page; pre-announcing Hussh's App Intents posture is a category error.

What this is not

Not a commitment to a specific Apple Intelligence API. The current Apple Intelligence surface as of pre-WWDC 2026 is in flux and any specific API name in this page may be deprecated by June.
Not an Apple endorsement. Hushh is an independent third-party iOS-platform-aligned developer with no formal partnership.
Not a substitute for the cross-platform plan. App Intents conformance is the iOS execution path of the Personal Operating Layer thesis. Web, Android, and BYOA-cloud paths are separate execution surfaces under the same thesis.

Architecture link/status refresh

Current architecture truth: App Intents remains a platform-conformance planning lane unless checked native code and tests prove a specific surface.
North-star direction: native actions should be consent-aware and auditable through Hussh policy.
Not shipped or implied: App Intents does not bypass PCHP, vault, PKM, or partner data boundaries.
Source notes: internal architecture catalog and future infrastructure design notes.

Sources

2026-05-10 baseline chat snapshot — candidate target identified during the 2026-05-10 wiki baseline; originating discussion in 2026-05-08 super-app-reframe and 2026-05-09 Apple-meeting chats.
Personal Operating Layer — the strategic thesis this page operationalizes for iOS.
Apple Frame — decision discipline.