cyberAlchemyAI

Use when deciding whether work merits a governed multi-agent dispatch and, when it does, proposing, tension-checking, confirming, registering, running, closing, and observing that dispatch through repository-local bindings.

Use when deciding whether work merits a governed multi-agent dispatch and, when it does, proposing, tension-checking, confirming, registering, running, closing, and observing that dispatch through repository-local bindings.

The design principle behind Principle 5 (pairwise tension) of the subagents-strategy constitution. Use when designing the angle set for an n≥2 subject group (role investigate or evaluate) so the agents' micro-vectors are structurally opposed and their correlated bias cancels under composition — not merely non-overlapping. This is the design/theory layer; check-tension is the executable gate that enforces it before the human confirm.

Use when: building a compact, task-ready context pack from selector-level evidence and obligation-linked excerpts.

Route repository work through installed Arcanum capabilities and execute validated capability-bound dispatches through host-native operations.

Route repository work through installed Arcanum capabilities and execute validated capability-bound dispatches through host-native operations.

Use when: validating or designing an Arcanum dispatch route that chains sigils, spells, owner capabilities, handoffs, gates, observability, techniques, and optional boundary/evidence contracts.

Route repository work through installed Arcanum capabilities and execute validated capability-bound dispatches through host-native operations.

Govern authoritative references for research projects: enforce immutable pins, waiver lifecycle, ledger consistency, and inventory linkage before G2/G3-sensitive execution.

Guide any research experiment bundle to completion using staged AskQuestions decision packs, gate checks (G1-G4), adjudication closure, and claim-status propagation.

Emit structured MARS telemetry signals after startpoint, discovery, planning, execution, analysis, adjudication, or retrospective work. Use for workflow gaps, contract gaps, evidence gaps, decision friction, overhead, proposals, and reusable patterns that should inform later reflection.

Build the project-level research foundations baseline before protocol design by producing domain context, methodology/theory synthesis, source catalog updates, reference-ledger updates, and library-grade inventory coverage.

Normalize a brownfield research project to the MARS knowledge-stack contract using dependency-ordered waves across definitions, references, context bundles, inventory, and experiment artifacts.

Unified MARS startpoint. Detect greenfield or brownfield scope, run discovery, scaffold a repository-valid research project baseline when needed, and enforce structural readiness before protocol design or execution.