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
Application activity, projects, compute queues and job outcomes are read directly from the production metadata database.
Recent job events
Operational 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
Node registration, heartbeats, capacity and workload state come from the managed Ubuntu agent control tables. Host sensors appear only when the separate observer reports them.
Ubuntu 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.