Designed with Reference to Singapore IMDA Agentic AI Governance Framework (v1.5) • Self-Attested Architectural Alignment View Alignment Matrix ↓
Let's Chat Let's Chat
Designed with Reference to IMDA Agentic AI Framework (v1.5) Aligned with PDPC Singapore Guidelines AI Verify Foundation Testing Reference

Singapore IMDA AI Framework Alignment

Official architectural blueprint, technical controls, and operational governance standards demonstrating Let's Chat alignment with Singapore’s regulatory guidelines for autonomous and generative AI agents.

Standard: Model AI Governance Framework for Agentic AI (v1.5, released 22 January 2026)
Official Reference: IMDA AI Governance Framework Index
Testing Suite: AI Verify Foundation Guidelines
Jurisdiction: Republic of Singapore
Classification: Public Governance Architecture (Self-Attested Control & Evidence Matrix)
Inquiries: legal@letschat.asia

Regulatory Alignment Disclaimer & Assessment Scope

Let's Chat is designed with reference to Singapore's Infocomm Media Development Authority (IMDA) Model AI Governance Framework for Agentic AI (v1.5) (the foundational Model AI Governance Framework for Generative AI was officially launched on 22 January 2026, and IMDA's current governance index references v1.5) and AI Verify Foundation testing guidelines. This document outlines our self-attested architectural alignment, technical controls, and empirical evidence matrix. A control mapping does not itself constitute statutory certification, official licensing, accreditation, or endorsement by IMDA, the Personal Data Protection Commission (PDPC), or the Government of Singapore.

Executive Summary for Chief Risk & Compliance Officers

Singapore has established itself as the global gold standard for AI governance, with IMDA officially releasing the foundational Model AI Governance Framework for Generative AI on 22 January 2026, followed by expanded operational publications encompassing the Model AI Governance Framework for Agentic AI (v1.5) alongside the Transparency Guidelines for Generative AI Chatbots and the Starter Kit for Testing LLM-Based Applications for Safety and Reliability (v1.0).

Unlike conventional black-box chatbots that hallucinate or execute uncontrolled external actions, Let's Chat is engineered specifically around Singapore’s Four Core Governance Pillars: strict domain-bounded risk bounding, mandatory Human-in-the-Loop (HITL) confirmation for state modifications, dual-LLM circuit breaker resilience, and cryptographic multi-source attribution with full audit trails.

Knowledge Scope
DNS-Bounded RAG
Action Execution
Mandatory HITL
Resilience Model
Dual-LLM Circuit Breaker
Data Sovereignty
Singapore PDPA 2012
Regulatory Evaluation

1. Reviewed IMDA & PDPC Governance Publications

Let's Chat has completed an end-to-end architectural evaluation against the 10 foundational publications issued by the Infocomm Media Development Authority (IMDA), the Personal Data Protection Commission (PDPC), and the AI Verify Foundation:

Ref Official Publication Let's Chat Architectural Implementation
Doc 1 & 2 Model AI Governance Framework for Generative AI (Launched 22 January 2026) Foundational governance principles; bounded action spaces, zero unauthorized tool invocations, and sandboxed execution environments.
Doc 3 Transparency Guidelines for Generative AI Chatbots (IMDA / AI Verify) Mandatory persistent AI identity disclosure banner, source attribution pills with confidence matching scores, and real-time user feedback logging.
Doc 4 Model AI Governance Framework for Agentic AI (v1.5) Core architectural blueprint aligning with all Four Pillars: Risk Bounding, Human Accountability, Technical Controls, and End-User Responsibility.
Doc 5 Case Study: Responsible Deployment of OpenClaw (IMDA, May 2026) Integration of sandboxed tool interfaces, strict rate-limiting, and explicit user-driven ratification for state changes.
Doc 6 Discussion Paper: Legal Responsibility for AI Agents (IMDA, May 2026) Explicit non-agency contractual terms: AI outputs are informative and non-binding; clear division between Data Controller (Customer) and Data Processor (Let's Chat).
Doc 7 Starter Kit for Testing LLM-Based Applications for Safety & Reliability (v1.0) Continuous pre-deployment test suite for prompt injection resistance, jailbreak defense, groundedness scoring (>0.80), and PII redaction.
Doc 8 Team CREX: Embedding AI Safety Case Study Automated compliance guardrails built into the deployment pipeline with domain-bound context walls.
Doc 9 & 10 Model AI Governance Framework (2nd Ed) & Responsible AI Made Easy (PDPC/IMDA) Ethical AI baseline ensuring AI decision-making is explainable, transparent, human-centric, and auditable.
Architecture Deep-Dive

2. Operationalizing the 4 Pillars of Agentic AI Governance

How Let's Chat translates Singapore’s four governance mandates into production-grade software guardrails:

1

Pillar 1: Assess & Bound Risks Upfront

Agentic AI systems can wander or take unpredictable actions if their operating boundaries are not tightly constrained before execution. Let's Chat enforces multiple layers of upfront risk bounding:

Two-Tier DNS-TXT Lifecycle

Initial domain ownership requires a unique DNS TXT challenge record (letschat-site-verification=<token>) proving administrative control. Operational revocation is enforced immediately via edge administrative tombstones and periodic re-attestation polling, independent of DNS TTL propagation delays.

Strict Domain-Bounded Retrieval

RAG indexing is capped at 3 directory levels and 12 pages. Knowledge vectors are isolated by verified tenant IDs with zero cross-tenant contamination.

Zero-Hallucination Cutoff Threshold

Hybrid TF-IDF & Vector Space similarity rejects retrieval scores below 0.12, returning an explicit fallback message rather than fabricating ungrounded claims.

Prompt Injection Pre-Sanitizer

Incoming user queries are screened through an adversarial pre-filter that neutralizes prompt injection keywords, jailbreak triggers, and system override attempts.

2

Pillar 2: Make Humans Meaningfully Accountable

Under Singapore legal principles, autonomous AI agents cannot hold legal rights or obligations. Meaningful human oversight must be architecturally enforced for every consequential action:

Human-in-the-Loop (HITL) Cards

Any state-modifying action (submitting sales lead forms, booking calendar appointments, dispatching notifications) renders an interactive confirmation card requiring physical user ratification.

Operator vs Provider Boundary

Let's Chat acts strictly as a Data Processor providing software guardrails. Deploying organizations serve as Data Controllers responsible for domain content accuracy.

Non-Agency Contractual Disclaimers

In accordance with IMDA's Discussion Paper on Legal Responsibility, chatbot responses are advisory and non-binding; they do not form legal contracts without human confirmation.

Instant Human Escalation

When queries involve sensitive disputes, high-intent negotiations, or low confidence, the agent smoothly transfers the session to verified human representatives.

3

Pillar 3: Technical Controls, Safety Testing & Circuit Breakers

Reliability requires multi-tier technical safety nets that catch model failures, prevent data leaks, and ensure zero service interruption:

Measured Circuit Breaker & Edge Revocation

Local cache lookups execute in < 1ms, edge tombstone invalidation completes in < 5ms across regional edge POPs, and request denial on /api/chat is immediate upon cache update. Fails over to local deterministic engine upon timeout.

IMDA Safety Starter Kit (v1.0) Suite

Pre-deployment CI/CD evaluation validates prompt injection defense (15 adversarial vectors), groundedness overlap (>0.80), and latency bounds.

Immutable Trajectory Auditing

Decision paths, retrieved vector IDs, prompt payloads, and model identifiers are stored in immutable audit logs (AgentTrajectoryLog) for legal traceability.

Client DOM & Style Encapsulation

Closed Shadow DOM encapsulates widget styles and prevents host CSS bleed. In alignment with MDN Web Docs guidance, shadow roots are not a security barrier against hostile in-page scripts; therefore, all sensitive tokens and vector queries remain strictly server-side.

4

Pillar 4: Enable End-User Responsibility & Transparency

End users must always be aware that they are interacting with an AI agent, have immediate access to authoritative sources, and possess direct mechanisms to report discrepancies:

Persistent AI Identity Disclosure

The widget prominently displays an active AI indicator badge at all times ("AI Assistant • Grounded on Verified Site Data"), satisfying IMDA Transparency Guidelines.

Grounded Source Attribution Pills

Every substantive response renders clickable Grounded Sources pills disclosing document title, absolute URL, and confidence match percentage (e.g., 95% Match).

Continuous Feedback Loop

One-click thumbs up/down user feedback is logged to ResponseReview for engineering inspection via our automated Quality Management CLI.

Hallucination Disclaimers

Clear inline notices advise users to cross-verify critical financial, legal, or medical advice against cited official documentation.

Verification Standards

3. Singapore IMDA Alignment Matrix

Direct mapping of IMDA governance mandates to Let's Chat architectural controls and verification evidence:

Governance Area IMDA v1.5 Framework Guidance Let's Chat Architecture & Controls Status / Alignment Scope
AI Transparency Explicit disclosure that user is interacting with an AI system. Persistent header banner in ChatWidget.tsx Architecturally Aligned (Self-Attested Control)
Action Confirmation Human confirmation required prior to executing state-modifying actions. Interactive HITL Action Cards for leads/bookings Architecturally Aligned (Self-Attested Control)
Data Grounding Outputs must be grounded in verified enterprise knowledge sources. Two-tier lifecycle: DNS-TXT initial proof + edge administrative revocation Architecturally Aligned (Self-Attested Control)
Source Attribution Clear citation of underlying documents and confidence metrics. Grounded Sources pills with URL and match % Architecturally Aligned (Self-Attested Control)
Resilience & Failover Graceful degradation and technical circuit breakers against outages. Dual-LLM circuit breaker with measured <1ms cache lookup and <5ms edge sync Architecturally Aligned (Self-Attested Control)
Safety Red-Teaming Automated testing against prompt injection, jailbreaks, and PII leaks. test_safety_starterkit.py (IMDA Kit v1.0) Architecturally Aligned (Self-Attested Control)
DOM Encapsulation Style and DOM scoping without false reliance on client-side security boundaries. Closed Shadow DOM encapsulates CSS; auth tokens & RAG vectors remain server-side (MDN aligned) Architecturally Aligned (Self-Attested Control)
Auditability Immutable audit trails of model inputs, outputs, and trajectories. AgentTrajectoryLog & RuntimeCredentialEvent Architecturally Aligned (Self-Attested Control)
Privacy & Sovereignty

4. Singapore Personal Data Protection Act (PDPA 2012)

Let's Chat is architected from the ground up to respect Singapore privacy regulations and cross-border data transfer rules:

Zero Model Training on Tenant Data

Customer proprietary data, crawled website pages, and chat queries are strictly used for real-time RAG inference. They are never ingested into global training datasets.

Pre-Inference PII Redaction

Automatic regex and semantic filters redact Singapore NRIC/FIN patterns, credit cards, and telephone numbers before payloads are sent to inference engines.

Singapore Regional Data Sovereignty

Production databases and vector stores are hosted within the AWS Singapore (ap-southeast-1) region, fully satisfying PDPA cross-border requirements.

Frequently Asked Questions

5. Questions from Risk & Compliance Officers

Are chatbot conversations legally binding contracts on our enterprise?

No. In accordance with IMDA's Discussion Paper on Legal Responsibility for AI Agents (May 2026) and Let's Chat Terms of Service, AI outputs lack independent legal agency and do not constitute warranties or contracts. Commercial commitments require explicit Human-in-the-Loop ratification.

How does Let's Chat prevent prompt injection and hallucinations?

We deploy a two-fold defense: (1) an adversarial input sanitizer that strips jailbreak keywords, and (2) a strict Vector Space similarity threshold (cutoff score 0.12) that forces the model to reply with an explicit fallback when verified sources do not contain the answer.

Can an external party steal our widget embed code and deploy it elsewhere?

No. The embed code alone is non-functional without origin verification. Every browser request is attested against the allowed origin domains registered during DNS setup. Requests from unauthorized browser origins receive HTTP 403 Forbidden with zero vector embeddings transmitted. Furthermore, our threat model recognizes that non-browser API callers could synthesize headers, which is why rate limits, ephemeral signed JWTs, and tenant-partitioned databases enforce multi-layered defense.

How can we audit agent decisions for regulatory compliance?

Let's Chat maintains immutable session logs (AgentTrajectoryLog) detailing the user query, retrieved document IDs, raw model prompt, generated output, latency, and model version. These logs can be exported or reviewed via the Admin Portal and Quality Management CLI.

Need an Enterprise Compliance Assessment or DPO Review?

Our Singapore compliance and legal engineering team is available to assist enterprise risk assessments, review data processing agreements (DPAs), or provide custom red-teaming reports.

Official Compliance Desk: legal@letschat.asia | Registered in the Republic of Singapore