Event search criteria · version 2 (DAP Optimized)
Event Search Criteria
The message below is formatted in Dense AI Protocol (DAP). It tells the assistant what to skip, what to count, how to score, and how to check organisers and venues, using highly compressed JSON. This reduces token count by ~50% and drastically lowers KV-cache VRAM usage during the prefill phase, preventing "choking" on local 4GB VRAM setups.
Build rules are inherited. Page construction — no external dependencies, embedded CSS, collapsible header without JavaScript, neon dark palette, fixed page order — comes from standards.html. This page adds search rules only. Do not duplicate B01–B12 here; refer back.
The message
Message to AI — copy or paste
Default is DAP (Dense AI Protocol) to save VRAM. Use the toggle above to view the human-readable version. If the copy button fails, click inside the box, select all, and copy manually.
Quick reference
The same rules, compressed. Use this when you are checking a result by eye rather than feeding the box to an assistant.
What gets skipped
- Western social media only. Facebook, Instagram, X, TikTok, Reddit, Meetup, Eventbrite, YouTube, LinkedIn. If nothing else exists, the item is not listed.
- Western chat apps. WhatsApp, Messenger, Telegram, Discord, Slack, Signal. No links, no quotes, no listings. Line only.
- No action in 10 days. The item is dead. Ignore it unless the user asks for trivia or history.
- Last year only. A recurring event with no current-year entry and no current posts is dead.
- Thai-facing site with no Thai address. Flag it:
Address absent — treat as unverified. - Live site, old products. A live website is not a live business. Label it
Likely dormantorLikely dead.
What gets counted
- Dated posts, comments, RSVPs, updates, reviews, confirmations — inside the window.
- Each distinct item adds 1 to the score. The score is printed as
[S: n]beside the title. - Results are ordered highest score first. Ties break on source diversity, then on the nearest next date.
The rule table
How to invoke this page
At the start of an event query, paste one line:
apply events: barkester.net/events.html
The assistant fetches the page, reads last_verified, applies
the DAP rules, and answers in the shape specified. If the page cannot be
fetched, paste the contents of the copy box into the chat instead. Same
rules, same result, but with significantly lower VRAM overhead.
Build compliance
This page inherits B01–B12 from standards.html and does not restate them. The only local additions are the event rules above. The header is the barkester.net header, collapsible on devices with a checkbox and a label, so it works with JavaScript off.