catalog
Sealed, evaluated, verifiable. Categories follow what packs measurably do.
Showing 1–10 of 10 packs
The YantrikDB pack API: sealing, signing, mounting, installing and trusting knowledge packs from Python — an API surface that did not exist before 2026-07-28.
How the YantrikDB engine actually behaves: retrieval pipeline, scoring constants, write gates, deletion semantics, and pack internals. Grounded in the source at schema v38.
Early Modern English verse craft: the grammar, vocabulary and rhetorical devices of Shakespearean writing, as enforceable rules plus retrievable exemplars.
Einstein's working method as procedure: thought experiments, invariance-first reasoning, operational definitions and limiting cases — with his classic gedankenexperiments as worked examples.
PHP 8 as it is actually written now: enums, readonly, constructor promotion, property hooks and match; the comparison and array semantics that changed under you; and the security defaults — PDO emulation, unserialize, escaping, randomness, password hashing — that decide whether the application is exploitable.
Java as it is written on a current LTS, not as it was written in 2014. Records, sealed types and pattern matching; virtual threads and what still pins them; the concurrency and equality contracts that fail silently; java.time, BigDecimal and the numeric traps; and the JDK APIs that are insecure by default until you configure them.
Writing C that does not have a CVE in it. Memory safety, the undefined behaviour a modern optimiser will exploit, the standard-library functions whose signatures lie about what they do, integer promotion and overflow, and the build flags and sanitizers that catch what review misses.
WordPress plugin and theme engineering: the hook system and load order, WP_Query and the options API, REST routes and blocks, WooCommerce data stores, multisite — and the security discipline (sanitize in, escape out, prepare every query, nonce plus capability) that separates code that runs from code that survives a plugin review.
Operating rules for an agent working against a persistent memory substrate: which call to reach for, how to band importance, and the traps that silently degrade a memory store over time.
React 19 as it is written now: Actions, useActionState, useOptimistic and use(); ref as a plain prop; Server Components and the client boundary — plus the effect, key, closure and context bugs that only surface under StrictMode, reordering or a slow network.
YantrikDB