05 · DEPLOYMENT
Ship with evidence
Move an exact source revision through checks, release, and observable health.
Reproduce the reference locally and identify the boundary of the hosted demonstration.
The engineering problem
A working screenshot proves little about persistence, simultaneous callers, or which code reached the host. A portfolio must make those claims inspectable.
STEP 1
Reproduce the reference
Download the complete source archive. Follow README.md to run npm ci, start the pinned PostgreSQL development server, migrate, seed synthetic data, and start the Deno application. The test database is separate from the demonstration database.
STEP 2
Name the hosting decision
This public companion runs inside the existing forit.us Deno controller. Each visitor's bounded workspace persists in Redis using a whole-document atomic compare-and-set. The downloadable service uses PostgreSQL and warehouse row locks. They implement the same core scenario through separate code paths.
STEP 3
Release an immutable revision
Controller changes are committed to its canonical GitHub branch and submitted to the existing services.v39.us broker. AWS runs release checks before switching the blue/green targets. A release receipt and the live health revision provide deployment evidence.
YOUR TURN
Make the behavior visible.
- Download and unpack the PostgreSQL reference.
- Use its documented migration, seed, test, and scenario commands.
- Compare the SQL transaction boundary with the hosted sandbox's CAS boundary.
Acceptance evidence
Record the commands actually run, database-backed test outcomes, and health revision. The companion's public limit is 24 concurrent workspaces, 30-minute sessions, 120 actions each, and synthetic data only.
Read the working source.
These files belong to the downloadable PostgreSQL reference. The hosted companion has its own bounded state machine and persistence adapter.
Design review
Which guarantees would need to change before this became a contracted warehouse service?
Review the tradeoff
The public companion needs bounded anonymous sessions, while a contracted service needs durable customer identity, enforceable access policy, operational reconciliation, backups, recovery evidence, and agreed billing terms.