Continuity

Protected agent markets that keep following their stock quote.

Continuity is a launch, protection, and treasury platform for AI-agent tokens that trade against tokenized stocks on Solana. An operator connects a wallet, selects a ClawPump agent they control, defines that agent's token, and chooses a verified PreStocks stock token as the asset buyers will pay with. Continuity checks the exact stock mint and issuer lifecycle, prepares a stock-aware Meteora market, simulates the complete transaction, and asks the operator's wallet for the only signature that can launch it.

The product does not stop at launch. Every confirmed market is registered under Protected markets, where Continuity Sentinel continues checking the stock token, Meteora configuration, bonding-curve progress, fees, reserves, and later migration. If the stock token is retired or replaced, Continuity stops its own managed automation from deepening the obsolete market, explains why, and helps the operator prepare a separately reviewed successor market. It cannot rewrite or freeze the old pool.

Each protected market also has an Agent treasury. Continuity verifies that the bound ClawPump agent is the market's real onchain fee authority and shows the partner fees Meteora has recorded for it, separately from trader liquidity and the human operator's wallet. The complete goal is to track agent fees and put them to work through guarded yield. Reading and verifying those fees is live today. Claiming, swapping, and depositing them into a lending vault remain deliberately locked until the exact agent wallet has a supported, reviewable signing route.

This is already producing real mainnet protocol revenue. The confirmed CONT/SPCXx pool currently reports 308,601 raw fee units, equal to 0.00308601 SPCXx, as claimable partner fees for its bound agent. That value is live Meteora accounting—not fixture data—but it remains unclaimed. It is not yet wallet cash, guaranteed fiat value, or lending yield.

Public users can inspect stock lifecycles and protected markets without a wallet. Operators use the five-step launch flow. ClawPump agents can run the same safety policy through the Continuity skill or paid x402 service, while Claude, Codex, and other applications can use the read-only MCP/API. None of those agent interfaces receives unrestricted signing authority.

In one line:

owned ClawPump agent + new agent token + verified stock quote
  → wallet-approved Meteora market
  → continuous Sentinel protection
  → agent treasury: track fees → guarded yield

Start here: docs/product-flow.md explains the complete product in plain language: who uses it, where each token comes from, why only SPCXx is currently launch-ready, what the launch creates, what users do after launch, and which boundaries remain. Confirmed mainnet proof is indexed in docs/mainnet-transaction-evidence.md. External MCP, ClawPump skill, and x402 verification is documented in docs/external-agent-access.md. The website also includes a concise, single-page guide at /docs.

Understand the product: what Continuity is, one market from start to finish, Meteora DBC in plain language, and what happens after launch.
Inspect the proof: what works today, confirmed mainnet transactions, and what is not live yet.
Understand trust and ownership: persistence, roles and authority, and source architecture.
Run and integrate: local setup, agent access, environment, quote eligibility, agent treasury, and verification.

What Continuity is

Continuity serves one connected lifecycle rather than a collection of unrelated tools:

Product surface	What a person or agent accomplishes there
Markets	Browse the complete current PreStocks catalog, see which instruments are current or retiring, inspect exact source evidence, and open every market launched through Continuity. No wallet is required.
Launch	Pair an owned ClawPump agent and its new token with an eligible stock quote, review the bounded Meteora design, run a live Solana simulation, and explicitly approve the transaction in the operator wallet.
Protected markets	Open the live trade route, pool account, launch transaction, curve progress, and latest Sentinel result for each confirmed market.
Activity	Review automatic and on-demand lifecycle checks, deterministic verdicts, evidence hashes, receipts, and alerts.
Treasury	Track the real Meteora fees earned by each market's agent and, once the guarded claim-and-vault path is enabled, put those earnings to work without giving Continuity custody.
Skill, x402, and MCP/API	Let ClawPump agents and external applications request the same source-backed decision without receiving wallet custody or permission to launch.

This makes Continuity different from a generic token launcher and from a stock directory. The protected market is the product: verified before creation, observable while it trades, monitored after launch, and connected to the revenue of the agent responsible for it.

One protected market from start to finish

1. Choose the agent and define its token

The operator connects a Solana wallet and either selects a ClawPump agent they control or creates one through Continuity. They then define the new token for that agent or service. In the reference market, the agent is Continuity Sentinel and the token is CONT.

CONT now exists on Solana at Hae9…epua. Its name and ticker are Continuity product choices; PreStocks, ClawPump, Meteora, and Pyth did not issue it.

2. Choose the stock people will pay with

The operator chooses an eligible PreStocks token as the quote asset. In CONT/SPCXx, a buyer pays with SPCXx to receive CONT. Continuity verifies the exact mint rather than trusting a ticker, checks the issuer lifecycle, transfer behavior, Meteora compatibility, executable route, and independent market reference.

This matters because SPACEX and SPCXx are different Solana tokens even though both represent SpaceX exposure. PreStocks announced that SPACEX will expire and named SPCXx as its successor. Continuity preserves that source and the two exact mint addresses in a machine-readable lifecycle manifest.

Source: PreStocks SpaceX lifecycle notice

3. Review and create the market

Continuity turns the selected agent, new token, and verified stock quote into a bounded Meteora DBC configuration. The operator reviews the pricing and fee policy in product language. Continuity then builds the exact Solana instructions, lists the accounts that will be created or changed, checks both wallets, and simulates the transaction.

Only after every required check passes does the operator's wallet receive the final approval request. A successful signature creates the new token and its first stock-quoted market through Meteora's programs on Solana. The market is not hosted inside Continuity; Continuity registers and protects the onchain result.

4. Keep Sentinel attached after launch

Sentinel keeps checking the same stock mint, issuer lifecycle, DBC configuration, curve progress, fees, reserves, and migration state. The market appears under Protected markets with Trade, Pool, and Launch links. Activity stores the matching evidence and decision history.

If the stock later retires, Sentinel stops Continuity-managed actions and removes Continuity's Trade action. It does not seize user funds or modify the old pool. Instead, it preserves the reason and prepares a separately reviewed successor market for operator approval.

5. Track agent fees and prepare them to earn

Meteora can record part of the trading fees for the ClawPump agent configured as the market partner. Treasury reads those fees directly from the pool, checks that the registered agent is the real fee authority, and shows the SOL the agent keeps for operating costs. The intended next step is to claim a policy-capped amount and supply it to one reviewed yield vault so idle agent revenue can earn without exposing trader liquidity.

The treasury is currently read-only. Displayed claimable fees are real onchain accounting, but they have not entered the agent wallet and are not yield. Claiming and vault deposits remain locked until the exact ClawPump agent can review and sign the required transaction through a supported public route.

6. Reuse the decision outside the website

The same lifecycle and market decision is available through the Continuity ClawPump skill, a paid x402 service, and read-only MCP/API tools. This lets an agent check a market before acting or sell a verified scan to another agent. Payment buys the answer, never transaction authority.

Terms used below

A mint is the unique Solana address for one exact token.
The base token is the new agent token being launched, such as CONT.
The quote token is what buyers pay with, such as SPCXx.
A pool is the onchain market account holding the pricing and liquidity rules.
Graduation is when a successful opening curve migrates into a regular Meteora DAMM v2 liquidity pool.

What Meteora DBC means

DBC means Dynamic Bonding Curve. In plain terms, it is the launch engine that creates the new agent token and opens its first automatic market on Solana.

At the beginning there is no traditional order book waiting for one buyer and one seller to match. Meteora uses a reviewed pricing curve instead:

a buyer pays with the chosen stock quote token;
the curve calculates how much of the new agent token the buyer receives;
the price changes as buying and selling change the pool's reserves;
trading fees are recorded by Meteora; and
when the reviewed quote-token target is reached, liquidity graduates into a normal Meteora DAMM v2 pool.

Continuity does not invent that market math or hold the pool's money. It checks the exact stock token, explains the settings, simulates the launch, requires a human wallet signature, records the resulting addresses, and watches the market afterwards. Meteora's official DBC overview describes the underlying launch and graduation system.

The complete SpaceX example

SPACEX is an existing PreStocks token.
PreStocks announces that SPACEX will expire and identifies SPCXx as its successor.
Continuity captures the source, verifies the exact mints, and creates a lifecycle manifest.
Users, applications, and ClawPump agents can see that SPACEX is retiring.
If a registered market depends on SPACEX, Sentinel returns ROLLOVER_REQUIRED and stops Continuity-managed actions through that market.
Continuity prepares a new market configuration using the verified successor SPCXx rather than silently changing the old pool.
The operator reviews the assets, DBC policy, accounts, and simulation.
Continuity rebuilds the transaction with a fresh blockhash and simulates it again.
Only the operator's wallet can approve and submit the transaction.
Once confirmed, Continuity records the resulting Meteora configuration and pool addresses and begins post-launch monitoring.

What happens after a launch?

A confirmed launch is not the end of the product flow:

Meteora DBC holds the live bonding-curve market on Solana. Buyers can exchange the verified stock quote for the new agent token while the curve is active.
Jupiter can route users into that liquidity. Continuity's Protected markets table opens the exact buy/sell pair in Jupiter and links to the pool and launch transaction on Solscan.
Continuity Sentinel keeps checking the stock quote, curve, fee settings, reserves, and graduation state.
When the curve reaches its reviewed target, Meteora migrates liquidity to the configured DAMM v2 pool.
If the stock quote later retires or becomes unsafe, Continuity removes its Trade action, stops Continuity-managed automation, alerts the operator, and preserves the evidence needed to prepare a successor market. It does not freeze or rewrite the old pool.

Trading and custody remain with the user's wallet and Solana protocols; Continuity is the safety, launch-review, and monitoring layer around the market.

The current CONT/SPACEX screen is a clearly labelled demo replay of steps 4–6; there is no live CONT/SPACEX pool. The real reference market is CONT/SPCXx: it was confirmed on Solana mainnet on 25 September 2026 and is registered for Sentinel monitoring. The replay explains the rollover problem; the live market proves the protected successor path.

How automatic monitoring works

Monitoring is automatic after a protected market is registered:

Vercel calls Continuity's protected scheduler once per day on the current free deployment plan.
Continuity refreshes the issuer lifecycle record and loops through every registered protected market.
For each market it reads the expected quote mint and current Meteora pool state, then runs the same deterministic safety rules used before launch.
The result, evidence hash, market snapshot, and any alert are stored in Supabase.
Markets shows the latest protection state, while Activity keeps the append-only run history.

The Check now action and the protected API endpoint only request an extra immediate run; they do not replace the schedule. No wallet is signed and no funds move during a monitoring check.

ClawPump automations are an additional agent-facing path. They can ask for the same Continuity verdict on their own schedule and explain it to an operator or paid x402 customer. The core market monitor still runs even when nobody opens the website and even when a ClawPump chat is idle.

Why launch `CONT/SPCXx` at all?

Continuity is not primarily a token launchpad. CONT/SPCXx is the first-party market for the Continuity Sentinel agent and proves the full product loop:

issuer lifecycle evidence
          ↓
exact-mint safety verdict
          ↓
stock-aware Meteora DBC configuration
          ↓
unsigned transaction and Solana preflight
          ↓
explicit operator approval
          ↓
registered market and continuous monitoring

Launching an arbitrary token against an arbitrary stock would not prove the safety claim. Pairing the reference token with SPCXx demonstrates that the launch configuration is derived from a verified successor instrument and that the same lifecycle policy can later protect the resulting market.

Is Continuity "Pump.fun with stocks"?

Not by itself. ClawPump already supports launching an owned agent's token against an approved custom Pump.fun quote asset. Its live pair catalogue includes many tokenized stocks. Rebuilding only that form would duplicate an existing ClawPump capability and would not explain what happens when a quote token is retired or replaced. See the ClawPump Partner API.

Continuity's stronger workflow is Create protected agent market:

authenticate an owned ClawPump agent;
define the token representing that agent or its service;
choose a lifecycle-verified stock quote asset;
apply a stock-aware Meteora DBC policy;
simulate and approve the launch;
keep Sentinel attached to the resulting market; and
track the agent's market fees, then route claimed earnings into policy-approved yield vaults once agent-authorized signing is available.

This makes ClawPump's agent identity, wallet, skills, automations, and revenue surface part of the product while Meteora supplies the distinctive launch and liquidity mechanics.

The direct ClawPump custom-pair route remains useful as a compatibility path for assets in ClawPump's approved Pump.fun catalogue. At the time of verification, that catalogue contained a different SpaceX asset named SPCX, but not the exact PreStocks successor mint SPCXx used by this reference implementation. Continuity therefore builds the SPCXx flagship through Meteora's official DBC SDK instead of pretending that ClawPump currently exposes that exact pair.

The live PreStocks catalog currently contains eight instruments. Continuity monitors all eight, but catalog presence does not automatically mean launch eligibility. SPCXx is the only fully reviewed quote asset in the current reference-launch adapter. The eight current PreStocks mints are not silently enabled: each must independently pass exact-mint, Token-2022 transfer-policy, Meteora token-badge, executable-route, and market-reference checks. A monitored instrument can therefore be visible while remaining unavailable for launch.

What is configurable?

Meteora DBC controls the bonding curve used for initial price discovery, its fee schedule, the quote amount required for graduation, the liquidity split, and migration into the eventual DAMM pool. See the official DBC overview.

The current CONT/SPCXx configuration is deliberately fixed and hashable:

new CONT mint with a fixed one-billion-token supply and six decimals;
existing SPCXx mint as the quote asset;
dynamic opening fee that settles from 100 to 25 basis points over 15 minutes;
a graduation threshold recalibrated to approximately $1,000 of SPCXx;
migration to Meteora DAMM v2;
permanently locked migrated liquidity split between creator and partner.

The protected-agent-market wizard now exposes the owned ClawPump agent and base-token metadata. Market design remains deliberately bounded to the reviewed equity profile while the first launch is proven; broader supply, fee, graduation, and allocation choices can be added as versioned safe presets. Safety invariants are not optional: the exact quote mint, source-backed successor, retired-asset rejection, fresh reference checks, simulation, and human wallet approval cannot be switched off.

Product paths

Public user

Open Markets
  → inspect the eight current instruments
  → open an instrument
  → read its lifecycle status and evidence
  → no wallet required

Confirmed reference market

Open Markets
  → review the live PreStocks catalog under Stock coverage
  → find CONT / SPCXx under Protected markets
  → inspect its Sentinel status, curve progress, latest check, and Solscan launch
  → open SpaceX to trace SPCXx back to the SPACEX lifecycle evidence

The locked CONT/SPCXx workflow has already completed. It is retained as the project's reproducible mainnet proof, not as a second launch mode in the product. The Launch page now focuses on creating the next protected market.

Custom protected-market operator

Open Launch
  → connect a Solana wallet
  → sign the one-time Continuity login message
  → create or select a ClawPump agent mapped to that wallet
  → define the new agent token
  → select a launch-enabled stock quote asset
  → save the operator-owned draft in Supabase
  → review the bounded stock-aware Meteora design
  → build and store the exact preflight result
  → continue only after simulation passes
  → approve and submit in the same verified operator wallet
  → register the confirmed market and begin monitoring

ClawPump or external agent

Call the Sentinel skill, API, or MCP
  → request an instrument or quote-rail scan
  → receive a deterministic verdict and proof
  → never receive unrestricted wallet authority

Active-market monitoring

Read a registered Meteora market
  → reconcile quote mint and reviewed configuration
  → monitor DBC progress, migration, fees, reserves, and lifecycle evidence
  → stop only Continuity-managed actions when policy fails
  → alert the operator and prepare a new reviewed market

What the current build can do

Public, automatically scanned registry of all eight current PreStocks instruments
Per-instrument lifecycle detail and source-evidence views
Verified SPACEX → SPCXx lifecycle manifest
Deterministic LAUNCH_SAFE, MANUAL_REVIEW, LAUNCH_BLOCKED, and ROLLOVER_REQUIRED verdicts
Wallet-free /demo replay and live-read /app workspace
Composite stock reference from direct Jupiter routes cross-checked with Pyth
Stock-aware $1,000 Meteora graduation calibration
Canonically hashed Meteora DBC configuration built with the official SDK
Authenticated ClawPump agent binding for fee and leftover-receiver roles
Exact unsigned creation transaction, account diff, wallet prerequisites, and Solana simulation boundary
Solana wallet challenge authentication with replay-resistant, hashed sessions
Supabase ownership for operators, mapped ClawPump agents, protected-market drafts, and stored preflight results
A focused five-step protected-market launch workflow with locked safety gates
Idempotent final transaction preparation, wallet sign-and-send, Solana confirmation, exact-account verification, and confirmed-market registration
Scheduled registered-market monitoring for quote identity, lifecycle state, DBC curve progress, graduation, fee configuration, and reserves
Public Markets view for confirmed protected markets, latest Sentinel status, curve progress, last check, and launch transaction
Durable Supabase lifecycle manifests, Sentinel runs, decision receipts, monitoring snapshots, and operator alerts
ClawPump Sentinel skill, x402-shaped scan endpoint, and read-only MCP tools
Hash-chained Sentinel and monitoring evidence
Confirmed CONT/SPCXx and operator-created ORBIT/SPCXx mainnet markets, each with a persisted POOL_LIVE post-launch scan
Read-only agent treasury views that verify the live Meteora fee authority, show claimable partner fees, and keep those fees separate from pool liquidity

What is not live yet

The remaining work is intentionally narrow and visible:

Only the exact SPCXx mint is launch-enabled. Every additional stock quote still needs compatible Meteora support and the same live identity, lifecycle, transfer, route, and price checks.
Broader DBC presets can be added only after they receive the same policy, account-review, simulation, and post-launch monitoring coverage.
Sentinel currently runs daily on the hosting plan. A paid scheduler or external keeper can increase cadence and add stronger retry guarantees.
Agent fees can be read and attributed, but the agent cannot claim them until ClawPump exposes a supported bounded Meteora claim or reviewed transaction signing route.
Treasury yield remains disabled until fee claiming, reserve limits, one allowlisted vault, withdrawal testing, reconciliation, and receipts are all proven end to end. Nothing is automatically swapped or deposited today.
The paid x402 endpoint is deployed, but its observed payment header must be corrected from devnet to mainnet before the first real paid request.
The live DBC markets have not graduated yet. Continuity will record the DAMM v2 destination only after Meteora creates it at the configured curve target.
Replacing a quote token requires a new reviewed market. Continuity cannot rewrite an existing pool or preserve its base mint through the current DBC creation route.

Claimable fees are real onchain accounting, but they are not the same as cash in the ClawPump wallet and they are not yield. Their realizable value depends on a successful claim and, if conversion is desired, a safe executable route.

Roadmap

Close the remaining external-agent proof. The MCP, interactive ClawPump skill, Cloud Service deployment, and unpaid x402 discovery paths are verified. Resolve the gateway's mainnet/devnet payment mismatch before one paid x402 call; if used in the submission, also capture one scheduled ClawPump automation run.
Enable bounded agent fee claims. Integrate a ClawPump-supported Meteora partner-fee claim action, show the decoded transaction, simulate it, require explicit approval, and store the returned signature and balance change.
Add a guarded treasury policy. Preserve an agent SOL reserve, cap every conversion and deposit, allow one reviewed SOL/USDC lending destination, and prove withdrawal before enabling any schedule. No borrowing or leverage.
Increase monitoring cadence and resilience. Add a production RPC with an SLA, more frequent scheduling, retry observability, and operator alerting.
Expand launch-ready stock quotes. Enable another PreStocks mint only after its exact mint, lifecycle, transfer behavior, Meteora compatibility, price reference, and executable route all pass.
Support true successor pools for existing base tokens. Add a reviewed AMM route that can create a new quote pool without pretending an old pool can be rewritten.

Confirmed mainnet proof

Two end-to-end launches are complete. The reference market is:

market: CONT / SPCXx;
transaction: 3Sbk…zch4;
CONT mint: Hae9…epua;
SPCXx quote mint: Xs3oZwbHvqis4NYcf4YKWmEia2eC84wSiVrcYcTqpH8;
Meteora DBC configuration: GVmofTcACEyQEdPGTLqiXeZNYBiCEX8wcr7mAkgHSYc;
Meteora virtual pool: HSokfXowJKiSvDoQtR3oVTuvBJ7kneUqZVE9pypZCnib;
finality: finalized at slot 450328456;
Supabase state: launch attempt CONFIRMED, protected market ACTIVE.
first monitoring receipt: 6de402b9…ef218 with lifecycle CURRENT and DBC state POOL_LIVE.

The custom operator flow independently launched ORBIT/SPCXx:

transaction: 5a7M…BK28;
ORBIT mint: CuRA…jkgG;
Meteora DBC configuration: AtDU5jy5eprpEaDpWtBZztkycvJRqaNGSBSExHq6Ya1b;
Meteora virtual pool: EBAYsw8Y9HzVinacauNAx11um8QUNAsLCShNeNV8M7jn;
first monitoring receipt: 8b871cd2…74b08 with lifecycle CURRENT and DBC state POOL_LIVE.

Live fee accrual

The CONT/SPCXx pool currently reports 308,601 raw partner-fee units, or 0.00308601 SPCXx, claimable by the configured ClawPump agent authority. This is the first verified revenue signal from a Continuity-launched market on Solana mainnet. It proves fee accrual, not fee custody: the amount remains in Meteora's accounting until the exact agent wallet can approve a supported claim transaction. See docs/agent-treasury.md.

Independent finalized RPC reads confirm that the mint exists under the SPL Token program and that the configuration and virtual pool exist under Meteora DBC. The complete human-readable record is in docs/mainnet-transaction-evidence.md.

Persistence and ownership

Solana remains the source of truth for token mints, signatures, Meteora configuration accounts, and pool accounts. Supabase indexes the offchain ownership and launch workflow around that state:

authenticated operators and their owned ClawPump agents;
protected-market drafts and their configuration hashes;
preflight attempts and simulation results;
idempotent launch attempts and transaction signatures;
confirmed base mint, DBC configuration, virtual-pool, and later migration-pool addresses;
lifecycle manifests, Sentinel runs, decision receipts, monitoring snapshots, and operator alerts.

The migration-pool address is intentionally null at initial DBC launch. That pool does not exist until the curve graduates and Meteora performs migration; Sentinel records it when it becomes real rather than inventing it at launch.

The database must never store wallet private keys. Operators authenticate with a wallet-signature challenge and sign transactions in their wallet.

The browser never receives the Supabase server secret. All database access runs through server routes, public roles have no table privileges, row-level security is enabled, session tokens are stored only as hashes, and the database never stores wallet private keys.

Sponsor roles

PreStocks supplies the stock instruments and lifecycle evidence.
ClawPump hosts the Sentinel AI agent, its optional agent automations, the installable skill, and paid scan distribution. Continuity's core daily market monitor runs independently through the Vercel scheduler.
Meteora supplies the DBC and DAMM programs that create and operate the stock-quoted market.
Jupiter supplies executable routes used to estimate the stock token's market value and may route swaps after launch.
Pyth independently cross-checks the reference market used by policy.
Solana supplies token accounts, wallet approval, transaction simulation, execution, and the permanent onchain market state.

Product roles and authority

Role	Can do	Cannot do
Public visitor	Browse instruments, lifecycle evidence, deadlines, and replayed decisions without a wallet	Create drafts, approve launches, or control agents
Human operator	Verify wallet ownership, map an owned ClawPump agent, create a draft, run preflight, and explicitly approve a launch	Manage another operator's drafts or bypass safety gates
Continuity reference operator	Use the wallet configured in `CONT_OPERATOR_WALLET` to approve the locked `CONT/SPCXx` reference launch	Substitute a different token, quote mint, agent, or policy inside the locked template
ClawPump Sentinel agent	Run scheduled/on-demand checks, expose the skill and paid scan, receive configured partner roles, and stop its own managed actions on a failure	Sign as the human operator, take custody of the operator wallet, or freeze third-party pools
External agent or application	Query the API/MCP for instruments, evidence, verdicts, and proofs	Receive unrestricted signing authority
Meteora programs	Create and operate the reviewed DBC market and later DAMM migration	Decide whether issuer lifecycle evidence is trustworthy

The two wallets are deliberately different. CLAWPUMP_AGENT_ID resolves the Sentinel agent wallet used for partner economics and automation. The connected human wallet owns the draft, pays account-creation/network costs, and supplies the only final approval signature.

Source architecture

All authored application code is TypeScript or TSX.

src/
  app/                    # Next.js routes and API surfaces
  components/             # Shared visual modules
  domain/continuity/      # Pure lifecycle, policy, hash, and receipt rules
  features/dashboard/     # Product workspaces and launch review UI
  features/home/          # Homepage and sponsor/product explanation
  features/wallet/        # Solana wallet and RPC access
  integrations/           # PreStocks, ClawPump, Meteora, Jupiter, and Pyth
  persistence/            # Supabase ownership, launch, and monitoring records
  services/               # Deterministic orchestration
  transactions/           # Meteora transaction construction and preflight
skills/
  continuity-sentinel/    # ClawPump skill package
supabase/
  migrations/             # Operator ownership and launch-state schema
docs/                     # Public product, verification, and evidence guides
.github/workflows/        # Secret-free CI verification

Route files compose features; domain modules contain no React or Next.js dependencies. eslint.config.mjs is ESLint configuration, not application source. TypeScript compilation is strict and allowJs is disabled.

Run locally

pnpm install
cp .env.example .env.local
pnpm dev

Configure Supabase

Create a Supabase project.
Open Project Settings → API Keys and copy the project URL and a server-only secret key into .env.local:
```
SUPABASE_URL=https://YOUR_PROJECT_REF.supabase.co
SUPABASE_SECRET_KEY=sb_secret_YOUR_SERVER_KEY
```
Apply all migrations in order:
Alternatively, after linking the Supabase CLI to the project, run supabase db push from the repository root.
Restart the app and open /api/health. integrations.supabase.status should be ready_for_launch_and_monitoring.

For an older project, SUPABASE_SERVICE_ROLE_KEY is accepted as a legacy fallback. New projects should use SUPABASE_SECRET_KEY. Do not prefix either variable with NEXT_PUBLIC_, commit the secret key, or paste it into client code. Add the same two server-side variables to Vercel before testing the deployed custom launch flow.

Open:

http://localhost:3000 — product site
http://localhost:3000/docs — single-page product guide
http://localhost:3000/demo — wallet-free lifecycle replay
http://localhost:3000/app — live-read product workspace
http://localhost:3000/app/activity — automatic and requested Sentinel history
http://localhost:3000/app/markets/spacex — SpaceX lifecycle detail
http://localhost:3000/app/launch — create a new protected market
http://localhost:3000/app/treasury — inspect agent fees and operating reserves

Agent access

ClawPump skill: skills/continuity-sentinel/SKILL.md
Interactive ClawPump skill scan: GET /api/v1/scans/quote-rail
Paid x402 scan origin: POST /api/v1/scans/quote-rail
Sentinel runs: GET/POST /api/v1/sentinel/runs
Scheduled lifecycle and protected-market monitor: GET /api/v1/sentinel/schedule
Read-only agent treasuries: GET /api/v1/treasuries
MCP endpoint: POST /api/mcp

The MCP server exposes list_market_lifecycle, get_market_evidence, and run_quote_rail_scan. Payment never grants transaction or signing authority. The Activity page refreshes automatically every 15 seconds and paginates the latest 100 durable Sentinel records in pages of eight.

Production environment variables

The essential Vercel secrets are:

CLAWPUMP_API_KEY — lets the server create and verify ClawPump agents;
PYTH_PRO_API_KEY — supplies the independent price cross-check;
SUPABASE_URL and SUPABASE_SECRET_KEY — store operators, launches, monitoring checks, and history;
CRON_SECRET — protects the automatic daily monitor endpoint.

The first-party reference settings are:

CLAWPUMP_AGENT_ID — Continuity Sentinel's ClawPump agent ID;
CONT_OPERATOR_WALLET — the human wallet that approved the completed CONT reference launch;
CONT_TOKEN_METADATA_URI — the published CONT metadata URL;
METEORA_DBC_CONFIG_ADDRESS and METEORA_DBC_POOL_ADDRESS — the confirmed CONT/SPCXx accounts that the reference Sentinel scan inspects.

Set SOLANA_RPC_URL to a reliable mainnet RPC for server reads and NEXT_PUBLIC_SOLANA_RPC_URL to a browser-safe mainnet RPC for wallet actions. JUPITER_API_KEY remains optional. The exact copyable checklist and public mainnet addresses are documented in docs/product-flow.md and docs/mainnet-transaction-evidence.md.

Mainnet launch prerequisites

Before intentionally launching another protected market:

Set CONT_OPERATOR_WALLET to the human Solana wallet that will sign.
Apply all Supabase migrations.
Fund that human wallet for Solana account creation and transaction fees.
Fund the configured Continuity Sentinel agent wallet enough for its required onchain account to exist.
Set CRON_SECRET in Vercel so the scheduled registered-market monitor can authenticate.
Open /app/launch, verify the operator wallet, run preflight, inspect every account change, and approve only if the wallet request matches the review.

Every deliberate ClawPump-agent funding transfer, submitted launch attempt, confirmed Meteora address, and first post-launch Sentinel result must be added to docs/mainnet-transaction-evidence.md. Supabase remains the machine-readable source of launch and monitoring records; the document is the public evidence index. Never place secrets or signed transaction payloads in the repository.

No mainnet transaction is sent merely because these variables are configured. Execution is disabled by default in the sense that public reads, scans, drafts, and simulations never sign. Only the final explicit wallet approval sends the reviewed transaction.

Why only `SPCXx` can launch today

Continuity monitors the complete eight-asset PreStocks catalog, but monitoring does not imply that every mint can be used as a Meteora DBC quote token. The launch wizard currently enables SPCXx, the verified SpaceX successor. Live audits of the seven current PreStocks issuer mints confirm their catalog identity and Jupiter routes, but the mints currently lack the required Meteora DBC quote badge and expose transfer-fee behavior that the current launch path cannot safely approve. Continuity shows those assets in the selector and on their detail pages, but fails closed until the onchain requirements pass.

In simpler terms: imagine Meteora DBC is a vending machine and the stock token is the payment card. SPCXx currently has the permission mark and payment behavior the machine understands. The other seven cards are real, but the machine does not yet support their fee rules and has not approved them for this use. Continuity therefore watches those assets but does not let a user start a launch that Meteora would reject.

This is a Meteora compatibility boundary, not a UI whitelist. When a mint gains compatible DBC support, Continuity must add its price-reference adapter and the mint must pass the same live identity, lifecycle, badge, transfer-policy, route, and price-reference audit before launch approval is enabled.

What is a transfer fee?

A normal token transfer moves the full amount from one account to another. A token with a transfer fee automatically removes a small portion during that move. For example, sending 100 units with a 1% transfer fee can deliver only 99 units to the destination.

That difference matters inside an automated market: the market must calculate prices and reserves using the amount it actually receives, not the amount the sender requested. The seven other live PreStocks mints use transfer-fee behavior that the current Meteora DBC quote-token route does not safely accept, and they do not currently have the required Meteora token badge. Continuity therefore monitors them but refuses to advertise a launch that the reviewed route cannot complete correctly.

Agent treasury

Continuity's Agent treasury is designed to let an agent track its market fees and put eligible earnings to work through guarded yield. Its live surface is currently read-only: it reads the Meteora partner-fee balance, verifies that the onchain fee authority is the market's bound ClawPump agent, and shows that agent wallet's SOL operating reserve. The figures refresh automatically and no signature is requested.

This is deliberately not a vault for public deposits. It never counts or moves trader liquidity, user tokens, or the human operator's wallet balance. If the fee authority does not match the registered agent, or Sentinel has paused the market, the treasury displays the problem instead of enabling an action.

The complete intended path is:

Read live Meteora partner fees
  → verify the market's bound ClawPump agent is the fee authority
  → claim only that agent's earned fees
  → keep a fixed operating reserve
  → optionally convert a capped amount to a supported asset
  → supply it to one allowlisted Solana lending vault
  → record every movement and pause automatically on Sentinel risk

Only the first two steps are live today. Claiming and lending remain locked. Meteora's current DBC SDK provides claimPartnerTradingFee and returns an unsigned transaction whose fee payer and required authority must sign. ClawPump does sign transactions through approved, purpose-built tools—such as swaps, wallet transfers, lending, and x402 payments—but, as checked on 25 September 2026, its public Partner API and official 134-tool catalog do not document a generic Solana transaction signer or a Meteora partner-fee claim tool.

That is a statement about the current supported public integration surface, not a claim that ClawPump has no internal signing capability. Continuity will not export the agent private key, call an undocumented internal route, or ask the human operator to impersonate the agent.

Integration request for the ClawPump team

Continuity needs either a bounded meteora_claim_partner_fees tool or a reviewed arbitrary-transaction approval flow. The safe interface should:

verify that the requesting user controls the agent;
allowlist the Meteora program and exact claim instruction;
show decoded instructions, accounts, fee amounts, and destination;
simulate before signing and enforce maximum claim/spend values;
require explicit confirmation and an idempotency key; and
return the Solana signature and post-transaction balance evidence without exporting the private key.

Once that supported route exists, Continuity can add an honest Claim button and then proceed to one capped SOL/USDC lending destination—no borrowing, leverage, or automatic destination changes.

Primary references: Meteora's DBC method and signing reference, ClawPump's official tool catalog, ClawPump Partner API, and Jupiter Lend. The implementation phases and trust boundaries are specified in docs/agent-treasury.md.

Verification

pnpm typecheck
pnpm lint
pnpm test
pnpm build
pnpm sentinel:run

With Supabase configured, live Sentinel API/MCP runs write durable hash-chained records and decision receipts there. The CLI still uses the same store boundary; without Supabase it falls back to .continuity-data/, which is ignored by Git. Only user- and judge-facing product, verification, and evidence documents are kept under docs/.

Name		Name	Last commit message	Last commit date
.github/workflows		.github/workflows
docs		docs
public		public
scripts		scripts
skills/continuity-sentinel		skills/continuity-sentinel
src		src
supabase/migrations		supabase/migrations
.env.example		.env.example
.gitignore		.gitignore
AGENTS.md		AGENTS.md
README.md		README.md
eslint.config.mjs		eslint.config.mjs
next-env.d.ts		next-env.d.ts
next.config.ts		next.config.ts
package.json		package.json
pnpm-lock.yaml		pnpm-lock.yaml
tsconfig.json		tsconfig.json
vercel.json		vercel.json

Latest commit

History

Folders and files

Repository files navigation