A.M.A.N.D.A. // Supervised decision runtime
Six governed stages. One accountable decision.
A.M.A.N.D.A. analysis is Hyde Workshop's supervised decision method. It defines the mission, verifies evidence, audits the implementation, routes the work, tests defenses, and prepares a recommendation that stops at a human approval gate.
Each stage owns one responsibility. No stage owns the final decision.

Adaptive Mission Agent
AI Amy
Turns an unclear request into a defined mission with audience, objective, scope, constraints, acceptance criteria, and a named human owner.
Primary output: mission brief and acceptance criteria.

Multi-Source Mapping Agent
AI Maya
Maps grounded evidence, official documentation, dates, versions, claims, missing information, and source quality before any conclusion is formed.
Primary output: evidence map and source-grounding record.

Analytical Audit Agent
AI Aria
Audits technical quality, accessibility, SEO, performance, compatibility, maintainability, and whether a claimed improvement can actually be demonstrated.
Primary output: audit findings and remediation requirements.

Neural Navigation Agent
AI Nancy
Maps the implementation route across page code, Elementor, WordPress, plugins, hosting, caching, analytics, consent, dependencies, handoffs, and rollback.
Primary output: controlled implementation route and sequencing.

Defense Diagnostics Agent
AI Dawn
Examines security, privacy, permissions, consent, unsafe actions, sensitive data, backups, recovery, incident response, and rollback requirements.
Primary output: risk register, safeguards, and recovery requirements.

Accountability Agent
AI Astra
Combines the earlier stages into a recommendation for human review. Astra can prepare a decision, but cannot grant human approval or authorize autonomous deployment.
Primary output: READY FOR HUMAN REVIEW, or a governed stop or revision state.
How an A.M.A.N.D.A. analysis runs
An A.M.A.N.D.A. analysis is a six-step review that ends with a decision made by a named person. One role handles each step, and each role leaves a written artifact behind, so the reasoning can be checked, challenged, or reversed.
When to use it
- Adopting a new AI tool, or connecting an agent to files, accounts, or APIs.
- Changing a production WordPress page, template, or plugin.
- Publishing AI-assisted content that makes factual claims.
- Automating a task that spends money, sends messages, or deletes data.
What you end up with
A decision record: the six artifacts, the recommendation (adopt, pilot, restrict, or reject), the name of the person who decided, and the date.
What it does not do
It does not deploy anything, approve its own recommendation, or guarantee an outcome. It does not replace legal, security, or compliance advice. Astra can prepare a decision, but only a person can make it.
Illustrative example: adding an AI chat widget to a WordPress site
- Amy: goal is to answer pre-sales questions, with no pricing promises, and the site owner decides.
- Maya: read the vendor's documentation, data-handling terms, and current version, and note anything unverified.
- Aria: measure page speed and accessibility with and without the widget on a staging copy.
- Nancy: plan the order of work: staging, one page, then sitewide, with cache-purge steps.
- Dawn: check what visitor data the widget sends, where API keys live, and how to switch it off fast.
- Astra: brief the owner to pilot on one page with a monitoring window, or reject if speed or privacy checks fail.
This example is illustrative, not a case study. For a public list of common risks in applications built on large language models, see the OWASP GenAI Security Project (opens in a new tab).
Browser-only brief builder.
Describe the outcome and get a structured route, not a black-box promise. It updates as you type and nothing leaves your browser.
WordPress / Elementor controlled repair
Primary constraint: risk and safety. Separate page-level defects from Elementor, WordPress, plugins, hosting, caching, analytics, and consent before changing production.
- AAmy: missionDefine the defect, affected users, desired result, acceptance criteria, exclusions, and human owner.
- MMaya: evidenceCollect complete code, screenshots, template context, plugins, versions, cache layers, and relevant documentation.
- AAria: auditAudit HTML, CSS, JavaScript, headings, IDs, ARIA, images, SEO, accessibility, performance, and compatibility.
- NNancy: routingMap the implementation across page code, Elementor, WordPress, plugins, hosting, cache and CDN, and analytics and consent.
- DDawn: defenseCheck credentials, scripts, forms, external dependencies, backups, recovery, safeguards, and rollback.
- AAstra: decisionPrepare the recommendation and stop at HUMAN_REVIEW before publishing or deployment.
Next: turn a workflow into controls in AI Forge, watch the sequence in the Workshop, or send a project brief.