Core Concepts

Core concepts & glossary

The key words behind Reqursor Platform, explained in plain language.

This page defines the words you'll see throughout Reqursor Platform. You don't need a technical background: each term has a plain-language definition.

The basics

TermWhat it means
StoreA single online shop that Reqursor Platform builds and runs for you. Each store runs in its own separate environment, so one store's problem never affects another.
AgencyYour organization, the customer of Reqursor Platform. Everything you create belongs to your agency and is walled off from other agencies. (Technical docs may also call this a tenant.)
All your storesYour whole collection of stores, managed together. You can make the same change across many stores at once instead of one by one.
Store platform connectorThe part of Reqursor Platform that teaches it how to run one particular kind of store platform. Reqursor Platform supports one store platform today; support for more is planned.
Dashboard & AssistantHow you interact with Reqursor Platform: a visual dashboard and a conversational assistant you can ask, in plain language, to build, change, or explain your stores.

Declaring what you want

TermWhat it means
Store definitionThe complete description of what a store should be: its design, pages, settings, and features. It is the one official description of that store.
Intended setupWhat you've said the store should look like (the store definition).
Current setupWhat the store actually looks like right now, as measured by Reqursor Platform. Keeping the current setup matching the intended setup is the job of the part that makes changes.
Preview-and-confirmThe step between a proposal and a real change. Reqursor Platform always shows you what will change and waits for your approval before touching a live store.

How changes are made and stores stay healthy

TermWhat it means
Reliable change systemThe part of Reqursor Platform that carries out changes. Every change is checked before it goes live, and the same request always gives the same result: predictable and repeatable.
The approval lineThe dividing line between the AI's proposals (above) and guaranteed results (below). It is the recorded, approved change.
Plan, change, checkThe three steps of every change: work out what will happen, do it, then check that the result matches what you approved.
In syncA store that has successfully reached the setup you approved. An in-sync store matches its definition.
Unexpected changeWhen a store's actual setup no longer matches what was approved, for example, a setting changed by hand. Reqursor Platform spots unexpected changes automatically and sorts them by type.
UndoGoing back to the last version that worked, in one click, by putting the store's earlier setup back. It restores the store's setup, not business data: orders and customers stay untouched.
Safe to repeatA safety property: applying the same change twice has the same effect as applying it once. Running it again never causes damage.

Separate stores and safety

TermWhat it means
Separate environmentsEvery store runs in its own separate environment: its own network, storage, and computing power. Stores can't interfere with each other. This is built into how they are set up, not just a promise.
Wall between agenciesThe boundary that keeps each agency's work apart. One agency can never see or affect another agency's stores or data.
SecretSensitive information (like passwords or access keys for other services) a store needs. Reqursor Platform stores secrets separately and refers to them only by a safe reference; they're never exposed to the AI, activity records, or the saved history of your store's setup.
Locked versionsEvery building block a store uses is locked to one exact, checked version, so setting up a store works the same way every time and nothing changes underneath you unexpectedly.

Want the deeper story?

See How every change is checked before it goes live for how these pieces work together to make AI safe for live stores.