UI & functional requirements · v1
Shared rules for a coherent suite.
This reference captures major product behavior, interaction language, and reusable functional expectations for future development cycles and agents.
01
Product scope
The current service is EraAI Cloud. Desktop is a separate future delivery target.
- 01Treat EraAI as one product suite with shared identity, branding, navigation conventions, and account context.
- 02The customer-facing suite currently contains Flex, Agent Studio, Cowork, Insight, and Control.
- 03Admin Console is an internal laboratory for development and operations teams, not a commercial suite product.
- 04Do not infer desktop behavior from cloud requirements. Desktop requirements will be specified separately.
02
Identity and access
Authentication is suite-wide; authorization comes from the user’s organization.
- 01Use one login entry for the entire suite rather than product-specific login screens.
- 02Offer Google, email, SAML SSO, and passkey as the four authentication entry methods.
- 03An organization determines which products a user can open. Commercial packaging may be separate or bundled and must not be hard-coded into UI logic.
- 04Show products without access for orientation, but label them clearly and never imply that a click will open an unavailable service.
- 05After authentication, continue to the product the user originally selected. Admin Console opens directly; other products also open directly until an organization intro/switcher flow is defined.
- 06Logging out from any product clears the shared suite session and returns directly to the EraAI Cloud home page. Every product account menu, including Admin Console, exposes this action consistently.
03
Suite entry
The home page is the common cloud doorway and product map.
- 01Show all five suite products plus the internal Admin Console laboratory.
- 02Preserve the atmospheric mint, lavender, and sand canvas with restrained glass surfaces and enterprise-grade hierarchy.
- 03Keep product availability visible as Included, Not included, or Internal rather than relying on color alone.
- 04Unauthenticated product selection opens login with the intended destination preserved.
- 05Authenticated product selection opens the selected product without an extra marketing or confirmation step.
- 06The suite home provides a browser-local light/dark theme control and restores the latest preference on return.
- 07Internal builds consolidate Developer Hub, suite references, Official Site, and Product Environment in one quiet workspace section without a duplicate footer utility strip.
- 08The internal workspace is hidden on first launch. Its latest browser-local state is always restored; when hidden, Developer Portal and Show internal actions appear together in the header.
- 09Suite product cards unfold from large product marks on entry; descriptions reveal on hover or keyboard focus without changing card or page geometry, with a stable reduced-motion fallback.
- 10Customer builds omit the complete internal workspace section.
04
Interaction language
Interfaces should be direct, predictable, and explicit about system state.
- 01Use short action labels and factual, action-oriented assistant language.
- 02Every visible control must respond, navigate, expand, submit, or communicate why it is unavailable.
- 03Use neutral actions by default. Reserve teal for focus, active state, governance, success, and live status.
- 04Keep status paired with text, not color alone. Preserve visible keyboard focus and accessible names.
- 05Use progressive disclosure for advanced controls; do not hide required context or consequences.
05
Common product patterns
Products share foundations while retaining domain-specific workflows.
- 01Use the shared 52px transparent header rail, suite switcher, profile menu, resizable panels, and shared chat where applicable.
- 02The EraAI logo in every shared product switcher returns directly to the EraAI Cloud home page.
- 03Pinned and Recent are collapsible entity groups; saved chat rows restore their latest conversation and the chat panel.
- 04Operational pages preserve source-specific tabs, graphs, timelines, query builders, previews, simulations, and inspectors.
- 05Dense interfaces use 13–14px operational body text, thin borders, restrained surfaces, and compact controls.
- 06Do not flatten specialized workflows into generic cards or tables merely to make products look alike.
- 07Chat is closed on first entry. The sidebar starts open at 220px, chat width starts at 360px, and the light theme is active.
- 08After interaction, restore browser-local shell state and the last supported Cowork, Agent Studio, or Admin Console location.
- 09Product switching resumes the target product. Logout preserves workspace preferences while clearing demo authentication.
- 10Local workspace continuity does not sync between browsers or devices and never stores drafts, secrets, transient dialogs, or sensitive data.
06
Deployment audience
Internal and customer builds expose different supporting services.
- 01ERA_DEPLOYMENT_AUDIENCE accepts internal or customer and defaults to internal.
- 02Internal builds expose Developer Hub, Requirements, Brandbook, Admin Console, and startup-team utilities.
- 03Customer builds omit internal navigation and placeholders while retaining the entitled commercial suite.
- 04Deployment audience is presentation control, not authentication, authorization, or entitlement enforcement.
- 05The Developer Hub uses a three-level navigation model: Product, Developers, Market, and Resources at level one; labeled domain groups at level two; and destination pages at level three.
- 06The shared Developer Hub shell persists across every internal reference route so the complete startup workspace remains directly switchable.
- 07One browser-local Developer Hub light/dark preference applies across the complete workspace and is restored after navigation or reload; Brandbook inherits this preference instead of maintaining a separate theme control.
07
Delivery and maintenance
Requirements are a durable engineering input, not a one-time design note.
- 01Record new major, shared, or reusable functional requirements in this reference during the same change.
- 02Keep brand rules in the brandbook and behavioral/product rules here; cross-reference when a decision affects both.
- 03Distinguish demos from production behavior in both UI and documentation.
- 04Do not present future integrations as active. Surface configuration, entitlement, and provider dependencies explicitly.
- 05Validate requested public routes in preview and production delivery before marking work complete.