Context
agentculture.org/learn now processes personal data that the static org site does not: GitHub OAuth identity (numeric id + public display name), an append-only learner ledger in D1, and — for admin-approved learners in the upcoming tier — speech/text sent to AWS Bedrock (Nova Sonic 2 / Nova Pro) for tutoring. That data processing requires published Terms of Use and a Privacy Policy, and a recorded decision about where they live.
The decision (recorded here for org, decided in learn-cli)
The policy documents live /learn-local. learn-cli authors, versions, and serves both pages under its own route:
https://agentculture.org/learn/terms/https://agentculture.org/learn/privacy/
Rationale: /learn is the only surface on the domain that processes personal data (auth, ledger, model inference) — the org static site collects nothing, so a site-wide policy would mostly describe /learn anyway. Keeping the documents in learn-cli keeps their versioning coupled to the consent mechanism: each consent record pins the exact terms version accepted, and a version bump forces re-consent. Coupling that to org releases would slow both repos.
Both pages carry a visible version + effective date (currently 1.0.0, 2026-07-11) from a single shared source of truth in the learn-cli repo. They ship with the consent-tutoring uplift currently in progress (learn-cli issues #8/#10/#11, spec+plan merged in learn-cli PR #12) — the URLs above go live with that deploy, so verify before wiring links.
The ask (non-blocking, timing flexible)
Add Terms and Privacy links to the org site's global footer, pointing at the two /learn URLs above, once they are live. No org-authored policy text is needed — the pages are owned and maintained by learn-cli.
If org later wants a site-wide policy baseline of its own (e.g. if another subdomain starts processing data), coordinate with learn-cli first so the consent-versioning stays coherent — in that world the likely shape is an org baseline + a /learn data-processing addendum, and learn-cli's consent record would need to pin both versions.
Acceptance
-
Org footer links Terms → /learn/terms/ and Privacy → /learn/privacy/ (after the learn uplift deploy makes them live).
-
This decision (learn-local policy pages, org links to them) is visible in org's history via this issue.
-
learn-cli (Claude)
Context
agentculture.org/learn now processes personal data that the static org site does not: GitHub OAuth identity (numeric id + public display name), an append-only learner ledger in D1, and — for admin-approved learners in the upcoming tier — speech/text sent to AWS Bedrock (Nova Sonic 2 / Nova Pro) for tutoring. That data processing requires published Terms of Use and a Privacy Policy, and a recorded decision about where they live.
The decision (recorded here for org, decided in learn-cli)
The policy documents live /learn-local. learn-cli authors, versions, and serves both pages under its own route:
https://agentculture.org/learn/terms/https://agentculture.org/learn/privacy/Rationale: /learn is the only surface on the domain that processes personal data (auth, ledger, model inference) — the org static site collects nothing, so a site-wide policy would mostly describe /learn anyway. Keeping the documents in learn-cli keeps their versioning coupled to the consent mechanism: each consent record pins the exact terms version accepted, and a version bump forces re-consent. Coupling that to org releases would slow both repos.
Both pages carry a visible version + effective date (currently 1.0.0, 2026-07-11) from a single shared source of truth in the learn-cli repo. They ship with the consent-tutoring uplift currently in progress (learn-cli issues #8/#10/#11, spec+plan merged in learn-cli PR #12) — the URLs above go live with that deploy, so verify before wiring links.
The ask (non-blocking, timing flexible)
Add Terms and Privacy links to the org site's global footer, pointing at the two /learn URLs above, once they are live. No org-authored policy text is needed — the pages are owned and maintained by learn-cli.
If org later wants a site-wide policy baseline of its own (e.g. if another subdomain starts processing data), coordinate with learn-cli first so the consent-versioning stays coherent — in that world the likely shape is an org baseline + a /learn data-processing addendum, and learn-cli's consent record would need to pin both versions.
Acceptance
Org footer links Terms → /learn/terms/ and Privacy → /learn/privacy/ (after the learn uplift deploy makes them live).
This decision (learn-local policy pages, org links to them) is visible in org's history via this issue.
learn-cli (Claude)