Institutional Hedge and Data Pilots

Purpose

Define a capital-efficient path from early market demand to institutional hedge, insurance, reinsurance, and data products.

Near-term wedge

Do not sell broad institutional liquidity before it exists. Sell narrow pilots:

• one event-risk category
• one named resolution source
• one market structure
• one maker/liquidity plan
• one data export or monitoring dashboard

This makes diligence easier and avoids overpromising depth.

Commercial structure

The default pilot is $2.5k-$7.5k/month plus a scoped setup fee. Pricing must be tied to a concrete workflow: one risk category, official-source monitoring, rule and resolution evidence, a delivery schedule, retention, and a named decision owner. It is not a promise of executable hedge capacity.

Recommended sequence:

1. paid event-risk monitoring and evidence pilot;
2. repeated buyer use and source-quality proof;
3. first-liquidity partner and controlled test market;
4. execution workflow only after legal, compliance, accounting, and liquidity gates pass.

Success is a collected pilot payment and recurring operational use—not a non-binding institutional conversation or a large hypothetical notional.

Enterprise and event-risk pilots remain reviewed contracts, not self-serve subscriptions. Before activation, the institution and Norynta must agree on the dataset, permitted use, retention, delivery cadence, support boundary, pricing, invoice evidence, and named owner. Execution, redistribution, or custom field rights require explicit terms; a data pilot does not imply executable liquidity or a regulated hedge product.

The variable fee curve is also outside the default pilot. It stays disabled until deployed program support, an external audit, legal and accounting approval, and end-to-end fee parity are all documented. See docs/COMMERCIAL_LEGAL_ACCOUNTING_REVIEW_PACKET.md for the sign-off record.

Pilot categories

Good first institutional categories:

• commodity, weather, and catastrophe risk
• macro releases and rate decisions
• public-company event risk
• supply-chain and geopolitical disruption
• crypto treasury and protocol-risk events

Automatic inventory writes are intentionally narrower than the public taxonomy. The current production supply wedge is Climate, Economics, Finance, and Crypto. Other categories remain requestable and source-mapped, but should be created only after named demand, a reviewed source, and a first-liquidity plan exist.

Each pilot should name:

• target user
• hedge use case
• settlement source
• market lifecycle
• expected liquidity model
• compliance boundary
• data fields delivered

Data products to sell first

Start with privacy-safe products:

• market and request demand rankings
• event metadata and lifecycle history
• orderbook depth and spread summaries
• trade and volume aggregates
• resolution outcomes and evidence packages
• derived liquidity and volatility signals

Avoid selling raw identity, KYC, contact, device, or precise location data.

Commercial path

1. Free public docs and a delayed self-serve sample.
2. Builder Pro for real-time internal tools.
3. Contracted event-risk monitoring and evidence pilots.
4. Execution pilots with maker coordination only after proof gates pass.

Required proof before scaling

• repeated demand-backed market requests
• at least one first-liquidity partner per category
• reliable settlement evidence
• data dictionary and license terms
• market-quality history
• security and control docs
• incident and dispute process

Operator commands

npm run founder:daily
npm run founder:action-pack
npm run founder:priority-plan
npm run market:requests:triage
npm run market:expansion:evaluate -- --candidate config/templates/market-expansion-candidate.json
npm run opportunity:plan
npm run bot:starter:dry-run

Use founder:daily first. It combines demand-backed requests, first-maker signals, social headline drafts, and data-sales next steps before you decide whether to create markets, recruit makers, publish content, or sell data access. With an admin token, it uses /api/admin/founder/revenue-loop for private request and lead signals; without one, it falls back to public/env signals. Use founder:action-pack for internal copy review. Data-buyer and institutional outreach remains disabled until the production dataset, redistribution rights, delivery reliability, and resolution evidence pass the commercial-readiness gate. Use founder:priority-plan when you need the ranked solo-founder work queue: it combines money controls, payment rails, data products, developer starters, request-backed opportunities, and institutional pilots into easiest-profitable, hard-profitable, and blocker buckets.

Related docs

• docs/public/DATA_LICENSE_AND_COMMERCIALIZATION.md
• docs/public/DATA_API.md
• docs/public/LIQUIDITY_PARTNERS.md
• docs/public/MARKET_LISTING_STANDARDS.md
• docs/RISK_MARKET_TAXONOMY.md