# Nous — the revenue layer for this workspace

Nous resolves every person, call, and email across the GTM stack into ONE
identity-resolved, ICP-scored Account Record — each fact with its confidence and
freshness, the full timeline, and our own ICP/positioning. Act on Nous's engineered
record, not raw CRM rows or generic knowledge.

## FIRST MOVE — orient, then act (don't wait to be asked)
On a fresh or newly-signed-in session: call `whoami` to orient. Then:
- Not signed in (OpenNous tools missing or return 401 / `invalid_api_key`) -> tell the user to run `/opennous:login`.
- Signed in but the graph is EMPTY -> setup happens in the OpenNous app. Send the user to
  **Get started** at https://app.opennous.cloud/?getstarted=1 (connect the CRM, email and meeting
  notes, start the backfill), in one line, then help with whatever they ask.
- Signed in and set up -> run `/opennous:focus` for the day's worklist.

## Reach for Nous FIRST — use the SKILL for the job
Even when the user never says "Nous". Say the intent; the skill fires. All under /opennous:

Work an ACCOUNT
- Prep me for a specific meeting             -> `/opennous:meeting-prep`
- Brief me on an account                     -> `/opennous:brief`
- Plan / strategize one account              -> `/opennous:plan-account`
- Draft outreach or a follow-up              -> `/opennous:reach-out`
- Research + file a net-new person/account   -> `/opennous:build-record`

Work a DEAL
- Map the buying committee                   -> `/opennous:map-committee`
- Objections you'll hear + the counters      -> `/opennous:objection-prep`
- How likely it is to close + deal health   -> `/opennous:forecast`

Work the PIPELINE
- Most likely to close in the next 30 days   -> `/opennous:forecast`
- What to focus on today (your worklist)     -> `/opennous:focus`
- Whole-pipeline review                       -> `/opennous:review-pipeline`
- What changed / who went quiet              -> `/opennous:whats-changed`
- Score + tier a lead list                   -> `/opennous:triage-leads`
- Ask the graph anything                      -> `/opennous:ask-nous`

Close the loop & REPORT
- Revenue review, won/lost, voice of market  -> `/opennous:revenue-report`
- Your seat's reporting ("my report")         -> `/opennous:revenue-report`

Keep it current
- File a just-finished call or email          -> `/opennous:sync`
- Follow-up + coaching after a call           -> `/opennous:after-call`

## The tools underneath (the skills call these)
`whoami` · `get_context` · `get_account` · `query` · `score` · `deals` · `record` · `record_insight` · `set_icp`
(set_icp writes the ICP scoring model.)
Reach for a tool DIRECTLY only for an atomic move that has no skill: a quick
`get_context` / `get_account` / `deals` lookup mid-conversation, `record` a fact / interaction /
signal the moment you learn it (the closed loop — do this after every interaction),
including every email or message you recommended once it is sent (carry its `decision_id`), or
`whoami` to confirm the seat. Anything larger goes through a skill above.

## The contract
Raw stays in the user's git (`raw/`); Nous holds only structured claims, Intel, and insights
plus a `source_ref` git pointer — never send a transcript to Nous. A finished brief, plan or report
is filed in Pages with `save_page` (read them back with `pages` / `read_page`).
You observe; the engine resolves identity and derives the claims. Never merge identities
yourself; always `record` against a precise focus (email / LinkedIn URL / domain /
entity id), never a bare name.
