Preferred path
Use a typed plugin library that understands the target VMAD record family. Reload and compare the result.
Binary fallback
Raw byte replacement is allowed only when all conditions hold:
- the exact target string and owning record are identified;
- the encoding and length prefix are understood;
- every occurrence is classified;
- the transform updates lengths and enclosing record sizes correctly, or the replacement is exactly the same byte length;
- a parser can walk the complete file before and after;
- a byte diff shows no unrelated changes;
- the original remains untouched.
Do not use global bytes.replace on a plugin. Do not rename a script without also shipping the corresponding PSC/PEX and preserving property contracts.
Validation
- Audit plugin structure before the change.
- Extract the target record and VMAD tree.
- Apply the transform to a workspace copy.
- Reparse the complete plugin.
- Compare masters, FormIDs, record sizes, VMAD scripts, properties, and unrelated bytes.
- Compile renamed scripts and run the ship gate.
Evidence standard
Use this hierarchy for version-sensitive facts:
- The active project's
ENVIRONMENT.md,TASK.md, installed framework version, and build files. - Official upstream documentation or source for that exact version.
- Known-good files from the user's installed mod library, read-only.
- Direct inspection of the relevant ESM, ESP, DLL, script, log, or archive.
Do not substitute memory, an old example, or a plausible token. Record the evidence path or URL in VALIDATION.md.
Claude Code execution adapter
- Keep
CLAUDE.mdconcise and use this skill for procedural detail. - Load only the skills needed for the current milestone because invoked skill content remains in context.
- Use high or xhigh effort for risky architecture, plugins, DLLs, and hostile review.
- Before compaction or a usage boundary, persist exact state, commands, uncommitted changes, and remaining validation.
- Treat auto memory as candidate learning, not verified truth, until it passes the memory-promotion protocol.
Skill-specific provider control
Require byte-length invariance or a typed writer; never improvise VMAD offsets.