runtime-behavior-probe

To validate runtime behavior beyond static checks, you can plan and execute runtime probes using a validation matrix. This approach investigates edge cases, drift, and failure modes in local or live integrations by running temporary probe scripts.

A validation matrix is a structured plan used to coordinate runtime probes and verify real behavior. It helps manage temporary probe scripts and ensures systematic coverage of edge cases, drift, and failure modes before generating findings-first reports.

To safely execute runtime probes in a live environment, use gates and state controls to minimize risk before running any costly probes. A plan-first approach with a validation matrix and pilot execution helps manage and contain potential failure modes.

Yes, runtime probes apply to local development, integration tests, and live usage scenarios. They coordinate and verify real runtime behavior to investigate edge cases, drift, or failure modes that may appear across these different environments.

The best way to report runtime probe findings is by generating a findings-first report. After planning a focused probe, assembling a validation matrix, and executing a pilot, you summarize the results to guide decisions.

Yes, runtime probes require a self-contained directory with a SKILL.md file containing the name and description. You can optionally include scripts, references, and assets to support the structured probe execution protocol.