Cinch
Sign inStart a workspace
Explore

Living release log

What changed—and what actually shipped.

This timeline records production releases rather than every commit. Each entry connects the deployed source to its purpose, evidence, architectural decisions, known limits, and recovery posture.

PUBLIC RELEASE RECORDSchema v1
3

production releases indexed

1application2marketing100%rollback stated
Last verifiedAugust 10, 2026
ScopeCinch application and public-marketing repositories
PostureCurated public engineering snapshot

Production timeline

Release units, not activity theater.

Commits are useful evidence, but a release is the meaningful public unit: a particular source revision reached production, passed a named proof boundary, and retained a recovery path.

marketingMarketing 14
exercised

Public engineering dossier

Added a layered technical portfolio covering decisions, infrastructure, delivery, resilience, and engineering field notes without coupling the public site to the application runtime.

2ee78482
documentationarchitectureresilience

Highlights

  • Published six focused engineering routes from one curated evidence source.
  • Made ADR maturity, consequences, evidence, and known limitations visible together.
  • Added regression coverage for public claims and the marketing runtime boundary.

Evidence

  • Production Sites version
  • Rendered-route regression suite
  • Both canonical hosts verified
Related decisionsADR-001ADR-002MKT-001
Known limits

The public dossier is a curated projection; private implementation evidence remains in the owning repository.

Recovery

The prior immutable Sites version remains available for independent rollback.

marketingMarketing 13
exercised

Shared Cinch brand package

Moved the public site onto the published Cinch brand package so the application and marketing surfaces can share one versioned visual identity.

c3978bfe
design-systemdocumentation

Highlights

  • Consumed the public brand package as a pinned dependency.
  • Synchronized favicon and touch assets from the same package version.
  • Added tests that detect drift between packaged and published assets.

Evidence

  • Published package version
  • Brand asset synchronization test
  • Production marketing release
Related decisionsMKT-001
Known limits

Application adoption is owned and released independently by the application repository.

Recovery

The prior immutable Sites version remains available for independent rollback.

applicationApplication 2026.08.10
exercised

Health-gated blue/green application delivery

Repeated the complete stateless web-fleet promotion after candidate readiness while preserving the separately managed stateful synchronization service.

f491c695
infrastructureresiliencesecurity

Highlights

  • Started and validated both replacement web instances before promotion.
  • Verified the public release identity against the promoted source revision.
  • Completed all public checks while the serving synchronization image remained unchanged.

Evidence

  • Candidate readiness records
  • Exact source identity verification
  • Post-cutover public journeys
  • Unchanged synchronization image proof
Related decisionsADR-001
Known limits

Active authenticated-session and WebSocket continuity through promotion remains an explicit evidence gap.

The current stateful synchronization singleton has a separate availability limit.

Recovery

The prior immutable application image and guarded recovery path were retained for the rollback window.

Publishing contract

The platform supplies facts. Marketing supplies restraint.

After a successful production deployment, the application pipeline can propose a sanitized manifest. Validation rejects unknown decisions, incomplete evidence, missing recovery posture, chronology drift, and common forms of sensitive material before the entry can publish.

01Deploy succeeds

The exact production source is known.

→
02Manifest generated

Facts, evidence, gaps, and ADRs are serialized.

→
03Public PR reviewed

Claims and sensitive details cross a deliberate boundary.

→
04Log publishes

The marketing release remains independently reversible.

Behind the releases

See the decisions that constrain how Cinch evolves.

Decision register