Ω Omega Architecture

Reactive, agent-based architecture for Flutter
One channel · typed intents · flows · agents · CLI · inspector · traces

   

Intro · Why Omega · Quick start · Mental model · CLI · Links

---

Introduction

What is Omega?

Omega Architecture is a Dart / Flutter package plus a omega CLI that organizes your app around a few clear ideas: a single OmegaChannel for events, flows that orchestrate use cases, agents that run side effects and domain logic, and a thin UI that sends intents and reacts to flow expressions — instead of growing a tangle of setState, callbacks, and hidden dependencies across widgets.

Why use it?

• Easier to reason about — business rules live in flows and agents; screens stay declarative.
• Safer evolution — typed intent/event names, optional contracts in debug, and omega validate catch wiring mistakes before they ship.
• Better debugging — inspector (overlay, dialog, or browser + VM Service), time-travel sessions, and traces so you see what happened and in what order.
• Less boilerplate — omega g ecosystem, project templates, and an optional AI coach for scaffolding.

This README is only a summary. Go to the documentation for install steps, diagrams, every guide, and the learning path:

Documentation site →
_{Suggested path: Getting started · Core concepts · Data flow}

---

Why Omega

You want	You get
UI that does not drown in logic	Intents in, expressions out — widgets stay declarative
One nervous system for the app	OmegaChannel — events everyone hears
Confidence when the app grows	Typed names, optional contracts, omega validate
To see what the app is doing	Inspector (in-app, tab, or browser + VM Service) + time-travel
New features without boilerplate fatigue	omega g ecosystem + optional AI coach

---

Start in one minute

dart pub global activate omega_architecture
omega create app my_app && cd my_app && flutter run

Add Pub’s global bin to your PATH (Windows: %LOCALAPPDATA%\Pub\Cache\bin). If omega is not found, use the CLI guide (PATH, dart run omega_architecture:omega …).

Existing app: add omega_architecture to pubspec.yaml, then from the app root:

dart run omega_architecture:omega init

---

What it feels like

The UI states what it wants (intent). Flows coordinate. Agents react through a behavior engine. The channel carries events; navigation and state show up as predictable streams — not setState spaghetti across the tree.

OmegaScope(
  channel: channel,
  flowManager: flowManager,
  child: const MyApp(),
);

More depth: Documentation · API reference

---

CLI at a glance

Command	What it does
omega create app	New Flutter app with Omega wired in
omega init	Drop Omega into an existing app
omega g ecosystem <Name>	Flow + agent + behavior + page
omega validate / doctor	Catch wiring mistakes early
omega inspector	VM Service → inspect in the browser
omega ai coach …	Optional — scaffold or evolve modules (env + API keys)

Full reference: CLI guide

---

Where to look next

Web docs	Guides, architecture map, CLI, inspector
CLI	All omega and omega ai commands
Inspector	Overlay, launcher, VM / browser
example/	Auth reference — cd example && flutter run

---

Package layout

lib/omega/                 → channel, intents, events, agents, flows, ui, bootstrap
lib/omega_architecture.dart → public barrel export

---

License

MIT