Skip to main content

Applications

An application is a whole system your agent builds on Plexara: a transactional database of its own, the automations that do the work, the forms and endpoints people and partner systems use, and the pages people open. An administrator releases it as one pinned set, so what runs is exactly what was released, and one step puts the previous release back. The 900 series builds a shop on the demo tenant: catalog, checkout, stock, order confirmation and storefront.

10 min
Architecture

901 - What an application is

An application is a whole system built on Plexara and held as one record: a database schema, the automations that do the work, the forms and endpoints people and systems use, the events that drive it, and the pages people see. The agent builds the parts, an administrator releases them as one pinned set, and the record answers what the system is made of, what runs, and who decided.

Read
12 min
Architecture

902 - A database of its own

An application database is a transactional PostgreSQL schema the application owns: constraints the database enforces, row-level security keyed on the caller, and a role only the application’s own automations log in as. Every table is a migration the agent writes, the platform reviews, plans against a rolled-back transaction, and proves from zero on a throwaway database before it saves.

Read
13 min
Product

903 - The work: automations, forms and endpoints

The parts that do an application’s work. A checkout form that places an order, its lines and its stock decrements in one transaction; an API whose order query needs no filter because the database adds it; a confirmation that runs once per order as an event; scheduled upkeep; and tests that run each automation against a real copy of the database.

Read
11 min
Governance

904 - Releases: what runs is what was released

A release applies the pending migrations and pins every automation and asset at a version. From then on the endpoints, forms, schedules and event runs execute the pinned versions, and a save changes nothing live until the next release. What a release records, what it refuses, who may make one, and why this boundary is what lets agent-written software run unattended.

Read
10 min
Governance

905 - Rollback and the diagram

A rollback restores an earlier release’s pins in one step and records itself as a new release, reverting the migrations applied since when each one can be reverted. The diagram draws how the parts fit together from the parts themselves, compares any two releases, and reports findings before they reach production, so the picture of the system is always the system.

Read
11 min
Product

906 - Pages people open

An application answers a browser at an address of its own: a page endpoint, static files pinned by the release, the application’s endpoints, and a record of who is signed in. Who may open each page, how a viewer signs in, how a page’s script is held to its own origin, how a public storefront and a portal report reach the application, and how one environment of a site becomes a part the release moves.

Read
12 min
Product

907 - Capstone: the shop, end to end

One request, one application. The shop assembled in the order an agent builds it: the record and its schema, five migrations, a checkout, an API, a confirmation event, nightly upkeep, a storefront, and the first release. Then a change, a second release, and a rollback, with what the administrator reads at each step.

Read