rudironsoni/Orlix

orlix-tcti-next-step

Select the next owning OrlixTCTI test suite and emit a narrow scope envelope without reimplementing or interpreting test behavior.

orlix-tcti-debug

OrlixTCTI debugging with native LLDB and kernel-owned C proof. Use for crashes, watchpoints, disassembly, ELF, Mach-O, instruction encodings, symbols, sections, relocations, and OrlixTCTI runtime corruption.

orlix-implementation-boundaries

Use before implementing or triaging Orlix changes when ownership could involve OrlixOS, OrlixKernel, OrlixMLibC, OrlixCoreUtils, OrlixMachine, Containers, Herdr, OrlixTCTI, OrlixHostAdapter, the native Orlix app, upstream Linux, upstream mlibc, packages,…

orlix-tcti-debug

OrlixTCTI debugging with native LLDB and kernel-owned C proof. Use for crashes, watchpoints, disassembly, ELF, Mach-O, instruction encodings, symbols, sections, relocations, and OrlixTCTI runtime corruption.

orlix-tcti-next-step

Select the next owning OrlixTCTI test suite and emit a narrow scope envelope without reimplementing or interpreting test behavior.

orlix-tcti-next-step

Select the next owning OrlixTCTI test suite and emit a narrow scope envelope without reimplementing or interpreting test behavior.

orlix-implementation-boundaries

Use before implementing or triaging Orlix changes when ownership could involve OrlixOS, OrlixKernel, OrlixMLibC, OrlixCoreUtils, OrlixMachine, Containers, Herdr, OrlixTCTI, OrlixHostAdapter, the native Orlix app, upstream Linux, upstream mlibc, packages,…

orlix-tcti-debug

OrlixTCTI debugging with native LLDB and kernel-owned C proof. Use for crashes, watchpoints, disassembly, ELF, Mach-O, instruction encodings, symbols, sections, relocations, and OrlixTCTI runtime corruption.

orlix-implementation-boundaries

Use before implementing or triaging Orlix changes when ownership could involve OrlixOS, OrlixKernel, OrlixMLibC, OrlixCoreUtils, OrlixMachine, Containers, Herdr, OrlixTCTI, OrlixHostAdapter, the native Orlix app, upstream Linux, upstream mlibc, packages,…

orlix-tcti-debug

OrlixTCTI debugging with native LLDB and kernel-owned C proof. Use for crashes, watchpoints, disassembly, ELF, Mach-O, instruction encodings, symbols, sections, relocations, and OrlixTCTI runtime corruption.

orlix-docs-ingest

Add or update Orlix knowledge in the canonical docs ontology. Use for architecture, decision, epic, story, task, capability, terminology, provenance, and durable lesson changes.

orlix-docs-lint

Validate the Orlix documentation ontology, generated index, frontmatter, typed links, routes, and stale references. Use before shipping any Orlix knowledge change.

orlix-write-to-harness

Use before editing the Orlix ontology brain, AGENTS.md, agent skills, subagents, hooks, generated rules, or harness guidance. Preserves repository source of truth and prevents duplicated or stale status.

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-binary-debugging

Use when Orlix diagnosis may require Hopper, LLDB, disassembly, symbol inspection, crash frames, or binary-level validation after source and logs are insufficient.

orlix-codex-handoff

Use for long Orlix sessions, compaction risk, or a request to continue work from conversation history.

orlix-docs-query

Answer Orlix architecture, ownership, decision, epic, story, task, capability, provenance, and relationship questions from the canonical docs ontology.

orlix-docs-refresh

Reconcile current Orlix source, reports, decisions, and multiple ontology pages without rewriting unchanged knowledge.

orlix-dynamic-workflows

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

orlix-native-performance

Use when discussing, planning, measuring, or claiming Orlix native performance, ELF execution performance, syscall throughput, terminal throughput, storage throughput, or imported-binary startup behavior.

orlix-ontology

Apply the Orlix Markdown ontology when choosing object types, properties, typed links, normalization, source modeling, or schema changes.

orlix-runtime-claim-verification

Use before claiming Orlix work is fixed, green, complete, runtime-ready, package-ready, or upstream-test successful. Verifies that exact commands, logs, failure/skip accounting, crash reports, and ADR proof order support the claim.

orlix-session-lessons

Use when deriving durable Orlix lessons from a conversation, correcting agent behavior, or improving harness reliability.

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-binary-debugging

Use when Orlix diagnosis may require Hopper, LLDB, disassembly, symbol inspection, crash frames, or binary-level validation after source and logs are insufficient.

orlix-codex-handoff

Use for long Orlix sessions, compaction risk, or a request to continue work from conversation history.

orlix-docs-ingest

Add or update Orlix knowledge in the canonical docs ontology. Use for architecture, decision, epic, story, task, capability, terminology, provenance, and durable lesson changes.

orlix-docs-lint

Validate the Orlix documentation ontology, generated index, frontmatter, typed links, routes, and stale references. Use before shipping any Orlix knowledge change.

orlix-docs-query

Answer Orlix architecture, ownership, decision, epic, story, task, capability, provenance, and relationship questions from the canonical docs ontology.

orlix-docs-refresh

Reconcile current Orlix source, reports, decisions, and multiple ontology pages without rewriting unchanged knowledge.

orlix-dynamic-workflows

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

orlix-native-performance

Use when discussing, planning, measuring, or claiming Orlix native performance, ELF execution performance, syscall throughput, terminal throughput, storage throughput, or imported-binary startup behavior.

orlix-ontology

Apply the Orlix Markdown ontology when choosing object types, properties, typed links, normalization, source modeling, or schema changes.

orlix-runtime-claim-verification

Use before claiming Orlix work is fixed, green, complete, runtime-ready, package-ready, or upstream-test successful. Verifies that exact commands, logs, failure/skip accounting, crash reports, and ADR proof order support the claim.

orlix-session-lessons

Use when deriving durable Orlix lessons from a conversation, correcting agent behavior, or improving harness reliability.

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 the Orlix ontology brain, AGENTS.md, agent skills, subagents, hooks, generated rules, or harness guidance. Preserves repository source of truth and prevents duplicated or stale status.

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-binary-debugging

Use when Orlix diagnosis may require Hopper, LLDB, disassembly, symbol inspection, crash frames, or binary-level validation after source and logs are insufficient.

orlix-codex-handoff

Use for long Orlix sessions, compaction risk, or a request to continue work from conversation history.