A finished Rule now starts private. Catalogs, search, and /rules/{id} stay closed until the person who holds the pen turns on a share link, or the team features the Rule. The public door is a rotating /r/{slug}; turning that link off kills the slug, and turning it on again makes a new one.
Share asks for a community-agreed checkbox before the link turns on. Uploaded files follow the same readers, drop location metadata, and go away with the Rule, the draft, or the account. Deleting an account lists each owned Rule with PDF and RULE.md export first.
Changes
Three visibilities: private (default), shared by link, and public and featured. Lists, sitemap, and indexing only include featured Rules.
Shared-by-link reads go through /r/{slug}, not /rules/{id}. A private Rule 404s like a missing one. /r/… is always noindex.
Share rebuilt: invite by email, people with access (owner, one reader, then “N more people can read it”), invite-only vs anyone with the link, confirm checkbox, copy, turn off. Featured rows show as anyone-with-the-link; the pen-holder cannot set featured.
Named admins (RULE_ADMIN_EMAILS) can open a private Rule. Those reads are logged.
Guest finish stays private and can be claimed after sign-in.
Upload rows follow the Rule’s readers (including a shared-by-link file). New images strip location metadata. Files delete with the Rule, draft, or account.
Delete Account lists owned Rules with PDF and RULE.md, then a confirmation checkbox.
Case-study Share copies the page link instead of opening the privacy modal. The sign-in banner sits below the header so Share stays clickable.
Share and Delete Account are full-viewport sheets below 640px and 546px dialogs from md.
Stories for Share and Delete Account, plus tests for access, slugs, uploads, Share, and account delete.
Screenshots
How to Test
Apply the Prisma migration (npx prisma migrate deploy locally; npm run migrate:smoke for the throwaway check).
Storybook → Components / Modals / Share (Default, then Anyone with the link) and DeleteAccount. Confirm the community-agreed box appears before Turn on link, Copy is disabled until the link is on, and Delete Account lists PDF / RULE.md.
Resize below 640px and at 640+: Share and Delete Account should be a full-viewport sheet, then a 546px dialog.
Finish a Rule while signed in. It should stay off lists. A signed-out window on /rules/{id} should 404.
Open Share, invite someone, switch to Anyone with the link, tick the checkbox, turn the link on. Open /r/{slug} signed out. Copy the link. Turn it off: the old slug 404s. Turn it on again: a new slug works, the old one still 404s.
After migrate, Mutual Aid Colorado, Food Not Bombs Boulder, and Boulder Street Medics should be the featured catalog rows. Other existing Rules stay private.
Upload a community photo on a private Rule: the owner can open /api/uploads/{id}; a stranger cannot. After the share link is on, the file should load for someone using that link.
Profile → Delete account: both owned Rules appear with PDF and RULE.md; Delete account stays disabled until the checkbox is ticked.
On a use-case completed Rule, Share should copy the page URL (no privacy modal).
Optional: set RULE_ADMIN_EMAILS to a signed-in address and open a private Rule you do not own; the read should succeed and log.
Notes
The migration features only those three consented pilot titles. Every other existing Rule stays private.
Featuring a Rule is a team action. The Share control never offers public and featured to the pen-holder.
Turning the link off clears shareSlug. Turning it on again allocates a new slug, so forwarded copies of the old URL stop working.
Guest uploads still use the grant cookie until sign-in claims the files.
RULE_ADMIN_EMAILS is documented in .env.example. Unset means no named-admin bypass.
## Overview
A finished Rule now starts private. Catalogs, search, and `/rules/{id}` stay closed until the person who holds the pen turns on a share link, or the team features the Rule. The public door is a rotating `/r/{slug}`; turning that link off kills the slug, and turning it on again makes a new one.
Share asks for a community-agreed checkbox before the link turns on. Uploaded files follow the same readers, drop location metadata, and go away with the Rule, the draft, or the account. Deleting an account lists each owned Rule with PDF and RULE.md export first.
## Changes
- Three visibilities: **private** (default), **shared by link**, and **public and featured**. Lists, sitemap, and indexing only include featured Rules.
- Shared-by-link reads go through `/r/{slug}`, not `/rules/{id}`. A private Rule 404s like a missing one. `/r/…` is always `noindex`.
- Share rebuilt: invite by email, people with access (owner, one reader, then “N more people can read it”), invite-only vs anyone with the link, confirm checkbox, copy, turn off. Featured rows show as anyone-with-the-link; the pen-holder cannot set featured.
- Named admins (`RULE_ADMIN_EMAILS`) can open a private Rule. Those reads are logged.
- Guest finish stays private and can be claimed after sign-in.
- `Upload` rows follow the Rule’s readers (including a shared-by-link file). New images strip location metadata. Files delete with the Rule, draft, or account.
- Delete Account lists owned Rules with PDF and RULE.md, then a confirmation checkbox.
- Case-study Share copies the page link instead of opening the privacy modal. The sign-in banner sits below the header so Share stays clickable.
- Share and Delete Account are full-viewport sheets below 640px and 546px dialogs from `md`.
- Stories for Share and Delete Account, plus tests for access, slugs, uploads, Share, and account delete.
## Screenshots

## How to Test
1. Apply the Prisma migration (`npx prisma migrate deploy` locally; `npm run migrate:smoke` for the throwaway check).
2. Storybook → **Components / Modals / Share** (Default, then Anyone with the link) and **DeleteAccount**. Confirm the community-agreed box appears before Turn on link, Copy is disabled until the link is on, and Delete Account lists PDF / RULE.md.
3. Resize below 640px and at 640+: Share and Delete Account should be a full-viewport sheet, then a 546px dialog.
4. Finish a Rule while signed in. It should stay off lists. A signed-out window on `/rules/{id}` should 404.
5. Open Share, invite someone, switch to Anyone with the link, tick the checkbox, turn the link on. Open `/r/{slug}` signed out. Copy the link. Turn it off: the old slug 404s. Turn it on again: a new slug works, the old one still 404s.
6. After migrate, Mutual Aid Colorado, Food Not Bombs Boulder, and Boulder Street Medics should be the featured catalog rows. Other existing Rules stay private.
7. Upload a community photo on a private Rule: the owner can open `/api/uploads/{id}`; a stranger cannot. After the share link is on, the file should load for someone using that link.
8. Profile → Delete account: both owned Rules appear with PDF and RULE.md; Delete account stays disabled until the checkbox is ticked.
9. On a use-case completed Rule, Share should copy the page URL (no privacy modal).
10. Optional: set `RULE_ADMIN_EMAILS` to a signed-in address and open a private Rule you do not own; the read should succeed and log.
## Notes
- The migration features only those three consented pilot titles. Every other existing Rule stays private.
- Featuring a Rule is a team action. The Share control never offers public and featured to the pen-holder.
- Turning the link off clears `shareSlug`. Turning it on again allocates a new slug, so forwarded copies of the old URL stop working.
- Guest uploads still use the grant cookie until sign-in claims the files.
- `RULE_ADMIN_EMAILS` is documented in `.env.example`. Unset means no named-admin bypass.
New Rules stay off lists until the person who holds the pen turns on a share link, or the team features one. Uploaded files are readable only by those readers, stripped of location metadata, and deleted with the Rule, draft, or account.
Share asks the person who holds the pen to confirm their community agreed before a link turns on, and deleting an account lists each owned Rule with PDF and RULE.md export. Case-study Share copies the page link instead of opening the privacy modal, and the sign-in banner stays below the header so Share remains clickable.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Overview
A finished Rule now starts private. Catalogs, search, and
/rules/{id}stay closed until the person who holds the pen turns on a share link, or the team features the Rule. The public door is a rotating/r/{slug}; turning that link off kills the slug, and turning it on again makes a new one.Share asks for a community-agreed checkbox before the link turns on. Uploaded files follow the same readers, drop location metadata, and go away with the Rule, the draft, or the account. Deleting an account lists each owned Rule with PDF and RULE.md export first.
Changes
/r/{slug}, not/rules/{id}. A private Rule 404s like a missing one./r/…is alwaysnoindex.RULE_ADMIN_EMAILS) can open a private Rule. Those reads are logged.Uploadrows follow the Rule’s readers (including a shared-by-link file). New images strip location metadata. Files delete with the Rule, draft, or account.md.Screenshots
How to Test
npx prisma migrate deploylocally;npm run migrate:smokefor the throwaway check)./rules/{id}should 404./r/{slug}signed out. Copy the link. Turn it off: the old slug 404s. Turn it on again: a new slug works, the old one still 404s./api/uploads/{id}; a stranger cannot. After the share link is on, the file should load for someone using that link.RULE_ADMIN_EMAILSto a signed-in address and open a private Rule you do not own; the read should succeed and log.Notes
shareSlug. Turning it on again allocates a new slug, so forwarded copies of the old URL stop working.RULE_ADMIN_EMAILSis documented in.env.example. Unset means no named-admin bypass.