Define reviewed publications and record the field-sampling frame.
IR-WP-0007-T03 can now record a capture-linked publication separately from generated drafts. The field-outcome design is written, and credential, billing, and website-pull gates were rechecked and left waiting. Assistant: grok Assistant-Session: 01a106a5-fc07-78c2-b64f-8e04cea25daf
This commit is contained in:
parent
a25cc867dd
commit
6808aa3594
11 changed files with 296 additions and 7 deletions
|
|
@ -11,7 +11,7 @@ topic_slug: custodian
|
|||
origin: residual
|
||||
origin_ref: IR-WP-0004
|
||||
created: "2026-09-14"
|
||||
updated: "2026-10-03"
|
||||
updated: "2026-10-04"
|
||||
state_hub_workstream_id: "624750a5-d613-5e32-a656-595de03ef73c"
|
||||
---
|
||||
|
||||
|
|
@ -60,3 +60,8 @@ pinned `intelligence-radar-key-check` recipient; Radar requested secrets-engine
|
|||
`docs/evidence/2026-09-27-ir-wp-0005-t01-native-delivery.md`.
|
||||
|
||||
2026-10-03: human gate routed to hub decision 62aa95e4-3ccc-4867-8806-5e3db005b483 (D1: Attended OpenBao provisioning window: one session clears the pending credential lanes) by CUST-WP-0075; resolving that decision raises C-40 here.
|
||||
|
||||
Rechecked 2026-10-04: decision `62aa95e4-3ccc-4867-8806-5e3db005b483` is still
|
||||
`open` (`decided_at` null, last hub update 2026-10-03). The radar inbox has no
|
||||
new secrets-engine message. No delivery check was run and no credential was
|
||||
read. Stays wait.
|
||||
|
|
|
|||
|
|
@ -11,7 +11,7 @@ topic_slug: custodian
|
|||
origin: residual
|
||||
origin_ref: IR-WP-0004
|
||||
created: "2026-09-14"
|
||||
updated: "2026-09-14"
|
||||
updated: "2026-10-04"
|
||||
state_hub_workstream_id: "b877f5e2-0c0e-5bca-9082-873eab857ada"
|
||||
---
|
||||
|
||||
|
|
@ -70,3 +70,8 @@ Blocked: the mechanism is ready (T01/T02 done), but no authoritative provider bi
|
|||
exists for the pending run_id `29a46a1d6c2d9ef6cfce8de6efef75cddcfecee346c1b4babf57119f1a241d71`
|
||||
yet. Applying `reconcile` here without that evidence would be exactly the fabrication this
|
||||
workplan forbids. Waits on external evidence (likely via the IR-WP-0005 admitted read-only path).
|
||||
|
||||
Rechecked 2026-10-04: the ledger still has the one `reserved` event for
|
||||
`29a46a1d6c2d9ef6cfce8de6efef75cddcfecee346c1b4babf57119f1a241d71` and no
|
||||
provider billing artifact. IR-WP-0005-T02 is still wait, so the read-only path
|
||||
is still closed. `reconcile` was not called. Stays wait.
|
||||
|
|
|
|||
|
|
@ -11,7 +11,7 @@ topic_slug: custodian
|
|||
origin: residual
|
||||
origin_ref: IR-WP-0004
|
||||
created: "2026-09-14"
|
||||
updated: "2026-09-14"
|
||||
updated: "2026-10-04"
|
||||
state_hub_workstream_id: "e75cf5ae-3df2-507e-8fa3-8de687137623"
|
||||
---
|
||||
|
||||
|
|
@ -39,6 +39,12 @@ review (`docs/evidence/2026-09-14-ir-wp-0004-review.md`) and found to require a
|
|||
dedicated, sourced measurement campaign rather than a redo inside this session —
|
||||
inventing pinned versions without primary-source verification would violate P11.
|
||||
|
||||
Rechecked 2026-10-04: the instrument mismatch in
|
||||
`docs/evidence/2026-09-14-ir-wp-0004-review.md` is unchanged, and requester
|
||||
access is still absent because IR-WP-0005-T02 is waiting on open decision
|
||||
`62aa95e4-3ccc-4867-8806-5e3db005b483`. No benchmark versions were pinned and
|
||||
no Frontier/Efficient comparison was produced. Stays todo.
|
||||
|
||||
## Collect and assess representative field outcomes
|
||||
|
||||
```task
|
||||
|
|
@ -55,14 +61,20 @@ Residual IR-WP-0004-T02. Paid execution depends on BOTH IR-WP-0005 credential re
|
|||
Blocked, 2026-09-27: paid execution still needs IR-WP-0005-T02 (wait) and IR-WP-0006-T03
|
||||
(wait) both closed. The sampling-frame/verifier design portion this task allows to proceed
|
||||
earlier is nontrivial methodology work in its own right (real task origins, held-out sets,
|
||||
verifiers, failure taxonomy) and was not attempted in this session to avoid a rushed
|
||||
design under time pressure; it remains open, undecomposed, for a dedicated pass.
|
||||
verifiers, failure taxonomy) and was not attempted in the 2026-09-27 pass.
|
||||
|
||||
Design portion recorded 2026-10-04 in
|
||||
`docs/evidence/2026-10-04-ir-wp-0007-t02-sampling-frame.md`: origin,
|
||||
inclusion, exclusion, hold-out, dependence groups, and a failure taxonomy
|
||||
that includes verifier dependence (reward hacking and a checker that shares
|
||||
the generator's errors). No field tasks were frozen and no runs were made.
|
||||
Paid execution still waits. Status stays wait.
|
||||
|
||||
## Complete reviewed publication and operational disposition
|
||||
|
||||
```task
|
||||
id: IR-WP-0007-T03
|
||||
status: todo
|
||||
status: done
|
||||
priority: high
|
||||
state_hub_task_id: "314f79fd-d95a-5e02-b67d-67e35e4334ed"
|
||||
```
|
||||
|
|
@ -75,6 +87,14 @@ definition (claim-to-capture references, exclusions, revision identity, correcti
|
|||
distinct from a generated draft) is still open; it is a schema/format design decision
|
||||
better made deliberately than folded into this pass. Stays todo.
|
||||
|
||||
Done 2026-10-04: `python3 -m intelligence_radar publish` records a reviewed
|
||||
publication in `data/publications/` and renders `digests/reviewed/<revision>.md`.
|
||||
An included claim must name a capture already in the ledger. An excluded claim
|
||||
must name the reason. `supersedes` links a correction to an earlier revision.
|
||||
The scheduler does not write these files, and a generated draft is not accepted
|
||||
as the record. No publication was issued; nothing had been reviewed. The local
|
||||
timer decision remains ADR 0003.
|
||||
|
||||
## Compare decomposition with measured monolithic execution
|
||||
|
||||
```task
|
||||
|
|
|
|||
|
|
@ -71,3 +71,8 @@ path remains the brief inbox: an export saved there, including one saved from
|
|||
Grok's email delivery, is retained by T02. Pulling the websites themselves
|
||||
waits on a real export or an authorized account feed that does not guess
|
||||
private endpoints.
|
||||
|
||||
Rechecked 2026-10-04: the inbox has no new export. It still holds the empty
|
||||
3 October Grok file and the 27 September ChatGPT file whose archive name is
|
||||
already taken by different bytes. email-connect has no Intelligence Radar
|
||||
feed. No session was sent to chatgpt.com or grok.com. Stays wait.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue