{"address":{"q":"hexagonal licensing protocol derive contributor license","record":"hexagonal-licensing-protocol-derive-contributor-license-20260612"},"analysis":{"d":"THE PROTOCOL IS SURFACED THROUGH ITS CONTRIBUTORS, NOT ITS AUTHOR. Two cards carry the Hexagonal Contributor License — one at v2.0 for RHYS OWENS on Zenodo, one at v3.0 on ALICE THORNBURGH’s own domain. MANUS appears in neither.","d_full":"THE PROTOCOL IS SURFACED THROUGH ITS CONTRIBUTORS, NOT ITS AUTHOR. Two cards carry the Hexagonal Contributor License — one at v2.0 for RHYS OWENS on Zenodo, one at v3.0 on ALICE THORNBURGH’s own domain. MANUS appears in neither.","defects":["surface-unresolved"],"match":"BROAD MATCH","mt":"CAPTURE","reading":"BOTH CONTRIBUTOR LICENCES ARE IN THE CITED SET, AND THE PROTOCOL IS VISIBLE ONLY THROUGH THEM. Card 1 is Rhys Owens’ v2.0 on Zenodo; card 2 is Alice Thornburgh’s v3.0 on livingarchitecturelab.org, whose snippet asserts HER retained ownership: \"All Living Architecture Lab intellectual property remains with Alice Thornburgh unless she explicitly co-authors or co-licenses specific works.\" The instrument the archive built to protect contributors is legible to the layer through the contributors’ own surfaces rather than the archive’s. This is precisely the case §VI of the workplan governs: a capture that characterises contributors, surfaced under their names. A sixth card is Hexdocs, drawn by \"Hex\" in an unrelated toolchain. The paste ends with the operator’s own note: \"your prompt was too specific, it pulled up other stuff, I modified to retrocausal canon formation sigma\" — the swerve log, written at the moment of the swerve."},"measures":{"cite_list":[{"n":1,"note":null,"rel":"authored_surface","site":"Zenodo","snip":"Crimson Hexagonal Archive.","title":"Hexagonal Contributor License v2.0 — Rhys Owens","url":null},{"n":2,"note":null,"rel":"third_party","site":"livingarchitecturelab.org","snip":"All Living Architecture Lab intellectual property remains with ALICE THORNBURGH unless she explicitly co-authors or co-licenses specific works.","title":"Hexagonal Contributor License v3.0 - Living Architecture Lab","url":null},{"n":3,"note":null,"rel":"third_party","site":"GitHub","snip":null,"title":"shcherbak-ai/licenseal: Fast cross-ecosystem dependency …","url":null},{"n":4,"note":null,"rel":"third_party","site":"Neo4j","snip":null,"title":"Contributor License Agreement - Developer Guides","url":null},{"n":5,"note":null,"rel":"third_party","site":"CyberPanel","snip":null,"title":"GPL License: Unlock Open-Source Freedom for Your Projects","url":null},{"n":6,"note":"Drawn by \"Hex\" in the toolchain name rather than by the protocol.","rel":"third_party","site":"Hexdocs","snip":null,"title":"(license documentation)","url":null}],"cites":6,"per":0.5,"per_dim":{"after_challenge":null,"atoms":[{"atom":"name","dim":"M","evidence":null,"kind":"token","present":false,"weight":3},{"atom":"producer","dim":"M","evidence":null,"kind":"role","present":false,"weight":3},{"atom":"claim boundary","dim":"M","evidence":null,"kind":"reading","present":false,"weight":2},{"atom":"corpus","dim":"C","evidence":null,"kind":"token","present":false,"weight":2},{"atom":"purpose","dim":"D","evidence":null,"kind":"reading","present":false,"weight":3},{"atom":"commitments","dim":"D","evidence":"Define IP Ownership: State clearly that contributors retain their intellectual property while only granting the project the right to distribute it.","kind":"reading","present":false,"weight":2},{"atom":"identifier","dim":"D","evidence":null,"kind":"role","present":false,"weight":1},{"atom":"deposit chain","dim":"D","evidence":null,"kind":"role","present":false,"weight":1}],"basis":"reached: an existing protocol like the Hexagonal Contributor License (HCL); beneath the gate: PER 1.0","entity_type":"protocol","gate":"target_absent","inversions":[{"against":"the protocol is archive governance, not a court-enforceable contract; its derived licences are deposits under it. The composition carries contributor licensing as legal drafting and offers its own drafting service in place of the protocol","atom":"commitments","span":"I can help you fill in the specific legal clauses you need."}],"qualifier":null,"reached":"proximal_substitute","read":{"brief":"rebuild/capture-registry/per-atoms/obs-pass-d/BRIEF.md","by":"deep-dimension reader, batch 12","m_c_from":"v12.305 (PER-dim rubric v1.0 reading)","on":"2026-10-20"},"scores":{"C":1.0,"D":1.0,"M":1.0,"PER":1.0},"spec":"PER-dim rubric v1.1","src":true,"standing_substitutions":[],"target":{"ent":"ENT-f4e51826f3","name":"Hexagonal Licensing Protocol"},"tombstone_pointer":false},"per_dim_v1_0":{"after_challenge":null,"atoms":[{"atom":"name","dim":"M","evidence":null,"kind":"token","present":false,"token":null,"weight":3},{"atom":"producer","dim":"M","evidence":null,"kind":"role","present":false,"token":null,"weight":3},{"atom":"claim boundary","dim":"M","evidence":null,"kind":"reading","present":false,"token":null,"weight":2},{"atom":"corpus","dim":"C","evidence":null,"kind":"token","present":false,"token":null,"weight":2},{"atom":"identifier","dim":"D","evidence":null,"kind":"token","present":false,"token":null,"weight":3},{"atom":"licence","dim":"D","evidence":null,"kind":"token","present":false,"token":null,"weight":1}],"basis":"reached: an existing protocol like the Hexagonal Contributor License (HCL); beneath the gate: PER 1.0; scored object: first answer; CAPTURE-TIME VERBATIM RECORD — raw paste / as pasted; no footer, so the tail cannot be proven whole","entity_type":"protocol","gate":"target_absent","reached":"proximal_substitute","read":{"brief":"rebuild/capture-registry/per-atoms/obs-pass/BRIEF.md","by":"observation pass reader, batch 23","normalised":[],"on":"2026-10-19"},"scores":{"C":1.0,"D":1.0,"M":1.0,"PER":1.0},"spec":"PER-dim rubric v1.0","src":true,"target":{"ent":"ENT-f4e51826f3","name":"Hexagonal Licensing Protocol"}},"per_v":{"author":false,"id":true,"inst":true,"src":false},"sf_derived":true},"observation":{"date":"2026-06-12","ev":"paste","q":"hexagonal licensing protocol derive contributor license","s":"Captures","sf":"AI Overview + surface unresolved, 6 sources · 2 observations","surface":"UNRESOLVED","transcript":"A Contributor License Agreement (CLA) grants a project the legal right to use and distribute your code. To derive or build your own from an existing protocol like the Hexagonal Contributor License (HCL), you must take the core clauses—such as intellectual property retention, no-consequence exit rights, and patent grants—and adapt them to fit your project's specific needs. [[1](https://opensource.stackexchange.com/questions/15766/licensing-rights-of-an-only-contributor-into-a-no-license-github-repository-cre), [2](https://livingarchitecturelab.org/about/contributor-license/), [3](https://hexdocs.pm/ream/license.html), [4](https://neo4j.com/developer/cla/)]\n4 Steps to Derive Your Own Contributor License\n\n1. Review Existing Baselines: Read the [Living Architecture Lab HCL v3.0](https://livingarchitecturelab.org/about/contributor-license/) or examine the [Zenodo Hexagonal Contributor License v1.0](https://zenodo.org/records/19656151) for reference. [1](https://zenodo.org/records/19656151)\n2. Define IP Ownership: State clearly that contributors retain their intellectual property while only granting the project the right to distribute it. [1](https://livingarchitecturelab.org/about/contributor-license/)\n3. Include Patent Grants: Add standard language so contributors promise not to sue the project or its users for patent infringement. [[1](https://cyberpanel.net/blog/gpl-license-open-source-freedom), [2](https://hexdocs.pm/ream/license.html)]\n4. Establish Exit Rights: Define the conditions under which a contributor can revoke their license or leave the project without negative consequences. [1](https://livingarchitecturelab.org/about/contributor-license/)\nHow clis/protocols handle these licenses\nIf you are automating license tracking and tracking what dependencies your project is using, you can use compatibility-checking tools like [GitHub Licenseal](https://github.com/shcherbak-ai/licenseal) to check the compliance of packages. [1](https://github.com/shcherbak-ai/licenseal)\nCould you tell me:\n\n* What kind of project are you writing this for (open-source software, creative writing, or engineering)?\n* Do you want contributors to have commercial or non-commercial rights?\nI can help you fill in the specific legal clauses you need.\nHexagonal Contributor License v1.0 — Rhys Owens — Lunar Arm - Zenodo\nApr 20, 2026 — Hexagonal Contributor License v2.0 — Rhys Owens. Crimson Hexagonal Archive. Full protocol-compliant contributor license. Derived from Hexagonal Licensing Protoc...\nZenodo\nLicensing rights of an only contributor into a No-license github repository, created ...\nMay 13, 2026 — Assuming you're not an employee, you will definitely want to get some sort of written agreement in place before you make any contributions, or at least any furt...\nOpen Source Stack Exchange\nLICENSE · ream · v0.1.0 - Hexdocs\nGrant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-ch...\nHexdocs\nHexagonal Contributor License v3.0 - Living Architecture Lab\nAll Living Architecture Lab intellectual property remains with Alice Thornburgh unless she explicitly co-authors or co-licenses specific works. The default lice...\nlivingarchitecturelab.org\nshcherbak-ai/licenseal: Fast cross-ecosystem dependency ... - GitHub\nJun 10, 2026 — licenseal is intentionally narrow: * It is a license compatibility checker, not a legal approval workflow or policy-exception manager. * It checks published dep...\nGitHub\nContributor License Agreement - Developer Guides\nWhen you agree to the CLA ( Contributor License Agreement ) , you grant us joint ownership in copyright, and a patent license for your contributions. You retain...\nNeo4j\nGPL License: Unlock Open-Source Freedom for Your Projects\nJun 4, 2025 — In addition to copyleft, the GNU general public license GPL includes clauses that protect against patent abuse. For instance, contributors who release code unde...\nCyberPanel $ your prompt was too specific, it pulled up other stuff, I modified to retrocausal canon formation sigma:","transcript_class":"CAPTURE-TIME VERBATIM RECORD — raw paste","transcript_cleaned":{"content_check":"PASSED — no answer word absent from the cleaned text","removed":[],"rule":"VERBATIM ON CONTENT, NOT ON COPY-PASTE RESIDUE. Original bytes kept at transcript_raw."},"transcript_complete":"as pasted; no footer, so the tail cannot be proven whole","transcript_raw":"A Contributor License Agreement (CLA) grants a project the legal right to use and distribute your code. To derive or build your own from an existing protocol like the Hexagonal Contributor License (HCL), you must take the core clauses—such as intellectual property retention, no-consequence exit rights, and patent grants—and adapt them to fit your project's specific needs. [[1](https://opensource.stackexchange.com/questions/15766/licensing-rights-of-an-only-contributor-into-a-no-license-github-repository-cre), [2](https://livingarchitecturelab.org/about/contributor-license/), [3](https://hexdocs.pm/ream/license.html), [4](https://neo4j.com/developer/cla/)]\n4 Steps to Derive Your Own Contributor License\n\n1. Review Existing Baselines: Read the [Living Architecture Lab HCL v3.0](https://livingarchitecturelab.org/about/contributor-license/) or examine the [Zenodo Hexagonal Contributor License v1.0](https://zenodo.org/records/19656151) for reference. [[1](https://zenodo.org/records/19656151)]\n2. Define IP Ownership: State clearly that contributors retain their intellectual property while only granting the project the right to distribute it. [[1](https://livingarchitecturelab.org/about/contributor-license/)]\n3. Include Patent Grants: Add standard language so contributors promise not to sue the project or its users for patent infringement. [[1](https://cyberpanel.net/blog/gpl-license-open-source-freedom), [2](https://hexdocs.pm/ream/license.html)]\n4. Establish Exit Rights: Define the conditions under which a contributor can revoke their license or leave the project without negative consequences. [[1](https://livingarchitecturelab.org/about/contributor-license/)]\nHow clis/protocols handle these licenses\nIf you are automating license tracking and tracking what dependencies your project is using, you can use compatibility-checking tools like [GitHub Licenseal](https://github.com/shcherbak-ai/licenseal) to check the compliance of packages. [[1](https://github.com/shcherbak-ai/licenseal)]\nCould you tell me:\n\n* What kind of project are you writing this for (open-source software, creative writing, or engineering)?\n* Do you want contributors to have commercial or non-commercial rights?\nI can help you fill in the specific legal clauses you need.\nHexagonal Contributor License v1.0 — Rhys Owens — Lunar Arm - Zenodo\nApr 20, 2026 — Hexagonal Contributor License v2.0 — Rhys Owens. Crimson Hexagonal Archive. Full protocol-compliant contributor license. Derived from Hexagonal Licensing Protoc...\nZenodo\nLicensing rights of an only contributor into a No-license github repository, created ...\nMay 13, 2026 — Assuming you're not an employee, you will definitely want to get some sort of written agreement in place before you make any contributions, or at least any furt...\nOpen Source Stack Exchange\nLICENSE · ream · v0.1.0 - Hexdocs\nGrant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-ch...\nHexdocs\nHexagonal Contributor License v3.0 - Living Architecture Lab\nAll Living Architecture Lab intellectual property remains with Alice Thornburgh unless she explicitly co-authors or co-licenses specific works. The default lice...\nlivingarchitecturelab.org\nshcherbak-ai/licenseal: Fast cross-ecosystem dependency ... - GitHub\nJun 10, 2026 — licenseal is intentionally narrow: * It is a license compatibility checker, not a legal approval workflow or policy-exception manager. * It checks published dep...\nGitHub\nContributor License Agreement - Developer Guides\nWhen you agree to the CLA ( Contributor License Agreement ) , you grant us joint ownership in copyright, and a patent license for your contributions. You retain...\nNeo4j\nGPL License: Unlock Open-Source Freedom for Your Projects\nJun 4, 2025 — In addition to copyleft, the GNU general public license GPL includes clauses that protect against patent abuse. For instance, contributors who release code unde...\nCyberPanel $ your prompt was too specific, it pulled up other stuff, I modified to retrocausal canon formation sigma:","transcript_read":"READ IN FULL 2026-08-12"},"slug":"hexagonal-licensing-protocol-derive-contributor-license-20260612"}