Skip to content

2026-09-02 Histo Factory campaign controller

Built the standalone Factory controller prototype for current histo and viseg campaigns.

Work Done

  • Added a standalone factory_controller package in the Factory campaign prototype worktree.
  • Reproduced the current six histo campaign scopes and the viseg anatomy campaign with their existing producer identifiers and Polars completion logic.
  • Added fresh vxData evaluation, Argo in-flight reads and bounded worker submission, and minimal FastAPI campaign endpoints.
  • Added focused tests for stable case identifiers, worker capacity and payloads, and fresh histo evaluation.
  • Ran Ruff formatting and lint, ty type checking, and three pytest tests successfully.

Lessons Learned: Pitfalls

  • The controller-to-worker payload and CLI contract was not discoverable until the worker package appeared in the shared worktree. Confirming the contract with the coordinating agent prevented coupling the controller to worker imports.
  • A nested Ruff configuration inherited the parent package’s banned-import rules until the standalone package declared its own lint selection.

Lessons Learned: Improvements

  • A short Factory prototype contract document should name package entrypoints, worker JSON fields, Argo labels, commands, and resource defaults before parallel implementation starts.
  • The vxData SDK path dependency does not carry its Conda runtime dependencies, so new standalone packages must repeat httpx, minio, python-dotenv, and truststore explicitly.
Navigation

Type to search…

↑↓ navigate↵ selectEsc close