Skip to content

WORK_AI_NATIVE_HOME.md

Latest commit

 

History

History
107 lines (86 loc) · 4.81 KB

WORK_AI_NATIVE_HOME.md

File metadata and controls

107 lines (86 loc) · 4.81 KB
Raw

A3S Work AI-Native Home

Product intent

A3S Web opens its canonical #home route with the user's intended outcome, not with a file grid or a product chooser. The home surface therefore makes the durable A3S task composer the primary entry point while retaining templates, folders, and recent files as supporting content below it.

The interaction model is informed by task-first productivity products such as Skywork, but the visual treatment, execution controls, local-workspace model, and safety contract remain native to A3S.

Information architecture

The Work home is ordered as follows:

  1. A3S Work identity and a concise outcome-oriented promise.
  2. The complete task composer, including execution mode, model, effort, file references, Skills, drag-and-drop context, and the real queue submission path.
  3. One-click capabilities that map only to implemented actions: create text, spreadsheet, or presentation artifacts; open a file; prepare data-analysis or file-organization tasks; and open the local-files workspace.
  4. Managed templates, folders, and recent files for direct manipulation.

Recent, Favorites, Trash, and managed-folder views remain file-management surfaces. They do not repeat the home hero.

Interaction contract

  • A fresh A3S Web installation opens the AI home. An explicit previous choice to use the local-files surface is still restored.
  • The right-side AI Assistant is closed by default. It opens when the user submits a home task, so the initial canvas is not needlessly compressed.
  • The home composer and the assistant use the same task draft and durable runtime. Keyboard submission and the send button follow the same path.
  • Home, files, Office editing, and code editing are scenes in one Work product. They share one conversation list, active session, draft, context, queue, and default agent. Scene changes never create or restore a second hidden session.
  • Asynchronous session creation is correlated with the draft that initiated it, so a late response cannot replace a conversation the user selected while the request was in flight.
  • Prompt starters populate an editable draft; they never auto-send.
  • Creating an Office artifact, opening a file, or entering the local workspace stays a direct operation rather than becoming an artificial chat step.
  • Potentially destructive file organization remains plan-first and must use the existing reviewed file-operation boundaries.

Delivery plan

Phase 1 — Task-first home

Implemented in the first release:

  • AI-native hero and full task composer.
  • Real capability shortcuts with no placeholder media features.
  • Task-submit-to-assistant transition.
  • Default home and collapsed-assistant behavior.
  • Existing templates and file library preserved below the task entry.
  • Responsive layouts for a narrow Work pane and a 360 px viewport, plus dark theme support and keyboard-accessible controls.

Phase 2 — Personalized starting points

  • Rank task starters from recent Work outcomes without exposing file content.
  • Add resumable recent tasks and generated-output previews beside recent files.
  • Provide a searchable Skill catalog launched from the composer while keeping / as the keyboard path.
  • Add format-aware starters when the current workspace contains spreadsheets, presentations, or document collections.

Phase 3 — Proactive Work orchestration

  • Allow reviewed task recipes to be saved and scheduled.
  • Surface workspace-change suggestions without auto-running destructive work.
  • Hand completed Work outputs to Knowledge as explicit source packages, keeping knowledge-base creation and compilation as separate operations.
  • Add outcome and recovery telemetry that is local by default and opt-in for aggregate product analytics.

Success measures

  • Median time from opening Work to the first submitted task.
  • Share of home sessions that start a task, open an existing file, or create an artifact without navigation detours.
  • Task submission failure and recovery rate.
  • Assistant close/reopen rate after home submission.
  • Keyboard completion and narrow-pane overflow regressions.

Release acceptance

  • The home composer submits through the production unified task controller.
  • @ file references, / Skills, execution mode, model, and effort remain available.
  • Starting a task opens the AI Assistant exactly once.
  • Switching among home, files, Office, and code scenes preserves the same session ID and draft, including when session creation completes in flight.
  • #home is the only Work route; removed product-prefixed routes are not retained.
  • Non-home library views retain direct file-management behavior.
  • The page has no horizontal overflow at 360 px and remains legible in light and dark themes.
  • Focused component tests, type checking, lint, formatting, production build, and browser regression all pass.