Skip to main content
Read each operation’s literal instructions. Click a data name to see its description, type, producer, consumers, and declared changes. Read checks separately from actions. A run belongs to one exact version. It records each invocation’s inputs, outputs, checks, changes, and failure. An unchecked operation is marked unchecked. A check can pass, fail, or lack enough evidence. Use method logs RUN_ID to give your coding agent the saved evidence. Ask it to identify the smallest incorrect instruction, missing input, or wrong criterion. Edit the method, validate it, and save a version with a reason that names the defect. For a useful comparison, keep the input data and expected result fixed. Compare actual outputs and false passes, not just how many model checks passed. Run the edited version when you want new execution evidence.