Operational values appear only after a trusted API observation.
Awaiting the first control API responseRead-only facts loop
Awaiting PLEXBLD platform aggregateAgent jobs
Ollama runtime
Recent activity
| Event | Area | Actor / source | Status | Time |
|---|
Universal World Knowledge Network
One canonical ontology shared across PLEXBLD. Release facts come from the private versioned object in PLEXBLD storage.
Universal graph changes
Knowledge & model controls
Every control area remains visible. Each card reports its real source state; unconnected capabilities stay clearly marked.
Operations
Population-level mobile scans and the cloud processing platform are reported separately from production records. Account identities load only after an owner opens a statistical bucket.
PLEXBLD app activity
Bounded statistical summaries across mobile accounts; no account list is preloadedProjects, processing and stored outputs
Production cloud projects, assets, artifacts, capture runs, compute jobs and outbox stateOperational sources
Security
Current Access protection and application identity anomalies come from verified Access JWTs and production D1 records. Cloudflare edge-threat events remain a separate source.
Security sources
Infrastructure
Ten-second Ubuntu samples provide real timelines while this page is open. Longer views use bounded one-, five- or thirty-minute rollups from seven days of retained host metrics.
Ubuntu load and task timelines
Every visible point can be selected for its exact bucket detailUbuntu compute nodes
Infrastructure sources
Access & billing
Accounts, sessions, memberships, devices, grants and pairing state come from production D1. Billing, subscriptions and third-party licenses stay explicitly separate until their ledgers are connected.
Access and commercial sources
Public pages
Availability, response status, response time and security-header coverage are checked server-side against configured PLEXBLD public origins.
Configured public endpoints
Publishing sources
Console settings
Runtime source state, freshness and last successful reads come from the protected control API.