Individual skill
peridigm-evidence-fracture
Clarify Peridigm simulation requirements, preserve confirmed physical intent, call evidence-producing CLI or MCP tools, and interpret actual solver results. Executable profiles cover two-point elastic verification and a synthetic precracked tensile damage demonstration; other physics require new qualification.
Skill/peridigm/peridigm-evidence-fracture/SKILL.md
Source commit 56705e07ce6e99f0d5a0d0c7b5e28b6b2c0bc973
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 3, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,301
- Repository last updated
- Oct 27, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 3,435 bytesmetadata.jsonasset · 740 bytesreferences/capabilities.mddoc · 1,922 bytesreferences/fracture.mddoc · 4,847 bytesreferences/validation.mddoc · 2,333 bytes
Read excerpt
# Peridigm evidence workflow
The AI client supplies language understanding. The deterministic core supplies context state, compilation, execution and checks; neither silently invokes another model nor treats a successful process as physical validation.
## Clarify and confirm
1. Call `peridigm_doctor` and `peridigm_templates` before promising a supported simulation.
2. Call `peridigm_start_context(request, actor)` with the actual request. Retain its `run_id`.
3. Ask the returned questions, grouping at most three important questions per turn. Distinguish missing facts from facts inferable from an explicitly accepted template. Do not invent steel, concrete, damage or contact parameters.
4. Pass the actual answer to `peridigm_answer_context`. Selecting `compression-two-point-v1` or `notched-tension-damage-v1` returns its complete synthetic parameters and confirmation hash. Record whether confirmation comes from the human or an AI operator acting within explicit delegation; never label a scripted test or operator answer as a human response.
5. Submit the returned `confirm_spec_sha256` only after review. If the user changes the problem, start a new specification. Preserve the old one.
For CLI use `pd-agent start --json '{"request":"..."}'`, then `answer`, `validate`, `submit`, `status`, `log`, `repair`, `collect`, and `report`. CLI and MCP share `core.py`. The project-local launcher sets the machine config; do not embed server paths or credentials in reusable instructions.
