This document is the single source of truth for how MyRxWallet describes its platform, products, and scope. Every external communication — website copy, pitch materials, partner agreements, regulatory submissions, press statements, and developer documentation — must conform to these terms. When in doubt, use the exact phrasing in the Canonical Wording section. Do not paraphrase.
Language drift is a compliance risk. A term that sounds harmless in context can create regulatory exposure — particularly around securities law, healthcare data privacy, and financial services definitions. These rules exist to prevent that drift.
| Context | Use This | Not This | Why |
|---|---|---|---|
| Company type | infrastructure company | tech startup / platform / protocol | "Infrastructure" signals non-transactional, non-speculative intent to regulators |
| Industry | regulated digital environments; health and compliance infrastructure | healthtech, fintech, crypto, blockchain company | Vertical labels invite regulatory categorization we have not sought |
| Stage | development-stage company | pre-revenue, pre-launch, startup | "Development-stage" is the correct SEC and accounting designation |
| What the company builds | verification and authorization infrastructure | a marketplace, exchange, wallet app, or financial platform | The prohibited terms each carry specific regulatory definitions |
| Competitive framing | no direct comparison required — describe what we do | better than X, unlike Y, competing with Z | Comparative claims invite scrutiny and create liability for unsubstantiated superiority |
Each pillar has a fixed description, approved synonyms, and prohibited terms. Required context must appear in the same sentence or immediately adjacent paragraph whenever the pillar is named in an external communication.
"MRxID is non-transferable and non-custodial. No private keys, assets, or financial value are held by or through this system."
"MRxAccess produces verifiable, signed authorization decisions. No protected health information (PHI) is transmitted, stored, or processed by this layer."
"MRxScore measures identity verification completeness and credential attestation strength. It is not a credit score, not a product of any credit bureau, and is not used in lending, underwriting, or financial eligibility decisions."
"MRxRoyalty distributions are attribution records tied to verified contribution provenance. They are not financial instruments, investment products, or securities of any kind."
"MRxDAO is the preeminent on-chain governing body of the MyRxWallet ecosystem, structured under Wyoming SF0038 (DAO LLC). It operates in alignment with — not in place of — applicable U.S. federal and state law. MRxDAO issues Platinum Grade classifications to individuals and entities meeting the highest ecosystem compliance standards. Sentinel AI Agent provides AML/KYC monitoring and fraud detection in support of DAO governance. Sentinel AI flags anomalies — it does not make final determinations."
These rules apply across all pillars and all external communications.
| Topic | Approved Framing | Prohibited Framing | Why |
|---|---|---|---|
| Platform type | infrastructure layer; control layer; verification layer | marketplace; exchange; DeFi protocol; app | Each prohibited term carries regulatory meaning |
| Blockchain reference | distributed ledger; immutable audit record; hash-anchored provenance | blockchain (alone); on-chain (as marketing term); crypto | Avoid triggering crypto-asset regulatory framing |
| Data handling | no PHI stored; hash-based evidence; immutable provenance; no data broker | data monetization; selling data; user data marketplace | HIPAA and CCPA exposure; also inaccurate |
| Automation / AI | deterministic logic; rule-based decision; algorithmic verification | AI-driven decisions; autonomous agent; self-executing | AI Act, FTC algorithmic accountability exposure |
| Regulatory status | engineered to align with; designed to operate within; compliance-by-architecture | approved by; certified by; licensed under; compliant with (as a blanket claim) | We hold no regulatory approvals at this stage — these claims are false |
| Financial framing | non-custodial; non-transactional; non-advisory; no financial product | investment; asset appreciation; store of value; financial return | Securities law triggers; Howey test exposure |
| Health claims | health identity infrastructure; FHIR-native integration; clinical data provenance | medical platform; diagnostic tool; clinical decision support (without FDA context) | FDA SaMD regulation; FTC health claims rules |
| User benefits | verifiable, portable identity; auditable access; transparent provenance | earn money; make returns; profit from your data | Invites securities classification and FTC deceptive practices scrutiny |
| DAO governance | MRxDAO governance layer; on-chain governing body; ecosystem governance; Platinum Grade classification | DAO government; decentralized law; replaces regulators; AI rules | MRxDAO governs the ecosystem — it operates under law, not above it |
| Sentinel AI | AI-assisted monitoring; pattern-based anomaly detection; automated screening; Sentinel AI Agent flags | AI decides; autonomous enforcement; self-executing AI; AI-ruled compliance | Sentinel AI is a monitoring layer. Human/DAO governance makes final determinations. |
The following statements must not be paraphrased. They have been drafted to be accurate, defensible, and regulator-legible. Use exact phrasing.
| Rule | Applies To | Requirement |
|---|---|---|
| Pillar naming | Any use of MRxID, MRxAccess, MRxScore, MRxRoyalty in external materials | Include the required context statement for that pillar in the same document section |
| Score display | Any public-facing use of an MRxScore value or range | Always accompany with the MRxScore Disclaimer above. No score display without disclaimer. |
| Financial language | Any reference to MRxRoyalty distributions or attribution earnings | Always accompany with the MRxRoyalty Disclaimer above. "Earnings" and "distribution" require the non-securities qualifier. |
| Regulatory claims | Any reference to compliance, regulatory alignment, or standards conformance | Use "engineered to align with" — never "approved by," "certified under," or "compliant with" as a blanket claim. |
| Stage disclosure | Any pitch deck, investor communication, or partnership agreement | Include "development-stage company" designation. Required as a matter of legal accuracy. |
| Health data claims | Any reference to PHI, EHR integration, or clinical data | Always include the Data Handling Statement or a direct equivalent in the same document. |
| MRxDAO governance reference | Any mention of MRxDAO, Platinum Grade, privileged licensing, or ecosystem governance | Always include the MRxDAO Governance Identity Statement. Explicitly note alignment with — not replacement of — federal and state law. |
| Sentinel AI reference | Any mention of Sentinel AI Agent, AML/KYC monitoring, or fraud detection | Always include the Sentinel AI Monitoring Statement. Never imply AI makes final decisions — state that Sentinel AI flags and MRxDAO governance confirms. |
| Platinum Grade classification | Any reference to Platinum Grade status for an individual or entity | Confirm it was issued by MRxDAO. State the criteria basis (identity verification, compliance posture, operational integrity). Never frame as a financial designation. |
Language is infrastructure. The words used to describe this platform determine how regulators, partners, and counsel categorize it.
Precision is not bureaucracy — it is the first line of compliance defense.