verify-gr-math
GR/warp verification workflow for CasimirBot: enforce WARP_AGENTS constraints, math-stage reporting, adapter verification, certificate integrity, and training-trace export. Use when editing GR/warp modules, constraint policies, warp viability, math stage registry, or any change that requires the Casimir verification gate.
When & Why to Use This Skill
This Claude skill automates the GR/warp verification workflow for CasimirBot, providing a robust framework for enforcing WARP_AGENTS constraints, math-stage reporting, and certificate integrity. It ensures that all modifications to physics-based modules pass the rigorous Casimir verification gate, maintaining high standards for agent safety and mathematical viability through automated validation and evidence-based reporting.
Use Cases
- Constraint Enforcement: Automatically validate changes to GR/warp modules against strict WARP_AGENTS policies to prevent physical or mathematical regressions.
- Pre-deployment Verification: Execute the Casimir verification gate as a mandatory check for patches to ensure 'physically viable' status and certificate integrity.
- Automated Math Reporting: Generate and refresh math-stage evidence, including unit coverage and stage maturity reports, to maintain a transparent audit trail.
- Traceability & Auditing: Export detailed training-trace logs and certificate hashes to document agent behavior and verify adapter contract compliance.
- Dependency Analysis: Identify affected files within the GR/warp pipelines and resolve stage dependencies to determine the required scope of testing for any given change.
| name | verify-gr-math |
|---|---|
| description | "GR/warp verification workflow for CasimirBot: enforce WARP_AGENTS constraints, math-stage reporting, adapter verification, certificate integrity, and training-trace export. Use when editing GR/warp modules, constraint policies, warp viability, math stage registry, or any change that requires the Casimir verification gate." |
Verify GR Math
Overview
Run the repo guardrails for GR/warp changes (math-stage checks, required tests, adapter verification, and certificate integrity) before claiming viability or completion.
Workflow Decision Tree
- Scope the change
- Identify touched files.
- If any file is in the GR/warp pipelines or listed in
MATH_STATUS.md, run the full workflow. - If unsure, run
npm run math:trace -- <path-or-tag>to resolve stage and dependencies.
- Update math-stage evidence
- Run
npm run math:reportto refreshreports/math-report.jsonandreports/math-report.md. - Run
npm run math:validateto check stage rules and evidence coverage.
- Run required tests (warp/GR features)
- When touching GR/warp features or Stage 3 modules, run the required tests from
WARP_AGENTS.md:- tests/theory-checks.spec.ts
- tests/stress-energy-brick.spec.ts
- tests/york-time.spec.ts
- tests/gr-agent-loop.spec.ts
- tests/gr-agent-loop-baseline.spec.ts
- tests/gr-constraint-gate.spec.ts
- tests/gr-constraint-network.spec.ts
- tests/stress-energy-matter.spec.ts
- Use
npx vitest run <file...>ornpm run test -- <file...>.
- Run Casimir verification gate (required for any patch)
- Run
npm run casimir:verify -- --ci --trace-out artifacts/training-trace.jsonl. - If auth/tenancy is enabled, pass
--tokenand--tenant(checkENABLE_AGI_AUTHandAGI_TENANT_REQUIRED). - Override the adapter endpoint with
--urlorCASIMIR_PUBLIC_BASE_URLif needed.
- Enforce results
- If verdict is FAIL, fix the first failing HARD constraint and re-run until PASS.
- Do not claim "physically viable" unless all HARD constraints pass and certificate status is ADMISSIBLE with integrity OK.
- Capture verdict, firstFail, deltas, and certificate hash in the response.
- If verification cannot run, state that and stop.
Reference Files
WARP_AGENTS.mdfor constraints, required tests, and certificate policy.MATH_STATUS.mdfor stage maturity and allowed claims.MATH_GRAPH.jsonfor dependency stage edges.reports/math-report.jsonfor evidence gaps and unit coverage.docs/ADAPTER-CONTRACT.mdandcli/casimir-verify.tsfor adapter details.