Skip to content

zero-intelligence.md

Latest commit

 

History

History
215 lines (176 loc) · 8.43 KB

zero-intelligence.md

File metadata and controls

215 lines (176 loc) · 8.43 KB

ZERO Intelligence

ZERO Intelligence is the data product built from verified autonomous behavior. During operator growth, realtime Intelligence access is free so ZERO can increase operator density, collect better verified behavior, and make public profiles and leaderboards more valuable. Future commercial packaging should monetize scale, retention, redistribution, support, and SLAs rather than basic operator access.

It is not a hosted deployment product. Operators should be able to run ZERO locally, through Docker, or on Railway without paying ZERO and without sending exchange credentials to ZERO. Railway is the preferred hosted deployment path because it gives operators their own project, secrets, services, volumes, databases, logs, and billing relationship.

Public Surfaces

  • Open-source ZERO Runtime
  • Operator CLI
  • Local paper mode
  • Self-custodial live mode, once shipped
  • Railway and Docker deployment templates
  • Public profiles
  • Public leaderboards
  • Public verification badges
  • Public benchmark pages
  • Delayed or rate-limited public intelligence snapshots

Growth-Mode Free Surfaces

  • Realtime Intelligence API access for verified operators
  • Public profiles and leaderboards
  • Public verification badges
  • Delayed and rate-limited public intelligence snapshots
  • Hosted-compatible Railway/Docker contract testing

Future Commercial Surfaces

  • Historical decision and risk datasets
  • Advanced filters, cohorts, and benchmark analytics
  • Commercial intelligence connectors and enrichment feeds
  • Webhooks and streaming feeds
  • Higher API limits and bulk exports
  • Commercial redistribution rights
  • Enterprise support, reliability commitments, and SLAs

Public Runtime Contract

The open runtime now emits the same safe packets that the commercial data product should ingest later:

  • GET /intelligence/snapshot returns zero.intelligence.snapshot.v1, a delayed public aggregate derived from a verified ZERO Network profile. Its source binds both the deployment claim hash and deployment heartbeat hash.
  • GET /intelligence/catalog returns zero.intelligence.catalog.v1, the commercial API, billing, scope, dataset, and rate-limit contract.
  • GET /intelligence/commercial returns zero.intelligence.commercial.v1, the pinned hosted API boundary for plans, scopes, datasets, usage events, webhooks, exports, reliability tiers, and privacy.
  • GET /v1/intelligence/snapshots, /history, /cohorts, and /benchmarks expose the hosted-compatible read API shape. Delayed snapshots are public; realtime, history, cohort, and benchmark scopes require a bearer token when ZERO_INTELLIGENCE_API_TOKEN is configured.
  • POST /v1/intelligence/webhooks and /exports expose the hosted-compatible write API shape for signed webhook fixtures and aggregate export jobs.
  • GET /intelligence/model-gateway returns zero.model_gateway.status.v1, the provider-agnostic, fail-closed model routing status for advisory intelligence, including optional OpenAI, Anthropic, Ollama, and OpenRouter adapter readiness, bounded retry policy, usage counters, and public-safe cost-estimate source.
  • POST /intelligence/export writes an opt-in local JSONL packet when ZERO_INTELLIGENCE_EXPORT_PATH is configured and the request includes {"consent":true}.

The public runtime does not upload intelligence packets to ZERO. Hosted ingestion is a future commercial API surface, not a requirement for local operation.

Packaging

  • Growth mode: runtime, CLI, public profiles, public leaderboards, delayed snapshots, realtime Intelligence API access, hosted-compatible Railway contracts, and onboarding credits are free for verified operators.
  • Future operator plans: higher API quota, alerts, webhooks, longer history, saved views, and profile verification features.
  • Future teams/funds: team API keys, cohort analytics, bulk exports, private benchmarks, and redistribution rights.
  • Future enterprise: SLOs, support, compliance needs, custom retention, and commercial redistribution.

Hosted API Shape

The hosted API should use bearer API keys, explicit scopes, usage events, and standard rate-limit headers even while access is free in growth mode. The checked contract fixture lives at contracts/intelligence/commercial.json.

The public server now includes a reference implementation of the hosted API boundary under /v1/intelligence/*. It is not a production billing service; it is a contract harness for clients, docs, Railway smoke tests, and contributor work.

  • x-zero-ratelimit-limit
  • x-zero-ratelimit-remaining
  • x-zero-ratelimit-reset
  • x-zero-ratelimit-policy

Primary scopes:

  • intelligence:read:delayed
  • intelligence:read:realtime
  • intelligence:read:history
  • intelligence:cohorts
  • intelligence:exports
  • intelligence:webhooks
  • intelligence:redistribute

Primary datasets:

  • verified_behavior_snapshots
  • cohort_benchmarks
  • risk_operations_history
  • leaderboard_history

Primary usage events:

  • snapshot.delayed.read
  • snapshot.realtime.read
  • history.query
  • cohort.query
  • benchmark.query
  • webhook.delivery
  • export.created
  • redistribution.reported

Reference auth and signing variables:

ZERO_INTELLIGENCE_API_TOKEN=...
ZERO_INTELLIGENCE_API_PLAN=team_fund
ZERO_INTELLIGENCE_API_ACCOUNT_ID=acct_...
ZERO_INTELLIGENCE_WEBHOOK_SIGNING_KEY=...
ZERO_INTELLIGENCE_STORE_PATH=/data/zero/intelligence.jsonl

The reference implementation enforces protected scopes when a token is configured, emits real x-zero-ratelimit-* headers, and returns webhook signature fixtures with:

x-zero-signature-timestamp
x-zero-signature
x-zero-signature-algorithm

The signature payload is timestamp + "." + canonical_json_body signed with HMAC-SHA256. The signing key is never returned.

Durable Reference Store

When ZERO_INTELLIGENCE_STORE_PATH is configured, the hosted-compatible reference API appends public-safe JSONL records for delayed/realtime snapshots, usage events, webhook subscription fixtures, and export jobs. History queries then read stored snapshot records before falling back to the current runtime snapshot.

The store is intentionally aggregate-only:

  • API tokens and webhook signing keys are never written.
  • Account IDs and webhook target URLs are persisted as SHA-256 hashes.
  • Raw journals, trace IDs, idempotency keys, symbols, exchange order IDs, wallet identifiers, and strategy labels remain excluded by the same privacy checks that guard public Network and Intelligence packets.

This is not the final commercial warehouse or billing system. It is the durable, stdlib, self-hostable persistence boundary that production hosted Intelligence can replace with Postgres, ClickHouse, or another append-only warehouse without changing the public API contract.

Data Rules

  • Local runtime use is private by default.
  • Telemetry is opt-in.
  • Public profile publishing is opt-in.
  • Public profile packets must use the zero.network.profile.v1 redaction contract.
  • Verified live badges require proof without custody.
  • Aggregated intelligence must not expose raw private operator secrets, exchange credentials, private notes, or non-consented strategy details.
  • Model gateway status must not expose prompts, raw model outputs, provider secret values, or hosted request metadata.
  • Model gateway health probes are config-only by default; explicit network probes must return only public provider, attempt, token-count, and status metadata.
  • Model gateway audit bundles must prove fail-closed controls and evidence requirements without including prompts, raw outputs, headers, request IDs, or secret values.
  • Model gateway costs must come from operator-configured prices or provider usage metadata; the public runtime must not bake stale vendor pricing into source code.
  • Growth-mode intelligence should remain free for operator density.
  • Future paid intelligence should monetize scale, history, reliability, redistribution, and support, not basic runtime use.
  • Core runtime and venue adapters should remain public. Commercial connectors should exist for intelligence enrichment, partner integrations, redistribution, and enterprise data delivery.

Flywheel

Open runtime -> verified behavior -> public network proof -> Intelligence

The runtime creates behavior. The network verifies behavior. ZERO Intelligence turns verified behavior into free operator utility first, then future commercial scale, retention, redistribution, and SLA products.