coulomb/freedom-intelligence
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Correct the false Qwen3.8-27B claim in the 2026-09-23 brief.

Browse source 
The brief's lead delta asserted a candidate -> approved move that no file
records; the catalog is unchanged since a78187c. Appends an operator
correction so later briefs do not read it back as fact, and starts a
compatibility-executor defect log as the FI-WP-0005-T07 acceptance baseline.
Records activity-core's scope reply (029814b0) on T04.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 51320@bnt-lap001
Assistant-Session: 9d40b4c7-8e3c-42ee-b755-d658d4640d6c
This commit is contained in:
tegwick 2026-09-24 02:23:31 +02:00
parent 67064ec950
commit ee32b47123
3 changed files with 53 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

19
briefs/2026/09/2026-09-23.md
View file

@ -43,3 +43,22 @@ sources_checked:
- Operators should prioritize setting `HF_TOKEN` and pulling Llama-3.2-3B-Instruct into `models/` One Zone IA, as its collection is blocked by an HF gate.
- The decision on whether Qwen3.8-27B will replace Qwen3-8B as the default R instruct model needs to be made. This will inform the next collection priority.
- Continue monitoring Axis A and B for new releases, especially from Qwen, DeepSeek, and Meta, as per the allowlist.
---
## Operator correction (appended 2026-09-24)
The first headline delta is **false**. Qwen3.8-27B was not moved from
`candidate` to `approved`. `inventory/catalog/Qwen__Qwen3.8-27B__candidate.yaml`
has `status: candidate` with an empty `collection.approved_by`, unchanged
since `a78187c` (2026-09-13). No approval decision exists.
The catalog is the authority (`inventory/collection-policy.md`). This brief's
body is left as the executor wrote it; this note is appended so the claim is
not read back as fact by later briefs, which receive the previous brief as
context.
Recorded as a defect of the compatibility executor in
`docs/evidence/2026-09-23-brief-defects.md` (FI-WP-0005 acceptance baseline).
The remaining lab implications (HF gate on Llama-3.2-3B, the open Qwen3.8-27B
vs Qwen3-8B decision) restate `inventory/RESERVE-STATUS.md` correctly.

27
docs/evidence/2026-09-23-brief-defects.md Normal file
View file

@ -0,0 +1,27 @@
# Compatibility executor defect log
Baseline for the FI-WP-0005-T07 canary comparison: defects produced by the
current `rein-aharness fi-research-brief` path (single llm-connect call, no
network access, no primary sources). The canary must not reproduce these.
| Date | Defect | Class | Evidence |
| --- | --- | --- | --- |
| 2026-08-04…14 | DeepSeek-V4-Flash-0731 reported as a 12B dense model; once claimed as already collected | invented facts; false collection claim | Corrected in `inventory/catalog/deepseek-ai__DeepSeek-V4-Flash-0731__strategic.yaml` history (FI-WP-0004-T05) |
| 2026-09-23 | "Qwen3.8-27B has been moved from 'candidate' to 'approved'" | invented state change; contradicts the catalog | Catalog unchanged since `a78187c`; `approved_by` empty. Correction appended to `briefs/2026/09/2026-09-23.md` |
## Pattern
Both defects are assertions about **lab state** that the brief had in its own
context and still got wrong, not stale knowledge about the outside world. The
executor receives the catalog and the previous brief, then narrates a change
that no file records.
Consequences for the FI-WP-0005 acceptance run (T07):
1. Compare canary output against the catalog for every claim about collection
status, sizes and licenses. Any assertion of a state change must cite the
file and revision that made it.
2. Briefs with no external delta should say so, rather than manufacturing an
internal one. Both defect days had genuinely quiet outside channels.
3. A false claim propagates: the previous brief is context for the next one.
Corrections belong in the brief file, not only in the workplan.

7
workplans/FI-WP-0005-profiled-brief-execution.md
View file

@ -165,6 +165,13 @@ agreed grant v2 schema revision is recorded here.
**2026-09-22:** Proposal sent to activity-core (`8ee9a6ab`). Awaiting reply.
**2026-09-24:** activity-core replied (`029814b0`): both items are in scope.
Grant v2 extends the WP-0038 grant/close boundary and needs an ADR amendment
plus rein-aharness agreement; the generic resolver fits the read-only
context-resolver registry (ACT-ADR-007). No workplan opened yet — new workplans
there need the founder's go-ahead, which they are raising. **Blocker for T07:
the founder's go-ahead for the activity-core workplan.**
### T05 — glas-harness handoff: `harness.fi-research-brief@1.0.0`
```task