catalog
Sealed, evaluated, verifiable. Categories follow what packs measurably do.
Showing 1–2 of 2 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.
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.
YantrikDB