GeneSYS Functionality Inventory

Operator Surfaces

CLI Command Groups

Runtime, Tools, And Policy

• Core runtime code manages sessions, prompt assembly, mode prompts, autonomy, compaction safety, workspace context, planning, tool fallback, tool filtering, provider routing, and persistent session state.
• Built-in tools include file read/write/list/stat/glob/grep/edit, apply_patch, bash/program execution, process lifecycle, jobs and rules, Git branch/commit/diff/push/PR/worktree operations, MCP resource access, plugin MCP/LSP calls, memory get/search/recall/profile, model listing, browser open/click/screenshot, webfetch/websearch, validation runs, task delegation/events, subagents, temporal setup/status/stop/namespace, tool permissions, todos, content extraction/decoding, code symbol/reference/diagnostic helpers, and user questions.
• Tool policy is represented through groups, skill-aware selection, permission checks, approval prompts, managed policy views, enterprise worker requirements, and audit events.
• Sandbox support spans provider-neutral sandbox types, Docker/gVisor readiness helpers, browser sandbox state, workspace/browser instance lifecycle, process tracing, and enterprise hardening checks.

Memory, Prompts, And Compaction

• Memory packages cover local-first memory providers, memory state, lifecycle, profile memory, MEMORY.md-style context, recall/search/profile tools, and memory method registration.
• The memory worker performs session extraction, consolidation, compaction summaries, HACP-facing memory handling, worker handlers, and dream consolidation jobs.
• Prompt infrastructure includes bootstrap/runtime/system/inbound/report slots, prompt registry and store, skill routing, context budget accounting, and session-mode prompt augmentation.
• Compaction and resume flows preserve summaries, memory references, memory index paths, candidate/write counts, and durable metadata on sessions.

Plugins, MCP, LSP, And Channels

• Plugin runtime supports Claude-compatible plugin manifests, marketplace install/import, enable/disable/uninstall, component resolution, skill discovery, agents, hooks, MCP servers, LSP servers, sandboxed plugin server supervision, status reporting, preflight smoke tests, and dynamic MCP tool naming.
• Runtime registrars expose auth, control, media, notifications, pairing, plugins, projects, PTC, sandbox, schedule, self-heal, sessions, tasks, and verification methods.
• Channel adapters include Telegram plus service hooks for Slack, Discord, Signal, Line, Lark, BlueBubbles, Baileys, and related pairing/delivery status surfaces.
• Companion functionality includes conversation/task sessions, companion jobs, rules, schedule storage, Temporal-backed workflows, and hidden control sessions.

Web Apps

• The Everything workspace is optimized for active work: ask/research/task/follow-up entry points, active sessions, recent activity, task lanes, schedule lanes, companion health, plugin marketplaces, media plugin checks, project sessions, transcript detail, profile summary, runtime configuration, and unavailable/not-found handling.
• The Playground control console is optimized for operators: runtime health, control signals, memory ledger, model/provider lanes, prompt groups, policy/mode/autonomy state, tools and bootstrap profiles, plugin runtime counts, channel adapters, pairing approvals, logs, audit tail/archive views, sandbox state, self-heal jobs, media-store status, PTC runs, and settings.
• Shared UI models in packages/ui define runtime health, audit timelines, enterprise policy/docker/install/worker health, workspace connection/run/task states, prompt context breakdowns, transcript entries, tool activity, approvals, pending questions, checkpoints, skills, memory, diffs, and command catalog metadata.

Sigroom And HACP Integration

• The @hacp/genesys-harness package is the bridge from local GeneSYS execution into Sigroom rooms.
• Launch contracts and startup guards enforce package boundaries before a harness joins a room.
• Runtime coordinators, runtime turns, output buffers, and loop supervision translate GeneSYS work into HACP-compatible room activity.
• HACP Control exposes hacp work commands that preview or call Sigroom harness-task API routes for list, select, edit, complete, test, test-all, sandbox-open, sandbox-status, and sandbox-stop.
• Launcher signing and platform endpoint modules connect local runtime evidence, Sigroom platform APIs, and signed receipts.
• @gene/loop-engine supports autonomous loop workitems that Sigroom can schedule and observe.

Operations, Release, And Verification

• Repository scripts cover package builds, app builds, CLI web asset bundling, HACP harness packaging, full release packaging, local install from packed packages, post-publish verification, dependency-policy checks, SBOM generation, audit/signature checks, sandbox security checks, release guardrails, clean dist, and version bumping.
• Production package builds now minify tsup output across GeneSYS packages, and Vite web app builds use esbuild minification with sourcemaps disabled.
• Full GeneSYS release packaging rejects source maps, sourceMappingURL references, TypeScript source files, node_modules paths, and hidden worktree/cache directories before publishing a bundle.
• Live acceptance lanes include workspace E2E tests and HACP verification modes when provider credentials or local live services are available.
• Trading help runs a vendored TradingAgents engine in Docker with allowlisted provider secrets, persistent report/checkpoint directories, JSON output, and an explicit financial-advice disclaimer.
• Current GeneSYS apps/docs is a placeholder package; this Sigroom page and the GeneSYS apps/docs README are the current functionality inventories until a hosted GeneSYS docs site is implemented.