TRUST & READINESS / DEVELOPMENT STATEMENT
Clarity is part
of the product.
What the prototype does, what it does not do, and what must be in place before a production pilot.
Current stage: private pre-alpha. The application is for local development and synthetic evaluation. Do not upload employer, customer, government, classified, or otherwise sensitive security data.
Current capabilities and limits
| Area | Available now | Important boundary |
|---|---|---|
| Prioritization | Deterministic contextual score | Weights are prototype assumptions, not calibrated loss probabilities. |
| Evidence | Supplied factor context and confidence | Sources and control effectiveness are not independently validated. |
| Decisions | Named authority and rationale records | Names are self-reported; no SSO, RBAC, or identity-backed approval yet. |
| Verification | Operator-reported outcome and before/after assessment | A recorded statement is not independent proof of remediation. |
| Receipts | SHA-256 checksum and local audit hashes | Not digitally signed or externally anchored; a privileged actor can rewrite the local chain. |
| Deployment | Local container and automated checks | No production availability, compliance certification, or managed-service commitment. |
Security and release gates
Before a production pilot, the build requires identity and access controls, tenant-boundary testing, managed data storage, migrations, secrets management, backup and restoration tests, rate limits, operational monitoring, and an independent security review. Scanner connectors and threat enrichment remain planned capabilities.
Automated testing and security checks help find defects. Passing checks do not establish that the application is secure or compliant.
Display concepts, not live services
The global operations panel and cyber wire use synthetic or editorial demonstration content. Map locations are illustrative; they do not represent attacks, attribution, customer deployments, or SOC coverage. No news feed is connected. The board offers split-flap, ticker, and classic-frame treatments with optional, controllable motion.
Privacy in this preview
The marketing pages contain no contact form, account registration, analytics scripts, or third-party fonts. The interactive illustration runs in the browser without contacting an API or storing entries. The hosting environment may still generate request logs.
This statement covers the public website preview and is not a client data-processing agreement. A verified contact channel, reviewed collection notice, and data-handling practices are required before accepting inquiries or customer evidence.
Proposed Exposure Decision Review
The planned advisory engagement starts with one agreed environment and an authorized, sanitized export. Its intended outputs are a prioritized review queue, an evidence-gap register, accountable next actions, and a leadership decision brief.
Scope, authorization, data classification, handling requirements, delivery terms, and acceptance criteria must be agreed before any engagement. No live scanning, exploitation, autonomous remediation, or third-party access is authorized by this preview.
Engagements are not yet open through the website. A contact route will be configured and tested before inquiries open.
Working identity
Royal Guard Cyber is the working brand used for this development effort. This preview does not assert trademark registration, a particular legal entity status, customer endorsements, or vendor partnerships.