✳ MESH.

Ruby engineering · integration reliability

A release can succeed.
Its response can disappear.

MESH keeps the operation, explains the uncertainty and reconciles with the partner — without publishing twice.

The failure is real

From a defective package to a confirmed release.

74 seconds · English captions

Unedited browser screencast of the existing application. Russian UI, English captions, no audio. The lost response is injected through the real API; the independent Node/SQLite partner commits before the reply is lost. No API responses or displayed states are mocked.

01 / Validate

Reject the exact defect

A manifest digest mismatch returns FILE_DIGEST. Publishing remains disabled until the corrected bytes pass validation and the real scanner.

02 / Diagnose

Keep uncertainty visible

HTTP_TIMEOUT becomes unknown. Read-only diagnostics explain lookup_only and explicitly state that the report did not query the partner.

03 / Reconcile

Recover the same operation

The ordinary dispatcher looks up the original operation. Its identity, digest and sequence must match before confirmation.

Read the full English transcript
  1. MESH: Ruby backend engineering, from partner package to a confirmed release.
  2. A studio submits a private ZIP and a manifest. Validation checks exact bytes, inventory and the real scanner.
  3. The bad package is rejected: FILE_DIGEST explains the defect. Publishing stays disabled.
  4. A corrected package passes. The validation is bound to its digest, policy and integration configuration.
  5. Inject a lost response through the real API. The independent HTTP partner commits the release before the reply is lost.
  6. HTTP_TIMEOUT becomes unknown. A missing response does not authorize another publish request.
  7. Read-only diagnosis provides a safe next action: look up the same operation ID. It does not query remote state.
  8. The ordinary dispatcher reconciles by lookup. Confirmation must match the operation, artifact digest and sequence.
  9. One real publish request, one remote effect. The captured workflow is a local simulator exercise, not a live external studio.

Download video · Download captions · Capture report

A useful frontend, a Ruby core

See the workflow, then inspect its guarantees.

The marketplace follows brief → proposal → immutable agreement → versioned delivery → acceptance. Publishing adds a focused external integration lab. All images below are actual application captures; portraits and portfolio artwork are illustrative demo assets.

Executed, not just configured

Follow the evidence.

Exact sources and limits ↗

Accepted application release: 3d849af. Recording and first clean preparation: fa40e97, with application source unchanged. Each linked report has its own source revision and environment. A scan is a dated observation, not a permanent security guarantee.

Explain the guarantee and its cost

Small enough to understand.
Serious enough to investigate.

Eight-domain Rails monolith. Framework-independent Domain/Application layers for Publishing execution. PostgreSQL, private storage and HTTP adapters protect real invariants; the rest stays idiomatic Rails.