Skip to main content
Intramedial
AS

Read-only demo account · Enterprise

The Awesome Company, Inc.

All capabilities enabled · unlimited quotas · 42 active agents · 4 workspaces

Preview · Tops

Tops (demo)

The system that watches the system. Infrastructure Tops + Tops on one hash-chained ledger.

Tops status

One chain. Two surfaces. Always verifiable.

Chain integrity

Intact

Last verified 5/20/2026 · 1,247 entries inspected

Ledger Bundles anchor

5/21/2026

Bitcoin-rooted OTS proof

Configuration health

1 config at elevated detail

Extended / forensic levels are adversary-readable

Infrastructure Tops

Always on. Cannot be disabled.

Mandatory
Entries · last 30 days
1,247

ingest, export, key issue, webhook, cron, anchor

Admin reads · last 30 days
0

Target: zero in normal operation

Last platform write
5/21/2026

5/21/2026, 2:20:00 PM

9 kinds tracked

Tops

Customer-controlled. Adversary-safe by default.

Configurable
Entries · last 30 days
84,312

observe, decide, skip, state, drift

Active configs
6

1 org · 2 workspace · 3 actor

Sampling range
10% — 100%

Across all active configs

5 kinds available

Why two control models?

Infrastructure Tops is mandatory because optional transparency about ourselves is theater. If we let you turn off the record of what we do on your workspace, the record would be useless the moment it mattered most.

Tops is yours. Your actors run inside your workspace; what they observe and decide is yours to record at the granularity you choose — per org, workspace, actor, kind, environment, with sampling and adversary-safety controls. Default is the “Recommended” preset (full coverage at safe detail); presets and per-field controls let you trade write volume against forensic depth.

Configuration changes themselves are recorded. Every adjustment to a Tops config writes a tops_config_change entry into the chain — turning Tops off, raising the detail level, sampling down a high-volume actor. You cannot disable the watcher without leaving a trace of disabling it.