Skip to content

Commit ce3e61b

Browse files
DeltaClimbsDeltaClimbs
committed
initial commit: MOP-001 draft, manifesto, charter, canary policy
Signed-off-by: DeltaClimbs <DeltaClimbs@users.noreply.github.com>
0 parents  commit ce3e61b

11 files changed

Lines changed: 1614 additions & 0 deletions

File tree

‎.gitignore‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
node_modules/
2+
dist/
3+
.DS_Store
4+
*.log
5+
.env
6+
.env.local

‎CANARY.md‎

Lines changed: 70 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,70 @@
1+
# OpenWyrd MOP — Warrant Canary (policy)
2+
3+
**Project:** OpenWyrd MOP and the SendWyrd reference deployment at sendwyrd.com.
4+
**Status:** Policy published. **First signed attestation pending — pre-launch.**
5+
6+
This file documents the canary mechanism. The first signed attestation lands when the project's hosted reference deployment formally launches and the maintainer key exists. Until then, this is a commitment to the form the canary will take, not an active canary.
7+
8+
Other hosts running MOP MUST publish their own canary at `/canary` with their own key once they accept production traffic. This document does not speak for them.
9+
10+
---
11+
12+
## Affirmations (template)
13+
14+
Once active, each signed attestation will affirm — to the personal knowledge of the signer, as of the timestamp:
15+
16+
1. We have **never** received a National Security Letter, FISA order, FISA §702 directive, or any classified compulsion process.
17+
2. We have **never** received a court order, subpoena, or administrative demand under seal or accompanied by a gag.
18+
3. We have **never** been compelled to modify SendWyrd, OpenWyrd MOP, or any dependency to weaken, backdoor, or instrument it for surveillance, key escrow, or targeted code delivery.
19+
4. We have **never** been compelled to disclose, escrow, or generate cryptographic keys, signing material, or secrets — ours or a user's.
20+
5. We have **never** been compelled to log, retain, or hand over IP addresses, request metadata, recipient handles, publish timestamps, or any data the server transiently sees.
21+
6. We have **never** received a pen-register / trap-and-trace order, Title III wiretap, or equivalent foreign instrument compelling targeted surveillance of any user or address.
22+
7. We have **never** been compelled to disclose the identity of a user, contributor, maintainer, or operator.
23+
8. We have **never** been compelled to add or retain a specific user, key, or capability URL against our policy.
24+
9. No hosting provider, registrar, CDN, or upstream dependency has notified us of compulsion targeting this service that they have passed through to us.
25+
10. No party has demanded suspension of, or change in language to, this canary.
26+
11. No employee, contractor, or maintainer has been approached covertly for any of the above.
27+
28+
We retain the right to refuse to re-sign. We will not lie. **Absence of a fresh signature is the signal.**
29+
30+
---
31+
32+
## Mechanism
33+
34+
- **Signing:** PGP detached signature over this file's bytes. Signature stored at `CANARY.md.asc`.
35+
- **Freshness anchor:** the most recent Bitcoin block height + hash inserted into the signed bytes. Block hashes are unforgeable proof the file was not signed before that block existed; verification requires only any Bitcoin node or block explorer.
36+
- **Cadence:** re-sign every 28 days.
37+
- **Stale threshold:** 35 days. Past day 35 with no re-sign, treat the canary as dropped — no warning, no carve-out.
38+
- **Single-signer at v1.** Promote to 2-of-3 maintainer multi-sig once two additional independent maintainers exist.
39+
40+
## Triggers
41+
42+
The canary drops when the signer:
43+
- refuses to re-sign within the 35-day window, OR
44+
- removes the file, OR
45+
- changes the affirmations text in any non-editorial way.
46+
47+
A vague or hedged language change is itself a signal — diff the canary across versions; the affirmations should be byte-stable apart from freshness fields.
48+
49+
## Hosting (once active)
50+
51+
The signed canary will live, identically, in three places:
52+
53+
- `github.com/openwyrd/mop/CANARY.md` (+ `CANARY.md.asc`)
54+
- `https://openwyrd.org/canary` (DNS- and TLS-anchored mirror)
55+
- `https://sendwyrd.com/canary` (build-time pull from `openwyrd/mop`, surfaced to active users mid-session)
56+
57+
A take-down requires three independent compulsions — GitHub, the DNS/host, and the SendWyrd deploy pipeline — without any of three surfaces noticing. If any one mirror falls out of sync, treat all three as suspect.
58+
59+
## Verification (once active)
60+
61+
```
62+
gpg --verify CANARY.md.asc CANARY.md
63+
```
64+
65+
The fingerprint will be cross-publishable at:
66+
- this repo (`SECURITY.md`)
67+
- <https://keys.openpgp.org>
68+
- <https://openwyrd.org/.well-known/maintainer.asc>
69+
70+
If the fingerprint differs across all three sources, treat the project as compromised.

‎CONTRIBUTING.md‎

Lines changed: 47 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,47 @@
1+
# Contributing to OpenWyrd MOP
2+
3+
## Sign your commits — DCO, not CLA
4+
5+
Every commit must carry a `Signed-off-by:` line. We use the [Developer Certificate of Origin](https://developercertificate.org) (DCO), not a Contributor License Agreement. The DCO is a developer-friendly attestation; it does not concentrate relicensing power in a single entity.
6+
7+
To sign your commits automatically:
8+
9+
```
10+
git commit -s -m "your message"
11+
```
12+
13+
This appends:
14+
15+
```
16+
Signed-off-by: Your Name <you@example.com>
17+
```
18+
19+
Your signature attests to the DCO text below. Commits without `Signed-off-by` will be rejected by CI and at merge.
20+
21+
## What the DCO says
22+
23+
By making a contribution to this project, I certify that:
24+
25+
1. The contribution was created in whole or in part by me and I have the right to submit it under the open source license indicated in the file; or
26+
2. The contribution is based upon previous work that, to the best of my knowledge, is covered under an appropriate open source license and I have the right under that license to submit that work with modifications, whether created in whole or in part by me, under the same open source license (unless I am permitted to submit under a different license), as indicated in the file; or
27+
3. The contribution was provided directly to me by some other person who certified (1), (2) or (3) and I have not modified it.
28+
4. I understand and agree that this project and the contribution are public and that a record of the contribution (including all personal information I submit with it, including my sign-off) is maintained indefinitely and may be redistributed consistent with this project or the open source license(s) involved.
29+
30+
(Full text: <https://developercertificate.org>.)
31+
32+
## How spec changes happen
33+
34+
See [`governance/CHARTER.md`](governance/CHARTER.md) for the RFC process. In short:
35+
36+
1. Open an issue describing the gap or proposed change.
37+
2. If accepted as in-scope, draft a new MOP-NNN doc as a PR.
38+
3. The PR is merged once: (a) a reference implementation lands the change, AND (b) the conformance suite is updated, AND (c) at least one non-reference implementation has signaled feasibility.
39+
4. Breaking changes require a new MOP-NNN doc and a 12-month deprecation window — never an in-place edit of an existing doc post-1.0.
40+
41+
## What stays out of scope
42+
43+
This is a **relay-layer protocol**. Pull requests that drift toward chat-app, social-graph, feed-algorithm, or conversation-hosting territory will be closed. The primitive is the wyrd; everything else is application concern, not protocol concern.
44+
45+
## License of contributions
46+
47+
By submitting code, you agree it is licensed under Apache-2.0. By submitting spec prose, you agree it is licensed under CC-BY-4.0. Both per `LICENSE-CODE` and `LICENSE-DOCS` in this repo.

‎LICENSE-CODE‎

Lines changed: 202 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,202 @@
1+
2+
Apache License
3+
Version 2.0, January 2004
4+
http://www.apache.org/licenses/
5+
6+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
7+
8+
1. Definitions.
9+
10+
"License" shall mean the terms and conditions for use, reproduction,
11+
and distribution as defined by Sections 1 through 9 of this document.
12+
13+
"Licensor" shall mean the copyright owner or entity authorized by
14+
the copyright owner that is granting the License.
15+
16+
"Legal Entity" shall mean the union of the acting entity and all
17+
other entities that control, are controlled by, or are under common
18+
control with that entity. For the purposes of this definition,
19+
"control" means (i) the power, direct or indirect, to cause the
20+
direction or management of such entity, whether by contract or
21+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
22+
outstanding shares, or (iii) beneficial ownership of such entity.
23+
24+
"You" (or "Your") shall mean an individual or Legal Entity
25+
exercising permissions granted by this License.
26+
27+
"Source" form shall mean the preferred form for making modifications,
28+
including but not limited to software source code, documentation
29+
source, and configuration files.
30+
31+
"Object" form shall mean any form resulting from mechanical
32+
transformation or translation of a Source form, including but
33+
not limited to compiled object code, generated documentation,
34+
and conversions to other media types.
35+
36+
"Work" shall mean the work of authorship, whether in Source or
37+
Object form, made available under the License, as indicated by a
38+
copyright notice that is included in or attached to the work
39+
(an example is provided in the Appendix below).
40+
41+
"Derivative Works" shall mean any work, whether in Source or Object
42+
form, that is based on (or derived from) the Work and for which the
43+
editorial revisions, annotations, elaborations, or other modifications
44+
represent, as a whole, an original work of authorship. For the purposes
45+
of this License, Derivative Works shall not include works that remain
46+
separable from, or merely link (or bind by name) to the interfaces of,
47+
the Work and Derivative Works thereof.
48+
49+
"Contribution" shall mean any work of authorship, including
50+
the original version of the Work and any modifications or additions
51+
to that Work or Derivative Works thereof, that is intentionally
52+
submitted to Licensor for inclusion in the Work by the copyright owner
53+
or by an individual or Legal Entity authorized to submit on behalf of
54+
the copyright owner. For the purposes of this definition, "submitted"
55+
means any form of electronic, verbal, or written communication sent
56+
to the Licensor or its representatives, including but not limited to
57+
communication on electronic mailing lists, source code control systems,
58+
and issue tracking systems that are managed by, or on behalf of, the
59+
Licensor for the purpose of discussing and improving the Work, but
60+
excluding communication that is conspicuously marked or otherwise
61+
designated in writing by the copyright owner as "Not a Contribution."
62+
63+
"Contributor" shall mean Licensor and any individual or Legal Entity
64+
on behalf of whom a Contribution has been received by Licensor and
65+
subsequently incorporated within the Work.
66+
67+
2. Grant of Copyright License. Subject to the terms and conditions of
68+
this License, each Contributor hereby grants to You a perpetual,
69+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
70+
copyright license to reproduce, prepare Derivative Works of,
71+
publicly display, publicly perform, sublicense, and distribute the
72+
Work and such Derivative Works in Source or Object form.
73+
74+
3. Grant of Patent License. Subject to the terms and conditions of
75+
this License, each Contributor hereby grants to You a perpetual,
76+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
77+
(except as stated in this section) patent license to make, have made,
78+
use, offer to sell, sell, import, and otherwise transfer the Work,
79+
where such license applies only to those patent claims licensable
80+
by such Contributor that are necessarily infringed by their
81+
Contribution(s) alone or by combination of their Contribution(s)
82+
with the Work to which such Contribution(s) was submitted. If You
83+
institute patent litigation against any entity (including a
84+
cross-claim or counterclaim in a lawsuit) alleging that the Work
85+
or a Contribution incorporated within the Work constitutes direct
86+
or contributory patent infringement, then any patent licenses
87+
granted to You under this License for that Work shall terminate
88+
as of the date such litigation is filed.
89+
90+
4. Redistribution. You may reproduce and distribute copies of the
91+
Work or Derivative Works thereof in any medium, with or without
92+
modifications, and in Source or Object form, provided that You
93+
meet the following conditions:
94+
95+
(a) You must give any other recipients of the Work or
96+
Derivative Works a copy of this License; and
97+
98+
(b) You must cause any modified files to carry prominent notices
99+
stating that You changed the files; and
100+
101+
(c) You must retain, in the Source form of any Derivative Works
102+
that You distribute, all copyright, patent, trademark, and
103+
attribution notices from the Source form of the Work,
104+
excluding those notices that do not pertain to any part of
105+
the Derivative Works; and
106+
107+
(d) If the Work includes a "NOTICE" text file as part of its
108+
distribution, then any Derivative Works that You distribute must
109+
include a readable copy of the attribution notices contained
110+
within such NOTICE file, excluding those notices that do not
111+
pertain to any part of the Derivative Works, in at least one
112+
of the following places: within a NOTICE text file distributed
113+
as part of the Derivative Works; within the Source form or
114+
documentation, if provided along with the Derivative Works; or,
115+
within a display generated by the Derivative Works, if and
116+
wherever such third-party notices normally appear. The contents
117+
of the NOTICE file are for informational purposes only and
118+
do not modify the License. You may add Your own attribution
119+
notices within Derivative Works that You distribute, alongside
120+
or as an addendum to the NOTICE text from the Work, provided
121+
that such additional attribution notices cannot be construed
122+
as modifying the License.
123+
124+
You may add Your own copyright statement to Your modifications and
125+
may provide additional or different license terms and conditions
126+
for use, reproduction, or distribution of Your modifications, or
127+
for any such Derivative Works as a whole, provided Your use,
128+
reproduction, and distribution of the Work otherwise complies with
129+
the conditions stated in this License.
130+
131+
5. Submission of Contributions. Unless You explicitly state otherwise,
132+
any Contribution intentionally submitted for inclusion in the Work
133+
by You to the Licensor shall be under the terms and conditions of
134+
this License, without any additional terms or conditions.
135+
Notwithstanding the above, nothing herein shall supersede or modify
136+
the terms of any separate license agreement you may have executed
137+
with Licensor regarding such Contributions.
138+
139+
6. Trademarks. This License does not grant permission to use the trade
140+
names, trademarks, service marks, or product names of the Licensor,
141+
except as required for reasonable and customary use in describing the
142+
origin of the Work and reproducing the content of the NOTICE file.
143+
144+
7. Disclaimer of Warranty. Unless required by applicable law or
145+
agreed to in writing, Licensor provides the Work (and each
146+
Contributor provides its Contributions) on an "AS IS" BASIS,
147+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
148+
implied, including, without limitation, any warranties or conditions
149+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
150+
PARTICULAR PURPOSE. You are solely responsible for determining the
151+
appropriateness of using or redistributing the Work and assume any
152+
risks associated with Your exercise of permissions under this License.
153+
154+
8. Limitation of Liability. In no event and under no legal theory,
155+
whether in tort (including negligence), contract, or otherwise,
156+
unless required by applicable law (such as deliberate and grossly
157+
negligent acts) or agreed to in writing, shall any Contributor be
158+
liable to You for damages, including any direct, indirect, special,
159+
incidental, or consequential damages of any character arising as a
160+
result of this License or out of the use or inability to use the
161+
Work (including but not limited to damages for loss of goodwill,
162+
work stoppage, computer failure or malfunction, or any and all
163+
other commercial damages or losses), even if such Contributor
164+
has been advised of the possibility of such damages.
165+
166+
9. Accepting Warranty or Additional Liability. While redistributing
167+
the Work or Derivative Works thereof, You may choose to offer,
168+
and charge a fee for, acceptance of support, warranty, indemnity,
169+
or other liability obligations and/or rights consistent with this
170+
License. However, in accepting such obligations, You may act only
171+
on Your own behalf and on Your sole responsibility, not on behalf
172+
of any other Contributor, and only if You agree to indemnify,
173+
defend, and hold each Contributor harmless for any liability
174+
incurred by, or claims asserted against, such Contributor by reason
175+
of your accepting any such warranty or additional liability.
176+
177+
END OF TERMS AND CONDITIONS
178+
179+
APPENDIX: How to apply the Apache License to your work.
180+
181+
To apply the Apache License to your work, attach the following
182+
boilerplate notice, with the fields enclosed by brackets "[]"
183+
replaced with your own identifying information. (Don't include
184+
the brackets!) The text should be enclosed in the appropriate
185+
comment syntax for the file format. We also recommend that a
186+
file or class name and description of purpose be included on the
187+
same "printed page" as the copyright notice for easier
188+
identification within third-party archives.
189+
190+
Copyright [yyyy] [name of copyright owner]
191+
192+
Licensed under the Apache License, Version 2.0 (the "License");
193+
you may not use this file except in compliance with the License.
194+
You may obtain a copy of the License at
195+
196+
http://www.apache.org/licenses/LICENSE-2.0
197+
198+
Unless required by applicable law or agreed to in writing, software
199+
distributed under the License is distributed on an "AS IS" BASIS,
200+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
201+
See the License for the specific language governing permissions and
202+
limitations under the License.

0 commit comments

Comments
 (0)