Edge Watch¶
Menu Location: Kiva Tools > Edge Watch
Last Updated: 2026-10-14
Overview¶
Edge Watch is a weekly KLAI scan for ecommerce, SEO, and web-platform best practices worth adopting. It answers a different question than Feature Ideas: Feature Ideas asks what you should build, Edge Watch asks what the search, platform, deliverability, and checkout world has changed and you should start doing. A new Google Search capability, a newly required email-sender rule, a newly recommended structured-data type, or a proven checkout-UX change all land here, even when no competitor ships them as a product feature.
Items are ranked by likely business impact, and anything already surfaced in an earlier week is not presented as new again.
The page is available on the Kiva Logic master site. On other stores it redirects away.
Primary Functions:
- Automatic weekly scan, plus a manual Force Run Now
- Each item tagged with the area it came from and a link to the source
- KLAI's own guess at whether you already do it, so obvious items can be skipped fast
- Triage each item as Adopt, Already do, or Dismiss, saving instantly (or by keyboard shortcut) with an Undo back to New
- Each item carries an
EW-id; run/edge <id>in Claude Code to pull one into a project and mark it Building - Email digest of the genuinely new items, sent only when there is something new
Where the Items Come From¶
The weekly job researches six areas and then runs one synthesis pass that turns the material into ranked, concrete items:
- Search / SEO: the Google Search Central blog and changelog, Search Engine Land, and Search Engine Roundtable, for genuinely new Search features, ranking changes, and SEO guidance. This is where platform capabilities (like Google "preferred sources") surface
- Web platform: Core Web Vitals and page-experience updates from web.dev and Chrome, plus schema.org / structured-data changes
- Deliverability: bulk-sender and email-deliverability rules affecting transactional and marketing email, including Gmail and Yahoo sender requirements, DMARC / BIMI / one-click-unsubscribe, and Postmark and SendGrid guidance
- Checkout / CRO: Baymard Institute checkout and ecommerce UX research and newly published conversion best practices
- Accessibility & compliance: storefront WCAG / ADA expectations and US state privacy / cookie-consent law changes
- Platform capabilities: new integration and feed capabilities on platforms a subscription-grocery or delivery store could plug into, including Google Merchant Center and Shopping, Klaviyo, and Meta / TikTok shopping
Evergreen advice, marketing fluff, competitor product features, and things you would have to build from scratch are filtered out before you see them.
Page Layout¶
Force Run Now¶
A single Force Run Now button at the top runs the scan immediately, without waiting for the weekly schedule. A confirmation asks first, because the run makes several web-search calls and can take a minute.
When the run finishes you get a message telling you how many items were new out of the total, and whether a digest email went out. Clicking Force Run Now does not disturb anything you have already triaged.
Items Table¶
| Column | Description |
|---|---|
| ID | The item's EW-<id> reference. Use it with the /edge command (below) to turn the item into a project |
| Item | The item's title, a short summary of what it is, and a "Why it matters" line for your store |
| Area | The area the item came from. Links out to the original source when a URL is available. A freshness note (such as the publisher and month) appears beneath it |
| Impact | KLAI's guess at the business impact of adopting it: High, Medium, or Low |
| Effort | Rough adoption-effort guess: small, medium, or large |
| Already? | KLAI's honest self-assessment of whether you likely already do this: yes, no, or unsure. Advisory only |
| Added | The date the item was surfaced |
| Status | Where you have filed the item: Adopt, Already do, Dismissed, Building, or New |
| Actions | The triage buttons: Adopt, Already do, Dismiss, and an Undo that resets the item to New. Items already in a project show "In a project" instead of buttons |
A Sort control above the table sets the order:
- Smart (impact) (the default): still-actionable items first, highest impact at the top, with Building and Dismissed items pushed to the bottom and shown faded.
- Most recent and Oldest: plain date order, with no status grouping.
Triaging Items¶
Triage saves instantly, with no page reload. Click Adopt, Already do, or Dismiss on a row and the status label updates in place; resolved rows fade so the eye falls on what is still open. An Undo button appears once an item has a non-New status and resets it back to New.
You can also work the list from the keyboard: hover a row, then press A to adopt, E for already do, D to dismiss, or U to undo.
Building an Item in Claude Code¶
Each item carries an EW-<id> in the first column. To turn one into a project, run /edge <id> in Claude Code, for example /edge 43. Claude drafts a project file from the item and flips its status to Building here, so it drops out of the active list. Building items are shown faded, and a later scan never resets them.
If nothing has been generated yet, the page says so and points you at Force Run Now or the weekly run.
Triage Statuses¶
| Status | Meaning |
|---|---|
| New | Freshly surfaced, not yet reviewed |
| Adopt | You have decided this is worth adopting |
| Already do | You already do this, or you are passing on it |
| Dismissed | Not relevant. Dismissed items are not proposed again |
| Building | Pulled into a Claude Code project with /edge and now being built. Shown faded and sorted to the bottom in the Smart view. This is set by the build workflow, not by a button on the page |
Dismissing does not delete the item; it stays on the page, faded, so you can revisit the decision. Nothing the scan does later will reset a status you set. If the same item is surfaced again in a future week, it keeps the status you gave it.
The Weekly Digest¶
After each weekly run, if any new items were found, KLAI emails a digest of them to the Kiva Logic owner, best-first, with the summary, why it matters, impact, effort, and source link for each. When a run turns up nothing new, no email is sent, so the digest is always worth opening.
Common Use Cases¶
Catching a platform shift before a customer asks about it. The scan is pointed at best-practice and platform sources, not competitors, so a change like a new Search capability or a new sender requirement shows up here rather than in a support ticket.
Finding quick wins. Sort yourself by the Effort column: a small item with High impact and Already? marked no is the shortest path to a measurable change.
Setting the adoption shortlist. Mark the keepers Adopt, clear the noise with Dismiss, and the table becomes a shortlist rather than an inbox.
Getting a fresh batch before a planning session. Force Run Now bypasses the weekly schedule.
Troubleshooting¶
No items on the page. Nothing has been generated yet. Use Force Run Now, or wait for the weekly run. If the page stays empty after a run, check the site's error log for an "Edge Watch" entry. A failed gather or synthesis step is logged there.
A run reports a failure. The message on the page names the error. A run that could not gather any material, or whose synthesis returned nothing usable, is reported as failed and stores no items.
Force Run Now is slow. Expected. Each of the six areas is researched with live web search before the synthesis pass, so a run takes a minute or more.
An item says you already do it but you do not. The Already? value is KLAI's guess, not a fact. It is deliberately only advisory, so an important item still surfaces. Triage it normally.
An item you dismissed is missing. It is still there, sorted to the bottom and faded. Dismissed items are never surfaced as new again.
Recent Updates¶
2026-10-14: Triage now saves instantly with no page reload. The per-row buttons became a button group with an added Undo (resets an item to New), and you can hover a row and press A / E / D / U to adopt, mark already-do, dismiss, or undo. Resolved rows fade in place.
2026-10-07: Each item now shows an EW- id in a new ID column and an Added date column, with a Sort control (Smart / Most recent / Oldest). Added a Building status: run /edge <id> in Claude Code to pull an item into a project, which marks it Building here so it drops off the active list and is never re-surfaced.
2026-09-23: Edge Watch added. Weekly KLAI scan of ecommerce, SEO, and web-platform best practices worth adopting, with an Adopt / Already do / Dismiss triage page and a weekly email digest.