AURiX: Sweet

See what is controlling the page right now - overlays, redirects, trackers, permission grants. Local, private, on-device.

AURiX: Sweet is five structural-observation instruments in one install. Each one answers a different plain question about the page in front of you, and none of them interprets, scores, or sends anything anywhere. Gauge — what is the page doing right now? A quiet bottom strip shows the present-tense structural state of the page: scroll locks, overlay obstructions that capture clicks meant for the page underneath, focus traps, navigation overrides, and the silent permission and storage activity a page performs in the background. When something deserves attention the readout shifts. When nothing does, Gauge stays quiet. Scope — look HERE, before you commit. Right-click any link, element, or page and Scope reads its structural posture and shows a single signal in a grammar small enough to read in one glance: a filled circle for Stable, a hollow circle for Uncertain, an upward triangle for Fracture. Scope composes the readings of the other instruments under a worst-state-wins rule, so one glance tells you what the whole stack thinks — without you reading four dashboards. Trace — how did I actually get here? Every redirect, every navigation hop between the link you clicked and the page you landed on, recorded locally, per tab, in a bounded buffer. If a link said one thing and sent you somewhere else, Trace caught the divergence. Ledger — what changed since before? Price changed after you put it in the cart? Ledger has the diff. Terms of service updated between visits? Ledger has both versions. State changes, timestamped, held in a bounded local buffer — so "I swear the price was different" becomes "here is the recorded change at this timestamp." Receipt — bind this moment. One click captures the structural state of the page — what loaded, what permissions were requested, what origin the content claimed — bound to a timestamp. Not a screenshot; screenshots are pixels, easily faked. Receipts are ephemeral by default: nothing is stored to disk unless you deliberately export it. AURiX refuses to conclude. It never labels a page "safe" or "dangerous." It emits mechanism — what is observably happening, in terms you can check — and leaves the meaning to you. That refusal is the design. Local. Private. Identity-free. There is no AURiX server, no account, no profile, no telemetry, no network calls of any kind. Everything an instrument observes stays in your browser's local storage until you delete it. Export — a screenshot, a JSON observation receipt — is always a deliberate, user-initiated act through the system save dialog. "i" created this initially to make money. Along the way i stumbled onto much bigger and, in my mind, more important things — they already exist in the Sweet. i benefit twice over: from knowing it helps people, and from what that shows — that my work is functional, serious, and strictly cohesive with my ethos. It is free so that everyone, myself included, profits. If it weren't, i wouldn't be me; it wouldn't be AURiX. — AURiX Founder