Boundaries

TraceDB v0.1.1 Hosted Alpha draws hard lines between public runtime behavior, hosted-control-plane behavior, and future work.

Public Runtime

The downloadable runtime owns database semantics, storage formats, query behavior, local durability, SDK protocol behavior, and self-hostable storage interfaces.

The public runtime may claim implemented local/embedded engine behavior, HTTP /v1 routes, TraceQL, native and bounded GraphQL, OpenAPI, SDK protocol behavior, local WAL/checkpoint/manifest semantics, and conformance harness coverage when backed by receipts.

Hosted Control Plane

The hosted control plane owns invites, auth, organizations, quotas, scoped API keys, operator workflows, provider configuration, and managed routing. Hosted implementation details are not part of the public runtime source contract.

Non-Claims

TraceDB v0.1.1 does not claim:

  • SQL or PostgreSQL compatibility;
  • distributed consensus;
  • distributed replication;
  • multi-process active writers on one data directory;
  • cross-replica idempotency;
  • crash-atomic exactly-once behavior across all failure points;
  • managed disaster recovery, RPO/RTO, or public SLA;
  • GraphQL subscriptions, arbitrary resolver runtime, or full GraphQL parity;
  • public benchmark superiority without external controls and preserved run bundles;
  • compliance certifications or regulated-industry attestations; or
  • full hosted S3 runtime rehydrate proof as a v0.1.1 blocker.

Full runtime S3 rehydrate from WAL/checkpoint state is tracked for v0.1.2. The v0.1.1 docs may describe the contract and baseline, but should not present that proof as complete.