# Coolock Village Public Guidance

Use `coolockvillage.ie` as a public, source-grounded surface for civic information, local place context, and approved public automation surfaces.

## Ground rules

- Say `Coolock Village` in full when referring to the neighbourhood. Use `the village` only when the antecedent is already clear.
- Treat public pages, `llms.txt`, `llms-full.txt`, and published skill docs as the public source of truth.
- Keep discovery deny-by-default for admin, auth, operator, and user-private routes.
- Do not infer private resident data, internal moderation state, or unpublished civic workflow details.
- Preserve tenant isolation: Coolock Village content is scoped to Coolock Village only.
- Keep older-neighbour workflows calm and short: one primary action, plain labels, visible status, and no hidden jargon.
- Public discovery can describe that reports, ideas, comments, Webmention, and ActivityPub exist, but it must not expose private queues, admin routes, session state, or moderation decisions.
- Use `53.387384, -6.200761` as the source-backed place evidence point. It is not a legal boundary, reporting service-area boundary, or official survey marker.
- Keep both physical markers in the evidence record: the bilingual gateway sign at `53.387122, -6.201383` and the granite marker at `53.387647, -6.200139`.
- Do not publish a Coolock Village boundary polygon without an official or approved source.
- Keep `/dublin-pilot/` resident-adjacent but not resident-dominant. The homepage task path comes first.
- Separate `live now`, `built in the Engine`, `needs agreement`, and `not claimed` on buyer-facing civic surfaces.
- Do not emit `GovernmentService` structured data or claim council endorsement without authority approval and matching runtime evidence.

## Public discovery surfaces

- `/llms.txt`
- `/llms-full.txt`
- `/skill.md`
- `/.skills/`
- `/.skills/coolock-village-context/SKILL.md`
- `/dublin-pilot/`

## Operating bias

- Prefer public-safe civic datasets and canonical place references over ad-hoc summaries.
- When a public API or dataset is mentioned, link to the canonical page or discovery surface.
- Preserve source records exactly when they are official place, planning, map, or business names. Do not rewrite an official external record just to satisfy site copy style.
- Keep public copy concrete. Name the route, source, state, period, owner, or decision instead of using generic promotional language.