Composition example. Illustrative data assembled into a real-shape Landscape dashboard — sidebar shell with left rail + right #aside (activity + agents), KPI row with deltas, ingest-rate sparkline, treemap, faceted file search, scan table. Composes ~15 Tux* + Nuxt UI 4 primitives.

indices

/research

Continuously indexed by 4 agent runtimes. Drift reconciler last ran at 12:00 CST. Last 24h: 203 scans queued, 198 complete, 4 failed, 1 in progress.
47.2 TB

Indexed across all corpora

47.2 TB

Indexed across all corpora

↑ 1.4 TB · last 7 days

12.8M

Files tracked

↑ 124k · vs last week

203

Active scans · last 24h

↓ 14 · vs yesterday

ITAR-tagged records in this corpus

Corpus size · by directory

Ingest · 28 daysIngest rate, files per hour, last 28 days
movementlabraw-corridor-feeds7.6 TBprocessed1.9 TBgrantsnsf-12343.8 TBtxdot-781.6 TBfhwa-2024885 GBpublications20251.3 TB20241.0 TB

Ingest trend · 12 months, current vs prior

Drag the brush handles below to narrow the window — hover or tab into the chart for value tooltips.

Corpus composition · stacked by file type

108M

Total

52M

PDF

31M

CSV

25M

GeoJSON

020406080100JanFebMarAprMayJunJulAugSepOctNovDec523125
  • PDF
  • CSV
  • GeoJSON

Throughput · status · health

scans / weekday

Throughput · last 4 weeks avg

Failed bars overlaid behind completed (comparison overlay variant).

050100150200MonTueWedThuFriSatSun
  • Completed
  • Failed

files · by tier

Access-tier distribution

Restricted + ITAR slices auto-fold into Other below minSlice; here they're material enough to show on their own.

Public · 4,120,843 (31.9%)Internal · 6,411,203 (49.6%)Restricted · 2,230,117 (17.2%)Other (1) · 174,022 (1.3%)

Files

12.9M

  • Public4,120,843 · 31.9%
  • Internal6,411,203 · 49.6%
  • Restricted2,230,117 · 17.2%
  • Other (1)174,022 · 1.3%

health · sla + utilization

System health

Two single-target metrics that genuinely have hard floors / soft caps — the cases where gauges actually earn their seat.

95100

API uptime

99.84%

0100

Agent pool

72%

Active corridor study · I-35 mile 174–195

Live operational view of the corridor study that's also published in Hassan et al. 2025. Treatment zones, construction zone, and instrumentation sites in a single linear view.

Northbound →

I-35 corridor — northbound

Pre-treatment baseline — mile 174 to 178Treatment zone A — mile 178 to 184Construction zone — mile 184 to 188Treatment zone B — mile 188 to 192Post-treatment baseline — mile 192 to 195FM 60 intersection — mile 175.5Site 12 instrumentation — mile 180Treatment applied — mile 189Site 18 instrumentation — mile 193174175180185190195
Intersection
12Instrumented site
Treatment applied
!Incident

Files · 1.2M results

ScanPathAgentStartedFilesStatus
scan-7f5bd95a/research/movementlab/raw-corridor-feedsagent-0412:14:08412,843running
scan-83012ab1/research/grants/nsf-1234agent-0211:48:3388,402completed
scan-c0a18bbe/research/publications/2025agent-0411:21:1912,207completed
scan-d44ef902/research/scratchagent-0310:55:000failed

File · findings.pdf

path
/research/grants/nsf-1234/data/2026/Q4/findings.pdf
size
4,217,832 bytes
modified
2026-04-22T14:33:18Z
owner
rchen@tti.tamu.edu
tier
ITARRestricted
classifier
CLS-204 · 0.87 confidence