What each module may do, and what stops it.

• Outside autopilot, the proposal waits for your approval.
• Approval follows the store's autonomy setting. Campaigns have no separate switch.

• Archiving a bol ad item asks you to confirm first, because bol does not re-enable an archived item.

• With the store's kill switch on, the policy gate refuses the agent's writes.

• Campaign status writes are limited to active and paused. Removing a campaign is not one of them.
• A daily budget under EUR 1.00 is refused. It is not quietly raised to the minimum.
• StackAdapt is connect-only. Magistry reads it and does not write to it.

• Irreversible actions always wait for you, whatever the autopilot settings say.
• A capability you switched off is never auto-run. The Brain still proposes it for your approval.

• Automatic rollback of losing ad moves runs only with autopilot on and its own switch turned on.
• Rollback from the decision log is offered only on Google Ads and promotion moves.
• A rollback is refused when another writer now holds that setting. It never overwrites a later writer.

• Each proposed move passes the policy gate first. The kill switch, the module's own switch and dry-run mode are checked before anything runs.
• Until you choose a mode, the Brain runs in dry run: it records what it would do and changes nothing in your ad accounts.
• Pick the Brain's mode: off, approval only, dry run, or autopilot.

Its limits are listed in the columns before this one.

• The irreversible phases of a feed migration wait for proven offer parity and your explicit confirmation.
• A run that would delete a large share of the feed is held. Only a person's force push clears the hold; scheduled pushes cannot.

• Two phases of a feed migration cannot be undone: the takeover push, and deleting the old feed app's data source.

• Pushing to Google Merchant Center stays off until you turn it on for the store.
• Pause feed pushes on their own. Sync, classification and decisions keep running.

• Automatic fixes cover only the issue types on a fixed list, such as a missing description, brand, colour, gender or age group.
• Meta, Pinterest and TikTok catalog feeds are built but not yet pushing in production.

• Only a member with write access to the store can turn tracking on or off.

• A refund reaches Google Ads only as an adjustment to the purchase conversion already sent, only while refund adjustments are on, and only if that purchase reached Google first.

• Turn server-side tracking on or off per store.

• Profit mode only turns itself on when at least 80% of recent orders have cost coverage, and not after you set the mode yourself.
• An order with zero match quality is not sent.
• Server-side conversions to Meta, TikTok and Reddit are built but not yet sending in production.

• A design can also be proposed as an ad on a Google Ads Performance Max or Meta campaign. It waits on the ads page, and the existing ad push carries it once approved.
• Social auto-publish is off by default, so a design proposed as a post waits in the review queue until someone approves it.

• A design published as a social post is final. Publishing cannot be undone from the post's page, and an Instagram caption cannot be edited afterwards.

• On a store set to approval only, a design the Marketing Brain commissions shows as a card a person approves. Switching social off in the Brain's areas stops it commissioning designs.

• The capability matrix lists the loop of generate, place, measure and iterate as beta: parts have shipped, and there are no placement results yet.
• Its design document is a plan. Only the parts it marks done are built, such as campaign sets, the claim check, organic results per design and comments.
• Studio designs go to Google Ads and Meta campaigns only. On Google, only a Performance Max campaign takes them.
• Google Ads takes images from the engine but not video, because uploading to YouTube is not connected yet.
• The paid readback is built but not yet proven on a live studio ad. It starts reporting with the first design that runs in a campaign.
• It does not pause a losing ad or scale a winning one on its own. That step is still in the plan.

• A Catalog Agent move with confidence below 0.85 is not executed. It waits for a person to review it.

• A price or catalog change that was applied can be reverted from its row in the decision log.
• A discount test runs for 14 days and is then reverted to the original price.
• While the kill switch is on, reverts wait too. A store-wide pause stops both the change and its undo.

• Each kind of store change has its own switch in Settings: drafting underperformers, copy rewrites, discount tests and seasonal revival. Every one of these write switches starts off.
• While the kill switch is on, the action executor writes nothing to Shopify.

• A discount test never prices a variant below 1.8 times its cost.
• A single Catalog Agent price move is capped at 30% in either direction. Anything larger is refused.
• The Catalog Agent will not archive a product with more than 50 units in stock. It has to run a clearance first.

• The edit comes back as a diff for you to review. Deploying it is a separate step that you take.
• A Studio change reaches your store only when someone with write access to the store approves and deploys it.

• You can schedule a validated change for a later moment, and give it an end time after which the pre-deploy snapshot is restored.
• A deploy can be rolled back by restoring its snapshot from the Theme page.
• A rollback restores only the files its snapshot captured and touches nothing outside them.

• A scheduled change can be cancelled before it runs. It goes back to a proposed change.

• It never writes checkout or payment templates. Those paths are blocked before a deploy.
• The Studio AI can read and edit theme files and generate images. It cannot run shell commands or browse the web.
• If your theme was edited outside Magistry after the change was prepared, the deploy is refused and the change has to be made again.
• Deploying needs the store's theme repository to be set up first, from the Theme tab.

• Before any fix runs, Magistry reads what you allow per category and drops or holds every action you did not allow.
• Storefront copy categories start on propose, so a text change waits for your approval unless you change that.
• If your settings cannot be read, every category is treated as propose. An unreadable setting is never taken as permission to write.

• Accessibility fixes in the theme are validated with the same checks Theme Studio uses and written as a theme edit, so they go through its snapshot and rollback.
• You can undo one live compliance copy edit, or all of them on the store, which puts your original text back.
• Only a compliance change that is live can be undone from the Compliance controls page.
• It accepts pending Merchant Center terms only when the legal category is on auto and you have given that consent. An accepted term is not withdrawn afterwards.

• Per category, such as footer copy, product data, prices or policy pages, you choose auto, propose or off on the Compliance controls page.
• Withdrawing struck-through prices that break the 30-day rule is your own switch. It is off until you turn it on, and you see the count first.

• No AI writes Liquid in a compliance theme fix. Each fix is a fixed, rule-based change to the markup.
• The 30-day reference price check applies only to stores selling into the EU or EEA.

• You choose how matches are made: linked automatically, linked above a confidence threshold with the rest sent to review, or every match reviewed.

• A price cut it causes is filed as a discount test in the decision log, so it can be reverted from that row, which puts the original price back.

• One switch turns competitor tracking off for the store. It is on by default, and every crawl, match, monitor, pricing, discovery and ad check reads it first.

• It reads public storefront data only. It never logs in to a competitor's store.
• A store that turns off its public product feed cannot be crawled this way and is skipped.
• Ad tracking covers Meta only, through the Meta Ad Library, and needs a Meta access token. Without one it does nothing.
• A competitor-driven price move only ever lowers a price, only on an active product, and only in semi-autonomous or autonomous mode.
• Paid search for discovery is capped per run, because each search costs money.

• Everything the score cannot settle waits for you on the Candidates page, where you approve or reject it.
• While creating products is off, a high-scoring candidate is parked for your review instead of being approved by the score.

• Magistry has no undo for a product it created. The product stays a draft in Shopify until you publish or delete it there.

• Looking for products is one switch (Look for new products). It only fills the candidate shortlist and creates nothing in your shop.
• Creating products is a separate switch (Add new products). It is off until you turn it on, and nothing is onboarded while it is off.

• It does not publish products. Every product it creates starts as a Shopify draft, and putting it on sale is a separate decision.
• A machine approval is checked again against the current rules before a product is created. A person's approval is not second-guessed.
• The supplier cost from reverse-image search is an estimate read from a listing page. It is used until you enter the real cost.
• A suspended store does not run research, even when someone starts a run by hand.

• In the launch chat, each step is proposed as a card. Steps that spend, create accounts, publish or go live wait for your approval, unless you have set that kind of step to run on its own.
• Going live needs every blocking readiness check to pass and the launch to be confirmed. The confirmation waits for you unless you have set go-live steps to run on their own.
• Autopilot only runs steps that change nothing outside Magistry or only draft. A step that spends, creates an account, publishes or goes live stays a card unless the store's launch policy sets that kind of step to automatic, which full autopilot does for all four. Undo, cancel and purge are always a card.

• Undo, cancel and purge are cards of their own, and undo also needs the launch's rollback confirmation, which is cleared after use.
• Undo has not yet been proved against a real merchant's Shopify store. When Shopify does not read back what was there before, the undo is marked unconfirmed rather than done.

• On suggest only, the launch chat describes each step in words and writes no card, so it runs nothing itself.
• Deleting a store's launch data runs as a dry run only. The delete itself ships switched off.

• No store has completed a launch on the rebuilt version.
• First ad campaigns have not yet been proved live. Live proof waits on test ad accounts.
• It builds Shopify stores only.

• Bank lines get booking proposals from your rules and from Magistry's model. A person who may book accepts or changes each one in the bank workbench.
• Closing a period can require sign-offs, and the close shows which sign-offs are still missing.

• A booking made from a bank line is undone by posting a reversal entry, and the original entry stays in the ledger. Ending a payment match books nothing.

• Booking straight from your saved rules runs as a job that ships switched off. While it is off, no rule books anything and each proposal waits for a person.

• Magistry does not file your VAT return. It prepares the figures, and you or your accountant file in Mijn Belastingdienst Zakelijk.
• Tax rules are written for Dutch businesses only.
• Statements come in as files. Live bank feeds, Stripe and Peppol connections are built but not connected yet.
• Payout matching does not guess. When several bank lines fit one transfer it is marked ambiguous for a person to settle.
• One statement import takes up to 5,000 lines. A longer file is split into several imports.

• You decide each dispute: fight, accept, or refund. The recommendation is advice and you can override it.

• Choosing fight, accept or refund records your decision on the dispute in Magistry. It issues no refund and sends nothing to Shopify, so there is nothing there to take back.

• Automatic refunds on pre-dispute alerts are on by default. Magistry can switch them off for your store on request, which sends every alert to a person. No alert feed is connected yet, so none has run.

• It tracks disputes and their deadlines. It does not submit evidence to Shopify for you today: you respond in Shopify admin with Submit response on the chargeback.
• Submitting from Magistry needs a Shopify dispute-evidence permission that requires Shopify's approval, and the app does not request it yet.
• Only Shopify Payments disputes are synced.
• Pre-dispute alerts from card networks (Ethoca, Verifi) are not connected. The poller reports zero alerts.
• A packet can be partial. When a field is missing, the draft says so instead of filling the gap.

• Only people with write access to the business can issue the token or change the connection.
• You approve each remote MCP server the agents may consult. Each one is a source of facts, and the database refuses one that could write.

• A sync only writes Magistry's own copy of your data. It upserts the same rows again on each run and sends nothing back to your backend, so there is nothing there to undo.

• The worker only pulls for a business whose custom API connection is marked connected. Without one, nothing is read.

• Theme edits, the storefront audit, Store Shield and returns stay closed. They need a Shopify storefront, not a catalogue.
• The custom API connection only reads. Magistry does not write back to your backend through it.
• Your endpoint must use https and a public address. Anything else is refused before a request is made.
• Building the endpoint is engineering work on your side. We set it up with you, one business at a time.
• On Shopware, the only write is a product price, and only when its owner in Magistry has declared it.

• Replies and actions leave on their own only when the desk is on autopilot. In approval mode every draft and every action waits in the inbox for a person.
• In the inbox you approve, edit or reject each draft, one at a time or in bulk.
• Proactive messages to customers start with a batch that waits for your approval. Later batches for the same signal send on their own only after you allow it.

• A sent reply and an issued refund are final. Refunds carry an extra check that reads the order's refunds back, so a retry cannot pay twice.

• While the store's kill switch is on, the agent blocks everything it proposes except deferring a thread or escalating it to a person.

• It answers email only, from an IMAP or Outlook mailbox. Gmail is connected over IMAP, not as its own connector.
• Refunds, cancellations, address changes and gift cards are carried out on Shopify orders.
• It does not auto-send a reply to a message older than 14 days by default. The draft stays for a person to send.
• Only four substantive replies go into one conversation within 30 days by default. After that the thread needs a person.
• A proactive message reaches at most 200 customers per signal.

• A reply is posted only after a person approves it. The one exception is a reply on The Shopinion when you have switched on automatic posting for the store, which is off by default.

• A reply Magistry publishes cannot be undone from Magistry.

• You turn reputation monitoring on and off for your store under Reputation.
• Automatic posting stops while the store's kill switch is on, and also when the switch cannot be read.

• It does not post replies on Trustpilot, Google or other review sites. You copy the approved draft into the site's reply box and mark it resolved.
• It cannot email a reviewer, because a review or mention carries no address to reach them.
• Social networks such as X are not read yet. Those sources accept a connection and return nothing.
• A crisis alert reports what triggered it and opens a ticket for you. It does not reply to anyone or post anything.

• A design sent to an ad campaign becomes a draft creative on the ads page. It goes to the ad platform only after it is approved there.
• A design sent to social becomes a proposed post. It publishes once you approve it, or through your auto-publish setting if you have switched that on.

• Inside the editor, undo and redo step back and forth through your changes. Once a design is published as a social post, that is final: publishing cannot be undone from the post's page.

• Creative Studio opens when the store's Beta features switch is on in Settings. Until then the studio pages send you to that switch.

• Designs go to Google and Meta campaigns only. Other ad networks do not take studio files yet.
• On Google, only a Performance Max campaign takes studio images.
• On Meta, an approved design is added as a paused ad in each active ad set.
• The photo tools are four: remove a background, upscale, erase and extend. Each one is a paid model call.

• The draft waits as a proposal. When you approve it, or when auto-publish is on and the post has an image or video, it is queued.
• Auto-publish is a switch in the brand profile. Off means every post goes to your review queue.
• You approve or reject each proposed post. An approved post is queued for its slot.
• With auto-publish on, a post without an image or video is not published on its own. It waits for you.

• A published post is final. Archiving a post in Magistry removes it from your queue and does not take it down from Facebook or Instagram.

• The Enabled switch in the brand profile turns the hourly run off. With it off, the run stops before it drafts, schedules or publishes anything.

• It publishes to Facebook Pages and Instagram business accounts. Other networks can be connected, and Magistry does not publish to them today.
• It does not answer direct messages on its own. DM auto-reply is off in every brand profile by default.
• Video is off by default. When you turn it on, Magistry checks the store's monthly budget before it generates a video.

• The gate then decides whether a person must review. On a store set to approval only, every action waits. An irreversible action always waits, whatever the store's mode.
• With autonomous mode off, decisions are still computed but never applied on their own. Each one waits for a person.
• An approval that moves money or cannot be undone is confirmed with Face ID in the Magistry mobile app.

• A revert only covers the catalog actions the revert executor knows. Any other row is refused rather than guessed at.

• Before the Marketing Brain acts, one gate checks in a fixed order: the kill switch, the module switch, dry-run mode, the automation feature, the rate limit and the AI budget. The first failure stops it.
• The kill switch in Settings stops the agents that write and spend on your store. Turning it on or off needs a role with write access to the store.
• While the kill switch is on, reverts stop too. The switch pauses movement in both directions.
• Feed pushes have their own pause, separate from the store-wide kill switch.

Its limits are listed in the columns before this one.

• A proposed row does nothing until someone approves it. Only an approved row reaches the executor and Shopify.
• Approve or turn down a proposed catalog change in the browser or in the mobile app. Both use the same ruling, so the two cannot disagree.

• Reverting a row runs the inverse change in Shopify, then stamps the original row as reverted. The original stays on record.
• Revert an applied catalog row from the decisions page. It needs a role with write access to the store.
• The Brain rolls back a losing Google Ads change on its own only when the store is on autopilot and automatic rollback is switched on.
• Only a row that was applied and not yet reverted can be reverted. A row that never reached Shopify has nothing to undo.
• Reverts cover the catalog actions the revert executor knows, such as price tests, drafts and copy rewrites. Any other row is refused.
• A Brain Google Ads rollback is refused when another writer has changed that setting since, or when no prior state was captured.

• While the kill switch is on, reverts are paused along with forward changes.

Its limits are listed in the columns before this one.

• A store change comes back as an approval card. The change runs only after you approve that card.
• Only the person who owns the conversation can approve its cards, and only with a role that has write access to the store.
• A card that moves money or cannot be undone is approved in the Magistry mobile app with Face ID. The browser cannot approve it.

• A refund or an order cancellation made through Magistry is final and cannot be undone.

• Revoking a connected AI client's access refuses every token issued to it from that moment on.
• Ask Magistry to turn the store's kill switch on and it does so at once. Turning the switch off again comes back as an approval card for you to approve.

• It works on one store at a time. There is no chat across several stores.
• It does not guess a number for data it has no tool to read. It says it cannot read it.
• On the shared demo account, every tool except reads is refused.

• Before an approval that moves money, the phone reads a key that only opens with your face or fingerprint and signs a one-time code from the server.
• You approve or reject each item. Approving something that moves money needs Face ID or a fingerprint. Rejecting does not, because refusing to spend is the safe direction.

• A Marketing Brain move that already ran can be reverted from its receipt under Done, when the receipt says the worker would still accept it. A revert needs your confirmation too.
• Money approvals are sent at once and only when the phone is online. Other answers wait five seconds with an Undo and queue while offline.

• An approved Marketing Brain proposal goes through the same function as the dashboard button, so the kill switch, rate limiter and spend cap apply.

• The phone's passcode is never accepted in place of a face or fingerprint for money. It may unlock reading only.
• At most three non-critical pushes per person per local day.
• On iPhone, urgent pushes arrive as time-sensitive notifications. They are not critical alerts that break through Do Not Disturb.