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

What gets counted

The rule table

E01
Western social media never primary. Skip if it is the only source.
E02
Western chat apps excluded. Line only.
E03
Thai and English sources both, where they exist.
E04
Non-Thai addresses: English plus national language.
E05
10-day activity window. No action in 10 days means dead.
E06
Action means a dated post, comment, RSVP, update, review, or confirmation.
E07
Recurring events need a current-year entry, or current posts showing action.
E08
Order by number of recent updates and posts.
E09
Print the score as [S: n] next to the title.
E10
Tie-break on source diversity, then nearest next date.
E11
Thai address in Thai script, then English, plus cross-street and landmark.
E12
Non-Thai address in English and national language, plus cross-street and landmark.
E13
Never invent a cross-street. Say unconfirmed and say what would confirm it.
E14
List website, Line, and phone when each exists.
E15
No western chat app contacts. Say no permitted contact listed.
E16
Give previous functions when available.
E17
Shortest useful summary of online talk, with links. One line each.
E18
State whether history is long and consistent, short, or absent.
E19
Search organiser name plus scam, review, Thailand.
E20
State red flags explicitly. No history at all is the biggest.
E21
State local or not. If unclear, say local status unconfirmed.
E22
Thai company must have a Thai address. No address is a red flag.
E23
Brick-and-mortar: use every method to get the most recent active date. A live site is not proof.
E24
Old products or old posts: label Likely dormant or Likely dead.
E25
Do not over-research a venue; do not under-research an organiser.

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.