dacp-interpreterlisted
Install: claude install-skill Tibsfox/gsd-skill-creator
# DACP Interpreter
Scripts in bundles are **review-only references** — the interpreter NEVER auto-executes any script (SAFE-01).
## Summary
The DACP Interpreter handles receiving-side bundle processing. When a `.bundle/` directory appears alongside a `.msg` file, the interpreter detects, validates, loads, and integrates the bundle into a structured `ExecutionContext`.
### Fidelity Level Guide
| Level | Contents | What to Do |
|-------|----------|------------|
| 0 | Intent markdown only | Read intent.md, proceed with instructions |
| 1 | Intent + structured data | Access `typedData` for structured parameters |
| 2 | Intent + data + schemas | Validate your understanding against schemas |
| 3 | Intent + data + code | Review scripts, decide whether to execute or reference |
| 4 | Intent + data + code + tests | Verify with provided test fixtures before proceeding |
### Interpretation Pipeline
```
DETECT -> VALIDATE -> LOAD -> INTEGRATE
| | | |
| | | +-- buildExecutionContext()
| | +-- loadBundle()
| +-- validateBundle()
+-- Check for .bundle/ directory
```
## Workflow
### Step 1: Detect Bundle Companion
Look for a `.bundle/` directory alongside the `.msg` file. If found, prefer the bundle over raw `.msg` content.
### Step 2: Validate Bundle
Call `validateBundle(bundlePath)` to check:
- `.complete` marker exists (atomicity guarantee)
- `manifest.json` parses and validates against