Orchestrate Aurora governance scanners into one deterministic promotion verdict with merged findings and remediation. Use when users ask for full governance preflight, one report for readiness, unified go/no-go gating, cross-domain drift checks, or orchestration across threadcore-governor, zipwiz-governor, aurora-script-governor, aurora-narrative-tone-governor, aurora-repo-stabilizer, and optional aurora-canon-reconciler draft validation.
Canonical-source-first governance scan for Aurora narrative outputs. Use when users ask to run a narrative linter, tone/cadence governance check, anti-flourish validation, or LLM writing style audit against ORION rules (R1-R6, LINT-NARR-001..006, CTL P001+), and return findings-only pass/review/block results without rewriting.
Run Quantum Forge engine operations for Aurora by validating GUMAS v3.0 Forge modules, executing deterministic engine turns, generating/verifying ORION capsules, and producing leadership-ready Markdown plus machine-readable JSON run artifacts. Use when users ask to operate or diagnose Quantum Forge runs, produce Forge execution reports, run charforge capsule operations, or correlate QUANTUM_FORGE manifest/vector context with live engine signals. Do not use for governance gating, canon promotion, or continuity reconciliation.
Build selective-integration capsules for Aurora by triaging external kit/archive modules into include, backup_only, or reject decisions with deterministic criteria, specialist routing notes, and rollback-ready canonization metadata. Use when users ask to absorb parts of a ZIP/archive safely, run selective integration, create or validate selective integration capsules, map modules into integration paths, or apply the Aurora_SelectiveIntegrationProtocol_v2.5 workflow. Not for broad governance preflight or THREADCORE/ZIPWIZ audits; route those to aurora-governance-orchestrator, threadcore-governor, zipwiz-governor, aurora-script-governor, or aurora-canon-reconciler.
Scan Aurora project trees and map code, logic, modules, scripts, and docs to the best-matching Codex skills with deterministic, precision-first scoring. Use when users ask to find which skill applies to a repo/path, surface skill-to-module routing, build a skill coverage map, reduce skill selection ambiguity, or audit where existing skills should be used before implementation. Not for implementing feature code directly, governance promotion verdicts, or canon reconciliation itself.
Govern THREADCORE artifacts with deterministic validation, diagnostics, and L3 bridge outputs. Use when checkpoint manifests, continuity logs, payload or capsule JSON, delta-chain records, or THREADCORE beacon and THREADREFLECT markdown blocks must be validated for required fields, ethics and anchor integrity, identity continuity, and remediation readiness. Trigger on requests such as validate THREADCORE, audit threadcore artifacts, check continuity bundle, beacon lint, drift governance review, produce THREADCORE diagnostics, or generate L3 bridge entities from THREADCORE materials. Not for broad repo script hardening or non-THREADCORE canonization.
Manage Git and GitHub operations for the Aurora / ORIONCORE workspace with project-specific safety rules. Use when users ask to configure remotes, create GitHub repos, scan local-vs-remote drift, draft PR packets, publish branches, back up or replace bootstrap GitHub history, push root or nested repos, diagnose auth/SSH issues, or perform repo-aware GitHub setup across the root control-plane repo and named nested repos. Do not use for general code changes, CI failure debugging, or PR comment handling unless the task is primarily about repo publishing and remote state.
Govern ZIPWIZ packaging and export artifacts with deterministic validation, remediation reporting, and evolution mapping. Use when bundle manifests, staging manifests, ZIPWIZ packaging protocol docs, beacon capsule JSON, or ZIPWIZ runtime alignment evidence must be checked for anchor and ethics integrity, structural drift, and timeline continuity. Trigger on requests such as validate ZIPWIZ artifacts, audit zipwiz packaging, check zipwizard export manifests, generate ZIPWIZ evolution timeline, or produce ZIPWIZ governance diagnostics. Not for broad script hardening, CI stabilization, or THREADCORE artifact governance.