Orchesity
PricingContactDashboard

Product docs

Generate accountable backend scaffolds

These docs explain the operational path from prompt to artifact: how Orchesity interprets stack intent, streams generation progress, records readiness evidence, and exports generated projects.

Contents

Generate flowProof packRealtime progressDownload and GitHubEnvironment
Generate flow
  1. 1Submit a natural-language prompt from Dashboard > Generate.
  2. 2Orchesity extracts explicit framework and language preferences from the prompt or selector.
  3. 3The backend creates a generation record, charges credits, and starts the generator engine.
  4. 4Progress streams through WebSocket while database polling remains the fallback path.
  5. 5The finished artifact is snapshotted with readiness checks and proof metadata.
Proof pack

Every completed generation writes `.orchesity_artifact.json`. The proof pack is the human-readable evidence layer inside that manifest.

Prompt contract
What the agent understood: prompt summary, interpreted stack, explicit constraints, and excluded assumptions.
Decision ledger
Why the selected stack and artifact shape were chosen, with evidence references.
Readiness proof
Critical checks, validation findings, run command, failed blockers, and readiness classification.
Repair plan
Actionable repair steps for failed critical checks, wired to Repair Artifact through Coding Polish Agent with rollback support.
Generation black box
Trace keys that connect requested intent, planned stack, realized artifact, and readiness report.

When proof status is needs_repair, the dashboard exposes Repair Artifact. This starts a validation-guided Coding Polish Agent pass using the proof pack repair plan, then records the polish report and rollback snapshot on the generation detail page.

Realtime progress

Generation progress streams over ws://host/ws/<client_id>. The frontend reconnects on transient disconnects and falls back to polling generation history when the live stream is interrupted. Backend reconnect handling is identity-aware, so a stale socket cannot remove a newer connection for the same client id.

Download and GitHub

Completed generations can be downloaded as ZIP archives or pushed to GitHub after OAuth connection. GitHub preflight checks verify repository name, connection status, artifact availability, and whether the generation was already pushed.

Environment
NEXT_PUBLIC_API_URL
Frontend API base URL.
NEXT_PUBLIC_WS_URL
Optional explicit WebSocket URL; otherwise derived from API URL.
BACKEND_URL
Public backend URL used by the product.
BACKEND_INTERNAL_URL
Internal backend callback URL for generator webhook updates.
DATABASE_URL
PostgreSQL connection string.
OPENAI_API_KEY
LLM provider key for generation and polish flows.
Important limitation

Proof packs document generation evidence. They do not replace human code review, security review, dependency review, or production acceptance testing.