How the AI writes your store's setup safely
How a plain-language request becomes a checked, confirmed, on-the-record store setup, and why the result is no different from one a person wrote by hand.
Every store Reqursor manages has exactly one official description of what it should be: its store definition (see Core concepts). Reqursor's core bet is that this description can be written mostly by AI, safely. This page explains the steps that make that true.
From a sentence to a confirmed store setup
You describe what you want
In plain language: a brief for a new store, a request to change something, or an answer to a question the AI asked back.
The AI drafts the store's setup
It turns your words into the specific fields of a store definition: the store's design styles, page content, and settings, whatever the request touches.
Reqursor Platform checks the draft
Before you ever see it, the draft is checked against a strict set of rules: nothing broken, nothing that contradicts itself, nothing that points to a version that doesn't exist.
You preview and confirm, or adjust
You see exactly what will change. You can ask for adjustments, or approve it as is. Nothing is final yet.
Your approval puts it on the record
The confirmed draft becomes the store's official setup (what it should be from this moment on), kept on the record.
Until you confirm, it's just a draft
Before your approval, the AI's output is a proposal: it can be thrown away, and it has no power over any real store. Only your confirmation gives it authority. See How every change is checked before it goes live for what happens next.
Once it's on the record, Reqursor can't tell who wrote it
This is the important part: a setup written by the AI and one written by a person are built the same way. Same store definition, same fields, same checks. Reqursor has no "AI mode"; it treats every confirmed setup exactly the same way, regardless of how it was drafted.
That's not a courtesy: it follows from what a store's setup is. A store's setup is simply "what's on record for this store right now." The record itself doesn't say who proposed it, so there's nothing for Reqursor to treat differently even if it wanted to.
That doesn't mean we lose track of who wrote what; it just moves. Every confirmed change stays credited to whoever (or whatever) proposed it, and every change stays in the store's history where you can review it. The AI's fingerprints are on the paper trail, not on how Reqursor behaves.
Why this is the safe way to do it, not the risky one
- Checked before you see it: broken or contradictory drafts never reach the preview stage.
- You always confirm: nothing reaches a live store without your approval.
- Nothing is treated as special: a change written by the AI gets exactly the same guarantees (predictable, traceable, and undoable in one click) as any other change.
- Nothing is lost if you undo a change: every earlier version of the store's setup is kept, so you can go back to any of them.
Not every AI-written change looks the same
Building a new store, moving one over, customizing a live one, and fixing unexpected changes are all written by the AI, but they start from different triggers and get reviewed a little differently. See Six ways your store's setup gets written.
Where to go next
Six ways your store's setup gets written
The six ways a store's setup gets written, and how each one is reviewed.
How every change is checked before it goes live
What happens once a setup is on the record.
Core concepts
Definitions for store definition, desired state (the setup a store should have), and the rest.
How every change is checked before it goes live
Why you can trust AI with live stores: the line between the AI and the engine, and the three steps every change goes through.
Six ways your store's setup gets written
Building a new store, moving one over, changing a live one, fixing a problem, editing by hand, and using a template are six ways a store's setup gets written, and all are treated the same once you confirm.