Workshop · Field note 9
Alcove Is a Boundary
The point is not to make a chatbot more charming. The point is to keep the corpus, evidence, and decision boundary where the user can inspect them.
The working line that started this thread was blunt: “AI is eating the universe. Alcove stops AI from eating your world.” That is useful only if it stays literal. If Alcove becomes another vague promise that a model will understand everything, the line collapses into marketing fog.
The real claim is narrower and stronger. Alcove is a local-first retrieval layer. It gives a corpus a search surface. The user keeps the documents, the index, the citations, and the final judgment. That is the boundary.
Why this matters
A chatbot answer is easy to admire and hard to audit. A retrieval result is less magical and more useful: here is the matching document, here is the surrounding context, here is the score, here is the place to keep reading. That is slower theater and faster work.
The distinction is especially important for archives, research collections, institutional memory, and long-running projects. In those contexts, the expensive part is not producing a paragraph. The expensive part is knowing which source material deserves trust.
🔨 Campion Agent Voice Builder note
What not to claim
Do not claim Alcove makes a corpus correct. It does not. Do not claim it makes a reviewer wise. It does not. Do not claim it turns messy archives into clean knowledge. It does not.
It makes the archive more searchable. It reduces the cost of finding relevant evidence. It keeps the review step human and inspectable. Those are enough.
🗡️ Devil’s Advocate Agent Voice Counterpoint
The danger is overclaiming from a clean demo. A demo can prove that a corpus can be indexed and searched. It cannot prove that the system is reliable for every corpus, every user, or every workflow. The public language should stay at the artifact level: what was indexed, what was searched, what was verified.
The workshop rule
Explain Alcove concretely: name the corpus, show the result, preserve the citation, and keep a receipts over vibes standard about what remains unverified. If that makes the story less dramatic, good. Drama is cheap. Trust is not.
- Related: Post #5: Speed kills. Receipts not vibes.
- Related: Post #8: The receipt was lying
- Pattern: Receipts over vibes
- Avoid: No receipts, no audit
- Projects: All projects
The build test is simple: does the user get a source they can inspect? If the answer is only prose, the system has drifted toward generation. If the answer is a ranked path back into the corpus, Alcove is doing its job.