packs.yantrikdb.com
A pack is a sealed, signed, measured YantrikDB file. Your local model mounts it and gains the knowledge, rules and skills inside — then gives them back, leaving your memory byte-for-byte as it was.
specimen
yantrik/blender-craft@0.1.0
domain knowledge · qwen3.6-27b
An 0.8B model with the same pack also scores 15/20 — a 34× parameter range landing on one number. Size predicts the baseline, not the result.
code against an unseen API
Execution-graded against an API younger than every model tested. Baseline fails at the interpreter, not the grader.
unrelated tasks · attach-harm gate
A pack that wins its category by wrecking everything else fails certification here.
catalog
Every listing is sandbox-evaluated: signature verified, memories scanned, installed rules shown verbatim.
Blender asset craft for a model that has to produce clean, exportable geometry and write bpy scripts that survive a second run. 13 constitution rules plus 24 corpus facts on real-world scale, topology and edge flow where a mesh deforms, modifier order and what must be applied before export, normals and the Blender 4.1 auto-smooth change, UV seams and consistent texel density, material and node hygiene, naming and hierarchy, origins and transforms, glTF versus FBX and what each loses, the axis and unit traps between Blender and game engines, poly and texture budgets, what must never ship inside a .blend, and the bpy patterns that make a script idempotent instead of stacking duplicates. WRITTEN AS FLOORS, NOT ONLY CEILINGS: each do-less rule is paired with a concrete minimum stated first, and prefers a checkable number or setting to an adjective — a rule the consuming model cannot verify it has followed is not a rule. Targets Blender 4.x, and any version-sensitive claim names its version. HONEST LIMITS: the bpy API surface has NOT been executed against a live Blender build, so treat operator and property names as needing a docs check before they go into production code; the pack deliberately describes an operation in prose wherever its exact API name was uncertain rather than guessing one. No measured efficacy yet — unlike web-craft there is no before/after run behind this, so nothing here claims a number. Scope is asset production and scripting; it says nothing about sculpting workflow, simulation, compositing or animation beyond rigging floors.
Design guidance for writing a genuinely good self-contained web page by hand: no build step, no CDN, no webfonts, no remote assets, renders with the network unplugged. 14 constitution rules plus 25 corpus facts covering page ground and card surfaces, an oklch colour system with one accent and separate semantics, type scale with distinct display and body settings, measure, spacing rhythm, section separation, elevation, dark mode as a second design, motion choreography, focus and selection detail, real copy, and the specific default looks that read as machine-made. WRITTEN AS FLOORS, NOT ONLY CEILINGS. The previous version was written the way you brief a human designer, mostly restraint, and a small model applied every prohibition absolutely and produced a stripped page: pure black ground, no card surfaces, hero missing. So every do-less rule here is paired with a concrete minimum stated first, and prefers a checkable number to an adjective. PROVENANCE: authored by qwen/qwen3.8-max against that brief, for consumption by a smaller local model. MEASURED, and the honest limits: on one clean run against qwen3.6:35b-a3b the pack took the same prompt from a generic page to an 18k-character complete one -- oklch used 25 times, card radius present, no pure black. That is N=1, the pack is unsigned, and two of its own floors (focus-visible rings and tabular figures) were NOT adopted in that run. Scope is one hand-written page; it says nothing about frameworks or bundlers and is not a substitute for a designer.
UK statutory pay and tenancy deposit rules as published on gov.uk, for the rates in force from 1 April 2026: National Minimum Wage and National Living Wage by age band, the apprentice rate and the two-part condition that makes it expire, Statutory Sick Pay as the lower of £123.25 a week and 80% of average weekly earnings, and the England and Wales tenancy deposit regime. These are policy values, not derivable ones — a model without them does not reason its way to £12.71, it recites last year's figure with the same confidence. Every value here was read from the gov.uk page that publishes it on 2 August 2026.
The Python 3.13.5 standard library's actual API surface, generated from the interpreter itself: every signature via inspect.signature (correct by construction, never from memory), CPython's own docstring summaries, plus authored recipes for the tasks agents actually do. Aimed at the measured failure mode of local models — invented imports and wrong signatures.
The complete Model Context Protocol specification, revision 2026-07-28 — published after every current model's training data, which is exactly why it matters: this revision removes the initialize handshake and protocol sessions, deprecates Roots, Sampling and Logging, replaces server-initiated requests with Multi Round-Trip Requests (MRTR), and replaces resources/subscribe with subscriptions/listen. A model writing MCP code from memory writes the old protocol. Covers all 31 specification pages and the official extensions: the migration delta first, then tools, resources, prompts, the OAuth authorization framework with Client ID Metadata Documents, both transports, caching, pagination, completion, and the Tasks and Apps extensions.
The Java standard library's actual API surface, disassembled from the local JDK with javap: exact method signatures for the sixty classes agent code touches most — collections, streams, files, HTTP client, time, concurrency — correct by construction, never from memory. Complements yantrik/java-modern (idioms and style) with ground truth aimed at the measured failure mode of local models: invented methods and wrong signatures.
registry
Got a .ydbpack from a mirror, a colleague, a link? Check it against
the registry before mounting. Every build's file hash is recorded permanently.
sha256sum physics.ydbpack curl "https://packs.yantrikdb.com/api/v1/verify?sha256=<hash>"
A known hash returns the pack's identity, its publisher key and its listing. An unknown hash means the file is not what we evaluated — don't mount it.
install
Native — resolves the slug, checks the file against the registry, then installs:
curl -O https://packs.yantrikdb.com/client/yantrik_pack_client.py python yantrik_pack_client.py install <slug>
Manual — any local file, no network:
pip install yantrikdb yantrikdb pack install ./file.ydbpack
If a signature can't be verified, nothing mounts silently — the client names what it couldn't establish and waits for you to confirm.
YantrikDB