Documents

These are the working documents. They are drafts: they change, and they are numbered in reading order rather than importance.

• Research Memo — Application-Layer Encryption at the Data-Access Layer Status: Draft 1 · Date: 2026-08-08 · Scope: landscape, prior art, regulatory basis, gap analysis Purpose: establish, with citations, whether a language-agnostic …
• PRD — Fieldseal Fieldseal: a portable specification and reference implementations for transparent field-level encryption-at-rest at the data-access layer. Status: Draft 1 · …
• Fieldseal Core Specification Version: 0.1-draft · Date: 2026-08-08 (rev. 2026-08-22) · Status: Working draft. Not for production use. Not independently reviewed — the Phase 0 cryptographic …
• Compliance Mapping Date: 2026-08-08 · Status: Draft 1 · Verification: clause numbers below were read from primary sources (eCFR, Federal Register full text, the PCI DSS v4.0.1 …
• ORM Adapter Notes Date: 2026-08-08 · Status: Draft 1 · Purpose: the per-ORM engineering detail behind the conformance-level matrix in the spec (§10). Written to be read by …
• Dissemination and Evidence Track Date: 2026-08-08 · Status: Draft 1 Separation of concerns. Nothing in the research memo, the PRD, the specification, or the code should be written for a …
• Verification Log Date: 2026-08-08 · Method: independent re-verification of the 20 highest-risk factual claims against primary sources (eCFR, Federal Register, NIST CSRC, PCI …
• Phase 1 Implementation Plan Date: 2026-08-08 · Status: Draft 1 · Purpose: the engineering plan for Phase 1 (“prove the format,” PRD §8): what gets built, in what order, gated …
• Test Vector Technical Specification Date: 2026-08-08 · Status: Draft 1 · Purpose: the engineering specification for authoring, validating, and consuming the machine-readable test vectors described …
• Core Library Architecture Specification Date: 2026-08-08 · Status: Draft 1 · Purpose: the language-agnostic architecture every core implementation (core/{python,typescript,java,dotnet,go}) follows. …
• Python Core Technical Specification Date: 2026-08-08 · Status: Draft 1 · Purpose: the Python binding of docs/09-core-architecture.md. First implementation built in Phase 1; it also hosts the …
• TypeScript Core Technical Specification Date: 2026-08-08 · Status: Draft 1 · Purpose: the TypeScript/Node binding of docs/09-core-architecture.md. Second Phase 1 implementation; it is also the …
• Django Adapter Technical Specification Date: 2026-08-08 · Status: Draft 1 · Purpose: the engineering design for adapters/django (package fieldseal-django), targeting Django 6.1 / 5.2 LTS. Built …
• Prisma Adapter Technical Specification Date: 2026-08-08 · Status: Draft 1 · Purpose: the engineering design for adapters/prisma (package @fieldseal/prisma), targeting Prisma 7.x. Built on the …
• Conformance & CI Technical Specification Date: 2026-08-08 · Status: Draft 1 · Purpose: how conformance is claimed, proven, and continuously enforced. This is the machinery behind the project’s …
• Operational Tooling Technical Specification Date: 2026-08-08 · Status: Draft 1 · Purpose: engineering design for tools/backfill and tools/leakage-estimator. The backfill tool is PRD requirement AD-6; the …
• Cryptographic Reviewer Brief Date: 2026-08-08 · Revised: 2026-08-22 · Status: Draft 2 — the document sent to prospective reviewers Why this exists. Fieldseal is a draft specification for …
• M2 Implementer Brief — building a second core in isolation Date: 2026-08-22 · Status: Draft 1 · Purpose: the handoff given to whoever builds the second reference core. It exists so that the independence rule (docs/11 …
• M2 Report — the TypeScript core, built in isolation Date: 2026-08-22 · Status: Draft 1 · Purpose: the deliverable docs/17-m2-implementer-brief.md §5 asks for: the isolation statement, the divergence list …
• What Encrypted Search Costs — a plain-language guide Date: 2026-08-31 · Status: Draft 1 · Purpose: what it costs to search an encrypted field, written for the people who decide whether to adopt this specification …
• The Patient-Directory Demonstration — two stacks, one Postgres table Date: 2026-09-09 · Status: Draft 1 · Purpose: design and reasoning for the Phase 1 demonstration application (docs/07 §2, WS-G): a Django frontend and a Prisma …
• The Write Path — one encrypted field, from save() to the database Date: 2026-09-19 · Status: Draft 1 · Purpose: a picture of what the specification requires to happen when an application writes one encrypted, indexed field, …
• The Read Path — one encrypted field, from the row to a value Date: 2026-09-19 · Status: Draft 1 · Purpose: a picture of what the specification requires to happen when an application reads one encrypted field, drawn from …
• The Equality Query — finding a row by an encrypted value Date: 2026-09-19 · Status: Draft 1 · Purpose: a picture of what the specification requires to happen when an application looks a row up by the value of an …
• Keys — the hierarchy, and the life of a key version Date: 2026-09-19 · Status: Draft 1 · Purpose: two pictures of the specification’s key model: which keys exist and how each is made from the one above it, …
• Phase 1 Retrospective Date: 2026-09-22 · Status: Draft 1, decision made (§10) · Purpose: the third clause of milestone M5’s exit test in docs/07-implementation-plan.md §3: …
• Phase 2 Implementation Plan Date: 2026-09-22 · Status: Draft 1; four of the five §5 decisions made by the maintainer on 2026-09-22, the .NET framework open · Purpose: the engineering plan …
• Architecture Decision Records Decision records for choices that gate implementation. ADRs here do not replace the spec-change process (CONTRIBUTING.md: issue → citation → breakage statement …
• Spec-gap issue drafts (G1–G26) Date: 2026-08-08 · Status: all thirteen posted to the GitHub tracker on 2026-08-08; issue numbers align with gap numbers (Gn = issue #n) for G1–G13 only — G14, …