Skip to content

research-log.md

Latest commit

 

History

History
70 lines (60 loc) · 4.03 KB

research-log.md

File metadata and controls

70 lines (60 loc) · 4.03 KB
Raw
layout research-log
title Research Progress Log
subtitle A dated public ledger of meaningful research updates, artifacts, formalization milestones, result-status changes, and inspection routes.
lane support
shell home
type support_page
support_type research_log
status canonical
last_updated 2026-05-23
updated May 2026
permalink /research-log/
section Research Log
summary The Research Progress Log is the program's dated public ledger of meaningful research-stream events — new artifacts, registry additions, result-status changes, falsification updates, formalization milestones, errata, release packets, and inspection-route refinements.
summary_short The program's dated public ledger of meaningful research-stream events — distinct from the Changelog and the Corpus Changelog.
summary_cards
title body
Typed and dated
Every entry carries a stable id, a date, a type drawn from the IA §4.4 enum, and a status. Entries are appended; nothing is silently rewritten.
title body
Not a blog
Not a newsletter, not a press feed, not a marketing surface. Operational ledger language only, sized for reviewers and journalists.
title body
Distinct from /changelog/
The Changelog records site, layout, and release changes. The Corpus Changelog records semantic corpus corrections. This log records the active research stream.
right_rail
related meta
title url
Publications
/publications/
title url
Latest Publications
/publications/latest/
title url
Changelog
/changelog/
title url
Corpus Changelog
/corpus-changelog/
title url
About this Site
/about-site/
type scope status updated
Support page
Research progress ledger
Canonical
May 2026

What this page records

This page records meaningful research-stream events — new publications, registry additions, result-status changes, falsification-pack updates, formalization milestones, errata, release packets, and refinements to the inspection routes that let readers check claims. Each entry is typed, dated, and pinned by a stable identifier so future references resolve.

What it does not record

This page is not a blog, not a newsletter, not a press feed, and not a replacement for [Publications]({{ '/publications/' | relative_url }}). Three near-adjacent surfaces deliberately do not overlap:

Surface Records
[Changelog]({{ '/changelog/' relative_url }})
[Corpus Changelog]({{ '/corpus-changelog/' relative_url }})
[Publications]({{ '/publications/' relative_url }}) / [Latest]({{ '/publications/latest/'
Research Log (this page) Active research progress and artifact / process updates

If you are tracking a single published artifact, start at [Publications]({{ '/publications/' | relative_url }}). If you want the program's near-term progress, this is the right page.

How entries are constructed

Each entry follows the IA Doctrine v5 §4.4 schema: a stable rlog-YYYY-MM-DD-NNN id, an ISO date, one of nine type values (publication · registry · taulib · result-status · pre-registration · falsification · erratum · release · website), a status (recorded · updated · superseded · corrected), a title, a short operational summary, optional linked artifacts, and related lanes. Entries are appended; older entries are not silently rewritten.

The current backfill starts in late April 2026. The cadence is intentional — not a daily log, not a release-engineering ticker, but a record of events the program judges worth reading later.