EntityMesh does not publish one universal build-time promise. Timing depends on whether the verified site is crawlable, source material is complete, provider/runtime capacity is healthy, generated drafts pass grounding and quality gates, and reviewers are available. Durable jobs expose queued/running/retrying/blocked states rather than pretending every build is immediate. Approval also does not publish by itself: an authorized user must explicitly publish after all required artifacts pass. A reviewed proposal can give a scope-specific expectation, but repository automation is not evidence of a guaranteed delivery date.
Your approval pace determines the build timeline
Source readiness, execution capacity, quality gates, and your approval pace all matter. Publishing is a separate explicit action.
You can approve and publish in stages at your own pace
You can review in stages, but each public version is created only by an explicit publish that passes the current gates. Start with the free diagnostic.