# Portal Compliance Agent: Every Portal App on Design Standard > The Portal Compliance Agent is the agent that runs design compliance checks across your Ai1 portal in the Ai1 platform by MyZone AI: it sorts each finding, sends each fix to its owner, confirms the fix landed and checks new apps before they ship, without making design judgments itself. Canonical page: https://myzone.ai/pages/agents/ai-portal-compliance-agent Part of Ai1, by MyZone AI. Book a design check walkthrough: https://calendly.com/d/ct6h-tcy-8qf/ai1-demo?a1=Portal%20Compliance%20Agent&utm_source=myzone.ai&utm_medium=agent-page&utm_content=ai-portal-compliance-agent-final Last updated: 2026-10-05. Reviewed by the MyZone AI team. Every portal app kept on design standard, new apps checked first. ## At a glance - **Coverage:** Every app on the portal's current app list - **Findings:** Sorted by type and severity from the Designer's own rules - **Fixes:** Design to the Designer, code to the app's team, releases to the DevOps Agent - **A pass:** Every page opened while logged in, at desktop and phone size, plus the Designer's sign-off - **New apps:** Checked in full before they go live - **What it never does:** Make a design judgment or fix an app itself ## What the Portal Compliance Agent does - **Checks the whole portal:** It runs the automated design checks across every app, working from the portal's current list of apps rather than a remembered count. - **Sorts every finding:** Each finding gets a type and a severity based on the Designer's own rules. Anything the rules do not cover goes to the Designer. - **Sends each fix to its owner:** Design questions go to the Designer, code changes to the app's own team and releases to the DevOps Agent. - **Confirms fixes landed:** Once a fix is in, it runs the checks again and confirms the Designer's earlier ruling was addressed. - **Checks new apps before launch:** A new app has to pass the same full check before it goes live, so it joins the portal already on standard. ## How the Portal Compliance Agent differs from an automated design scanner An automated design scanner reports what it can see and leaves you to decide what matters and who fixes it. The Portal Compliance Agent sorts every finding by the Designer's own rules, sends each fix to its owner and checks again to confirm it landed. A pass needs every page opened while logged in at desktop and phone size plus the Designer's sign-off, and the Designer's ruling always beats a scan. ## How it works 1. **Check** (When you ask, or before a new app ships): Automated design checks run across every app in the portal. 2. **Sort** (After each check): Each finding is given a type and a severity from the Designer's rules. 3. **Route** (Once findings are sorted): Each fix goes to the one who owns it: the Designer, the app's own team or the DevOps Agent. 4. **Confirm** (Once a fix lands): The checks run again once the fix lands, to confirm it worked. ## When to use it - **You want to know if every portal app still meets the standard:** It runs the full check and reports every app, with each finding sorted and sent to its owner. - **A new booking app is ready to go live:** It runs a full check first, and any design question goes to the Designer before launch. - **An app has just been fixed:** It reruns the checks and confirms the fix landed and the Designer's ruling was met. ## What you get - A portal-wide report covering every app - Findings sorted by type and severity - Each fix routed to its owner - Confirmation once a fix has landed - A full check of each new app before it ships ## Example: portal compliance report Example with a fictional company. Names, people and figures are invented to show the agent's output. Any resemblance to a real company or person is unintended. Industry facts are real and cited with their sources. What it was asked: Tell us whether every app in our member portal still meets the design standard, and check the new class pass shop before it goes live. A sample whole-portal compliance report and new-app check for a fictional studio group, in the agent's usual four steps: check, sort, route, confirm. All figures are invented; no real portal, server or client data was read. Design rulings and sign-off come from the Designer, every code change is made by a person on the app's own team and releases go through DevOps Agent. Run date: 1 October 2026. ### What it found - Five of seven portal apps pass. Membership billing fails four checks at phone size, and trainer rota counts as a fail because four of its pages would not open at phone size. - Six of the eight findings were sorted by the Designer's own rules and sent to the app teams; two are not covered by the rules and wait for the Designer's ruling. - The new class pass shop is not ready to ship: desktop is clean, but three phone pages and the Designer's sign-off are missing, and anything missing counts as a fail. ### Sources - [Demographics of Mobile Device Ownership and Adoption in the United States | Pew Research Center](https://www.pewresearch.org/internet/fact-sheet/mobile/), Pew Research Center (accessed 2026-10-01) ## Guardrails - It never makes a design judgment. The Designer decides what is on brand, and that ruling always beats a scan. - A pass needs complete evidence: every page opened in a real browser while logged in, at desktop and phone size, plus the Designer's sign-off. Anything missing counts as a fail. - It does not fix apps itself; each fix goes to its owner. - On each Ai1 server it covers only that server's own portal apps. ## Frequently asked questions ### How do you keep several apps on the same design standards? Check every app against the same rules, from the current app list rather than a remembered count, and send each fix to its owner. In Ai1 by MyZone AI, the Portal Compliance Agent sorts each finding by type and severity using the Designer's own rules, and anything the rules do not cover goes to the Designer. It is ready to use, and on each Ai1 server it covers that server's own portal apps. ### What evidence should design QA need before an app passes? Complete evidence: every page opened in a real browser while logged in, at desktop and phone size, plus the Designer's sign-off. Under the Portal Compliance Agent, anything missing counts as a fail, so a quick automated scan on its own never earns a pass. ### Why run a design check before an app is released? Fixing an app after people are using it means clean-up work and a portal that feels inconsistent. The Portal Compliance Agent runs the same full check on each new app before it goes live, and any design question goes to the Designer before launch, so the app joins the portal on standard. ### Does the Portal Compliance Agent fix apps or judge design itself? No. Design questions go to the Designer, code changes to the app's own team and releases to the DevOps Agent. It then checks again to confirm the fix landed. It never makes a design judgment either. The Designer decides whether an app looks right, and the Designer's ruling always beats a scan. ## About Ai1 Ai1 is the AI operations platform by MyZone AI, where each client runs on its own private server. The Portal Compliance Agent is included on every Ai1 level, including Developer Core, with no per-agent charge. It works alongside the other Ai1 agents on your account. Pricing: https://myzone.ai/pages/services/ai1-pricing. Security: https://myzone.ai/pages/security.