Skip to content

Research Runtime Center V5.0 ​

Status: Frozen architecture
Scheduler: Research Runtime Scheduler V3.0
Effective: 2026-08-05
Timezone: Asia/Shanghai

Why V5 exists ​

V4 mixed long-term Research Program work with the Daily production line. The 09:00 Engine advanced a long-term object before the 10:00 same-day topic decision, so newly discovered topics could not complete Reading and Analysis before the 15:00 Production gate.

V5 removes that structural conflict.

Four independent runtime systems ​

RuntimeResponsibilityInputOutput
DailySame-day discovery, research, production and publicationSame-day signalsReleased Daily Research
WeeklyIndependent AI Research BriefPrevious seven days of validated Daily ResearchMaterial changes, connections, evidence and disputes, judgments, and open questions
AcademicFormal academic observationPaper, Benchmark, Specification or InstitutionAcademic Observation
ProgramLong-term governed researchIndependent Program queuesProgram transition and Program publication

The four systems have separate records, queues and operational timelines.

Daily Runtime ​

text
09:00 Discovery → Signal Pool
10:00 Queue → Today's Research Plan
11:00 Reading → Reading Result
13:00 Analysis → Research Object
15:00 Production → Publication Candidate
20:00 Publication → GitHub + Website + Commit Verify + Release

The three Daily columns are Digital Employee, Industry Architecture and Open-source Engineering. Each column must be Selected or No Selection every day.

Stage authority ​

  • Discovery executes the three Research Intelligence profiles.
  • Queue performs three-column triage only.
  • Reading executes Skill 03.
  • Analysis executes Skill 04.
  • Production executes Skills 05–08.
  • Publication performs release only.

From 2026-08-12, Analysis and Production also apply Editorial Architecture V2: research-question-first analysis, extensible article-type identification, dynamic content modules, evidence identities, research independence, six editorial gates, and an optional separately framed Community Edition. The V5 Runtime topology and stage order remain unchanged.

Production has one legal input: Research Object. Publication has one legal input: a complete Publication Candidate.

Independent schedules ​

  • Weekly Runtime: Sunday 20:30.
  • Academic Runtime: Wednesday 16:00.
  • Research Program Runtime: Monday 12:00.

Program covers TMPA, FCoP, CodeFlowMu, Digital Employee and Research Operating System. It never enters Daily Runtime.

Runtime Records ​

V5 creates separate JSON records under:

  • research/runtime/records/daily/
  • research/runtime/records/weekly/
  • research/runtime/records/academic/
  • research/runtime/records/program/

Every terminal shift reports Input, Work Result, Output, Next, Metrics, Evidence and Artifacts.

GitHub Actions and ChatGPT workers ​

GitHub Actions opens execution slots. ChatGPT workers perform the actual research. An opened slot remains Waiting until the worker writes a valid result. Scheduler execution must never manufacture Completed.

Freeze rule ​

After V5.0, the four-system separation, the six Daily stages and the nine Scheduler V3 task identities are frozen. Future work is optimization: source quality, worker effectiveness, metrics, UX, evidence quality and publication quality.

Last updated: