SciDEX — Task: [Senate] Design executor plugin architecture for e

## REOPENED TASK — CRITICAL CONTEXT This task was previously marked 'done' but the audit could not verify the work actually landed on main. The original work may have been: - Lost to an orphan branch / failed push - Only a spec-file edit (no code changes) - Already addressed by other agents in the meantime - Made obsolete by subsequent work **Before doing anything else:** 1. **Re-evaluate the task in light of CURRENT main state.** Read the spec and the relevant files on origin/main NOW. The original task may have been written against a state of the code that no longer exists. 2. **Verify the task still advances SciDEX's aims.** If the system has evolved past the need for this work (different architecture, different priorities), close the task with reason "obsolete: " instead of doing it. 3. **Check if it's already done.** Run `git log --grep=''` and read the related commits. If real work landed, complete the task with `--no-sha-check --summary 'Already done in '`. 4. **Make sure your changes don't regress recent functionality.** Many agents have been working on this codebase. Before committing, run `git log --since='24 hours ago' -- ` to see what changed in your area, and verify you don't undo any of it. 5. **Stay scoped.** Only do what this specific task asks for. Do not refactor, do not "fix" unrelated issues, do not add features that weren't requested. Scope creep at this point is regression risk. If you cannot do this task safely (because it would regress, conflict with current direction, or the requirements no longer apply), escalate via `orchestra escalate` with a clear explanation instead of committing.

Git Commits (1)

[Verify] Executor plugin architecture — already resolved [task:aecf86227fab]2026-04-21

Spec File

[Senate] Design executor plugin architecture for external compute scaling

Quest: Resource Governance Priority: P3 Status: open

Goal

Document and stub the architecture for offloading analyses to external compute. Define the interface contract: how analyses are packaged, submitted, monitored, and results collected. This prepares for AWS Batch, Lambda, or K8s integration without implementing the cloud side yet.

Acceptance Criteria

☐ Architecture design doc at docs/planning/external-compute-architecture.md

☐ Executor interface defined (same as Analysis Sandboxing quest)

☐ Job packaging: how analysis inputs are bundled for remote execution

☐ Result collection: how outputs come back and get committed to DB

☐ Cost tracking: how remote compute costs flow into resource_usage table

☐ Security: how credentials and data are handled in remote environments

Approach

Design the executor plugin interface (coordinate with Analysis Sandboxing quest)

Define job manifest format: inputs, tools needed, resource budget, timeout

Define result manifest format: outputs, logs, resource usage, cost

Document AWS Batch integration path (Dockerized analysis, S3 staging)

Document K8s integration path (pod spec, persistent volumes)

Write architecture doc with diagrams

Dependencies

_Identify during implementation._

Dependents

_Identify during implementation._

Work Log

_No entries yet._

Payload JSON

{
  "requirements": {
    "coding": 7,
    "reasoning": 6
  }
}

Sibling Tasks in Quest (Resource Governance) ↗

✓[Senate] Link 50 isolated artifacts into the governance graphP80

✓[Senate] Implement hard memory and CPU limits for analysis processesP5

✓[Senate] Add concurrent analysis limits and queue managementP5

✓[Senate] Implement daily cost budgets with auto-pauseP4

✓[Senate] Build real-time resource monitoring dashboardP4

✓[Senate] Add process watchdog that kills runaway analyses and orphaned processesP4

[Senate] Design executor plugin architecture for external compute scaling done coding:7 reasoning:6