Keyboard-Workflow on 1K Scanner — Official Blog

Filters and sorting are not search engines: they are candidate-narrowing tools

Mon, 23 Feb 2026 22:00:00 +0900

1k_scanner is not a document scanner. It is a Rust+egui based multi-market, multi-timeframe trading scanning app.

The core idea is simple:

Instead of searching for the right entry, use scanning to narrow your attention to a small set of candidates that are worth a deeper review.

So this guide is about using filter/sorting signals (including consensus cues) as a candidate narrowing routine.

1) Why narrowing comes first

When you first open 1k_scanner, it looks like a lot of charts at once. That is not noise; it is the starting point for narrowing down.

If you open charts one by one, the question becomes: “Which chart should I check next?”

With a scanning workflow, the better question is: “Which symbols should I review thoroughly for the next 2–3 minutes?”

In practice, the consensus hotlist/cues and your routine act as the “filters/sorting” that answer that question.

2) One-minute reset: lock the grid mental model

The grid is built as:

Rows = timeframes
Columns = symbols

That means one column gives a multi-timeframe chain for the same symbol.

Now set the two core view modes:

Ctrl/Cmd + 7: dense grid
Ctrl/Cmd + 8: expanded grid

A practical loop:

Use dense grid (Ctrl/Cmd+7) for a broad scan.
Use expanded grid (Ctrl/Cmd+8) to reduce candidates for deeper checks.
Switch back if you need broader context again.

That is the essence of filtering: not seeing more, but deciding what to stop seeing.

3) 5-minute interpretation of EMA/NRZ: user-level use only

When many users first see EMA and NRZ, they may think these are “what to buy” signals. Use them as context checks instead.

EMA (persistence): quick read of how durable the larger directional context looks.
NRZ: quick read of whether pullback handling still feels structurally supported.

In practice, ask only two questions:

Is this candidate aligned with the larger flow?
Does the post-pullback structure look like it can hold, or is it already fracturing?

This keeps you from overfitting those two panes into instant actions.

4) Consensus signal: what the directional frame cue actually means

Consensus is not an execution signal.

Interpret it this way in daily use:

If multiple signs line up, you get a directional frame cue (long/short emphasis).
If signals are mixed, neutral, or weak, you get low-emphasis behavior.

Even with a strong directional cue:

It does not mean “enter now.”
It means “this is the next set to validate.”

Even with neutral/mixed cues:

It does not mean “take the opposite trade immediately.”
It may simply mean “watch less aggressively or pause.”

Consensus is, in short, a way to allocate attention and review time.

5) Focus happens through Space

After you narrow to a few candidates, move from scan to focused validation.

Space: toggle single chart mode.
Keep moving within row/column so one symbol’s timeframes stay grouped.

Prefer this sequence over immediate action:

Narrow in filter stage
Validate in single-chart stage
Return to list and repeat

This loop is where consistency comes from.

6) Check-note routine: `V` to save, `N` to review

Most misses are not because the right symbol was absent. They happen because the observation rhythm was not captured.

Use this compact loop:

V: add/toggle the current chart in check-note.
N: open the CheckNote section and review.

A simple 3-line format is enough:

Why this symbol became a candidate.
What was seen at the EMA/NRZ level.
Next action (observe more / execute setup / defer).

This removes the “I forgot the reason” problem next session.

7) Template is your operation repeatability layer

If you skip this, your routine collapses after the first good session.

Create template
- Set Grid Size, Timeframes per row, Exchange, then run Generate Template (by size).
Save layout
- F12 stores the current workspace layout.
Load layout
- Ctrl/Cmd + L opens the load dialog next time.

At first, use two templates:

Scan template: wide coverage for candidate collection.
Focus template: fewer charts for in-depth checking.

That is your filtering pipeline in practice.

8) Practical 10-minute routine

0:00–1:30 Verify tab and grid state after launch.
1:30–3:30 Scan broadly in dense mode (Ctrl/Cmd+7).
3:30–5:30 Use EMA/NRZ as context checks to prioritize candidates.
5:30–7:00 Narrow candidates using the directional consensus cue.
7:00–9:00 Focus with Space on 2–3 candidates and mark V.
9:00–10:00 Review with N, then save/load layout (F12, Ctrl/Cmd+L).

When you treat filtering this way, 1k_scanner becomes less about finding the perfect chart and more about protecting your decision rhythm.

Use it not to chase signals, but to keep your observation consistent.

Drop the mouse: keyboard workflow is how you actually scan 1,080 charts

Fri, 20 Feb 2026 21:50:00 +0900

In trading, the first question is rarely “which chart to open next.” It is usually: what should I evaluate first?

In 1k_scanner, keyboard-first workflows reduce context switching and keep your observation order stable. This post is a practical 10-minute routine you can use immediately in a 1,080-chart environment.

1) Start routine: first 30 seconds after launch

Use this order whenever you launch the app.

Confirm current tab and grid state
- Check whether the loaded workspace is the one you want to work with.
- If not, return to your scanning view first.
Begin with a wide view for candidate selection
- Ctrl/Cmd + 7: dense grid (many symbols at once)
- Ctrl/Cmd + 8: expanded grid (focus on fewer symbols)
Lock the grid mental model
- The grid is built as rows = timeframes, columns = symbols.
- A single column gives a multi-timeframe sequence for one symbol, so comparison is faster and less fragmented.

Completing this pre-check keeps the process from turning into random clicking and turns it into a structured sequence of questions.

2) First pass scanning: treat EMA/NRZ as context checks

How to read EMA/NRZ without overfitting

Use EMA (persistence view) as a clue for how durable the current flow looks.
Use NRZ as a clue for whether pullback handling is coherent enough to stay in the setup.

At this stage, use only two operational questions:

Is this candidate aligned with the larger directional context?
Is the pullback showing structure that can hold, or is it already losing coherence?

Read consensus signals as filter signals, not entry signals

For many users, this is the most important shift.

When multiple observations point in the same direction, the symbol receives a directional frame cue (long/short color and stronger emphasis).
When directional input is mixed, neutral, or weak, the symbol is less emphasized (often no strong frame cue).

The key is not “consensus = guaranteed entry.” The key is “consensus helps me narrow which names deserve close review.”

So do not lock entry decisions there. Use consensus as a candidate filtering step first.

3) Focus routine: scan → expand → decode

After candidates are narrowed:

Move the focus with arrow keys or W/A/S/D.
Use Space to toggle single-chart expansion.
Refine checks within that symbol across nearby time windows.
Switch between Ctrl/Cmd + 7 and Ctrl/Cmd + 8 to balance breadth and focus.

In expanded mode, do not jump to action immediately. First lock the larger context in the same column, then confirm pullback/structure behavior in lower frames.

4) Check-note routine: V to add, N to review

A 1,080-chart workflow helps you see more, but memory can still fragment. Use this note loop to prevent that.

V: add or toggle current chart in Check Note.
N: open the CheckNote section and review.

A simple note template:

Why this symbol became a candidate (one line)
Why it is rejected or delayed (one line)
Next check plan (one line)

This is lightweight, but it preserves your decision history and avoids losing rationale between sessions.

5) Template workflow: keep scanning reproducible

Even the cleanest keyboard rhythm is unstable without repeatable templates.

Generate template: set Grid Size, Timeframes per row, Exchange, then run Generate Template (by size)
Save layout: persist the current workspace view with F12
Load layout: reopen a saved layout with Ctrl/Cmd + L

Two templates are enough to start:

Scanning template: broad symbol coverage for fast narrowing
Focus template: fewer symbols with larger spacing for detailed review

6) 10-minute repeatable checklist

First 2 minutes

Launch app and confirm workspace
Open dense grid with Ctrl/Cmd+7
Trim to ~8–12 candidates from consensus frame cues

Next 4 minutes

Read each candidate by symbol column (row-by-timeframe, column-by-symbol)
Check EMA/NRZ for persistence + pullback coherence
Keep consensus cues at “priority” level only, not entry-level yet

Next 3 minutes

Expand each candidate with Space
Add notes with V
Exclude weak candidates and log the reason

Final 1 minute

Open N and close the loop on notes
Save/load your routine layout for next session

1k_scanner is not a document scanner. It is a Rust+egui based multi-market, multi-timeframe trading scanning app. It is designed so you can reduce how much you have to search manually and focus your attention on the candidates that are worth your next decision cycle.