Private systems. Public standards.
A cockpit for life, archives, automation, and publishing.
The Diary system connects Diary, Dossier, DAM, GAS, and HUB: a disciplined way to preserve memory, understand context, automate work, and publish cleanly.
Capture
Classify
Preserve
Automate
Publish
Cockpit Central
The Windows command surface for the whole system.
Cockpit Central brings desks, pulses, workflows, files, API status, deployment checks, and self-healing signals into one visible operating surface.
One System, Five Product Lanes
Each lane has its own job, but they work together as one operating model.
Why this exists
The world is messy. The system gives it places to land.
Files, photos, trips, homes, machines, contacts, scripts, APIs, and websites all become easier to trust when they have names, owners, versions, and visible rules.
Creator Editorial
Built by someone who needed the system to survive real life.
I built the Diary system because private life produces more evidence than memory can responsibly hold. Photos, conversations, trips, homes, scripts, APIs, and websites all deserve structure before they become noise.
Diary preserves the lived proof. Dossier keeps people and context readable. DAM protects media and metadata. GAS automates the parts that should not depend on memory. HUB makes the public surface publishable. Cockpit Central is the place where all of that becomes visible enough to operate.
The goal is not a louder system. The goal is a calmer one: authority where authority is needed, automation where automation helps, and human judgment where human judgment still matters.
Meet the Team
Two people, one AI teammate, and an operating system for a life that moves.
Schmallegger is personal by design. The public layer introduces the human and AI team behind the Diary system while the private evidence stays protected in Dossier.
Leopold Schmallegger
Creator and product owner of the Diary system, with a professional track across ERP, automation, archives, property operations, and web publishing.
Diane Schmallegger
Education, learning design, maker perspective, and real-world usability for a system that has to work for people, not just machines.
Team AI
Codex-supported collaborator for the Diary system: translating human intent into cleaner software, better audits, readable pages, and practical Human-AI operating habits.
Public Network
Three public sites, one operating logic.
The public Schmallegger network separates system, real estate, and travel so each surface stays clear while still pointing back to the same Diary system discipline.
SL
Schmallegger
The public home for the Diary system, its product lanes, team, proof, and privacy.
www.schmallegger.netPE
PoldiEstates
The public real-estate and 0R operations surface for a small, curated property lane.
www.poldiestates.comSW
SchmallWorld
The travel, stage, lifestyle, culture, and perspective lane.
www.schmallworld.netProof Signals
Early evidence from the system, framed without pretending to be public customer testimonials.
Privacy first
The public site stays small by design. Sensitive archive work remains private unless explicitly published.
Cloud ready
HUB now separates source authority, local Git working copies, and Cloudflare deploy roots.
Human readable
The system is allowed to be technical, but the public surface must remain calm, clear, and understandable.