Evidence Console

you shouldn’t be seeing this.

Open Live Stream View Snapshot
  • operator intent + selective attention
  • historical memory + confidence drift
  • redaction that changes while you watch
This is a simulation. No keystrokes, mic audio, GPS, or personal data is collected.

Subject Snapshot

status: active visibility: limited channels: 3 hidden

confidence: low priority: monitor first seen: — sessions: — state: preserved
objective: ██████████ handoff: pending resale: mixed
operator intent
decision source: ████████
disposition: retain
purge policy: none
notes: baseline watch
historical memory
prior match: confirmed
recurrence: detected
cross-day linkage: ██████
retention: indefinite
asymmetry
visible layers: partial
enrichment: external
hidden channels: 3
viewer access: restricted
selective attention
focus window: wide
spike trigger: none
behavior drift: stable
watch mode: passive
valuation
suitability score: rising
partner signal: ██████████
outcome state: in-progress
classification: consumer
What you’re seeing (without revealing the “how”)

This page mimics how “internal dashboards” look — not how illegal tools work. It uses daily-seeded values + harmless interaction signals (scroll/click/tab visibility) to create the feeling of intent, memory, and escalation.

The creepy part isn’t a virus. It’s the idea that normal telemetry can be made to feel like surveillance.

Compiled Profile

this is what makes it feel real: selective fields, redacted fields, and “decisions.”

coarse region— ████
network identitypublic ip: — • route: —
device surfaceplatform: — • display: — • tz: —
attentionactive time: 0:00 • tab switches: 0 • idle bursts: 0
interest graph—
trigger terms—
ad outcomes—
risk posture—
unknown fields████████████████████

Notice the trick: some fields are readable, some are redacted, and some are “unknown.” That’s the asymmetry.

Live Evidence Stream

it slows when you’re idle. it spikes when you act. (selective attention)

stream: running visibility: visible redaction drift: active observer: attached
init [boot] observer attached • memory loaded • session linked (loose)
Why this feels “wrong”
  • Intent shows up as decisions (“priority changed”).
  • Memory shows up as “seen before.”
  • Asymmetry shows up as hidden channels and redaction.
  • Outcome shows up when the system says “sufficient.”

Current State

tracking continues quietly exit does not erase state viewer access remains limited

This page is designed to make people realize how “normal” telemetry can be weaponized into something that feels like surveillance. The scary part is the presentation — not a magical hacker tool.

☕ Thank you for visiting! If you’d like to support the site, you can buy me a coffee — it’s always appreciated.