Bring the Kyanite repo, MCP server, media pipeline, localization pass, or diagnostic you want running. Kyanite helps install it, adapt it to your setup, document the tradeoffs, and leave you with commands you can use again.
Open the repo, inspect the artifact, and pick the Kyanite build closest to the blocker you want running in your environment.
Use the gallery as a map: install one of the tools, read the build context, or start with a smaller asset before a scoped implementation conversation.
For builders who want Kinocut, Epoch, DialectOS, OpenGlaze, repo diagnostics, or another Kyanite build installed, adapted, and handed off cleanly.
Read the notes behind the project: what the tool does, where it is useful, what still needs care, and how the implementation surface should behave.
Use templates, workflows, and operator assets when you do not need a full implementation pass yet but want fewer blank-page starts.
Build logs and implementation notes show where a tool works, where it is rough, and what it takes to use it well.
The title is new; the work is old. Twelve years of enterprise deployments plus public, measured AI work. The honest path, artifacts included.
Evals are the FDE skill nobody lists: my 495-trial public benchmarkThe market says it cannot find people who can build AI evals. The skill is learnable and I published mine: 495 trials, certified floors, sabotage cell, open source.
Forward deployed vs solutions engineer vs implementation vs customer engineer: the title decoderFour titles, one job family, different coding bars. A decoder that reads any posting and tells you what you are actually signing up for.
Tool you need running, repo you need installed, video pipeline you need usable, Spanish QA you need trusted, diagnostic you need explained, or a build you need handed off. If it connects to Kyanite's tools and practice, bring the blocker.
