Skip to content

2026-09-16 Factory framework assessment

Read-only review of the standalone framework and v1, with a proposed execution boundary.

Work Done

Read ~/work/factory-framework source, README and example, compared relevant ~/work/mono/apps/factory code, and considered the user’s earlier notes. No application source changed and no cluster jobs were submitted. The framework remains a scaffold; its existing Pixi Python reports a TabError in src/factory_framework/base.py:55.

Proposed, not implemented or approved: one shared runtime behind CLI/FastAPI, local and Argo compute adapters, and a separate execute-only worker command. Consumer repositories own fixed-semantics services and images. Preserve lightweight schema discovery, incremental output persistence, and operational resource context without exposing inference parameters. Review draft is local to this session at /tmp/factory-framework-review.md.

Pitfalls

V1 submits Workflow CRDs through Kubernetes credentials, not Argo REST tokens. Its active-work subtraction is not atomic deduplication. Its registry, configurable rules, monorepo paths and service-owned dispatch should not be copied wholesale. V1 discovery and worker completion predicates also need explicit alignment when ported. The old notes contain both shared-image and split-image alternatives; neither is settled.

Improvements

Before implementation, settle named check results, public dispatch versus worker execution, job receipts versus persisted outputs, resource context, and the chosen Argo authentication/transport contract. Prove a local CLI-to-worker vertical slice before adding HTTP and cluster submission. Keep recommendations marked as proposals until reviewed rather than documenting them as shipped architecture.

Navigation

Type to search…

↑↓ navigate↵ selectEsc close