The public engineering record for ShieldFive. Posts land as milestones ship — cryptography migrations, post-quantum work, security reviews, audits. Written for developers and security researchers, not for marketing.
· Cho García
Notice under section 15 of the privacy policy. From 30 October 2026 a new account records the page its visit started on, the referring host name and our own campaign tags, so we can tell which channels lead to accounts that use and pay for the service. It stays on the account, goes to no analytics provider, and is deleted with the account.
· Cho García
An assistant can now list, search, organize, upload to and move files into a ShieldFive vault through a local MCP server, with a grant the server can check but not open. The post covers the key wrap, scopes, revocation, the verified move-in, one upload bug the first smoke test caught, and the limits: the model provider still sees what the assistant reads.
· Cho García
The library reached 1.0.0 after a ten-week release candidate. No wire format or function changed from rc.6; the release makes the API stable under semantic versioning and keeps the v1 format frozen. Audit status is unchanged: no paid third-party audit, and 1.0.0 does not claim one.
· Cho García
In May 2026 a periodic adversarial pass audited the running product against its own source code, in five parallel deep-dives, and surfaced sixteen must-fix items that were closed over the following weeks. Only a handful were genuine zero-knowledge boundary issues; the rest were truthful-copy, legal, and ops gaps.
· Cho García
Phase 3 made ML-KEM-1024 plus XChaCha20-Poly1305 the default cipher suite for new uploads — one byte changes on disk, no file is rewritten, and the Suite 0x01 dispatch path stays untouched. Rollback is a single env-var flip back to the previous default, not re-encryption.
· Cho García
Phase 2 introduced the v1 self-describing wire format on disk for new uploads, through a five-stage rollout with mandatory bake windows. The staged design caught a memory bug in code review, a base-branch misroute in PR review, and two v0-shape assumptions in cross-deployment testing. The artifact most worth keeping is a cross-layer audit method that generalizes to Phase 3.
· Cho García
ShieldFive's cryptography moved from inline production code into a standalone open-source library, with the production deployment re-importing the library via a byte-identical v0 compatibility bridge. Wire format unchanged. Database unchanged. No user-visible change.