Open Questions and Risks

Highest-priority gaps

• The planned product backend and LangGraph graph are absent from the checkout.
• The frontend calls product endpoints that are not evidenced by server routes here.
• The executor currently has local/SQLite implementations while the plan targets MinIO/Postgres.
• Auth, tenant isolation, presigned URL policy, and rate limiting are design requirements rather than verified product behavior.
• Restart recovery needs an end-to-end test across checkpoints, mappings, and objects.

Risks and actions

Risk	Action
Plan/implementation drift	Track acceptance criteria against checked-in code
Untrusted code	Keep microVM/network policy and image allowlists mandatory
Lost workspace changes	Test crash-safe manifest flush and storage writes
Unauthorized artifacts	Enforce thread ownership at backend and object layers
Metadata divergence	Add SQLite/Postgres contract tests
Long-running runs	Define cancellation, leases, and cleanup semantics

Acceptance checklist

• Signed-in user creates a thread.
• Upload is authorized, stored in MinIO, and registered in Postgres.
• DeepAgent reads the file and executes generated Python in a microVM.
• Artifacts persist and render in the frontend.
• Backend restart resumes the same thread and sandbox mapping.
• Executor and product tests cover failure, limits, and ownership.