FACTUAL ACTIVITY RECORD · An activity record based on work that took place
Establishing the central activity ledger
Linking multiple work records through one nine-column format
Purpose
A common record was needed to trace delivery paths and decision evidence across commits, pull requests, issues, and Codex tasks from multiple repositories.
Implementation
The central ledger uses nine columns for ID, publication-candidate state, date, repository, commit, subject, pull request, issue, and Codex task. It distinguishes the actively maintained source from frozen history and defines when completion work must add corresponding evidence.
- このrepositoryのPRをmergeする場合は、Issueをcloseするか途中段階としてopenのまま維持するかを問わず、同じPRへactive historyの更新を含めてください。
- 台帳には、`ID`、`Draft Target`、`Date`、`Repository`、`Commit`、`Subject`、`Pull Request`、`Issue`、`Codex Task`を、確認できる一次情報に基づいて記録します。`Draft Target`は活動記録への公開ターゲットとして検討するか否かのフラグとし、値は`◎`、`◯`、`✗`、`保留`に限定して、否定には`✗`を使用してください。更新前に対象のRepository、full Commit SHA、PR URL、Issueの完全URLまたは`owner/repo#番号`を検索し、確定した行は`Repository + full Commit SHA`を識別子として、同じcommitの行を重複して追加せず、既存行の`未特定`、`候補`、不足している関連情報を更新してください。同じIssueに複数のPRまたはcommitが関係する場合はそれぞれの履歴を残し、Issue IDだけを基準に別のPRまたはcommitの行を上書き、統合、削除してはなりません。Rendering diagram…
What was confirmed
Verification results
All 263 rows were confirmed to have nine columns, and full verification plus diff checks passed.
Documentation and operating rules were applied without changing application runtime, database, or infrastructure.
Basis for completion
The work was complete when heterogeneous evidence was linked into unique rows and the central ledger could be continued under one verified format.