# BitterLog Public Context

## Product Sentence

BitterLog is an append-only evidence workbench for agent-run proof: raw traces,
receipts, prompt/output artifacts, annotations, stable digests, and
account-scoped retrieval.

## User And Job

The user is an AI-native operator building software with agents. The job is to
preserve what happened in a run, recover the exact source record behind a
summary or failure, and make evidence inspectable for later review.

## Object Loop

```text
Agent Run -> Raw Event or Bucket Object -> Digest/Timestamp/Receipt -> Annotation/Query -> Reviewable Proof
```

## Bitter Role

Bitter is the agent-operable software environment. BitterLog owns the evidence
and memory satellite: raw traces, receipts, prompt/output artifacts,
annotations, stable digests, and account-scoped retrieval. Factory can use this
evidence, BitterGrid can attach deploy receipts to it, and BitterPass can
support credentials for agents, but those systems do not become the evidence
ledger.

## Boundary And Not-X

BitterLog is not Factory's control plane, BitterGrid's deployment executor,
BitterPass's credential authority, a generic observability dashboard, or a
marketing-site login system. The public marketing repository does not contain
customer evidence payloads, account delegation internals, ClickHouse bootstrap,
credential material, or private support/debug material.

## Live Proof

The public marketing root is `https://bitterlog.com/`. The API index is
`https://api.bitterlog.com/api/v1`. The public API status is
`https://api.bitterlog.com/api/v1/status` and currently reports ledger counts,
release identity, `secret_material_returned: false`, and
`analytics.enabled: false`. The release identity path for this marketing site
is `https://bitterlog.com/up/`.

## Claim Ledger

- Live-proven: public marketing root, health/release identity, API index, API
  status, ledger counts, no returned secret material, Bitter account links, and
  analytics currently disabled in status.
- Source-proven: static Nuxt marketing site, Radicchio manifest, public smoke
  tests, Markdown alternate, AI-readable discovery files, and marketing-only
  repository boundary.
- Private: customer traces, prompt snapshots, stdout/stderr, rendered outputs,
  account delegation internals, ClickHouse bootstrap, credential material,
  customer-specific onboarding, and private support/debug material.
- Future or conditional: customer-facing raw SQL, ClickHouse search,
  similarity, shared buyer access, form forwarding, and instant self-serve
  BitterLog onboarding unless current live proof intentionally supports them.

## CTA Truth

Create or request access through Bitter account surfaces. Sign in through
Bitter. API index and status are public. Onboarding remains request-reviewed
during launch, and this site does not expose a working marketing-form endpoint.

## Current Public Copy

BitterLog stores raw traces, receipts, prompt/output artifacts, and annotations
with stable digests so operators can move from a run summary back to the exact
source record. Account-scoped access runs through Bitter. ClickHouse-backed
search is a projected read model, not the ledger itself, and public API status
advertises when analytics is available.

## Public Routes

- Home: https://bitterlog.com/
- Public source: https://github.com/sheetgenius/bitterlog-marketing
- Home Markdown: https://bitterlog.com/index.md
- Health and release identity: https://bitterlog.com/up/
- API index: https://api.bitterlog.com/api/v1
- API status: https://api.bitterlog.com/api/v1/status
- Sitemap: https://bitterlog.com/sitemap.xml
- Robots: https://bitterlog.com/robots.txt
- AI index: https://bitterlog.com/llms.txt