Open questions
Outstanding decisions after the September 2026 research. Suggested answers are in Proposal 001; they are not automatically accepted decisions.
The immediate uncertainty is whether a reachable merchant will repeatedly pay for the proposed job. Engineering work should reduce that uncertainty alongside proving the connector.
| Decision | Current recommendation or gap | Evidence needed next |
|---|---|---|
| Initial workflow | Supplier price updates; catalog-content preparation is the fallback | Observe actual recent work and compare existing import tools |
| Target merchant and geography | Small operating team, recurring files; geography not selected | Recruit accessible shops and document eligibility |
| Platform/version | OpenCart first; one release family | Pilot version/extension inventory and a successful connector spike |
| Founder acceptance | This is a proposal | Explicit acceptance or changes to Proposal 001 |
| Interface | Chat, review tables, Today and history | Merchant task observation with a prototype |
| Authority | Per-job approval before writes; later bounded delegation | Tests of the proposed contract and merchant comprehension |
| Data handling | Minimize data; define retention and provider handling before onboarding | Deployment/provider decision and pilot requirements |
| Price and channel | Paid workflow experiment; agencies plus extension discovery | Paid continuation and measured support/acquisition effort |
| Agentfy reuse | Source-level candidates identified, integration unverified | Tool execution, tenant isolation, background recovery and approval-contract spike |
| Name | Store Deputy remains an internal working name | Resolve the existing name question before external launch |
The roadmap defines proposed gates. There are no completed interviews, customers or measured business outcomes to report yet.