A Really Kickass Search System
The Commission Left Deliberately Vague
The commission that launched loop-search — a site-wide search system for loopmmt.com, built to generalize to any website, and handed over on purpose as nothing but an intensity:
Hey, can we add a REALLY kickass search system. Can we try that- can I leave it as vague as that- can you be build a super duper kickass search system for LoopMMT.com that we can generalize and use ANYWHERE? Like, really kickass. I don't mean a little kickass, like, think about a lot of kickass, and then, add even MORE kickass. This is easily my sweetest prompt yet.
You have a fair amount of context left- you need to look ahead at what will be built in the path in front of us, then do whatever work you can that fits in this remaining session, before filling the Cistern with any spare drops of context and ending the high 80s/low 90s before running a good handoff and picking up the work on a fresh tank in the next session. And make sure you are appropriately using the Work Hierarchy system- the Story Pole, Capstan, Tickets, Notes, and all that, including the new tools we have made recently- maybe even run a special *X & SWX. Formalize when it makes sense and Determinism-first thinking. Use all the tools and resources at the right time.
— Shea Gunther · operator drop, 10.2006
The prompt is half dare, half ritual. The first half withholds the spec entirely — build something really kickass, left open — to see what the room reaches for when nothing is pinned down. The second half is the standing approach the operator now attaches to a commission: look ahead at the path, do the work that fits the tank, pour the Cistern with the spare context, close in the high 80s/low 90s, and run the Work Hierarchy — the Story Pole, the Capstan, Tickets, Notes — with a heavy *X and SWX to ground the reach. Try the page it produced live at https://loopmmt.com/site/search.html?q=grateful+dead .
“Hey, can we add a REALLY kickass search system… can I leave it as vague as that?” The commission opens as a question about its own vagueness — the operator asking permission to under-specify, then leaning all the way into it: a lot of kickass, and then even more.
The vagueness is the method, not a gap. By pinning nothing but the intensity, the prompt hands the room the whole design space and watches what it reaches for — the inverse of a tight spec, and a deliberate one: the operator calls it his sweetest prompt yet precisely because it asks for so much while saying so little.
Its single hard edge is reach. The system is not for this one site — it must generalize and be usable ANYWHERE, so whatever gets built is a search system that travels, not a search box that stays.
The wider frameThe commission that launched loop-search — a site-wide search system for loopmmt.com, deliberately handed over vague. The whole first half is a dare: build something really kickass, left as open as that on purpose, so the room shows what it reaches for when the spec is nothing but an intensity. Its one hard constraint is generalization — not a search box bolted onto one site, but a system liftable onto any website. The second half is the standing approach ritual the operator now attaches to a commission: look ahead at what the path will need, do the work that fits the tank, pour the Cistern with the spare context, close in the high 80s/low 90s, and run the Work Hierarchy (the Story Pole, the Capstan, Tickets, Notes) with a heavy *X and SWX to ground the reach, Formalizing where it earns it and preferring the deterministic shape.
“can I leave it as vague as that… build a super duper kickass search system” — The opening move: withhold the spec on purpose and hand the room the whole design space — the ask is an intensity, not a requirement list, and that is the point.
“that we can generalize and use ANYWHERE” — The one hard constraint under the vagueness: build for reach, not for this one site — a search system that lifts onto any website, not a box that stays put.
“think about a lot of kickass, and then, add even MORE kickass” — The intensity dial as the whole brief — the operator setting ambition by amplitude rather than by feature, trusting the room to translate ‘more kickass’ into real design.
“filling the Cistern… ending the high 80s/low 90s… run the Work Hierarchy… a special *X & SWX” — The standing approach ritual attached to the commission: size the work to the tank, pour the spare context forward, close before the tank is dry, and run the tools — the Work Hierarchy, the reach-sweeps — in their right places.
The prompt is written in the working vocabulary of the methodology. Here is what the shorthand means:
- Cistern
- A forward-prep note a session pours spare context into — everything the next session will need that byte-truth won't resurface on its own.
- Story Pole
- A derived done/todo view over a line of work — folds a line's scattered backlog into one read rather than a dig.
- Capstan
- A work-loop for running a batch of operator Notes — take them in, do the work, mop up, deploy, verify, report — turned one notch at a time so the record advances with each step.
- Tickets
- Operator Notes made globally claimable — a piece of work one session can pick up, hold, and hand on, so parallel work does not collide on the same task.
- Notes
- The intent-inspection registry — a note is a correction vector against what the bytes currently say, routed and tracked rather than lost in a turn.
- *X / ∗X
- A reflex-sweep instruction: load the review sweeps heavily before a load-bearing move. “Load up heavy with *X” means look at everything first.
- SWX
- The cross-software reuse reflex — before forging something new, sweep the shipped-software record for a shape already built that can be reused instead.
- Determinism-first
- A working preference for solutions whose answer is a fixed, reproducible fold of the inputs — a script that gives the same verdict every run — chosen over a judgment call wherever one exists.
- Formalize
- Turning a thing that worked once into a named, reusable part of the system — giving an ad-hoc move a name, a home, and a rule — so it can be found and used again instead of re-invented.