One operating system for how EraAI is built.
A daily workspace for product, design, engineering, marketing, website development, sales enablement, and platform operations.
AI Suite
Vision, positioning, audiences, capabilities, outcomes, and product relationships.
Open reference →02Platform Delivery
Deployment audiences, environments, configuration registry, and routing rules.
Open reference →03Work Stories
Concrete futures for how EraAI changes everyday organizational work.
Open reference →04Architecture
Product concepts, system boundaries, and the Flex configuration approach.
Open reference →05Requirements
Canonical shared behavior, access, shell, interaction, and delivery requirements.
Open reference →06Brandbook
Canonical visual identity, product marks, components, and interaction language.
Open reference →07Common UI Guidelines
Implementation rules for shared typography, surfaces, controls, and states.
Open reference →08Reusable Skills
Repeatable dev workflows, portable downloads, and Rebuild All orchestration.
Open reference →Where EraAI lives
FIGMA_PUBLIC_URLPlatform-provided preview originDeployment-specificInternal workspace omittedWork Stories
Use to turn product vision into concrete changes in meetings, decisions, preparation, and execution.
Architecture
Use before defining Flex discovery, configuration, modules, connectors, deployment, or data boundaries.
AI Suite
Start here when writing official-site copy, shaping a roadmap, or explaining how products fit together.
Platform Delivery
Use for deployment configuration, environment ownership, routing, and internal/customer visibility.
Requirements
Use before changing shared behavior, authentication, suite entry, shell state, or reusable interactions.
Brandbook
Use before changing identity, typography, color, product marks, common components, or visual hierarchy.
Common UI Guidelines
Use while implementing shared shell, control, state, accessibility, or responsive patterns.
Reusable Skills
Use to repeat established update, synchronization, review, and delivery processes.
More sections will live here.
Future engineering standards, release playbooks, research references, and customer-delivery guides can join the new product, story, and architecture foundations as they become canonical.