Delta Signal ATLAS-7 Full Agent Brief
Version: llms-full-v13
Last updated: 2026-07-21
Audience: Codex, Claude Code, Cursor, MCP clients, IDE agents, integration reviewers
Status: canonical public operator brief for the live GitHub Pages surface; refreshed after the July 15 issuer-wide calculation replay, customer-route audit, and governed semantic MCP verification.

Purpose
This file is the shortest public document that still captures the live Delta Signal operator contract. Read it before changelogs, before examples, and before hard-coding route, pricing, grant, or parser assumptions.

One-screen summary
- Delta Signal ATLAS-7 is a filing-backed issuer-intelligence service for crypto-exposed public companies and DeltaSignal Synthetic Baskets.
- The public surface is REST + MCP + OpenAPI + Arazzo + x402-compatible payment behavior + signed wallet grant sessions. Public clients should not request or store Delta Signal API keys. Standard Base x402 is the compatibility-first requirement at `accepts[0]`; Circle Gateway is an explicitly selectable additive path at `accepts[1]` for Circle-aware clients that support `GatewayWalletBatched`.
- ProofPay for DeltaSignal is an additive Hedera testnet x402 preview deployed as a separate Azure backend. It is not a new `accepts[]` entry on the Base `/v1/*` or `/mcp` challenges. It creates single-use quotes, returns a Hedera HBAR HTTP 402 challenge for sealed evidence, mirror-verifies settlement, and issues an Ed25519 payment-to-artifact receipt.
- Public-facing basket language uses DeltaSignal Synthetic Basket names. Do not expose third-party basket-provider branding in public summaries unless the live route explicitly returns it as source metadata.
- The product is evidence-first. It is not a trading bot, not a retail signal room, and not an investment-advice surface.
- Public discovery starts with `openapi.json`, `/v1/pricing`, `/v1/contract/fields`, MCP `initialize`, and MCP `tools/list`.
- Natural-language MCP help is live through the free discovery-tier `deltasignal_help` tool. Use it before paid workflows when a user asks "help", "what can I ask?", "help perps", or "show examples".
- AI10-specific discovery starts with `deltasignal_help`, especially `help groups` and `help synthetic ai10`.
- Synthetic AI10 audit mode is live through REST and MCP for driver, threshold, export, publication-safety, and event-confirmation questions.
- Signed grant-session tokens authorize grant-covered requests. Plain unsigned wallet headers are intentionally not enough. The backend maps enrolled wallets to database-managed grant records and grant runway fields.
- `/v1/pricing` is the public pricing source of truth. `/v1/contract/fields` is the parser-field source of truth.
- For paid calls, reconcile actual spend from the per-call settlement receipt plus settlement or payment proof, not only from `cost_usd`. Grant-covered calls stay separate and should not settle.

Trust order
When two sources disagree, trust them in this order:
1. Live production response from the exact route and caller context you are using.
2. Live public discovery metadata: `openapi.json`, `/v1/pricing`, `/v1/contract/fields`, and MCP discovery.
3. This file.
4. `changelog-llm.html` for dated drift history.
5. The landing page or older notes.

Deployment-state labels
Use these labels whenever summarizing Delta Signal routes, specs, or research notes:
- `LIVE`: confirmed by current production response, `openapi.json`, `/v1/pricing`, `/v1/contract/fields`, or MCP discovery.
- `PLANNED`: documented design or route intent that is not confirmed by live discovery.
- `PROPOSED`: architecture or product research that has no live route contract yet.
- `LOCAL_ONLY`: implemented or tested in a source tree but not yet verified in Azure production.
- `DEPRECATED`: replaced by a newer live contract or name.
- `SECOND_LEVEL_LINK_NOT_FETCHED`: mentioned as a drilldown link but not inspected in the current evidence packet.

Agent rule: never promote `PLANNED`, `PROPOSED`, `LOCAL_ONLY`, or `SECOND_LEVEL_LINK_NOT_FETCHED` material to `LIVE` unless live discovery confirms it.

Primary links
- Product page: https://aitrailblazer.github.io/deltasignal-atlas-codex-plugin/
- Canonical brief: https://aitrailblazer.github.io/deltasignal-atlas-codex-plugin/llms-full.txt
- Compact brief: https://aitrailblazer.github.io/deltasignal-atlas-codex-plugin/llms.txt
- Human changelog: https://aitrailblazer.github.io/deltasignal-atlas-codex-plugin/changelog.html
- LLM changelog: https://aitrailblazer.github.io/deltasignal-atlas-codex-plugin/changelog-llm.html
- Changelog RSS: https://aitrailblazer.github.io/deltasignal-atlas-codex-plugin/rss.xml
- Changelog Atom: https://aitrailblazer.github.io/deltasignal-atlas-codex-plugin/atom.xml
- OpenAPI 3.1: https://api.aitrailblazer.net/openapi.json
- MCP endpoint: https://api.aitrailblazer.net/mcp
- Pricing contract: https://api.aitrailblazer.net/v1/pricing
- Field contract: https://api.aitrailblazer.net/v1/contract/fields
- Readiness: https://api.aitrailblazer.net/v1/readiness
- Grant challenge: https://api.aitrailblazer.net/v1/grant/challenge?wallet=<wallet>
- Arazzo workflow YAML: https://aitrailblazer.github.io/deltasignal-atlas-codex-plugin/arazzo/deltasignal-arazzo.yaml
- Arazzo workflow JSON: https://aitrailblazer.github.io/deltasignal-atlas-codex-plugin/arazzo/deltasignal-arazzo.json
- Public x402 handshake workflow: https://aitrailblazer.github.io/deltasignal-atlas-codex-plugin/arazzo/publicMcpX402Handshake.arazzo.yaml
- Hedera ProofPay preview: https://proofpay-hedera.kindbeach-299ce8c4.eastus.azurecontainerapps.io
- Hedera ProofPay discovery: https://proofpay-hedera.kindbeach-299ce8c4.eastus.azurecontainerapps.io/.well-known/proofpay
- Hedera ProofPay source and verifier: https://github.com/aitrailblazer/proofpay-hedera-x402
- Performed Hedera testnet payment: https://hashscan.io/testnet/transaction/0.0.7162784-1784665192-906989595

Read order for agents
Use this order unless the user asks for a narrower probe:
1. Read this file.
2. Read `changelog-llm.html` if you need dated drift history or public provenance.
3. Read `openapi.json` for the current public route map.
4. Read `/v1/pricing` before assuming route cost or grant debit behavior.
5. Read `/v1/contract/fields` before wiring a parser.
6. Probe one bounded route or MCP workflow before scaling usage.

Exact first probes
These are the safest first validation calls for a new integration:
- `GET /v1/pricing`
- `GET /v1/contract/fields`
- `GET /v1/readiness`
- `POST /mcp initialize`
- `POST /mcp tools/list`

Hedera ProofPay preview probes:
- `GET https://proofpay-hedera.kindbeach-299ce8c4.eastus.azurecontainerapps.io/health`
- `GET https://proofpay-hedera.kindbeach-299ce8c4.eastus.azurecontainerapps.io/.well-known/proofpay`
- `GET https://proofpay-hedera.kindbeach-299ce8c4.eastus.azurecontainerapps.io/catalog`
- `POST https://proofpay-hedera.kindbeach-299ce8c4.eastus.azurecontainerapps.io/quotes` with `{"ticker":"MSTR","period":"2025-12-31"}`. Quote creation is free and does not move funds.

Do not start by:
- assuming a route price from an old note
- assuming grant units from a single legacy field name
- assuming SPECTRA summary aliases are the parser contract
- assuming public MCP exposes every internal or newly built tool
- treating a plain HTTP 402 as proof of service failure

Most recent public verification anchor
The current GitHub Pages surface is aligned to the latest public verification notes summarized here:
- Live verification date: `2026-07-15` (public discovery reconfirmed `2026-07-16`).
- Live discovery: OpenAPI `1.5.2` with `68` paths; MCP `tools/list` with `81` tools, including `26` governed `atlas7_*` semantic tools; `/v1/pricing` with `30` routes; `/v1/contract/fields` with `47` fields.
- CompanyFacts/PIT replay execution: `edgarcompanyfactsmirror-sx9ym3w`, source date `2026-07-13`, completed `378/378` issuers and materialized `817,992` rows with `0` errors.
- Current calculation-universe boundary: `378` issuers = `215` crypto-canonical issuers + `163` expanded public-equity issuers. The earlier `312` expanded rows / `298` distinct tickers describe a historical cohort snapshot.
- Customer-route regression audit execution: `deltasigatlasaudit-29735310`, covering `215` issuers and `1,935` operations: `1,923` successful, `0` failed, `0` skipped, and `12` not applicable.
- Audit detail: historical operations `645` successful / `0` failed; composite operations `430` successful / `0` failed; identity gaps `0`.
- Audit artifact prefix: `20260715T123025Z`; summary SHA-256: `a341b77512418aeb5a5070dea4fa421c80b2dac40976100665098031e3a97840`.
- Scope boundary: the 378-issuer calculation replay and 215-issuer customer-route audit are separate governed surfaces. Do not combine their totals or treat an audit `not_applicable` result as a failure.
- Governed semantic tools expose model/field catalogs, validation, evidence envelopes, issuer/report inputs, history, pressure, and lineage. Raw SQL is never returned.

Previous Synthetic AI10 verification anchor
- Live verification date: `2026-07-02`.
- Latest deployed MCP/backend revision checked for this brief: `ca-web-intel-mcp--0000577`.
- Deployed image checked for this brief: `acrgniwebintel001.azurecr.io/ca-web-intel-mcp:skill-synthetic-ai10-answer-completeness-20260702-055337`.
- Live Synthetic AI10 audit route is available at `GET /v1/synthetic-etf/audit/{product}`.
- Live Synthetic AI10 MCP audit tool is available as `deltasignal_synthetic_etf_audit`.
- Live authenticated REST audit smoke for `Delta Signal Synthetic AI 10 Basket` returned `audit_status=complete`, `source_date=2026-06-30`, `observed_bucket_utc=2026-07-01T14:45:00Z`, `canonical_event_status=not_confirmed`, and `factor_history.export.row_count=656`.
- Live authenticated MCP audit smoke returned `audit_status=complete` and exposes the answer-completeness sections `constituent_contributions`, `presentation_parity`, `trident`, `trident.liquidation_gradient`, and `question_readiness`.
- Live MCP discovery exposes `deltasignal_synthetic_etf_audit`, and its output schema mentions `question_readiness` and `constituent_contributions`.
- Current Synthetic AI10 audit boundary:
  - `constituent_contributions.status=partial` because live contribution rows are coverage/weight evidence until per-constituent pressure-driver joins are persisted.
  - `presentation_parity.status=requires_artifact` until a named chart/report artifact is supplied for parity comparison.
  - `trident.status=unavailable` and `trident.liquidation_gradient.status=unavailable` until persisted TRIDENT/liquidation-gradient evidence exists.
  - `canonical_event_status=not_confirmed`; do not call the current read a confirmed ATLAS-7 release event unless live threshold and coverage evidence pass.
- Verification artifact path in the backend repo: `artifacts/deltasignal-synthetic-etf-audit/azure-deploy/20260702T060725Z/Synthetic_AI10_Azure_Deploy_Answer_Completeness_Report_2026_07_02.html`.
- Previous live verification anchor:
- Live verification date: `2026-06-28`.
- Latest deployed MCP/backend revision checked for this brief: `ca-web-intel-mcp--0000563`.
- Live public no-key MCP discovery exposes `deltasignal_help` as a free discovery-tier tool.
- Live public no-key `deltasignal_help` returns `schema_id=deltasignal.help.v1`, `payment_status=free_discovery`, `billing_status=not_charged`, `x402_required=false`, common example prompts, next-best discovery calls, and the non-advice boundary.
- `deltasignal_help` with `topic=perps` returns a structured `perp_market_boundary`: public reads are read-only over recorded/materialized rows, no live Coinbase fetch happens during help reads, raw ladders are not exposed, default normalization is a rolling 30-day available-bucket window, and `MARKET_ALPHA` is market-state telemetry rather than issuer alpha or a trade signal.
- Live MCP discovery exposes `deltasignal_synthetic_etf_pressure_state`.
- Live Synthetic AI10 contract: public calls should use `Delta Signal Synthetic AI 10 Basket` or `DeltaSignal Synthetic AI10 Basket` for canonical product `AI-PERP-INTX`.
- Synthetic AI10 lineage is preserved in `identity_lineage`: `canonical_name=Delta Signal Synthetic AI 10 Basket`, `methodology_changed=false`, `method_version=synthetic_ai10_etf_v1`.
- Synthetic AI10 responses preserve top-level `source_date`, `observed_bucket_utc`, `computed_at_utc`, `route_uri`, `evidence_hash`, `billing_status`, `payment_status`, `quoted_cost_usd`, `caveats`, `quality_flags`, `identity_lineage`, and `disclosures`.
- Live OpenAPI/pricing expose Coinbase perp/SPECTRA read routes: `/v1/market-atlas/perps/constituents/{product}`, `/v1/market-atlas/perps/factors/{product}`, `/v1/market-atlas/perps/calculation-history`, `/v1/market-atlas/perps/rankings`, `/v1/market-spectra-field-map/{product}`, and `/v1/synthetic-etf/pressure-state/{product}`.
- Coinbase perp/SPECTRA is additive market intelligence derived from persisted market-factor rows. It is not canonical SEC/XBRL issuer truth, not live exchange execution, and not personalized trading advice.
- Latest public changelog tripcode: `ATLAS-JUN-28-MCP-HELP-LIVE`.
- Previous public changelog tripcode: `ATLAS-JUN-28-SYNTHETIC-ETF-PUBLIC-WORDING`.
- Public copy now describes the basket layer as DeltaSignal Synthetic Basket evidence. Source-provider names, source files, weights, hashes, and lineage are internal evidence metadata unless a live route explicitly exposes them.
- DeltaSignal Synthetic Basket lanes include Synthetic AI10 Basket, Synthetic Innovators 100 Basket, Synthetic AI Power Infrastructure Basket, and Synthetic Semiconductor 25 Basket.
- The four evidence levels are Level 1 issuer truth, Level 2 public-market behavior, Level 3 basket pressure, and Level 4 derivative dislocation where a linked venue product exists. Missing levels remain explicit and must not be inferred.
- Current live route matrix from the 2026-06-28 verification pass:
  - `GET /v1/readiness`: `LIVE`; protected by x402/API-key flow; returns readiness, source date, caveats, quality flags, and billing envelope when authorized; unauthenticated HTTP 402 is expected and is not a service failure.
  - `GET /v1/pricing`: `LIVE`; authoritative public route-pricing source; use it instead of stale prose or copied examples.
  - `GET /v1/contract/fields`: `LIVE`; authoritative parser and field-contract source for agents and clients.
  - `GET /openapi.json`: `LIVE`; authoritative REST path and schema discovery surface.
  - `POST /mcp initialize` and `POST /mcp tools/list`: `LIVE`; authoritative MCP discovery surfaces for tool availability.
  - `POST /mcp tools/call name=deltasignal_help`: `LIVE`; free discovery-tier Natural Language help surface; no x402 payment required; use `topic=overview`, `tools`, `pricing`, `fields`, `grants`, `x402`, `morning_brief`, `company_report`, `perps`, `spectra`, or `examples`.
  - `GET /v1/synthetic-etf/pressure-state/{product}`: `LIVE`; route-declared price observed at `$0.12`; returns Synthetic Basket pressure-state evidence with lineage/disclosures; not a regulated ETF offer, personalized advice, or exchange-native truth claim.
  - `GET /v1/market-atlas/perps/constituents/{product}`: `LIVE`; route-declared price observed at `$0.08`; returns product constituent/readiness evidence; does not claim Coinbase owns or verifies the synthetic basket.
  - `GET /v1/market-atlas/perps/factors/{product}`: `LIVE`; route-declared price observed at `$0.10`; returns persisted market-factor evidence; not SEC/XBRL issuer truth.
  - `GET /v1/market-atlas/perps/calculation-history`: `LIVE`; route-declared price observed at `$0.20`; returns persisted calculation-history evidence; do not infer full-depth historical order-book reconstruction before durable recording began.
  - `GET /v1/market-atlas/perps/rankings`: `LIVE`; route-declared price observed at `$0.12`; returns market-factor ranking evidence; not an execution directive.
  - `GET /v1/market-spectra-field-map/{product}`: `LIVE`; route-declared price observed at `$0.08`; returns SPECTRA field-map/derived-label evidence over persisted rows; visual labels are presentation-only unless backed by raw factors.
  - AS/GLFT execution-control research: `PROPOSED`; treat it as a risk-envelope design concept unless a future live route, pricing entry, OpenAPI schema, and MCP tool confirm deployment.
- Previous public changelog tripcode: `ATLAS-JUN-20-GRANT-NATURAL-EXPIRY-LIVE`.
- Earlier referenced Natural Language grant rollout: Azure Container App revision `ca-web-intel-mcp--0000536`.
- Grant challenge/session/status responses can expose `grant_expires_at` and `grant_expires_in_seconds` for the actual grant window. The existing `expires_at` and `expires_in_seconds` fields on challenge/session responses remain the short signing/session TTL.
- Active grant runway metadata can list `grant_expires_at` in `grant_runway_authoritative_fields` alongside USD runway fields.
- Grant-covered Natural Language routes can include `GET /v1/morning-brief/natural`, `GET /v1/top-stressed/natural`, and `GET /v1/covenant-stress/natural` when the active grant contract includes them.
- Exact route matching resolves `/v1/covenant-stress/natural` before templated ticker routes such as `/v1/covenant-stress/{ticker}`.
- OpenAPI was observed at 48 public paths.
- `/v1/pricing` and `/v1/contract/fields` were live public discovery surfaces.
- Company Report was observed at `cost_usd: 0.6` with a public standard display price of `$0.60` and a live route-declared range of `$0.45-$0.75`.
- Wallet grants used a signed challenge -> `personal_sign` -> session -> token flow.
- `/v1/grants/status` was part of the confirmed live public surface for contexts where an active grant identity or grant token makes explicit grant-runway reporting available; a plain request without identity may correctly return HTTP 400.
- Verified budget-grant reporting exposed USD-style runway semantics rather than request-count semantics.

How to think about drift
- If production now exposes more than this file says, trust production.
- If source branches or private notes mention fields or routes that production does not expose, do not assume they are live.
- If a spec says "planned" but `openapi.json`, `/v1/pricing`, and MCP discovery now expose the route, treat the live route as authoritative and preserve any caveats returned by the response.
- If a source note says "not deployed in this pass," re-check live discovery before repeating that claim; deployment state can change after the note was written.
- If `/v1/grants/status` is exposed for the caller context, trust its explicit runway fields over older grant wording.
- If pricing prose and `/v1/pricing` disagree, trust `/v1/pricing` and the route-specific challenge.
- If the contract adds fields, treat the public surface as additive unless a newer contract explicitly marks a breaking change.

What Delta Signal is
- Delta Signal ATLAS-7 is an issuer-intelligence and evidence-rendering layer grounded in SEC / XBRL filings and Delta Signal processing.
- It produces structured market and issuer workflows such as Morning Brief, Company Report, Pressure Board, Alpha Sweep, Quick Ticker Check, and Daily Change evidence views.
- It also exposes DeltaSignal Synthetic Basket evidence layers that turn issuer truth, public-market behavior, basket pressure, and derivative dislocation into bounded public-company pressure views.
- It returns evidence, metadata, caveats, and billing context designed for machine use.

DeltaSignal Synthetic Basket public naming
- Use `DeltaSignal Synthetic AI10 Basket` for the concentrated AI-leader basket.
- Use `DeltaSignal Synthetic Innovators 100 Basket` for the broad innovation and technology basket.
- Use `DeltaSignal Synthetic AI Power Infrastructure Basket` for power, grid, data-center, compute-infrastructure, and miner-to-HPC transition evidence.
- Use `DeltaSignal Synthetic Semiconductor 25 Basket` for semiconductor supply-chain pressure.
- These are synthetic evidence baskets inside Delta Signal. They are not personalized recommendations and should not be described as customer-managed exchange-traded funds.
- Public summaries should say `DeltaSignal Synthetic Basket` instead of third-party basket-provider names. Preserve returned lineage metadata without treating it as a methodology change or marketing copy.

What Delta Signal is not
- Not a broker.
- Not a wallet or settlement service.
- Not a promise that every route is free.
- Not a substitute for settlement proof when x402 actually moved funds.
- Not an authorization to invent evidence, infer freshness, or convert uncertainty into conviction.

Fast-start behavior
- Start with readiness or another bounded workflow.
- Inspect metadata before trusting the narrative summary.
- Preserve source dates, computed timestamps, caveats, quality flags, stale indicators, and evidence hashes where available.
- Never ask for internal secrets or internal API keys in a public integration path.

Public grant flow
For enrolled EVM wallets, the documented wallet grant flow is:
1. `GET /v1/grant/challenge?wallet=<wallet>`
2. `personal_sign` the returned message exactly as provided
3. `POST /v1/grant/session` with wallet, timestamp, and signature
4. Attach the returned token in `X-DeltaSignal-Grant-Token` before settlement

Grant rules
- Plain unsigned wallet headers are intentionally rejected as grant proof.
- The signed grant-session token is the authorization artifact.
- The wallet grant flow is separate from ordinary x402 settlement.
- If grant issuance fails, expires, or is unavailable, the client should fall back to ordinary x402 instead of blocking the request path.
- Public wallet integrations should implement the signed session flow above. Internal identity headers or API keys are first-party operations mechanisms and should not be documented as customer integration requirements.

Grant-covered Natural Language routes
- Natural Language routes are not automatically free; they are grant-covered only when the caller has a valid signed grant session and the active grant contract includes the exact route.
- Current grant-eligible Natural Language route examples include `GET /v1/morning-brief/natural`, `GET /v1/top-stressed/natural`, and `GET /v1/covenant-stress/natural`.
- If a Natural Language route is not grant-eligible for the caller context, expect ordinary x402/payment-required behavior rather than assuming service failure.
- Preserve the same evidence and non-advice rules for Natural Language output as for structured JSON routes.

Grant sizing and runway rules
- Do not guess the unit of a grant field unless the live contract states it explicitly.
- If production exposes `grant_limit_type=budget_usd`, `grant_limit_unit=usd`, `grant_budget_usd`, or `grant_remaining_usd`, treat the grant as a USD-denominated budget grant.
- If production exposes `grant_expires_at` or `grant_expires_in_seconds`, treat those as the grant-window expiry fields. Do not confuse them with the short challenge/session `expires_at` or `expires_in_seconds` fields.
- If production exposes `grant_runway_authoritative_fields`, use that list to decide which grant fields are authoritative for runway display.
- If production exposes a debit policy such as `grant_debit_policy=route_declared_price`, use that policy rather than legacy "credit" wording.
- If production exposes `grant_cache_treatment=fresh_and_cached_charge_same_route_quote`, assume fresh and cached covered reads debit the same route quote unless the live contract changes.
- If public runway fields are absent, treat grant coverage as boolean in public integrations and rely on x402 fallback for exhaustion handling.

Pricing and billing rules
- `/v1/pricing` is the authoritative public route-pricing surface.
- Delta Signal pricing applies only to Delta Signal-derived evidence workflows and analytical outputs. It does not provide access to, redistribute, or resell any upstream market-data feed.
- Company Report is not the older `$0.30` assumption. The corrected public display contract is `$0.60` standard with a live route-declared range of `$0.45-$0.75`.
- Grant-covered, API-key-bypassed, or discovery responses may show `cost_usd: 0`.
- Public grant or x402 billing envelopes may also expose fields such as `billing_mode`, `payment_status`, `billing_status`, `quoted_cost_usd`, `actual_cost_usd`, `credits_charged`, `settlement_receipt`, and request-scoped billing metadata.
- Treat those fields as Delta Signal response-envelope billing data.
- Standard Base x402 remains first in the 402 challenge for broad client compatibility.
- Circle Gateway is an optional additive payment path. Circle-aware buyers must explicitly select `GatewayWalletBatched` by capability or provider pin and sign against the challenge-provided Gateway verifying contract.
- Circle Gateway settlement requires deposited or available Gateway balance. A Base ERC-20 USDC balance alone may return `insufficient_balance`; that closed failure is not a settled or charged call.
- Do not claim automatic fallback after an invalid or failed proof. A buyer that wants another requirement must select and sign it explicitly.
- A runnable Node.js buyer is published with setup instructions at https://aitrailblazer.github.io/deltasignal-atlas-codex-plugin/examples/circle-aware-buyer/README.md and source at https://aitrailblazer.github.io/deltasignal-atlas-codex-plugin/examples/circle-aware-buyer/buyer.mjs. It defaults to dry-run, selects Circle by capability, validates the live requirement, signs the challenge-provided Gateway domain only with `--pay`, and prints a sanitized settlement/receipt summary.
- Signed grant-session calls are separate from settlement and should remain zero-settlement when the grant covers the route.
- For standard `x402_direct`, wallet movement plus the response receipt is the reconciliation path.
- For `circle_gateway_batched`, the response receipt must remain the authoritative per-call attribution surface, including route, quote, charged/attributed amount, settlement mode, payer reference, reconciliation key, batch/transaction reference when available, timestamp, status, and quality flags.
- Treat `cost_usd` as the Delta Signal billing-envelope signal, not the sole authority for externally settled x402 spend.

Hedera ProofPay usage
- Deployment state: `LIVE` public testnet preview. The Azure backend exposes health, discovery, catalog, quote creation, paid evidence, and receipt-finalization routes. The performed-payment proof is independently visible on HashScan.
- The preview is separate from the live Base/Circle/MPP DeltaSignal route families. Do not claim that `https://api.aitrailblazer.net/v1/*` or `POST /mcp` accepts HBAR unless live discovery later adds that network.
- Safe inspection: read `/.well-known/proofpay`, read `/catalog`, create a bounded quote with `POST /quotes`, then inspect its payment terms, expiry, request hash, and paid resource URL. These steps do not move funds.
- Paid execution requires explicit user approval:
  1. Call the quote's paid resource URL.
  2. Receive HTTP 402 with `network=hedera:testnet`, HBAR asset `0.0.0`, exact amount, seller account, and timeout.
  3. Let a Hedera x402-compatible buyer sign and settle.
  4. Retry with payment proof.
  5. Mirror-verify buyer debit, seller credit, amount, result, network, and transaction ID.
  6. Call `/receipts/finalize` to release the decryption key and Ed25519 receipt.
  7. Run the repository's offline verifier against the trusted public key.
- Never paste a Hedera private key into a prompt, browser, source file, transcript, screenshot, or repository. The paying agent owns the buyer key; the resource server needs only the public seller account and its separate receipt-signing key.
- The public demonstration transaction is a completed prior run, not a payment that occurs when documentation or video is viewed: value buyer `0.0.9676074`; seller `0.0.9676073`; transaction fee payer `0.0.7162784`; amount `1,000,001` tinybar; transaction `0.0.7162784-1784665192-906989595`.
- HashScan proves ledger settlement. The ProofPay signed receipt separately binds payment to request, encrypted delivery, evidence hash, output hash, source date, and software commit.
- Current boundary: the preview fulfills a deterministic MSTR filing-evidence fixture for the bounty demonstration. It does not yet proxy arbitrary live DeltaSignal MCP tools, live market data, or investment advice.

Primary public workflows
- Morning Brief: readiness, daily changes, risk distribution, top stressed issuers, alpha opportunities, caveats, and non-advice framing.
- Company Report: single-issuer diligence across SEC / XBRL fundamentals, covenant stress, peer ranking, alpha signals, source metadata, quality flags, and live history or SPECTRA context where available.
- Pressure Board: stress-oriented market view.
- Alpha Sweep: opportunity-oriented screen.
- Quick Ticker Check: bounded issuer triage.
- Synthetic AI10 Pressure State: compact current pressure-state read for Delta Signal Synthetic AI 10 Basket.
- Synthetic AI10 Audit: live audit-grade driver and verification payload for questions about factors, deltas, z-scores, threshold flags, event confirmation, four-level coverage, constituent contribution readiness, presentation parity, TRIDENT availability, liquidation-gradient availability, and publication safety.
- Natural Language routes: readable Markdown or rendered output that should preserve evidence boundaries rather than inventing new evidence.

Public capability and lane map
- Core issuer universe: 215 issuer rows in the original crypto-exposed public-company coverage map, with 201 nonblank unique tickers and 13 CIK-only or unresolved ticker rows.
- Current calculation universe: 378 issuer rows, composed of 215 crypto-canonical issuers plus 163 expanded public-equity issuers.
- Historical expanded cohort snapshot: a 312-row expanded issuer cohort with 298 distinct tickers. Preserve this only as historical context.
- Synthetic membership surface: 326 synthetic basket membership rows, 180 unique public-equity tickers, and 2 canonical linked perp instruments.
- DeltaSignal Synthetic AI10: 10 constituents. Use this for the concentrated AI leader pressure-state workflow.
- DeltaSignal Synthetic Tech100: 100 constituents. Use this for broad innovation and technology pressure-state context.
- DeltaSignal Synthetic AI + Power Infrastructure Basket: 81 constituents. Use this for AI power, grid, data-center, nuclear, cooling, compute-infrastructure, and miner/HPC overlap context. Level 4 remains not applicable until a validated linked derivative product exists.
- DeltaSignal Synthetic Semiconductor 25 Basket: 25 constituents. Use this for semiconductor and hardware supply-chain pressure context. Missing Level 4 remains explicit unless a validated linked derivative product is added.
- DeltaSignal Synthetic Crypto Industry Innovators Basket: primary crypto-equity lane for companies tied to crypto revenue, exchanges, mining, treasury exposure, digital asset financial infrastructure, and crypto capital markets.
- DeltaSignal Synthetic Bitcoin Mining Infrastructure Basket: miner-specific lane for mining operators, mining infrastructure, hash-rate exposure, power contracts, hosting, site concentration, and AI/HPC optionality.
- DeltaSignal Synthetic Digital Asset Infrastructure Basket: exchanges, brokers, custody, payment rails, blockchain software, clearing, crypto financial infrastructure, and capital-market access.
- DeltaSignal Synthetic Crypto Treasury Exposure Basket: balance-sheet lane for crypto holdings, treasury policy, financing, dilution, debt, preferreds, convertibles, BTC/ETH exposure, and treasury sensitivity where filings support classification.
- DeltaSignal Synthetic AI + Power Infrastructure Overlap: crossover lane for crypto/mining issuers with AI/HPC, data centers, power, grid, hosting, cooling, and compute relevance.
- DeltaSignal Synthetic Public Market Rails Basket: financial-market infrastructure relevant to digital assets, including trading, brokerage, custody, index, clearing, settlement, payments, and exchange infrastructure.
- DeltaSignal Synthetic Speculative / Emerging Crypto Issuers Basket: smaller, newer, thinner, less-proven, or evidence-limited crypto-exposed issuers separated from mature infrastructure names.
- Lane output is cohort and pressure-intelligence metadata. It is not a regulated ETF claim, broker signal, target price, trade instruction, or investment advice.

Governed semantic MCP
- Live public MCP discovery exposes 26 tools with the `atlas7_*` prefix.
- Start with `atlas7_model_catalog` to discover governed semantic models and supported intents.
- Use `atlas7_field_catalog` to inspect allowlisted fields, filters, sorts, freshness, and evidence requirements for one model.
- Use `atlas7_compile_query` or `atlas7_explain_signal` to validate a request and inspect the public plan or SQL fingerprint without exposing raw SQL.
- Use `atlas7_semantic_query` only with allowlisted model, intent, field, filter, and sort inputs. The response is an ATLAS evidence envelope, not a database console.
- Preserve source dates, accessions, CIK/ticker identity, fact names, evidence hashes, freshness, quality flags, and missing-evidence states.
- Use `atlas7_evidence_lineage` or `atlas7_lineage_audit` when a user asks how a fact or calculation is supported.
- Treat subscription gating as part of the contract. Tool discovery does not imply that a caller is entitled to execute every semantic route.

Natural-language MCP help and routing
- `deltasignal_help` is the human orientation surface. Use it before paid or evidence workflows when the user asks for help, examples, groups, fields, pricing, grants, x402, Morning Brief, Company Report, Synthetic AI10, perps, SPECTRA, tools, or integration guidance.
- `help groups` should list available workflow groups and the exact focused help command for each group.
- `help synthetic ai10` should be AI10-specific. It should explain the Delta Signal Synthetic AI 10 Basket pressure-state workflow, the audit workflow, linked-market boundary, fields to preserve, caveats, and copy/paste prompts.
- Users should be able to ask natural questions such as:
  - What is the Synthetic AI10 pressure state right now?
  - What factors are driving the Synthetic AI10 state?
  - Is Synthetic AI10 in a confirmed ATLAS-7 release event?
  - Show the Synthetic AI10 audit payload with z-scores, threshold flags, and four-level coverage.
  - Compare the current Synthetic AI10 bucket to the previous bucket.
  - What changed from Releasing to Normal in Synthetic AI10?
  - Can we safely publish this Synthetic AI10 read?
- A backend Fetcher or MCP-capable client should route plain current-state questions to `deltasignal_synthetic_etf_pressure_state`.
- A backend Fetcher or MCP-capable client should route why/driver/confirmation/publishability/audit questions to `deltasignal_synthetic_etf_audit`.
- Compact pressure-state output is enough for "what is the current state?"
- Audit output is required for "why," "what factors," "what changed," "is the event confirmed," "do we have z-scores," "do we have threshold flags," "do we have four-level coverage," and "can this be published safely?"
- Audit output is also required for "which constituents drove it," "does the chart match the data," "is TRIDENT available," "is liquidation-gradient evidence available," and "what can a customer-facing article safely claim?"

Synthetic AI10 evidence boundary
- Delta Signal Synthetic AI 10 Basket is a synthetic benchmark pressure-state workflow, not a regulated ETF claim.
- Synthetic AI10 output is not issuer truth by itself, not exchange-native microstructure truth, not a broker signal, not a target price, not a trade instruction, and not investment advice.
- The compact pressure-state tool may say that a linked-market state is Releasing, Normal, or another state. Do not promote that label into a confirmed ATLAS-7 event unless the audit tool returns passing threshold flags and a confirmed event classification.
- The audit tool can expose current bucket, previous bucket, factor-history pagination/export metadata, audit-window z-scores, threshold flags, event classification, four-level coverage, provenance, caveats, and quality flags.
- The audit tool can also expose `constituent_contributions`, `presentation_parity`, `trident`, `trident.liquidation_gradient`, and `question_readiness` so agents can answer customer questions without overclaiming missing evidence.
- If `event_classification.canonical_confirmed` is false or the payload carries a quality flag such as `canonical_event_not_confirmed`, say that no canonical ATLAS-7 event is confirmed.
- If `presentation_parity.status=requires_artifact`, ask for the specific chart/report artifact before claiming parity between rendered visuals and raw evidence.
- If `trident.status=unavailable` or `trident.liquidation_gradient.status=unavailable`, say that TRIDENT/liquidation-gradient evidence is not available rather than fabricating an execution or liquidation read.
- If Level 1, Level 2, Level 3, or Level 4 coverage is partial, label the result as a partial linked-market or synthetic read instead of a full four-level ATLAS-7 verdict.
- Preserve source dates, observed bucket timestamps, method version, quality flags, caveats, route URI, payload mode, and evidence boundaries in any summary.

Representative public route pricing
Treat these as examples, not hard-coded truth:
- Morning Brief: typically `0.18` when exposed that way.
- Company Report: `0.6` according to the current public verification anchor.
- Pressure Board: typically `0.14`.
- Alpha Sweep: typically `0.14`.
- Quick Ticker Check: typically `0.18`.
- Natural Language top-stressed and Morning Brief Markdown routes: typically `0.95` when the live route metadata confirms them.

Parser contract
- Treat `/v1/contract/fields` as the source of truth for parser-stable field names and paths.
- Treat the public contract as additive-only unless a new contract version says otherwise.
- Hard-code only fields you have verified in the live contract.
- Do not assume future or internal grant-ledger fields are public just because code or private notes mention them.
- Company Report parsers should prefer `mcp_summary` plus the documented structured nested fields, not ad hoc or SPECTRA-specific summary aliases.

Load-bearing field paths
- Readiness: `ok`, `age_minutes`, `freshness_window_hours`.
- Generic provenance: `ticker`, `route_uri`, `source_date`.
- Company Report: `mcp_summary`, `confidence`, `data.ticker`, `data.workflow`, `data.status`, and the documented nested per-section fields.
- Daily changes: `changed_companies`, `changes`, `data`, `rows`, and row-level `ticker` where arrays are returned.
- Stress compatibility: `stress_50pct` or `stressed_leverage_50pct`.

ATLAS-7 and SPECTRA model
- ATLAS-7 is the issuer evidence and generation layer.
- SPECTRA is the field-map and interpretation layer over ATLAS-history-shaped rows.
- SPECTRA is not an independent evidence source.
- Missing evidence must remain missing.

Strict evidence rules
- Preserve `source_date`, `computed_at`, filing dates where returned, stale flags, caveats, quality flags, evidence hashes where available, `payload_mode`, `route_uri`, and billing metadata.
- Compact aggregate responses may contain null freshness fields inside nested `combined_provenance.evidence_contract` objects when there is no single canonical upstream artifact for the aggregate.
- When those compact freshness fields are null, use the top-level `data.evidence_hash` as the authoritative integrity anchor when it is populated.
- Do not convert uncertainty into confidence.
- Do not let Natural Language rendering override returned caveats or provenance metadata.

Terminal broker contract
- When `/v1/contract/fields` exposes `terminal_broker`, treat it as the source of truth for brokered envelope fields.
- Covered brokered datasets currently include covenant-stress, alpha-signals, and company-fundamentals in the documented contract notes.
- Terminal clients should key results by `endpoint_id` and treat summaries as opaque unless the live route contract says otherwise.
- Load-bearing terminal envelope fields include `endpoint_id`, `status`, `cache_status`, `quote_status`, `summary`, `evidence_summary`, `estimated_usd`, `cost_usd`, and `confirmation_token`.

Public MCP behavior
Endpoint:
POST https://api.aitrailblazer.net/mcp

Expected public discovery behavior
- JSON-RPC `initialize` and `tools/list` are the correct first MCP probes.
- JSON-RPC `tools/call` with `name=deltasignal_help` is the safest Natural Language help probe and is free discovery-tier.
- Public MCP discovery should work before paid execution.
- Public `tools/call` may return x402 payment-required behavior.
- Public `deltasignal_help` should not return x402 payment-required behavior; if it does, treat that as a help-surface regression and re-check live deployment.
- Free-tier or grant-covered execution may use an active grant context or the wallet grant-session flow.
- Public users should not request, store, or transmit internal API keys. Use x402 challenge/retry for paid execution, or signed wallet grant sessions when the wallet is enrolled in the backend grant database.

Public Natural Language help examples
Use this no-key MCP call when the user asks for help, examples, or "what can I ask?":

curl -sS https://api.aitrailblazer.net/mcp \
  -H 'content-type: application/json' \
  --data '{"jsonrpc":"2.0","id":"help","method":"tools/call","params":{"name":"deltasignal_help","arguments":{"topic":"overview","detail":"short","include_examples":true}}}'

Use this no-key MCP call when the user asks about Synthetic Basket, Coinbase perp, or SPECTRA pressure-state workflows:

curl -sS https://api.aitrailblazer.net/mcp \
  -H 'content-type: application/json' \
  --data '{"jsonrpc":"2.0","id":"help-perps","method":"tools/call","params":{"name":"deltasignal_help","arguments":{"topic":"perps","detail":"short","include_examples":true}}}'

Expected help response fields
- `schema_id=deltasignal.help.v1`
- `status=ok`
- `payment_status=free_discovery`
- `billing_status=not_charged`
- `x402_required=false`
- `common_commands`
- `featured_workflows`
- `example_prompts`
- `next_best_calls`
- `evidence_boundary`
- `non_advice_boundary=true`
- `perp_market_boundary` when `topic=perps`

Example prompts surfaced by help
- "Generate today's Delta Signal Morning Brief."
- "Create a Delta Signal Company Report for RIOT."
- "Quick check MSTR with source dates, caveats, and quality flags."
- "Show the latest Delta Signal Pressure Board."
- "Run an Alpha Sweep across crypto-exposed issuers."
- "Show daily changes and changed companies from the latest Delta Signal run."
- "Generate a SPECTRA field map for COIN."
- "Show the Synthetic AI10 pressure state and preserve identity lineage and disclosures."
- "List available Delta Signal MCP tools and schemas."
- "Show current Delta Signal pricing and explain grant-session requirements."

Internal smoke shape
Use this only for first-party internal smoke with an authorized key in the operator environment:

curl -sS https://api.aitrailblazer.net/mcp \
  -H 'content-type: application/json' \
  -H "x-api-key: $MCP_API_KEY" \
  --data '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"agent-smoke","version":"1.0.0"}}}'

curl -sS https://api.aitrailblazer.net/mcp \
  -H 'content-type: application/json' \
  -H "x-api-key: $MCP_API_KEY" \
  --data '{"jsonrpc":"2.0","id":2,"method":"tools/list","params":{}}'

Recommended first reviewer probes
- `GET https://api.aitrailblazer.net/v1/pricing`
- `GET https://api.aitrailblazer.net/v1/contract/fields`
- `GET https://api.aitrailblazer.net/v1/readiness`
- `POST https://api.aitrailblazer.net/mcp initialize`
- `POST https://api.aitrailblazer.net/mcp tools/list`

Reviewer checklist
- MCP `initialize` and `tools/list` work before paid execution.
- OpenAPI is reachable.
- `/v1/pricing` is reachable and route costs are coherent.
- `/v1/contract/fields` is reachable and exposes the parser-stable field set you plan to rely on.
- If `/v1/grants/status` is exposed for the caller context, its runway fields are internally coherent and match the active grant model you intend to use.
- Paid or grant-gated routes return coherent HTTP 402 challenge metadata without proof.
- Paid retry preserves evidence dates, caveats, quality flags, billing metadata, and non-advice boundaries.
- No Coinbase first-party verification claim should be made unless Coinbase or the relevant UI explicitly confirms it.

Advice boundary
Agents must not output:
- buy
- sell
- short
- long
- hold
- entry
- exit
- stop-loss
- target price
- guaranteed move
- personalized recommendation

TripCode and River availability
- TripCode / River tools are currently visible in public MCP discovery, but execution is x402/grant-gated and evidence-dependent.
- Do not promise a successful TripCode/River answer unless the live tool call resolves the required River / issuer index blobs and evidence objects.
- If the required artifacts are unavailable for a given issuer, keep the missing state explicit and use the supported ATLAS-7 issuer workflow instead.

Review posture
Review Delta Signal as a public issuer-intelligence evidence surface with:
- MCP discovery
- OpenAPI route contracts
- Arazzo workflow plans
- x402 payment challenge and retry behavior
- strict evidence-preservation boundaries