rudironsoni/OrlixSystem

orlix-tcti-next-step

Orlix TCTI next-step agent harness. Use when continuing TCTI work, running the harness, choosing the next gate, or coordinating planner and safety review.

orlix-tcti-safety

Orlix TCTI safety agent harness. Use for App Store, x18, JIT, MAP_JIT, RWX, PROT_EXEC, HostAdapter, defconfig, generated-tree, or physical-device preflight checks.

orlix-tcti-golden-elf

Orlix TCTI golden ELF agent harness. Use for golden ELF listing, validation, hash checks, ELF shape inspection, and switch-debug execution reporting.

orlix-tcti-oracle

Orlix TCTI oracle agent harness. Use for switch-debug, golden ELF, decoded semantics, reducers, and no-phone execution proof.

orlix-tcti-plan-consistency

Orlix TCTI plan-consistency agent harness. Use for ADR, PLAN, IMPLEMENT, defconfig policy, and stale-reference checks.

orlix-tcti-report-reader

Orlix TCTI report-reader agent harness. Use to read report JSON, validate schema facts, and expose report fields without arbitrary shell behavior.

orlix-tcti-reproducer

Orlix TCTI reproducer agent harness. Use to read reducer artifacts, replay reducers, and validate actual status against expected status.

orlix-tcti-debug

Orlix TCTI debug agent harness. Use for LLDB, disassembly, ELF, Mach-O, crash, instruction encoding, objdump, readelf, sections, symbols, or relocations.

orlix-tcti-status

Orlix TCTI status agent harness. Use to read TCTI report JSON, summarize pass/fail/todo/evidence state, and identify stale or missing reports.

orlix-codex-handoff

Use for long Orlix sessions, compaction risk, archival, handoff to another agent, or any request to continue work from conversation history.

orlix-dynamic-workflows

Use when Orlix work may benefit from explicit workflow packets, subagent orchestration, or independent research, implementation, test, and review tracks.

orlix-session-lessons

Use when deriving lessons from an Orlix conversation, correcting agent behavior, improving harness reliability, or turning a derailed session into durable repo-local guidance.

rulesync

Generates and syncs AI rule configuration files (.cursorrules, CLAUDE.md, copilot-instructions.md) across 20+ coding tools from a single source. Use when syncing AI rules, running rulesync commands, importing or generating rule files, or managing shared AI…

orlix-implementation-boundaries

Use before implementing or triaging Orlix changes when ownership could involve OrlixKernel, OrlixMLibC, OrlixOS, OrlixHostAdapter, OrlixTerminal, upstream Linux, upstream mlibc, packages, product payloads, session APIs, or generated trees. Routes fixes to the…

orlix-upstream-conformance

Use when building, running, triaging, or claiming success for upstream Linux, upstream mlibc, Coreutils, or other upstream project test suites in Orlix. Requires pristine upstream sources and upstream tests; failures must be routed to the owning Orlix layer…

orlix-write-to-harness

Use before editing Orlix harness files such as AGENTS.md, docs/plans, docs/harness, ADR indexes, .agents/skills, .codex/agents, Codex rules, hooks, or harness-related repo guidance. Ensures changes preserve the repo as the source of truth, avoid duplicate…