Troptions Pay
Legacy description: Legacy payment utility narrative tied to merchant acceptance and network reach messaging.
Institutional rewrite: Payment narratives are converted into rail-evaluation records with provider dependencies and dated claim controls.
Required evidence: Provider relationship evidence; Acceptance-condition matrix; Dated source snapshots
Current system module: payments-and-rail-evaluation
Next steps: Reconcile merchant claims; Attach provider confirmation; Publish controlled language
Blocked conditions: No verified merchant-count evidence; No provider/legal sign-off
Troptions Unity
Legacy description: Unity track presented as Solana utility with community and humanitarian narratives.
Institutional rewrite: Unity claims are managed as source-tagged records requiring governance, legal classification, and impact evidence.
Required evidence: Token legal memo; Governance disclosures; Impact reporting method
Current system module: claim-and-source-registry
Next steps: Define approved institutional language; Add impact evidence schema
Blocked conditions: No reserve/custody proof for backing claims; No legal clearance
Troptions Gold
Legacy description: Gold and commodity narratives linked to reserve and value-positioning statements.
Institutional rewrite: Gold assertions are routed through custody, valuation, legal, and accounting evidence workflows.
Required evidence: Custody records; Valuation policy; Accounting review
Current system module: rwa-and-proof-workflows
Next steps: Package evidence bundles; Apply risk and legal review gates
Blocked conditions: No custody/provider approval; No accounting treatment review
Merchant/Payment Rails
Legacy description: Merchant-network reach statements spanning Troptions and adjacent payment references.
Institutional rewrite: Merchant narratives are treated as claim records with verification status and blocked wording until evidence is attached.
Required evidence: Dated merchant dataset; Provider attestation; Coverage exclusions
Current system module: legacy-claim-registry
Next steps: Tag conflicting sources; Publish verification state
Blocked conditions: Conflicting source counts; Missing primary evidence
RWA / SALP Concepts
Legacy description: Conceptual tokenization narratives for real assets and structured programs.
Institutional rewrite: Concepts are translated into intake packages requiring title, valuation, legal, and custody controls.
Required evidence: Title and rights evidence; Valuation packet; Custody and legal classification
Current system module: rwa-intake
Next steps: Standardize intake checklists; Map release gates
Blocked conditions: Incomplete intake package; Missing legal or custody validation
GivBux Relationship
Legacy description: Third-party relationship appears in payment and merchant narratives.
Institutional rewrite: Third-party materials are treated as external references requiring direct validation.
Required evidence: Relationship documentation; Provider status letter
Current system module: source-map
Next steps: Document relationship scope; Flag external dependency risk
Blocked conditions: No direct contractual evidence
Humanitarian / Community Use Cases
Legacy description: Community and impact language used for adoption and mission narratives.
Institutional rewrite: Impact narratives require measurable methodology, governance controls, and reporting.
Required evidence: Impact framework; Program-level reporting
Current system module: insights-and-disclosures
Next steps: Define metrics; Attach evidence references
Blocked conditions: No measurable impact evidence
Institutional Control Plane
Legacy description: Not part of early narrative; introduced during institutional transition.
Institutional rewrite: Control-plane governance centralizes approvals, readiness checks, and release-gate discipline.
Required evidence: Audit logs; Role controls; Approval workflow traces
Current system module: admin-control-plane
Next steps: Finalize operator controls; Expand observability
Blocked conditions: Gate failures; Role control gaps
Client Portal
Legacy description: Legacy public audience channels were broad and promotional.
Institutional rewrite: Client portal provides role-aware evidence access and readiness tracking.
Required evidence: Access policy; Disclosure templates
Current system module: client-portal
Next steps: Expand portal modules; Align with diligence workflows
Blocked conditions: Missing access approvals
XRPL / AMM / DEX Simulation Layer
Legacy description: Exchange and liquidity narratives were broad and aspirational.
Institutional rewrite: XRPL, AMM, and DEX logic is simulation-first and readiness-gated.
Required evidence: Simulation logs; Risk review; Provider/legal gate status
Current system module: xrpl-simulation
Next steps: Expand scenario coverage; Add route risk scoring
Blocked conditions: No live signing approval
AI Search / Agentic RAG / MCP Future
Legacy description: Legacy content not consistently machine-readable.
Institutional rewrite: Source-aware AI stack publishes claim-linked, compliance-aware, machine-readable trust artifacts.
Required evidence: Source map integrity; Prompt and policy controls
Current system module: ai-search-and-rag
Next steps: Expand provenance metadata; Strengthen policy gates
Blocked conditions: Missing source traceability
Telecom / Concierge Future
Legacy description: Support was historically ad hoc and messaging-led.
Institutional rewrite: Telecom concierge is planned for controlled rollout with compliance and provider constraints.
Required evidence: TCPA controls; Provider onboarding; Consent architecture
Current system module: telecom-readiness
Next steps: Keep dry-run mode; Complete legal/provider approvals
Blocked conditions: No live telecom activation without approval
x402 Machine-Payable Future
Legacy description: No equivalent in early Troptions narratives.
Institutional rewrite: x402 readiness enables metered API/report access under legal and provider controls.
Required evidence: Commercial policy; Legal classification; Settlement controls
Current system module: x402-readiness
Next steps: Publish readiness constraints; Define billing controls
Blocked conditions: No commercial activation without approvals