Skip to content

🧭 Iterion feature inventory

140 criteria · 16 categories · 35 bots in the repository

September 11, 2026 · Capabilities, use cases and limitations of the reviewed version.

Iterion combines agent orchestration and Git workflows with active supervision, memory across missions, asynchronous interaction, file recovery, plugins, scheduling and team coordination. Use this inventory to identify the capabilities your developers and operators need, and check their scope before adoption.

Comparison guide · Feature availability — 10 products

Status key. ✅ Documented in the reviewed version. 🟡 Available with a material restriction on backend, deployment, scope or activation. 🧩 A method supplied as a bot using engine capabilities. Deferred work is listed separately and excluded from the total.

Evidence. Documentation review and targeted code inspection: 139 criteria at commit bbc1ddc7844b81582b6dfc4d0b7f381680bb284b, plus connector criterion X09 at 603d2a1e3314252dd2995e3bfaa4a7394e13093b; no execution tests were performed for this inventory. A checkmark does not imply parity across backends, managed availability or certified reliability. The project describes itself as experimental. current-state

⭐ Capabilities to explore

CapabilityWhat it enables in your workflow
👁️ Active supervisionAn agent can monitor a mission and send guidance while work is in progress.
🙋 Asynchronous questionsAn agent can keep working while you prepare an answer, then wait at a chosen point.
📚 Memory and knowledgeSelected knowledge can be reused across runs, bots and projects.
Recovery and rewindResume the graph, investigate errors and restore supported file states.
🧩 Skills and pluginsDistribute team methods, tools and technical knowledge.
Triggers and schedulingStart a mission from a forge event, a schedule, a card or another result.
📋 Board and shared configurationTrack work and delegate specific configuration fields to business users.
🏢 Native multi-tenant platformOperate agent workflows across organizations and teams with scoped resources, credentials and roles.
🔐 Permissions and data protectionMake access, secrets and data transformations explicit workflow settings.

These categories help you assess fit. Their presence in Iterion does not establish their absence elsewhere.

🗺️ Browse the inventory

📝 Authoring and sharing · 🔀 Orchestration · 🧠 Models, sessions and context · 🙋 Human interaction · 👁️ Supervision · 📚 Memory and knowledge · 🧩 Skills, plugins and integrations · ⏪ Recovery and rewind · 🌿 Git and delivery · ⚡ Triggers and scheduling · 📋 Team coordination · 🔐 Permissions, secrets and data · 🏢 Organizations, access and usage · 🔎 Observability · ⚙️ Deployment and evaluation · 🤖 Bot methods

📝 Authoring and sharing workflows

IDFeatureStatusUsage and scope
A01Declarative .bot workflowsDefine agents, tools, data and transitions in a versionable file. A deterministic graph does not make LLM responses identical. dsl
A02Synchronized visual and source editorsCanvas, node library, inspector, live validation, undo and redo. visual-editor
A03Guided bot creationStarter templates, mission form, parameters and a first run; equivalent creation through the CLI. visual-editor
A04Portable .botz bundlesDeterministic ZIP archive containing the workflow, prompts, skills, attachments and manifest; supports declaring a minimum engine version. bundles
A05Reusable variables, presets and promptsParameterize a method at launch and distribute specializations without copying the entire workflow. bundles dsl
A06Team bot editingCreate, duplicate and edit bundle files in cloud Studio, with conflict checks on save. visual-editor
A07Importing an existing Claude workflow🟡Static converter from Claude JavaScript files to a .bot draft, with a report of unsupported elements. Does not import n8n workflows. import
A08Schemas and static diagnosticsValidate references, properties and graph/data-flow constraints before execution. General node-output schema validation is an engine option, not enabled by product entry points in this build; compute outputs are checked separately. dsl output-validation-code compute-types-code
A09Mermaid diagram exportGenerate a compact, detailed or full workflow diagram for documentation and review. cli-reference

🔀 Orchestrating agents, code and events

IDFeatureStatusUsage and scope
O01Explicit agents and judgesSeparate production from evaluation in the graph; a judge is a configurable LLM evaluation, not proof of correctness. dsl
O02Deterministic tools and scriptsCommand nodes or JavaScript, Python and shell/Bash scripts, with stdout capture and error handling. dsl
O03Computation without a model or shellThe compute node provides bounded expressions, transformations, map/filter/reduce and typed outputs. dsl
O04Conditional, LLM and round-robin routingSelect a branch using rules, a model decision or a declared rotation. routers
O05Parallel branches and result collection🟡fan_out_all, fan_out_each, with wait_all or best_effort collection; concurrent workspace writes are restricted. routers groups-iteration-subbots
O06Bounded, data-driven loops and ordered iterationFixed or data-resolved bounds, foreach, and explicit unbounded loops governed by fuel and a stagnation monitor. Empty foreach input requires a guard if its body must never run. groups-iteration-subbots loop-fuel-code loop-edges-code
O07Reusable parameterized groupsDeclare a subgraph and instantiate it with distinct parameters and prefixes. groups-iteration-subbots
O08Sub-bots with their own runs🟡Call another bot, retrieve its output and isolate its work; budgets, memory and supervisors have parent/child limitations. groups-iteration-subbots memory-and-knowledge supervisors
O09Resource pools and concurrency limitsDeclare resources and reserve a slot with needs, for example to limit simultaneous worktrees. groups-iteration-subbots dsl
O10Emitting and waiting for internal events🟡In-run emit/wait, retained events for late waiters and mandatory timeouts. Durable parking on external events is deferred. event-primitives

🧠 Models, sessions and context

IDFeatureStatusUsage and scope
B01Six execution backends🟡claw, claude_code, pi, codex, kimi, grok, with different capabilities and support levels. backends delegation
B02Model and backend selection per nodeMix executors in one workflow, select the model independently of the backend and apply launch overrides. backends
B03Provider or credential fallback🟡Configurable fallback chains when the initial access is unsuitable; changes should remain observable. backends
B04Cross-backend fallback and skip routes🟡Declare a fallback executor or a workflow-defined skip route; prerequisites are validated. Codex is excluded from the first cross-backend fallback version. backends
B05Fresh, inherited or forked sessions🟡Choose conversational continuity between steps; session resume and fork are not wired for Kimi/Grok. dsl delegation
B06Persistent sessions on node re-entry🟡session: persist reuses a node's conversation in a loop; supported on Claude Code, pi and Codex along the main workflow path. session-persist
B07Artifact-only handoffartifacts_only passes the useful result without carrying the previous step's conversation history. dsl
B08Context compaction🟡Configurable threshold and retention of recent exchanges; depends on the executor and can support error recovery. dsl run-recovery
B09Behavior dialsQualitative or numeric prompt settings for depth, caution, style and more. They guide the model without enforcing permissions or guaranteeing quality. cursors
B10Reasoning effort settings🟡Choose reasoning_effort per node or through input data; levels adapt to model and backend support, independently of behavior dials. ultracode effort-code
B11Sub-agents and workflows created within a node🟡ultracode enables dynamic orchestration on claw and Claude Code depending on model, harness and tools; separate from declared fan-out and sub-bots. Pi does not provide this capability. ultracode subagents-code pi-code

🙋 Human interaction and guidance

IDFeatureStatusUsage and scope
H01Typed approval formshuman nodes support text, choices, booleans, numbers and lists; review context is separate from expected answers. human-in-the-loop
H02Agent questions during execution🟡ask_user with answers through Studio, CLI or API; support depends on backend and transport. human-in-the-loop delegation
H03Questions without blocking the agent🟡ask_user_async lets the agent continue before receiving answers; asynchronous interaction runs on the main path, outside fan-out branches. async-interaction
H04Explicit answer synchronization🟡await_answers synchronizes pending questions; the node requires a timeout, and the run remains active while waiting. async-interaction
H05Automatic answers or human escalation🟡llm and llm_or_human modes follow workflow policy; an automated answer is not human approval. human-in-the-loop
H06Guidance added to an active run🟡Inbox and steering redirect work at backend-defined intake points; they do not instantly cancel an ongoing action. backends supervisors
H07Files and images at launch or in an answer🟡Persisted attachments with MIME type, size and hash; vision depends on the model. Review gates do not accept the same uploads as ordinary human nodes. attachments human-in-the-loop
H08Review dialogue before integration🟡Review companion, correction requests and an optional review environment; explicitly choose human_required or an agent verdict. review-merge-gate
H09Operator pause with checkpoint🟡Request a pause at the next safe boundary, then resume; local in-process path only, with remote cloud pause unimplemented. pause-code

👁️ Supervising an active mission

IDFeatureStatusUsage and scope
S01Agent supervising another agent🟡Observe an agent/judge node and inject guidance during execution; supervisors declared inside sub-bots are not currently wired. supervisors
S02Supervision monitors, cadence and budgetReact to events, errors or cost signals with a cooldown and evaluation limit; account for supervision costs. supervisors
S03Attaching a supervisor to a session🟡Attach through the CLI to a local run, or to a Claude Code session with prepared transcript and hooks; remote cloud attachment is deferred. supervisors
S04Changing budgets and iterations during a run🟡Raise limits or grant extra iterations with acknowledgment and a recorded event; changes apply at safe boundaries. dsl steering-code

📚 Reusable memory and knowledge

IDFeatureStatusUsage and scope
M01Document memory across runsRetain knowledge as Markdown documents beyond a single run's artifacts. memory-and-knowledge
M02Seven visibility scopes🟡Private run, bot, project, multiple projects, user, organization and global catalog; storage and context determine access. Global scope is read-only for organizations. memory-and-knowledge
M03Agent memory read, write and list tools🟡memory_read, memory_write, memory_list, with configurable permissions; check the adapter and backend in use. memory-and-knowledge memory-code
M04Index and selective context loadingInject an index, preload selected documents and reinject memory before compaction according to configuration. memory-and-knowledge
M05Automatic bot memory🟡auto_memory maintains a MEMORY.md per bot and repository; opt-in on claw/Claude Code/pi, with restrictions for cloud sandboxes without read-back. memory-and-knowledge
M06Memory quotas and secret detection🟡Aggregate, space and document quotas; structured secret detection does not cover all confidential data. memory-and-knowledge
M07Memory import and exporttar.gz archives through CLI/API, with skip, overwrite or rename strategies to retain or transfer knowledge. memory-and-knowledge

🧩 Skills, plugins and technical integrations

IDFeatureStatusUsage and scope
X01Editable skills library🟡Global, project or bundled skills; management CLI and local editor, with selected skills transported to cloud runners. skills-library
X02Skills selected per workflow or nodeName and description enter the context; content loads on demand. A missing skill produces a warning. skills-library
X03Plugins with declarative contributions🟡MCP, skills, output rewriting, commands, agents, hooks and lifecycle features; backend support varies by contribution. plugins
X04Private organization plugins from GitResolve private and public sources, then transport them for local or cloud runs. plugins
X05Command output compression🟡RTK plugin and compress modes reduce text sent to the model; plugin availability and activation depend on the interface in use. plugins
X06MCP client in workflows🟡Declare MCP servers, inherit them or disable them per node; transports and support depend on the backend. dsl delegation
X07MCP server for controlling Iterioniterion mcp exposes launch, monitoring, human answers and board operations, locally or against a configured remote instance. mcp-server
X08Web search and page reading🟡Native tools or configured providers/MCP, including DuckDuckGo, Brave, SearXNG and Firecrawl; coverage varies by backend. web-search
X09Deterministic connector actions and package generation🟡Local in-process action: nodes use typed parameters, bound connections and structured results with pagination/completion indicators. Generate packages from OpenAPI/Swagger with an authored overlay. Project catalogs require opt-in; cloud transport and the catalog MCP facade are outside this delivered scope. connector-dsl connector-local-code connector-cli-code

⏪ Recovery, repair and rewind

IDFeatureStatusUsage and scope
R01Workflow state checkpoints🟡Resume eligible states with outputs, counters and position; interrupted steps may execute again. resume
R02Sub-bot recovery after restart🟡Reattach the parent to its recorded child run instead of always launching a new child, when the state is recoverable. subbot-reattach
R03Rewinding to an earlier node🟡rewind invalidates dependent outputs; --auto locates a changed node. Branch and starting-state restrictions apply. resume
R04File snapshots outside Git history🟡Filesystem tracker wired to local CLI/Studio, with deduplicated states at execution boundaries; cloud runners do not wire this tracker. Separate from pushed Git workspace checkpoints. workspace-versioning tracker-wiring-code runner-code
R05Targeted restoration and pre-rewind backup🟡Restore run-produced files from available local snapshots while protecting operator changes; ignored or oversized paths are excluded. workspace-versioning resume
R06Actions with verifiable postconditionsCheck a condition before and after a command, skip an already-satisfied action and select required/recover/best_effort policy. verified-actions verified-code
R07Bounded action repair🟡Propose a corrected command, then optionally delegate recovery to an agent; opt-in, bounded attempts, with success determined by the postcondition. verified-actions verified-code
R08Controlled retries and automatic recovery🟡Error classification, backoff, compaction or human pause; optional CLI auto-resume excludes terminal errors. run-recovery recovery-code
R09Recovery hint after pod loss🟡Expose the last successfully pushed workspace checkpoint and a recovery command; this does not automatically restore files or validate a deliverable. resume
R10Forking a run from an earlier exchange🟡Create a resumable run with modified inputs and restore the code snapshot when available; conversational precision depends on the backend. cli-reference fork-code

🌿 Working and delivering in a repository

IDFeatureStatusUsage and scope
G01Separate worktree per run🟡Isolate a run's Git changes; behavior depends on mode and repository, particularly for empty repositories. dsl repo-scope worktree-finalization
G02Git finalization policy🟡Retain or integrate the result according to the selected policy; finalization authority must be granted. cli-reference worktree-finalization
G03Merge gate with result review🟡Review, corrections and merge/squash decision within the supported flow; configure acceptance criteria and the target branch. review-merge-gate
G04Changes and commits viewInspect modified files, diffs and commits from a run; metadata is persisted for documented cloud paths. visual-editor cloud-git
G05Conservative worktree pool cleanup🟡Bounded collection of eligible old worktrees preserves dirty, active or recoverable work; it is not a strict disk cap. worktree-pool
G06Devbox tooling environment🟡Prepare tooling declared by the bot and repository; requires a compatible installation and execution environment. devbox
G07Repository targeting, connection and creation🟡Guided forge connection, target selection and authorized creation in cloud Studio. Manifests also support optional or no repository requirements; creation needs forge permissions. repo-scope

⚡ Triggers, scheduling and chaining

IDFeatureStatusUsage and scope
T01Manifest-defined invocationsDeclare forge, command, schedule, board and keepalive inputs, with direct launch or card creation. bot-invocations
T02Multi-forge and JSON inbound webhooksGitHub, GitLab, Forgejo/Gitea or generic payloads; configurable event/project/author filters and authentication. webhooks
T03Forge commands and conversations🟡Slash commands and bot replies in authorized GitHub/GitLab threads; replies still rely on a skill, while native forge.reply is deferred. forge-conversations bot-invocations
T04Local and cloud schedulingCron, guards and overlap policy; runs through host cron locally or the platform scheduler. scheduling
T05Keepalive and availability waits🟡Relaunch recurring missions using guards and availability windows; configure behavior per bot and backend. scheduling bot-invocations
T06Triggers on events and run outcomesSubscribe to board events, explicit events or run completion to chain missions. trigger-spine
T07Durable outbox for cloud board effects🟡Materialization, claim, retry and permanent failure for trigger effects; at-least-once execution with documented residual failure windows. trigger-outbox
T08Automatic mission outcome routing🟡Policy frozen at launch for merge, relaunch or escalation; server option and decision log. outcome-router
T09HTTP callbacks and web notifications🟡HMAC-signed completion callbacks, operator alerts and Web Push require configuration; native desktop notifications are deferred. outbound-callbacks notifications usage-caps

📋 Coordinating team work

IDFeatureStatusUsage and scope
K01Native kanban independent of a forgeCards, columns, labels, priorities, assignments and comments through Studio or CLI. native-tracker
K02Typed custom fields and dependenciesValidated card schema, hard blockers and waiting_deps state prevent premature launches. native-tracker
K03Autonomous issue dispatcher🟡Selection, claim, launch, retries, stall detection and concurrency limits; native tracker and configurable adapters. dispatcher
K04Pipeline board and mission controlView planned tasks and active runs, launch by priority and limit concurrent pipelines. visual-editor native-tracker
K05GitHub Projects V2 synchronization🟡Bidirectional statuses; issue fields synchronize according to a specific mapping, not arbitrary field replication. github-board-sync
K06Links between cards, runs and resultsLatest run, worktree, wait states and event history establish work provenance. native-tracker
K07Configuration editor for non-operators🟡Share revocable access to selected repository file fields; forge commits, conflict checks and audit, without operator Studio access. config-share

🔐 Permissions, secrets and data

IDFeatureStatusUsage and scope
P01Tool permissions and read-only mode🟡Ask/deny gates on agent calls: claw, Claude Code and pi RPC; Kimi/Grok deny only, Codex without this gate. permission: does not apply to shell tool nodes. permissions delegation
P02Execution sandbox🟡Configurable isolation by backend, driver and deployment; auto can degrade, while Codex uses its own sandbox. sandbox
P03Bot-bound secrets and host controls🟡Bindings limit supplied secrets; allowed_hosts covers supported egress paths. This guarantee does not extend to every shell call. secrets-reference
P04Secrets sealed at restAES-256-GCM with record binding; authorized cloud components share the key. Automatic master-key rotation is not currently available. secrets-reference
P05File-based secret injection🟡Materialize a secret with as: file, with in-run refresh on supported paths. secrets-reference file-secret-refresh
P06Local sensitive-data detection and masking🟡Go-based privacy_filter covers accounts, emails, phone numbers, URLs and secrets. Person names, postal addresses and dates are excluded. privacy_filter
P07Restoring masked values🟡privacy_unfilter restores original values if the vault file is retained; the vault is not replicated to Mongo/S3. Trace masking targets privacy_filter inputs and privacy_unfilter outputs, not data flowing elsewhere. privacy_filter vault-code runner-code
P08Upload and browser preview controls🟡MIME, size, path and SSRF controls on covered routes; active content is restricted, without a general guarantee that files are harmless. attachments browser-pane
P09System credential vault for desktop🟡macOS Keychain, Windows Credential Manager or Linux Secret Service integration requires the system service. Separate from cloud secret sealing. desktop keychain-code

🏢 Organizations, access and usage

IDFeatureStatusUsage and scope
E01Multi-tenant organizations, teams and rolesSeparate platform resources by tenant and assign operator/administrator permissions and editing capabilities. cloud-overview config-share
E02Organization SSOGeneric OIDC and dedicated connectors, with organization-specific configuration and access policies. sso
E03User or organization LLM keysBYOK, defaults and launch/integration overrides follow the resolution chain; providers bill separately. byok secrets-reference
E04Subscription/OAuth authentication🟡Reuse authentication supported by CLI backends within the limits of those accounts and their providers. oauth-forfait backends
E05Opt-in contributor credential pool🟡Credential lending with audience, availability, limits and per-run leases; does not increase provider quotas. credential-pool
E06Run budgets: cost, tokens, duration and iterations🟡Configurable limits, backend-dependent estimates, finalization headroom and separate sub-bot budgets; not a universal billing cap. dsl
E07Platform quotas and launch admission🟡Concurrency, rate, monthly and cost quotas; quota reads can allow a launch through on storage errors. quotas-and-limits
E08Subscription usage-window protection🟡Adjustable soft/hard thresholds and policies; measurement is currently specific to Claude Code and separate from monetary budgets. usage-caps
E09Personal tokens and administration auditAttributed API access and administrative actions; change history covers supported operations. cloud-rest-api secrets-reference
E10Effective settings and their originsLaunch displays backend, permission, compression and auto-memory values and provenance, plus nodes with their own settings. settings-precedence

🔎 Observing and inspecting results

IDFeatureStatusUsage and scope
U01Live run consoleGraph, events, logs and counters for monitoring execution in Studio. visual-editor
U02Artifacts and history per step/iterationVersioned outputs and persisted events for inspecting completed runs. persisted-formats
U03Cost reports and usage statisticsBreakdown by model/provider, run counts, failures and P50/P95 durations; precision depends on available accounting. visual-editor
U04Session task list🟡Deterministic TodoWrite/todo_write history reconstructed from events; currently populated by Claude Code and claw. session-board
U05AI-generated monitoring widgets🟡Notes, metrics, checklists, progress and charts; local opt-in with an evaluation budget, not currently wired to cloud. session-board
U06Web previews and timestamped captures🟡Result URLs, run-linked captures and live browser through manual local attachment; cloud live browsing and Playwright auto-attach are deferred. browser-pane
U07Browsable file deliverablesA tool can publish a generated file as a run attachment using a stdout directive; publication failures are reported without failing the tool. attachments
U08Post-mortem worktree terminal🟡Inspect an idle run in its retained environment; local Unix only, without a cloud host terminal. post-mortem-shell
U09Structured logs, errors and tracing🟡Process JSON, alerts and Sentry/GlitchTip integration; a DSN is required and tracing is enabled separately. observability
U10Prometheus, OTLP and Grafana dashboards🟡Metrics endpoint and supplied observability stack; costs, tokens, retries and durations depend on data exposed by each backend. observability-stack
U11Direct run file editing🟡Edit a text file in a retained local worktree; 4 MiB limit, without Git staging, locking or concurrent conflict checks. Separate from the bot editor. run-file-editor

⚙️ Deploying and evaluating the platform

IDFeatureStatusUsage and scope
D01CLI, Studio, desktop app and self-hosted cloudMultiple interfaces around the same engine; feature parity is incomplete. current-state desktop
D02Distributed runners and platform storageNATS queue, runners, MongoDB and S3 storage; Kubernetes architecture and scaling require operation. cloud-architecture
D03Bot sources frozen at cloud launchHashed snapshot of parent, sub-bots and resources; runners do not silently substitute their own catalog version. bot-bundle-snapshots
D04API and TypeScript SDKControl runs, resume and consume events; documented SDK support for Node, Deno and Bun. cloud-rest-api readme
D05Recipes and variant comparisonCombine workflow, parameters, prompts, budgets and evaluation policy into benchmark campaigns. recipes
D06Convergence analysis on recorded runs🟡bench asymptote aggregates verdicts by iteration without replaying LLMs; it neither guarantees convergence nor constitutes a completed competitive benchmark. asymptote-bench
D07MIT-licensed source codeModifiable, self-hostable engine; third-party components and services retain their own terms. license
D08Desktop multi-project switchingSelect and return to multiple projects in the native app; onboarding prepares a first project. desktop desktop-projects-code
D09Desktop updates with signature verification🟡Verify the manifest and artifact using Ed25519, then offer installation according to package and platform. This does not imply macOS notarization or Windows signing. desktop updater-code

🤖 Methods supplied as bots

IDFeatureStatusUsage and scope
C01Application and feature development🧩app-dev, feature-dev, feature-gap-fill, bmady bundles; workflows adaptable to the repository and acceptance criteria. bot-app-dev bot-feature-dev bot-feature-gap-fill bot-bmady
C02Code review and review dialogue🧩review-pr, revi-converse and review helpers; verify forge coverage and permissions. bot-review-pr bot-revi-converse
C03Continuous improvement and modernization🧩whole-improve-loop, branch-improve-loop, modernize, evolve; each bot defines its checks and approval steps. bot-whole-improve-loop bot-branch-improve-loop bot-modernize bot-evolve
C04Tests, coverage and instrumentation🧩test-coverage, e2e-coverage, golden-master, instrument build or inspect evidence suited to the project. bot-test-coverage bot-e2e-coverage bot-golden-master bot-instrument
C05Security audits and dependency maintenance🧩sec-audit-source, sec-audit-deps, dep-update-guard, secured-renovacy, supply-shield and variants; an automated audit cannot certify the absence of vulnerabilities. bot-sec-audit-source bot-sec-audit-deps bot-dep-update-guard bot-supply-shield
C06Vulnerability monitoring🧩vuln-watch detects issues and routes remediation according to configuration. bot-vuln-watch
C07Accessibility🧩rgaa-audit, ultra11y; assess audits and fixes against the tested scope, without assuming automatic compliance. bot-rgaa-audit bot-ultra11y
C08Documentation and architecture🧩docs-refresh, product-docs, wiki-gen, adr-cartograph, adr-rechallenge produce and update documents for review. bot-docs-refresh bot-product-docs bot-wiki-gen bot-adr-cartograph bot-adr-rechallenge
C09Content monitoring, triage and planning🧩feed-watch, issue-triage, whats-next, campaign; collection, synthesis and coordination using the supplied workflows. bot-feed-watch bot-issue-triage bot-whats-next bot-campaign

🚧 Deferred work and remaining limitations

AreaStatus in this inventory
dsl: 2 versioning, explicit file imports and migrationDescribed in ADR-098; no implementation evidence found in the parser/CLI at the reviewed commit. These commands and imports are not listed as shipped. dsl-roadmap
Durable run parking on external eventsDeferred; distinct from triggers that launch runs and active internal waits. event-primitives async-interaction
Supervisors declared inside sub-botsDeclarations are not wired; parent support does not extend to children. supervisors
Cloud supervisor attachment and Studio toggleDeferred; workflow-declared supervision exists, while CLI attachment targets local execution. supervisors
Memory parity across execution pathsThe UI incorrectly lists some bot/project spaces; cloud sub-bots do not receive the parent's MemoryStore; driver read-back limits auto-memory. memory-and-knowledge
Filesystem snapshots and PII vault on another podThe file tracker is local; the PII vault is a file in the executor's storeDir. Remote Git checkpoints and Mongo/S3 storage do not transfer them. tracker-wiring-code vault-code runner-code
Cloud live browser and Playwright auto-attachDocumented as future work. Existing previews and captures do not establish remote live browsing. browser-pane
AI-generated session widgets in cloudDedicated cloud storage and DSL declaration are deferred; current curation is local and opt-in. session-board
PII detection for names, postal addresses and datesPlanned for a later version; the five current categories provide limited coverage. privacy_filter
General node-output validation in product launchesThe engine exposes opt-in validation and bounded correction, but CLI/Studio/cloud entry points do not enable it in this build. compute output conformance is active independently. output-validation-code output-options-code compute-types-code
Automatic master-key rotation and per-tenant KMSUnavailable; current sealed storage does not provide this capability. secrets-reference
Native desktop notificationsDeferred; Web Push is separate from native application notifications. notifications
Automatic remediation bot triggered by SentryDescribed as an intention; error-watch does not yet exist. Error reporting and Sentry MCP access are separate capabilities. sentry-feedback-loop
Broader business connector catalogThe local deterministic foundation is available in X09. Broader packaged coverage, the catalog MCP facade and cloud transport remain outside this delivered scope; future connectors are not counted as installable. Tracking: connector catalog, issue #1072.

Cross-cutting limitations. Sub-bot budgets are not aggregated into the parent's budget, and launch quotas are not a strict financial barrier during storage errors. Resuming a run does not guarantee exactly-once execution of external effects. dsl quotas-and-limits resume

Improvement methods. Bots can incrementally retain validated work and measure iteration verdicts. Outcomes depend on the configured checks; improvement on every iteration and freedom from regressions are not guaranteed. improvement-ratchet

🔬 Inventory evidence

Stable criterion IDs support future comparisons. The total spans primitives, interfaces, operations and methods; it is not a competitive score.

Row references point to a pinned repository version. Targeted code inspection complemented the documentation for the following mechanisms:

CategoryEvidence in the inspected code
Local connector actionsTyped action recipe and result contract, in-process resolver wiring, OpenAPI/Swagger generation: DSL, local launch wiring, CLI. Reviewed at the separate connector commit recorded in X09.
Loop controlFixed/data-resolved bounds, finite fuel and loop stagnation checks: bounds and monitor, back-edge handling.
Output schemasOpt-in general validation versus active compute conformance: option, validator, compute path.
Asynchronous interactionStoreAsyncAskBinder, InteractionKindAsync persistence, human_input_requested event: async code.
SupervisionCoordinator, cooldown, MaxEvals limit and injection: supervision code.
MemorySeven Visibility values, MemoryStore contract and tool/index wiring: scopes, contract, tools.
Verified actionsSkip precondition, recipe, postcondition and bounded repair stages: implementation.
RecoveryError-class dispatch, attempt counter, retry/compaction/pause: implementation.
Files and rewindCapture, Restore, RestoreOnly and protected paths: tracker contract.
PluginsManifest and typed contributions: implementation.
Shared editorReadable field projection, patch validation and SHA conflict rejection: service.
Credential poolAcquisition, contributor ranking, leases and release: broker.
Board triggersClaim, retry and effect materialization: worker.
Limit adjustmentsbump_loop/raise_budget, deduplication and typed replies: transport.
PII maskingRegistration of both tools, validation and per-run vault: implementation.

Documentation and targeted implementation checks underpin this inventory. Capabilities remain tied to the cited commit and should be reassessed when the version changes.

📦 The 35 source bundles

Counted from bots/*/main.bot at the reviewed commit. These are source bundles; not every binary embeds all 35, and some support other workflows.

adr-cartograph · adr-rechallenge · app-dev · arbitrate · bmady · branch-improve-loop · campaign · dep-update-guard · devbox-setup · docs-refresh · e2e-coverage · evolve · feature-dev · feature-gap-fill · feed-watch · golden-master · instrument · issue-triage · modernize · product-docs · revi-converse · review-env · review-pr · rgaa-audit · sec-audit-deps · sec-audit-source · secured-renovacy · supply-shield · supply-shield-cve · test-coverage · ultra11y · vuln-watch · whats-next · whole-improve-loop · wiki-gen

The CSV inventory contains the same criteria, statuses, limitations and references for further comparisons.

📎 Pinned sources

The short references above resolve to the following documents and files.