Design Decisions
Why Reqursor works the way it does: the reasoning behind decisions like no autonomous remediation and a mandatory preview-and-confirm gate.
Some of Reqursor's most important properties come from deliberate decisions, not accidents of implementation: like requiring your confirmation before any AI-proposed change goes live, even a low-risk one. This section explains the reasoning behind decisions like that: what was decided, why, and what the trade-offs were.
More on this section is coming
Individual decision write-ups, starting with the preview-and-confirm gate and the no-autonomous-remediation rule, are on the way.
Troubleshooting
What to do when a store has an unexpected change, a change fails, or something looks wrong, and what keeps running when something else breaks.
Glossary & Reference
The full A-Z reference for every term used across Reqursor's docs, an expanded companion to the introductory glossary in Core Concepts.