Skip to content

docs(vision): sync reasoning-window defaults after gate item 6 - #14

Merged
AlexSKuznetsov merged 2 commits into
mainfrom
docs/sync-reasoning-window-defaults
Aug 28, 2026
Merged

docs(vision): sync reasoning-window defaults after gate item 6#14
AlexSKuznetsov merged 2 commits into
mainfrom
docs/sync-reasoning-window-defaults

Conversation

@AlexSKuznetsov

Copy link
Copy Markdown
Collaborator

Item 6 (#13) widened the reasoning window and its coupled knobs, but two descriptions still carried the pre-item-6 values. This is a docs/fixture-only sync — no runtime behavior changes.

Changed

  • services/vision-worker/README.md — the service that owns these knobs:
    • Prose: "roughly six-second window" → twenty-second window, reworded to say why it's wide (a placement's before/after contrast, which a tight window hides).
    • Env table: REASON_WINDOW_SECONDS 6→20, REASON_MAX_FRAMES 4→8, EVENT_COOLDOWN_SECONDS 20→25.
  • apps/console/.../VisionPanel.test.tsx — mock fixture hardcoded 6 / 4 / 20. Unasserted, but aligned to 20 / 8 / 25 so it doesn't mislead. Test still passes.

Deliberately unchanged

  • Console UI renders these live from /v1/status, not constants — already correct, not stale.
  • .env.example doesn't set these knobs; architecture docs (00–19) describe concepts, not tunables; docs/spikes/* are frozen lab records.

🤖 Generated with Claude Code

AlexSKuznetsov and others added 2 commits August 27, 2026 18:41
Item 6 (PR #13) widened the reasoning window and its coupled knobs, but two
descriptions still carried the old values:

- vision-worker README: "roughly six-second window" and the env table's
  REASON_WINDOW_SECONDS=6 / REASON_MAX_FRAMES=4 / EVENT_COOLDOWN_SECONDS=20.
  Updated to 20 / 8 / 25 and reworded the window prose to state why it is wide
  (a placement's before/after contrast, which a tight window hides).
- console VisionPanel test fixture hardcoded window_seconds=6, max_frames=4,
  event_cooldown_seconds=20. These are unasserted mock values, but aligning them
  to 20 / 8 / 25 keeps the fixture honest. Test still passes.

The live Console UI is unaffected -- it renders these from /v1/status, not from
constants. No `.env.example` or architecture-doc changes were needed.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Point the hero "NVIDIA Spark Hackathon Seattle 2026 · Winner" badge at the
LinkedIn announcement post, and add a "Source on GitHub" link in the footer.
The badge keeps its pill styling as a link (no underline, accent-border hover).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@AlexSKuznetsov
AlexSKuznetsov merged commit 52eb2c8 into main Aug 28, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant