EraAIInternal
EraAI Developer Hub

One operating system for how EraAI is built.

A daily workspace for product, design, engineering, marketing, website development, sales enablement, and platform operations.

01

AI Suite

Vision, positioning, audiences, capabilities, outcomes, and product relationships.

Open reference →
02

Platform Delivery

Deployment audiences, environments, configuration registry, and routing rules.

Open reference →
03

Work Stories

Concrete futures for how EraAI changes everyday organizational work.

Open reference →
04

Architecture

Product concepts, system boundaries, and the Flex configuration approach.

Open reference →
05

Requirements

Canonical shared behavior, access, shell, interaction, and delivery requirements.

Open reference →
06

Brandbook

Canonical visual identity, product marks, components, and interaction language.

Open reference →
07

Common UI Guidelines

Implementation rules for shared typography, surfaces, controls, and states.

Open reference →
08

Reusable Skills

Repeatable dev workflows, portable downloads, and Rebuild All orchestration.

Open reference →
Environments

Where EraAI lives

Full registry →
Official sitehttps://eralabs.org/Public corporate presence
Product developmenthttps://ai.eralabs.org/Current suite environment
Make previewFIGMA_PUBLIC_URLPlatform-provided preview origin
Customer deploymentDeployment-specificInternal workspace omitted
Today’s references

Work 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.

Workspace roadmap

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.