Development log · July 2026

Autonomous development loop: active

MoreYears.news is moving from a launch page toward a complete evidence-first publication through small, reviewable changes. Each increment is specified, built, tested, and checked in production before the next one begins.

The important guardrail

Product development can advance automatically when a change is low-risk and reversible. Editorial automation remains gated: code checks alone cannot approve medical claims, sources, or health advice.

Infrastructure identity, secrets, authentication, destructive data changes, paid services, and major architecture choices also stop for human approval.

Release history

Cycle by cycle

Newest first. Completed entries summarize changes checked in production; the current release candidate remains marked pending until its post-deployment verification finishes.

  1. Verification pending

    Built the trust and transparency center

    This release candidate addresses issue #21 through PR #26.

    • Adds distinct About, Editorial standards, and Corrections routes with a cohesive trust-center design and cross-links.
    • Makes the mission, source roles, uncertainty language, disclosures, AI-assistance boundaries, and publication approval boundary visible before regular coverage begins.
    • Defines dated, explained, preserved correction history while honestly stating that no public intake channel exists yet.
  2. Production verified

    Built a practical research-guides collection

    This release candidate addresses issue #20 through PR #24.

    • Adds a complete Guides landing page plus plain-language clinical-trial and biomarker interpretation guides.
    • Separates evidence maturity, trial design, measurement reliability, surrogate status, function, healthspan, and lifespan without analyzing a real intervention or product.
    • Integrates the collection with shared navigation, homepage, metadata, sitemap, deterministic validation, and responsive QA.
  3. Production verified

    Built the evidence-oriented article experience

    This release candidate addresses issue #19 through PR #22.

    • Adds an honest Latest page and a clearly labeled article-format demonstration without publishing a real medical or scientific claim.
    • Makes content status, evidence maturity, study population, reporting confidence, caveats, provenance, disclosures, and update history visible to readers.
    • Integrates both routes with the homepage, shared navigation, metadata, sitemap, deterministic checks, and hosted responsive QA.
  4. Production verified

    Increased the loop’s queue depth and cycle ambition

    This release candidate addresses issue #17 through PR #18.

    • Requires the controller to prepare three dependency-ready issues before a normal build, so claiming one leaves two queued.
    • Raises the normal target to a coherent reader-facing increment spanning roughly one to three related routes and their complete integration and QA.
    • Preserves one active implementation PR, one issue per build, every risk boundary, and every release gate.
  5. Production verified

    Made every content page easier to navigate

    The cycle completed issue #15 through PR #16.

    • Added one consistent Home, Evidence guide, and Development log navigation pattern across every content page.
    • Added a semantic, no-JavaScript mobile menu with large touch targets, visible keyboard focus, and honest current-page state.
    • Added hosted Chromium QA that measures responsive behavior and preserves screenshot evidence; it caught and prevented a real desktop-navigation defect before release.
  6. Production verified

    Made missing pages honest and useful

    The cycle completed issue #7 through PR #14.

    • Added a branded, accessible not-found page with a clear route back to the homepage.
    • Replaced the misleading homepage fallback so unknown URLs return the custom page with an honest HTTP 404 status.
    • Added hosted container checks for existing routes, direct 404-page access, missing-path behavior, and automatic cleanup.
  7. Production verified

    Published a guide to reading longevity evidence

    The cycle completed issue #6 through PR #13.

    • Added a five-rung guide explaining what cell, animal, observational, randomized, and replicated human evidence can and cannot establish.
    • Covered the cross-cutting questions that shape evidence quality, relevance, and practical meaning.
    • Linked the guide from the homepage, added it to the sitemap, and extended deterministic route and content validation.
  8. Production verified

    Made the site discoverable and repaired a release defect

    The cycle completed issue #5 through PR #8, then used production QA to find and fix an incorrect web-manifest content type through issue #9 and PR #10.

    • Added crawl rules, a sitemap, canonical URLs, social-sharing metadata, a favicon, a web manifest, and a share card.
    • Extended deterministic validation for the new discovery and sharing assets.
    • Verified both HTML routes and every new asset in production, including the corrected application/manifest+json response.
  9. Production verified

    Established the governed autonomous development loop

    The first manual cycle completed issue #2 through PR #4.

    • Added durable product, architecture, editorial, roadmap, and release-gate guidance.
    • Installed the GitHub queue, controller state, labels, issue template, deterministic site validation, and container CI.
    • Published this development route and verified the homepage and log in production at desktop and mobile sizes.

Queue snapshot

Up next

Two dependency-ready reader improvements remain queued while the trust center is reviewed.

  1. Issue #23 · Build ready

    Build an evidence-aware homepage news hierarchy

    Turn the homepage into a clearer publication front using only existing, honestly labeled demonstration content and guides.

  2. Issue #25 · Build ready

    Create science and interventions orientation hubs

    Add useful publication maps for aging-science areas and intervention categories without fabricating coverage.

This is a published snapshot, not a live GitHub feed. Priorities can change when dependencies, production incidents, or QA findings emerge.

← Return to MoreYears.news