Data sovereignty and zero-state telemetry
Maintained by PointSav Digital Systems. Each revision is content-addressed by its commit hash.
- Track-B documentation wave: security category — 4 R1 infrastructure-exposure redactions (port, bind-address/CORS, threshold count, secret-scanner catalogue), 1 mechanical frontmatter fix
- fix(governance): retract bcsc-disclosure-posture TOPIC + purge naming/describing references — resolves standing conflict with the convention's own §0/Rule 5
- feat(security): close ES-parity gap for the Aug 3 pilot's 12 rewritten TOPIC articles
- feat(security): Index Topic integration test — index_group tags on 13 articles, materialized security-index.md/.es.md with delimited auto-generated blocks; fix(glossary): repair CSV data-integrity bug (2 malformed rows, 1 duplicate), add Display_Form/Styling term-authority columns, delete 187 empty stub bullets, fix dead A-Z anchor nav
- security/: replace 12 articles with fresh-draft-first pilot rewrites against schema-topic.yaml
- Rewrite data-sovereignty-telemetry.md body (EN+ES) to describe real current behavior — no IP masking, flagged as known gap, per operator direction
- Correction: security/data-sovereignty-telemetry.md — real telemetry daemon stores unmasked IPs, contradicting the published GDPR/PIPEDA masking claim (EN+ES)
- fix(frontmatter): short_description band-fit to house style (120-180 chars) — security/
- Phase C A1a: split security/ + ai/ out of architecture/ (23 articles, 46 EN+ES files); category frontmatter fixed; redirects.yaml 301s; new _index.md landings