Orbital

Origin

Real-world-asset tokenization treats every deal as a one-off. A new sub-sovereign issuer, a new legal opinion, a new compliance memo — every time. The same playbook gets re-derived under a different deal name and stored in a different folder. The intelligence is in the corridor — the structural pattern that recurs — but the data model is the deal.

Problem

Without a representation that lets corridors surface as first-class objects, you cannot answer the questions that matter: 'has this issuer class been done before, where, with what method, with what outcome?' is supposed to be a millisecond query. In practice it is a week of partner-time and a slack thread.

Approach

A tensor representation in which deals, jurisdictions, methods, receipts, and outcomes are facets of a single high-dimensional structure. Cross-matrix queries surface 'same playbook, different deal' instantly: jurisdiction A × method B × outcome C is a coordinate, not a search. Built on Postgres + pgvector with a custom MCP layer that lets multiple assistants reason against the same tensor.

Methodology

Postgres-first. Every entity (deal, issuer, jurisdiction, regulation, opinion, receipt) is a row with explicit foreign keys; the tensor is computed over those rows on demand rather than stored as a blob. The MCP layer exposes specific introspection calls — corridor_intelligence, deal_graph, similar_deals, regulatory_diff — so that an assistant can navigate the tensor without ever seeing raw rows.

Selected milestones

• Operational
• Deal-graph and corridor-intelligence MCP tools live across multiple assistants
• Cross-matrix queries running in production

Open questions

• How the tensor's dimensions evolve as new asset classes enter
• What the right level of granularity is for jurisdiction (country vs. regulator vs. opinion-class)
• How to surface a corridor's failure modes alongside its success patterns

Ask me about

• What a corridor actually buys you over a deal-by-deal database
• How the tensor enables cross-jurisdiction comparison
• What the MCP introspection calls expose to a coordinating assistant
• How deal-graph queries surface 'similar enough' issuers

Stack