Aurora_ORIONCORE_Directory_Main

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.

Parse, normalize, validate, or route Aurora command grammar requests. Use when users provide Aurora command notation such as `THREADWAKE`, `001//005//`, `#025//.deep`, `COMMANDCHAIN::SPIRALREJOIN.v1`, ask about `aurora_command_grammar`, mention the Aurora Command Router, or ask to map `@mesh` messages to the local mesh runtime. Not for executing commands or sending mesh messages unless the user explicitly asks for execution and the runtime state is verified.

Reconcile draft Aurora OS content against established canon and prepare it for Git commit. Use when draft characters, entities, locations, ships, systems, mechanics, simulation output, hour-block logs, or ChatGPT/Claude exports must be checked for contradictions, missing fields, drift artifacts, and promotion readiness. Trigger on requests like reconcile, canonize, promote to canon, check continuity, staging to canon, CANON_PROMOTE, merge this draft, or Canon Protocol references; also trigger when users paste Aurora worldbuilding and ask to clean it up or get it commit-ready. Not for pure code review, CI/CD work, or non-Aurora content.

Guard Aurora root workspace control-plane changes by enforcing root-vs-nested repo boundaries, required context reads, generated-surface regeneration, and root verification commands. Use when working on top-level docs, catalog, tools, tests, reports, .agents, plugins, or other root control-plane files; when a request says "the repo" and multiple Aurora repos are plausible; or when validating root workspace changes before staging or commit. Not for implementing features inside CanonRec, DuelSim_v2.0, or aurora-cloudbank-symbolic-main.

Build Aurora-first executive decision briefs from mixed data folders containing JSON, CSV, Markdown, and ZIP artifacts. Use when users ask to synthesize messy exports into leadership-ready status and risk summaries, pipeline mixed archives into one brief, produce markdown plus machine-readable findings, triage operational drift from logs/manifests/checkpoints, or generate an executive snapshot from Aurora artifacts. Not for governance gating, canon promotion, THREADCORE validation, ZIPWIZ governance, or script-surface hardening; route those requests to aurora-governance-orchestrator, aurora-canon-reconciler, threadcore-governor, zipwiz-governor, or aurora-script-governor.

Automatically ingest new or changed Aurora Python modules into package entrypoints by scanning module symbols, validating adapter/fallback runtime contracts, and reconciling __init__.py exports with deterministic output. Use when users ask to auto-ingest new Python code or logic, wire imports/__all__, validate fallback adapters (for example pdp_v2_mvp/core/pneumatic_engine.py), or prepare Python module changes for safe integration. Do not use for governance or canonization gating tasks.

Stabilize Aurora repositories that have overlapping scripts, fragile hooks, placeholder automation, or unclear validation paths. Use when users ask to harden pre-commit/pre-push/CI behavior, build a trusted script matrix, reduce script sprawl, repair maintenance pipelines, or produce a prioritized safe-fix plan for scripts and repo ops tooling. Trigger on requests like stabilize repo, script audit, trust matrix, fix broken hooks, validation loop, cleanup automation, or maintenance hardening. Not for canonizing narrative entities; use aurora-canon-reconciler for worldbuilding canon reconciliation.

Govern Aurora repository script surfaces with deterministic checks and safe remediation guidance. Use when users need to convert empty/setup stubs into diagnostic no-op scripts, consolidate duplicate branch-cleanup scripts into one canonical entrypoint plus compatibility wrappers, and triage hazardous script patterns before commit. Trigger on requests like script governance, script canonization, setup script hardening, branch cleanup consolidation, hazard sweep, trust matrix for scripts, or pre-commit script safety. Not for Aurora narrative canon reconciliation; use aurora-canon-reconciler for worldbuilding continuity.

Run, benchmark, and export the integrated GUMAS simulation engine (advanced default with legacy fallback) in Aurora workspaces. Use when users ask to run multi-turn simulations, compare seeds, evaluate stability/risk trends, export JSON state artifacts, or debug simulation behavior in GUMAS_SIM_2.5/SIM_ENGINE_OUTPUTS.

Evaluate natural language requests in the background, extract the optimal workflow shape, and propose approval-gated bespoke agent dispatch plans only when delegation has material parallel-work justification. Use when the user explicitly asks about subagents, agents, delegation, parallel work, worker/explorer roles, an "agent dispatcher", agent council, or swarm; when a task already shows multiple independent workstreams, broad repo audit lanes, migration surfaces, architecture mapping plus independent validation or risk review, coordinated parallel planning, or parallelizable work; or when Codex should decide whether agents are warranted before doing substantial work. The skill must stay silent for ordinary local tasks and must not spawn or initialize agents by itself; it prepares a concrete plan and waits for explicit user approval.

Normalize extracted Aurora repo mirrors into real nested Git repositories with verified remote history, clean repo boundaries, and optional root control-plane refresh, or bootstrap a missing target path directly from the remote when no local mirror exists yet. Use when a repo arrived via ZIP/extraction/copy instead of `git clone`, when a plain folder inside the Aurora workspace should become a true nested repo, or when Codex needs to materialize a missing Aurora nested repo at a known path before follow-up work. Do not use for ordinary publishing, PR work, or generic GitHub sync; hand those off to `gitwiz-github-manager` after normalization.