Library

Library is Atoi's signed-in root. It gives you a useful orientation before you configure a project or invent an organization system.

#Read the lead row first

The first ranked item represents the clearest next move: work that needs your decision, an Atoi proposal, or onboarding when the product still lacks useful context. It is a single lead, not a dashboard of competing alerts.

Open the item to inspect its source and act. Dismiss or refine it when the ranking is wrong; the correction is more useful than rearranging a manual board.

#Browse generated collections

Below the lead, Library can organize reusable item types into generated collections. Examples include projects, documents, conversations, scheduled work, and connected context. The exact mix depends on what exists for the current user.

These collections are views over durable records. Moving through Library does not copy a conversation or turn a document into a new object. A generated tile should remain useful before configuration and become sharper as more context is connected.

#Open focused work

Library items open in focused dialogs, tabs, or the shared context panel. Use the smallest surface that preserves the relevant context:

• a conversation opens with its transcript;
• a project opens its current project surface;
• a document opens as a document;
• accountable work opens with its state and receipt;
• a connection or computer opens its own control surface.

The product avoids a permanent roster or room sidebar. Atoi can summon a capability through the composer, a card, or a shortcut without making internal topology the main navigation.

#Ask Atoi

Use Ask Atoi or Command-K to summon the composer. Describe an outcome, optionally choose context, and send. The composer is summoned when needed rather than occupying the bottom of Library at all times.

#Adjust by asking

If Library overweights the wrong material, tell Atoi what should matter. Prefer statements such as “keep release blockers above reading suggestions” over creating and maintaining a new board hierarchy.

Library should remain generated but not mysterious: each useful item needs an intelligible title, source, status, and action. See Memory and personalization for how durable preferences should remain reviewable.