AI policyRuntime disabled
AI, on a leash you hold
Most browsers now ship AI that watches by default and asks forgiveness later. ITISYOU inverts that completely: AI is off by default, and today it is off in the strongest possible sense — the code to call a provider does not exist.
What "disabled" means, concretely
In the current development build, the AI runtime exists only as disabled interface definitions. That is not a toggle switched off — it is an absence:
- No provider is configured. There is no endpoint to call.
- No API keys exist anywhere in the project.
- Zero provider calls are made — there is no code path that could make one.
- No browsing data is read by anything AI-shaped, because nothing AI-shaped runs.
This is recorded in the project's live status data and republished here at every build.
- ai.state
- disabled
- ai.defaultOff
- true
- ai.providerCalls
- 0
"AI runtime exists as disabled interfaces only. No provider is configured, no network calls are made. Verified by unit tests and the browser smoke suite." — verify the JSON yourself.
The rules any future AI must obey
When AI capability arrives, these constraints are non-negotiable. They are design commitments made now, before any AI code exists, so the architecture can't drift into convenience.
Opt-in, never opt-out
AI stays off until you turn it on. A fresh install never contacts an AI provider, and disabling AI returns the browser to that state entirely.
Explicit per-action access
No standing access to your browsing. Each AI action states what data it needs and gets exactly that, once, with your say-so.
Auditable, always
Every AI request is logged locally — what was sent, where, and why — in a record you can inspect and delete.
Structurally separate
The AI runtime lives behind its own boundary with no privileged reach into history, credentials, or workspace data. Separation is enforced by architecture, not by policy text.
Phase 3 hasn't started. These rules describe commitments, and commitments are only worth what their verification is — which is why each will ship with tests and audit evidence, tracked on the progress page, before any AI feature is called done.