Products / Product Academy

Understand the authority before you operate a Desk.

This is the public-safe documentation map for Diary, Dossier, Home, DAM, GAS, Hub, Reach, Brand, Experience, Lab and Edu, plus the shared Cockpit Central application. It explains what each product owns, how the products cooperate, and where to find the current reference without exposing private archives or credentials.

Know the authority Read the signal Act deliberately Verify the result
11 + 1eleven governed products and one shared operating application.
24active Cockpit Pulse definitions from the current registry.
1 authorityper fact, configuration, workflow, and release.
Public safeprivate paths, identities, evidence, and credentials stay private.
Product map

Eleven products, one calm operating model.

Search by product, responsibility, or capability. Cockpit Central remains the shared application that operates the products.

Public reference reviewed 2026-08-15.

1

Diary

Life archive and workflow discipline

Diary gives files and media a durable place in time. It governs intake, naming, life-stage context, archive structure, workflow execution, and evidence trails.

  • Capture and intake
  • Naming and bracket fields
  • Life stages and evidence
  • Hourly and manual workflow
Open Diary overview
D

Dossier

People, relationships, and context

Dossier preserves the human explanation around evidence: who was involved, which account or provider supplied it, and which conversation gives it meaning.

  • People and identities
  • Correspondence and mail
  • Provider takeouts
  • Relationship context
Open Dossier overview
H

Home

Smart-home authority and evidence

Home connects properties, rooms, devices, telemetry, cameras, snapshots, and automations while keeping provider bridges and local credentials inside clear boundaries.

  • Homes, rooms, and devices
  • Telemetry and last state
  • Camera evidence
  • Provider bridges
Open Home overview
M

DAM

Media, metadata, and provenance

DAM keeps images, video, audio, documents, metadata, derivatives, and source evidence coherent even when file formats expose different capabilities.

  • Metadata and GPS
  • Sidecars and visible codes
  • Conversion and previews
  • Source provenance
Open DAM overview
G

GAS

Google automation and API authority

GAS operates Google-side menus, imports, APIs, spreadsheet workflows, and reviewed synchronization into durable local authority tables.

  • Apps Script menus
  • OAuth and API setup
  • Spreadsheet automation
  • Provider synchronization
Open GAS overview
U

Hub

Publishing, releases, and public delivery

Hub turns approved product knowledge into governed websites and releases. It owns GitHub-to-Cloudflare publishing, domains, consent, analytics, and public intake services.

  • Git and GitHub releases
  • Cloudflare Pages and D1
  • Public website standards
  • Consent and analytics
Open Hub overview
R

Reach

Channels, publishing, and response

Reach governs social profiles, publication queues, channel-specific media, immutable evidence, engagement metrics, responses, and provider access boundaries.

  • Channel inventory
  • Post and reel variants
  • Metrics and reactions
  • Response workflow
Open Reach overview
B

Diary Brand

Corporate identity and brand authority

Diary Brand governs how Diary Suite looks, sounds, teaches, labels, approves, and expresses itself in digital and physical form.

  • Visual identity
  • Voice and vocabulary
  • Assets and training
  • Diary Merch and approvals
Open Diary Brand overview
X

Diary Experience

Human-centered product quality

Diary Experience turns findability, clarity, task success, accessibility, trust and satisfaction into governed product evidence.

  • Usability and UX research
  • Menus and information architecture
  • Accessibility and interaction
  • Reversible changes and retest
Open Diary Experience overview
L

Diary Lab

Governed testing and learning

Diary Lab turns voluntary testing into a governed path from application and Core approval through cohorts, assignments, evidence, feedback, and accountable learning.

  • Voluntary applications
  • Core-reviewed enrollment
  • Cohorts and assignments
  • Evidence and feedback
Open Diary Lab overview
E

Edu

Governed learning and credentials

Edu turns subject expertise into reviewed learning journeys, course versions, assessments, feedback and verifiable credentials.

  • Learning design
  • Course authoring and review
  • Assessment and feedback
  • Credentials and improvement
Open Diary Academy
C

Cockpit Central

Windows command and observability surface

Cockpit Central exposes the product authorities without replacing them. Desks provide detail, Pulses summarize change, and commands launch controlled actions.

  • Desks and previews
  • Pulses and weather
  • Role-aware workflows
  • Setup and release readiness
Open full Cockpit reference
Shared rules

The concepts that keep every lane consistent.

Authority

Every governed fact has one editable source. Mirrors, caches, deployment folders, and reports may carry it, but they do not compete with it.

Evidence

Plans, provider imports, device signals, metadata, and verified presence have different confidence. Diary keeps the difference visible.

Machine roles

Core, Full, Maker, and Client describe permitted behavior. Manual and scheduled runs can have different gates without creating parallel code.

Intake

New files enter known queues, receive format-appropriate metadata, and move through reviewed stages before joining an archive or library.

Deployment

Development, source history, validation, release, and installation are separate gates. Internal deployment storage is never a public download authority.

Open Apps Ready

Privacy

The public Academy explains the model. Private archives, credentials, person-level compliance evidence, and machine-local state stay outside the public site.

Portfolio discipline

New integrations do not automatically become products.

Graduation criteria

A product needs its own editable authority and data contract, governed documentation, governed source, independent user value, and a release/support lifecycle. A Desk/Pulse pair is required when Cockpit Central operates it.

Contextual identity

The complete line appears only on portfolio-level surfaces. Individual products and channels use Diary {Product} | Part of Diary Suite, keeping the relationship visible without turning every footer into a product catalogue.

Documentation policy

Current reference first; history remains evidence.

Public Product Academy

Curated, privacy-safe, and linked to current product behavior. This is the readable reference for users, reviewers, and the Diary Pulse website viewer.

Private offline Academy

Detailed implementation notes, audit evidence, repair lessons, historical decisions, and machine-specific material. It is broader by design and is never published wholesale.

Help & guidance

Start with the outcome, then follow the product boundary.

Choosing a lane

Catalog explains each governed product. Capabilities explains the rules shared across products. Operating Surfaces shows how people work with them. Lifecycle & Licensing explains when an idea becomes a supportable offering.

Need something that does not exist?

Send a Product Request through Signal. Diary Athanor can route the demand into Discovery without presenting an unreviewed idea as a finished product.

Send a product signal