Delta Signal ATLAS-7 Full Agent Brief
Version: llms-full-v5
Last updated: 2026-06-20
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 June 20 grant-expiry and Natural Language grant-coverage rollout.

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.
- The public surface is REST + MCP + OpenAPI + Arazzo + x402-compatible payment behavior + signed wallet grant sessions.
- 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`.
- Signed grant-session tokens authorize grant-covered requests. Plain unsigned wallet headers are intentionally not enough.
- `/v1/pricing` is the public pricing source of truth. `/v1/contract/fields` is the parser-field source of truth.
- For plain x402 calls, reconcile actual spend from settlement or payment proof, not only from `cost_usd`.

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.

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

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`

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:
- Latest public changelog tripcode: `ATLAS-JUN-20-GRANT-NATURAL-EXPIRY-LIVE`.
- Latest referenced live 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 `/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 returns evidence, metadata, caveats, and billing context designed for machine use.

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.
- Some first-party or partner flows may also use issued identity headers, but public wallet integrations should implement the signed session flow above.

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.
- 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`, and request-scoped billing metadata.
- Treat those fields as Delta Signal response-envelope billing data.
- For plain x402 calls, reconcile real spend from settlement or payment proof when the wallet moved.
- Treat `cost_usd` as the Delta Signal billing-envelope signal, not the sole authority for externally settled x402 spend.

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.
- Natural Language routes: readable Markdown or rendered output that should preserve evidence boundaries rather than inventing new evidence.

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.
- Public MCP discovery should work before paid execution.
- Public `tools/call` may return x402 payment-required behavior.
- Free-tier or grant-covered execution may use an active grant context or the wallet grant-session flow.
- Public users should not request internal API keys.

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