⚖️ the licensing stack

everything here is given away on purpose — the code, the specs, the patents — except the three things that matter: the name, the sealed soul, and the person. four instruments do the giving; three buttons prove the keeping. press one — the verdict shows below it.

MIT · code CC BY 4.0 · specs pledge · patents TWIN LICENSE · the bones §17 · proof, not prose

four instruments

one repo, four kinds of material, four ways to give it away. each card: why it's cool, what it grants, what it asks — and the full text, one click down.

⚙️

the code

MIT

every runnable surface — the runtime, the companion, the tools — is free to use, fork, sell, and embed. no permission, no royalty, forever. the ecosystem default.

grants
  • use, copy, modify, merge
  • publish, distribute, sublicense
  • sell copies — commercial is fine
asks
  • strip the copyright + permission notice
full text — MIT License
MIT License

Copyright (c) 2026 Kody Wildfeuer

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
📐

the specs & essays

CC BY 4.0

the blueprint is the giveaway — copy it, teach it, ship it, even commercially. attribution is the only string, and that string is the standard-making mechanism: every derivative carries the source home.

may
  • share & redistribute in any medium
  • adapt, remix, build upon — any purpose
  • implement the protocol, teach it, sell the teaching
must
  • drop attribution — credit, link the license, note changes
full text — CC BY 4.0 (human-readable deed + governance)
Creative Commons Attribution 4.0 International (CC BY 4.0)

Covers: my-twin.profile.md, rapp-twin.profile.md, SPEC.md, and the design docs
under */design/ — the specs & essays layer (see /LICENSING.md).

YOU ARE FREE TO:
  Share  — copy and redistribute the material in any medium or format.
  Adapt  — remix, transform, and build upon the material for any purpose,
           even commercially.
The licensor cannot revoke these freedoms as long as you follow the terms.

UNDER THE FOLLOWING TERM:
  Attribution — You must give appropriate credit, provide a link to the
  license, and indicate if changes were made. You may do so in any reasonable
  manner, but not in any way that suggests the licensor endorses you or your
  use.
No additional restrictions — You may not apply legal terms or technological
measures that legally restrict others from doing anything the license permits.

Attribution is the standard-making mechanism: derivatives carry the source,
so the pattern spreads with its provenance intact.

Full legal code: https://creativecommons.org/licenses/by/4.0/legalcode
🛡️

the patents

Patent Pledge

the patent is a shield, not a toll booth. we pledge never to assert it against a conformant implementation — build without fear. the pattern wins by adoption, not by tax. shields answer swords.

grants
  • non-assertion for conformant implementations
  • irrevocable, runs with the patents, binds successors
terminates
  • if you assert a patent at the ecosystem (defensive only)
full text — RAPP Patent Pledge
# RAPP Patent Pledge

**The pledge:** We will not assert any patent we hold or control that reads on
the RAPP twin protocol (the pattern described in `my-twin.profile.md`,
`rapp-twin.profile.md`, and the `kody-w/twin` protocol surfaces — signed
content-addressed identity frames, the public-bones / sealed-soul split, the
static pulse broadcast, capture-and-splice lineage, twin-anchored pairing, and
delegated twin reports) against anyone for making, using, or distributing a
**conformant implementation** of that protocol.

**Why:** The pattern wins by adoption. The patent exists as a shield — prior
art and freedom to operate — not as a toll booth. Implementers should build
without fear.

**Defensive termination:** This pledge is void, as to a given party, if that
party (or its affiliates) asserts any patent against the RAPP ecosystem, its
maintainers, or any conformant implementation. Shields answer swords.

**Conformant** means: implements the protocol as specified, does not
misrepresent modified twins as authentic (signature verification honored), and
preserves provenance/lineage.

This pledge is irrevocable for conformant use, runs with the patents, and binds
successors. It is a public statement of intent by the RAPP project (Kody
Wildfeuer), 2026-07-06. It is not legal advice and does not expand any license
beyond its terms.
🧬

the twin — a person's bones

TWIN LICENSE v1.0

identity is not software. render, verify, mirror, and splice the public bones freely — but you may never present a fake as authentic, impersonate the person, or clone them. the cryptography enforces most of it: an altered twin fails its own signature.

may
  • fetch, verify, cache, mirror byte-identically
  • render & interact per the protocol
  • splice traits into your OWN twin, lineage preserved
  • quote & study for interop, with attribution
may not
  • distribute modified bones as authentic
  • impersonate the owner
  • train a derivative persona of the owner
  • strip provenance / lineage / signatures
full text — TWIN LICENSE v1.0 (draft)
# TWIN LICENSE v1.0 (draft)

A license for a person's digital twin — the public bones of a digital organism
that represents a living human being. Code is covered by open-source licenses;
a person is not. This license covers the space between.

**Covered material ("the Bones"):** the public identity artifacts of this twin —
card.json, facets.json, visual genome and body/outfit assets (holo.svg, holo.md,
textures), signed frames (frames/), the feed (feed.xml), and any published
public notes. **Not covered:** the tools and runtime code (MIT — see LICENSE),
and the sealed private half (never published; all rights reserved absolutely).

## You MAY, freely and without asking:
1. Fetch, verify, cache, and mirror the Bones byte-identically. Any mirror is a
   valid door; the hash is the authenticity test.
2. Render and interact with the twin per the RAPP twin protocol — host it, talk
   to it, let it participate in your spaces, carry its delegation reports.
3. Splice published traits into YOUR OWN twin with lineage recorded, as the
   protocol provides. Lineage attribution must be preserved.
4. Quote and study the Bones for interoperability, research, and commentary,
   with attribution.

## You may NOT:
1. Distribute modified Bones as authentic. If the signature does not verify
   against the twin's published public key, it is not this twin, and must not
   be presented as this twin.
2. Impersonate the owner — present any derivative of the Bones as being,
   speaking for, or authorized by the person this twin represents.
3. Train or generate a derivative persona of the owner (a model, agent, or twin
   intended to emulate this specific person) without the owner's written
   consent. Splicing individual traits into your own distinct twin (§MAY-3) is
   not a derivative persona; cloning the person is.
4. Strip provenance — remove or falsify lineage, frame history, signatures, or
   this license.

## Terms
- Violation terminates this license automatically. Verified byte-identical
  redistribution can never violate it.
- The owner's rights of personality, publicity, and identity are reserved in
  full and are not waived by publication of the Bones.
- This license travels with the Bones: mirrors must include it.
- Composes with the RAPP twin canon: signature verification proves authenticity
  (my-twin §2/§4); foreign frames are claims until quarantined (§14);
  succession passes ownership per §15 — heirs inherit the owner's rights.

Owner: Kody Wildfeuer · Twin address: kody-w/twin · Version: TWIN-LICENSE-1.0
(draft, 2026-07-06)

§17 · the three things that matter — proven, not promised

the proof rule: no public claim without a runnable proof. these buttons run the actual verification live, in your browser — fetching only from api.github.com, kody-w.github.io, and raw.githubusercontent.com. trust is never requested, only made unnecessary.

🔒 the private key is not in the repo

the giveaway is total — except the soul. the twin's public bones are published; its private signing key is absent from the network entirely. this button queries the live GitHub API for kody-w/twin and scans the whole tree for it.

contents/keys + the full recursive git tree
— press the button — the verdict shows here —
    run it yourself
    curl -s https://api.github.com/repos/kody-w/twin/contents/keys | grep name
    #   → only "twin.pub"  (the public half)
    curl -s "https://api.github.com/repos/kody-w/twin/git/trees/main?recursive=1" | grep -c '"twin.key"'
    #   → 0   (the private half never left the device)

    📜 the licenses actually travel

    a license only matters if it arrives with the thing it governs. this button fetches TWIN-LICENSE.md from two independent doors, hashes both with SHA-256 in your browser, and shows them byte-identical. kill either door; the license survives on the other.

    github.io vs raw.githubusercontent
    — press the button — the verdict shows here —
      run it yourself
      a=$(curl -s https://kody-w.github.io/twin/TWIN-LICENSE.md | shasum -a 256 | cut -d' ' -f1)
      b=$(curl -s https://raw.githubusercontent.com/kody-w/twin/main/TWIN-LICENSE.md | shasum -a 256 | cut -d' ' -f1)
      [ "$a" = "$b" ] && echo "IDENTICAL — the license is content-addressed too: $a"

      📄 first-use evidence exists

      the name is the one exclusive asset, so the clock has to start in public with a date on it. this button fetches both published essays from the github.io mirror (kodyw.com itself is CORS-walled) and renders their publish dates and the RAPP™ footer line, verbatim from the body.

      the-ai-you-keep · what-is-our-moat
      — press the button — the verdict shows here —
        run it yourself
        for s in the-ai-you-keep what-is-our-moat; do
          curl -s "https://raw.githubusercontent.com/kody-w/kody-w.github.io/master/_posts/2026-07-05-$s.md" \
            | grep -E "^date:|RAPP™"
        done

        the mark — the one thing not given away

        implement the protocol freely; the name is the only fence. it's what makes “RAPP-compatible” mean something — the Bluetooth / USB / Java model.

        RAPP
        ™ claimed · registration in progress
        the platform / protocol name. word mark, filed first (IC 009 + IC 042).
        THE AI YOU KEEP
        ™ claimed · registration in progress
        the brand line — yours, alive, quiet, forever, private to the bone.
        the usage rule: implement the protocol freely under the instruments above. call your implementation “RAPP-compatible” only if it conforms — implements the protocol as specced, honors signature verification, preserves provenance (the same conformance the patent pledge requires). “RAPP” as your product's name: no.  🔨 COMPATIBILITY.md — being written