# BitterGit Public Context

## Product Sentence

BitterGit is Git-compatible source custody for agent runs, with signed run
provenance, run-level review, and BitterGrid verification receipts.

## User And Job

BitterGit is built for operators and teams whose agents commit across multiple
repositories. They need to know which run made what, what verified, what failed,
and what can be accepted or reverted without treating a bot account as the unit
of review.

## Object Loop

```text
WakePacket -> AgentRun -> Commit -> RunTrailers -> RunBundle -> GridReceipt -> Accept/RevertDecision -> SourceHistory
```

The source-custody record should connect the wake packet that asked for work,
the agent run that did the work, the commits it produced, the signed trailers on
those commits, the run bundle that groups them, the BitterGrid receipt that
verified them, and the human or agent decision that accepted, reverted, or
superseded the change.

## Place In Bitter

Bitter CLI stamps and signs run provenance around ordinary Git operations.
BitterGit preserves repositories, source history, commit provenance, and
source-linked workflow metadata. BitterGrid builds, deploys, verifies, and
records runtime receipts. BitterLog can carry source-custody evidence into
future wake packets.

## Boundary

BitterGit is not a GitHub clone, project tracker, social network, CI system,
deploy executor, account/billing layer, or secret-value store.

The public `bittergit.com` root is a marketing surface, not the Git remote or
product API endpoint. The product service repository owns Git remotes,
repository storage, account integration, and source-custody verification gates.

## Current Status

Bitter's own fleet is tenant zero. External accounts are request-only.

The public marketing site is live and Grid-verified at the release reported by
`https://bittergit.com/up`.

Public source repository: `https://github.com/sheetgenius/bittergit-marketing`.
It owns website source, Markdown mirrors, crawler files, smoke tests, and
deployment-boundary docs. It does not own the product Git remote/API service.

Access requests start in BitterDesk at `https://bitterdesk.com/`. There is no
self-serve signup queue or static form endpoint on the marketing site.

## Deployment Facts

- service key: `bittergit.com`
- Grid service id: `30`
- active verified release: reported by `https://bittergit.com/up`
- health path: `/up`
- Radicchio site id: `102`
- publish directory: `.output/public`
- deployment path: GitHub source event -> BitterGrid build/deploy ->
  Radicchio/static site

Known caveats:

- Grid customer app ownership is not applicable to this platform-style service.
- Grid edge binding is untracked even though public verification passes.
- Radicchio serves `/index.md` as `application/octet-stream` and does not emit
  canonical HTTP `Link` headers for Markdown alternates.

## Public Routes

- HTML: https://bittergit.com/
- Markdown: https://bittergit.com/index.md
- Robots: https://bittergit.com/robots.txt
- Sitemap: https://bittergit.com/sitemap.xml
- AI index: https://bittergit.com/llms.txt
- Full AI context: https://bittergit.com/llms-full.txt
- Health: https://bittergit.com/up
- Access requests and support: https://bitterdesk.com/
- Public source repository: https://github.com/sheetgenius/bittergit-marketing
- Changelog: https://github.com/sheetgenius/bittergit-marketing/blob/main/CHANGELOG.md
- Contributing: https://github.com/sheetgenius/bittergit-marketing/blob/main/CONTRIBUTING.md
- Security and public boundary: https://github.com/sheetgenius/bittergit-marketing/blob/main/SECURITY.md

## Repository Commands

```bash
npm install
npm run generate
npm run qa:smoke
npm run test:headers
Scripts/workcell-verify
```