For the complete documentation index, see llms.txt.

Documentation

Repository docs

This route renders the repository README and markdown under docs/ .

Source: docs/SMART_ANALYSIS.md

Rendered document

docs/SMART_ANALYSIS.md

Parsed server-side (markdown to HTML in the app). Same bytes you get from the checkout.

Smart Analysis

Smart Analysis is the repo scan that runs before you deploy. It detects how your app should be built, generates Railpack plans (or recognizes a Dockerfile), and optionally verifies the build.

When to run it

  • First time deploying a service
  • After significant repo changes (new framework, Dockerfile, monorepo layout)
  • When a deploy failed due to build or scan issues — then use Improve scan with failure context

Re-scanning updates scanResults linked to your deployment and refreshes the blueprint.

Scan progress nodes

NodeDescription
ScannerResolve commit and repo scope
Clone repoCheck out repository at commit
ClassifierDetect deploy shape and deploy units
Railpack prepareGenerate Railpack build plan per unit
Deploy briefingOperator summary (markdown)
Build and repairVerify build; AI repair loop when enabled
FinalizeSchema version and final build status

Watch scan logs in the UI for the first or error line if a node fails.

Deploy shapes

ShapeMeaning
staticPlain static files, no build step
static_buildSPA or static site with a build step
serverServer app built and run as a container
multiMultiple deploy units (compose-style)
existing_dockerUses repo Dockerfile instead of Railpack

Deploy routing uses shape plus Railpack deploy.startCommand to choose ECS vs S3. See How It Works.

Scan result fields

Key fields in the stored analysis response:

FieldPurpose
deploy_units[]Name, root, type, framework, port, railpack_plan
build_statuspassed, failed, skipped, etc.
build_verificationVerification attempt logs and message
repair_history[]AI repair attempts if build failed initially
deploy_briefingHuman-readable scan summary
railpack_versionRailpack version used for the plan

Build verification

When enabled, SD Artifacts runs a test build after plan generation. Outcomes:

  • Passed — safer to deploy; blueprint shows green build status
  • Failed — review build_verification.log_excerpt and repair_history
  • Skipped — verification not run for this scan

Use Improve scan to send failure logs back to SD Artifacts for remediation.

Improve scan (feedback)

After a failed deploy or failed verification:

  1. Open Improve scan from scan results
  2. Add context about what failed
  3. SD Artifacts re-analyzes with your failure evidence
  4. Review updated plan before redeploying

Package path (monorepos)

Scans are scoped to a package path per service (for example apps/web). The classifier and Railpack prepare run in that scope while still understanding repo layout.

See Monorepos and Multi-Service.

Related