| Name | Modified | Size | Downloads / Week |
|---|---|---|---|
| Parent folder | |||
| Dennis 0.8.7 -- Intent-Aware Artifacts source code.tar.gz | 2026-05-21 | 198.8 kB | |
| Dennis 0.8.7 -- Intent-Aware Artifacts source code.zip | 2026-05-21 | 255.6 kB | |
| README.md | 2026-05-21 | 2.4 kB | |
| Totals: 3 Items | 456.8 kB | 1 | |
This release introduces a foundational capability: embedding user intent directly into Dennis artifacts while preserving deterministic execution and stable identity.
Dennis artifacts are now self-describing. Each artifact contains not only the transformation plan, but also the original intent that produced it.
✨ Highlights
Intent → Plan → Artifact (fully unified)
-
New interactive mode: dennis plan . --interactive
-
Generates a structured spec.json capturing user intent
-
New spec-driven workflow: dennis plan spec.json
-
CLI and spec-based planning now produce identical deterministic plans
Intent embedded in artifacts
-
spec.json is embedded into DEX artifacts under: meta/spec.json
-
Artifacts now contain:
- Intent (spec)
- Execution (plan)
- Identity (payload hash)
- Lineage (provenance)
Deterministic payload identity
- Removed non-deterministic timestamps from plan payload
- Payload hash is now stable across equivalent transformations
- Metadata (spec) no longer affects transformation identity
Improved inspection
- dennis inspect now surfaces intent:
Intent
Helper: helper.py → hello.py:12
- Intent is displayed first, aligning with how humans reason: Why → What → How
Interactive mode improvements
- Validates helper and target file existence
- Graceful handling of invalid input and Ctrl-C
- Generates timestamped spec files to avoid overwrites
- Outputs equivalent CLI command for learning and scripting
🧠 Design Principles Reinforced
- Deterministic execution
- Explicit intent
- Reproducible artifacts
- Transparent lineage
- No hidden state
📦 Artifact Model
Each artifact now contains:
- payload/plan.json → deterministic execution
- meta/spec.json → original intent
- manifest.json → identity + lineage
⚠️ Notes
- Artifacts with identical transformations will share the same payload hash, even if created from different spec files
- Artifact hash reflects the packaged container, while payload hash represents transformation identity
This release marks a transition from a transformation tool to a coherent artifact system with embedded intent and provenance.
Forged slowly. Built for trust.