Engineering log · public evidence

foldready

Fold-Ready Score + porting engine for iOS apps on the iPhone Fold (iOS 27). Swift CLI + Next.js web.

Releases · changes · evidence

How this project evolved

A chronological selection of actually merged changes, GitHub releases and, where verified, a public project page. Every entry links to its source.

  1. Merged code change

    product: evidence-first Duo offer, research and customer review experience

    Merged source-code change; production results are not inferred.

  2. Documented prototype (self-reported)

    Input continuity tested in a synthetic Duo simulator

    A repository-authored milestone backed by a GitHub source. A code date alone does not prove the prototype was usable.

    A synthetic UIKit form retained its value through a simulated closed → open → closed journey. This does not validate a physical device or any client application.

  3. GitHub release published

    v0.5.0

    Officially published on GitHub Releases; deployment is not assumed.

  4. GitHub release published

    v0.4.0

    Officially published on GitHub Releases; deployment is not assumed.

  5. Merged code change

    Rebalance the score against a measured corpus (contract v2)

    Merged source-code change; production results are not inferred.

  6. Merged code change

    Readiness gate: result contract v1, CI gate, GitHub Action, work-order handoff

    Merged source-code change; production results are not inferred.

  7. Documented prototype (self-reported)

    Documented diagnostic contract and CI quality gate

    A repository-authored milestone backed by a GitHub source. A code date alone does not prove the prototype was usable.

    A versioned results contract and CI gate help compare source-code signals. No score certifies an app's real device compatibility.

  8. Repository created

    foldready

    Date the GitHub repository was created, not the verified date of the first prototype.

A selective history: GitHub provides repository, merge and release dates. Additional product milestones are source-linked maintainer statements, not independent certification. Shipping, deployment and user adoption are never inferred from code activity.