hexaemeron

Work a failure you already have down to its cause, then guard it: stop the line, preserve the evidence, reproduce, localise, reduce to a minimal case, fix the cause rather than the symptom, and leave behind a test that fails without the fix. Use when a test fails, a build breaks, a fuzz campaign returns a counterexample, behaviour stops matching expectations, or something that worked has stopped. Do not use it to hunt for findings nobody has observed yet, which belongs to solidity-auditor and x-ray, and do not use it to speed up something that already works, which belongs to metron.

Decide what a step must emit so its behaviour is visible afterwards: the on-call questions first, then structured events, bounded metrics, correlation across the whole path, and alerts on what someone actually feels. Use when adding logging, metrics, tracing or alerting, when shipping anything that runs unattended, or when an incident could not be explained from what was recorded. Do not use it to instrument a failure you are chasing right now, which belongs to elenchus, and do not use it to measure something slow, which belongs to metron.

Run the one-shot delivery loop: study, runbook, then per-step implement/audit/prose/push until a working prototype exists. Use only when a Wildcat contributor explicitly asks to start, run, resume, or report a Hexaemeron or Fiat delivery, including /hexaemeron:fiat forms. Do not infer activation from a similar task.

Generate Echidna/Medusa-compatible Solidity fuzz suites from Foundry or Hardhat projects. Trigger on "fizz", "generate fuzz suite", "build fuzz harness", "stateful fuzzing", "fuzzing harness", "property testing", and "invariant suite".

Decide what gets written down and where it lives: the decision record behind a choice that would be expensive to reverse, the comment that explains why rather than what, the runbook an alert points at, and the README somebody starts from. Use when a decision is made, an interface changes, an alert needs somewhere to point, or the same explanation has been given twice. Do not use it to lint or rewrite prose, which belong to imprimatur and vulgate, and do not use it to decide what a study must contain, which belongs to protasis.

Check prose that ships for banned AI writing tells, technical terms used without evidence, and repeated structural formulae that survive a wordlist. Use while drafting, editing, or reviewing public prose, or when the user names a term to ban. This is the diagnostic gate; Vulgate performs a content-preserving rewrite.

Rank the held Next Fiat jobs across explicitly in-scope, non-mature skills, select the most worthwhile job out of 100, set one durable goal or loop, run that job through Fiat, then repeat until no eligible frontier remains. Use only when the user explicitly asks for Kronos, for a repeated ranked Fiat frontier loop, or for the ranking on its own without running anything. Do not use it for one ordinary Fiat delivery.

Change performance only against a recorded measurement: baseline first, one change at a time, re-measure the same way, then keep it or revert it. Use when something is slow, when a budget exists, when a change might have cost time, or when a profile is needed before touching code. Do not use it for Solidity gas, which belongs to hermes and its Foundry loop, and do not use it for something that is broken rather than slow, which belongs to elenchus.

Harden the off-chain surface: the Python that harvests, indexes, replays and releases, the commands it shells out to, the URLs it fetches, the secrets it holds, the dependencies it pulls, and the model output it acts on. Use when a step accepts data from outside the process, runs a subprocess, fetches a URL, reads a credential, adds a dependency, or feeds an agent. Do not use it to review Solidity, which belongs to solidity-auditor and x-ray, and do not use it to diagnose a failure that has already happened, which belongs to elenchus.

Hold a Fiat study and runbook to a content contract before any code is written: stated assumptions, testable success criteria, a chosen design with its trade named, the five discipline questions answered before any build, and steps that are discrete, green at both ends, sized for the audit loop and explicit about the gates they incur. Use when a topic is about to enter the study or runbook phase, when a requirement arrives vague or bundles several capabilities, or when deciding whether a runbook is ready to build from. Do not use it to run the controller or write a receipt, which belong to fiat, and do not use it to record a decision after the fact, which belongs to hypomnema.

Security audit of Solidity code while you develop. Trigger on "audit", "check this contract", "review for security". Modes - default (full repo) or a specific filename.

Rewrite AI-assisted or generic text into a plain human register while keeping every fact, number, commitment, caveat, link, and intended meaning fixed. Use for messages, documents, announcements, and public repository prose after diagnostic wording checks.

Generates an x-ray.md pre-audit report covering overview, enhanced threat model (protocol-type profiling, git-weighted attack surfaces, temporal risk analysis, composability dependency mapping), invariants, integrations, docs quality, test analysis, and developer/git history. Triggers on 'x-ray', 'audit readiness', 'readiness report', 'pre-audit report', 'prep this protocol', 'protocol prep', 'summarize this protocol'.