dotagents

OLD NAME:Composition Decompose Skill

STATUS:

Purpose

Enable agents on this Android terminal to autonomously browse, classify, and decompose composition recordings into structured Process Definition Entities (PDEs). This skill bridges the gap between raw voice recordings captured via Pixel Recorder and actionable, routed work items that can feed into the chronicle and episode workflows.

Tools

composition-browser (bash script)

Interactive terminal UI for browsing and acting on compositions.

Location: ~/bin/composition-browser Requires: composition (@miadi/composition), fzf, jq Optional: transcription (@miadi/transcription), miaco (mia-co)

Subcommand Usage Purpose
(none) composition-browser Interactive fzf picker with live previews
list composition-browser list List all composition slugs
show <slug> composition-browser show ep108-... Observe + classify + transcription
segments <slug> composition-browser segments ep108-... Transcription segment breakdown
decompose <slug> composition-browser decompose ep108-... [--run] [-e claude] Delegates to miaco decompose composition

miaco decompose composition (Node.js CLI)

The decomposition engine. Reads compositions, classifies transcriptions, routes to strategies, and optionally runs LLM decomposition to produce PDEs.

Location: $PREFIX/bin/miaco (symlink to mia-co npm package) Version: 0.13.0

Option Purpose
--dry-run --run Preview what would be decomposed without calling engine
--run -e claude Run decomposition using Claude (sonnet) as engine
--run -e hermes Run decomposition using local Hermes agent
--segments Show transcription segment breakdown
--full Show full segment text (not just gists)
--json Machine-readable JSON output
--index <n> Process only one transcription at index n
-s <strategy> Override strategy: standard, iterative-refinement, adversarial-consensus
-w <path> Override PDE working directory (default: ~/.pde/)
--parent <uuid> Nest PDEs under an existing PDE
--force Process compositions classified as unsafe-or-ambiguous

Composition Root

COMPOSITIONS_ROOT="${COMPOSITIONS_ROOT:-$HOME/compositions-nyro}"

Each composition folder contains composition.json with metadata, transcription text files, and optional audio clips.

PDE Output

PDEs are written to ~/.pde/<YYMMDDHHmm>--<uuid>/ with:

Workflow: Decompose a Composition

1. Discover available compositions

composition-browser list

2. Inspect a composition (non-destructive, offline)

composition-browser show <slug>
# or equivalently:
miaco decompose composition ~/compositions-nyro/<slug>

This prints: form classification, intent, segment moves, routing strategy — all without calling any engine.

3. Dry-run to preview decomposition plan

miaco decompose composition ~/compositions-nyro/<slug> --dry-run --run -e claude

Shows the prompt size and strategy that would be used, without spending tokens.

4. Run actual decomposition

miaco decompose composition ~/compositions-nyro/<slug> --run -e claude

Produces PDEs in ~/.pde/. Each transcription in the composition gets its own PDE.

5. Review PDE outputs

ls ~/.pde/
# Read a specific PDE:
cat ~/.pde/<folder>/pde-<uuid>.md
# Or inspect structured data:
jq . ~/.pde/<folder>/pde-<uuid>.json

Routing Strategies (automatic)

The decomposer routes each transcription based on its form and segment structure:

Route Strategy When
direct standard Short, clear intent — single-pass decomposition
layered iterative-refinement Long monologues/journals — multi-pass to preserve thinking
(adversarial) adversarial-consensus Manual override only — cross-checks via opposing passes

Design Principles

  1. Read-only on compositions — miaco never writes to the composition folder. PDEs land in .pde/.
  2. Offline-first — Classification, segmentation, and routing need no API. --run is opt-in.
  3. 32KB prompt ceiling — Full text for most transcriptions; segment gists for very long ones.
  4. Musician ownership — The composition belongs to whoever recorded it. Decomposition is a separate concern.

Engines Available on This Device

Engine Notes
claude Uses Claude sonnet via API (default for --run)
hermes Local Hermes agent (haiku-based, see ~/src/hermes-agent/)
ollama Local Ollama if running
pi Pi coding agent

Known Observations (from v0.13.0 testing)