Section
Reference
Canonical policies, reference sheets, migration matrices, and source-of-truth documentation.
Start here
Use this section when you need exact policy, source-of-truth fields, or implementation mapping rather than narrative explanation.
Featured document Mutant Language Reference This document is the practical reference for Mutant language features, reserved keywords, and builtins.Reading path
Curated · top deep dives
Everything else in reference
Modules A Mutant program can be more than one file. import loads another .mut file, binds it to a namespace, and links it into the same program. Execution Modes Mutant has three execution modes and one modifier. This document is the definitive statement of what each one changes; every row below is traced to the code that implements it. Mutant limits reference This document is generated by go run ./cmd/gendocs from the source tree. Do not edit it by hand; edit the constant's doc comment and regenerate. Graph Database The db builtins embed a property graph database in the mutant runtime for modeling entities and the relationships between them: people and documents in a knowledge graph, or processes, files, and… Secure Networking & Traffic Interception Mutant ships a networking toolkit in its standard library so that tools such as TLS clients/servers and mitmproxy-style interception proxies can be written entirely in Mutant source. Structured Data: The Formats Evidence Arrives In Every fallible builtin here follows the language convention of returning (result, err); destructure with let value, err = ... and check err before touching value. Runtime Integration: Embedding Lua Mutant can embed and run Lua scripts from a string, a file, or a remote HTTP endpoint. Detection rules — Sigma Sigma is the portable format for log detections: a rule is a YAML file naming the fields to look at and the condition that has to hold, and a backend compiles it into whatever the SIEM of the day… Interchange schemas Mutant parses fourteen kinds of artifact and each parser hands back its own shape, because each artifact is its own shape: an $MFT record carries eight timestamps, a Prefetch file carries a list of…