Local Media Desk documentation
Developer guides, implementation references, and the operator manual for Local Media Desk.
Build with understanding.
Operate with evidence.
Developer guides explain the system and how to extend it. The operator manual covers daily workflows, administration, and recovery. Choose the reading path for the work you need to do.
Building the platform
Start as a developer
Get access, set up locally, understand the system, and make your first contribution.
Developer handbook
Architecture, data model, domain walkthroughs, and contribution patterns. Developer access required.
Implementation reference
Browse source-derived APIs, database tables, jobs, permissions, and packages. Developer access required.
Common operator tasks
Check production health
Build a release manifest and assess each production boundary without changing it.
Respond to an incident
Classify, stabilize, communicate, recover, and close with durable evidence.
Release or roll back
Verify the coordinated release chain and understand what a traffic rollback cannot undo.
Run Local Media Desk workflows
Trace account research through planning, fulfillment, creative delivery, and results.
Operate Seiche
Run and troubleshoot the civic product within Local Media Desk.
Access and recovery
Understand break-glass requirements and how to restore an operator account or documentation grant.
Find an operational answer
Administer the platform
Manage workspaces, people, access, readiness, evidence, and cost boundaries.
Operate integrations
Identify provider ownership, credentials, connector health, jobs, and schedules.
Troubleshoot by symptom
Start from the observed failure and follow evidence to the responsible boundary.
Use the reference shelf
Look up permissions, states, topology, jobs, interfaces, and configuration sources.
How to read operational claims
Canonical pages show an operational state, accountable role, backup role, and verification date when one exists. Requires verification means the procedure or an external prerequisite has not been exercised by a backup operator. A Git commit date proves only that the source changed.
Repository evidence is not production evidence
Code can prove that a control or procedure exists. It cannot prove that an account is funded, a credential is installed, an alert reaches someone, a backup restores successfully, or the expected release is serving traffic. Those claims require current control-plane evidence or a recorded drill.
Access follows authorization
Navigation, search, Markdown export, and page rendering use the same current Local Media Desk authorization decision. Signing in reveals only the pages your workspace and platform grants allow. Authorization is a page property—not the way this manual is organized.
Manual access model
How page access, search, Markdown, and repository sources work.
Client guidance
Workspace reviews, decisions, and administration for client teams.
Engineering reference
Architecture, runbooks, and decisions that support—but do not replace—canonical operator guidance.
Sign in
Use your current Local Media Desk identity and grants.
Last updated on