Correct two counts that disagreed with the files they describe
The exam: eval/testset.jsonl holds 78 cases (A10 H28 L8 N5 P10 R10 T5 U2). workflow-map.html called it a 75-question exam in the two places it states the current total. Corrected. The two sentences describing how the exam "grew from 67 questions to 75" are left alone - that step is historically correct: 67 plus the eight live-model failures is 75, and the Phase 5 findings H26, H27 and H31 took it to 78 afterwards. The env files: .env.example said TWO 0600 files under ~/ai/ and listed pg-ai.env and api.env, but its own line 105 refers to langfuse.env, and README.md, scripts/deploy.sh and compose/langfuse-compose.yml all use three. The header was simply wrong; langfuse.env is now named in it. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
parent
61ddce808f
commit
45034eb4d1
2 changed files with 6 additions and 5 deletions
|
|
@ -1,9 +1,10 @@
|
||||||
# =============================================================================
|
# =============================================================================
|
||||||
# .env.example — every key, no values. Committed deliberately.
|
# .env.example — every key, no values. Committed deliberately.
|
||||||
#
|
#
|
||||||
# On lin001 these live as TWO 0600 files under ~/ai/, never in Git:
|
# On lin001 these live as THREE 0600 files under ~/ai/, never in Git:
|
||||||
# ~/ai/pg-ai.env the POSTGRES_* / AGENT_DB_* block
|
# ~/ai/pg-ai.env the POSTGRES_* / AGENT_DB_* block
|
||||||
# ~/ai/api.env everything else
|
# ~/ai/langfuse.env the Langfuse SALT / NEXTAUTH_SECRET block (see below)
|
||||||
|
# ~/ai/api.env everything else
|
||||||
# Follow the ~/authelia/authelia.env precedent: chmod 0600, owned by azureuser.
|
# Follow the ~/authelia/authelia.env precedent: chmod 0600, owned by azureuser.
|
||||||
# =============================================================================
|
# =============================================================================
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -651,7 +651,7 @@ shows the control-room machine opening the page on 28 August, the day the rule w
|
||||||
three questions on 31 August, each answered.</td></tr>
|
three questions on 31 August, each answered.</td></tr>
|
||||||
|
|
||||||
<tr><td class="ph">8</td>
|
<tr><td class="ph">8</td>
|
||||||
<td><b>The exam</b> — 75 engineer-checked questions run end to end and scored</td>
|
<td><b>The exam</b> — 78 engineer-checked questions run end to end and scored</td>
|
||||||
<td><span class="badge b-blocked">Runnable, and never run</span></td>
|
<td><span class="badge b-blocked">Runnable, and never run</span></td>
|
||||||
<td><b>Nothing is blocking this and it has still not been done.</b> The model account arrived on 27
|
<td><b>Nothing is blocking this and it has still not been done.</b> The model account arrived on 27
|
||||||
August, so both AI steps can be scored; no scorecard has ever been produced. The set covers 28
|
August, so both AI steps can be scored; no scorecard has ever been produced. The set covers 28
|
||||||
|
|
@ -714,7 +714,7 @@ returns that document’s heading, purpose and prerequisites and withholds t
|
||||||
The rulebook already refused instruction language and still does; this removes the temptation
|
The rulebook already refused instruction language and still does; this removes the temptation
|
||||||
rather than relying on catching it.</li>
|
rather than relying on catching it.</li>
|
||||||
<li><b>What it still does not prove:</b> whether the labelling and wording are <em>good enough</em>.
|
<li><b>What it still does not prove:</b> whether the labelling and wording are <em>good enough</em>.
|
||||||
They work; they are not yet scored. The 75-question exam can now be run and has not been. And no
|
They work; they are not yet scored. The 78-question exam can now be run and has not been. And no
|
||||||
operator has yet sat at a control-room PC and got an answer — the one check that cannot be
|
operator has yet sat at a control-room PC and got an answer — the one check that cannot be
|
||||||
done from here.</li>
|
done from here.</li>
|
||||||
<li><b>Found today, and worth repeating:</b> the most obvious question at this station —
|
<li><b>Found today, and worth repeating:</b> the most obvious question at this station —
|
||||||
|
|
|
||||||
Loading…
Add table
Reference in a new issue