History
Dates and titles below are the git history, CHANGELOG.md, and the GitHub pull requests. When a commit date and a GitHub merge time fall on different days, both are stated. The repository is https://github.com/kaanuluer/KATA.
- Repository starts
a581f1cInitial commit.c57c16cKATA framework initial content: README, docs, schemas, examples, research.6ffc9f7KATA assets: logo.d9037b3Remove corrupted logo upload (retry via web UI).302ba83KATA assets: hero banner and logo.Five commits that day share the message “KATA framework part 1: README, license, gitignore”:
3d5275a,29899e1,1a514d4,e85217e,2191ce3. - Price integrity, and a mapping onto other mandates
0129d8aRecord price integrity and the AgentCommerceBench gap (#1). GitHub #1 Add price integrity and an AgentCommerceBench mapping was opened 2026-10-09T02:02:58Z and merged 2026-10-09T02:05:23Z.2ab98f5Map KATA objects to Verifiable Intent and AP2 mandates. (#2). GitHub #2 Map KATA to Verifiable Intent, AP2, TAP, and AGNTCY was opened 2026-10-09T02:42:08Z and merged 2026-10-09T02:52:11Z. - Related-work notes, then the intent agreement
37d54b0Record a reading of Sardine's agentic-commerce fraud report in the KATA docs. (#3). GitHub #3 Update KATA docs from Sardine's 2026 agentic commerce fraud report was opened 2026-10-12T05:06:29Z and merged 2026-10-12T05:07:08Z. CHANGELOG.md for that day records the reading of Sardine's public report Rethinking Fraud Prevention for Agentic Commerce (2026). The changelog says no schema or example changed, and that nothing in the update is a measured result.d9d5712Separate the KATA core from optional profiles and related work. (#4). GitHub #4 Keep the KATA core lean: optional profiles and Darwinium as related work was opened 2026-10-12T12:43:56Z and merged 2026-10-12T12:44:19Z. The changelog says an implementation needs the four questions, the intent and delegation schemas, and the decision outcomes, and that use-case examples are profiles. It cites Darwinium's press release of 8 October 2026 as that related-work entry.8ca5197Add a signed intent agreement and a reference action check. The changelog points at docs/intent-agreement.md, schemas/intent-mandate.json, schemas/agreement.json, and the reference library's Ed25519 mandate, action check, and revoke-or-expire path.GitHub #5 Add a signed intent agreement and a reference action check was opened 2026-10-12T22:46:54Z. GitHub lists it as a draft and records no merge time.
- Decisions, the deployment service, and this page
32711abApply Kaan's intent-agreement decisions to the spec and the reference check. The changelog records the agreement inside the delegation, the spend ledger on the agreement, several live intents inside one parent set, and the principal's signature as the activation.39c6328Apply the confirmation, ledger, revocation, FX, institution-key, and ES256 decisions. The changelog records canonical confirmation text, a hash-chained ledger with a 60-second staleness step-up, auto-selection of one matching intent, pull plus push plus a transparency log, a pluggable daily FX ceiling, institution keys at .well-known plus an allowlist, and ES256 beside Ed25519.5df8892Add a Vercel service for the revocation list, transparency log, and daily FX.2e36a7dPoint the Vercel FastAPI entrypoint at the repository-root app.py.28c0765Send a user agent on Frankfurter FX requests and use the v1 host.87d97e2Add an English KATA page with a sample intent check and live status.b237da9Use the teal seal and KATA wordmark on the web page.GitHub #6 Relicense KATA under PolyForm Noncommercial 1.0.0 was opened 2026-10-13T03:45:55Z and merged 2026-10-13T04:16:43Z. The LICENSE file in this checkout is the PolyForm Noncommercial License 1.0.0. Versions published before that change were released under Apache-2.0.
CHANGELOG.md for 2026-10-13 also records
/historyand/docs(design, authorization, intent, threat model, schemas, and the API reference), with FastAPI's generated OpenAPI page at/docs/openapi.This checkout adds the Global Agent Bureau on that service: organizations and hashed API keys, the agent registry, stored intents and the verify API, incident reports, purpose-coded inquiries, the rule-based trust score, signed alerts, the individual portal, and disputes. The requirements are in docs/gab-requirements.md. The organization dashboard is /dashboard and the individual portal is /portal.