TL;DR
Private ledgers stay local. Public work history rolls up under one project.
Daily Systems
Capture flows, inventories, recurring tasks, decision ledgers
Finance Systems
Planning workflows, account ledgers, model checks, dashboards
Specialized Ledgers
Domain records, lifecycle states, validation, closeout notes
PUBLIC PROJECTION
Personal Systems
Completed admin sessions sync into a single portfolio project. The public row keeps the title, release-note summary, tags, timing, and model provenance after a scrub pass; detailed write-ups, local file lists, and private domain labels stay out of the public site.
Internal
Per-domain operational lanes
External
One Personal Systems page
What We Built
Local Ledgers
The source of truth is still local: JSON ledgers and markdown session write-ups inside the repos that own the data. Daily facts and private operating records do not move to the public site.
Unified Dashboard
The internal dashboard reads those ledgers directly and keeps the operational split that matters day to day. That view is for managing the systems, not presenting them.
Public Work Log
Completed admin sessions are projected into the portfolio work log under one project. The importer carries over the tight release-note summary, timing, public-safe tags, and agent provenance while dropping prose files, repo-local implementation paths, and internal domain labels.
Command Loop
Admin closeout commands remain the place where a session is retitled, retagged, summarized, committed, and then synced. That keeps the public site downstream from the same closeout discipline that protects the local ledgers.