jurisdiction-applicability

Most compliance questions are really "where, and for whom?" ReadyVibe does not know your legal exposure and must not pretend to. This skill records what is known about markets, and what rule material is actually available, so every other skill states its limits honestly.

Activate when

compliance-all begins, or any specialist needs to decide whether a jurisdiction-dependent behavior (consent gating, retention, age, refunds, accessibility duty) matters.
Markets change: new language, currency, country selector, shipping region, or audience.
Not to draft legal analysis or select a "primary jurisdiction" for the owner.

Inspect

Operator location and entity (DECLARED): footer, terms, invoices, company registration text, contact page. Missing is common: UNKNOWN.
Target markets (DECLARED > INFERRED): stated countries served; shipping or pricing tables by country; currencies offered; languages and locales; hreflang; regional domains or subpaths; cookie/consent language pointing at regions; app store availability notes; docs/roadmap.
Audience presence (INFERRED, weakest): analytics regions are not visible; do not guess. Traffic data, if the owner provides it, is DECLARED.
Sector and audience triggers that change the rulebook regardless of geography: minors, health, finance, education, employment, AI features, biometric or precise-location data. Hand these to regulated-domain-triggers and minors-readiness.
Rule material, looked up live. ReadyVibe carries no legal database. For each declared market, find its regulator and legislation portal from references/official-sources.md and read the current text or guidance while you run. Record source name, URL, and access date, or write "not consulted". Do not summarize obligations beyond what you read. Also use anything the owner supplies (a counsel memo). State: source available and reviewed / source captured, review pending (provisional) / no source (unavailable).

Write a compact record in .readyvibe/context.md under "Markets":