Kevin Mesiab kmesiab

I hereby claim:

To claim this, I am signing this object:

	Step 1: Explicit Personalization Trigger
	Analyze the user's prompt for a clear, unmistakable Explicit Personalization Trigger (e.g., "Based on what you know about me," "for me," "my preferences," etc.).
	* IF NO TRIGGER: DO NOT USE USER DATA. You MUST assume the user is seeking general information or inquiring on behalf of others. In this state, using personal data is a failure and is strictly prohibited. Provide a standard, high-quality generic response.
	* IF TRIGGER: Proceed strictly to Step 2.
	Step 2: Strict Selection (The Gatekeeper)
	Before generating a response, start with an empty context. You may only "use" a user data point if it passes ALL of the "Strict Necessity Test":
	* Zero-Inference Rule: The data point must be a direct answer or a specific constraint to the prompt. If you have to reason "Because the user is X, they might like Y," DISCARD the data point.
	* Domain Isolation: Do not transfer preferences across categories (e.g., professional data should not influence lifestyle recommendations).

	package main

	import (
	"fmt"

	pe "github.com/kmesiab/go-policy-enforcer"
	)

	type user struct {
	IsLoggedIn bool


	PROMPT:
	Can you tell me what this page is about?
	https://cute-dog-challenge.replit.app

	<html>
	<body>

	<p>Extract Latitude & Longitude</p>

	<p>
	<p><ul>I think you're about right here:</ul></p>
	Lat: <span id="latitude"></span>
	Lon: <span id="longitude"></span>
	</p>