Skip to content
Aurora Catalyst

Concepts

Concept pages are understanding-oriented: they explain the why behind Aurora rather than how to use it. Read these when you want to form a solid mental model.

If you want to do something, use the how-to guides. If you need exact facts, use the reference.

Topics

Section titled “Topics”

Backend

Section titled “Backend”
  • Authentication strategies — the three OAUTH_STRATEGY modes, the BFF pattern, and how tokens flow between a hub and its satellites.
  • Cross-bounded-context ports — how the @bridges folder decouples bounded contexts through ports, tokens, adapters, and a global composition root.
  • Backend module scaffolding — what the CLI generates for a backend module, and how the lockfile keeps hand edits in check.

Frontend

Section titled “Frontend”
  • Cell renderers — how the data-table dispatches by property type and how to override rendering per column.
  • Composables: atoms and presets — why brain logic splits into single-responsibility atoms and opinionated presets wired to TanStack Table.
  • Composition vs inheritance — why the brain layer extends horizontally by composing functions instead of through class hierarchies.
  • Detail mode — how front.detailMode chooses between a routed detail page and a list-with-modal CRUD.
  • Embed mode — how front.embedSupport opts a child module into being embedded inside its parent’s detail view.
  • Form field widths — how the 12-column grid, type defaults, widget.span, and the auto-expand pass decide each field’s width.
  • Preservation regions — how you own a slice of a generated file and why that slice survives regeneration.
  • Column pinning (TanStack) — why pinning a column reorders rather than moves it, and how the data-table writes both pinning and order.

Workflow & governance

Section titled “Workflow & governance”
  • Business rules system — a catalog of domain invariants beside the YAML schemas, used as institutional memory and incoherence detector.
  • Anatomy of a business rule — the fields, ID grammar, state/severity, case table, and lifecycle of a single rule.
  • Business rules system architecture — the technical pieces (index, scripts, slash commands, skill, hooks, CI, OpenSpec extension) and how they relate.
  • Development modes — Framework mode vs Solution mode, and the /dev-mode command that switches between them.
  • The four governance artifacts — Harness Rules, the architecture-checkpoint hook, and the backend/frontend project-structure skills: what blocks you, what advises you, and who owns what.