Beta Community CC0 Agreement

**Effective date:** 2026-06-21

**Version:** 1

**Operator:** the Operator

**Status:** SERVED — operator decided 2026-06-21 to serve this

operator-drafted text now (pre-counsel) on the nwc/nwd/ss live test

sites. Counsel review is still pending per

`~/central/copyright/cc0-question/00-README.docx` §6; counsel-revised

wording will be published as v2 and will force re-acceptance on every

member's next login.

---

0. What this is

This is a clickwrap agreement that every person admitted to the beta

community signs **before** access to the password-gated test sites

(`dir.nwpcode.org`, planned `sd.nwpcode.org`) or to the Narrow Way Commons

review queue is granted. It combines:

• CC0 dedication of the user's contributions
• Confidentiality of test-tier material
• No-warranty acknowledgement
• Acknowledgement of the three-gate public-release pipeline
• Acknowledgement of the upstream-copyright stack

Drafted per `~/central/copyright/12E-DRAFTING-PACK.md` §2 and §4 with

the test-environment-specific clauses sketched in

`~/central/copyright/04-SITES-AND-USER-AGREEMENTS.md` §3.

---

1. The agreement (draft text)

By accepting this agreement, you (the "Beta Member") agree to the

following terms with the Operator (the Operator).

1.1 CC0 dedication of your contributions

For every contribution you make to the project — whether on AV

Commons (`avc.nwpcode.org`), Saint School (`ss.nwpcode.org`), or any

test-tier site (e.g. `dir.nwpcode.org`, `sd.nwpcode.org`) — you

dedicate that contribution to the public domain under **CC0 1.0

Universal**, with an **MIT Licence** fallback should CC0 prove

ineffective in any jurisdiction. You acknowledge:

• Your contribution is **inbound = outbound**: it is offered under

the same dual licence as the rest of the project.

You certify the **origin of your contribution** (aka the Developer

Certificate of Origin, DCO v1.1) — that it is yours to give. This

applies to all your contributions and is summarised in section 5

below.

You give the **moral-rights consent under s 195AW** of the

*Copyright Act 1968* (Cth) as set out in the project's canonical

NOTICE text, available at the site footer.

1.2 Confidentiality of test-tier material

You acknowledge that material visible inside password-gated test

sites (`dir.nwpcode.org`, `sd.nwpcode.org`, and any equivalent

future test site) is **not for redistribution**. You agree:

• Not to export, screenshot at scale, scrape, or copy test-tier

material outside of legitimate research and study use

Not to share test-tier material with any person who is not

themselves a beta member of this project

To report any accidental leakage to the Operator promptly

You may, of course, take personal notes for your own research; you

may quote test-tier material when discussing it with other beta

members; you may use what you learn to inform the original content

you create through the AVC review pipeline.

1.3 No-warranty on test material

You accept test material on an **as-is** basis. Transcripts, indexes,

and search results are computer-generated and may contain errors.

You agree not to rely on the test-tier material as authoritative,

and the Operator makes no warranty of accuracy.

1.4 The three-gate public-release pipeline

You acknowledge that:

• **No test-tier material flows to the public surface directly.**
• The public surface (e.g. `saint.school`) receives only material

that has cleared the three-gate AVC review (writer / pedagogy /

theology).

The public surface contains operator-and-community **reworked**

human-authored expression, public-domain sources, open-licensed

sources, and short attributed quotations from publicly available

upstream video where useful.

Your contributions, after AVC three-gate approval, may form part

of the public surface.

1.5 The upstream copyright stack

You acknowledge:

• Test-tier sites index third-party copyrighted audio under fair

dealing for research, study, and criticism (`Copyright Act 1968`

ss 40, 41), and equivalent provisions of US and EU law.

Where the Operator has obtained explicit permission from a

rightsholder (e.g. Spiritual Direction LLC for DIR), that

permission has its own terms and you agree to abide by them.

Upstream rightsholders retain all rights to their material; the

Operator's CC0 dedication is bounded to material the Operator and

CC0-bound beta members have authored.

1.6 Both AI-content pathways are welcome

You may submit either:

• **Pathway A**: prompt-based AI output, with little or no further

editing, OR

**Pathway B**: AI-assisted material that you have substantially

reworked and integrated as your own intellectual effort

Both are equally welcome and dedicated under the same dual licence.

Where AI output does not attract copyright under strict-jurisdiction

rules, no claim is made — the material is freely usable as public

domain. Where copyright does subsist, the dedication operates

normally.

There is **no separate AI-disclosure requirement**. What you certify —

through the Developer Certificate of Origin (section 5) — is simply

that each contribution is yours to give: created by you, based on work

you have the right to submit, or provided to you by another who so

certified. That single certification governs regardless of the tools

you used, and the doctrinal soundness of every contribution is judged

on its merits by the guild reviewers, not by how it was drafted.

1.7 Beta posture

You acknowledge that the project is in a beta phase. Features,

content, structure, and these terms may change at any time. When

this agreement is updated, you will be required to re-accept the

new version on next login.

1.8 Termination

The Operator may revoke your beta admission at any time without

notice for cause (violation of this agreement or the AUP) or with

reasonable notice without cause. On revocation:

• Your access to test-tier sites and the AVC review queue ends
• Your previously-submitted contributions remain CC0-dedicated

(CC0 is irrevocable; this agreement does not undo past

contributions)

You may terminate your participation at any time by emailing the

Operator. Your past contributions remain CC0-dedicated.

1.9 Governing law

This agreement is governed by the laws in force in Victoria,

Australia.

---

5. Certificate of Origin — aka Developer Certificate of Origin (DCO v1.1) — summary (incorporated by reference)

By making a contribution under this agreement, you certify that the

contribution was created by you, or is based on previous work you

have the right to submit under the open-source licence indicated,

or was provided to you by another person who so certified. You

understand the contribution will be public and a record (including

your name and email in commit metadata and Signed-off-by trailers)

will be maintained indefinitely.

Full DCO v1.1 text is reproduced in `CONTRIBUTING.md` at every NWP-

project repository.

---

6. Signature

By clicking "I accept" on the admission form, you acknowledge:

• You have read and understood this agreement
• You agree to be bound by its terms
• You provide the moral-rights consent in s 195AW form referenced

at section 1.1

You acknowledge confidentiality of test-tier material at section 1.2

Your acceptance is recorded with timestamp, IP address, user-agent,

and your verified email. A copy of the agreement at the version you

accepted is preserved in the project's audit trail.

---

7. Notes to counsel

This draft is for counsel's review per `~/central/copyright/cc0-question/`. Specifically:

• §1.1 dual-licence + DCO + s 195AW consent references are anchored to the canonical NOTICE drafted at `12E-DRAFTING-PACK.md`. The former AI-assistance *disclosure duty* was removed (operator decision 2026-07-22): the DCO warranty (§5) governs contribution rights tool-agnostically, and doctrinal soundness is judged on the merits by guild reviewers — a separate AI-disclosure obligation added procedural burden without independent protective value. §1.6 retains the permissive "both AI pathways welcome" stance.
• §1.2 confidentiality is broad; consider whether a narrower formulation (e.g. tying it to specifically marked content rather than the whole site) is preferable.
• §1.5 upstream-stack acknowledgement assumes Dan Burke has provided written permission for DIR per `DAN-BURKE-AND-FEEDBACK-WORKFLOW.md`; if permission is conditional, section 1.5 needs corresponding conditions.
• §1.6 two-pathway language is from `12E-DRAFTING-PACK.md` §4.
• The agreement is "lite" — no liquidated damages, no indemnity from member back to operator, no jury-trial waiver (the latter being a US convention not relevant in Victoria). Counsel may recommend adding/removing specific clauses for the Australian context.
• §1.9 specifies Victorian law. Counsel may recommend explicit non-exclusive jurisdiction in Victoria.
• This is the doc tagged Q-BETA-01 in `~/central/copyright/07-OPEN-QUESTIONS-AND-VERIFICATION-CHECKLIST.md`. Status: HIGH priority for the counsel engagement.