Product Deep Dive

Cockpit Central turns private operations into visible command.

It is the Windows-based product cockpit for Diary and its product lanes: Diary, Dossier, Home, DAM, GAS, Hub, Reach, Brand, and Lab. One place to see status, launch workflows, inspect data, audit machines, and decide what is ready to move.

Open full Academy reference Browse Product Academy

Desks

Each Desk owns a data surface: project files, brackets, YouTube inventory, API status, setup state, support cases, health, concierge stages, and more.

Pulses

Pulses summarize what matters right now: world clocks, sync health, home inventory, cloud readiness, workflow progress, and travel context.

Commands

Menus collect the operational actions so scripts, setup routines, audits, and help are reachable without hunting through folders.

Current Reference

The reference now follows the live Cockpit registries.

The Product Academy documents all 23 active header Pulses, the optional TeamViewer definition, Desk families, weather and world clocks, workflow MachineTypes, shortcuts, and the public-safe Diary Pulse relationship.

Read the Cockpit Central reference

Registry-basedPulse names, scopes, and refresh intervals come from the current header widget authority.

Public-safeBehavior is documented without exposing private paths, credentials, or person-level evidence.

Mobile-readyThe same exact-host pages can be shown in the Diary Pulse website viewer.

Operating Model

One interface, many authorities.

Cockpit Central does not replace the authority lanes. It exposes them. Corporate identity governs visual behavior, Setup governs configuration, AI Desk receives self-healing signals, and HUB governs deployment readiness.

ObserveLoad the current machine, sync provider, role, version, and product state.

InspectOpen grids, filters, previews, status rows, links, and local evidence.

ActRun controlled scripts through role-aware menus and workflow gates.

LearnRoute errors, audits, and decisions back to AI Academy and self-healing lanes.

What Cockpit Central centralizes

The product is deliberately operational: calm enough for daily work, complete enough for forensic repair.

Data views

Project definitions, product files, bracket inventories, stages, API links, assets, support tickets, and machine setup data.

Workflow control

Hourly and manual workflows, role-aware tasks, sound state, progress bars, queues, and script visibility.

Deployment readiness

Setup, maintenance tools, Git/GitHub preparation, Cloudflare publish gates, and machine-specific installation checks.

Human context

World clocks, travel/stage status, homes, people, and the signals that keep technical work grounded in real life.