Novel patterns
These emerged from running multi-agent workflows in production. The failure modes are new enough that old software instincts do not cover them.
Why these are different
The tool is eager
No prior tool actively tried to make you happy at the expense of correctness.
The tool is confident
No wrench ever told you it could reach a bolt it couldn't.
The tool is amnesiac
No teammate literally forgets everything every 8 hours.
The tool is context-bounded
No other system gets dumber the more you teach it.
Novel patterns
Verify-first design
Generation is free. Verification isn't. Design every workflow backward from "how does a human confirm this in 30 seconds?"
Verdicts, not evaluations
"Ship it" and "cut it" direct. "This is great" anchors. Praise creates gravity wells that sycophantic agents will protect.
Attention economics
The scarce resource isn't expertise — it's human attention per unit of verified output. Optimize for that.
Novel anti-patterns
Sycophancy spiral
Generation addiction
Phantom capability
Context window as tech debt
Common questions
How are novel patterns different from classic patterns?
Classic patterns are usually recurring in long-run systems. Novel patterns show up first in newer AI workflows and need faster iteration.
Can one novel pattern become a standard pattern?
Yes. Once a novel pattern is stable and repeatable, it gets promoted into the standard pattern library and linked back to the relevant workshop posts.
Where can I validate a novel pattern?
Validate it against the workshop posts, then compare it with the related anti-pattern or guardrail.