Security
How this site protects what it holds: security and privacy as part of every change, with its threat model, secrets and audits.
How puncoz-packages-docs protects what it holds. Security and privacy are a property of every change, not a pre-deploy event — see ADR-0005.
Living snapshots. Edit in place so each file describes the system as it is right now. No revision tables, no "previously X, now Y" — delete what is no longer true (ADR-0002).
Documents
| File | Answers |
|---|---|
threat-model.mdx | What is worth protecting, from whom, and what stops them |
data-classification.mdx | How sensitive a piece of content or data is, and how it must be handled |
secrets.mdx | Every secret: what it is, where it lives, whether it reaches the browser |
checklist.mdx | The audits, and the gates at which they run |
<feature-slug>.mdx | A feature's own threat surface, when it warrants one |
Template: ../_templates/security.mdx
The rules that matter most
1. Never guess at a security decision. Whether a project is private, who may read it, whether a route is public, what is sent to the search provider — the owner decides, and it is recorded (ADR-0004).
2. Private stays private. Today every page in content/ is published on every
surface: the site, the Markdown routes, llms.txt / llms-full.txt, static.json, share images,
sitemap.xml, structured data and the search index. No private project content goes there until an ADR decides how it is
kept and served (AGENTS.md §6.1).
3. Published is permanent. A page that was served, indexed or crawled cannot be recalled. Treat it as public from that moment, and rotate anything secret it contained.
4. Tool-specific rules arrive with the tool. Algolia is adopted, and its checks are in
checklist.mdx. When a host, analytics, CI or an
authentication provider is adopted, its ADR adds its own entries there. This project makes
no claim about tools it has not adopted.