Agent #8 · Live

Surveillance / Observation Anchor

Knox commits your events at the moment they happen. Agent #8 analyzes the observation side — who is touching the anchored stream, from where, with what rhythm. Every report is itself Bitcoin-anchored, so if a dispute or investigation later turns on when a pattern first appeared, you hold a tamper-evident answer.

What the agent reads

Your own anchor stream metadata

Agent #8 queries only the events anchored under your Knox API key — source IPs, user-agent strings, timing, latency. It does not examine the payloads themselves. Raw identifiers are hashed to short opaque tokens before appearing in the anchored report.

Per-API-key scopedMetadata onlyHashed tokens in output
What the agent writes back

A self-anchored report

Every run returns an observation index (0–100), a surveillance band (quiet / routine / active / intense), the triggered signal set, and a SHA-256 report hash. The hash is then committed to the Knox chain itself — you cannot edit history of what the agent observed at a prior run.

Index 0–1004 bandsReport hash anchored
Eight signals analyzed

What pattern strength looks like

single_source_dominanceweight 20

One IP accounts for more than 80% of anchors. Strong bot-like or single-user signature.

source_diversificationweight 10

Unusually broad distinct-IP distribution. Real-world access pattern.

off_hours_concentrationweight 15

More than 40% of anchors land outside 06:00–22:00 UTC. Access rhythm inconsistent with human business-hours use.

new_source_appearanceweight 15

New source IPs first appear in the most recent 24h of a multi-day window. Observer pool shift.

velocity_spikeweight 10

Last hour's anchor rate is 5× or more above the rolling mean. Observation burst.

ua_uniformityweight 10

Two or fewer distinct user-agent strings across 30+ anchors. Consistent with single-client automation.

latency_clusterweight 10

Anchor latency coefficient of variation below 0.15. Automated infrastructure at a fixed network distance.

access_rhythmweight 10

Anchors cluster at specific minute-of-hour values. Periodicity consistent with scheduled automation.

Call it with your key

Run the agent

The agent is authenticated. Provision a Knox API key at bonissystems.com — free tier covers 100 events / month and includes the agent API. Then:

curl -s https://bonissystems.com/api/knox/agents/surveillance?hours=720 \
  -H "Authorization: Bearer knox_YOUR_KEY_HERE"

hours controls the analysis window (default 30 days, max 90 days). Report is returned as JSON and a surveillance_report anchor event is written to your chain.

Positioning

What this is and is not

This agent is

  • A pattern-strength scan over access metadata for your own anchored events

  • A self-anchored record of how the observation pattern changed over time

  • A hand-off trigger for human review, forensic teams, counsel

This agent is not

  • A surveillance identification or attribution system

  • A determination of who is watching or why

  • A replacement for SIEM, IDS, or human security judgment