Scheduled
5 min read By NT²
Semantic columns, not form widgets
Tech
A password field is not “a secret text box on this screen.” It is a semantic column type the whole vault understands—masking, health, share defaults, and wire shape included.
Tech
Engineering deep dives into the architecture and implementation behind NT² Vault.
48 posts
Scheduled
6 min read By NT²
Slots, not a blank page
Tech
A passport, a bank account, an API key, and a seed phrase are not the same kind of text. A vault that treats them as one blank page will always ask you to remember the structure yourself.
Scheduled
8 min read By NT²
Replica batch under the hood — packet shapes
Tech
Blind sync is easier to trust when you can picture the packet. The edge sees shapes, sizes, and progress—not titles, notes, or a searchable attic of your secrets.
Scheduled
8 min read By NT²
Threat model, 2026: browsers and extensions
Tech
Threat models age with browsers. This 2026 refresh keeps the residual risks named—XSS, unlocked theft, hostile extensions, origin supply chain—and checks which defenses still hold when the client world moves.
Scheduled
9 min read By NT²
Benchmarks from a 10k-item OPFS vault
Tech
A large local vault is not proven by a slogan. It is proven by measuring the paths people actually use—first page after unlock, debounced search, FTS versus filter queries—and by being honest about what those numbers do not mean.
Scheduled
8 min read By NT²
Offline-capable is not sync later if lucky
Tech
Many apps call themselves offline-capable when they mean a read-only cache and a queue that hopes the tower returns. A local-first vault puts full CRUD on the device first. Sync is an optional second path.
Scheduled
8 min read By NT²
XSS steals sessions elsewhere; here keys are non-extractable
Tech
A vault that advertises invincibility is selling theater. NT² names the residual risks—XSS while unlocked, a stolen unlocked device, a hostile extension—and designs so those failures do not also become password oracles or exportable key dumps.
Scheduled
8 min read By NT²
Shared crypto packages get a 100% coverage floor
Tech
Specs bound scope. Security veto owns residual risk. Coverage floors own a narrower job: no uncovered line in the shared packages that seal, wrap, and describe vault facts—because agents will otherwise ship “done” with a hole.
Scheduled
7 min read By NT²
Security veto is a role, not a vibe
Tech
Agents can draft patches and greenlights. They cannot own the decision that a vault still refuses password escrow, extractable keys, or a “helpful” recovery desk. Security veto is a role with authority—not a mood in chat.
Scheduled
7 min read By NT²
Specs before agents write code
Tech
An agent that codes from a vague prompt will invent a product. An agent that codes from a written contract will ship the slice you approved—or stop where the contract ends.