1. Deployment Portfolio & Search
Press ⌘ K to search across all customer deployments by name, project slug, or hosting type. Filter by Active, Provisioning, or Blocked status directly from the toolbar dropdown.
2. Bootstrap a New Customer Project
Click "New deployment" in the top header. The 3-step wizard provisions an isolated customer workspace from canonical roadmap templates. In remote production, customer workspaces use the GitHub-backed repository; local filesystem paths and local Git commands apply only to development or explicitly local-mode workflows.
3. Artifact Browsing & In-App Editing
Select any customer deployment to open the Artifacts pane. Review Milestones 0–10, requirements intakes, and working session logs. Click "Save artifact" to persist with atomic locks and ETag optimistic concurrency, or "Save & commit" to stage and record a Git snapshot.
4. Git Repository Check-Ins & Sync
Click "Commit changes" to stage all modified files and record a signed Git commit with the operator's identity. Click "↻ Refresh" to re-scan the customer workspace. In remote production, status, refresh, artifact reads, and commits use the GitHub-backed workspace; local filesystem wording applies only to development or explicitly local-mode workflows.
5. Granola Meeting Ingest & Redaction
Click "Import Granola" to map meeting notes into milestone files. The backend automatically strips credentials, API keys, passwords, and personal chatter before saving.
6. Roadmap Template Synchronization
Click "Sync templates" to calculate diffs against upstream crogl-roadmap-to-production/templates/ and reconcile changes while strictly preserving customer-specific custom notes.
7. Deployment Overview
Select a customer and open the Overview tab. The rendered overview starts at Executive Summary; YAML frontmatter is hidden from the readable body. The compact metadata row shows status, freshness/last refresh time, source snapshot, source-commit availability, ETag, and refresh actor/provenance.
The rendered Overview is a presentation layer for overview.md. Complete raw Markdown—including YAML frontmatter—remains available in Artifacts and in the API response; rendering does not rewrite either source.
Click "↻ Refresh overview" for an operator-only manual refresh. It collects bounded, redacted workspace evidence, generates and validates a candidate, then writes only after validation. The UI reports Loading, Refresh complete, No changes detected; overview is current., Conflict (409), 401 authentication required, 403 operator permission required, 404 missing overview or endpoint, and 503 refresh failed; last good overview preserved. A missing overview.md is an expected first-generation condition: the first successful refresh creates it, while a missing refresh endpoint is a separate routing/deployment failure.
Automated refreshes preserve the complete Owner Notes section verbatim. Material claims and recommendations retain provenance through source paths and section/line references, commit SHAs, PR URLs, or approved meeting-note provenance; source snapshot, source commits, and ETag identify the evidence and stored version.
Cloud Scheduler currently runs with dry_run:true and must not call the GitHub write path, so there are no scheduled production writes. Broad scheduled writes remain NO-GO until the documented pilot, idempotence, Owner Notes, SHA-protected write/read-back, and weekday-cycle gates pass.
8. Access and Permissions
Authenticated Crogl users with viewer access may list deployments, read artifacts and overviews, view Git status/activity, and preview template differences. The cs-operator role is required for mutations such as manual overview refresh, artifact writes, bootstrap, commits, template-sync apply, and meeting imports.
A viewer without cs-operator must not receive an operator-permission error for read-only workspace views. A 401 indicates missing or expired authentication; a 403 on a mutation indicates insufficient authorization.