Compare commits

..

No commits in common. "aa60c033b37d3eb53fc8f8632de838e6508f1377" and "bf39793de18cca15ee8fcea2f9b4257e413a4af4" have entirely different histories.

2 changed files with 2 additions and 29 deletions

View file

@ -1,19 +0,0 @@
# Intake records
## RMGR-IN-0001 — Validate assistant provenance on a natural multi-session window
```yaml
id: RMGR-IN-0001
kind: intake
title: Validate assistant provenance on a natural multi-session window
status: open
origin: residual
origin_ref: RMGR-WP-0009
priority: low
owner: repo-manager
description: When two coding-assistant sessions naturally commit to one repository,
run rmgr assistant-provenance report and retain the non-secret interleaving evidence.
Do not manufacture or infer a collision.
created: '2026-08-21T20:09:23.942286+00:00'
updated: '2026-08-21T20:09:23.942286+00:00'
```

View file

@ -4,7 +4,7 @@ type: workplan
title: "Coding-assistant commit provenance trailers"
domain: infotech
repo: repo-manager
status: finished
status: active
owner: codex
topic_slug: infotech
created: "2026-08-21"
@ -284,13 +284,5 @@ misclassify the cutover task as incomplete.
- [x] Hook live via `core.hooksPath`; never blocks, idempotent, silent for humans
- [x] Claude, Codex, and Grok each emit trailers, or are recorded as unable with a reason
- [x] `git log` alone answers "which assistant, which model, which session"
- [x] Natural overlapping-session proof handed off as residual `RMGR-IN-0001`
- [ ] Overlapping-session report runs against at least one real collision window
- [x] Cutover commit recorded; pre-cutover history reported as unknown, not inferred
## Closure
Finished 2026-08-21. The contract, global hook, three assistant integrations,
report, and honest cutover boundary are live. The non-deterministic operational
proof that requires two future sessions is preserved as file-backed intake
`RMGR-IN-0001` (`origin: residual`, `origin_ref: RMGR-WP-0009`) rather than
keeping an otherwise complete workplan active.