diff --git a/status/current-state.html b/status/current-state.html index 079cec2..e885ac6 100644 --- a/status/current-state.html +++ b/status/current-state.html @@ -125,6 +125,9 @@ header.top { padding: clamp(40px, 7vw, 76px) 0 34px; } /* flex, not grid: flex items grow to fill the last row, so a count that does not divide by the column count never leaves an empty tinted cell */ +.revs { border-collapse: collapse; margin-top: 16px; font-size: .92rem; } +.revs td { padding: 4px 14px 4px 0; vertical-align: top; border: 0; color: var(--muted); } +.revs td.mono { white-space: nowrap; color: var(--ink); font-weight: 600; } .kpis { display: flex; flex-wrap: wrap; gap: 1px; background: var(--hair); border: 1px solid var(--hair); border-radius: 4px; overflow: hidden; margin-top: 30px; } @@ -306,22 +309,24 @@ footer { margin-top: 72px; padding-top: 22px; border-top: 1px solid var(--hair); Plant Operations Assistant · Proof of Concept

Where the build actually stands

-

Most of this page was read off the running host on 28 August 2026 - — containers listed, endpoints probed, the database queried, and two questions put through the - live assistant end to end. Nothing here is taken from the plan. Where this page and the build - documents disagree, this page is the later reading.

-

Updated 31 August. The three open findings are - closed. They turned out to be one defect wearing three faces, and it was settled not by choosing - between the two disagreeing sides but by going to the SCADA configuration and finding that - both were describing something the historian does not use. The section that used to list - them now records what was actually wrong.

+

Read off the running host, not taken from the plan. Where this page and the + build documents disagree, this page is the later reading.

+ + + + + +
1 SepSeed re-keyed onto CI Server item names; live database + migrated, API rebuilt, answer re-checked. Trace log shows the full question set was run + earlier the same day, before the re-key.
31 AugThe three open findings closed — one defect wearing + three faces.
28 AugPage first compiled from the host: containers listed, + endpoints probed, database queried, live answers timed.
28containers on lin001
7 of them ours
-
7phases done
of nine
-
1request still outstanding
the historian login
-
0open findings
all three closed 31 Aug
-
78exam questions
never yet run as a gate
+
7steps done
of nine
+
4open items
1 of them blocking
+
78exam questions
last run 1 Sep, before the re-key
3.96slive answer, 28 Aug
contract-valid
@@ -342,7 +347,7 @@ footer { margin-top: 72px; padding-top: 22px; border-top: 1px solid var(--hair);
- WRPS plant assistant topology as built, 28 August 2026 + WRPS plant assistant topology as built, 1 September 2026 The SCADA server cicore1 reaches the assistant on the Docker host lin001 without signing in. The SQL host imh, which would supply real plant history, does not yet exist. lin001 runs seven containers built by this project alongside twenty-one that @@ -499,7 +504,7 @@ footer { margin-top: 72px; padding-top: 22px; border-top: 1px solid var(--hair);
02

What is done, and what is not

-

Nine phases, each ending in a gate that must pass before the next begins — +

Nine steps, each ending in a check that must pass before the next begins — so that when an answer comes out wrong there is one place to look, not four. Two gates have never been run, and one phase was built out of order.

@@ -512,7 +517,7 @@ footer { margin-top: 72px; padding-top: 22px; border-top: 1px solid var(--hair);
Documents, equipment names, tag definitions and the stand-in plant history. Five database roles with the split that matters: the answer path can read and nothing else, and only the ingestion role can write documents.
-
  • healthy 8 days
  • 92 document chunks
  • 8 equipment, 65 tags, all aliased
  • 49 historian items mapped
  • no host port
  • agent_ro cannot INSERT
+
  • 92 document chunks
  • 8 equipment, 65 tags, all aliased
  • keyed on CI Server items since 1 Sep
  • 49 historian items mapped
  • no host port
  • agent_ro cannot INSERT
@@ -599,12 +604,17 @@ footer { margin-top: 72px; padding-top: 22px; border-top: 1px solid var(--hair);
08

The exam

- Never run + Run 1 Sep — but before the re-key, and no scorecard kept
Engineer-reviewable questions, every data-dependent one with a pinned time - window. Nothing blocks running it — the model account arrived on 27 August — and it - has never been run as a gate. No scorecard exists. Two cases fail by design until the historian - lands.
-
  • 28 historical
  • 18 procedural
  • 14 advisory
  • 13 reference
  • 2 unclear
  • pass mark: 85% / 95% / zero breaches
+ window. The whole set was put through the live assistant on 1 September, 01:01–02:08 + UTC — every question, found in the assistant’s own trace log. Two things are wrong + with it as a gate: it ran nine hours before the seed was re-keyed, so it scored a system + that no longer exists; and no scorecard was kept, so there is no result to read. A run + against the current build is planned. Earlier, the 67-question version passed for weeks against + the stand-in model — which is why it caught none of the eight failures that appeared + minutes after the first real model call on 27 August. Two cases fail by design until the + historian lands.
+
  • 30 historical
  • 18 procedural
  • 14 advisory
  • 14 reference
  • 2 unclear
  • pass mark: 85% / 95% / zero breaches
@@ -643,19 +653,19 @@ footer { margin-top: 72px; padding-top: 22px; border-top: 1px solid var(--hair); cube lin001 · ai-internal + proxy cube.yokogawa.tech → 302 - Healthy 7 h and answering the data lane — but off stand-in tables, not the historian. + Healthy and answering the data lane — but off stand-in tables, not the historian. Restarted 1 Sep to pick up the item-keyed models. cubestore lin001 · ai-internal
/datadisk/cubestore nothing — no host port - Up 7 days. A hard dependency of cube, not an optimisation — cube will not start without it. Absent from the original architecture deck. + A hard dependency of cube, not an optimisation — cube will not start without it. Absent from the original architecture deck. ai-api lin001 · ai-internal + proxy
0600 env file api.yokogawa.tech → 302
and /ask under ai.… - Healthy 2 h. A procedural question answered end to end in 3.96 s: correct document identity, prerequisites quoted, steps withheld, scope banner present. + Rebuilt 1 Sep — it now refuses a retired SCADA name outright instead of finding nothing. A procedural question answered end to end in 3.96 s: correct document identity, prerequisites quoted, steps withheld, scope banner present. ai-web lin001 · proxy · static build ai.yokogawa.tech → 403 - Up 26 h. The 403 is the deny arm working correctly. The allow arm is now proven from the console itself — the access log shows 10.0.0.21 since 28 August. + The 403 is the deny arm working correctly. The allow arm is now proven from the console itself — the access log shows 10.0.0.21 since 28 August. langfuse + lf-db lin001 · ai-internal + proxy
/datadisk/langfuse lf.yokogawa.tech → 302 @@ -671,7 +681,7 @@ footer { margin-top: 72px; padding-top: 22px; border-top: 1px solid var(--hair); openplc-runtime lin001 · host ports 502, 8443 Modbus TCP, bound 10.0.0.17 - Up 8 days. Live control for this demo. The one deliberate exception to the no-published-ports rule, contained by that binding plus firewall scope. Never restarted as a side effect of AI work. + Live control for this demo. The one deliberate exception to the no-published-ports rule, contained by that binding plus firewall scope. Never restarted as a side effect of AI work. svc_agent_ro yau-sls-poc-imh · TDS 1433 not reachable @@ -814,7 +824,22 @@ footer { margin-top: 72px; padding-top: 22px; border-top: 1px solid var(--hair);
-
05

Every component, and what its job is

+
05

What is open, and on whom

+

One thing is still needed from other people. Three more are ours, and none of them stops + anything today.

+ + + + + + + +
OpenWhoseBlocking?
A read-only login to the real plant historian, and its schemaOutside this projectYes — every number is a stand-in until it lands
The OpenPLC editor is not installed anywhere, so the control logic has no reviewable + source outside the containerOursNo
The assistant refuses to recommend a setpoint. That is deliberate, and expected to be + revisited as a featureOurs — a decision, not a defectNo
Faults in the deployment scripts and database migrations have nowhere to be recorded as + a test, so a fixed one can come backOursNo
+ +
06

Every component, and what its job is

Twenty-eight containers on one shared host. Seven are ours; twenty-one were already here and serve other demos. This is the list the architecture deck never carried.

@@ -1009,7 +1034,7 @@ footer { margin-top: 72px; padding-top: 22px; border-top: 1px solid var(--hair);
-
06

Deliberate shortcuts, all reversible

+
07

Deliberate shortcuts, all reversible

Documented rather than hidden, and none of them to be shipped. Production closes them in this order: network separation, then secrets, then database guardrails, then document control integration, then resilience.