Skip to content

hashgraph-online/awesome-codex-plugins / plugins/boshu2/agentops/skills/orchestrate

orchestrate

Verified

Dispatch parallel workers without write collisions and decide what idle or finished ones do next. Use when: managing agents, or running or planning agents in parallel, even two.

references/session-associations.md

View on GitHub
# Session associations

AgentOps work and runtime identity guidance.

## Work-to-session associations

The caller passes work identity at dispatch/start before execution can fail,
and records the dispatch reference in native work comments/metadata or existing
runtime facts. At startup, record observed identity in that caller-owned channel
before substantive work, independently of final handoff. These are versioned
facts under their source owners, not a new AO association database, lifecycle,
packet schema or permanent writer. Core skills return facts; tracker mutation
requires the caller's authority. No memory/evidence file belongs in a consumer
checkout by default; requested CDLC evidence uses owner-selected protected
external non-Git storage.

Keep these facts distinct in the native record or its permitted evidence:

| Fact | Required distinction |
|---|---|
| Source work | Backend/store identity, database/project identity where available, native work ID and permitted source revision/intent locator; a bead ID alone or workspace basename is not globally unique. |
| Execution | Selected runtime and requested model/ID separately from actual observed model/session/context IDs; absent observations are explicit unknowns, never synthetic UUIDs. |
| Relations | Native parent, dispatch controller and resume predecessor are separate links, each with its observation source. Record the selected runtime's actual resume identity even when it reuses a session ID. Unknown is distinct from an observed absence of parent. |
| Provenance | Who or which runtime observed the fact, when, through which native operation/record, and its permitted locator. Caller-supplied facts remain labeled as supplied; do not upgrade inference to observation. |
| Work span | Only the source interval supported by explicit work/start/switch observations. Where frozen byte offsets are available use half-open `[start, end)` ranges tied to that source identity/digest. A search line is a locator, not an inferred byte boundary. |

For a child, pass its work identity before launch, then record the child's
observed ID and independently supported parent link at startup. For resume,
retain the predecessor reference and add the observed resume relation; a
requested resume ID does not prove a resumed execution. Workspace adjacency,
matching task titles, filenames and guessed line numbers establish neither
identity nor parentage. A native session can cover multiple work items: record
only supported spans for each, preserve unrelated and unassigned spans, and
leave an unknown end unknown until an observation supports it. Never assign a
whole session to a work item because one hit names that work.

If launch, startup observation or native recording fails, retain the caller's
pre-execution record, available bounded failure facts and explicit unknowns;
report any recording gap. Recovery reopens permitted startup/native sources
without depending on a final handoff, preserving earlier failures/unknowns as
history when later observations resolve them. Do not fill gaps with invented
IDs, inferred edges or unrelated source spans.

All metadata follows source-owner and recipient/model/destination authorization,
including locators, native comments, filenames and diagnostics. BD/Dolt is
versioned and is not a secret store. Use permitted opaque locators rather than
restricted paths/excerpts or credentials; opacity grants no clearance. Check
access before resolving a locator, never retrieve denied bytes and redact later.

Association is not coverage: CASS discovery, `view`/`expand` windows and tool-call
mining do not prove full prose/outcome reading. Preserve missing sources and
unknown lengths, never zero or an excerpt's digest presented as the full
source. Frozen bounds/digests identify available evidence; they do not
prove bytes were emitted, delivered to the host or semantically processed.
Head/tail excerpts leave the middle unread; new tails or children belong to a
later observation, not a rewritten completed denominator. No AgentOps command
verifies coverage, and an association supports no acceptance claim.

reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall