CodexReset.liveTibo 리셋 추적
● TRANSPARENT ALGORITHM WHITEPAPER

予測アルゴリズム手法とアーキテクチャ

ブラックボックスを排除した透明な予測アルゴリズムの全貌。

1. What counts as a published reset record

We do not publish a calibrated probability. A record can be counted only when its source text explicitly describes a completed reset benefit and includes a stable source URL and timestamp.

P(t) = Baseline(t) + W_tibo · S_tibo + W_status · S_status + W_cadence · S_cadence + W_milestone · S_milestone - Cooldown(Δt)

Banked credits, future promises, ordinary product posts, and personal rolling-window estimates are distinct claim types. They remain visible as observed records but never increment the public-reset count or calendar.

WEIGHT BREAKDOWN

2. Classification and correction rules

Tibo Posts Semantic HintRule: completed evidence
A source mentioning “reset” alone is insufficient. The publication classifier requires explicit completed-action wording; ambiguous items remain observed updates.
Reset Cooldown DecayRule: future notice
Future-tense statements such as “landing tomorrow” are notice-only, even if a later reset is expected.
OpenAI Incident StatusRule: context only
An OpenAI status page is linked as context only. This site does not assert platform health or infer compensatory actions from incidents.
Major Model Launch CadenceRule: no inference
Product releases are archived as context and never treated as reset evidence without an explicit completed-reset source statement.
User Milestone AchievementsRule: cited only
The site does not publish subscriber or active-user estimates unless a specific public source is displayed next to the claim.
San Francisco Working WindowRule: display only
Timezones change display only. They do not establish whether a reset applies to an account, plan, or region.
Community Consensus IndexRule: non-evidence
Community chatter is not confirmation evidence and is not used to publish a public-reset fact.
Edge Buffer HeadroomRule: unavailable
This site has no access to OpenAI capacity telemetry and does not infer capacity or account eligibility.
SOURCE HIERARCHY

3. Monitored Accounts & Verification Tiers

Tibo Sottiaux
Tibo Sottiaux PRIMARY
Head of Codex, OpenAI
@thsottiaux ↗
Sam Altman
Sam Altman EXECUTIVE
CEO, OpenAI
@sama ↗
OpenAI Official
OpenAI Official SYSTEM
Company Announcements
@OpenAI ↗
Kevin Weil
Kevin Weil PRODUCT
Chief Product Officer, OpenAI
@kevinweil ↗
OpenAI Developers
OpenAI Developers DEVREL
Platform & API Status
@OpenAIDevs ↗

3. Freshness, corrections, and limitations

Static source-linked history is preserved if an upstream source is unavailable. Live upstream labels are treated as observations until reviewed against this publication rule:
1. Preserve source URL, author, timestamp, excerpt, and provenance.
2. Classify the record as completed reset benefit, banked credit, notice-only, or unknown.
3. Publish only completed, source-linked records in reset counts and calendar markers.
4. Accept corrections through the contact page; a correction must link to public evidence.