| name | vams-research |
| description | Map academic papers, research ideas, protocol mechanisms, and mathematical designs into VAMS implementation reality. Use when evaluating SIRA, HORMA, HIPIF, EvoMem, ProPlay, CHC cognitive scoring, AutoSkill, DBOS, DA sampling, TEE/ZK trust, token economics, or any research-to-code proposal for VAMS. |
VAMS Research
Use this skill to convert research into executable engineering decisions.
Workflow
- Identify the paper, claim, or proposed mechanism.
- If external or current, verify the source before relying on it.
- Read relevant VAMS docs and code paths.
- Use
references/research-map.md to map concepts to subsystems.
- Separate implemented, partial, stubbed, and aspirational pieces.
- Express formulas in LaTeX and identify parameters.
- Define tests, metrics, and failure modes before recommending implementation.
Output Shape
- Research Claim: precise mechanism and source.
- VAMS Mapping: files, modules, and current maturity.
- Math/Protocol Model: equations, variables, thresholds.
- Implementation Plan: narrow steps and tests.
- Risks: security, economic, cognitive, deployment, and mock-mode risks.
- Decision: adopt, prototype, reject, or defer.