Execution Center  /  Core & Enterprise Stores  /  2026
◉ Phase 1 release 30 Nov · full scope by 16 Jan
Detailed day-wise & time-wise implementation roadmap · rescheduled 09 Nov 2026

VeloxIQ Core + Enterprise Stores
10 November — 30 November 2026

React + Vite + TypeScript (existing UI pages) • Node.js + Express + TypeScript • PostgreSQL 16 on Hostinger VPS • Nginx + PM2 • Cloudflare DNS/SSL/WAF • Cloudflare R2 nightly backups • Git with versioned API contracts for integrating applications.

Revised requirement, 04 Nov 202618 workdays · 3 Sundays off4 sprints + Phase 2 roadmap3 developers, no testersStarts from database architecture
21
Calendar dates
18
Scheduled working days
423 h
Total team capacity
141 h
Capacity per developer
0 / 216
User-tracked completed blocks

Team: three developers, each tests their own work

Monday–Friday: 10:00–13:00, 13:00–14:00 lunch, 14:00–16:00, 16:00–18:00, 18:00–19:00 (8 h). Saturday: 11:00–13:00, 13:00–14:00 lunch, 14:00–16:00, 16:00–18:00, 18:00–19:00 (7 h — assumed end time 19:00, please confirm). The last block every day is reserved for self-testing, PR review and merge, because there are no testers.

What 30 November delivers — and what follows

30 November = Phase 1 production release, not the whole application.
Only the brief UI pages exist today; database, backend, hosting and integrations start from zero. Three developers have 423 hours until 30 Nov. Core administration plus all 20 Stores workflows needs roughly twice that, so the remaining workflows are scheduled week by week in Phase 2 (below) instead of being squeezed in untested.

Phase 1 — live on 30 Nov

Hostinger VPS + Cloudflare + R2 backups, Git branching, CI/CD, database architecture
Core: company/project/site/store setup, users, roles, privileges, scopes
Core: versioned approval workflows (≤4 levels) and major-material allocation with Core Admin approval
Stores: WF01 vendors/items, WF02 MR, WF03 RFQ, WF04 PO, WF05 vendor response/advances (PMS mock)
Stores: WF08 GRN/QC, WF09 site stock, WF10 issues/returns, WF20 additional quantity, Phase-1 reports

Phase 2 — 01 Dec to 16 Jan

WeekDatesScope

4 sprints and milestones

Progress

0 / 216 blocks completed or verified

Source & priority

Baseline is the Enterprise Stores Requirements (revised 04 Nov 2026): Core owns company setup, users/privileges and approval configuration; Stores consumes them. BOQ is removed everywhere. Open items from requirement §9 appear as decision blockers rather than being guessed.

Time slots, hours and the Phase-2 week plan are planning estimates, not requirements.

Execution protocol — repeat every working day

10:00 — Stand-up (15 min)

Yesterday's merges, today's blocks, blockers, open PRs waiting for review. Saturday starts at 11:00.

16:00 — API hand-off

Backend developers push the day's endpoints to staging and update the OpenAPI contract in Git so the frontend can connect the same day.

18:00–19:00 — Self-test & PR

Each developer tests their own work, records evidence against the workflow number, opens a PR, reviews a teammate's PR and merges to develop.

Timeframe & milestones

21-day visual calendar

Select any working day to open its full three-person, time-blocked plan. Saturdays are working days (11:00–19:00). Sundays are rest days (15, 22, 29 Nov).

November 2026

Sprint exit criteria

216 individually trackable work blocks

Daily assignment details

Each card says exact activity, how to do it, dependency and proof of done. Click a task to expand. Status selections persist only in your local browser.

Requirement-to-build traceability

Complete scope tracker — whole application

Every Core function and all 20 Stores workflows are listed. Phase 1 – build is scheduled day by day until 30 Nov. Phase 1 – mock integration works against a labelled mock of another module. Phase 2 – scheduled has a planned week between 01 Dec and 16 Jan. Decision pending waits for the owner.

ID / RefFunctionalityDelivery classificationPlanned dateAcceptance scopeOwner / dependency
Hosting, Git and contract-first integration

Platform and module dependencies

Other VeloxIQ applications integrate through versioned OpenAPI contracts kept in Git — never by reading each other's database tables.

Deployment map

CLIENT & EDGE

React + Cloudflare

Existing React/Vite + TypeScript UI, served from Cloudflare Pages (or Nginx on the VPS). Cloudflare DNS proxy, SSL Full (strict) with origin certificate, WAF and rate limit on login.

APPLICATION

Express on Hostinger VPS

Node.js LTS + Express + TypeScript, run by PM2 behind Nginx reverse proxy. Core and Stores as separate modules in one backend with service interfaces. Attachments on VPS disk outside web root.

DATA & BACKUP

PostgreSQL + Cloudflare R2

PostgreSQL 16 on the VPS (localhost only) with core and stores schemas, scoped by company/project/site. Nightly encrypted pg_dump + attachments to Cloudflare R2, 7 daily / 4 weekly retention, tested restores.

Dependency register

Owner / systemNeededAffectsWhenResponsible

Git working rules (because other applications integrate)

Branches: main (production), develop (staging), feature/<workflow>-<short-name>, release/x.y, hotfix/x.y.z.
main and develop are protected: every change goes through a PR with one reviewer and green CI.
API contracts live in contracts/*.yaml; breaking changes need a new version (v2), never a silent edit.
Releases are tagged (v1.0.0) with a CHANGELOG so integrating applications know what changed.
Database changes only through migrations committed in Git — no manual changes on the VPS.
Secrets (DB, R2, SMTP, JWT keys) stay in server env files, never in Git.
No testers — developers own quality

Self-testing, cross-testing & release gates

Each developer tests what they build every day (18:00–19:00), every PR is reviewed by another developer, API tests run in CI, and on 27–28 Nov everyone tests someone else's module.

Acceptance-check matrix (requirement §8)

IDTest objectiveTarget windowTested byGate

For every workflow also test: authorised completion, returned correction, denied scope, missing settings, stale version, duplicate retry and failed cross-module handoff. Record evidence against the workflow number.

Gated milestones

30 November go/no-go checklist

Owner accepts Phase-1 scope and the Phase-2 schedule.
Zero open critical defects in stock ledger, scope/privileges or approvals.
Fresh backup in Cloudflare R2 taken before migration; restore tested twice.
Concurrent issue/receipt and duplicate-submit tests pass on staging.
PMS/HRMS/P&M mocks clearly labelled; no mock shown as verified money or identity.
Rollback runbook ready; monitoring and alert owner assigned.
Transparency and ownership

Open risks & decisions

These constraints must be consciously resolved. The 30 November target is not met by dropping controls or calling a mock integration live.

Risks and decision blockers, with mitigation

Change-control principles

The Enterprise Stores Requirements (revised 04 Nov 2026) is the source for this plan; it replaces the earlier SRS v2.1 plan (21 Oct–16 Nov), which is superseded. BOQ is out of scope everywhere. Core owns administration and approval configuration; Stores only consumes it. Hours are estimates — rebase them after Sprint 1 against actual progress.

No silent code or database changes. This HTML is a planning document; task statuses are saved in this browser only.