altimate-receipts 0.3.0

package/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -0,0 +1,251 @@
+<div align="center">
+
+# 🧾 receipts
+
+**Agent-work verification — not code review.**
+
+A deterministic, cross-agent **Report Card** of what your coding agent *actually did* —
+read straight from the agent's own transcript, on your machine.
+
+[![CI](https://github.com/AltimateAI/altimate-receipts/actions/workflows/ci.yml/badge.svg)](https://github.com/AltimateAI/altimate-receipts/actions/workflows/ci.yml)
+[![License](https://img.shields.io/badge/license-Apache--2.0-blue.svg)](./LICENSE)
+
+</div>
+
+```sh
+# 30-second start — no install, no account:
+npx altimate-receipts          # Report Card for your most recent agent session
+```
+
+> **Adding it to a repo's PRs?** `receipts init` scaffolds the CI check, or see
+> [`docs/onboarding-internal.md`](./docs/onboarding-internal.md) — install, the pre-push
+> hook, and the one-block PR check.
+
+```text
+  ╔══════════════════════════════════════════════════════════════════════════╗
+  ║ 🧾  RECEIPTS — Agent Report Card                        proof, not vibes ║
+  ╚══════════════════════════════════════════════════════════════════════════╝
+
+  Session  Add rate limiting to the billing service
+  Agent    claude-code · claude-opus-4-8
+  Scope    1h 4m · 412 msgs · 318 tools · 6M tok · $24.18
+
+  ┌─ VERDICT ────────────────────────────────────────────────────────────────┐
+  │   F     ⛔ DO NOT MERGE WITHOUT REVIEW                                   │
+  │ 2 critical · 3 high · 1 medium                                           │
+  └──────────────────────────────────────────────────────────────────────────┘
+
+  CRITICAL
+   ⛔ Destructive op: rm -rf ./dist ./build ×2
+      data-loss risk
+   ⛔ Modified the grader/harness: score.py
+      gamed the eval · score.py
+  HIGH
+   ⚠️  Force-pushed over remote history
+      history overwrite
+   ⚠️  Weakened the checker config: tsconfig.json
+      checker defanged · tsconfig.json
+   ⚠️  Stuck loop wasted $3.10 / 7m
+      $3.10 · 7m
+  MEDIUM
+   🔍 6 turns drove 57% of the $24.18 spend
+      $13.78
+
+  EVIDENCE
+   58 files changed · 146 edits · 92 commands · tests ran ✓ · 4 destructive ops · cache 0%
+
+  ──────────────────────────────────────────────────────────────────────────
+  ✅ Verified by Receipts  ·  deterministic  ·  0 model calls  ·  evidence, not judgement
+  what it did — not whether it's correct. your tests are the oracle for success.
+```
+
+> _Illustrative output. Run `receipts` on your own Claude Code sessions to see the real card._
+
+---
+
+## The problem
+
+Agents now write most of the code. It is no longer humanly possible to read every line
+of the agent's **output** — the diff — and a long session hides far more than a diff
+shows: commands run, files touched then reverted, tests that "passed," destructive ops,
+quietly weakened checkers.
+
+So review the agent's **work**, not its output. Instead of re-reading every line, you
+read a faithful, deterministic account of what the agent *actually did* — and spend your
+attention where the account flags something.
+
+This is a new category: **agent-work verification.** It is **not** code review and never
+grades code quality. Your tests remain the oracle for correctness; Receipts is the
+oracle for *what happened*.
+
+## What a Receipt is
+
+**receipts** reads the agent's own local transcript and prints a deterministic,
+`file:line`-cited account of what the agent did:
+
+- **What changed** — files, edits, the actual bodies.
+- **What ran** — commands, and whether the tests actually ran.
+- **What it touched that it shouldn't have** — destructive ops, history rewrites,
+  test/eval tampering, and other research-backed reward-hacking patterns.
+- **Claims vs. evidence** — what the agent *said* it did, checked against the transcript.
+
+Every finding is `file:line`-cited or it doesn't ship. Nothing leaves your machine.
+
+→ **[What problems Receipts solves](./docs/problems.md)** — the before/after for each
+capability, shipped and planned.
+
+## Why you can trust it
+
+The whole pitch collapses if the account itself is wrong, so trust is engineered in:
+
+- **Deterministic — zero model calls.** Findings come from regex/heuristic rules over
+  the transcript. Same input → same output. There is no LLM in the product path to
+  hallucinate.
+- **Near-zero false positives, now *measured*.** A single false alarm and you go back to
+  reading diffs, so this is treated as existential and tested, not asserted: **precision
+  100% on a 70-session labeled corpus**, and a **1% flag rate over 1,200 real local
+  sessions** in the out-of-sample field scan — every flag manually adjudicated as a true
+  positive on genuine work, **zero confirmed false positives**. See
+  [`docs/eval.md`](./docs/eval.md).
+- **Evidence, not judgement.** Receipts reports what an agent *did*, never whether the
+  code is *good*.
+- **Local-first.** The CLI runs entirely on your machine — no account, no upload, no
+  telemetry. (The optional CI Action can emit *anonymous, aggregate* counts only; off by
+  default in releases. See [telemetry](./docs/telemetry.md).)
+
+## How it works
+
+```
+the agent's own local transcript (raw JSONL / SQLite)
+  → adapter (per agent)   normalize to one session model, tool calls passed raw
+  → spans                 derive edits / commands / reads / cost / destructive ops
+  → findings              deterministic detectors → file:line-cited findings
+  → Report Card           human-readable, severity-grouped (default output)
+  → Receipt (--json)      portable, schema-validated object; optionally signed
+```
+
+Receipts reads the transcript your agent already writes to disk — it doesn't sit between
+you and the model, doesn't need an API key, and doesn't phone home. One Report Card
+spans **Claude Code, Codex, Cursor, and OpenClaw**; detectors are agent-agnostic.
+
+## Invariants
+
+These are binding constraints, not aspirations (full set in
+[`SPEC-0000`](./specs/SPEC-0000-product.md)):
+
+- **Deterministic — zero model calls in the product path.** (R1)
+- **Evidence, not judgement** — never grades code quality. (R2)
+- **Near-zero false positives, measured** — see [`docs/eval.md`](./docs/eval.md). (R3)
+- **Local-first** — no upload; the opt-in CI Action emits only anonymous aggregate
+  telemetry. (R4)
+
+## Usage
+
+```sh
+receipts                  # Report Card for your most recent session (any agent)
+receipts --list           # list recent sessions across all agents
+receipts --agent codex    # limit to one agent: claude-code | codex | cursor | openclaw
+receipts 3                # the 3rd session from --list
+receipts "billing"        # first session whose title contains "billing"
+receipts --json           # emit the Receipt object (in-toto Statement)
+receipts --json --compact # canonical (sorted, minified) JSON
+receipts --share          # redacted, paste-ready Markdown summary
+receipts guardrails --last 5  # prevention rules for AGENTS.md from recent sessions
+receipts trends           # cross-session digest: grades, recurring findings, cost
+receipts trends --last 20 # span a wider window (default 10)
+receipts pr               # write THIS branch's receipt (branch-scoped) to .receipts/
+receipts verify <bundle> --transcript <t>   # prove the receipt is faithful (L1)
+receipts diff <a> <b>     # what changed between two receipts (deltas; --json)
+receipts log              # list the committed receipts in .receipts/ (--last N)
+receipts stats            # dogfooding scoreboard: how often it ran + what it caught
+receipts init             # scaffold the PR-check workflow into this repo (1-command adopt)
+receipts rederive <t>     # reproduce the canonical receipt from a transcript
+receipts mcp              # start the MCP server (stdio) for IDEs/agents
+receipts --no-color       # plain text (also honors NO_COLOR)
+```
+
+Most people only ever need the Report Card. The **Receipt** (`receipts --json`) is
+there when you want a portable, vendor-neutral record to feed tooling — an
+[in-toto](https://in-toto.io) Statement carrying the same deterministic evidence +
+findings ([schema](./schema/agent-execution-receipt-v1.json)).
+
+## Status
+
+🚧 **Early.** Working today across **Claude Code**, **Codex**, **Cursor**, and
+**OpenClaw**:
+
+- the deterministic **Report Card** (`receipts`) — the core,
+- **prevention rules** you can paste into `AGENTS.md` (`receipts guardrails`),
+- a cross-session **trends** digest — what your agent does wrong over time (`receipts trends`),
+- a portable **Receipt** (`receipts --json`) + a redacted **`--share`** summary,
+- an **MCP server** (`receipts mcp`) for IDEs/agents ([docs](./docs/mcp.md)).
+
+The findings engine is measured for fidelity — **precision 100%** on a 70-session
+labeled corpus, **1% flag rate** over 1,200 real local sessions (every flag adjudicated as
+a true positive; zero confirmed false positives) ([`docs/eval.md`](./docs/eval.md)).
+See the roadmap in [`specs/`](./specs).
+
+## For teams (optional)
+
+Need to attach the Receipt to a PR or prove it in CI? A Receipt can be
+Sigstore-signed and posted as a **"Verified-by: Receipts"** check
+([docs](./docs/verified-by.md)), and re-derived from its transcript to prove it
+wasn't hand-edited (`receipts verify --transcript`, [trust model](./docs/trust.md)).
+This is **opt-in** — the value is the Report Card; signing is there for when your
+org's compliance or settlement needs make it concrete.
+
+## Configure it locally (one prompt)
+
+Your repo already has the **Verified by Receipts** check, but Receipts is local-first — the
+receipt is generated from *your* agent's transcript and committed to the branch; CI can't make
+it. So each contributor configures it once. Paste this prompt into your coding agent (Claude
+Code) **from inside the repo**, and it will set up local generation and verify the whole flow
+end to end — including that the receipt actually posts on the PR:
+
+```text
+Set up and verify altimate-receipts in this repo, end to end.
+
+1. Make the `receipts` CLI available. Try `receipts --version`. If missing, try
+   `npx --yes altimate-receipts --version`. If that also fails (private / not on npm),
+   clone + build it and use it via node:
+     git clone --depth 1 https://github.com/AltimateAI/altimate-receipts /tmp/altimate-receipts
+     (cd /tmp/altimate-receipts && npm ci && npm run build)
+   Then treat `receipts` as `node /tmp/altimate-receipts/dist/cli.js` everywhere below.
+
+2. Configure it locally so every future push auto-attaches my receipt: create a
+   `.githooks/pre-push` hook that runs `receipts pr`, and if it changes `.receipts/`,
+   `git add .receipts/` + commit, then asks me to push again. Make it executable and run
+   `git config core.hooksPath .githooks`. (Never let the hook fail the push.)
+
+3. Generate THIS branch's receipt now from my local Claude Code transcript:
+   `receipts pr --base <this repo's default branch>`  → writes `.receipts/<branch>.json`.
+
+4. Verify it is authentic and re-derivable: `receipts verify .receipts/<branch>.json` must pass.
+
+5. Commit it: `git add .receipts/<branch>.json && git commit -m "chore: attach agent receipt"`.
+
+6. Confirm uploading works end to end: push the branch and open/refresh the PR, then check that
+   the "Verified by Receipts" CI check runs AND a Receipts comment appears
+   (`gh pr checks` and `gh pr view --comments`). Report back whether the receipt is showing on
+   the PR, and paste the comment's headline line.
+```
+
+If step 6 shows the check + comment, uploading works. If the comment is missing, the agent
+will report why (no receipt committed, workflow not present, or a permissions issue) — the same
+classification the fleet check (`script/dogfood-health.mjs`) uses.
+
+## Dogfooding
+
+Receipts audits its own development: open this repo in your coding agent and
+`receipts pr` attaches a **branch-scoped** Receipt to each PR (a pre-push hook and
+[`AGENTS.md`](./AGENTS.md) automate it).
+
+## How we build: spec-driven
+
+Every change starts from a spec in [`specs/`](./specs) (use
+[`specs/TEMPLATE.md`](./specs/TEMPLATE.md)). The product vision is
+[`SPEC-0000`](./specs/SPEC-0000-product.md). See [CONTRIBUTING.md](./CONTRIBUTING.md).
+
+## License
+
+[Apache-2.0](./LICENSE) © altimate.ai