Two-week plan: 5–16 October 2026
Scope confirmed by Dmitriy · 4 October 2026: store connection, catalog reads and base-price changes only, with explicit owner approval. DigitalOcean is confirmed for hosting; the test OpenCart store is confirmed. The schedule and exact infrastructure still need agreement.
Proposed schedule · drafted 4 October 2026 from the Jira project STOR and the decisions log. Not yet agreed with Yevhen or Artem; the dates are targets, not promises. Two weeks fit the Admin flow with one real change; everything the product is meant to do beyond that is listed under After 16 October, not hidden.
By Friday 16 October our test OpenCart store is connected to a hosted Store Deputy, its owner asks the Admin Agent about the catalog and approves a base-price change that is applied and verified. Today none of this leaves a developer's machine, and no real store has ever been connected.
Who does what: Yevhen — API, app, the single MCP, Agentfy and end-to-end checks. Artem — the OpenCart module: its REST API, Connect, reads and the one write. Dmitriy — decisions, hosting and accounts, the pilot store, acceptance on both Fridays.
The finish line
Done on 16 October means all of this is true on a hosted Store Deputy, not locally:
- The owner installs the module in our test OpenCart 3 store, presses Connect, signs up, and comes back connected. The Admin Agent is created on its own.
- The owner asks about products, prices and stock in the chat and gets answers from the test store, with a real language model.
- The owner asks to change prices of a few products, sees the exact list — product, old price, new price — and approves it.
- The prices change in the store, are read back, and the owner gets a receipt: applied, skipped, why.
- A price that changed in the meantime is skipped, not overwritten. Pause in the store's admin stops the agent.
- Every tool call is in the journal; a revoked or paused store refuses calls.
Decisions needed on Monday
Without these the schedule slips from day one.
| Decision | Why it blocks | Owner |
|---|---|---|
| Confirmed 4 October: connection, catalog reads and approved base-price changes only | Scope agreed; other write operations are outside these two weeks | Dmitriy |
| DigitalOcean confirmed 4 October. Dmitriy determines the configuration: projects, domains and resources | Provider and decision owner agreed; configuration details pending | Dmitriy |
| Dmitriy selects the existing or separate Agentfy pilot environment on DigitalOcean | Environment choice and model access details pending | Dmitriy |
| Test OpenCart confirmed 4 October | No merchant recruitment or live-store installation required for these two weeks | Dmitriy |
| Confirmed 4 October: Yevhen and Artem agree REST 1.0 schemas and examples on Monday 5 October, then freeze it through 16 October | Changes only by joint agreement to resolve a blocking issue | Yevhen, Artem |
Week 1 · 5–9 October: connect through REST, read with a real model
| Days | Yevhen — API, app, MCP | Artem — OpenCart module | Dmitriy |
|---|---|---|---|
| Mon 5 | Merge the stacked branch (STOR-19, 21, 23, 26) and STOR-48 into main; bring Jira statuses in line with the code | Finish STOR-38 (reproducible build, install regression). Start STOR-18: REST 1.0 routes, authentication, replay protection, manifest | The decisions above, before lunch |
| Tue 6 – Wed 7 | Host API, app and website with a public address; connect the hosted Store Deputy to the Agentfy environment (STOR-8 groundwork). STOR-25: the REST adapter in the API, built against the contract's fixtures until Artem's endpoints land | STOR-18 complete, including pairing. STOR-24: read endpoints for catalog, base price and stock, reusing the STOR-39 reader | Prepare the test OpenCart store, test catalog and access for acceptance |
| Thu 8 – Fri 9 | STOR-5, part 1: proposal → approval → versioned job in the API; the approval gateway replaces the stub in the policy; the app shows the review table with Approve | STOR-20: Connect and return through REST 1.0 pairing. STOR-42: settings and Pause in the module's admin. STOR-27: first contract tests on both test shops | Friday review |
Friday 9 October: a test shop connects to the hosted Store Deputy through REST 1.0, the Admin Agent is created automatically, and it answers a catalog question with a real model. Reads only; no write yet.
Week 2 · 12–16 October: one approved change, on the test store
| Days | Yevhen — API, app, MCP | Artem — OpenCart module | Dmitriy |
|---|---|---|---|
| Mon 12 – Tue 13 | STOR-5, part 2: execution through the module's write endpoint, read-back, receipt in the chat and the app, journal entries. STOR-28: the end-to-end Admin flow on the hosted stack, including every refusal | STOR-5, module side: the base-price write endpoint that accepts only an approved operation, conditional update, ledger (STOR-43), the product-saved event from the spike. Negative tests for writes in STOR-27 | Approve the wording of the review table and the receipt; choose the few products for the test store’s first change |
| Wed 14 | Install on the test OpenCart store together with Artem; fix what breaks | Same: extensions, renamed admin, HTTPS, PHP version | Present at the install |
| Thu 15 – Fri 16 | Fixes from the test store. The website's early access leads to the hosted app. STOR-22 only if the Agentfy change is small; otherwise record the gap | Pilot build of the module with a separate pilot key; install and uninstall regression; compatibility notes for the pilot | Friday acceptance against the finish line; decide what comes next |
Friday 16 October: the finish line above, on our test OpenCart store.
After 16 October
Not in these two weeks, and not promised to the pilot:
- Shoppers and the cart — the Frontend Agent and stage B (STOR-29–37).
- Supplier price file: matching, exceptions, the recurring job (STOR-6).
- Creating products (STOR-9), sales reports (STOR-10), scheduled checks (STOR-11).
- Plans, billing and Upgrade (STOR-12, 13); pricing is not announced.
- OpenCart 4 (STOR-14).
- Any write other than the base price: stock, orders, categories, descriptions, customers. Each needs its own approval, verification and recovery rules before it is built.
- The platform admin panel: what it is for has not been decided.
Risks
| Risk | What it does to the plan | What softens it |
|---|---|---|
| The module's REST 1.0 has not been started; everything in week 2 depends on it | Week 2 slips by however many days STOR-18 slips | Yevhen's adapter is built on contract fixtures from Tuesday; the contract is frozen on Monday |
| DigitalOcean selected; infrastructure and model access still need setup | Friday 9 depends on a reachable stack | Configure addresses, access and Agentfy before integration |
| Test environment unavailable | End-to-end acceptance is blocked | Prepare HTTPS access from DigitalOcean and reproducible test data |
| STOR-22 needs a change inside Agentfy, another team's repository | The agent's "who is asking" stays the agent itself, not the person | Kept optional in week 2 and recorded if it does not land |
| Test coverage does not prove real-store compatibility | A live rollout needs separate validation later | Record supported versions and extension limits; keep real-shop pilot outside this milestone |
| Two people and ten working days, no slack | Any slipped item moves the finish line | Scope is cut, not stretched: reads first, one write, nothing else |