Problem
The foundation needed repeatable evidence that tenant separation, capture, drafting, approval, scheduling and queue handling worked together without intermittent browser failure.
Documented product proof · 17 August 2026
Harvtec Promote Validated Workflow
This dated product proof records what Harvtec measured in the Harvtec Promote release candidate using synthetic workspace data. It is technical validation, not a customer case study or a claim about live social-channel performance.
Problem, method and result
Proving the governed workflow before live activation
Method
Harvtec rebuilt the container stack from blank disposable volumes, applied every database migration, ran the Release build, audited dependencies and exercised PostgreSQL-backed and browser-level acceptance suites.
Promote contribution
Promote kept the seeded evidence in its workspace, prepared reviewable copy, required owner approval, created publish jobs and denied a restricted user access to another tenant's route.
Measured outcome
The Release build completed with zero warnings and errors; 15 unit and 25 integration tests passed; and three browser journeys passed 15 out of 15 runs over five repetitions.
Evidence basis
What the validation included
Fresh infrastructure
PostgreSQL, the one-shot migrator, the web application and the worker started from a clean disposable data set and reported healthy readiness.
Signed-in workflow
A seeded owner signed in, selected the Harvtec workspace and completed the capture-to-publishing-queue journey through the rendered application.
Negative access check
A restricted seeded user was denied a direct route into a different tenant, providing browser-level evidence for the workspace boundary.
Access
Public information, controlled systems
The evidence used synthetic records and non-customer credentials on a disposable local stack. It does not prove a production deployment, provider approval, successful live posts, customer adoption, marketing reach or commercial outcome.
Interpretation
Measured results and explicit exclusions
Measured
Build quality, automated application behaviour, blank-database migration, local container health and signed-in seeded workflow behaviour were measured on 17 August 2026.
Excluded
No customer identity, customer content, production credential, private campaign result or commercially sensitive provider data was used or published.
Recheck trigger
Harvtec will repeat operational acceptance after a hosted deployment and after any material workflow, provider, product-name or canonical-page change.