FACTUAL ACTIVITY RECORD · An activity record based on work that took place
Establishing non-applied Activity records and ID sequencing
Separating Draft Target and delivery state from applicationStatus while preventing skipped candidates
Purpose
Activity needed a contract that could retain decisions that were not applied, separating publication-candidate state from result application without automatically removing non-applied work from the sequence.
Implementation
Schema version 4 adds applied and not-applied, with bilingual non-applied titles, list badges, detail notices, and confirmation evidence. Application status is not inferred from Draft Target, pull-request presence, or merge state, while Skill and tests make the inspector reject unmapped earlier candidates and ID gaps.
- mappingがなければ、`sequenceCheck`を確認する。対象より前の公開候補が未mappingのままなら、後続Activityへ新しいIDを割り当てず、先行候補の扱いを先に確定する。
- 通常の追記では既存最大値の次の`activity-NNNN`を使用する。CEOが過去の割り当て誤りを明示的に訂正する場合だけ、影響する全記事、source map、registry、test、URL identityへの影響を一つのbreaking migrationとして揃える。自動で繰り下げない。Rendering diagram…
What was confirmed
Verification results
Targeted tests and diff checks passed for schema, UI, source maps, public boundaries, and ID sequencing.
At the cutoff, the new contract and an earlier article correction were applied, while later bulk drafts, full verification, and completion decisions remained unfinished.
Basis for completion
This change unit was complete when the non-applied schema and UI, independent application decisions, and gap-prevention checks were implemented and verified.