Dennis 0.8.5: The Chickens Are Safe, But Now We Need Trust (and Receipts)

🐔 The Chickens Are Still Safe

A few weeks ago, we solved a critical industry crisis:

👉 Chickens were being unnecessarily sacrificed in code transformations.

They were removed from rituals, given a proper coop, and are now attending coding seminars.

Everything seemed under control.

Transformations were deterministic.
Diffs were canonical.
Lineage was clear.

And yet… something was still missing.

🧠 We Can Prove Transformations

Up to this point, Dennis could already answer:

What will change?
What changed?
Is this transformation correct?

Not "probably correct."
Deterministically correct.

That’s a big step forward. But it’s not enough.

❗ The Question That Actually Matters

There is one question that keeps showing up in real systems:

Should I trust this transformation?

Not:

Is the diff valid?
Is the plan reproducible?
But:

Who made this… and do I trust them?
That’s the gap Dennis 0.8.5 closes.

🔐 Trust, Made Explicit

DEX artifacts could already be signed. Now, that signature actually means something.

Dennis 0.8.5 introduces: 👉 Explicit, Inspectable Trust

🧾 Transformations With Receipts

Run:

dennis inspect artifact.dex

And you get more than metadata. You get a Trust Report:

Who signed it
Whether the signature is valid
Whether that identity is trusted
Whether the artifact should be accepted

No assumptions.
No conventions.
No "looks legit to me."

Just a decision.

⚖️ Strict Trust (No Middle Ground)

Dennis now follows a simple rule:

An artifact is accepted only if at least one trusted signature exists.

That’s it.

✅ Trusted → Accepted
❌ Not Trusted → Rejected

Nothing in between.

🧠 Why This Changes Things

We already trust:

• Commits
• Builds
• Containers

But transformations? Those usually come from:

A script someone ran
Somewhere
At some point
Dennis changes that. Now transformations have:

• Identity
• Signatures
• Policy
• Consequences

📦 Also: Size Matters

Artifacts now track their size end-to-end.

And the result is… almost boring:

They’re tiny.

Which is exactly what you want. Because now:

• Storing them is trivial
• Sharing them is cheap
• Scaling them is realistic

And artifact-based workflows stop being theoretical.

🔄 The Shift

You can feel the evolution now:

Before: Run and hope.
Then: Inspect and verify.
Now: Decide whether to trust.

That last step is the one that matters in teams.

🐔 The Chickens, Revisited

The chickens reviewed the new trust model.

Their feedback:

Fewer rituals
More signatures
Significantly reduced anxiety

Legal is still involved. The chickens remain cautiously optimistic.

🚀 Try It

Dennis 0.8.5 is live.

1. Upgrade:

pip install dennis-forge --upgrade

1. Create your key (if you haven't):

dennis keygen

1. Set up trust: Approve your key so Dennis knows to trust artifacts signed by it:


dennis key approve ~/.dennis/keys/default.pub --signer ~/.dennis/keys/default.key


1. Apply with strict trust:

dennis apply artifact.dex --strict

🔗 Dennis on GitHub 🔗 The Forge (SaaS)

Final Thought
We made transformations:

• Visible
• Deterministic
• Verifiable

Now we’re making them:

Trustworthy

And that’s when they stop being tools… and start becoming something you can rely on.

How do you currently handle trust in your refactoring workflows?
Manual review? Signed commits? Something else?
Curious how others approach this.