Skip to content

Practical patterns, starters & CLI tools for loop engineering with AI coding agents. Design systems that prompt and orchestrate agents (inspired by Addy Osmani and Boris Cherny). Includes loop-audit, loop-init, loop-cost.

docs(sources): cross-link Open-Spek as a related but differently-scoped project (#252)

Mehmet Cevheri BOZOGLAN69d9f6604cbe
diff --git a/resources/sources.md b/resources/sources.md
index 4f31d41..cd993fe 100644
--- a/resources/sources.md
+++ b/resources/sources.md
@@ -44,6 +44,9 @@ These provide important context and guardrails for loop design.
- **Marius ([@sololys](https://github.com/sololys))** — [KY Cut Surface Philosophy v0.1](./ky-cut-surface-philosophy-v0_1/) (July 2026)
Archived public philosophy on the distinction between generation and consequence. Not a pattern or runtime — indexed via [stories/ky-cut-surface-generation-vs-consequence.md](../stories/ky-cut-surface-generation-vs-consequence.md).
+- **Open-Spek** — [open-spek/loop](https://github.com/open-spek/loop), [open-spek.github.io](https://open-spek.github.io) (July 2026)
+ An independently-developed, differently-scoped use of the term "loop engineering": a test-gated, fresh-context loop that turns a frozen Spek — the complete knowledge required to recreate a piece of software — into a verified implementation, one milestone at a time, rather than a scheduled maintenance cadence. First proof: [open-spek/jsonq](https://github.com/open-spek/jsonq) (21 iterations, 252 tests, 100 percent coverage, 0 human-edited lines). Not a pattern for this repo's registry — cross-linked here because the term collides across both projects and readers of either may otherwise conflate them.
+
## How This Repo Relates
We treat the above sources as the current best articulation of the idea and aim to turn the abstract framework into practical, copyable patterns, templates, and tool-specific guidance (with special attention to the Grok Build TUI, which has strong native support for the primitives).