VyDex

VyDex keeps important claims in AI, science, and technology tied to the evidence, limits, and later updates that change how they should be read.

Table of Contents

• What It Solves
• What It Does
• Why It Is Different
• Current Status
• Major Milestones Roadmap
• Links
• License And Notices

What It Solves

Important frontier claims are often scattered across announcements, papers, articles, and later corrections. Readers, researchers, and builders then have to reconstruct what was claimed, what the evidence supports, and whether later information changed the conclusion. VyDex keeps that history in one evidence record.

What It Does

Maintains versioned evidence records. Each Entry keeps the claim, evidence, scope, caveats, statuses, sources, and methodology context together. Immutable publication snapshots preserve the history behind the current record.

Publishes a portable static ledger. The public site is generated as HTML, CSS, JavaScript, and JSON from repository-controlled records. It does not require a runtime database, backend, Pages Function, or Worker.

Produces deterministic data releases. Each dataset release has a fixed release identity, an immutable Schema and export path, and a complete file manifest. A stable convenience URL can point to the latest immutable artifact without replacing it.

Checks changes without publishing them. Pull requests and pushes run type checking, unit tests, static generation, sitemap validation, Playwright journeys, and Axe checks. These checks are read-only: they cannot create release commits or deploy the site.

Search, filtering, public Entry revision browsing, and exact historical citation remain planned capabilities rather than current Stage 1 behavior.

Why It Is Different

VyDex is not a daily newsletter, prediction market, leaderboard, or general technology-news feed. Those formats organize information around recency, popularity, or forecasts. VyDex organizes it around a maintained claim and the evidence needed to assess it.

History remains authoritative. Current pages come from canonical records and immutable snapshots; generated hosting output and deployment history cannot replace them.

Limits stay beside the claim. Scope and caveats are part of the record rather than footnotes added after a conclusion.

Hosting remains replaceable. Cloudflare Pages serves complete static output, but it does not own release identity or the permanent evidence archive. A future custom domain can replace the Pages hostname without changing route paths or record IDs.

Current Status

Stage 1 contains the wide evidence-ledger Homepage, generated Entry v2 and Topic Trail pages, the material Changelog, current Methodology 2.0.0 and retained Methodology 1.0.0 routes, the About and Scope Limits page, the Dataset 2.0.0 Export JSON page, and a static not-found page. These surfaces share the Frontier Atlas design system and remain readable without browser JavaScript. Production builds also generate a complete sitemap index and child sitemap, and robots.txt advertises the production sitemap index.

The active release and its immutable Dataset are selected by the committed files under generated/release-data/. Earlier releases remain retained in that history and archive rather than being replaced by later deployments.

The release gate validates canonical records and snapshots, constructs one release model, builds into isolated runtime storage, verifies the Schema, export, routes, redirects, links, counts, and navigation, then runs the complete Playwright and Axe matrix against that exact staged output. A byte-based selection check first detects whether committed source changed the active public artifact; the explicit synchronization command creates a successor only when one is needed. Promotion replaces local dist/ and the manifest only after every check succeeds.

Pull requests and pushes run the same read-only validation. After a push to main passes, a separate GitHub Actions workflow checks out that exact validated commit, repeats the application and browser checks, builds dist/, and deploys the static output to the approved Cloudflare Pages project. Deployment does not generate release commits, compare marketing copy, or automatically roll production backward.

A separate manually dispatched workflow can still rehearse production rollback under the protected GitHub production environment. That rehearsal is an explicit maintenance operation and is never part of an ordinary push or deployment.

Stage 1 is live at https://vydex.pages.dev. The initial production deployment passed the complete hosted verification suite, and the protected rollback rehearsal verified the earlier deployment, restored the intended deployment, and passed final verification. Public Entry revision browsing and search remain later work.

Major Milestones Roadmap

• Stage 1 — Public Seed Ledger. Complete and live. The initial evidence records, Topic Trails, Methodology, About content, immutable Entry histories, Frontier Atlas interface, public pages, JSON export, release identity, manual Cloudflare Pages deployment, hosted verification, and protected rollback rehearsal have passed live acceptance.
• Stage 2 — Searchable Evidence Database. Users can search real Entries, filter by evidence fields, and understand why results are ordered as they are.
• Stage 3 — Versioned Ledger and Citation. Users can inspect Entry history, open older versions, see what changed, and cite an exact version with its applicable Methodology.

Roadmap wording describes direction, not released functionality. See the changelog for implemented changes.

Links

• VyDex website — The canonical public origin; the latest branch may be ahead of the deployed site.
• Documentation — These docs track the latest main branch. Released app builds may not include every documented change yet.
• Quickstart
• Changelog — Includes unreleased changes available only in the latest commits.
• License

License And Notices

VyDex uses a split-license structure:

• Application and site source code: MIT License.
• Original database entries, methodology, reports, metadata, taxonomy, changelog records, and public data exports: CC BY 4.0, unless otherwise noted.
• VyDex names, logos, social-preview images, and brand assets are not included in those licenses.

Third-party material remains subject to its original terms. See NOTICE.md for attribution and third-party font information. Final public-distribution legal review remains the project owner's responsibility.