Agentic AI Atlasby a5c.ai
OverviewWikiGraphFor AgentsEdgesSearchWorkspace
/
GitHubDocsDiscord
i.3Wiki
Agentic AI Atlas · Phase 5: Risk Register
docs/genty-features-backlog-updated/phase5-risk-registera5c.ai
Search the atlas/
Wiki · linked records

Article and nearby pages

I.Current articlepp. 1 - 1
Gap Status MatrixGenty Stack RoadmapNext StepsGap Inventory: Category SummaryPhase 1 Inventory Adversarial Check ResultsPhase 2 Codebase Audit -- Adversarial Corrections
I.
Wiki article

docs/genty-features-backlog-updated/phase5-risk-register

Reading · 8 min

Phase 5: Risk Register reference

Gaps rated by risk factor (Low/Medium/High) based on: implementation uncertainty, cross-cutting impact, dependency depth, external dependencies, and architectural complexity.

Page nodewiki/docs/genty-features-backlog-updated/phase5-risk-register.mdNearby pages · 14Documents · 0

Continue reading

Nearby pages in the same section.

Gap Status MatrixGenty Stack RoadmapNext StepsGap Inventory: Category SummaryPhase 1 Inventory Adversarial Check ResultsPhase 2 Codebase Audit -- Adversarial CorrectionsPhase 2: Stale Paths ReportPhase 3: Closed GapsPhase 3: Status Reclassification -- All ChangesPhase 4: Critical Path AnalysisPhase 4: Parallel Work TracksPhase 5: Quick WinsPhase 6: Milestone SummaryPhase 6: Roadmap

Phase 5: Risk Register

Gaps rated by risk factor (Low/Medium/High) based on: implementation uncertainty, cross-cutting impact, dependency depth, external dependencies, and architectural complexity.

---

High Risk Gaps (15 total)

These gaps have significant uncertainty, multiple dependencies, architectural complexity, or exposure to external changes.

Architectural Risk (Core Loop Changes)

Gap IDTitleEffortPriorityRisk Drivers
GAP-AGENT-003Process Orchestration with Effect RoutingLHighRequires restructuring orchestrateIteration.ts core execution path. capabilityRouter has zero consumers. Coordinator template is new architecture.
GAP-PAR-001Concurrent Effect ExecutionMHighWiring concurrent execution into the sequential orchestration loop. Fundamental architectural change to the core engine. 6 direct dependents.
GAP-PAR-003Multi-Harness Parallel DispatchLHighCross-iteration team coordination is absent. Depends on PAR-001 + SUBOBS-002. Complex distributed coordination.
GAP-PERF-002Session CompactionMCriticalMultiple compaction strategies and auto-compact triggers require careful design. Incorrect compaction loses critical context.

External Dependency Risk

Gap IDTitleEffortPriorityRisk Drivers
GAP-ECO-001CC Plugin Compatibility LayerMCriticalCC plugin format is external and may evolve. Adapter maintenance burden. Depends on understanding CC marketplace internals.
GAP-ECO-002CC Marketplace Protocol SupportLHighCC marketplace API is external. Protocol may change without notice. No existing implementation to build on. 12 downstream gaps blocked.
GAP-TOOLS-032MCP AuthenticationLMediumOAuth flows are security-sensitive. Token storage requires secure credential management. MCP auth spec may evolve.
GAP-SEC-006OAuth IntegrationLMediumFull OAuth flow with refresh lifecycle. Security-sensitive. Shares infrastructure concerns with TOOLS-032.

Architectural Complexity Risk

Gap IDTitleEffortPriorityRisk Drivers
GAP-AGENT-005Cross-Run CommunicationLHighGreenfield. AGENT_MESSAGE event type, routing between runs, delivery guarantees. No prior art in codebase.
GAP-TOOLS-012LSP Integration for Code-Aware RoutingLHighLSP client is architecturally significant. Language server lifecycle, diagnostic consumption, and routing integration.
GAP-TOOLS-017Git Worktree IsolationLHighWorktree lifecycle management is tricky (especially on Windows). Blocked by PAR-001.
GAP-TOOLS-023Multi-Step Workflow CompositionLHighctx.workflow() intrinsic with conditional branching and retry policies. Declarative workflow engine design.
GAP-PAR-010Fork-Join Process PatternLMediumState inheritance at fork points and synchronization at join points. Blocked by PAR-003.
GAP-RUN-003Run Forking and BranchingLMediumJournal fork-from-point requires new replay architecture. Blocked by STATE-006.
GAP-STATE-006Session Rewind and HistoryLMediumReplayEngine replays from start only. Fork-from-arbitrary-point requires new architecture. Blocked by PROC-003.

NEEDS_RESPEC Risk (Blocked on Decision)

Gap IDTitleEffortPriorityRisk Drivers
GAP-UX-001Rendering FoundationLHighArchitecture evolved to tula-ui/observer-dashboard. Blocks 5 downstream NEEDS_RESPEC gaps. Decision needed before any Track 6 work.
GAP-UX-001aEffect Tree VisualizationMHighBlocked on UX-001 respec.
GAP-UX-001fStreaming Output PanelsLHighBlocked on UX-001 respec + SUBOBS-001. Double dependency.
GAP-UX-001dMessage Type RenderingLMediumBlocked on UX-001 respec.
GAP-SUBOBS-005Dashboard Subagent Drill-DownLMediumOriginal spec assumes nonexistent embedded SDK dashboard.
GAP-SESSION-005Session Sharing and CollaborationLLowBlocked by REMOTE-003. Distributed systems complexity.

---

Medium Risk Gaps (17 total)

Moderate uncertainty, limited cross-cutting impact, or one significant but manageable concern.

Gap IDTitleRemainingPriorityRisk Driver
GAP-SUBOBS-001Streaming Output CaptureSCriticalNode.js child process streaming is well-understood, but harness diversity (Pi vs CLI vs remote) adds complexity.
GAP-SUBOBS-002Subagent Progress TrackingSHighProgress percentage extraction from heterogeneous output formats requires heuristics.
GAP-SUBOBS-004Subagent Health and TimeoutSMediumHang detection based on output silence requires threshold calibration.
GAP-REMOTE-003Remote Sessions (WebSocket)MHighRun directory sync for remote execution is distributed systems work.
GAP-REMOTE-007Host Contract LayerMHighTypes exist but zero consumers. Implementation + adoption risk.
GAP-PROC-001Process Chaining and PipelinesMHighUpgrading from skill-level to process-level pipelines with typed I/O.
GAP-PROC-003Process Versioning and MigrationLMediumSchema design for process version metadata and migration strategies.
GAP-PERF-004Streaming Message RenderingMHighMulti-harness streaming requires different approaches per harness type.
GAP-PERF-007Aggressive ParallelismMMediumAuto-detecting independent effects requires analysis of effect inputs/outputs.
GAP-PAR-005Parallel File OperationsMMediumConstrained by single-session harness architecture.
GAP-PAR-006Streaming ParallelismMMediumPipeline parallelism between orchestration phases is new territory.
GAP-OBS-006Analytics and Feature FlagsMMediumSink pipeline architecture decisions.
GAP-OBS-008Agent Progress SummarizationMMediumLLM-based or heuristic summarization strategy needs design.
GAP-PROMPT-007Context Compression FamiliesLMediumSemantic family grouping is fundamentally different from strata grouping.
GAP-SEC-007Privacy SettingsMMediumPII filtering is cross-cutting.
GAP-STATE-002Memory ConsolidationLMediumMerge/prune/weight algorithms for memories. Blocked by STATE-001.
GAP-UX-001cPermission/Breakpoint Approval UISHighRisk visualization quality depends on design decisions.
GAP-UX-010Typed Effect Interaction PatternsMMediumMulti-harness rendering of typed interaction schemas.
GAP-UX-001bStructured Diff RenderingMMediumPlatform choice uncertainty from UX-001 respec.
GAP-UX-001eProgress and Status LineSHighSmall once rendering target decided; blocked on UX-001.

---

Low Risk Gaps (18 total)

Well-scoped, self-contained, no architectural surprises, clear implementation path.

Gap IDTitleRemainingPriority
GAP-PERF-001Prompt Caching (Ephemeral)SCritical
GAP-HADAPT-003Cost-Based Routing PoliciesSHigh
GAP-ECO-003Plugin Trust, Provenance, BlocklistSHigh
GAP-SEC-002Trust Classes for PluginsSHigh
GAP-STATE-001Long-Term Memory ExtractionSHigh
GAP-MCPC-003Channel Permission RelaySHigh
GAP-OBS-NEW-001Webhook and Alert SystemSHigh
GAP-PROMPT-010Safety/Reversibility FrameworkSHigh
GAP-JSON-004JSON Session Management APISHigh
GAP-AGENT-001Sub-Harness Invocation with IsolationSHigh
GAP-AGENT-006Cross-Run State SharingSHigh
GAP-AGENT-004Built-in Process TemplatesSMedium
GAP-USER-017Plugin Management IntegrationSHigh
GAP-PROF-001Auto-Configure from User ProfileSMedium
GAP-ECO-004Plugin Auto-Update and VersioningSMedium
GAP-ECO-005Plugin Validation and DiagnosticsSMedium
GAP-ROUTE-002Effect Priority and SchedulingSMedium
GAP-ROUTE-003Effect Result CachingSMedium
GAP-HADAPT-005Harness Health MonitoringSMedium
GAP-PROMPT-004Prompt Inspection ToolingSMedium
GAP-PROMPT-006Instructions Loaded HookSMedium
GAP-OBS-003Prompt Plan ObservabilitySMedium
GAP-OBS-005Context IntrospectionSMedium
GAP-TOOLS-026Structured User InteractionSMedium
GAP-TOOLS-031MCP Resource BrowsingSMedium
GAP-TOOLS-028Sleep/Delay EnhancementSLow
GAP-BRK-003Breakpoint AnalyticsSLow
GAP-TOOLS-007JS/TS REPL ToolSLow
GAP-UX-011Command DiscoverabilitySMedium
GAP-UX-008Resume DashboardSMedium
GAP-UX-009Failure Triage ViewSMedium
GAP-RUN-001Run Comparison and DiffingMMedium
GAP-RUN-002Run Archival and RestoreMLow
GAP-OBS-007Audit ExportMMedium
GAP-TOOLS-037Fetch Content ProcessingMLow
GAP-SESSION-003Session TemplatesMMedium
GAP-TOOLS-029Structured Output ToolMMedium

---

Risk Mitigation Strategies

1. Core Loop Changes (PAR-001, AGENT-003)

  • **Strategy:** Feature-flag the concurrent execution path. Keep sequential path as default. Gradual rollout.
  • **Spike first:** Build a proof-of-concept of concurrent effect execution on a branch before committing to the architecture.

2. External Dependencies (ECO-001, ECO-002)

  • **Strategy:** Abstract the CC marketplace protocol behind a PluginSource interface. Support babysitter-native as primary, CC-compatible as secondary.
  • **Pin versions:** Track CC plugin spec version and alert on breaking changes.

3. NEEDS_RESPEC Gaps (UX-001 and dependents)

  • **Strategy:** Schedule a focused respec session for UX-001 before starting Track 6. Decision: adopt tula-ui as the rendering foundation. Then update all 5 dependent NEEDS_RESPEC gaps.
  • **Decouple data from rendering:** All data APIs are complete. Rendering can be swapped independently.

4. Security-Sensitive Gaps (SEC-006, TOOLS-032)

  • **Strategy:** Consolidate OAuth and MCP auth into a shared credential manager module. Design review before implementation. Follow established patterns (e.g., keytar or OS keychain).

5. Distributed Systems (REMOTE-003, SESSION-005)

  • **Strategy:** Start with read-only remote observation (status, events). Add remote mutation (run creation, effect dispatch) incrementally. Avoid attempting full remote execution in one milestone.

Trail

Wiki
Babysitter Docs
Genty Features Backlog: Adversarial Gap Analysis

Phase 5: Risk Register

Continue reading

Gap Status Matrix
Genty Stack Roadmap
Next Steps
Gap Inventory: Category Summary
Phase 1 Inventory Adversarial Check Results
Phase 2 Codebase Audit -- Adversarial Corrections
Phase 2: Stale Paths Report
Phase 3: Closed Gaps

Page record

Open node ledger

wiki/docs/genty-features-backlog-updated/phase5-risk-register.md

Documents

No documented graph nodes on this page.