Platform View

Documentation is adapted for macOS.

Shell commands, launchd paths, and Apple runtime guidance

CLI Version Context

Installed CLI: 1.1.0 (latest compatibility profile)

Support Bundle

Capture a complete diagnostics artifact for support triage.

macos
OUT=~/Desktop/opta-support-$(date +%Y%m%d-%H%M%S).txt; { echo "# Opta Support Bundle"; echo "# Generated: $(date -u +%Y-%m-%dT%H:%M:%SZ)"; echo; opta doctor; echo; opta daemon status; echo; opta daemon logs --lines 200; echo; opta config list; } > "$OUT" && echo "Saved $OUT"
Support FAQ

Learn About

Deep workflow guides aligned to this documentation section.

Opta Local Architecture

Opta Local operating model, architecture, and execution surfaces.

general

Opta CLI Masterclass

Deep command workflows, session control, and production operator patterns.

cli

Opta LMX Masterclass

Advanced LMX runtime behavior, memory strategy, and performance tuning.

lmx
Browse all Opta Learn guides

Change Impact Workflow

The change-impact workflow converts a natural-language change description into a ripple-effect checklist across runtime layer docs, web surfaces, logos, and release nodes.

Workflow Goal

Prevent stale ecosystem content after shipping changes. Instead of manually guessing what to update, follow the canonical workflow and registry map in content-sync-map.

When to Run

  • Any runtime layer feature or behavior change (CLI, daemon, LMX, Init, Code)
  • Any logo or brand-asset update
  • Any release cut, channel move, or deployment URL change
  • Any app add/remove/rename in the ecosystem

Required Inputs

The workflow depends on these canonical files:

content-sync-map inputs
docs/content-sync-map/registry/apps.yaml
docs/content-sync-map/registry/logos.yaml
docs/content-sync-map/registry/content-nodes.yaml
docs/content-sync-map/workflow/change-impact.md

Workflow Steps

  1. Identify affected app IDs from the change description.
  2. Filter content nodes by describes and matching stale_when conditions.
  3. If logos changed, include all files in referenced_in as mandatory updates.
  4. Group checklist output by surface (Help, Learn, Status, Home, Init, etc).
  5. Prioritize as MUST, SHOULD, and CONSIDER.
No skip path for logo references
Logo changes are always MUST-update items for every file listed in registry/logos.yaml under referenced_in.

Output Checklist Shape

Keep checklist output file-specific and reason-tagged. Example structure:

change-impact checklist format
## Update Checklist - [Change Description]

### MUST Update (direct impact)
- [ ] path/to/file - reason

### SHOULD Update (stale conditions match)
- [ ] path/to/file - reason

### CONSIDER Updating (indirect impact)
- [ ] path/to/file - reason

Quick Start

Use the workspace slash command /sync-check or request: "Run change-impact workflow for: [your change]".

Related page: Synergies.

Previous
Synergies
Next
Overview