Tell the true story: README rewrite, orchestration graphic, glamour shots, steer-line context % (round L) #36

Merged
ClaudiuSchuster merged 1 commit from oss-oo/observatory-story-tory20260925 into main 2026-09-25 09:44:18 +00:00
Owner

What

The README (and the repo story) now tell what the product actually is: an interactive cockpit for ALL ZCode sessions — steering with queue semantics + optimistic echo, question answering, native archive/pin/hide, favorites dock, lineage colors, hydration prediction, bell visibility, and honest limits.

  • Orchestration graphic (Mermaid): brains → pinkies → bells + MQTT (broker, zcode/session/<id>/turn-* topics, listener, external consumers) → cockpit → release-return; every arrow a real mechanism.
  • Glamour shots embedded: dashboard (lineage colors, hints, dock), steer console, question modal — fixture data, no secrets; sources follow the established screenshot discipline.
  • Social preview refreshed (tagline + chips; reproducible via make social-preview, ≤ 1 MiB).

Steer target line: context % + cache hit rate (addendum)

⟶ steer target: … · GLM-5.3 · max · 64% ctx · cache ~96% · project · idle — mirroring the desktop client math: latest model request tokens.total (step-finish parts, input includes cached tokens) over the provider-config modelConfigRules context window (live file, embedded z.ai snapshot fallback, ZDO_PROVIDER_CONFIG override); cache rate = Σ cache.read ÷ Σ input across the session's requests. turn_usage sums deliberately not used (they overstate multi-request turns). Formula documented in the README; tooltips carry raw numbers.

Verified live: fixture DB (64% ctx / 96% cache) AND the real session DB (70% ctx / 89% cache over 473 requests) — read-only.

Owner UI findings (all DOM-geometry verified against a fixture DB)

  1. Modal title clipped at viewport top — .mpanel max-height now resolves against the wrap's content box, so the dock's bottom padding is honored; title fully inside at 1080p AND a real 620 px-high window, content area preserved.
  2. Vertical send button word order — writing-mode: vertical-lr (line boxes stack left→right): 'Send to' LEFT column, 'session' RIGHT (was reversed).
  3. Send button row-span — the steering console is a CSS grid; the send strip spans the prompt AND the status line row (button bottom == status bottom), status text keeps its own line.

Gates

  • Super-Linter (pinned slim v8.7.0, local podman): MARKDOWN + PYTHON_PYLINT + PYTHON_RUFF ✅
  • python3 -m py_compile + --help boot ✅ (CI runs the same)
  • Screenshot evidence: /tmp/pinky-story-evidence/ (dashboard, steer console, question modal, send-strip crop)
## What The README (and the repo story) now tell what the product actually is: an **interactive cockpit for ALL ZCode sessions** — steering with queue semantics + optimistic echo, question answering, native archive/pin/hide, favorites dock, lineage colors, hydration prediction, bell visibility, and honest limits. - **Orchestration graphic** (Mermaid): brains → pinkies → bells + MQTT (broker, `zcode/session/<id>/turn-*` topics, listener, external consumers) → cockpit → release-return; every arrow a real mechanism. - **Glamour shots** embedded: dashboard (lineage colors, hints, dock), steer console, question modal — fixture data, no secrets; sources follow the established screenshot discipline. - **Social preview** refreshed (tagline + chips; reproducible via `make social-preview`, ≤ 1 MiB). ## Steer target line: context % + cache hit rate (addendum) `⟶ steer target: … · GLM-5.3 · max · 64% ctx · cache ~96% · project · idle` — mirroring the desktop client math: latest model request `tokens.total` (step-finish parts, input includes cached tokens) over the provider-config `modelConfigRules` context window (live file, embedded z.ai snapshot fallback, `ZDO_PROVIDER_CONFIG` override); cache rate = Σ cache.read ÷ Σ input across the session's requests. `turn_usage` sums deliberately not used (they overstate multi-request turns). Formula documented in the README; tooltips carry raw numbers. Verified live: fixture DB (64% ctx / 96% cache) AND the real session DB (70% ctx / 89% cache over 473 requests) — read-only. ## Owner UI findings (all DOM-geometry verified against a fixture DB) 1. **Modal title clipped at viewport top** — `.mpanel` max-height now resolves against the wrap's content box, so the dock's bottom padding is honored; title fully inside at 1080p AND a real 620 px-high window, content area preserved. 2. **Vertical send button word order** — `writing-mode: vertical-lr` (line boxes stack left→right): 'Send to' LEFT column, 'session' RIGHT (was reversed). 3. **Send button row-span** — the steering console is a CSS grid; the send strip spans the prompt AND the status line row (button bottom == status bottom), status text keeps its own line. ## Gates - Super-Linter (pinned slim v8.7.0, local podman): MARKDOWN + PYTHON_PYLINT + PYTHON_RUFF ✅ - `python3 -m py_compile` + `--help` boot ✅ (CI runs the same) - Screenshot evidence: /tmp/pinky-story-evidence/ (dashboard, steer console, question modal, send-strip crop)
The README and repo story now match the product: an interactive cockpit
for ALL ZCode sessions (not a read-only dispatcher dashboard) — steering
with queue semantics and optimistic echo, question answering, native
archive, pin/hide/favorites dock, lineage colors, hydration prediction,
and honest limits. New Mermaid orchestration graphic (brains → pinkies →
bells + MQTT → cockpit → release-return) with every arrow a real
mechanism; three fixture-data screenshots embedded (dashboard, steer
console, question modal); social preview tagline/chips refreshed.

Steer target line gains context-window utilization and session-average
cache hit rate right after the reasoning level ('64% ctx · cache ~96%'),
mirroring the desktop client's own math: latest model request's
tokens.total (step-finish parts; input includes cached tokens) over the
provider-config context window (modelConfigRules cascade, live file with
an embedded z.ai snapshot fallback, ZDO_PROVIDER_CONFIG override), and
cache.read's share of summed input. turn_usage per-turn sums are
deliberately not used — they overstate multi-request turns. Formula
documented in the README.

Owner UI findings fixed, each verified against a fixture DB by DOM
geometry: the response modal's title no longer clips above the viewport
when the dock reserves bottom padding (max-height now resolves against
the wrap's content box); the vertical send button's columns read
left→right ('Send to' left, 'session' right — writing-mode vertical-lr);
and the send strip row-spans the prompt AND the status line via a CSS
grid on the steering console.
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
OSS-Singularity/zcode-dispatch-observatory!36
No description provided.