# Legache Smartwatch Concept

This note sketches a possible collaboration concept between `whetstone_RSA` and
Legache.

The goal is not "general AI on a watch."

The goal is a **bounded local knowledge interface** that can interpret short
voice or text requests, retrieve the right local information, and present fast,
useful results with local latency.

---

## Core Idea

If Legache already has:

- compact local document indexing
- strong metadata
- efficient retrieval
- structured organization of messy business information

then `whetstone_RSA` could sit on top of that as the **semantic interpretation
layer**.

In that architecture:

- Legache organizes and retrieves the right local knowledge
- RSA interprets the user's request into a bounded contract
- deterministic UI logic renders the response or action

---

## What The Watch App Would Actually Be

Not:

- a chatbot
- arbitrary long-form question answering
- open-ended reasoning over a large corpus

Instead:

- a fast local query bar
- a bounded voice-command interface
- a local knowledge lookup tool
- a semantic front-end for deterministic retrieval and display

---

## Example User Requests

- "What's our refund deadline?"
- "Who approves travel over two thousand dollars?"
- "Show the latest warehouse checklist."
- "Open the PTO policy."
- "Find the client note from yesterday."

These all have a useful bounded structure even if the phrasing is messy.

---

## Proposed Architecture

```text
synced local corpus + metadata
    ->
local retrieval / index lookup
    ->
RSA intent + slot interpretation
    ->
bounded answer contract
    ->
deterministic watch UI
```

Alternative flow:

```text
voice input
    ->
speech-to-text
    ->
RSA gate
    ->
retrieval + deterministic rendering
```

---

## What RSA Would Do

RSA would not try to "know everything in the documents."

RSA would help determine:

- what kind of request this is
- what data source or document family to search
- what entities or filters are being referenced
- whether the request is best handled as:
  - exact lookup
  - filtered search
  - policy answer
  - latest note/document retrieval
  - escalation / low-confidence fallback

RSA could also fill a small structured contract such as:

- mode
- entity type
- search domain
- filters
- requested action
- confidence

---

## Why A Watch Is Interesting

A smartwatch is a good fit if:

- latency matters
- privacy matters
- the requests are short
- the answer space is bounded enough
- hands-free voice interaction is useful

That makes this especially interesting for:

- field operations
- executives
- support staff
- warehouse / logistics contexts
- personal enterprise knowledge access

---

## What Makes This Plausible

This becomes much more plausible if Legache already solves:

- document sync
- metadata extraction
- retrieval quality
- local indexing

In that case, the watch does **not** need to solve open-ended question answering.

It only needs to:

- interpret the request
- retrieve the right local subset
- render a bounded answer or action quickly

---

## Good MVP Scope

Start with one narrow workflow.

Examples:

- policy lookup
- latest-note retrieval
- checklist lookup
- contact/account ownership lookup
- recent event / report lookup

The MVP should:

- use local synced data
- support short voice/text requests
- map requests into a bounded contract
- retrieve and display results locally

---

## Bad MVP Scope

Avoid:

- arbitrary multi-document reasoning
- long-form answer generation
- freeform research assistant behavior
- "answer anything about the whole company"

Those stretch beyond the bounded local-watch value proposition.

---

## Why This Could Be A Good Collaboration

Legache appears to already own an important part of the stack:

- organizing messy information into compact usable local structure

RSA would complement that by supplying:

- semantic intent interpretation
- bounded contract generation
- confidence / abstain behavior
- a small-model path for local interaction

That means the collaboration is not redundant.

It is potentially additive:

- Legache: local knowledge substrate
- RSA: bounded semantic interface layer

---

## Suggested Positioning

If discussed with Legache, position this as:

**A smartwatch-scale local knowledge interface built on top of Legache's indexed
corpus, with RSA acting as the semantic interpretation layer for bounded voice or
text requests.**

This is stronger than saying:

"let me build a watch AI app."

It is more specific, more technical, and more defensible.

---

## MVP Pitch Shape

Suggested framing:

"If Legache already has efficient local indexing and retrieval, I think there may
be a strong fit for a smartwatch or wearable interface that uses bounded semantic
interpretation on top of that. The goal would not be open-ended AI on a watch. It
would be fast local lookup and action for short enterprise knowledge requests,
using RSA-style intent and slot interpretation to drive deterministic retrieval
and display."