Applications & Use Cases

Capability boundary

SENEX has local-first working foundations and is developing toward a future V1-testnet. The scenarios below are product directions, not claims of production availability, regulatory compliance, clinical effectiveness, financial performance, or network-scale deployment.

The strongest use cases for AIA are those where personal or organizational context is valuable but should remain under the owner's control. Local-first operation can provide immediate utility; governed interaction can later enable bounded collaboration when participants explicitly choose it.

Status

Status label	Scope
Working foundation	Local-first AIA behavior and owner-controlled context are the present foundation.
V1-testnet target	Test governed interactions among authorized participants in a production-candidate environment using test-only value.
Research direction	Collective intelligence, verified contribution, provider coordination, and cross-organization applications.
External validation required	Domain safety, security, privacy, accessibility, legal suitability, and claims of real-world effectiveness.

A safe use-case pattern

A prospective application should be described through user-visible boundaries:

1. Local purpose — what value can the AIA provide without sending private context elsewhere?
2. Optional interaction — what additional outcome requires another participant or shared service?
3. Bounded authorization — what purpose, data category, recipient, and duration does the owner approve?
4. Minimum disclosure — what is the least information required for the interaction?
5. Verifiable outcome — how can the result be checked without exposing unrelated context?
6. Revocation and exit — how can future interaction stop, and what records must remain?
7. Human accountability — who responds when the result is wrong, unsafe, or disputed?

This pattern is a design discipline, not a guarantee that every proposed domain is suitable.

Personal knowledge and continuity

Potential outcome: help a person organize their own notes, decisions, preferences, and ongoing work while retaining local control.

The local-first foundation is most directly aligned with:

• retrieving owner-approved personal knowledge;
• maintaining continuity across projects and sessions;
• drafting or summarizing from sources the owner selects;
• distinguishing private context from information approved for sharing; and
• showing when an answer is based on local material versus an external interaction.

Before broader deployment, evaluation should cover incorrect retrieval, stale context, sensitive inference, deletion expectations, account recovery, and device compromise.

Team and organizational knowledge

Potential outcome: allow a team to coordinate with clear ownership and access boundaries rather than copying all internal material into a single unrestricted system.

A governed design could support:

• owner-approved workspaces and shared knowledge scopes;
• role-appropriate access to organizational context;
• traceable updates to shared material;
• explicit handoff between personal and organizational authority; and
• review of external-service interactions.

This direction requires external validation of access control, offboarding, retention, auditability, and protection of confidential or regulated information.

Service discovery and coordination

Research direction: help independently operated AIAs discover whether another authorized participant can contribute to a task, then coordinate a bounded exchange.

Publicly safe outcomes include:

• describing a needed capability without disclosing the full private objective;
• establishing the policy that applies before interaction;
• recording whether a requested service was accepted and completed;
• returning a useful result with provenance appropriate to the task; and
• challenging a failed or misleading service claim.

Provider settlement and contribution rewards are not live. No current scenario should be read as a paid marketplace.

Community and civic coordination

Research direction: aggregate voluntarily contributed observations into a shared picture while limiting unnecessary exposure of individual context.

Potential scenarios include community resource coordination, accessibility reporting, local planning feedback, or incident support. These uses are particularly sensitive to exclusion, surveillance, coercion, representational bias, and misuse by authorities. They should not advance beyond controlled research without affected-community participation and independent rights review.

Health and other high-stakes domains

SENEX may study how local-first assistance can help a person prepare questions, organize records, or understand their own information. It is not presented as a medical device, clinician, diagnosis system, emergency service, financial adviser, or legal adviser.

Any high-stakes application would need:

• qualified domain oversight;
• evidence appropriate to the claimed use;
• clear human responsibility;
• conservative failure behavior;
• applicable regulatory review;
• monitoring for unequal impact; and
• a safe route to professional or emergency support.

Until those requirements are satisfied, examples remain research directions rather than product promises.

Evaluation criteria

Use cases should advance only when testing can answer:

• Does the local mode provide useful value without coerced sharing?
• Can a participant understand and revoke an authorization?
• Is the external interaction limited to its stated purpose?
• Can users distinguish evidence, inference, and uncertainty?
• Can harmful or incorrect outcomes be reported and corrected?
• Are non-participants and vulnerable groups protected?
• Does the application work accessibly across relevant devices and contexts?

For system boundaries, see Architecture. For privacy expectations, see Privacy & Security. For staged validation, see the Roadmap.