Internal control plane · Right&Above
Application Assembly Pipeline is how we build software here. A request in chat becomes an implementation plan a person signs off on; the app is then assembled from a registry of human-reviewed modules, and AI agents write only the parts that are genuinely new.
01 Why a pipeline
Ask a model for a SaaS and you get something that runs on the demo and frightens you in production. Three problems show up every time — the pipeline exists to remove all three.
02 The conveyor
Every stage is a saga state routed by a state machine and queued through Redis; workers execute it and stream progress back to the chat. Session state lives in PostgreSQL, so a run resumes exactly where it stopped. Four of the stages hand their output to a critic before the run is allowed to move on.
INTENT
The chat request is resolved into a concrete application intent — domain, actors, surfaces — until the stage reports itself ready.
criticINTENT_REVIEWlight
DISCOVERY
The registry is searched for trusted modules that already cover parts of the intent. The critic verifies every candidate against the real registry, so nothing imaginary survives into the plan.
criticDISCOVERY_REVIEWlight
MODULE_SELECTION ◆ waits for a person
A wizard: you tick which discovered modules to wire in and fill each one's required variables, screen by screen. Config is encrypted per session and module before it is stored. The saga does not auto-advance — it sits here until you submit.
PLANNING
The plan is drafted around the fixed module set, not around what the model feels like reusing. The policy critic then checks it — deterministic rules plus an LLM pass; on a failing verdict planning is re-run with the critic's feedback until it clears.
criticPLAN_POLICYstandard · blocks
PLAN_APPROVAL ◆ waits for a person
The last stop before anything is written. A human reads the implementation guide and approves or rejects it.
CODE_GENERATION
Not one big generation call — a scaffold, a decomposition into tasks, then a tight per-task loop of write and review.
git init, write the agent briefing, commit the scaffold.RELEASE
Three deterministic sub-steps — RELEASE_BUILD, RELEASE_DEPLOY,
RELEASE_PROBE: a clean rebuild, a push into the runtime, then a health probe
against the deployed app. If the clean rebuild fails, the run bounces back once into
code generation with a release-fix task instead of shipping.
you A fullstack app with signup, login, sign-out and password reset. React front end, Nest API, cookie sessions.
forRoot() on the Nest side, host adapters for
the user store and hashing, headless hooks on the front end./, exercise
signup, login, sign-out and reset against the API at /api, with cookie
persistence across reloads.
03 Trusted Modules Registry
Sign-in, payments, subscriptions, transactional mail and shared domain logic live in a registry as reviewed, versioned modules. The pipeline reaches for these first, and only generates what is genuinely new.
core, nest, reactEach module carries a machine-readable briefing for the agent that installs it, and a checker enforces package boundaries, naming and secret handling before anything can be published.
MODULE_ID — DI tokens,
route prefix, Redux slice, event names. Two modules physically cannot collide on a
symbol space.
core may not import NestJS or React; react may not import
a UI library. The check runs before publish, so an app can restyle a module without
forking it.
04 Built on
Nothing exotic in the stack — so the applications it produces can be handed to in-house developers without a migration project first.
The pipeline is internal to Right&Above — we run it, you get the application. Talk to us about what you'd put through it.