active missions
0
Olympus observatory · live agent telemetry
See work move across Olympus.
Each portrait is a live specialist endpoint. Routes appear only when data moves: violet for dispatch, cyan for execution, amber for return, and teal for coordinated availability.
Specialists39
Active0
SystemLive
Linked0
Executing · cyanDispatch · violetReturning · amberConnected · tealDormant
Live server state only. Select the council for ownership details or dispatch new work through Zeus.
Live • temple of orchestration
Olympus commands.Compliance moves.
Zeus turns each quality request into a visible route—dispatching specialist AI workflows, organizing supplied evidence, and returning review-ready draft protocols and quality documents.
olympus routing
telegram • connected
HRHera
POPoseidon
DMDemeter
ATAthena
APApollo
RGHermesReg
ARArtemis
ASAres
AFAphrodite
HPHephaestus
KRKronos
AGArgus
ACAsclepius
DADaedalus
DIDionysus
HYHypatia
IRIris
JAJanus
NINike
OROrion
PRPrometheus
VUVulcan
THThemis
PNPanacea
HGHygieia
RHRhea
ALAtlas
ADAriadne
HEHestia
EOEos
NRNereus
CLCalliope
GAGaia
PTProteus
MNMnemosyne
HCHecate
MTMetis
BOBoreas
NENemesis
ZZeus
specialist network
Live Hermes profiles available for direct or orchestrated work.
0
profiles available
routing status
Connecting
Checking live agent activity…
MyZeusCompliance · Validation document services
Validation documentation, elevated.
For pharmaceutical and life-sciences professionals who need clear, defensible documentation without surrendering technical judgment. MyZeusCompliance helps turn validation needs, source evidence, and acceptance criteria into structured, review-ready Word documents.
Word-first deliveryProfessionally structured drafts designed for practical review and controlled revision.
Lifecycle perspectiveRequirements, risk, testing, traceability, deviations, and reporting considered together.
Qualified approval stays humanYour subject-matter experts retain authorship decisions, review authority, and final approval.
Built for regulated work
Move from a blank page to a defensible validation package.
Validation professionals are expected to move quickly while producing documentation that is complete, internally consistent, traceable, and ready for rigorous review. Starting every plan, protocol, test script, and report from scratch consumes expert time that should be spent making risk-based decisions.
MyZeusCompliance provides document-generation services through AI-supported specialist agents for validation, quality, engineering, data integrity, and regulatory work. You provide the intended use, system or equipment context, governing procedures, technical evidence, and approval expectations. The service organizes that material into a coherent Word draft your team can challenge, refine, execute, and approve through its established quality system.
Professional deliverables
Documentation across the validation lifecycle.
Engagements can begin with one focused document or a connected package. The drafting workflow is organized around intended use, risk, objective evidence, acceptance criteria, and traceability.
Define the validation path
Translate business, quality, regulatory, and technical expectations into a practical lifecycle strategy.
- Validation Master Plans and project Validation Plans
- Risk-based validation and qualification strategies
- System inventories, scope, roles, and deliverable matrices
Build executable qualification evidence
Create protocols and reports with clear prerequisites, tests, acceptance criteria, exceptions, and approvals.
- URS and design-review documentation
- IQ, OQ, and PQ protocols and reports
- Commissioning, qualification, and turnover packages
Apply CSV and CSA with purpose
Scale assurance activities to patient safety, product quality, data integrity, and system risk.
- CSV and Computer Software Assurance plans
- Part 11, data-integrity, and supplier assessments
- Requirements, risk assessments, test scripts, and traceability matrices
Connect evidence to the final decision
Present execution results, discrepancies, residual risk, and release rationale in a reviewable record.
- Validation Summary Reports and final reports
- Deviation, discrepancy, and exception documentation
- SOPs, change controls, periodic reviews, and remediation plans
A controlled working method
Expert input in. Review-ready structure out.
Define the decision
Clarify intended use, scope, document type, governing requirements, reviewers, and required outcome.
Provide the evidence
Attach specifications, procedures, risk records, vendor material, prior templates, and applicable standards.
Build the Word draft
Specialist agents organize sections, controls, tests, acceptance criteria, traceability, and document metadata.
Review and approve
Qualified personnel verify accuracy, resolve gaps, execute required testing, and approve the controlled record.
Accelerate authorship without outsourcing accountability.
MyZeusCompliance produces advisory drafts. Final suitability, execution, approval, and record control remain with your authorized quality and technical professionals.
Trust, evidence & responsible use
Draft faster.
Keep human authority.
MyZeusCompliance is built primarily to generate structured draft protocols and quality documents through WebChat and Telegram Chat. The AI workflows assist authorship; they do not validate a system, approve a record, release a product, or replace qualified professional judgment.
Document status
Every generated file begins as an uncontrolled draft
Before regulated use, authorized personnel must verify the intended use, jurisdiction, technical facts, source currency, risk controls, acceptance criteria, traceability, and site-specific content. The final file must be approved, versioned, executed where applicable, and retained in the customer’s authorized quality or document-management system.
Upload safety
Share only authorized source material
Do not upload protected health information (PHI), patient-identifiable information, credentials, regulated originals, or confidential material your organization has not authorized for external processing. Supported PDF and DOCX files are staged for the active request and scheduled for removal when it finishes or stops; exceptional retention in logs, failures, or backups must be evaluated under the applicable service agreement.
Methodology
Frame → ground → generate → govern
- Define intended use, document type, jurisdiction, reviewers, and approval route.
- Provide current specifications, procedures, risks, standards, and site evidence.
- Use specialist AI workflows to organize a draft and identify gaps or TBD items.
- Require qualified human verification, execution, approval, and document control.
Regulatory source hierarchy
Primary sources control the conclusion
Regulations, binding requirements, guidance, consensus standards, enforcement communications, and editorial interpretation must be identified separately. Guidance generally expresses an authority’s current thinking and does not create a universal requirement by itself.
CSV, CSA & data integrity
Applicability depends on product, system, and jurisdiction
FDA’s Computer Software Assurance guidance is formally scoped to production and quality-system software used by medical-device manufacturers. Pharmaceutical CSV, predicate-rule obligations, Part 11, EU GMP Annex 11, data integrity, and customer procedures may require a different or additional approach.
Sterile & parenteral work
Contamination control remains site-specific
Drafts may support aseptic-processing protocols, contamination-control strategies, environmental monitoring, utilities, sterilization, cleaning, and qualification. Facility design, product characteristics, process science, local procedures, current primary sources, and authorized microbiology and quality review must govern the final document.
Privacy & data handling
Use the minimum necessary information
The public dashboard can store interface preferences and limited session state in the browser. Protected chat and file operations require authentication. Customers remain responsible for authorization and redaction of submitted material. Do not assume HIPAA applicability or a business-associate relationship unless it has been assessed and established in writing.
Security
Controls reduce risk; they do not eliminate it
Credentials are intended to remain server-side, protected operations require authentication, and the service applies transport and browser-security controls. “Secure” is not a certification or guarantee. Security concerns should be reported through the service contact before sensitive operational use.
Accessibility
Accessibility is an active quality requirement
The interface includes semantic controls, accessible names, reduced-motion support, and keyboard navigation features. The service targets WCAG 2.2 AA, but does not claim full conformance until the complete authenticated experience has passed automated and manual assistive-technology testing.
Editorial policy & corrections
Verify high-impact conclusions in the controlling record
Regulatory news and AI summaries are decision-support material. Each material statement should identify jurisdiction, source type, publication or effective date, and primary link. Corrections should be dated and reflected in the changelog. Report suspected errors through the portfolio contact below.
Professional independence
No agency endorsement or delegated authority
MyZeusCompliance is an independent AI-assisted documentation service. It is not affiliated with, endorsed by, or acting for FDA, EMA, the European Commission, or another regulator. Named agents are workflow roles, not human reviewers or regulatory officials.
Service limitation
Advisory drafting, not final approval
The service does not provide regulatory approval, legal advice, medical advice, certification, validation approval, product-release authorization, or a substitute for qualified professional review. Users determine applicable requirements and remain accountable for final decisions and records.
The specialist council
Thirty-nine domains.
One visible command.
Each deity owns a regulated discipline, reports live availability, and opens directly into the correct Hermes profile.
39shown
—available
0working
Selected route · Zeus dispatch
Apollo — CSV / CSA Validation
Use for evidence packages and test strategy
- Best for URS, RTM, IQ/OQ/PQ, and validation deliverables.
- Strong default for computerized system assurance work.
apollovalidation_csv_bot
Specialist roster39 agents in view
Hera
Part 11, ALCOA+, audit trails, and electronic record control.
Part 11ALCOA+Audit trail
Poseidon
Change control, impact assessment, and revalidation triggers.
Change controlImpact
Demeter
SOPs, controlled procedures, QMS documentation, and templates.
SOPsQMS
Athena
Records, document control, retention, and filing structures.
RecordsRetention
Apollo
CSV / CSA, RTM, IQ/OQ/PQ, and validation evidence packages.
CSVCSARTM
Artemis
CAPA, deviations, investigations, and root cause analysis.
CAPARCA
Ares
Training, curricula, and role-based qualification.
TrainingQualification
Aphrodite
Supplier audits, qualification, and quality agreements.
SupplierQA
Hephaestus
Risk management, hazard analysis, FMEA, and residual risk.
RiskFMEA
HermesReg
FDA strategy, 483 responses, warning letters, and submissions.
FDA483
Kronos
Final escalation, risk acceptance, and executive authority.
ExecutiveEscalation
Argus
Inspection readiness, mock inspections, evidence readiness, and response preparation.
InspectionEvidence
Asclepius
QC laboratory systems, LIMS controls, analytical data integrity, and lab workflows.
QC LabLIMS
Daedalus
Facilities, HVAC, cleanrooms, critical utilities, and environmental qualification.
FacilitiesHVAC
Dionysus
Aseptic processing, sterility assurance, contamination control, and sterile operations.
AsepticSterility
Hypatia
Analytical method validation, verification, robustness, and lifecycle control.
MethodsRobustness
Iris
Regulatory intelligence, labeling compliance, UDI, artwork, and change monitoring.
LabelingUDI
Janus
Serialization, aggregation, unique identifiers, and track-and-trace controls.
SerializationTrace
Nike
Cleaning validation, residue control, cleaning-cycle qualification, and verification.
CleaningResidue
Orion
Technology, process, product, and knowledge transfer readiness.
Tech transferReadiness
Prometheus
Process validation lifecycle, process capability, PPQ, and continued verification.
PPQCPV
Vulcan
Cybersecurity, SaaS/cloud risk, vendor security posture, and control assessment.
CyberSaaS
Themis
Pharmaceutical governance, rule consistency, ownership boundaries, and escalation.
GovernanceQuality oversight
Panacea
Tablets, capsules, blending, granulation, compression, coating, and process validation.
TabletsGranulationPPQ
Hygieia
Sterile injectables, aseptic processing, fill-finish, utilities, and contamination control.
AsepticFill-finishCCS
Rhea
Solid dosage formulation, blending, granulation, compression, coating, and process understanding.
FormulationCPP/CQA
Atlas
Equipment characterization, scale-up modeling, and technology transfer engineering.
Scale-upTech transfer
Ariadne
MBR/BMR review, batch traceability, material reconciliation, and document data flow.
Batch recordsTraceability
Hestia
Cleanroom discipline, gowning conformance, environmental monitoring, and contamination risk.
CleanroomEM
Eos
Aseptic filling controls, interventions, media fill (APS) design, and line clearance logic.
Fill-finishAPS
Nereus
WFI, clean steam, HVAC interfaces, and sterilization-support systems (SIP/CIP).
WFIClean steam
Calliope
QA release narrative, batch disposition support, and release package compilation.
ReleaseDisposition
Gaia
Cell banks, seed trains, cell culture, fermentation, harvest, and upstream process control.
UpstreamCell culture
Proteus
Purification, chromatography, filtration, UF/DF, and viral-clearance evidence.
DownstreamViral safety
Mnemosyne
Stability programs, specifications, OOT trends, retest periods, and shelf-life evidence.
StabilityShelf life
Hecate
Packaging qualification, container-closure integrity, and extractables/leachables risk.
CCITE&L
Metis
Continued process verification, APR/PQR, capability, and statistical quality trending.
CPVAPR/PQR
Boreas
GDP, warehousing, cold-chain transport, excursions, returns, and recall readiness.
Cold chainRecall
Nemesis
Complaints, pharmacovigilance routing, safety signals, and post-market escalation.
ComplaintsSafety
Protected conversation
Sign in to open WebChat
Enter your MyZeusCompliance credentials. The rest of the dashboard remains available without signing in.
Validation (CSV)User typed a single request → Zeus produced a complete IQ protocol DOCX in 4 minutes.
Quality ManagementUser uploaded a deviation log → Zeus delegated to CAPA experts and drafted a risk-adjusted investigation.
Regulatory StrategyUser asked for filing guidance → Zeus compiled an FDA 510(k) preparation checklist based on current guidance.
WebChat · Hermes TUI gateway
Zeus WebChat
Connected to Hermes through the secure server gateway
Zeus · orchestrator
ready
Typing…
Starting requestEstimated 3% · calculating time remaining
Email drafted DOCX
GxP & Validation Life Cycle
Document Requisition Wizard
Select the target compliance deliverable to solicit from Zeus and Hermes specialists:
Applicable Regulatory Predicate Rules
Synthesized Compliance Requisition Prompt
⚡ Controlled Delivery Mode: Hermes will structure the response with formal GxP headers, numbered verification tables, review approval blocks, and produce a downloadable Microsoft Word (.docx) document artifact.
Folio 01 · routing board
Start from the event.
Choose the regulated event you need to control. Each board shows the specialist sequence before you dispatch it.
Computerized system change
Impact assessment, risk, requirements, test evidence, traceability, and release decision.
Poseidon → Apollo → Hera → KronosDeviation or CAPA
Containment, investigation, root cause, corrective action, effectiveness, and training impact.
Artemis → Hephaestus → AresVendor qualification
Criticality, audit evidence, quality agreement, platform support, and residual supplier risk.
Aphrodite → Hephaestus → HermesRegRegulatory response
Observation assessment, evidence control, response drafting, commitments, and executive approval.
HermesReg → Artemis → Demeter → KronosFolio 03 · deliverable catalog
Choose the evidence.
Select the controlled output you need. The owning specialist opens with the correct document context.
Evidence packages
Risk-based validation deliverables with traceability and explicit acceptance criteria.
URSRiskRTMIQ/OQ/PQVSR
Controlled records
Operating decisions translated into review-ready procedures and quality records.
SOPCAPADeviationChange control
Lifecycle controls
Supplier, training, retention, and inspection evidence across the controlled lifecycle.
SupplierTrainingRecordsInspection
Folio 04 · cadence ledger
Keep control in rhythm.
A risk-based review cadence for maintaining validated state and inspection readiness.
Impact and validation assessment
Assess scope, validation evidence, data integrity, and affected-role training before approval.
Open quality-record review
Review deviations, CAPAs, overdue training, access exceptions, and supplier actions.
System health and trend review
Assess incidents, audit trails, performance, backup evidence, and recurring failure modes.
Periodic review
Confirm intended use, validated state, vendor support, security posture, and documentation currency.
Regulatory intelligence · Hermes digest
Signals before they become gaps.
A deduplicated, reviewable feed for FDA, Federal Register, EMA, and MHRA publications. Summaries are decision support; verify the linked primary source before initiating a quality action.
Scheduled collectionWeekdays · 06:00 ASTAwaiting first Hermes run
0 signalsCadence: 0 6 * * 1-5
No digest has been ingested yet. The n8n schedule posts deduplicated items to
/api/news-feeds.AI intelligence · regulated life sciences
Machine signals. Human accountability.
A focused primary-source digest for artificial intelligence across pharma, parenteral manufacturing, and medical devices. Treat summaries as triage—not approval evidence—and verify every source before a controlled decision.
Scheduled collectionWeekdays · 07:00 ASTAwaiting first primary-source run
0 signalsCadence: 0 7 * * 1-5
No AI digest has been ingested yet. The scheduler can POST reviewed items to
/api/ai-news-feeds.Folio 05 · complete operating manual
How MyZeusCompliance works.
A practical tutorial for routing regulated work, collaborating with specialist agents, handling documents, and preserving approved evidence.
Release 3.71 · August 11, 2026
Latest control-room changes.
This ledger summarizes user-visible behavior now available in the control room. It is operational guidance, not a substitute for formal system change records or release approval.
Floating FDA and page controls
FDA News now anchors a global floating control rail. The page glides slowly down and back up, pauses for direct interaction and while FDA News is open, offers manual Up, Auto, and Down controls, and remains still when reduced motion is requested.
Professional validation services
A new Olympus-inspired About page explains the Word-document service, validation lifecycle deliverables, controlled working method, and the qualified professional's responsibility for review and approval.
Public control-room shell
The dashboard opens without a page-level login. WebChat and Telegram Chat request credentials inside the chat workspace before protected messages, files, and live operational data are loaded.
FDA-inspired dark view
Dark view is the first-visit default, with repaired foreground and background contrast for assistant responses, structured tables, and task output.
Recoverable document workflow
Long-running analysis and document generation use persistent background jobs with phase, estimated progress, remaining time, restored attachments, and durable failure status.
Controlled draft handling
Users can upload PDF or DOCX evidence, stop an active request, download generated DOCX/XLSX/PDF files, and confirm email delivery of a drafted DOCX through the configured workspace connector.
Chapter 1 · System overview
One control room, forty profiles.
MyZeusCompliance is a browser control room for a Zeus orchestrator and thirty-two regulated-domain specialists. A request can start with Zeus for cross-functional routing or go directly to the agent that owns the subject. Web messages are processed by the selected Hermes profile, can be mirrored through Telegram, and return to the same conversation ledger.
- Overview
- See the orchestration temple, current route, availability, and recent activity.
- About
- Review the validation-document services, available deliverables, working method, and professional-control commitments.
- Agents
- Compare specialist ownership, availability, and the exact Hermes profile behind each deity.
- WebChat
- Sign in inside the workspace, then send Hermes requests, attach evidence, read replies, and download generated files.
- Telegram Chat
- Sign in inside the shared chat workspace, then review Telegram/Hermes history and dispatch mirrored requests.
- Tasks
- Start common regulated events with a visible multi-agent route.
- Office
- See server-backed worker activity. Orange is ready; blue is working.
- Content
- Start validation, QMS, and governance deliverables from the owning specialist.
- Schedule
- Apply per-change, monthly, quarterly, and risk-based review cadences.
- News Feeds
- Review deduplicated regulatory news supplied by the Hermes/n8n schedule.
- Docs
- Review latest changes, tutorials, operating guidance, and troubleshooting.
- Glossary
- Search the controlled reference for compliance and platform terminology.
Governance rule: agent output is advisory working content until a qualified person reviews and approves it through the applicable controlled process.
Chapter 2 · Five-minute quick start
From the open dashboard to a useful result.
- Explore the public dashboard, then open Agents if you know the discipline or go directly to WebChat and keep Zeus selected.
- Enter your MyZeusCompliance credentials inside WebChat or Telegram Chat when the inline access gate appears.
- State the objective, regulated context, system or equipment, required deliverable, and any deadline or approval constraint.
- Upload supporting files in the Evidence dock before dispatching the request when the agent must analyze them.
- Review the route, response, assumptions, and cited evidence. Ask follow-up questions in the same agent session.
- Download the final DOCX, XLSX, or PDF, complete your human review, then transfer the approved file to the controlled repository.
Example request:
Create a simple autoclave IQ/OQ protocol using the attached equipment specification. Include document control, responsibilities, prerequisites, installation checks, operational tests, acceptance criteria, deviations, and approval signatures. Return a review-ready DOCX.
Chapter 3 · Choosing and routing agents
Use Zeus for coordination; go direct for clear ownership.
Start with Zeus
Cross-functional or uncertain work
Use Zeus when a request spans validation, data integrity, training, risk, records, regulatory, or executive approval. Zeus frames the work and coordinates the specialist sequence.
Choose a specialist
Focused single-domain work
Go directly to Apollo for validation, Artemis for CAPA, Demeter for SOPs, HermesReg for FDA strategy, or another clearly responsible profile.
Common routing examples
| Business event | Recommended start | Typical route |
|---|---|---|
| Computerized system change | Poseidon | Poseidon → Apollo → Hera → Kronos |
| Deviation or CAPA | Artemis | Artemis → Hephaestus → Ares |
| Supplier qualification | Aphrodite | Aphrodite → Hephaestus → HermesReg |
| Regulatory response | HermesReg | HermesReg → Artemis → Demeter → Kronos |
| Unclear or multi-domain request | Zeus | Zeus selects and coordinates the route |
Session behavior: browser history is separated by Hermes profile. Switching agents changes the profile; it does not merely rename the same chat. Choose New chat to clear the selected profile’s browser transcript and start a fresh Hermes session.
Chapter 4 · Tutorial
Draft controlled content in chat.
- Open WebChat. Choose Zeus for a multi-agent document or the owning specialist for a focused deliverable.
- Describe the protocol or controlled-content type, scope, source material, required sections, document identifier, and reviewer expectations.
- For validation protocols, Apollo normally owns the technical evidence structure. For SOPs and QMS documents, use Demeter.
- When you explicitly request a protocol, the activity label changes from Typing to Drafting protocol.
- Review the complete response in chat, including identifiers, tables, signatures, acceptance criteria, and any TBD fields.
- The newest protocol is packaged as a DOCX behind the scenes. Choose Email drafted DOCX below the chat to review the recipient and send it through Google Workspace.
Strong document request pattern:
Objective + regulated context + source files + required sections + acceptance criteria + document ID + output format + reviewer expectations
WebChat output is a controlled draft. Review and approve it before transferring it into your validated repository or QMS.
Chapter 5 · Tutorial
Upload and analyze source evidence.
- Select the agent that should own the analysis.
- Below the chat, choose Upload for analysis and select up to five PDF or DOCX files. Scanned PDF pages are OCR-processed automatically.
- Confirm the ready-file count appears. The dashboard server extracts PDF pages or Word paragraphs from the temporary upload.
- Write a specific request: identify the standard, expected output, review depth, and whether citations or a gap table are required.
- Dispatch the message. A background job keeps the activity route live while extracted evidence and citation markers are supplied directly to the selected profile; no Docker or file:// access is required.
- Follow the visible reading and analysis phases. Protocol wording appears only when you explicitly request a protocol.
- If needed, choose Stop request to interrupt the active Hermes connection.
- After the request finishes or stops, the temporary uploaded sources are deleted automatically.
PDF → [filename, page N]
DOCX → [filename, paragraph N]
Direct analysis accepts searchable PDF and DOCX files up to 25 MB per file. Files are staged for the active request and scheduled for removal when it finishes or stops. Do not upload PHI, patient-identifiable information, credentials, regulated originals, or confidential material your organization has not authorized for external processing.
Analysis prompt suggestion: “Analyze the attached file against the stated requirement. Cite the page, section, sheet, or row for every finding. Separate confirmed gaps, observations, assumptions, and recommended actions.”
Chapter 6 · Tutorial
Find and download generated outputs.
- Remain on the agent profile that created the file. Each profile has its own document storage.
- Select Refresh files after the agent reports that delivery is complete.
- The webpage intentionally lists only final-use formats: DOCX, XLSX, and PDF.
- Select Download. The server validates the selected profile and file path, then sends the file as a private attachment.
- If the agent gives an absolute path but no file appears, verify the file was written under the mounted profile directory and that the browser is still showing the same agent.
Hermes durable path:
/opt/data/profiles/zeuscompliance_orchestrator_bot/autoclave_iq_oq_protocol/QA-IQOQ-AUTOCLAVE-001.docx
Dashboard-mounted equivalent:
/data/profiles/zeuscompliance_orchestrator_bot/autoclave_iq_oq_protocol/QA-IQOQ-AUTOCLAVE-001.docx
Why you cannot “see” /opt/data in the browser: it is a server-side filesystem path. The supported user action is the authenticated Download link in the Evidence dock.
Chapter 7 · Live activity
Read dispatch, work, return, and readiness.
Idle / ready
Orange indicates the profile is available and waiting for work.
Zeus dispatch / working
Blue indicates a confirmed active profile; bright lightning connects Zeus to confirmed specialists, while violet lightning shows the declared Zeus dispatch route.
Specialist return
Green indicates a result returning to Zeus, then settles back to idle.
The Overview temple emphasizes route direction. Agents shows individual availability and profile ownership. Office maps all 40 profiles to workstations. These states come from the server and mounted Hermes profile databases; the interface does not invent a working state.
Chapter 8 · Quality and security controls
Use the system as advisory automation with controlled approval.
- Authenticate where required: the dashboard shell is public, while WebChat and Telegram Chat establish a protected HTTP-only session for internal APIs and sensitive actions.
- Keep credentials server-side: Telegram, Hermes, and dashboard keys are configured in Dokploy/VPS environment variables and are not exposed to the browser.
- Validate ownership: confirm the selected deity and exact Hermes profile before sending confidential or regulated evidence.
- Protect evidence: uploads and downloads are constrained to approved profiles, safe filenames, and validated profile-relative paths.
- Review output: verify accuracy, completeness, citations, calculations, intended use, and required signatures before approval.
- Preserve records: move the approved artifact to the official QMS, validation repository, DMS, or records system according to retention rules.
MyZeusCompliance is not the system of record. WebChat history and working files support the workflow; the approved controlled repository remains authoritative.
Chapter 9 · Troubleshooting
Resolve common dashboard and Hermes failures.
| Message or symptom | Meaning | Recommended action |
|---|---|---|
| Docker command is available but “docker version” failed | An older request supplied only a local path, so the agent tried a Docker-backed file tool. | Re-upload the PDF or DOCX and dispatch it from the Evidence dock. The dashboard now extracts the source server-side and supplies it directly. |
| PDF contains no extractable text | The PDF is image-only or lacks an OCR text layer. | Run OCR or export a searchable PDF, then upload it again. |
| Generated path shown, but no Download link | The file may be under another profile, outside the mounted directory, unfinished, or not one of the visible final formats. | Select the creating agent, refresh files, and confirm the path is under its durable profile directory with a .docx, .xlsx, or .pdf extension. |
| WebChat history is empty | The selected profile database may not be mounted or may have no session messages. | Confirm the Dokploy volume maps Hermes profiles to /data/profiles and that the selected profile contains state.db. |
| Agent is unavailable or misconfigured | The profile directory or gateway key is missing or does not match the dashboard Hermes key. | Check the profile’s scoped API_SERVER_KEY, shared authentication, volume mount, then restart that Hermes profile. |
| Telegram/Hermes bridge error | The dashboard could not complete the upstream request. | Verify HERMES_API_URL points to the API endpoint—not a login page—and confirm Hermes and Telegram credentials in Dokploy. |
| Upload failed | The file may be empty, unsupported, larger than 25 MB, or the profile volume may be read-only. | Use a supported document type, reduce file size, and verify write access to the mounted profile directory. |
Administrator health checks
GET /healthz
GET /api/health
GET /api/audit/profiles
GET /api/state
In Dokploy, the application is built from the Dockerfile and serves port 8000. The Hermes profile volume must be mounted at /data/profiles; Hermes receives uploaded durable paths under /opt/data/profiles.
Chapter 10 · Recommendations and glossary
Practices that produce stronger regulated work.
- Put the intended decision and deliverable in the first sentence.
- Name the governing regulation, procedure, standard, or acceptance basis.
- Request traceable citations for source-document analysis.
- Separate facts, assumptions, gaps, risks, and recommendations.
- Use one selected profile consistently until the focused work is complete; return to Zeus when coordination is needed.
- Require final files to use controlled identifiers and descriptive filenames.
- Refresh and download the final artifact before ending the session; do not rely only on a server path printed in chat.
- Document reviewer decisions and changes in the official quality workflow.
- Zeus
- The orchestration profile that frames requests and coordinates specialist work.
- Specialist
- A domain-owned Hermes profile such as Apollo, Hera, Artemis, or HermesReg.
- Hermes
- The agent runtime that executes profile conversations and tool work.
- Evidence dock
- The WebChat panel for uploading sources and downloading generated artifacts.
- Durable path
- A server-side profile path that persists through the mounted VPS volume.
- Controlled output
- A reviewed and approved artifact transferred to the authoritative quality repository.
- Working state
- A server-reported active profile turn, displayed in blue.
Chapter 7 · Compliance Q&A
Quick answers to common compliance questions.
Use this section when users need fast, professional guidance on validation, quality, and regulatory topics without opening a full manual chapter.
1. What is validation?
Validation is documented evidence that a process, system, or method consistently performs as intended for its approved use.
2. When is validation required?
Validation is required when a regulated process, software system, or method can affect product quality, patient safety, data integrity, or compliance.
3. What should a validation plan include?
A validation plan should define scope, responsibilities, risks, acceptance criteria, deliverables, and approval expectations.
4. What is an IQ/OQ/PQ lifecycle?
IQ confirms installation, OQ confirms operation within expected limits, and PQ confirms the process performs consistently in routine use.
5. What is traceability?
Traceability shows how each requirement is linked to risk, test evidence, and final approval so the record set is complete and auditable.
6. What is a deviation?
A deviation is any departure from an approved requirement, procedure, or expected result that must be documented and assessed.
7. What should happen after a deviation is found?
Contain the issue, document the facts, assess product and system impact, determine root cause, and assign corrective action as needed.
8. What is CAPA?
CAPA is the formal process for correcting a problem and preventing recurrence through investigation, action planning, and effectiveness review.
9. Why is document control important?
Document control ensures the current approved version is used, obsolete content is withdrawn, and records remain reviewable and reliable.
10. What is a quality record?
A quality record is objective evidence that a required activity occurred and met the approved procedure, specification, or acceptance criteria.
11. What does ALCOA+ mean?
ALCOA+ means data should be attributable, legible, contemporaneous, original, accurate, and complete, consistent, enduring, and available.
12. What is an audit trail?
An audit trail is a secure, computer-generated record showing who did what, when, and why for a regulated electronic action.
13. Why are access controls important?
Access controls limit actions to authorized users and help preserve the reliability, traceability, and accountability of regulated records.
14. When should a change be escalated?
Escalate a change when it can affect product quality, intended use, regulatory filings, labeling, inspection readiness, or validated state.
15. What is inspection readiness?
Inspection readiness means the organization can clearly explain controls, provide evidence quickly, and demonstrate that the quality system is maintained.
16. What should be reviewed before a regulatory response is sent?
Review facts, evidence, commitments, wording, deadlines, and approval authority before any formal response leaves the organization.
17. What is a commitment?
A commitment is an agreed follow-up action, correction, or deliverable that should be tracked to completion after a regulatory or quality discussion.
18. What is a controlled repository?
A controlled repository is the authoritative location for approved records, where versioning, access, and retention are governed.
19. Why start with Zeus?
Start with Zeus when a request is cross-functional or unclear, because Zeus can route it to the right specialist and keep the response aligned.
20. What should users do after reading a Q&A answer?
Apply the answer to the controlled process, verify the governing source, and escalate to the responsible specialist when the decision affects compliance.
Recommended tone: professional, plain-language, evidence-aware, and suitable for regulated-life-sciences audiences.
Folio 06 · controlled language
Compliance, defined.
Plain-language terms spanning quality systems, validation, data integrity, laboratories, regulatory operations, and the MyZeusCompliance workflow.
Loading terms
Folio 06 · compliance answers
Compliance Q&A.
Answers to common validation, quality, and regulatory questions in a concise, professional format.
1. How do we define validation?
Validation is documented evidence that a process, system, or method performs consistently for its intended regulated use.
2. When should validation be performed?
Perform validation when a regulated process, system, or method can affect product quality, patient safety, data integrity, or compliance.
3. What belongs in a validation plan?
A validation plan should define scope, roles, risk approach, acceptance criteria, deliverables, and approval requirements.
4. What do IQ, OQ, and PQ confirm?
IQ confirms installation, OQ confirms operation within expected limits, and PQ confirms the process performs consistently in routine use.
5. Why is traceability important?
Traceability connects each requirement to risk, test evidence, and approval so the record set is complete and audit-ready.
6. How should a deviation be handled?
Contain the issue, document the facts, assess impact, determine root cause, and assign corrective action through the approved quality system.
7. What is CAPA used for?
CAPA is used to correct a problem and prevent recurrence through investigation, action planning, and effectiveness review.
8. Why does document control matter?
Document control ensures the current approved version is used, obsolete content is withdrawn, and records remain reliable.
9. What qualifies as a quality record?
A quality record is objective evidence that a required activity occurred and met the approved procedure or acceptance criteria.
10. What should be reviewed before closing an investigation?
Review the facts, evidence, impact assessment, root cause, corrective actions, and closure rationale before final approval.
11. What does ALCOA+ require?
ALCOA+ requires data to be attributable, legible, contemporaneous, original, accurate, complete, consistent, enduring, and available.
12. What is an audit trail?
An audit trail is a secure, computer-generated record showing who did what, when, and why for a regulated electronic action.
13. Why are access controls critical?
Access controls limit actions to authorized users and help preserve the reliability, traceability, and accountability of regulated records.
14. When should a change be escalated?
Escalate a change when it can affect product quality, intended use, regulatory filings, labeling, inspection readiness, or validated state.
15. What does inspection readiness mean?
Inspection readiness means the organization can explain controls, provide evidence quickly, and demonstrate a maintained quality system.
16. What should be reviewed before a response is sent?
Review facts, evidence, commitments, wording, deadlines, and approval authority before any formal response leaves the organization.
17. What is a commitment?
A commitment is a follow-up action, correction, or deliverable that should be tracked to completion after a regulatory or quality discussion.
18. What is a controlled repository?
A controlled repository is the authoritative location for approved records, where versioning, access, and retention are governed.
19. Why start with Zeus?
Start with Zeus when a request is cross-functional or unclear, because Zeus can route it to the right specialist and keep the response aligned.
20. What should users do after reading a Q&A answer?
Apply the answer to the controlled process, verify the governing source, and escalate to the responsible specialist when the decision affects compliance.
workflow model
Hub
Zeus is ready to route work to the specialist network.
escalation layer
Standby
Kronos is available for risk acceptance and executive authority.
automation rule
Ready
Waiting for the next server-backed agent turn.
route history
Standby
No agent route is active.
No active routeidle
Live agent activity is reported by the server; no working state is simulated.
AI output is advisory until reviewed and approved in your controlled quality system.
Privacy · Security · Accessibility · Terms · Disclaimer · Editorial · Sources
Privacy · Security · Accessibility · Terms · Disclaimer · Editorial · Sources