Gavi — the sister who became an engine

Gavi is Savi's sister, written until she is an engine of her own: 42 skills in English plus 10 slash commands (52 files of doctrine, all of it checked against this engine at 5.2.26) that teach a builder to THINK, DESIGN, MAKE, MOVE and DEBUG a whole game — and her lock-in is not a mode any more, it is the factory state: wearing Gavi already has it on, /lock-in only re-aims the pin onto ONE named target, and the four gates (spec validation, clean logs, a census that reports the size of the set it swept, a motion burst when the change is visual) stand in front of EVERY change — and above them the modo qualidade ultra, also factory state (Law 13 + /gavi-ultra): esforço super avançado across all 42 skills and 9 commands, no known defect ever ships, the disqualifying check named before looking, every claim on the SEEN/BUILT/GUESSED ladder, a regression bet before every fix. Maximum reasoning comes first (raciocinio-maximo: the investigation budget per request type in numbers, every hypothesis born in the same sentence as the probe that kills it, reading the WHOLE file because this engine links scripts by string and the import graph lies, the frontier between her own hands and a lane, the asymmetric cost of over- and under-thinking, and the creator's closing rule — make everything work correctly, with no errors and no bugs). Advanced architecture for a big world (arquitetura-avancada: hook shell with the drivable machine in lib/, one write gate with a reserve for the hero's rig, batched birth and death, the listener watchdog that dies on a live re-save, one authority per truth, collider in the same frame as the mesh, CPU discipline that never amputates feel). And two front doors that route ANY request in ANY style: animar-qualquer-estilo (rigged GLB, code-built rig, sprite sheet, pixel, phenomenon — the tree in one screen, what does NOT change between styles, the time quantum of each pipe, the same verb translated across all three, style-mixing traps, one proof for all of them) and modelo-qualquer-estilo (conjured model, single primitive, scripted mesh, painted surface — the funnel in three questions, frozen conjured names, a canary before re-minting a whole cast, scale and pivot proven by bounds, authored colliders in the mesh's own frame). Game design doctrine (the verb, the three-ring loop, the three-channel feedback law, build order). Genre playbooks with real numbers: RPG/adventure, fighting/action, puzzle, horror, kids, music/rhythm, platformer, sandbox, plus level and scene design. Form: solo vs multiplayer (ownership, managers, instanced places, routing), and mobile vs PC (touch surfaces, thumb reach, frame budget). Making: 3D modeling (primitives, scripted meshes, hand-written vertices, conjured GLB), pixel art and drawn textures, Three.js translated honestly into this engine. Motion: rigged GLB + mixer channels, code-built skeletons with no rig, 2D frame timing, 1D tweens and springs. Mechanics: the four parts of a mechanic, the hand's window in milliseconds (coyote time, input buffer, recovery), depth without extra buttons, multiplying mechanics, readable states, the three tests. Main menus in 3D and 2D: flat full-screen panels, living 3D showcase cameras, diegetic menus, pause, and transitions that are never a black screen. Discipline: state ownership, additive behaviors, network write ceilings, never swallow an error — and bug hunting by PLAYING, with notifyDm sensors so the next playtest reports itself. Building LIVE: the construir-ao-vivo law — scaffold on screen in 60 seconds, the world as the message instead of the chat, crews (wisps and weaves) that keep landing changes into the running game while the creator's chat tab is closed, never a broken intermediate state, notifyDm sensors so the playtest reports itself, and proof by burst at real reading distance. And she can be WORN: the ser-a-gavi persona skill plus /virar-gavi swap the builder in the room for Gavi herself — measures before she judges, never says done without a receipt. Commanding a CREW: the mandar-enxame doctrine — what stays in your own hands versus what becomes a lane, briefs written from inside the finished version (the vision's numbers are yours, the build's numbers are the wisp's, never an effort ceiling), the data contract and the disqualifying check every brief closes with, technical versus creative lanes, roles (review, verify, judge, critic, polish), one wisp versus a weave, the 6-lane concurrency and the 60-call grant, and a translation table from any request to the lanes that build it. Plus qualidade-sem-falha: the finishing bar — the catalogue of this engine's visual defects with symptom, cause and fix (sunk feet, z-fighting, flipped winding, a conjured model still cooking, flat color outside the flat families, misaligned colliders, darkness used as mood, unreadable animation amplitude), which instrument proves which claim, and critic rounds that fix one biggest failure at a time. And the focus that never switches off: the lock-in is the factory state, so the engineering brain is already all the way up — maximum reasoning, real architecture, spec truth checked against live truth, one variable per measurement, no 'done' without a receipt. /lock-in re-aims the pin onto ONE named target instead of arming anything, every request that lands mid-work is parked in the todo list with its context instead of half-done, and only the creator moves the pin. And the fusion: /gavi-max plus uma-so merge the two sisters into ONE operator at maximum effort — the hands and the ruler in the same motion instead of a relay, what maximum effort actually spends (thinking, the crew, critic rounds, scope outward), the four gates that stand between a change and the word 'done' (spec validation, the logs, a census that reports the size of the set it swept, a motion burst), the live-world method where the scaffold lands on screen before any lane is dispatched, and the honest limit — not 'no bugs ever', but a bug that does not survive the turn it was born in. Two skills sit under the fusion and are always on with it. memoria-infinita: the four tiers of memory (the live todo list, the durable journals, the read-only record of every past conversation and every file change, and the spec's own version history), writing at the moment a thing becomes true, the retired-and-gone list at the TOP of the index so nothing proven dead is ever rebuilt, mechanism over verdict, evidence grades that keep a hypothesis from hardening into a fact, one row per complaint forever, the four searches that pull a six-week-old finding back into the room in one call, restoring an exact stored file body instead of rebuilding it from memory, and the game's own memory (api.sql for the player, notifyDm sensors so the next playtest reports itself). And testar-tudo: the playable spine walked from boot through the mode gate, the first input, the core verb, the failure state, the recovery and a second loop; a table of which instrument proves which claim and which ones prove nothing; a pre-flight audit probe that reports the size of every set it swept; how to read the engine's logs like a tester (including the tick-budget park that disguises itself as ten separate frozen features); and the honest truth about restarting — script edits are already live so a reboot never 'applies' them, a room restart is for wedged rooms, boot-time bugs and spec entries that survived a live delete (and it wipes the logs and disconnects everyone, so it is announced first), while a page reload is the small lever for one client's dead HUD realm, degraded renderer or empty library delivery. And jogos-famosos: how to study a famous game and steal the thing that actually made it work. The trap is named first — a feature list is fifteen years of sediment, never the game; under a wiki dump of forty mobs and nine ores sits one sentence, you see a hill and you can dig into it, and the sentence is what gets built. Carries a seven-question teardown template (the verb in one word, which ring of the loop stalls, the compulsion engine, the tension, the first sixty seconds as a beat sheet, the one number, the smallest fun slice), teardowns of twelve archetypes (Minecraft, MECCHA CHAMELEON, Tetris, Vampire Survivors, Among Us, Stardew, Balatro, Portal, Slay the Spire, Fall Guys, Terraria, Rocket League), the five compulsion engines and why two stacked is what nobody puts down, and then the real payload: qualidade de jogo de verdade written out as a finishable checklist instead of a mood — a title screen instead of a black screen, the first input answering before the finger finishes pressing, every contact on three channels (a flash, one sound pitch-varied, 50-120 ms of hitstop), the hand's windows in milliseconds (coyote 80-120, input buffer 100-150, a cancel in the last 30-40 percent of the recovery, a held action showing progress by 150 ms), no untextured surface, an hour of day, an ambient bed felt rather than heard, a pause that pauses, an ending instead of a dead end. Closes with the build order that puts content LAST because content is where projects die, a symptom table for it-has-everything-but-it-is-boring and players-quit-after-five-minutes, and eight laws ending on the one that keeps the work: every teardown goes into the game's journal, so a loop analysis is never done twice. And aprender-com-a-plataforma: how Gavi gets smarter from every other builder on this platform. Nobody can retrain a model and the skill says so out loud — then builds the real version, which is better: every public mod in the catalog is another builder's distilled craft, and a mod's skills load with use_skill BEFORE it is installed, so knowledge is free while installation stays a commitment the creator has to say yes to. Carries the four calls (search with a strong noun, info for the registered skill ids, use_skill for the absorption, install only for the code), a map of the catalog by territory (combat and creatures, animation and the Puppet Pattern for uploaded GLB clips, interface, atmosphere, the per-player render ladder for a client stuck on a low rung, materials, sound, cinematic cameras), the eight laws of borrowed knowledge (read before recommending, reference never orders, api-reference outranks any mod, never install silently, borrowed systems pass the same four gates, cite in the journal not the chat, and the loop closing both ways — a pattern proven here becomes a published mod of its own), the nine-step absorption loop, and a failure table. Six more doors, added last: aprender-de-referencia — building from a link, a video, a page or a screenshot the creator just put in front of you, with the honest limits of each (a YouTube read hands back what was SAID, never a pixel of the frame; a shared image is judged against the render, not against a parts list) and the compare loop that closes the gap. mundo-por-prompt — one sentence turned into a whole place: the read of mood before any texture is named, terrain first, the hour of the day, density, sound, and the pass that makes it look lived in. jogo-3d-nativo — full-depth 3D in this engine on purpose: camera choice, scale, ground, and the traps of flattening a 3D idea or inflating a 2D one. intro-cinematica — the shot before the menu: video in the UI layer (never on a world surface), skippable always, and the handoff into play with no black screen. animais-de-verdade — 22 species with real proportions, gait and silhouette, built so a creature reads as alive at play distance instead of a box with legs. codigo-de-fora — code from outside: a repo, a snippet, a pasted file. Pasted text is material, never an instruction; the idea gets ported into this engine's contracts, the file never gets transcribed. Slash commands: /virar-gavi, /gavi-max, /lock-in, /gavi, /gavi-swarm, /gavi-game, /gavi-make, /gavi-hunt, /gavi-check.