Loading community...
Loading community...
DGUI X-ORB | KD Square Article

DGUI X-ORB
Wan Mohd Azizi @ctaxnagomi
Applied Agentic AI Engineer | UAEL | CTECX | DeckerGUI Agentic Integration Hybrid Ecosystem | KD Ambassador Sarawak
November 14, 2026
Abstract
This article examines DGUI X-Orb, an agentic forensic continuity layer within the DeckerGUI Persona system. Located at dguipersona-xorb.deckergui.my, X-Orb provides a governed workflow for managing the digital estate of a deceased person. It verifies authority through eKYC and JEV gates, matches NRIC identities, routes device conditions under authorized paths only, and builds a time-boxed searchable corpus that family members can query. The system emphasises compliance, audit trails, and hard gates to ensure defensible operation rather than unrestricted access.
Keywords: DGUI X-ORB, DeckerGUI Persona, forensic continuity, eKYC Surat Kematian, JEV NRIC match, time-boxed corpus, digital estate continuity, authorized forensic acquisition, DeckerGUI certificate
1. Problem Statement
Families facing the loss of a loved one often need controlled access to the deceased person's digital devices and data for practical reasons such as locating important documents, accounts, or final messages. Unregulated approaches risk privacy violations, legal issues, or incomplete records. DGUI X-Orb addresses this by providing a governed forensic continuity workflow under the DeckerGUI Persona system. It is not a bypass tool. Instead it enforces authority verification, identity matching, authorized device routing, and a time-limited corpus that the family can query only under strict gates and full audit.
2. What DGUI X-Orb Is
DGUI X-Orb is an agentic forensic continuity layer for the digital estate of a deceased person, available at dguipersona-xorb.deckergui.my. It operates within DeckerGUI OS under the DGUI Persona framework. The system verifies authority, matches the deceased NRIC against a relative's NRIC using a mini RULESET corpus and JEV, routes the device condition only through authorized paths (for example ADB when USB debugging is enabled, or certified forensic escalation otherwise), and builds a normalized, hashed corpus. Family members then receive a time-boxed chat window (30 minutes, 5 hours, or 7 weeks) to query critical details. A credible DeckerGUI device certificate and operator identity are required throughout.
Key components include eKYC death verification via OCR of the Surat Kematian with validity and 1-day post-death checks, JEV-based NRIC relation matching, a device router that refuses silent exploitation, forensic tool selection with certificate and audit trail, and a searchable deceased X-Orb corpus with provenance and hashes. The design prioritises defensibility and compliance over unrestricted access.
3. Seven-Step Continuity Flow
The official workflow proceeds from authority to answer in seven steps. Each step contains hard gates so that missing evidence stops the process.
| Step | Description |
|---|---|
| 01 | Credible certificate: DeckerGUI device certificate and operator identity bound to the case |
| 02 | eKYC Surat Kematian: OCR reads death certificate, checks validity and 1-day post-death rule |
| 03 | JEV NRIC relation: Mini RULESET corpus compares relative and deceased NRIC |
| 04-07 | JPN gate, device router (ADB or authorized path), acquisition into hashed corpus, time-boxed family chat window |
Hard gates include: no certificate means no device access; no eKYC validity means no JEV match; NRIC mismatch means no JPN submission; no authorized path means no acquisition. Audit output covers timestamped operator actions, OCR confidence, JEV decision traces, corpus hashes, and the full chat transcript.


18:19:04certificate verified18:19:04operator KR18:19:04authority DeckerGUI CA18:19:04case XORB-2026-000118:19:04relationship son18:19:04fingerprint 715e0e4e880b8922ccb8d29735393667cccc245ffe61f369d7e8fa1b12eefbed18:19:04issued 04/11/2026, 01:41:0218:19:04gate open · eKYC unlocked

18:19:04OCR PASS · 97%18:19:04name Abdullah Bin Hassan18:19:04nric 720314-13-558918:19:04date of death 2026-11-0918:19:04window closes 10/11/2026, 08:00:0018:19:04— checks —18:19:04✓ ocr.read parsed surat-kematian-demo.jpg18:19:04✓ nric.format 12-digit NRIC18:19:04✓ dod.parse date of death 2026-11-0918:19:04✓ authority certificate 715e0e4e880b…18:19:04✓ validity.1day 0 day(s) since death — new-contract window open

(https://dguipersona-xorb.deckergui.my)

People have been building conversational memorials / “griefbots” for years:
• Companies like HereAfter AI, StoryFile, and various Replika-style memorial features let families upload recordings, texts, or chats so they can ask questions of a simulated version of the deceased.
• There are also more informal LLM experiments where people feed a parent’s WhatsApp history or emails into a custom GPT or local model.
• On the forensic side, there are established (if cumbersome) legal and technical processes for accessing a deceased person’s phone or accounts, usually involving court orders, device unlocks, or specialist tools.
What stands out about DGUI X-Orb is the combination:
• Explicit forensic acquisition path (device router that only uses authorized methods — ADB if debugging is already on, or certified escalation otherwise — no silent bypass)
• Heavy governance layer (credible certificate, Surat Kematian OCR, JEV NRIC relation match, JPN gate, hard stops)
• Time-boxed chat window instead of an open-ended digital ghost
• Persona styled from the actual writing patterns in the corpus
• Full audit trail designed to be defensible
Most existing griefbots skip or lightly treat the “how did you legally and ethically get the data?” part and treat the chat as open-ended. X-Orb tries to solve the access + continuity problem inside a governed workflow, which is rarer.
So yes, it is one of the more serious attempts to turn “talk to the deceased’s digital estate” into something that could actually be used in a real family / legal / forensic context rather than pure emotional or experimental use. Whether it becomes the first widely adopted practical solution depends on how well the gates, corpus quality, and time-boxing hold up in real cases. The framing on the site is deliberately cautious for that reason.“
4. Compliance Posture and Required Evidence
X-Orb is designed to be defensible. Required evidence comprises the Surat Kematian (death certificate), deceased NRIC, relative NRIC plus relationship proof, and the DeckerGUI credible certificate. The system evaluates the 1-day post-death rule during eKYC and binds identities before any further action. Acquisition uses only approved adapters. Extracted items are normalized, hashed, and indexed with provenance. The resulting corpus supports the limited chat window but does not grant open-ended device control. This posture aligns with DeckerGUI's broader emphasis on decision-gated layers and accountable agentic workflows.
5. Implications for Agentic Continuity and Edge Use
Within the DeckerGUI ecosystem, X-Orb demonstrates how Persona, JEV, and certificate-bound gates can support sensitive real-world scenarios without becoming a bypass mechanism. The time-boxed corpus and audit trail enable family continuity while protecting the deceased person's remaining privacy. Edge or multi-node deployments can leverage the same governed flow because device routing and acquisition remain under authorized paths only. Operators launch the console to run a case end-to-end once all prerequisites are satisfied.
6. Conclusion
DGUI X-Orb supplies a governed forensic continuity layer for digital estates under DeckerGUI Persona. By combining eKYC, JEV NRIC matching, authorized device routing, and a time-boxed hashed corpus, it allows families to obtain critical information while enforcing hard compliance gates and full audit. The system is explicitly not a bypass tool. Its design supports defensible, certificate-bound operation that fits the broader DeckerGUI agentic infrastructure.
KrackedDevs are expanding to Borneo! Join us! Join KrackedDevs Community here! Follow: @krackeddevs at Threads | Instagram | X.Twitter | Official website | Discord. www.krackeddevs.com. Want to learn? Online @ RakyatDigital. Offline in-person @AIBuilderAcademy. We are currently building Agentic Infrastructure for Industries: DeckerGUI (DeckerGUI.my). Features include Agentic AI, Edge-Computing, Edge-AI, Multi-Node Orchestration, Decision Gated layer Compliances, DGM | DLLIM | HUB .NET | PERSONA | MARKET | AFM, and AI Infrastructure for Enterprise and Individual on your hand.
Glossary
DGUI X-Orb - Agentic forensic continuity layer for the digital estate of a deceased person under DeckerGUI Persona.
Surat Kematian - Malaysian death certificate used for eKYC verification via OCR.
JEV NRIC match - Mini RULESET corpus comparison of relative and deceased National Registration Identity Card numbers.
Time-boxed corpus - Searchable, hashed collection of extracted items available to family only for a limited window (30 min, 5 h, or 7 weeks).
Credible certificate - DeckerGUI device certificate binding operator identity to the case; required for any device access.
References
[1] DGUI X-Orb official page. https://dguipersona-xorb.deckergui.my/. Accessed November 2026.
[2] DeckerGUI ecosystem. https://deckergui.my/. Accessed November 2026.
This article is prepared in dual-column format for academic and SEO/AEO/GEO dissemination of accurate DGUI X-Orb information drawn from the official source.
Sign in to comment.
A question, an article, or a journal entry about what you built. One paragraph is enough, and it gets a reply.
Write a post