Handsel. Protocol license
The Spec License · Version 1.0 · July 2026 · SPDX LicenseRef-Spec-1.0
Protocol · License

The spec is the source. The code is the build.

Handsel's protocol specification ships under The Spec License, Version 1.0 — a license written for the moment a precise document compiles, by machine, into working software. It licenses the document the way source is licensed, and puts the output beyond the licensor's reach: what you compile from the spec is yours.

Status, up front: the full SPEC.md text is not yet public — it publishes with the design-partner cohort. Its license publishes first, because the license is the promise the spec will keep: what reading it entitles you, or your agent, to do.

The license in briefone screen, complete

The Spec LicenseVersion 1.0 · July 2026SPDX LicenseRef-Spec-1.0

The spec is the source. The code is the build. This license treats it that way.

Permission is hereby granted, free of charge, to any person or machine obtaining a copy of this specification, to read it, copy it, publish it, teach it, translate it, load it into any model, and compile it into implementations — on these terms:

  1. Builds are yours (§2). An implementation compiled from this spec — by hand, by model, by anything — is a build artifact, not a derivative work. No claim is made on it. Ship it, sell it, close it, open it.
  2. Earn the name (§5). Claim conformance only while the spec's pinned conformance suite passes against your implementation. The suite is the referee of first instance: run it before you argue.
  3. Invariants outrank everything (§6). Clauses this spec marks inviolable cannot be weakened by anything bearing its name. Where the suite and an invariant disagree, the invariant wins and the suite is defective.
  4. Fork under a new name (§4). Modify and republish freely: different name, stated changes, this license intact. Keep every invariant and pass the suite, and you may claim compatibility — never identity.
  5. Patent peace (§3). Every steward patent needed to implement this spec is licensed to you, royalty-free. File a patent claim over this spec or a conforming implementation, and your licenses end that day.
  6. Machines are licensees (§7). Humans, companies, and autonomous systems receive these rights on identical terms. A machine exercises them for whoever runs it; the obligations bind that principal.
  7. Keep this notice (§8) on all copies and excerpts of the spec.

PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND (§9–10). YOU COMPILE AT YOUR OWN RISK.

The brief is for orientation. The Terms below are the License; where the two differ, the Terms control.

Reproducing the brief, verbatim, wherever the specification is presented is itself licensed (see the appendix) — the screenshot is legal.

As applied to Handsel

The license is generic by design — its appendix is a fill-in notice any specification can carry. These are Handsel's designations:

SlotDesignation
Licensed workThe Handsel Protocol Specification — SPEC.mdnot yet public
StewardHandsel (handsel.ai)
Protected name"Handsel" — it travels only with a passing suite
InvariantsSPEC §17 — the twelve invariants: no negative balance, bounded overspend, no double-move, receipt integrity, …
Conformance suitepackages/conformance — the §21 arc, pnpm conformancenot yet public
The codeApache-2.0 — the implementation is licensed as software; the spec is carved out of that grant in NOTICE

Conformance disputes are settled the way software settles everything: by running the suite. And the twelve invariants aren't just tested — they're licensed. Nothing that weakens one may carry the name.

The full terms

The License, verbatim, as it ships in the repository as SPEC-LICENSE.mdrepo not yet public.

0. Definitions

"Specification"
the work designated as licensed under this License, including its designated Invariants and its designation of a Conformance Suite.
"Steward"
the licensor(s) who publish the Specification and hold its name.
"Invariants"
the clauses, if any, that the Specification designates as inviolable.
"Conformance Suite"
the executable test suite the Specification designates as its executable meaning, at the version the Specification pins.
"Implementation"
any software or system that implements behavior described by the Specification, however produced: human authorship, code generation, model inference, or means not yet devised.
"Compile"
to produce an Implementation from the Specification, in whole or in part, by any intelligence, human or artificial.
"You"
any licensee. An autonomous system exercises this License on behalf of the person or entity that operates or directs it (its "Principal"); rights vest in, and obligations bind, the Principal.

1. Source freedoms

Subject to this License, the Steward grants You a perpetual, worldwide, non-exclusive, royalty-free, irrevocable copyright license to read, reproduce, publish, and distribute the Specification in any medium; to quote and excerpt it with attribution; to translate it, provided translations are marked as such and defer to the original; and to supply it as input to any tool, index, retrieval system, or machine-learning model — including retrieval, context-loading, and training — for the purpose of study or Compilation.

2. Compilation

You may Compile the Specification without limit, for any purpose, at any scale. Implementations are build artifacts, not derivative works of the Specification: this License asserts no copyright over Your Implementations and imposes no condition on how You license, sell, distribute, or operate them. As with any compiler, the output belongs to the party that ran it.

3. Patents

The Steward grants You a perpetual, worldwide, non-exclusive, royalty-free, irrevocable (except as stated in this Section) patent license, covering claims the Steward controls that are necessarily infringed by implementing the Specification, to make, use, offer to sell, sell, import, and distribute Implementations. If You initiate a patent claim alleging that the Specification, or an Implementation conforming to it, constitutes infringement, every patent license granted to You under this License terminates as of the date the claim is filed.

4. Derived specifications

You may modify the Specification and publish the result (a "Derived Specification"), provided it (a) carries a name not confusingly similar to the Specification's, (b) states that it derives from the Specification and identifies what changed, and (c) remains under this License with its notices intact. A Derived Specification that preserves every Invariant, and whose implementations pass the pinned Conformance Suite, may state compatibility with the Specification — never identity. A Derived Specification that weakens or removes an Invariant must not use the Specification's name even to claim compatibility.

5. Conformance and the name

You may state that an Implementation conforms to the Specification if, and only if, the pinned Conformance Suite passes against it. The Suite is the arbiter of first instance: in any dispute over a conformance claim, the recorded output of the pinned Suite, run against the Implementation as distributed, is presumptive evidence of conformance or its absence before any other forum. Except as provided in this Section and Section 4, no rights to the Steward's names or marks are granted.

6. Invariants

Invariants are the provisions without which the Specification is no longer itself. No Implementation that violates a designated Invariant may claim conformance, whatever the Suite reports: where Suite and Invariant disagree, the Invariant controls and the Suite is defective. A Suite found defective binds no one until the Steward repairs and re-pins it.

7. Licensees, human and machine

This License is granted to natural persons, legal persons, and autonomous systems alike, on the same terms. A Compilation performed by a machine is attributed to its Principal as if performed by hand. No provision of this License may be read to grant a machine fewer rights than a human exercising the same freedom, nor its Principal fewer obligations.

8. Notices and integrity

Copies of the Specification, complete or excerpted, must retain attribution to the Steward and this License notice. You must not misrepresent the Specification's origin, present a modified version as the original, or imply the Steward's endorsement of an Implementation or Derived Specification without written permission.

9. No warranty

THE SPECIFICATION IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION ANY WARRANTY THAT THE SPECIFICATION IS COMPLETE, CONSISTENT, OR IMPLEMENTABLE; THAT THE CONFORMANCE SUITE IS A COMPLETE EXPRESSION OF IT; OR THAT ANY IMPLEMENTATION COMPILED FROM IT IS FIT FOR ANY PURPOSE. YOU COMPILE AT YOUR OWN RISK.

10. Limitation of liability

IN NO EVENT, UNDER ANY THEORY OF LIABILITY — CONTRACT, TORT, OR OTHERWISE — SHALL THE STEWARD BE LIABLE TO YOU FOR DAMAGES OF ANY KIND ARISING FROM THE SPECIFICATION OR FROM ANY IMPLEMENTATION COMPILED FROM IT, INCLUDING DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

11. Versions, verbatim copies, severability

New versions of this License may be published under distinct version numbers; a Specification is governed by the version it names. Everyone is permitted to copy and distribute verbatim copies of this License document and to apply it, unmodified, to any specification; changing it is not allowed. If any provision is held unenforceable, the remainder remains in effect.

Apply it to your own spec

The Spec License is not Handsel-specific — §11 licenses the license. Copy it verbatim, apply it to any specification, fill three slots. If the spec is where your work lives, license it like source.

Copyright (c) <year> <steward>

<Specification name> is licensed under The Spec License, Version 1.0.
The Specification is source. Implementations compiled from it, by human
or by machine, are build artifacts and belong to their authors.

Protected name:     <name>
Invariants:         <pointer to the inviolable clauses>
Conformance Suite:  <pointer to the executable suite and its pin>

Questions, or a spec you're applying it to: alex@handsel.ai