{ "version": "1.0", "source": "Datagentics_Guardian_Public_FAQ_Ask_Datagentics_Knowledge_Base_v1.1", "principle": "Answers come from the approved Datagentics knowledge base. Not from an LLM. Not from unrestricted web content.", "synonyms": { "slm": [ "specialist language model", "language model", "small language model", "strategic language model", "slms", "specialist language models", "strategic language models", "small language models", "language models", "zmq slm", "kafka slm", "infrastructure slm", "zmq", "kafka" ], "llm": [ "large language model", "chatgpt", "gpt", "generative ai", "openai" ], "qhitl": [ "qualified and authorised human in the loop", "human in the loop", "hitl" ], "mq": [ "ibm mq", "messaging", "queue manager", "queue-manager" ], "controlled deployment": [ "poc", "proof of concept", "mvp", "trial", "pilot" ], "read-only first": [ "read only", "recommendation only", "recommend only" ], "intelligence foundation": [ "knowledge base", "learned knowledge", "context model" ], "governed by design": [ "governance", "governed" ], "operational intelligence platform": [ "oip", "guardian platform", "platform" ], "graded autonomy": [ "autonomy", "automation levels", "increasing autonomy" ], "customer secure environment": [ "on premise", "on-prem", "our environment", "inside our network", "private cloud" ], "approved product intelligence": [ "vendor knowledge", "vendor intelligence", "external knowledge" ], "sme": [ "subject matter expert", "specialist", "engineer knowledge" ], "cost": [ "price", "pricing", "spend", "budget", "expensive", "cheap", "afford", "affordable", "charge", "charges", "fee", "fees", "per token", "token cost", "token consumption" ], "token": [ "tokens", "token cost", "token consumption", "api cost", "inference cost", "per token", "token-based", "token based" ], "audit": [ "auditable", "evidence", "audit trail" ], "explain": [ "explainable", "explainability", "why", "reasoning" ], "cmdb": [ "configuration management database" ], "itsm": [ "service management", "ticketing", "servicenow" ], "z/os": [ "mainframe", "mainframes", "zos" ], "distributed": [ "distributed mq" ], "backup": [ "restore", "recovery", "dr", "disaster recovery" ], "hallucinate": [ "hallucination", "made up", "fabricate", "invent" ], "ip": [ "intellectual property", "who owns", "ownership" ], "data": [ "our data", "customer data", "operational data" ], "gpu": [ "gpus", "specialist hardware", "ai hardware" ], "footprint": [ "hardware", "size", "resource requirement", "requirements", "infrastructure" ], "high availability": [ "ha", "highly available", "resilience", "failover" ], "monitoring": [ "observability", "instrumentation", "telemetry" ], "encryption": [ "encrypted", "tls", "at rest", "in transit" ], "identity": [ "iam", "sso", "single sign on", "ad", "active directory", "ldap" ], "least privilege": [ "minimum permissions", "role based access" ], "kill switch": [ "stop", "shut off", "disable", "revoke autonomy" ], "separation of duties": [ "sod", "duty segregation" ], "cfo": [ "finance", "budget owner" ], "cio": [ "cto", "it leader", "technology leader" ], "outperform": [ "outperformance", "better performance" ], "on-call": [ "oncall", "on call", "duty engineer" ], "mttr": [ "mean time to repair", "mean time to resolve" ], "config drift": [ "configuration drift", "drift" ], "market": [ "community intelligence", "third party knowledge" ], "ibm": [ "ibm mq", "ibm products" ], "chatbot": [ "chat bot", "conversational agent" ], "hardware": [ "server", "servers", "machine", "machines", "box", "boxes", "on prem", "on-prem", "on premise", "on-premise", "on premises", "infrastructure", "environment", "estate", "footprint", "kit" ], "deploy": [ "deployed", "install", "installed", "installation", "hosted", "hosting", "run" ], "environment": [ "environments", "estate", "estates", "network", "networks", "hardware", "infrastructure", "on prem", "on-prem", "on premise" ], "servicenow": [ "service now", "snow" ], "ibm mq": [ "mq", "ibm mq", "messaging", "queue manager", "queue-manager", "queues" ], "our": [ "organisation", "customer", "enterprise", "own", "in-house" ], "infrastructure": [ "hardware", "footprint", "environment", "estate", "servers" ], "charge": [ "charges", "cost", "costs", "fee", "fees", "price", "pricing" ], "govern": [ "governance", "governed", "governance model", "governed by design", "control", "controls", "controlled", "guardrails", "policy", "policies" ], "autonomy": [ "autonomous", "automated", "automation", "graded", "gradual", "act", "action", "acting", "self-driving" ], "monitor": [ "monitoring", "observability", "instrumentation", "telemetry", "alerts", "alerting" ], "integrate": [ "integration", "integrated", "connect", "connected", "connects", "hook up", "plug in", "work with" ] }, "entries": [ { "id": 1, "section": "Guardian & the Proposition", "question": "What is Guardian?", "answer": "Guardian is Datagentics' Operational Intelligence Platform, designed to turn complex operational evidence into specialised, governed and explainable intelligence.", "status": "approved", "published": true }, { "id": 2, "section": "Guardian & the Proposition", "question": "What problem does Guardian solve?", "answer": "Technology estates generate vast amounts of data, yet diagnosis and action still depend heavily on scarce specialist expertise. Guardian helps close that intelligence gap.", "status": "approved", "published": true }, { "id": 3, "section": "Guardian & the Proposition", "question": "Who is Guardian designed for?", "answer": "Organisations operating complex, business-critical technology environments where resilience, operational control, specialist knowledge and the cost of failure matter.", "status": "approved", "published": true }, { "id": 4, "section": "Guardian & the Proposition", "question": "What types of organisations benefit most?", "answer": "Organisations with complex estates, critical services, specialist operational teams, significant resilience requirements and high operational risk.", "status": "approved", "published": true }, { "id": 5, "section": "Guardian & the Proposition", "question": "Is Guardian only for large enterprises?", "answer": "No. Complexity, criticality and the value of operational intelligence matter more than organisation size.", "status": "approved", "published": true }, { "id": 6, "section": "Guardian & the Proposition", "question": "Is Guardian suitable for regulated organisations?", "answer": "Yes. Guardian is designed around governance, control, auditability, customer isolation and human oversight, making regulated environments a natural fit.", "status": "approved", "published": true }, { "id": 7, "section": "Guardian & the Proposition", "question": "Which industries is Guardian relevant to?", "answer": "Guardian is relevant across financial services, telecommunications, utilities, healthcare and pharmaceuticals, government, transport, retail, manufacturing and other technology-dependent industries.", "status": "approved", "published": true }, { "id": 8, "section": "Guardian & the Proposition", "question": "What Guardian capability is available today?", "answer": "Guardian's initial operational specialism is IBM MQ. It is the first implementation of the wider Guardian platform approach.", "status": "approved", "published": true }, { "id": 9, "section": "Guardian & the Proposition", "question": "Is Guardian only an IBM MQ product?", "answer": "No. MQ is the first operational domain. The wider platform direction extends the same specialised, governed intelligence principles into additional technology domains over time.", "status": "approved", "published": true }, { "id": 10, "section": "Guardian & the Proposition", "question": "What is the longer-term vision for Guardian?", "answer": "A governed Operational Intelligence Platform spanning multiple enterprise technology domains while retaining specialist domain intelligence and customer control.", "status": "approved", "published": true }, { "id": 11, "section": "Guardian & the Proposition", "question": "What does Datagentics mean by Outperform?", "answer": "Guardian is designed not simply to help organisations react faster, but to improve resilience, efficiency and performance, reduce operational risk, optimise technology consumption and cost, and help organisations get more value from their technology investments.", "status": "approved", "published": true }, { "id": 12, "section": "Guardian & the Proposition", "question": "What makes an organisation a strong fit for Guardian?", "answer": "Complex technology, critical services, expensive failure, scarce specialist skills, fragmented operational evidence and strong governance requirements are all indicators of a strong fit.", "status": "approved", "published": true }, { "id": 13, "section": "Guardian & the Proposition", "question": "Is Guardian a monitoring platform?", "answer": "Guardian goes beyond monitoring. Monitoring identifies what is happening; Guardian is focused on understanding what it means, why it matters and what governed response is appropriate.", "status": "approved", "published": true }, { "id": 14, "section": "Guardian & the Proposition", "question": "Is Guardian an automation platform?", "answer": "Guardian can support a progression from sensing and recommendation toward governed action, but automation is controlled by policy, permissions and the customer's chosen level of autonomy.", "status": "approved", "published": true }, { "id": 15, "section": "Guardian & the Proposition", "question": "What is the core Guardian operating journey?", "answer": "Sense. Learn. Diagnose. Recommend. Govern. Act. The permitted journey for each use case remains controlled by the customer.", "status": "approved", "published": true }, { "id": 16, "section": "Intelligence, AI & SLM", "question": "Is Guardian an AI platform?", "answer": "Guardian uses specialised machine intelligence to understand operational environments. It is deliberately different from products built around a general-purpose Large Language Model.", "status": "approved", "published": true }, { "id": 17, "section": "Intelligence, AI & SLM", "question": "What are Datagentics' Specialist Language Models (SLMs)?", "answer": "Specialist Language Models are Datagentics' approach to operational intelligence, each specialised around a specific technology domain rather than general-purpose language generation. The Guardian zMQ SLM is the first in the family, focused on IBM MQ.", "status": "approved", "published": true }, { "id": 18, "section": "Intelligence, AI & SLM", "question": "How are Datagentics SLMs different from an LLM?", "answer": "An LLM is designed across broad language and knowledge domains. Datagentics Specialist Language Models are each specialised around a single operational domain and the environment they are helping analyse.", "status": "approved", "published": true }, { "id": 19, "section": "Intelligence, AI & SLM", "question": "Does Guardian depend on an LLM?", "answer": "No. Guardian does not depend on a Large Language Model to provide its core operational intelligence.", "status": "approved", "published": true }, { "id": 20, "section": "Intelligence, AI & SLM", "question": "Does Guardian consume AI tokens?", "answer": "Guardian's core intelligence does not depend on external token-based LLM inference.", "status": "approved", "published": true }, { "id": 21, "section": "Intelligence, AI & SLM", "question": "Does Guardian require an external generative AI service?", "answer": "No. Guardian does not require operational information to be sent to an external generative-AI service to provide its core intelligence.", "status": "approved", "published": true }, { "id": 22, "section": "Intelligence, AI & SLM", "question": "Where does Guardian's intelligence come from?", "answer": "Primarily from the customer's own operational environment, supplemented where appropriate by approved vendor, product and market intelligence.", "status": "approved", "published": true }, { "id": 23, "section": "Intelligence, AI & SLM", "question": "What is the Guardian Intelligence Foundation?", "answer": "It is the customer-specific body of relevant configuration, telemetry, operational history, patterns, dependencies and validated outcomes that gives Guardian context about the estate.", "status": "approved", "published": true }, { "id": 24, "section": "Intelligence, AI & SLM", "question": "Does Guardian need months to learn my environment?", "answer": "No. Guardian is designed to build an initial Intelligence Foundation from information already available, then enrich it through continued operation and validated outcomes.", "status": "approved", "published": true }, { "id": 25, "section": "Intelligence, AI & SLM", "question": "How quickly can Guardian become useful?", "answer": "Existing estate information, telemetry and history can provide an immediate starting point. The exact time to value depends on the scope and quality of available evidence.", "status": "approved", "published": true }, { "id": 26, "section": "Intelligence, AI & SLM", "question": "Can SME knowledge contribute to Guardian?", "answer": "Yes. Specialist knowledge and validated SME feedback can contribute to a controlled operational intelligence model.", "status": "approved", "published": true }, { "id": 27, "section": "Intelligence, AI & SLM", "question": "How does Guardian learn from outcomes?", "answer": "Validated outcomes can strengthen or challenge the knowledge associated with operational patterns and recommendations rather than every previous action being assumed correct.", "status": "approved", "published": true }, { "id": 28, "section": "Intelligence, AI & SLM", "question": "Can bad information become trusted knowledge?", "answer": "Guardian is designed around validation and governance rather than automatically accepting every observation, external source or user interaction as truth.", "status": "approved", "published": true }, { "id": 29, "section": "Intelligence, AI & SLM", "question": "What happens when Guardian does not know?", "answer": "It does not need to invent an answer. Insufficient evidence or confidence can be surfaced while keeping the decision with a qualified and authorised human.", "status": "approved", "published": true }, { "id": 30, "section": "Intelligence, AI & SLM", "question": "Can Guardian explain why it reached a conclusion?", "answer": "Yes. Explainability is a core design principle, with recommendations intended to be supported by relevant evidence and context.", "status": "approved", "published": true }, { "id": 31, "section": "Intelligence, AI & SLM", "question": "Can Guardian show the evidence behind a recommendation?", "answer": "Yes. Guardian is designed to expose supporting evidence rather than operate as an unexplained black box.", "status": "approved", "published": true }, { "id": 32, "section": "Intelligence, AI & SLM", "question": "How does Guardian address hallucination?", "answer": "Guardian's specialised, evidence-led approach avoids depending on a general-purpose LLM to generate core operational conclusions.", "status": "approved", "published": true }, { "id": 33, "section": "Intelligence, AI & SLM", "question": "Does Guardian distinguish evidence from assumptions?", "answer": "Yes. Guardian is designed to reason from available evidence and surface uncertainty rather than present unsupported assumptions as facts.", "status": "approved", "published": true }, { "id": 34, "section": "Intelligence, AI & SLM", "question": "Can Guardian express confidence?", "answer": "Guardian is designed to communicate the evidence and confidence associated with findings.", "status": "validate", "validate_note": "exact presentation before publication", "published": false }, { "id": 35, "section": "Intelligence, AI & SLM", "question": "Can Guardian use external product intelligence?", "answer": "Yes. Approved product intelligence can enrich its understanding of the technologies it supports.", "status": "approved", "published": true }, { "id": 36, "section": "Intelligence, AI & SLM", "question": "Can Guardian use IBM product intelligence?", "answer": "Yes. Relevant IBM lifecycle, fix, security and product information can contribute where approved and applicable.", "status": "approved", "published": true }, { "id": 37, "section": "Intelligence, AI & SLM", "question": "Can Guardian use wider market or community intelligence?", "answer": "Approved external sources can contribute where appropriate, but public information does not automatically become trusted operational knowledge.", "status": "approved", "published": true }, { "id": 38, "section": "Intelligence, AI & SLM", "question": "How does Guardian decide which sources to trust?", "answer": "Source authority, relevance, provenance and validation govern how information can contribute. Detailed weighting mechanisms remain Datagentics proprietary IP.", "status": "approved", "published": true }, { "id": 39, "section": "Intelligence, AI & SLM", "question": "What happens when two sources disagree?", "answer": "Guardian is designed to consider source authority, customer context and the quality of available evidence rather than blindly selecting one source.", "status": "approved", "published": true }, { "id": 40, "section": "Intelligence, AI & SLM", "question": "Can external information trigger an uncontrolled production action?", "answer": "No. An external information source by itself does not provide authority to perform an operational action. Actions remain subject to policy, permissions and governance.", "status": "approved", "published": true }, { "id": 41, "section": "Intelligence, AI & SLM", "question": "Can customers control external intelligence sources?", "answer": "External connectivity and approved sources can be governed according to customer security and operational policy.", "status": "validate", "validate_note": "implementation detail", "published": false }, { "id": 42, "section": "Intelligence, AI & SLM", "question": "Does Guardian automatically learn from every question a user asks?", "answer": "No. A question or interaction does not automatically become validated knowledge. New knowledge can pass through controlled review and validation.", "status": "approved", "published": true }, { "id": 43, "section": "Intelligence, AI & SLM", "question": "Can incorrect knowledge be challenged?", "answer": "The design principle is that operational knowledge remains governable and challengeable rather than permanently accepted because it appeared once.", "status": "validate", "validate_note": "workflow", "published": false }, { "id": 44, "section": "Intelligence, AI & SLM", "question": "How is outdated knowledge handled?", "answer": "Knowledge needs provenance, currency and validation so that outdated information can be identified and superseded.", "status": "validate", "validate_note": "implementation detail", "published": false }, { "id": 45, "section": "Intelligence, AI & SLM", "question": "Can I see where intelligence came from?", "answer": "Provenance and explainability are important design principles, allowing relevant evidence to be traced to its source.", "status": "validate", "validate_note": "exact user experience", "published": false }, { "id": 46, "section": "Deployment, Data & Privacy", "question": "Where is Guardian deployed?", "answer": "Guardian is installed within the customer's own secure technology environment.", "status": "approved", "published": true }, { "id": 47, "section": "Deployment, Data & Privacy", "question": "Does Guardian run inside my organisation's secure environment?", "answer": "Yes. This is fundamental to the enterprise deployment model.", "status": "approved", "published": true }, { "id": 48, "section": "Deployment, Data & Privacy", "question": "Is Guardian SaaS?", "answer": "For enterprise environments such as financial institutions, Guardian is deployed within the customer's controlled environment rather than relying on a shared external intelligence service.", "status": "approved", "published": true }, { "id": 49, "section": "Deployment, Data & Privacy", "question": "Does operational data need to leave my environment?", "answer": "Guardian's core operational intelligence is designed to operate within the customer environment.", "status": "approved", "published": true }, { "id": 50, "section": "Deployment, Data & Privacy", "question": "Is my operational data sent to an external LLM?", "answer": "No. Guardian does not require operational information to be sent to an external LLM to provide its core intelligence.", "status": "approved", "published": true }, { "id": 51, "section": "Deployment, Data & Privacy", "question": "Does Datagentics require permanent production access?", "answer": "Guardian operates within the customer's security and access model. Datagentics personnel do not inherently require unrestricted or permanent production access.", "status": "validate", "validate_note": "support model", "published": false }, { "id": 52, "section": "Deployment, Data & Privacy", "question": "What data does Guardian need?", "answer": "Only information relevant to building operational understanding for the approved technology domain and use case. Exact requirements are established during discovery.", "status": "approved", "published": true }, { "id": 53, "section": "Deployment, Data & Privacy", "question": "Who owns customer operational data?", "answer": "The customer retains ownership of its operational data.", "status": "validate", "validate_note": "contractual wording", "published": false }, { "id": 54, "section": "Deployment, Data & Privacy", "question": "Is customer intelligence isolated?", "answer": "Yes. Customer operational environments and customer-specific intelligence are isolated.", "status": "approved", "published": true }, { "id": 55, "section": "Deployment, Data & Privacy", "question": "Is one customer's information used to train another customer's Guardian?", "answer": "Customer operational information is not designed to become another customer's operational intelligence.", "status": "approved", "published": true }, { "id": 56, "section": "Deployment, Data & Privacy", "question": "Can Guardian operate with restricted external connectivity?", "answer": "The architecture is designed for controlled enterprise environments. Exact connectivity depends on deployment and approved external intelligence sources.", "status": "validate", "published": false }, { "id": 57, "section": "Deployment, Data & Privacy", "question": "Does Guardian need unrestricted internet access?", "answer": "No unrestricted internet access is assumed. External information sources can be governed according to customer security policy.", "status": "validate", "validate_note": "implementation", "published": false }, { "id": 58, "section": "Deployment, Data & Privacy", "question": "What information does Guardian retain?", "answer": "Operational information required to provide approved intelligence and evidence functions. Retention requirements are established according to deployment and customer policy.", "status": "validate", "published": false }, { "id": 59, "section": "Deployment, Data & Privacy", "question": "Can customers control retention?", "answer": "Customer governance and retention requirements form part of deployment design.", "status": "validate", "validate_note": "implementation", "published": false }, { "id": 60, "section": "Deployment, Data & Privacy", "question": "What happens to my data if Guardian is removed?", "answer": "Customer information is handled according to agreed retention, export and deletion requirements.", "status": "validate", "validate_note": "product and contractual process", "published": false }, { "id": 61, "section": "Deployment, Data & Privacy", "question": "Does Guardian send telemetry back to Datagentics?", "answer": "Its core operational intelligence is designed to reside within the customer's environment.", "status": "validate", "validate_note": "support and diagnostic telemetry position", "published": false }, { "id": 62, "section": "Deployment, Data & Privacy", "question": "Can customer data be used for Datagentics marketing or unrelated purposes?", "answer": "Customer operational information is governed by the customer agreement and is not treated as unrestricted Datagentics content.", "status": "validate", "validate_note": "legal wording", "published": false }, { "id": 63, "section": "Deployment, Data & Privacy", "question": "How is data minimisation applied?", "answer": "Guardian is designed to use information relevant to the approved operational purpose rather than collecting data without a defined need.", "status": "approved", "published": true }, { "id": 64, "section": "Infrastructure & Architecture", "question": "What infrastructure does Guardian require?", "answer": "Guardian has been designed to maintain a relatively small infrastructure footprint compared with large general-purpose AI platforms.", "status": "approved", "published": true }, { "id": 65, "section": "Infrastructure & Architecture", "question": "What is Guardian's indicative footprint?", "answer": "Evaluation deployments can be assessed around 2-4 vCPU and 8-16 GB RAM, with controlled enterprise deployments around 4-8 vCPU and 16-32 GB RAM. Actual sizing depends on scope.", "status": "validate", "validate_note": "before publication", "published": false }, { "id": 66, "section": "Infrastructure & Architecture", "question": "Why is the footprint relatively small?", "answer": "Guardian uses specialised operational intelligence rather than requiring large general-purpose LLM infrastructure.", "status": "approved", "published": true }, { "id": 67, "section": "Infrastructure & Architecture", "question": "Does Guardian require GPUs?", "answer": "The current Guardian MQ architecture does not rely on large GPU infrastructure.", "status": "validate", "validate_note": "absolute wording", "published": false }, { "id": 68, "section": "Infrastructure & Architecture", "question": "Does Guardian require specialist AI hardware?", "answer": "The current design does not depend on large specialist AI compute infrastructure.", "status": "validate", "published": false }, { "id": 69, "section": "Infrastructure & Architecture", "question": "How does Guardian scale?", "answer": "Guardian is designed to scale operational intelligence across enterprise estates while controlling interaction with the systems being observed.", "status": "approved", "published": true }, { "id": 70, "section": "Infrastructure & Architecture", "question": "Does Guardian support z/OS and distributed MQ?", "answer": "Guardian MQ is designed around enterprise MQ estates spanning z/OS and distributed environments.", "status": "validate", "validate_note": "current supported connectivity versus target", "published": false }, { "id": 71, "section": "Infrastructure & Architecture", "question": "How does Guardian connect to the estate?", "answer": "Through controlled interfaces and permissions appropriate to the technology being observed.", "status": "approved", "published": true }, { "id": 72, "section": "Infrastructure & Architecture", "question": "Does Guardian create a production dependency?", "answer": "Guardian is designed to sit outside the application's critical message path.", "status": "approved", "published": true }, { "id": 73, "section": "Infrastructure & Architecture", "question": "Does Guardian sit in the MQ message path?", "answer": "No.", "status": "approved", "published": true }, { "id": 74, "section": "Infrastructure & Architecture", "question": "What happens if Guardian becomes unavailable?", "answer": "Because Guardian sits outside the application message path, its failure is designed not to interrupt underlying business message flow.", "status": "approved", "published": true }, { "id": 75, "section": "Infrastructure & Architecture", "question": "What happens if connectivity is lost?", "answer": "Guardian is designed to handle connectivity failure safely rather than turn a loss of visibility into an uncontrolled action.", "status": "approved", "published": true }, { "id": 76, "section": "Infrastructure & Architecture", "question": "How does Guardian protect source systems?", "answer": "Collection is designed to be bounded using appropriate frequency, caching, deltas where available, rate controls, back-off and circuit-breaking principles.", "status": "approved", "published": true }, { "id": 77, "section": "Infrastructure & Architecture", "question": "What happens when the underlying platform is stressed?", "answer": "Guardian's source interaction is designed to back off rather than add uncontrolled load.", "status": "approved", "published": true }, { "id": 78, "section": "Infrastructure & Architecture", "question": "Can Guardian coexist with existing enterprise tooling?", "answer": "Yes. Guardian is designed to complement monitoring, observability, service-management and vendor tooling.", "status": "approved", "published": true }, { "id": 79, "section": "Infrastructure & Architecture", "question": "Is Guardian highly available?", "answer": "Enterprise resilience is part of the deployment design.", "status": "validate", "validate_note": "supported HA architecture", "published": false }, { "id": 80, "section": "Infrastructure & Architecture", "question": "Can Guardian be backed up and recovered?", "answer": "Backup and recovery need to form part of the enterprise deployment model.", "status": "validate", "validate_note": "exact capability", "published": false }, { "id": 81, "section": "Infrastructure & Architecture", "question": "What are Guardian's recovery objectives?", "answer": "", "status": "validate", "validate_note": "RTO/RPO before publication", "published": false }, { "id": 82, "section": "Infrastructure & Architecture", "question": "Can Guardian operate across multiple sites?", "answer": "", "status": "validate", "validate_note": "deployment topology before publication", "published": false }, { "id": 83, "section": "Infrastructure & Architecture", "question": "Does Guardian introduce a single point of failure?", "answer": "Guardian is outside the critical application path, so its availability is not intended to become a single point of failure for the underlying service.", "status": "approved", "published": true }, { "id": 84, "section": "Infrastructure & Architecture", "question": "How is Guardian upgraded?", "answer": "Product upgrades are intended to be controlled within the customer's enterprise change process.", "status": "validate", "validate_note": "release mechanism", "published": false }, { "id": 85, "section": "Infrastructure & Architecture", "question": "Can upgrades be tested before production?", "answer": "Enterprise deployment should allow changes to be validated through appropriate non-production controls.", "status": "validate", "validate_note": "supported process", "published": false }, { "id": 86, "section": "Infrastructure & Architecture", "question": "What happens if a Guardian upgrade fails?", "answer": "Upgrade and rollback behaviour must be defined as part of the supported product lifecycle.", "status": "validate", "published": false }, { "id": 87, "section": "Infrastructure & Architecture", "question": "How are vulnerabilities and security updates handled?", "answer": "Guardian requires a governed product maintenance and security update process.", "status": "validate", "validate_note": "published support policy", "published": false }, { "id": 88, "section": "IBM MQ Safety & Operations", "question": "Does Guardian read business message content?", "answer": "Guardian is designed to understand MQ operational condition without relying on access to business message payloads.", "status": "approved", "published": true }, { "id": 89, "section": "IBM MQ Safety & Operations", "question": "Does Guardian need access to message payloads?", "answer": "No business-message payload access is required for Guardian's core MQ operational intelligence.", "status": "approved", "published": true }, { "id": 90, "section": "IBM MQ Safety & Operations", "question": "Can Guardian affect application message flow?", "answer": "Guardian sits outside the MQ message path.", "status": "approved", "published": true }, { "id": 91, "section": "IBM MQ Safety & Operations", "question": "What MQ permissions does Guardian require?", "answer": "Permissions depend on the approved use case and deployment stage, beginning from a least-privilege and read-only position.", "status": "approved", "published": true }, { "id": 92, "section": "IBM MQ Safety & Operations", "question": "Can Guardian start completely read-only?", "answer": "Yes. Read-only sensing is a fundamental starting position.", "status": "approved", "published": true }, { "id": 93, "section": "IBM MQ Safety & Operations", "question": "Does Guardian change queue-manager configuration when connected?", "answer": "No. Any permitted operational action is separately governed.", "status": "approved", "published": true }, { "id": 94, "section": "IBM MQ Safety & Operations", "question": "How does Guardian avoid excessive polling?", "answer": "Through bounded source interaction, appropriate collection frequencies, caching, deltas, rate controls and back-off.", "status": "approved", "published": true }, { "id": 95, "section": "IBM MQ Safety & Operations", "question": "Can Guardian work alongside existing MQ monitoring?", "answer": "Yes.", "status": "approved", "published": true }, { "id": 96, "section": "IBM MQ Safety & Operations", "question": "How does Guardian identify developing MQ risk?", "answer": "By combining operational evidence, estate understanding, patterns and relevant product intelligence to identify conditions that warrant attention.", "status": "approved", "published": true }, { "id": 97, "section": "IBM MQ Safety & Operations", "question": "How does Guardian deal with dead-letter queue scenarios?", "answer": "DLQ conditions are examples Guardian can help identify, diagnose and govern recommendations around.", "status": "approved", "published": true }, { "id": 98, "section": "IBM MQ Safety & Operations", "question": "How does Guardian deal with backout queues?", "answer": "Backout handling is an operational condition Guardian can help analyse within the customer's policies and application context.", "status": "approved", "published": true }, { "id": 99, "section": "IBM MQ Safety & Operations", "question": "Can Guardian support infrastructure teams that must not access business data?", "answer": "Yes. Separation between MQ infrastructure operations and business-message content is an important Guardian MQ design principle.", "status": "approved", "published": true }, { "id": 100, "section": "IBM MQ Safety & Operations", "question": "Can Guardian manipulate business messages?", "answer": "Guardian's core MQ intelligence does not depend on manipulating business payloads. Any specific operational action must be explicitly governed.", "status": "validate", "validate_note": "supported actions", "published": false }, { "id": 101, "section": "IBM MQ Safety & Operations", "question": "Can Guardian identify MAXMSGL-related conditions?", "answer": "Guardian can use estate configuration and operational evidence to help identify conditions such as message-size constraints where relevant.", "status": "validate", "validate_note": "current detection", "published": false }, { "id": 102, "section": "IBM MQ Safety & Operations", "question": "Can Guardian understand queue-manager-level monitoring settings?", "answer": "MQ configuration and monitoring settings can contribute to estate understanding.", "status": "validate", "validate_note": "exact current coverage", "published": false }, { "id": 103, "section": "IBM MQ Safety & Operations", "question": "Does Guardian support queue-sharing groups and clusters?", "answer": "These are relevant enterprise MQ estate constructs.", "status": "validate", "validate_note": "current supported depth", "published": false }, { "id": 104, "section": "Security, Governance & Guardrails", "question": "How is Guardian secured?", "answer": "Guardian operates within the customer's security boundary and is designed around controlled access, least privilege, isolation, governance and auditability.", "status": "approved", "published": true }, { "id": 105, "section": "Security, Governance & Guardrails", "question": "What access does Guardian require?", "answer": "Only the access required for the approved operational use case.", "status": "approved", "published": true }, { "id": 106, "section": "Security, Governance & Guardrails", "question": "Does Guardian use least privilege?", "answer": "Yes. Least privilege is a core security principle.", "status": "approved", "published": true }, { "id": 107, "section": "Security, Governance & Guardrails", "question": "Can permissions differ by environment?", "answer": "Yes. Guardian's policy model is designed to support controls appropriate to different environments and use cases.", "status": "approved", "published": true }, { "id": 108, "section": "Security, Governance & Guardrails", "question": "How are credentials and secrets protected?", "answer": "Guardian is designed to operate within enterprise credential and secret-management controls.", "status": "validate", "validate_note": "implementation", "published": false }, { "id": 109, "section": "Security, Governance & Guardrails", "question": "Is data encrypted in transit and at rest?", "answer": "Enterprise deployments are designed around secure transport and storage.", "status": "validate", "validate_note": "exact standards before publication", "published": false }, { "id": 110, "section": "Security, Governance & Guardrails", "question": "Can Guardian integrate with enterprise IAM?", "answer": "The deployment model is designed to work within enterprise security controls.", "status": "validate", "validate_note": "supported integrations", "published": false }, { "id": 111, "section": "Security, Governance & Guardrails", "question": "What does Governed by Design mean?", "answer": "Governance is part of how Guardian operates rather than something added after intelligence or automation has been introduced.", "status": "approved", "published": true }, { "id": 112, "section": "Security, Governance & Guardrails", "question": "What guardrails exist around Guardian?", "answer": "Guardian operates within defined policies, permissions, environments, use cases and approval boundaries.", "status": "approved", "published": true }, { "id": 113, "section": "Security, Governance & Guardrails", "question": "Who controls what Guardian can do?", "answer": "The customer controls the operational permissions and governance boundaries within which Guardian operates.", "status": "approved", "published": true }, { "id": 114, "section": "Security, Governance & Guardrails", "question": "Can customers define their own policies?", "answer": "The policy model is designed to reflect enterprise and operational requirements.", "status": "approved", "published": true }, { "id": 115, "section": "Security, Governance & Guardrails", "question": "Can controls vary by service, application or environment?", "answer": "Yes. The policy approach is designed to support layered controls and appropriate inheritance or override.", "status": "approved", "published": true }, { "id": 116, "section": "Security, Governance & Guardrails", "question": "Can an action be prohibited completely?", "answer": "Yes. Policy can prevent an action from being available.", "status": "approved", "published": true }, { "id": 117, "section": "Security, Governance & Guardrails", "question": "What is QHITL?", "answer": "QHITL means Qualified and Authorised Human in the Loop. It ensures that where human judgement or approval is required, the decision remains with an appropriately qualified individual who also has the authority to approve that decision or action within the organisation's governance model.", "status": "approved", "published": true }, { "id": 118, "section": "Security, Governance & Guardrails", "question": "When is qualified and authorised human approval required?", "answer": "According to policy, risk and the permitted level of autonomy established for that use case.", "status": "approved", "published": true }, { "id": 119, "section": "Security, Governance & Guardrails", "question": "Can Guardian recommend without acting?", "answer": "Yes.", "status": "approved", "published": true }, { "id": 120, "section": "Security, Governance & Guardrails", "question": "Can Guardian remain permanently recommendation-only?", "answer": "Yes. The organisation retains control over the permitted level of autonomy.", "status": "approved", "published": true }, { "id": 121, "section": "Security, Governance & Guardrails", "question": "Can Guardian perform approved operational actions?", "answer": "Guardian's architecture is designed to support governed operational actions where explicitly permitted. Current action capabilities depend on the supported use case.", "status": "validate", "published": false }, { "id": 122, "section": "Security, Governance & Guardrails", "question": "Can autonomy increase gradually?", "answer": "Yes. The model supports graded autonomy rather than forcing a move directly from observation to automation.", "status": "approved", "published": true }, { "id": 123, "section": "Security, Governance & Guardrails", "question": "Can autonomy be withdrawn?", "answer": "The customer retains governance control over permitted actions.", "status": "approved", "published": true }, { "id": 124, "section": "Security, Governance & Guardrails", "question": "Are recommendations and actions auditable?", "answer": "Auditability is fundamental to the operating model.", "status": "approved", "published": true }, { "id": 125, "section": "Security, Governance & Guardrails", "question": "Can a qualified and authorised human see why Guardian made a recommendation?", "answer": "Yes. Guardian is designed around explainable rather than opaque operational intelligence.", "status": "approved", "published": true }, { "id": 126, "section": "Security, Governance & Guardrails", "question": "How are people kept in control?", "answer": "Through policy, permissions, evidence, QHITL, approval and graded autonomy.", "status": "approved", "published": true }, { "id": 127, "section": "Security, Governance & Guardrails", "question": "Is there a kill switch or immediate return to read-only?", "answer": "A rapid control mechanism is an important enterprise requirement.", "status": "validate", "validate_note": "exact implementation", "published": false }, { "id": 128, "section": "Security, Governance & Guardrails", "question": "Can Guardian support separation of duties?", "answer": "The governance model is intended to work with enterprise role and approval boundaries.", "status": "validate", "validate_note": "exact controls", "published": false }, { "id": 129, "section": "Resilience, Knowledge & Operating Model", "question": "How does Guardian improve operational resilience?", "answer": "By helping teams identify developing conditions earlier, diagnose faster, preserve specialist knowledge and apply more consistent governed responses.", "status": "approved", "published": true }, { "id": 130, "section": "Resilience, Knowledge & Operating Model", "question": "Can Guardian identify problems before incidents occur?", "answer": "Guardian is designed to identify developing risks and patterns where available evidence supports doing so.", "status": "approved", "published": true }, { "id": 131, "section": "Resilience, Knowledge & Operating Model", "question": "How does Guardian help reduce MTTR?", "answer": "By reducing the time needed to assemble evidence, understand context and reach a governed operational recommendation.", "status": "approved", "published": true }, { "id": 132, "section": "Resilience, Knowledge & Operating Model", "question": "Can Guardian help prevent repeat incidents?", "answer": "Validated incident knowledge and outcomes can strengthen future operational understanding.", "status": "approved", "published": true }, { "id": 133, "section": "Resilience, Knowledge & Operating Model", "question": "Can Guardian identify configuration drift?", "answer": "Configuration and estate condition form part of the operational intelligence opportunity.", "status": "validate", "validate_note": "current capability", "published": false }, { "id": 134, "section": "Resilience, Knowledge & Operating Model", "question": "Can Guardian correlate changes with developing problems?", "answer": "Operational history and relevant changes can contribute to diagnosis.", "status": "validate", "validate_note": "current capability", "published": false }, { "id": 135, "section": "Resilience, Knowledge & Operating Model", "question": "What happens when Guardian sees something new?", "answer": "It evaluates the available evidence and does not need to pretend that an unfamiliar condition is already understood.", "status": "approved", "published": true }, { "id": 136, "section": "Resilience, Knowledge & Operating Model", "question": "Can Guardian capture SME knowledge?", "answer": "Yes. Capturing and progressively retaining specialist operational capability is an important part of the proposition.", "status": "approved", "published": true }, { "id": 137, "section": "Resilience, Knowledge & Operating Model", "question": "Does Guardian replace SMEs?", "answer": "Guardian is designed to amplify specialist capability, preserve knowledge and reduce repetitive dependency rather than simply replace expertise.", "status": "approved", "published": true }, { "id": 138, "section": "Resilience, Knowledge & Operating Model", "question": "Can Guardian help less-experienced engineers?", "answer": "Yes. Governed access to specialist operational intelligence can help teams make more informed decisions while retaining appropriate controls.", "status": "approved", "published": true }, { "id": 139, "section": "Resilience, Knowledge & Operating Model", "question": "What happens when experienced engineers leave?", "answer": "Guardian creates an opportunity to retain validated operational knowledge and patterns that might otherwise leave with individuals.", "status": "approved", "published": true }, { "id": 140, "section": "Resilience, Knowledge & Operating Model", "question": "Does Guardian help on-call teams?", "answer": "Faster access to evidence, diagnosis and validated knowledge can reduce dependency on finding the right specialist during an incident.", "status": "approved", "published": true }, { "id": 141, "section": "Resilience, Knowledge & Operating Model", "question": "Does Guardian move operations from reactive to proactive?", "answer": "That is a central objective: progressing from sensing problems to understanding developing risk and helping organisations act earlier.", "status": "approved", "published": true }, { "id": 142, "section": "Resilience, Knowledge & Operating Model", "question": "Can Guardian reduce key-person dependency?", "answer": "Yes. Capturing validated specialist knowledge can make operational capability less dependent on a small number of individuals.", "status": "approved", "published": true }, { "id": 143, "section": "Resilience, Knowledge & Operating Model", "question": "Does Guardian remove accountability from people?", "answer": "No. Customer policy, permissions and governance retain human accountability and control.", "status": "approved", "published": true }, { "id": 144, "section": "Resilience, Knowledge & Operating Model", "question": "How does Guardian change the role of an SME?", "answer": "It can shift specialist effort from repeatedly solving familiar problems toward validating knowledge, improving operational patterns and addressing genuinely novel or high-value work.", "status": "approved", "published": true }, { "id": 145, "section": "Integration & Existing Tooling", "question": "Does Guardian replace monitoring?", "answer": "Not necessarily. Monitoring tells organisations what is happening; Guardian focuses on what it means, why it matters and what governed response is appropriate.", "status": "approved", "published": true }, { "id": 146, "section": "Integration & Existing Tooling", "question": "Does Guardian replace observability?", "answer": "No. Guardian can build on existing operational evidence rather than requiring organisations to discard useful investments.", "status": "approved", "published": true }, { "id": 147, "section": "Integration & Existing Tooling", "question": "Does Guardian replace IBM MQ tooling?", "answer": "Guardian complements the underlying platform and relevant vendor tooling with a specialised operational intelligence layer.", "status": "approved", "published": true }, { "id": 148, "section": "Integration & Existing Tooling", "question": "Why introduce another platform?", "answer": "Enterprises often already have extensive telemetry but still depend on scarce human expertise to turn that information into diagnosis and action. Guardian targets that intelligence gap.", "status": "approved", "published": true }, { "id": 149, "section": "Integration & Existing Tooling", "question": "Can Guardian reuse existing data?", "answer": "Yes. Reusing estate information, telemetry and history is an important part of building the Intelligence Foundation.", "status": "approved", "published": true }, { "id": 150, "section": "Integration & Existing Tooling", "question": "Can Guardian use historical incident information?", "answer": "Yes, where available, relevant and approved.", "status": "approved", "published": true }, { "id": 151, "section": "Integration & Existing Tooling", "question": "Does Guardian integrate with ITSM?", "answer": "Integration with enterprise service-management processes forms part of the Guardian operating model.", "status": "approved", "published": true }, { "id": 152, "section": "Integration & Existing Tooling", "question": "Does Guardian integrate with ServiceNow?", "answer": "ServiceNow is an identified integration within the Guardian direction.", "status": "validate", "validate_note": "current integration status before describing as live", "published": false }, { "id": 153, "section": "Integration & Existing Tooling", "question": "Can Guardian use CMDB or service information?", "answer": "Service and dependency context can enrich operational reasoning.", "status": "validate", "validate_note": "current implementation", "published": false }, { "id": 154, "section": "Integration & Existing Tooling", "question": "Does Guardian expose APIs?", "answer": "Integration interfaces form part of the enterprise platform approach.", "status": "validate", "validate_note": "current API scope", "published": false }, { "id": 155, "section": "Integration & Existing Tooling", "question": "How does Guardian fit with observability platforms?", "answer": "As an intelligence and governance layer that can make use of relevant operational evidence rather than replacing every source system.", "status": "approved", "published": true }, { "id": 156, "section": "Integration & Existing Tooling", "question": "Why not simply add AI to our monitoring platform?", "answer": "Guardian is not a generic AI interface placed over monitoring data. It is designed around specialised operational intelligence, evidence, governance, domain knowledge and controlled action.", "status": "approved", "published": true }, { "id": 157, "section": "Integration & Existing Tooling", "question": "Can Guardian integrate with Jira or workflow tools?", "answer": "Workflow integration is part of the wider operating model.", "status": "validate", "validate_note": "current integrations", "published": false }, { "id": 158, "section": "Integration & Existing Tooling", "question": "Can Guardian reuse existing extracts rather than connect directly?", "answer": "Yes. Existing estate extracts can provide useful discovery and intelligence inputs where direct connectivity is not yet appropriate.", "status": "approved", "published": true }, { "id": 159, "section": "FinOps, Capacity & Optimisation", "question": "How can Guardian help reduce technology cost?", "answer": "Operational intelligence can identify opportunities to reduce waste, improve utilisation and get greater value from existing technology investments.", "status": "approved", "published": true }, { "id": 160, "section": "FinOps, Capacity & Optimisation", "question": "Does Guardian support FinOps?", "answer": "FinOps forms part of the wider Guardian optimisation direction, connecting operational intelligence with technology consumption and cost.", "status": "roadmap", "published": true }, { "id": 161, "section": "FinOps, Capacity & Optimisation", "question": "Can Guardian identify unused or over-provisioned infrastructure?", "answer": "This forms part of the wider Guardian infrastructure and optimisation direction rather than the current Guardian MQ capability.", "status": "roadmap", "published": true }, { "id": 162, "section": "FinOps, Capacity & Optimisation", "question": "Can Guardian connect operational decisions to financial impact?", "answer": "The platform direction includes bringing operational and financial intelligence closer together so technology teams can understand both technical and cost impact.", "status": "roadmap", "published": true }, { "id": 163, "section": "FinOps, Capacity & Optimisation", "question": "Can Guardian help optimise cloud consumption?", "answer": "Cloud consumption and cost optimisation form part of the wider platform direction.", "status": "roadmap", "published": true }, { "id": 164, "section": "FinOps, Capacity & Optimisation", "question": "Can Guardian help optimise data-centre resources?", "answer": "Infrastructure utilisation, capacity and cost optimisation form part of the wider platform direction.", "status": "roadmap", "published": true }, { "id": 165, "section": "FinOps, Capacity & Optimisation", "question": "Can Guardian help with compute, storage and network utilisation?", "answer": "These are intended areas for the wider Guardian infrastructure intelligence direction.", "status": "roadmap", "published": true }, { "id": 166, "section": "FinOps, Capacity & Optimisation", "question": "Can Guardian help with energy and power constraints?", "answer": "The wider infrastructure direction can include operational intelligence around capacity, power and resource utilisation.", "status": "roadmap", "published": true }, { "id": 167, "section": "FinOps, Capacity & Optimisation", "question": "Is Guardian only about reducing headcount?", "answer": "No. Value can come from resilience, issue avoidance, productivity, capacity, technology optimisation, knowledge retention and better use of specialist people as well as cost reduction.", "status": "approved", "published": true }, { "id": 168, "section": "FinOps, Capacity & Optimisation", "question": "How does Guardian support the CFO conversation?", "answer": "By connecting technology operations to measurable cost, risk, productivity and value outcomes rather than treating operational intelligence as a purely technical benefit.", "status": "approved", "published": true }, { "id": 169, "section": "FinOps, Capacity & Optimisation", "question": "How does Guardian support the CIO conversation?", "answer": "By connecting operational resilience, technology performance, specialist dependency, cost and governance into a clearer operational picture.", "status": "approved", "published": true }, { "id": 170, "section": "FinOps, Capacity & Optimisation", "question": "Can Guardian help identify where enterprise support spend can be reduced?", "answer": "Operational intelligence may identify opportunities to optimise support and technology spend, but any benefit needs to be evidenced against the customer's environment rather than assumed.", "status": "approved", "published": true }, { "id": 171, "section": "Business Value & Measurement", "question": "How does Guardian create measurable business value?", "answer": "Potential value includes reduced incident impact, faster diagnosis, issue avoidance, greater productivity, better use of specialist expertise, cost optimisation and improved resilience.", "status": "approved", "published": true }, { "id": 172, "section": "Business Value & Measurement", "question": "How can Guardian reduce operational cost?", "answer": "By reducing repetitive effort, specialist dependency, incident impact and avoidable operational waste.", "status": "approved", "published": true }, { "id": 173, "section": "Business Value & Measurement", "question": "How can Guardian improve resilience?", "answer": "By improving visibility, diagnosis, knowledge retention, consistency and the ability to act on developing risk.", "status": "approved", "published": true }, { "id": 174, "section": "Business Value & Measurement", "question": "Can Guardian reduce the cost of incidents?", "answer": "Faster diagnosis, earlier detection and repeat-incident prevention can reduce the operational and business impact of incidents.", "status": "approved", "published": true }, { "id": 175, "section": "Business Value & Measurement", "question": "Can Guardian help organisations get more value from existing investments?", "answer": "Yes. Guardian is designed to use and enrich existing operational evidence rather than requiring wholesale replacement of useful tooling.", "status": "approved", "published": true }, { "id": 176, "section": "Business Value & Measurement", "question": "How does Guardian improve productivity?", "answer": "By reducing time spent assembling evidence, repeating diagnosis and locating scarce specialist knowledge.", "status": "approved", "published": true }, { "id": 177, "section": "Business Value & Measurement", "question": "How does Guardian help leaders understand operational risk?", "answer": "By translating operational evidence into clearer, governed intelligence about condition, developing risk and required attention.", "status": "approved", "published": true }, { "id": 178, "section": "Business Value & Measurement", "question": "How is Guardian's value measured?", "answer": "Against agreed baselines such as incident frequency and duration, operational effort, specialist dependency, risk exposure, technology consumption and customer-specific outcomes.", "status": "approved", "published": true }, { "id": 179, "section": "Business Value & Measurement", "question": "How do we build a benefits case?", "answer": "Discovery establishes the estate, pain points, current operating model and measurable baselines, which can then be tested during a Controlled Deployment.", "status": "approved", "published": true }, { "id": 180, "section": "Business Value & Measurement", "question": "How does Guardian help an organisation become more competitive?", "answer": "By helping technology operations become more resilient, efficient, cost-aware and capable of supporting business change with less operational friction.", "status": "approved", "published": true }, { "id": 181, "section": "Business Value & Measurement", "question": "Does Guardian guarantee savings?", "answer": "No generic savings figure can represent every estate. Benefits need to be evidenced against the customer's own baseline and outcomes.", "status": "approved", "published": true }, { "id": 182, "section": "Commercial Model & Procurement", "question": "What drives the cost of running Guardian?", "answer": "The commercial model is intended to be predictable and aligned to the scope and value of the platform rather than uncontrolled external AI consumption.", "status": "validate", "validate_note": "final model", "published": false }, { "id": 183, "section": "Commercial Model & Procurement", "question": "Are there external LLM or token charges?", "answer": "Guardian's core intelligence does not depend on external LLM token consumption.", "status": "approved", "published": true }, { "id": 184, "section": "Commercial Model & Procurement", "question": "Can AI costs unexpectedly increase as engineers ask more questions?", "answer": "Guardian avoids a core architecture in which every operational interaction inherently generates an external LLM token cost.", "status": "approved", "published": true }, { "id": 185, "section": "Commercial Model & Procurement", "question": "What infrastructure costs need to be considered?", "answer": "Guardian has been designed for a modest infrastructure footprint, with actual sizing determined by the estate and deployment.", "status": "approved", "published": true }, { "id": 186, "section": "Commercial Model & Procurement", "question": "How predictable is Guardian's operating cost?", "answer": "Predictable enterprise consumption and commercial control are design objectives.", "status": "validate", "validate_note": "final commercial model", "published": false }, { "id": 187, "section": "Commercial Model & Procurement", "question": "Is pricing linked to MQ message or transaction volume?", "answer": "", "status": "validate", "validate_note": "final commercial model before publication", "published": false }, { "id": 188, "section": "Commercial Model & Procurement", "question": "What does the customer licence?", "answer": "", "status": "validate", "validate_note": "final commercial model before publication", "published": false }, { "id": 189, "section": "Commercial Model & Procurement", "question": "Can customers start with one domain and expand?", "answer": "The platform direction supports progressive adoption from an initial operational domain into broader use as value is demonstrated.", "status": "approved", "published": true }, { "id": 190, "section": "Commercial Model & Procurement", "question": "What implementation costs are involved?", "answer": "Implementation depends on scope, integration, customer controls and the services required. These are defined transparently during discovery and commercial planning.", "status": "approved", "published": true }, { "id": 191, "section": "Commercial Model & Procurement", "question": "What support options are available?", "answer": "", "status": "validate", "validate_note": "support tiers and SLAs before publication", "published": false }, { "id": 192, "section": "Commercial Model & Procurement", "question": "Does the commercial model expose Datagentics' internal weighting mechanism?", "answer": "No. Customers need a clear and transparent commercial proposition, while proprietary internal mechanisms remain Datagentics IP.", "status": "approved", "published": true }, { "id": 193, "section": "Controlled Deployment & Adoption", "question": "What is a Guardian Controlled Deployment?", "answer": "A bounded deployment into an agreed customer environment with defined access, controls, scope, objectives and measures of success.", "status": "approved", "published": true }, { "id": 194, "section": "Controlled Deployment & Adoption", "question": "Why call it a Controlled Deployment rather than a POC?", "answer": "Because the objective is to demonstrate Guardian safely against a real operational environment under enterprise controls rather than create a disposable technical experiment.", "status": "approved", "published": true }, { "id": 195, "section": "Controlled Deployment & Adoption", "question": "What is required to begin?", "answer": "An agreed use case, relevant estate information, defined stakeholders, security and governance requirements and agreed success measures.", "status": "approved", "published": true }, { "id": 196, "section": "Controlled Deployment & Adoption", "question": "How quickly can Guardian be deployed?", "answer": "Deployment time depends on customer controls, scope, connectivity and environment readiness.", "status": "validate", "validate_note": "indicative timeframe", "published": false }, { "id": 197, "section": "Controlled Deployment & Adoption", "question": "Can we start completely read-only?", "answer": "Yes.", "status": "approved", "published": true }, { "id": 198, "section": "Controlled Deployment & Adoption", "question": "Can Guardian reuse existing estate extracts?", "answer": "Yes. Existing information can provide a valuable starting point.", "status": "approved", "published": true }, { "id": 199, "section": "Controlled Deployment & Adoption", "question": "Can Guardian demonstrate value without taking actions?", "answer": "Yes. Sensing, diagnosis, evidence and recommendations can demonstrate value before operational action is permitted.", "status": "approved", "published": true }, { "id": 200, "section": "Controlled Deployment & Adoption", "question": "How is success measured?", "answer": "Against agreed operational and business outcomes rather than simply proving that the software runs.", "status": "approved", "published": true }, { "id": 201, "section": "Controlled Deployment & Adoption", "question": "How does Guardian move toward governed action?", "answer": "Progressively, through agreed policies, permissions, QHITL and graded autonomy.", "status": "approved", "published": true }, { "id": 202, "section": "Controlled Deployment & Adoption", "question": "Can we remain permanently recommendation-only?", "answer": "Yes.", "status": "approved", "published": true }, { "id": 203, "section": "Controlled Deployment & Adoption", "question": "What happens after a successful Controlled Deployment?", "answer": "Successful outcomes can form the basis for broader production adoption and progressively expanded capability under customer governance.", "status": "approved", "published": true }, { "id": 204, "section": "Controlled Deployment & Adoption", "question": "Can adoption stop after the initial stage?", "answer": "Yes. Expansion remains a customer decision based on demonstrated value and approved governance.", "status": "approved", "published": true }, { "id": 205, "section": "Intellectual Property & Customer Rights", "question": "Who owns Guardian?", "answer": "Datagentics retains ownership of the Guardian platform and its underlying proprietary technology, models, patterns, software and intellectual property.", "status": "approved", "published": true }, { "id": 206, "section": "Intellectual Property & Customer Rights", "question": "Who owns my organisation's data?", "answer": "The customer retains ownership of its operational and business information.", "status": "validate", "validate_note": "contractual wording", "published": false }, { "id": 207, "section": "Intellectual Property & Customer Rights", "question": "Does Datagentics gain ownership of knowledge about my environment?", "answer": "Customer-specific operational information remains associated with the customer environment. The contractual boundary between customer-specific information and Datagentics platform IP is defined in the customer agreement.", "status": "validate", "validate_note": "legal wording", "published": false }, { "id": 208, "section": "Intellectual Property & Customer Rights", "question": "Does my operational data become Datagentics IP?", "answer": "No. Use of Guardian does not transfer ownership of customer operational data to Datagentics.", "status": "validate", "validate_note": "contractual wording", "published": false }, { "id": 209, "section": "Intellectual Property & Customer Rights", "question": "Can knowledge from my environment be used for another customer?", "answer": "Customer-specific operational data and intelligence are isolated and are not designed to become another customer's operational intelligence.", "status": "approved", "published": true }, { "id": 210, "section": "Intellectual Property & Customer Rights", "question": "Who owns customer-specific configurations, policies and integrations?", "answer": "Ownership and usage rights for customer-specific configuration, integrations and implementation deliverables are defined in the relevant customer agreement.", "status": "validate", "validate_note": "legal/commercial position", "published": false }, { "id": 211, "section": "Intellectual Property & Customer Rights", "question": "What happens to customer-specific intelligence when we stop using Guardian?", "answer": "Retention, export and deletion are governed by agreed contractual and data-retention requirements.", "status": "validate", "validate_note": "product capability and contract", "published": false }, { "id": 212, "section": "Intellectual Property & Customer Rights", "question": "How does Datagentics protect its own IP?", "answer": "Datagentics protects the proprietary mechanisms underlying Guardian while providing customers the transparency required to understand, govern and audit how Guardian operates.", "status": "approved", "published": true }, { "id": 213, "section": "Intellectual Property & Customer Rights", "question": "Does transparency mean Datagentics must disclose the SLM algorithms?", "answer": "No. Customers can receive the transparency needed to assess, govern and audit the platform without disclosure of proprietary implementation details.", "status": "approved", "published": true }, { "id": 214, "section": "Intellectual Property & Customer Rights", "question": "What Guardian information is proprietary?", "answer": "Detailed SLM mechanics, weighting methods, pattern structures, algorithms, internal architecture and other implementation details remain Datagentics proprietary technology.", "status": "approved", "published": true }, { "id": 215, "section": "Intellectual Property & Customer Rights", "question": "Can a customer export its own data?", "answer": "Customer data portability and export requirements need to be defined in the supported product and contractual model.", "status": "validate", "published": false }, { "id": 216, "section": "Intellectual Property & Customer Rights", "question": "How do you avoid IP ambiguity during consultancy or integration work?", "answer": "Customer agreements need to distinguish Datagentics background IP, Guardian platform IP, customer data and any customer-specific deliverables.", "status": "validate", "validate_note": "legal templates", "published": false }, { "id": 217, "section": "Risk, Assurance & Audit", "question": "How does Guardian support operational resilience requirements?", "answer": "Guardian is designed to improve evidence, visibility, diagnosis, control and knowledge retention around critical technology operations.", "status": "approved", "published": true }, { "id": 218, "section": "Risk, Assurance & Audit", "question": "Can Guardian provide evidence for audit and assurance?", "answer": "Auditability is a core design principle, including evidence around recommendations, approvals and permitted actions.", "status": "approved", "published": true }, { "id": 219, "section": "Risk, Assurance & Audit", "question": "Can Guardian show who approved an action?", "answer": "The governance model is designed to retain approval and action evidence.", "status": "validate", "validate_note": "exact audit record", "published": false }, { "id": 220, "section": "Risk, Assurance & Audit", "question": "Can a historical decision be reconstructed?", "answer": "Provenance and audit history are intended to support understanding of what evidence and controls informed a decision.", "status": "validate", "validate_note": "retention and reconstruction detail", "published": false }, { "id": 221, "section": "Risk, Assurance & Audit", "question": "Can Guardian support separation of duties?", "answer": "The governance model is intended to align with enterprise role and approval boundaries.", "status": "validate", "validate_note": "exact controls", "published": false }, { "id": 222, "section": "Risk, Assurance & Audit", "question": "Can Guardian policies reflect existing control frameworks?", "answer": "Guardian's policy model is designed to reflect customer governance requirements rather than impose a single universal control model.", "status": "approved", "published": true }, { "id": 223, "section": "Risk, Assurance & Audit", "question": "Does Guardian claim regulatory compliance on behalf of the customer?", "answer": "No. Guardian can support governance and evidence, but regulatory compliance remains dependent on the customer's overall controls, implementation and obligations.", "status": "approved", "published": true }, { "id": 224, "section": "Risk, Assurance & Audit", "question": "Can Guardian help demonstrate control effectiveness?", "answer": "Its evidence and auditability can contribute to assurance where the relevant controls and outcomes are defined.", "status": "validate", "validate_note": "reporting capability", "published": false }, { "id": 225, "section": "Risk, Assurance & Audit", "question": "How does Guardian manage operational risk when confidence is low?", "answer": "Low confidence or insufficient evidence can keep the decision with qualified people rather than trigger unsupported action.", "status": "approved", "published": true }, { "id": 226, "section": "Risk, Assurance & Audit", "question": "Can customers audit Guardian itself?", "answer": "Enterprise customers need sufficient transparency to assess the platform's security, governance and operation without requiring disclosure of proprietary IP.", "status": "validate", "validate_note": "assurance process", "published": false }, { "id": 227, "section": "Product Lifecycle, Support & Continuity", "question": "How are Guardian releases governed?", "answer": "Releases are intended to operate through a controlled product lifecycle compatible with enterprise change processes.", "status": "validate", "validate_note": "formal release policy", "published": false }, { "id": 228, "section": "Product Lifecycle, Support & Continuity", "question": "How does Guardian keep product intelligence current?", "answer": "Approved vendor and product intelligence can be maintained as part of the intelligence model.", "status": "validate", "validate_note": "update mechanism", "published": false }, { "id": 229, "section": "Product Lifecycle, Support & Continuity", "question": "Can a customer control when a new Guardian version is introduced?", "answer": "Enterprise change control is expected to govern deployment timing.", "status": "validate", "validate_note": "supported version policy", "published": false }, { "id": 230, "section": "Product Lifecycle, Support & Continuity", "question": "Can customers remain on an approved version?", "answer": "", "status": "validate", "validate_note": "version support and lifecycle policy", "published": false }, { "id": 231, "section": "Product Lifecycle, Support & Continuity", "question": "What support model does Datagentics provide?", "answer": "", "status": "validate", "validate_note": "support model and SLAs", "published": false }, { "id": 232, "section": "Product Lifecycle, Support & Continuity", "question": "What happens if Datagentics is unavailable?", "answer": "Guardian is designed not to sit in the critical application path. Wider support and continuity arrangements form part of enterprise adoption.", "status": "validate", "published": false }, { "id": 233, "section": "Product Lifecycle, Support & Continuity", "question": "What happens if Datagentics fails as a business?", "answer": "Enterprise adoption requires appropriate contractual, continuity, data and technology protections.", "status": "validate", "validate_note": "formal continuity position before publication", "published": false }, { "id": 234, "section": "Product Lifecycle, Support & Continuity", "question": "How is key-person risk addressed?", "answer": "Datagentics' operating model, documentation, company-controlled technology assets and support processes need to reduce dependency on any one individual.", "status": "validate", "validate_note": "formal position", "published": false }, { "id": 235, "section": "Product Lifecycle, Support & Continuity", "question": "How is customer continuity protected?", "answer": "Through deployment architecture, customer control, documented support processes and appropriate contractual protections.", "status": "validate", "published": false }, { "id": 236, "section": "Datagentics, Services & People", "question": "Who is Datagentics?", "answer": "Datagentics is building specialised operational intelligence designed to help organisations govern, operate and optimise increasingly complex technology environments.", "status": "approved", "published": true }, { "id": 237, "section": "Datagentics, Services & People", "question": "Why did Datagentics build Guardian?", "answer": "Because enterprise technology generates more operational information than ever while critical understanding still depends heavily on scarce specialist people and fragmented tooling.", "status": "approved", "published": true }, { "id": 238, "section": "Datagentics, Services & People", "question": "What services sit around Guardian?", "answer": "The Datagentics proposition includes Platform Integration, Consultancy and Resource Augmentation alongside the technology platform.", "status": "approved", "published": true }, { "id": 239, "section": "Datagentics, Services & People", "question": "Does Datagentics provide platform integration?", "answer": "Yes.", "status": "approved", "published": true }, { "id": 240, "section": "Datagentics, Services & People", "question": "Does Datagentics provide consultancy?", "answer": "Yes.", "status": "approved", "published": true }, { "id": 241, "section": "Datagentics, Services & People", "question": "Can Datagentics provide specialist resources?", "answer": "Yes. Resource Augmentation can complement the platform and consultancy proposition.", "status": "approved", "published": true }, { "id": 242, "section": "Datagentics, Services & People", "question": "Is professional services support mandatory?", "answer": "The required service model depends on customer scope and internal capability.", "status": "validate", "validate_note": "commercial position", "published": false }, { "id": 243, "section": "Datagentics, Services & People", "question": "Can our own teams operate Guardian?", "answer": "Guardian is designed to become part of the customer's operational environment rather than create permanent dependency on Datagentics personnel.", "status": "approved", "published": true }, { "id": 244, "section": "Datagentics, Services & People", "question": "How does Datagentics transfer knowledge?", "answer": "Implementation and adoption can include knowledge transfer so customer teams understand the platform, controls and operating model.", "status": "validate", "validate_note": "service detail", "published": false }, { "id": 245, "section": "Datagentics, Services & People", "question": "Who typically uses Guardian?", "answer": "Operational engineers, platform specialists, service teams, technology leaders, risk and governance stakeholders can derive different value from the same operational intelligence.", "status": "approved", "published": true }, { "id": 246, "section": "Datagentics, Services & People", "question": "What value does Guardian provide a Head of Infrastructure?", "answer": "Greater visibility of operational condition, developing risk, resilience, specialist dependency, cost and opportunities to improve efficiency and control.", "status": "approved", "published": true }, { "id": 247, "section": "Datagentics, Services & People", "question": "What value does Guardian provide an engineer?", "answer": "Faster access to relevant evidence, operational context and governed recommendations.", "status": "approved", "published": true }, { "id": 248, "section": "Datagentics, Services & People", "question": "What value does Guardian provide a CIO or CTO?", "answer": "A clearer connection between technology operations, resilience, risk, cost, efficiency and business performance.", "status": "approved", "published": true }, { "id": 249, "section": "Datagentics, Services & People", "question": "What value does Guardian provide Risk and Governance?", "answer": "Greater evidence, consistency, policy control and auditability around operational decisions.", "status": "approved", "published": true }, { "id": 250, "section": "Platform Direction & Executive Challenge", "question": "Is Guardian MQ the platform or a product on the platform?", "answer": "Guardian MQ is the first specialised operational implementation of the wider Guardian platform approach.", "status": "approved", "published": true }, { "id": 251, "section": "Platform Direction & Executive Challenge", "question": "Will I need a separate Guardian platform for every technology domain?", "answer": "The direction is a common governed platform approach supporting specialised operational domains rather than unrelated standalone tools.", "status": "validate", "validate_note": "architecture wording", "published": false }, { "id": 252, "section": "Platform Direction & Executive Challenge", "question": "What operational domains are planned beyond MQ?", "answer": "Additional messaging, infrastructure, mainframe and cloud domains form part of the platform direction. They remain roadmap until delivered.", "status": "approved", "published": true }, { "id": 253, "section": "Platform Direction & Executive Challenge", "question": "How will Guardian expand without losing specialist focus?", "answer": "By combining specialised intelligence for individual domains with common governance, evidence and controlled-action principles.", "status": "approved", "published": true }, { "id": 254, "section": "Platform Direction & Executive Challenge", "question": "How does Guardian fit into a broader enterprise AI strategy?", "answer": "Guardian provides specialised operational intelligence where general-purpose AI is not necessarily the right architectural or governance fit.", "status": "approved", "published": true }, { "id": 255, "section": "Platform Direction & Executive Challenge", "question": "How does Guardian fit into an operational resilience strategy?", "answer": "By improving visibility, diagnosis, knowledge retention, evidence and governed response across critical technology operations.", "status": "approved", "published": true }, { "id": 256, "section": "Platform Direction & Executive Challenge", "question": "Why Guardian?", "answer": "Because organisations often have plenty of operational data but still lack scalable, governed specialist intelligence to turn that evidence into timely decisions.", "status": "approved", "published": true }, { "id": 257, "section": "Platform Direction & Executive Challenge", "question": "Why Datagentics?", "answer": "Datagentics is focused specifically on the operational intelligence gap: combining domain expertise, governed intelligence and controlled action within the customer's environment.", "status": "approved", "published": true }, { "id": 258, "section": "Platform Direction & Executive Challenge", "question": "Why not build this ourselves?", "answer": "Guardian brings together specialised operational intelligence, domain expertise, governance, patterns and platform capability that each organisation would otherwise need to design, build, validate and maintain independently.", "status": "approved", "published": true }, { "id": 259, "section": "Platform Direction & Executive Challenge", "question": "Why not use an enterprise LLM?", "answer": "A general-purpose LLM and specialised operational intelligence solve different problems. Guardian does not require core operational reasoning to depend on external token consumption or unconstrained generated answers.", "status": "approved", "published": true }, { "id": 260, "section": "Platform Direction & Executive Challenge", "question": "Why not rely on vendor tooling?", "answer": "Vendor tooling remains valuable. Guardian creates an intelligence and governance layer around operational evidence rather than simply reproducing the underlying product tooling.", "status": "approved", "published": true }, { "id": 261, "section": "Platform Direction & Executive Challenge", "question": "What makes Guardian difficult to replicate?", "answer": "Its value lies in the combination of specialised operational intelligence, customer-specific context, governed knowledge, patterns, QHITL, graded autonomy and domain capability. Detailed implementation remains proprietary.", "status": "approved", "published": true }, { "id": 262, "section": "Platform Direction & Executive Challenge", "question": "What prevents a major vendor from doing something similar?", "answer": "Guardian is deliberately focused on the cross-cutting operational intelligence and governance problem rather than being limited to protecting a single vendor product.", "status": "approved", "published": true }, { "id": 263, "section": "Platform Direction & Executive Challenge", "question": "How does Guardian avoid becoming technical debt?", "answer": "It is designed to complement existing investments, maintain bounded interactions and avoid placing itself in critical application paths.", "status": "approved", "published": true }, { "id": 264, "section": "Platform Direction & Executive Challenge", "question": "How does Guardian avoid vendor lock-in?", "answer": "Customer ownership of customer data, open integration principles and clear separation between customer information and Datagentics IP are important principles.", "status": "validate", "validate_note": "portability commitments", "published": false }, { "id": 265, "section": "Platform Direction & Executive Challenge", "question": "What happens when Guardian gets something wrong?", "answer": "Guardian is deliberately governed. Evidence, confidence, permissions and qualified and authorised human approval provide controls rather than assuming intelligence is infallible.", "status": "approved", "published": true }, { "id": 266, "section": "Platform Direction & Executive Challenge", "question": "Can a customer independently verify a recommendation?", "answer": "Explainability and evidence are designed to allow qualified and authorised humans to understand and challenge Guardian's conclusions.", "status": "approved", "published": true }, { "id": 267, "section": "Platform Direction & Executive Challenge", "question": "What happens if Guardian and an SME disagree?", "answer": "Guardian provides evidence and reasoning to support a decision; it does not remove the ability of qualified people to challenge a recommendation.", "status": "approved", "published": true }, { "id": 268, "section": "Platform Direction & Executive Challenge", "question": "What happens when vendor guidance conflicts with what Guardian sees?", "answer": "Conflicting evidence is surfaced and considered using source authority, customer context and qualified judgement rather than silently selecting one answer.", "status": "approved", "published": true }, { "id": 269, "section": "Platform Direction & Executive Challenge", "question": "How do you stop poor data contaminating Guardian's intelligence?", "answer": "Guardian does not treat every observation or input as validated truth. Evidence quality, provenance, validation and governed learning are fundamental principles.", "status": "approved", "published": true }, { "id": 270, "section": "Platform Direction & Executive Challenge", "question": "Why does this matter now?", "answer": "Technology estates are becoming more complex while specialist skills remain scarce, resilience expectations are increasing and organisations face continuing pressure to control technology cost.", "status": "approved", "published": true }, { "id": 271, "section": "Platform Direction & Executive Challenge", "question": "Where does Guardian fit in the future enterprise operating model?", "answer": "Between the growing volume of operational information and the people accountable for critical technology, turning evidence into specialised, governed operational intelligence.", "status": "approved", "published": true }, { "id": 272, "section": "Platform Direction & Executive Challenge", "question": "How does Guardian help organisations outperform?", "answer": "By bringing resilience, operational intelligence, governance, productivity, cost optimisation and performance together rather than treating them as separate technology problems.", "status": "approved", "published": true }, { "id": 273, "section": "Ask Datagentics - Website Intelligence Layer", "question": "What is Ask Datagentics?", "answer": "Ask Datagentics is the proposed website intelligence experience that lets prospective clients ask natural-language questions about Guardian and receive answers grounded in approved Datagentics public knowledge.", "status": "approved", "published": true }, { "id": 274, "section": "Ask Datagentics - Website Intelligence Layer", "question": "Is Ask Datagentics just a chatbot?", "answer": "The intention is a governed knowledge experience rather than an unrestricted generic chatbot.", "status": "approved", "published": true }, { "id": 275, "section": "Ask Datagentics - Website Intelligence Layer", "question": "What can visitors ask?", "answer": "Questions about Guardian, SLM, deployment, security, governance, MQ, resilience, integration, services, commercial principles, IP, optimisation and platform direction.", "status": "approved", "published": true }, { "id": 276, "section": "Ask Datagentics - Website Intelligence Layer", "question": "Where do Ask Datagentics answers come from?", "answer": "From the approved public Datagentics knowledge base rather than unrestricted generation from unknown sources.", "status": "approved", "published": true }, { "id": 277, "section": "Ask Datagentics - Website Intelligence Layer", "question": "Does every visitor question become knowledge?", "answer": "No. Questions can be captured as analytics, but new knowledge only enters the approved base through review and validation.", "status": "approved", "published": true }, { "id": 278, "section": "Ask Datagentics - Website Intelligence Layer", "question": "What happens when Ask Datagentics does not have an approved answer?", "answer": "It can acknowledge the gap, provide safe related information where available and route the topic for Datagentics review rather than invent a product position.", "status": "approved", "published": true }, { "id": 279, "section": "Ask Datagentics - Website Intelligence Layer", "question": "Can Ask Datagentics reveal proprietary IP?", "answer": "No. Public answers explain capability, principles and outcomes while detailed SLM mechanics, weighting, algorithms, pattern structures and proprietary architecture remain protected.", "status": "approved", "published": true }, { "id": 280, "section": "Ask Datagentics - Website Intelligence Layer", "question": "Can Ask Datagentics analyse what prospective clients care about?", "answer": "Yes. Anonymous or appropriately governed question analytics can reveal recurring themes, areas of interest and knowledge gaps.", "status": "validate", "validate_note": "privacy/analytics design", "published": false }, { "id": 281, "section": "Ask Datagentics - Website Intelligence Layer", "question": "How does Ask Datagentics demonstrate the Datagentics philosophy?", "answer": "It applies the same principle of specialised, controlled and governed intelligence: approved knowledge, bounded disclosure, evidence and human validation.", "status": "approved", "published": true }, { "id": 282, "section": "Ask Datagentics - Website Intelligence Layer", "question": "What is the proposed intelligence loop?", "answer": "Question -> intent -> approved Datagentics knowledge -> answer -> related questions -> analytics -> knowledge-gap identification -> qualified and authorised human review -> approved new knowledge.", "status": "approved", "published": true }, { "id": 283, "section": "Intelligence, AI & SLM", "question": "Are Kafka or Infrastructure SLMs on the Datagentics roadmap?", "answer": "The Guardian zMQ SLM is the first Specialist Language Model in the family and the current live product focus, specialised for IBM MQ. A Kafka SLM and an Infrastructure SLM are on the Guardian platform roadmap.", "status": "roadmap", "published": true } ] }