Skip to content

Latest commit

 

History

History
91 lines (69 loc) · 3.2 KB

File metadata and controls

91 lines (69 loc) · 3.2 KB

Lara Architect UI — Product Roadmap

Product: Lara Architect UI is the Architecture Companion — a developer operating system beside the IDE.
It is not an engine demo and not a pile of Workspace pages.

Core discovers.
UI explains.
Developers decide.

Product shift

Each screen answers exactly one question. Navigation is a Companion OS, not a metrics dashboard.

Nav Question
Home What should I do now?
Issues What is wrong, where, and why?
Actions What can Lara Architect do for me?
Knowledge What does the system remember / believe?
History What happened over time?
Settings How is the Companion configured?
Architect Companion
├── Home
├── Issues
├── Actions
├── Knowledge      ← Memory · Standards · Learning · Ask · Conversations
├── History
└── Settings

Later (not primary Home): Project Explorer · Global Search · calm Notifications · Legacy Cleanup · architect:install.

Two orders (do not confuse them)

Layer Order Role
Engine (core) Analyzer → Evidence → Memory → Intelligence → Guidance Truth, contracts
UI (companion) Understand → Recommend → Preview → Resolve → Verify → Remember Daily developer flow

Memory / Intelligence / Guidance power Knowledge and Home recommendations. They are not the primary IA.

Differentiator: Developer Sessions

Start Improvement creates a focused session (goal, files, checklist, verify, finish → History).
That turns architecture work into a guided workflow — not disconnected actions.

Primary loop

Home / Issues
   → Start Improvement (Session)
   → Preview
   → Resolve
   → Verify
   → History

Version plan

Version Goal Outcome
UI 0.2 Companion OS shell Sidebar, Home (what next?), Issues / Actions / Knowledge / History / Settings rehomed
UI 0.3 Issue Center Code highlight, alternatives, Resolve / Ignore / Open file
UI 0.4 Action Center Safe / Assisted / Design first-class
UI 0.5 Legacy Cleanup Week plans + progress for large debt
UI 0.6 Project Explorer + deep Knowledge Module-centric navigation
UI 1.0 Complete Companion Sessions polish, architect:install, search, calm notifications

UI 0.2 acceptance

  • Brand experience as Architecture Companion (Workspace = engine surface / legacy path)
  • Persistent sidebar: Home, Issues, Actions, Knowledge, History, Settings
  • Home answers “what next?” with one recommended Start (+ Resume when available)
  • /architect/workspace redirects to Companion Home
  • UI still consumes core only — no analysis invented in React

Hard rules

  1. One-way dependency: UI → core.
  2. No invented architecture in the UI package.
  3. One question per screen.
  4. Safe / Assisted / Design policy still comes from core contracts.

Related