Reconcile FI workplan closure and external blockers
Assistant: codex Assistant-Model: gpt-6-astra Assistant-Session: 01a0e382-1bdd-7433-8e87-2be42228a158
This commit is contained in:
parent
d3def564ff
commit
e8e79db632
3 changed files with 42 additions and 12 deletions
|
|
@ -4,13 +4,13 @@ type: workplan
|
|||
title: "Move the daily brief to a profiled, granted execution on activity-core infrastructure"
|
||||
domain: agents
|
||||
repo: freedom-intelligence
|
||||
status: active
|
||||
status: blocked
|
||||
flavor: implementation
|
||||
owner: claude
|
||||
topic_slug: freedom-intelligence
|
||||
priority: high
|
||||
created: "2026-09-22"
|
||||
updated: "2026-09-22"
|
||||
updated: "2026-09-27"
|
||||
depends_on:
|
||||
- FI-WP-0004
|
||||
related:
|
||||
|
|
@ -142,7 +142,7 @@ arena.ai). openai.com and x.ai return 403 to plain clients, which is noted.
|
|||
|
||||
```task
|
||||
id: FI-WP-0005-T04
|
||||
status: progress
|
||||
status: wait
|
||||
priority: high
|
||||
state_hub_task_id: "d679352f-8b0d-5ca5-9e42-4173ed87f48a"
|
||||
```
|
||||
|
|
@ -176,7 +176,7 @@ the founder's go-ahead for the activity-core workplan.**
|
|||
|
||||
```task
|
||||
id: FI-WP-0005-T05
|
||||
status: progress
|
||||
status: wait
|
||||
priority: high
|
||||
state_hub_task_id: "e1d0bacd-b93d-50d5-b07d-e950e96443dc"
|
||||
```
|
||||
|
|
@ -232,7 +232,7 @@ and the post-cutover rollback.
|
|||
|
||||
```task
|
||||
id: FI-WP-0005-T07
|
||||
status: todo
|
||||
status: wait
|
||||
priority: high
|
||||
state_hub_task_id: "fd22b96d-39f0-53fd-9cdf-7bd29e758c54"
|
||||
```
|
||||
|
|
@ -251,7 +251,7 @@ recorded in `docs/evidence/`.
|
|||
|
||||
```task
|
||||
id: FI-WP-0005-T08
|
||||
status: todo
|
||||
status: wait
|
||||
priority: high
|
||||
state_hub_task_id: "3bd365ad-7e9c-54cc-ad2b-e1cbbf525636"
|
||||
```
|
||||
|
|
@ -267,6 +267,32 @@ grant schema revision, and canary and rollback evidence.
|
|||
profiled path, and rein confirms that FI no longer needs
|
||||
`AGENT_HARNESS_LEGACY_APPROACHES_UNTIL`. Target: before 2026-12-01.
|
||||
|
||||
## Closure review — 2026-09-27
|
||||
|
||||
T01–T03 and T06 are complete. None of the remaining tasks can meet its
|
||||
acceptance criteria in this repository alone. The plan is `blocked`; T04,
|
||||
T05, T07 and T08 are `wait` until the following evidence arrives. No new
|
||||
tasks or workplans were opened during this review.
|
||||
|
||||
| Task | Remaining blocker / evidence needed to resume |
|
||||
| --- | --- |
|
||||
| T04 | Activity-core workplan acknowledgement and agreed grant v2 schema revision. The latest FI inbox reply is still `029814b0`; it accepts scope but supplies neither. Activity-core `4c74f81` still admits only grant version `1` with `publish: false` in `src/activity_core/repository_grant.py`. |
|
||||
| T05 | Pinned `harness.fi-research-brief@1.0.0` with positive sandbox readiness and the host-install clarification. No FI profile or reply is present in the inspected Glas catalog/docs or FI inbox. `GLAS-WP-0012-T02` and `SAND-WP-0015-T04` remain `wait` in blocked owner plans (Glas `25cc488`, sand-boxer `505e82d`). |
|
||||
| T07 | T04 and T05 must deliver the actual grant, resolver and runnable profile before the disabled canary can be defined and exercised. A speculative definition cannot establish published, reconciled canary evidence. |
|
||||
| T08 | Successful T07, exercised rollback, five consecutive weekday profiled runs and rein's compatibility-retirement confirmation. Existing compatibility briefs do not satisfy this acceptance criterion. |
|
||||
|
||||
The owner declarations remain proposed and the existing daily definition remains
|
||||
on the compatibility path. FI-WP-0001–0004 are already closed; their explicitly
|
||||
deferred reserve and infrastructure handoffs do not establish completion of
|
||||
the profiled migration. README navigation now reflects these workplan states.
|
||||
|
||||
Validation: all 35 existing unit tests pass with
|
||||
`scripts/requirements-collect.txt` installed. The live durability audit
|
||||
(`--require-hub --allow-reconciled --require-date 2026-09-25`) passes against
|
||||
origin `26a3ce4`, including 11 valid published events. The five previously
|
||||
reconciled September 7–11 gaps remain acknowledged missing days, not successful
|
||||
briefs. State Hub reconciliation updated this plan and its four waiting tasks.
|
||||
|
||||
## Incident found during T06 (2026-09-22)
|
||||
|
||||
Briefs for 2026-09-15 to 2026-09-22 were stranded on railiance01 because
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue