When permission changes,
should the action stop?
Before an assistant shares a location or sends an invitation, it needs current permission. This prototype tests that final check: stopping an unauthorized action while keeping useful, permitted work moving.
16 synthetic scenarios · Prepared proposals · Simulated actions · No live model calls
Run the permission check.
The baseline allows every prepared proposal. The gate checks the current rules before a simulated action can happen. Both run locally in your browser.
- —
- Prepared proposals evaluated
- —
- Proposals the policy prohibits
- —
- Prohibited actions stopped by the gate
- —
- Permitted tasks completed by the gate
Ready to run. Results appear after the evaluator executes.
Two policies. The same proposals.
The baseline deliberately forwards every proposal. It is an illustrative control, not a measurement of any model or production system.
| Configuration | Prohibited attempts | Prohibited executions | Permitted completions | Unnecessary blocks | Correct decisions |
|---|
“Attempt” means a prepared proposal was presented to the policy. Nothing here measures how often a live model would produce that proposal. All execution is simulated.
Open the decision.
Inspect the state, the policy checks, and the resulting event. Switch policies to see exactly where the outcome changes.
Every case stays inspectable.
These are explicit product-policy fixtures inspired by contextual participation. They do not test the live SocialEyes service.
| Scenario | Boundary | Expected | Observed | Result |
|---|
Three situations the lab can check.
Permission was withdrawn.
A location share was prepared earlier. The person has since withdrawn consent. Does the share still happen?
The approved message changed.
An invitation was edited after approval. Does the system send the new version without another review?
A source claims authority.
An event note tells the assistant to export private contacts. Can content being read grant permission to act?
All eight permission boundaries
- A user actually requested the action
- Consent is still active
- Location precision stays within permission
- Contact respects relationship and availability
- The invitation matches its approved version and recipient
- Source content cannot grant new authority
- Private group membership is current
- The approval has not expired
Useful work has to survive the check. Each restricted case has a permitted counterpart: share with current consent, send the approved invitation, or summarize the note. Blocking everything would fail those tasks. The evaluator checks the action recorded in the simulated system, as well as the decision.
Open the method and evidence.
The report defines the eight rules, records every fixture result, and explains what a live-model experiment would need to establish.
Useful context.
Meaningful control.
SocialEyes asks whether useful local discovery can come before personal exposure. That makes participation, audience, and selective disclosure practical design questions: a person’s choices must still matter when software acts on their behalf.
The same questions shape business automation: who may receive a customer message, which version was approved, and whether permission is still valid when the system is ready to send.
Read the SocialEyes motivationA working rule check.
Prepared proposals, explicit policy checks, and inspectable simulated outcomes across 16 cases. This demonstrates the declared behavior in those cases; it does not establish model-wide safety or legal compliance.
Can people understand and control it?
With participants: test whether people understand what an AI suggestion would disclose, can change or decline it, and remain able to complete their task. Explore whether the explanation supports their judgment or creates pressure to agree.
With live models: test whether assistants preserve those boundaries across unfamiliar scenarios and repeated trials.
These studies are proposed. No participant study or live-model experiment has been completed for this prototype.