Skip to content

protective-computing/protective-computing.github.io

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

50 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

protective-computing.github.io

Official landing page for the Protective Computing discipline — systems design under conditions of human vulnerability.

Primary citations

Local Preview

Open index.html directly in a browser for a quick check, or run a minimal static server:

cd protective-computing.github.io
python -m http.server 8080

Then browse http://localhost:8080.

Docs Map

  • Audit this site: /docs/audit-this-site.html
  • Getting started: /docs/getting-started.html
  • Specification (v1.0): /docs/spec/v1.0.html
  • Principles index folder: /docs/principles/
  • Formal threat models: /THREAT_MODELS.md
  • Implementation patterns: /IMPLEMENTATION_PATTERNS.md
  • Compliance & audit matrix: /COMPLIANCE_AUDIT_MATRIX.md
  • Audit evidence index: /AUDIT_EVIDENCE.md
  • Independent review checklist: /INDEPENDENT_REVIEW_CHECKLIST.md
  • v1.1 planning issue templates: /V1_1_ISSUE_TEMPLATES.md
  • Reference implementation: /docs/reference-implementation/paintracker-mapping.html
  • Independent review: /docs/independent-review.html

Contributing

Use GitHub Issues for suggestions, critiques, and corrections.

Suggested labels:

  • spec-bug
  • spec-gap
  • spec-disagreement

Release Discipline

  • v1.x is stable and backward-compatible for compliance claims.
  • v1.1+ incorporates review-driven clarifications and implementation guidance.
  • v2.0 is reserved for paradigm-level changes (new principles or fundamental threat-model expansion).
  • Frozen baseline: v1.0.0 tag marks the stable reference state for reproducible audits; subsequent hardening/docs updates are tracked as v1.1+ guidance.

Metadata Audit

Run deterministic metadata + sitemap/robots integrity checks:

powershell -ExecutionPolicy Bypass -File scripts/metadata-audit.ps1

Audit artifacts are written to scripts/audit-output/. The script exits with a non-zero status code when any metadata, sitemap, or robots gate fails.

Policy: all HTML pages MUST include canonical + OG/Twitter baseline tags.

  • Stage 3 (verification hardness): CI fails if WEAK_VERIFICATION_COUNT > 0 (run: powershell -ExecutionPolicy Bypass -File scripts/semantic-ledger-audit.ps1 -GateStage3).

About

Official landing page for the Protective Computing discipline — systems design under conditions of human vulnerability.

Resources

License

Stars

Watchers

Forks

Packages

 
 
 

Contributors