sello 0.1.0

package/LICENSE

@@ -0,0 +1,200 @@
+                                 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 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 accept 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 2026 Juan Figuera
+
+   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,195 @@
+![Sello banner](docs/assets/sello-banner.png)
+
+# Sello
+
+Sello is a protocol for independently-verifiable records of AI agent actions.
+
+**Pronunciation:** commonly `SEH-yoh` or `SEH-yo`, from the Spanish word *sello*, meaning a seal or stamp.
+
+When an agent calls a service, the service creates a receipt for what it observed. The receipt is encrypted to the agent owner, signed by the service, and published to a transparency log. Later, the owner can retrieve and verify that receipt without trusting the agent's own logs.
+
+```text
+agent calls service
+  -> service creates encrypted signed receipt
+  -> transparency log stores receipt
+  -> owner fetches, verifies, decrypts
+```
+
+## Why Sello?
+
+Most agent logs are written by the same system whose behavior they describe. If the agent, runtime, or operator is compromised, those logs can be incomplete or false.
+
+Sello moves receipt-writing to the services the agent calls. The service was present for the action, but it is outside the agent's own logging path. The architectural inversion is simple: the signer is not the agent or its operator, but the receiver that observed the action.
+
+## What Sello Gives You
+
+Sello helps an owner verify that:
+
+- A specific service signed a specific receipt.
+- The receipt was encrypted for the owner.
+- The receipt was included in a trusted transparency log.
+- The receipt body was not modified after signing.
+
+Sello does not prove that the agent called every service it should have called, that every service is honest, or that unauthenticated log indexes returned complete results. Those limits are intentional and documented in the spec.
+
+## Repository Status
+
+This repository currently contains:
+
+- [SPEC.md](SPEC.md): the Sello protocol draft.
+- A TypeScript reference implementation in [`src/`](src/).
+- Implementation-backed v0.1 test vectors in [`fixtures/vectors/sello-v0.1.json`](fixtures/vectors/sello-v0.1.json).
+- Security review notes in [`docs/security-review.md`](docs/security-review.md).
+- SDK security audit notes in [`docs/sdk-security-audit.md`](docs/sdk-security-audit.md).
+
+The implementation includes a local end-to-end demo, compact JWS token verification, COSE_Sign1 receipt envelopes, HPKE encryption, a mock transparency log, a Rekor discovery adapter, owner verification, an MCP middleware prototype, security review notes, and a local benchmark. Live Rekor proof verification and production identity operations are still future work.
+
+📄 **Paper:** [Notarized Agents: Receiver-Attested Confidential Receipts for AI Agent Actions](https://arxiv.org/abs/2606.04193) (arXiv:2606.04193, submitted June 2026). Local PDF: [docs/paper/notarized-agents.pdf](docs/paper/notarized-agents.pdf).
+
+## Start Here
+
+| Goal | Read |
+|------|------|
+| Add Sello in a few lines | [SDK Quickstart](docs/sdk-quickstart.md) |
+| Try a wrapped tool locally | `node --run dev`, then `node --run example:tool` |
+| Try an MCP-style tool call | `node --run dev`, then `node --run example:mcp` |
+| Understand the protocol | [SPEC.md](SPEC.md) Quick Start |
+| Run the local demo | `node --run demo` |
+| Run the test suite | `node --run test` |
+| Measure local size/performance | `node --run bench -- --json` |
+| Emit receipts from a service | [SPEC.md](SPEC.md) §§3.1, 4.1, 5, 6.2 |
+| Verify receipts as an owner | [SPEC.md](SPEC.md) §§4.2, 5, 6.2, 7.1 |
+| Build the reference implementation | Start with "The First 10 Minutes" below |
+
+## Add Sello in a Few Lines
+
+```ts
+import { sello } from "sello";
+
+const receipts = sello.service();
+
+export const createEvent = receipts.tool("calendar.create_event", async (request) => {
+  return calendar.events.create(request);
+});
+```
+
+Then inspect verified actions:
+
+```bash
+npx sello actions --token <agent-token>
+```
+
+Sello works with your own log server. `sello.build` is optional convenience, not a protocol requirement.
+
+To try the repo's local loop:
+
+```bash
+# Terminal 1
+node --run dev
+
+# Terminal 2
+node --run example:tool
+node --run actions
+```
+
+The example wraps a fake calendar tool, emits a service-signed encrypted receipt, and lets the owner verify it from the local action log.
+
+For an MCP-shaped `tools/call` boundary, run `node --run example:mcp` instead of `node --run example:tool`.
+
+## The First 10 Minutes
+
+If you are implementing Sello, start with one local loop:
+
+1. Generate a fixed owner HPKE key pair.
+2. Generate a fixed service Ed25519 signing key.
+3. Create one mock compact JWS token containing `owner_hpke_pk` and `sello_logs`.
+4. Have the service create one receipt for one fake action.
+5. Store the receipt in a mock log under `sello_token_ref`.
+6. Have the owner fetch, verify, and decrypt the receipt.
+
+Do not start with Rekor, MCP middleware, distributed identity, or CLI polish. Those become much easier once one local receipt works end to end.
+
+You know the first loop works when the owner can print one verified receipt:
+
+```json
+{
+  "service": "example.com/tool/v1",
+  "action-type": "tools/call",
+  "result-status": "success",
+  "verified": true
+}
+```
+
+## Service Integration
+
+A Sello-aware service does this for each agent action:
+
+1. Verify the agent's authorization token.
+2. Read `owner_hpke_pk` and `sello_logs` from the verified token.
+3. Compute `sello_token_ref = SHA-256(raw compact JWS bytes)`.
+4. Build a CBOR receipt body describing the action.
+5. Encrypt the receipt body to the owner with HPKE.
+6. Sign the COSE_Sign1 envelope with the service key.
+7. Publish the envelope to an owner-trusted transparency log.
+
+The service signs what it observed. It does not need the owner's private key, and it does not need to understand the owner's downstream audit workflow.
+
+For most services, Sello should fit as middleware around an existing request handler: verify token, run action, emit receipt.
+
+## Owner Verification
+
+An owner verifier does this when reconstructing activity:
+
+1. Compute `sello_token_ref` from the same raw compact JWS bytes.
+2. Query every trusted log for matching receipts.
+3. Confirm each receipt's `sello_log_url` exactly matches the log that returned the proof.
+4. Verify log inclusion.
+5. Resolve the service signing key from `kid`.
+6. Apply revocation rules using log integrated time.
+7. Verify the COSE signature.
+8. Decrypt the HPKE payload.
+9. Validate and display the receipt body.
+
+For most owners, Sello should fit as a pull-based audit tool: provide the token and owner key, then retrieve the verified trail from trusted logs.
+
+## Core Terms
+
+- **Owner:** deploys the agent and holds the HPKE private key.
+- **Agent:** calls services with authorization tokens.
+- **Service:** signs receipts for actions it observed.
+- **Receipt:** encrypted CBOR body inside a signed COSE_Sign1 envelope.
+- **Transparency log:** append-only store that returns inclusion proofs.
+- **`sello_token_ref`:** SHA-256 of the exact raw compact JWS bytes.
+- **`sello_log_url`:** canonical URL of the log that stored the receipt.
+
+## Related Work
+
+Verifiable records of agent activity are an active area, and several projects are working nearby. Sello's specific combination, where the receiving service signs the receipt, encrypts it to the owner, and publishes it to a public transparency log, appears to be distinct, but the surrounding space is rich and worth knowing.
+
+Closest neighbors include Signet, which co-signs MCP responses but keeps receipts in operator-controlled storage; AgentROA, which publishes per-action receipts to a SCITT log but signs at an operator-side gateway and in cleartext; Agent Receipts, which signs on the agent-platform side; and the IETF SCITT working group, whose COSE_Sign1 transparency-receipt framework Sello builds on. Each gets one or two of Sello's four properties. None, as far as we found, combines all four.
+
+Much of this prior work surfaced after Sello's design had already converged on similar primitives. That independent convergence is a good sign the problem is real. See [SPEC.md](SPEC.md) §12 for the fuller prior-art discussion.
+
+## Sharp Edges
+
+- Hash the exact raw compact JWS bytes. Do not parse and reserialize first.
+- Compare log identities by canonical URL string; see `SPEC.md` §6.2.
+- Do not treat an unauthenticated Rekor/off-log index as proof of completeness.
+- Use verifiable log integrated time for revocation decisions, not the receipt timestamp.
+- Deduplicate only on the full spec key, including action type and input/output hashes.
+
+## License
+
+Apache 2.0. See [LICENSE](LICENSE).
+
+## Feedback
+
+Issues and pull requests are welcome. This is an early draft; adversarial review is the point.
+
+## Development
+
+The current dependency-free test command is:
+
+```bash
+node --run test
+```