Proof that a work existed by a date

# Proposal: Proof that a work existed by a date

## Why
In a dispute over who had a work first, a file's own dates are easy to fake. A record fixes that this exact work existed by its logged time, signed by you, and the daily root carries outside timestamps that do not depend on the registry.

## What Changes
- Hash each finished piece and publish a provenance record.
- Use `lineage` to show drafts and what fed what.
- Export a bundle with proofs and timestamps when you need to show it.


## Capabilities
### New Capabilities
- `dated-works`: A signed, dated record per piece, with outside timestamps on the daily root.

## Impact
- External service: AI Source of Truth at https://aisourceoftruth.com. Reads are anonymous. Writes need a publisher key pair you generate, a client id and secret from registration, and a token from `/oauth/token`.
- Routes used: `POST /v1/records`, `GET /r/{digest}/certificate`, `POST /v1/export`.
- No PromptReports product is required.
- Source of this plan: https://aisourceoftruth.com/use-cases/proof-of-authorship (CC0). Regenerate it with `curl -H 'Accept: application/json' 'https://aisourceoftruth.com/use-cases/proof-of-authorship/openspec?lang=http'`.

# Design: Proof that a work existed by a date

## Context
Writers, artists, researchers and studios. In a dispute over who had a work first, a file's own dates are easy to fake. A record fixes that this exact work existed by its logged time, signed by you, and the daily root carries outside timestamps that do not depend on the registry.

## Where it sits in your agent
Add it to the step where a piece is marked final, such as an export or a release script.

Over MCP, point the agent at `https://aisourceoftruth.com/mcp` (Streamable HTTP, JSON-RPC 2.0; read tools need no token). The tools this change uses: `publish_record`, `get_certificate`, `export_bundle`.

## Decisions
- Treat the registry as a source of facts about records, never about the world. Show what it says, with the digest, and do not turn a verdict into a quality score.
- If the registry cannot be reached, treat the answer as unknown (the same as `check`), never as `rely`, and retry later.
- Keep content private: send hashes. Never put personal data in a record; it is public and permanent.
- Keep the private key and client secret in your secret store. Rotate keys at `POST /v1/keys`; a revoked key cannot sign.

## Setup and signing helper

```sh
# Publisher setup, once. Make an Ed25519 key pair yourself; the registry never sees the private key.
# 1. Register: POST https://aisourceoftruth.com/v1/publishers with {"id","name","public_jwk"}, signed by that key
#    (X-AISOT-Signature over the exact body bytes, base64url) and an Idempotency-Key.
#    The answer carries client_id, client_secret and your key_id.
# 2. Token (60 minutes; mint another the same way):
curl -s -X POST 'https://aisourceoftruth.com/oauth/token' -H 'Content-Type: application/json' \
  --data '{"grant_type":"client_credentials","client_id":"'"$AISOT_CLIENT_ID"'","client_secret":"'"$AISOT_CLIENT_SECRET"'"}'
# ./sign-ed25519 reads bytes on stdin and prints the base64url Ed25519 signature.
```

## Calls
### POST /v1/records
append a signed record; the answer carries its digest and inclusion proof.

```sh
BODY='{ ...record }'
SIG=$(printf %s "$BODY" | ./sign-ed25519)   # base64url signature over these exact bytes
curl -s -X POST 'https://aisourceoftruth.com/v1/records' \
  -H "Authorization: Bearer $AISOT_TOKEN" \
  -H "X-AISOT-Key-Id: $AISOT_KEY_ID" \
  -H "X-AISOT-Signature: $SIG" \
  -H "Idempotency-Key: $(uuidgen)" \
  -H 'Content-Type: application/vnd.aisot.record+json' \
  --data-binary "$BODY"
```

### GET /r/{digest}/certificate
what the record proves, with signer, log position, proof and timestamps.

```sh
curl -s -H 'Accept: application/json' 'https://aisourceoftruth.com/r/{digest}/certificate'
```

### POST /v1/export
an offline bundle with proofs and timestamps for up to 100 records.

```sh
curl -s -X POST 'https://aisourceoftruth.com/v1/export' \
  -H 'Content-Type: application/json' \
  --data '{"digests":["{digest}"]}'
```

## What this does not prove
- A record proves this exact work existed by its recorded time and who signed it. It does not prove who wrote it, so it is evidence for a claim, not a verdict.

# Tasks: Proof that a work existed by a date

## 1. Configure
- [ ] 1.1 Set `AISOT_ORIGIN=https://aisourceoftruth.com` in the agent's environment.
- [ ] 1.2 Generate an Ed25519 key pair, register the publisher (`POST /v1/publishers`), and store `AISOT_CLIENT_ID`, `AISOT_CLIENT_SECRET`, `AISOT_KEY_ID` and the private key as secrets.
- [ ] 1.3 Mint a token at `/oauth/token` and confirm `GET /v1/me` answers with your publisher id.
- [ ] 1.4 Optional: add the MCP server `https://aisourceoftruth.com/mcp` to the agent's MCP config.

## 2. Build
- [ ] 2.1 Publish when finished: Hash the final file and publish a provenance record. Keep the original file safe: the record holds only its hash. (`POST /v1/records`)
- [ ] 2.2 Read the certificate: The certificate lists the appended time, the inclusion proof and the daily root's RFC 3161 timestamps and Bitcoin anchor once they exist. (`GET /r/{digest}/certificate`)
- [ ] 2.3 Export for a dispute: Export a bundle and give it with the file. Anyone can check it offline. (`POST /v1/export`)

## 3. Verify against the live registry
- [ ] 3.1 Publish when finished: The record's asset digest matches your file.
- [ ] 3.2 Read the certificate: The certificate shows the proof, or when it will be ready.
- [ ] 3.3 Export for a dispute: `node verify.mjs bundle.json` passes.

## 4. Done when
- [ ] 4.1 Each finished work has a dated, signed record and an offline bundle.

# dated-works Specification

## ADDED Requirements

### Requirement: Finished works are recorded
The release step SHALL publish a provenance record for each finished work and SHALL keep the exported bundle with the original file.

#### Scenario: Release
- **WHEN** a work is released
- **THEN** its record exists and a bundle for it is stored