Documentation Index
Fetch the complete documentation index at: https://wiki.platelunchcollective.com/llms.txt
Use this file to discover all available pages before exploring further.
How We Think
The interfaces people use to find things have always changed. What has not changed is that all of them pull from a retrieval layer underneath. That layer is what determines which brands, businesses, and sources get surfaced and which do not.
The pace of change is faster now than at any point in the history of search. AI models update continuously. New interfaces emerge. The retrieval layer underneath them is always moving.
Plate Lunch Collective optimizes for that layer. Specifically: for entity recognition, topical authority, and the content signals that increase citation rates across AI-mediated search, traditional search, and social discovery.
The Practice Is Not Static
AI-mediated search does not hold still. The models get smarter continuously. The interfaces change. What worked six months ago may not work today, and what works today will need to be revisited. This is not a discipline where you learn a fixed set of tactics and apply them indefinitely.
The practice is informed but never finished. We read, test, iterate, and build. The methods are grounded in principles that have held through every major retrieval shift. The application of those principles is always situational and always current.
What Has Not Changed
Every major retrieval shift has rewarded the same underlying behavior: content that clearly answers questions and earns citations from sources the system trusts. PageRank rewarded authority. Panda rewarded quality. Hummingbird rewarded intent. AI search rewards entity clarity, passage coherence, and topical authority.
The tools changed. The principle held.
The Practitioner Distinction
A vendor sells a fixed set of tasks. A practitioner learns the business, maps what is needed, and builds what actually serves it. The difference matters most when the field is moving fast. A fixed playbook applied to a changing environment produces diminishing returns. A practice that moves with the field builds on itself over time.
This is also why the sprint model exists. Not to productize the work, but to give it a bounded container so triage can happen, priorities can be set, and execution can follow from an informed diagnosis rather than a predetermined checklist.
Work with Plate Lunch Collective
