macOS
System Keychain, native notifications and foreground / background ownership.
Key protection, per-device identity, permission prompts, sleep and resume, signed updates.
Professional desktop conversation, room context, document hand-off.
A common communication and E2EE architecture for macOS, Windows, Linux, iOS, Android and Web — with explicit device ownership and a separate Headless integration profile.
Select a platform to inspect the target adapter and acceptance focus. All cards remain readable if JavaScript is unavailable.
System Keychain, native notifications and foreground / background ownership.
Key protection, per-device identity, permission prompts, sleep and resume, signed updates.
Professional desktop conversation, room context, document hand-off.
OS-protected credentials, notifications, per-user storage and application lifecycle.
Lock/unlock, local encryption, multi-user separation, update rollback.
Enterprise workstations and managed distribution.
Desktop secret store or an explicitly approved fallback; background lifecycle.
Secret-service availability, least privilege, packaging and desktop environment.
Technical teams and enterprise desktops.
Keychain, protected local storage, app lifecycle and push notification adapter.
Background limits, device recovery, lock state and push data minimization.
Secure mobile communication with native interaction patterns.
Android Keystore, app lifecycle, storage and notification permissions.
Key restore limits, battery policies, backup exclusions and device integrity.
Managed and personal Android devices under an agreed policy.
Browser-native cryptography and storage with an explicit session and data retention policy.
Storage eviction, tab concurrency, CSP, XSS protection and logout behavior.
Browser-based access without claiming native device guarantees.
Select a platform and carry only its fixed label into your evaluation request. No device or simulation data is sent. Request platform evaluation →
Platform adapters are architectural options, not a verified six-platform release or a claim that the same crypto store can be shared across devices.
State machines, message semantics, Matrix interoperability and E2EE contracts.
OS vaults, notifications, lifecycle and per-device crypto persistence.
Desktop, mobile and browser flows; accessibility and identity transparency.
A separate local-only Headless Client API and authorized host orchestration.
A functional account is an organizational identity, not an independent messenger. ITL designs delegated handling, BPMN case routing and controlled outward release as a separate business layer.
One service address, two separate E2EE rooms and controlled forwarding. An example of what can be composed from Headless Clientmodul Pro and an optional orchestration layer.
An insured person contacts the published organizational identity. Automated contacts must be recognisable as such.
The host application pairs room contexts, routes events and attachments under an agreed purpose, and checks invitations and staff access.
Employees work in a separate room. Outward replies are released under a documented policy with clear reviewer responsibility.
The automation component may decrypt and re-encrypt inside a trusted, authorized host. This does not create continuous E2EE between the member and a named employee; legal and provider integration boundaries must be checked.
Two room contexts, invitation states, inward routing, message revisions, explicit release, uncertain send and safe failure paths.
Room pairing, BPMN/case orchestration, user permissions, durable outbox and auditable incident response require a defined operating host.
Actual Matrix/Fachdienst test, security assessment, approved service login, allowed forwarding, retention, restart and provider/qualification decisions.
Two separately encrypted Matrix room contexts with an integrating host. The Headless module API stays local; any network interface belongs to the host.
Client and Headless are parallel product profiles; Native and Java are two paths inside Headless, not additional clients. Business orchestration and normative services remain separate scopes.
Purpose: User-facing messaging and device-local E2EE
Boundary: Own client identity, keys and platform adapter; no Headless host semantics
Current claim: Six target adapters, not one qualified six-platform release
Inspect boundary →Purpose: Embeddable TI-M communication component
Boundary: Local module API only; host owns its UI and any separately designed network gateway
Current claim: Existing development foundation; current release gate open
Inspect boundary →Purpose: Matrix transport, E2EE, SSSS and session lifecycle
Boundary: Single runtime and crypto owner in the ITL design; native handles do not enter business APIs
Current claim: Existing source-bound foundation; product-specific testing required
Inspect boundary →Purpose: Fully supported Java/Quarkus integration for PVS/KIS
Boundary: Java/Quarkus host → existing FFM bridge → local Flat C ABI → Rust; no second Matrix owner
Current claim: Java/Quarkus integration fully supported; SDK artefacts and host release evidence scoped separately
Inspect boundary →Purpose: Organizational handling, room pairing and controlled replies
Boundary: Trusted host owns authorization, forwarding policy, outbox, audits and incident handling
Current claim: Browser scenario; live E2EE and integration not qualified
Inspect boundary →Purpose: Internal business workflow and separate normative Fachdienst scope
Boundary: BPMN does not own Matrix keys or authoritative TI-Flow FHIR Task state
Current claim: BPMN foundation described; complete TI-Flow FD not implied
Inspect boundary →Purpose: Applicable external normative requirements
Boundary: Compliance reference for product profiles; not a deployable ITL runtime layer
Current claim: gematik release reference, not ITL product readiness
Inspect boundary →Own product-type PTV and platform-specific acceptance must be assessed for each target release.
Local-only module API; any host network interface remains outside the Headless API boundary (A_28651).
ATV obligations, controlled integration approval, operating context and independent evidence are separate from code quality.
Reference: TI-Messenger_26_2, gemSpec_TI-M_Pro 1.2.0. Applicability and legally relevant versions must be confirmed for each product and submission. Official source ↗
Define supported profiles, project scope, operating model and measurable acceptance before commitments.