# Exploring

These ideas aren't built yet. Designs may change, and an item may be dropped. See [how to read the roadmap](./index.md).

## Applications on a shared platform

We're separating OnEarly into two layers, so new experiences can be added without reworking the foundations.

- **The platform** is what every part of OnEarly shares: how content is stored and versioned, permissions and sharing, notifications, the API, and the app's navigation and building blocks.
- **Applications** are the experiences built for particular kinds of content, such as conversations, test ordering or booking. An application owns its content types and the screens and logic made for them.

Applications build on the platform, never the other way around. Some applications run inside OnEarly. Others are separate products that connect after you sign in and give consent.

Diagram: [Applications on a shared platform](https://docs.onearly.com/diagrams/roadmap-exploring.html)

Each application would describe itself to the platform in the same way:

| Part | What the application declares |
|---|---|
| Identity | Its name, who publishes it, and whether it runs inside OnEarly or as a separate product. |
| Content types | The kinds of content it owns. |
| Surfaces | How its content appears as a pill, card and page, for viewing, editing and creating. |
| Actions | The named things you can do with its content, the details each one needs, and the permission it requires. |
| Lifecycle | The states its content moves through and the rules between them, kept as data. |
| Notifications | A message for each event. OnEarly decides who receives it and respects their preferences. |
| Required access | Who needs to keep access, and for how long, while a piece of work is open. |

**Status:** Exploring

The features below are part of applications. They arrive with applications rather than on their own, and share their status.

### Pills, cards and pages

Every piece of content would look and behave consistently wherever it appears.

- A **pill** is a compact, inline mention, for example inside a message.
- A **card** is a summary, for example in a list or a conversation.
- A **page** is the full view.

Each surface comes in three modes: view, edit and create. If an application doesn't provide one, OnEarly shows a standard version, so content always has somewhere to appear.

### Switch applications on for your group

Group admins would choose which applications their group uses.

- A group admin switches an application on for the group and sets its defaults.
- These choices are saved as content in OnEarly, so they're recorded and shared like everything else.
- When OnEarly shows a piece of content, it uses the choice made on that item first, then the group's default, then the application that owns the content type, and finally the standard view.

### Scoped access for connected apps

Apps you connect to OnEarly would ask only for the access they need, and every change they make would show which app made it.

- An app asks for specific access rather than broad access to your account.
- The history of every change records the app that made it and who it acted for.

### Disconnect one app at a time

You would be able to disconnect any single app without affecting the others, and without breaking work that's still underway.

- Disconnecting one app removes only that app's access.
- Apps that keep working in the background, rather than only while you use them, declare the access they need to finish open work, such as a test request in progress.
- OnEarly refuses a removal that would break open work.

### Agent tools from application actions

The OnEarly Agent would be able to help with anything an application lets you do, under the same rules as you.

- Each action an application declares, with the details it needs and the permission it requires, becomes available in the app and as a tool the OnEarly Agent can use.
- The same permission checks apply however an action is taken, and every use is recorded in the history.

## Calendar view

See dated content, such as appointments and bookings, laid out on a calendar, alongside the table and list views.

**Status:** Exploring

## Connectors across your groups

Connectors would fit the way you belong to several groups, such as a family, a care team and an employer.

- Each account is used only where it belongs, and only by the people it's meant for.
- What the OnEarly Agent learns from an account is shared no more widely than the account itself.

**Status:** Exploring

The features below are part of connectors across your groups, and share its status.

### Member-scoped connectors

You would be able to add a connector that belongs to you only as a member of one group, such as your work mailbox in a Work group.

- Only you can see it, and it's used only in threads started in that group.
- It's retired automatically when your membership of the group ends.
- Changes made through it are recorded as you within that group (`GROUP_MEMBER`).

### Admins see which connectors members added

Group admins would be able to see which member-scoped connectors exist in their group, for example to check them when someone leaves.

- Admins see that a connector exists, but can't use it or read anything through it.

### Suggestions from connected accounts

An agent would read what a connector brings in and suggest content from it, such as contacts from the people who email you, appointments from calendar invitations, and organisations from email domains.

- A suggestion belongs where its connector does: to you, to you within a group, or to the group.
- It's made by the agent acting there, and shared no more widely than the connector.
- A group admin can switch suggestions off for the group.

Which agent makes the suggestions would follow the connector:

| Connector | Agent that makes the suggestions | Who can see them |
|---|---|---|
| Personal | Your agent | You |
| Member-scoped | Your agent, acting as a member of that group (`GROUP_MEMBER`) | You, within that group |
| Group | An agent of the group's own | The people who can use the connector |

### Confirm or discard suggestions

You would decide which suggestions are kept as fact.

- Suggested content carries `SUGGESTED` certainty on its links.
- You can confirm a suggestion, which makes it `ASSERTED`, or discard it.
- A suggestion nobody has confirmed never becomes the basis for another suggestion presented as fact.

### One record when two connectors see the same item

When two connectors bring in the same item, such as a calendar connected both by you and by your group, OnEarly would keep one record of it.

- Items match when they have the same external account and the same item ID.
- The agent for the more specific connector creates the record: the group's own agent for a group connector, or your agent as a member for a member-scoped one.
- Your own agent links to that record rather than copying it.

### Reasoning across your groups

Your own agent would spot things that cross the groups you can see, and tell only you.

- For example, a calendar clash between work and family, the same person appearing in two groups, or travel that overlaps a care appointment.
- These flags are your own content, and are never written back into a group.
- A flag refers to the records behind it with carbon copy turned off, so sharing the flag doesn't reveal them.

## Content types that evolve safely

Content types would be able to change over time without leaving older records behind.

- A content type, the template that describes a kind of record, is itself content in OnEarly, and each change to it is saved as a new version.
- A type moves through clear states: draft while it's being designed, published when it's ready to use, and deprecated when it shouldn't be used for new content.
- When a type changes, existing records can move to the newer version, so information stays consistent without losing its history.

**Status:** Exploring

## Group billing and payouts

Group admins would manage the group's billing and payouts from the **Finance** section of group settings.

**Status:** Exploring

## Referral and results documents on requests

The referral and your results would appear on a pathology request's page, alongside the steps that produced them.

**Status:** Exploring

Source: https://docs.onearly.com/roadmap/exploring/
