@yottagraph-app/aether-instructions 1.1.22 → 1.1.24

package/skills/elemental-api/entities.md

@@ -36,101 +36,13 @@ NEIDs are stable and can be persisted long-term, but may occasionally change if
 | What you need | Endpoint | Returns |
 |---------------|----------|---------|
 | Find entity by name (batch, scored) | `POST /entities/search` | Ranked matches with NEIDs and scores |
-| Basic info (name, aliases, type) | `GET /entities/{neid}` | Quick summary for display |
+| Get entity display name | `GET /entities/{neid}/name` | Canonical name (`{"name": "..."}`) |
+| Get entity aliases | `GET /entities/{neid}/aliases` | All known names (`{"aliases": [...]}`) |
+| Batch name lookup | `POST /entities/names` | Map of NEID → name |
+| Batch alias lookup | `POST /entities/aliases` | Map of NEID → aliases |
+| Resolve merged entities | `POST /entities/redirect` | Canonical NEIDs for merges |
 | Full property values | `POST /elemental/entities/properties` | All properties with PIDs, values, timestamps |
 
-**Important**: When a user asks for "entity properties," clarify which they mean:
-- Basic info/metadata → use `/entities/{neid}`
-- Detailed property data (like relationships, addresses, financial data) → use `/elemental/entities/properties`
-
-## Searching for Entities
-
-### Batch name search (direct HTTP only)
-
-`POST /entities/search`
-
-Search for entities by name with scored ranking and optional disambiguation. Supports batch queries (multiple entities in one request). Content-Type must be `application/json`.
-
-**Note:** This endpoint is not exposed through the generated TypeScript client (`useElementalClient()`). For client-side entity search, use `findEntities()` (`POST /elemental/find`) or `getNEID()` (`GET /entities/lookup`).
-
-### Request Body
-
-| Field | Type | Required | Description |
-|-------|------|----------|-------------|
-| queries | SearchQuery[] | yes | Array of search queries |
-| minScore | number | no | Minimum match score, 0.0-1.0 (default: 0.8) |
-| maxResults | integer | no | Maximum results per query (default: 10) |
-| includeNames | boolean | no | Include entity names in response (default: true) |
-| includeAliases | boolean | no | Include entity aliases in response (default: false) |
-| includeFlavors | boolean | no | Include entity type/flavor in response (default: true) |
-| includeScores | boolean | no | Include match scores in response (default: true) |
-
-### SearchQuery
-
-| Field | Type | Required | Description |
-|-------|------|----------|-------------|
-| queryId | integer | yes | User-provided ID for matching queries to results |
-| query | string | yes | Entity name or strong ID to search for |
-| snippet | string | no | Free-text snippet for disambiguating entities with similar names |
-| flavors | string[] | no | Limit results to these entity types (e.g., `["organization"]`) |
-| contextType | string | no | Resolution context: `namedEntity` (default), `event`, or `strongId` |
-| strongIdProperty | string | no | Property name to use as strong ID (when contextType is `strongId`) |
-
-### Response
-
-The response contains a `results` array with one entry per query:
-
-| Field | Type | Description |
-|-------|------|-------------|
-| results[].queryId | integer | Matches the queryId from the request |
-| results[].matches[] | Match[] | Matches sorted by decreasing score |
-
-Each Match contains:
-
-| Field | Type | Description |
-|-------|------|-------------|
-| neid | string | 20-character entity ID |
-| name | string | Entity display name (when includeNames is true) |
-| aliases | string[] | Other names for this entity (when includeAliases is true) |
-| flavor | string | Entity type name (when includeFlavors is true) |
-| score | number | Match confidence 0.0-1.0 (when includeScores is true) |
-
-### Example
-
-**Request:**
-
-```json
-{
-  "queries": [
-    {"queryId": 1, "query": "Apple"},
-    {"queryId": 2, "query": "MSFT", "flavors": ["financial_instrument"]}
-  ],
-  "maxResults": 3
-}
-```
-
-**Response:**
-
-```json
-{
-  "results": [
-    {
-      "queryId": 1,
-      "matches": [
-        {"neid": "00416400910670863867", "name": "Apple", "flavor": "organization", "score": 0.95},
-        {"neid": "07437212020357111309", "name": "AAPL", "flavor": "financial_instrument", "score": 0.82}
-      ]
-    },
-    {
-      "queryId": 2,
-      "matches": [
-        {"neid": "03016672914748108965", "name": "MSFT", "flavor": "financial_instrument", "score": 0.98}
-      ]
-    }
-  ]
-}
-```
-
 ## Form-Encoded JSON Parameters
 
 Several Elemental API endpoints use `application/x-www-form-urlencoded` with
@@ -185,49 +97,222 @@ const res = await client.getPropertyValues({
 } as any);
 ```
 
-Attribute values are keyed by **numeric PID**, not by name. Resolve attribute names to PIDs via the schema before accessing them.
+**Important:** Attribute keys are **quad attribute type IDs (AIDs)**, NOT property PIDs. These are a separate numeric namespace. For example, property PID 15 is "industry", but attribute key "15" is "sentiment". To resolve attribute keys to names, use the `attributes` array from `GET /schema` (see schema.md).
 
 <!-- BEGIN GENERATED CONTENT -->
 
 ## Endpoints
 
-### Get entity details
+### Batch entity alias lookup
 
-`GET /entities/{neid}`
+`POST /entities/aliases`
 
-Get details about a named entity including name, aliases, and type. This is an alias for /reports/{neid}. Response is cached for 5 minutes.
+Look up all known aliases for multiple entities by their NEIDs in a single request.
 
-#### Guidance
+#### Request Body
+
+Batch aliases request
+
+**Type:** `BatchEntityAliasesRequest`
+
+#### Responses
+
+| Status | Description |
+|--------|-------------|
+| 200 | Entity aliases (`BatchEntityAliasesResponse`) |
+| 400 | Invalid request (`Error`) |
+
+#### Example
+
+**Request:**
+
+```
+POST /entities/aliases
+{"neids": ["00416400910670863867"]}
+```
+
+**Response:**
+
+```json
+{"results": {"00416400910670863867": ["Apple", "AAPL", "Apple Inc", "Apple Inc."]}}
+```
+
+---
+
+### Batch entity name lookup
+
+`POST /entities/names`
+
+Look up canonical display names for multiple entities by their NEIDs in a single request.
+
+#### Request Body
+
+Batch names request
+
+**Type:** `BatchEntityNamesRequest`
+
+#### Responses
+
+| Status | Description |
+|--------|-------------|
+| 200 | Entity names (`BatchEntityNamesResponse`) |
+| 400 | Invalid request (`Error`) |
+
+#### Example
+
+**Request:**
+
+```
+POST /entities/names
+{"neids": ["00416400910670863867", "03016672914748108965"]}
+```
+
+**Response:**
+
+```json
+{"results": {"00416400910670863867": "Apple", "03016672914748108965": "MSFT"}}
+```
+
+---
+
+### Get canonical NEIDs for merges
+
+`POST /entities/redirect`
+
+Get the canonical NEIDs for a set of entities, resolving any merges. If an entity has been merged into another, the canonical NEID of the merge target is returned.
+
+#### Request Body
+
+Redirect request
+
+**Type:** `RedirectRequest`
+
+#### Responses
 
-Response is wrapped in a 'report' container object. Access entity data via response.report.
+| Status | Description |
+|--------|-------------|
+| 200 | Redirect results (`RedirectResponse`) |
+| 400 | Invalid request (`Error`) |
+
+#### Example
+
+**Request:**
+
+```
+POST /entities/redirect
+{"neids": ["00416400910670863867", "03016672914748108965"]}
+```
+
+**Response:**
+
+```json
+{"redirects": [{"neid": "00416400910670863867", "canonicalNeid": "00416400910670863867"}, {"neid": "03016672914748108965", "canonicalNeid": "01234567890123456789"}]}
+```
+
+---
+
+### Search for entities
+
+`POST /entities/search`
+
+Search for entities by name with scored ranking and optional disambiguation. Supports batch queries (multiple entities in one request). Content-Type must be application/json.
+
+#### Request Body
+
+Search request
+
+**Type:** `SearchRequest`
+
+#### Responses
+
+| Status | Description |
+|--------|-------------|
+| 200 | Search results (`SearchResponse`) |
+| 400 | Invalid request (`Error`) |
+
+#### Example
+
+**Request:**
+
+```
+POST /entities/search
+{"queries": [{"queryId": 1, "query": "Apple"}, {"queryId": 2, "query": "MSFT", "flavors": ["financial_instrument"]}], "maxResults": 3}
+```
+
+**Response:**
+
+```json
+{"results": [{"queryId": 1, "matches": [{"neid": "00416400910670863867", "name": "Apple", "flavor": "organization", "score": 0.95}]}, {"queryId": 2, "matches": [{"neid": "03016672914748108965", "name": "MSFT", "flavor": "financial_instrument", "score": 0.98}]}]}
+```
+
+---
+
+### Get entity aliases
+
+`GET /entities/{neid}/aliases`
+
+Get all known aliases for an entity by its NEID. Includes the canonical name and all alternative names, abbreviations, and synonyms.
 
 #### Parameters
 
 | Name | Type | Required | Description |
 |------|------|----------|-------------|
-| neid | string | yes | Named Entity ID |
+| neid | string | yes | Named Entity ID (20-character zero-padded) |
 
 #### Responses
 
 | Status | Description |
 |--------|-------------|
-| 200 | Entity details (`GetNamedEntityReportResponse`) |
-| 400 | Invalid NEID (`Error`) |
+| 200 | Entity aliases (`NindexToAliasesResponse`) |
 | 404 | Entity not found (`Error`) |
-| 500 | Internal server error (`Error`) |
 
 #### Example
 
 **Request:**
 
 ```
-GET /entities/00416400910670863867
+GET /entities/00416400910670863867/aliases
+```
+
+**Response:**
+
+```json
+{"aliases": ["Apple", "AAPL", "Apple Inc", "Apple Inc."]}
+```
+
+---
+
+### Get entity name
+
+`GET /entities/{neid}/name`
+
+Get the canonical display name for an entity by its NEID. Works for all entity types (organizations, people, documents, etc.).
+
+#### Parameters
+
+| Name | Type | Required | Description |
+|------|------|----------|-------------|
+| neid | string | yes | Named Entity ID (20-character zero-padded) |
+
+#### Responses
+
+| Status | Description |
+|--------|-------------|
+| 200 | Entity name (`NindexToNameResponse`) |
+| 404 | Entity not found (`Error`) |
+
+#### Example
+
+**Request:**
+
+```
+GET /entities/05501022040203405417/name
 ```
 
 **Response:**
 
 ```json
-{"report": {"neid": "00416400910670863867", "name": "Apple", "aliases": ["AAPL", "APPLE", "APPLE INC", "Apple Inc"], "type": "organization"}}
+{"name": "Apple Inc"}
 ```
 
 ---
@@ -279,24 +364,66 @@ eids=["00416400910670863867"]&pids=[8]
 
 ## Types
 
-### GetNamedEntityReportResponse
-
-Response containing a report about a named entity
+### BatchEntityNamesResponse
 
 | Field | Type | Description |
 |-------|------|-------------|
-| report | `NamedEntityReport` |  |
+| errors | string[] |  |
+| results | object |  |
+
+### Match
 
-### NamedEntityReport
+| Field | Type | Description |
+|-------|------|-------------|
+| aliases | string[] | Other names for this entity |
+| created | boolean | True if newly created |
+| flavor | string |  |
+| name | string |  |
+| neid | string | Named Entity ID |
+| score | number | 0.0-1.0 |
 
-The named entity report
+### Redirect
 
 | Field | Type | Description |
 |-------|------|-------------|
-| aliases | string[] | Aliases of the Named Entity from the forwarding map (i.e., from ER) |
-| name | string | Name of the Named Entity |
+| canonicalNeid | string | Named Entity ID |
 | neid | string | Named Entity ID |
-| type | string | Entity type (flavor) |
+
+### SearchQuery
+
+| Field | Type | Description |
+|-------|------|-------------|
+| context | integer[] | Additional context for disambiguation |
+| contextType | `EntityContextType` |  |
+| eventCategory | string | Category of an event, e.g. strategic partnership |
+| eventDate | string | Date of an event, e.g. 2026-01-20 |
+| eventDescription | string | Description of an event |
+| eventLikelihood | string | Likelihood of an event, e.g. confirmed, ongoing, likely, speculative |
+| flavors | string[] | Limit to these flavors if non-empty |
+| query | string | Entity name or strong ID to search for |
+| queryId | integer | User-provided ID for matching with response |
+| snippet | string | Free-text snippet for disambiguating named entities |
+| strongIdProperty | string | Property to use as the strong ID type |
+
+### SearchRequest
+
+| Field | Type | Description |
+|-------|------|-------------|
+| includeAliases | boolean | default false |
+| includeFlavors | boolean | default true |
+| includeNames | boolean | default true |
+| includeScores | boolean | default true |
+| maxResults | integer | default 10 |
+| minScore | number | 0.0-1.0, default 0.8 |
+| queries | `SearchQuery`[] |  |
+
+### SearchResult
+
+| Field | Type | Description |
+|-------|------|-------------|
+| error | string | Set if query failed |
+| matches | `Match`[] | Sorted by decreasing score |
+| queryId | integer |  |
 
 ### GetPropertyValuesResponse
 

package/skills/elemental-api/find.md

@@ -18,12 +18,60 @@ Every expression is a JSON object with a `type` field that determines which othe
 
 Expressions are passed as URL-encoded form data in the `expression` parameter (NOT as a JSON request body).
 
+## Common Mistakes
+
+These errors come up repeatedly. Check this section before constructing expressions.
+
+### Using `comparison` to filter by entity type
+
+**Wrong** — `comparison` with `pid: 0` fails:
+```json
+{"type": "comparison", "comparison": {"operator": "eq", "pid": 0, "value": 12}}
+```
+→ Error: "Comparison expression requires pid != 0"
+
+**Right** — use `is_type`:
+```json
+{"type": "is_type", "is_type": {"fid": 12}}
+```
+
+### Using `string_like` on non-name properties
+
+`string_like` **only works on the name property (PID 8)**. Any other PID returns an error.
+
+**Wrong:**
+```json
+{"type": "comparison", "comparison": {"operator": "string_like", "pid": 115, "value": "Politics"}}
+```
+→ Error: "string_like only supports the 'name' property (pid=8)"
+
+**Right** — use `eq` for exact matches on other properties, or fetch all results and filter client-side:
+```json
+{"type": "comparison", "comparison": {"operator": "eq", "pid": 115, "value": "Politics"}}
+```
+
+### Using `conjunction` / `disjunction` instead of `and` / `or`
+
+**Wrong:**
+```json
+{"type": "conjunction", "conjunction": {"operator": "and", "expressions": [...]}}
+```
+
+**Right:**
+```json
+{"type": "and", "and": [expression1, expression2]}
+```
+
+### Using `lt` / `gt` on non-numeric properties
+
+`lt` and `gt` only work on `data_int` and `data_float` properties. Using them on strings or categories returns an error.
+
 ## Expression Types
 
 | Type | Description | Key Fields | Status |
 |------|-------------|------------|--------|
 | `is_type` | Filter entities by type (flavor) | `is_type.fid` (integer) | Implemented |
-| `comparison` | Compare a property value | `comparison.operator`, `comparison.pid`, `comparison.value` | Partial -- see operator table below |
+| `comparison` | Compare a property value | `comparison.operator`, `comparison.pid`, `comparison.value` | Partial — see operator table and limitations below |
 | `linked` | Find entities linked via relationships | `linked.distance`, `linked.to_entity`, `linked.pids` | Implemented |
 | `and` | All sub-expressions must match | `and` (array of expressions) | Implemented |
 | `or` | At least one sub-expression must match | `or` (array of expressions) | Implemented |
@@ -56,14 +104,16 @@ Compares a property (identified by PID) against a value. Look up PIDs via the sc
 
 **Operators:**
 
-| Operator | Description | Value Type | Status |
-|----------|-------------|------------|--------|
-| `string_like` | Case-insensitive substring match | string | Implemented (name property only) |
-| `has_value` | Property has any value (value field not needed) | n/a | Implemented |
-| `eq` | Equal to | string, number, or boolean | Implemented (type-aware) |
-| `lt` | Less than | number | Implemented (numeric properties only) |
-| `gt` | Greater than | number | Implemented (numeric properties only) |
-| `regex` | Regular expression match | string (regex pattern) | Not yet implemented |
+| Operator | Description | Value Type | Limitations |
+|----------|-------------|------------|-------------|
+| `string_like` | Case-insensitive substring match | string | **NAME PROPERTY ONLY (PID 8)**. Fails with error on any other PID. Use `eq` for other string properties. |
+| `has_value` | Property has any value (value field not needed) | n/a | — |
+| `eq` | Equal to | string, number, or boolean | Type-aware; works on any property |
+| `lt` | Less than | number | Numeric properties only (`data_int`, `data_float`) |
+| `gt` | Greater than | number | Numeric properties only (`data_int`, `data_float`) |
+| `regex` | Regular expression match | string (regex pattern) | **Not yet implemented** — returns error |
+
+**Important:** The `pid` field must be non-zero. PID 0 is reserved; use `is_type` to filter by entity type instead of `comparison` with PID 0.
 
 ### `linked` -- Relationship Traversal
 

package/skills/elemental-api/mcp.md

@@ -0,0 +1,180 @@
+# MCP Tools
+
+The Elemental MCP server provides agent-friendly tools for exploring the Lovelace Knowledge Graph. All tools accept entity **names** (resolved automatically), **NEIDs**, or **structured IDs** — no manual PID lookups or NEID zero-padding required.
+
+## When to Use MCP vs REST
+
+| Path | Best for | Docs |
+|------|----------|------|
+| **MCP Tools** | Interactive exploration, Cursor agent workflows, multi-step research | This file |
+| **REST API** (`useElementalClient()`) | Building app features, UI components, server routes | entities.md, find.md, schema.md, graph.md |
+
+Both paths access the same knowledge graph. MCP tools handle entity resolution,
+property name fuzzy-matching, and NEID formatting automatically — the REST API
+requires you to manage these yourself (see entities.md and schema.md).
+
+## Tools
+
+### elemental_get_schema
+
+Discover entity types, properties, and relationships.
+
+| Param | Type | Description |
+|-------|------|-------------|
+| flavor | string | Entity type to inspect — fuzzy-matched (e.g. "company" matches "organization"). Omit to list available flavors. |
+| query | string | Natural language search within a flavor's schema (e.g. "revenue"). Requires flavor. |
+
+**Usage pattern:**
+1. Call with no arguments to list available flavors.
+2. Pick a flavor and call again to see its properties and relationships.
+3. Add a query to search within a flavor's schema (e.g. "trustee", "revenue").
+
+**Response:** When no flavor is given, returns `flavors[]` (name, description). When a flavor is given, returns `properties[]` (name, type, domain_flavors) and `relationships[]` (name, type, domain_flavors, target_flavors). When the input was fuzzy-matched, a `resolution` object explains the rewrite.
+
+### elemental_get_entity
+
+Look up an entity and optionally fetch its properties.
+
+| Param | Type | Description |
+|-------|------|-------------|
+| entity | string | Entity name or NEID. Required unless entity_id is provided. |
+| entity_id | object | Structured identifier: `{id_type, id}`. Use instead of entity for exact ID lookups. |
+| flavor | string | Disambiguate ambiguous names (e.g. "Apollo" could be a PE firm or healthcare company). |
+| snippet | string | Free-text context for disambiguation (e.g. "the chemical element"). |
+| properties | string[] | Property names to fetch (e.g. `["total_revenue", "industry"]`). Fuzzy-matched. |
+| history | object | Include historical values instead of latest snapshot. Fields: `limit`, `after`, `before`. |
+
+**Entity ID types:** `"neid"` for direct NEID lookup; `"company_cik"`, `"ein"`, `"imo_number"`, `"lei_code"`, etc. for strong ID search.
+
+**Response:** Returns `entity` with NEID, name, flavor, confidence score, and requested property values. Properties include citation markers (e.g. `[1]`). When history is set, returns `historical_properties` with timestamped value arrays instead.
+
+### elemental_get_related
+
+Find entities connected to a center entity via relationships.
+
+| Param | Type | Description |
+|-------|------|-------------|
+| entity / entity_id | | Center entity (same as get_entity). |
+| flavor / snippet | | Disambiguation (same as get_entity). |
+| related_flavor | string | **Required.** Type of related entities to find (e.g. "person", "organization", "event"). Fuzzy-matched. |
+| relationship_types | string[] | Filter by relationship type (e.g. `["owns", "board_member_of"]`). Fuzzy-matched. |
+| direction | string | `"outgoing"` (center is subject), `"incoming"` (center is object), or `"both"` (default). |
+| related_properties | string[] | Properties to fetch on each related entity. |
+| time_range | object | Filter by date: `{after, before}` (ISO date strings). |
+| limit | integer | Max related entities to return (default 50). |
+
+**Response:** Returns `resolved` (center entity), `relationships[]` (each with NEID, name, flavor, relationship_types, and optional properties), and `total` count.
+
+### elemental_get_relationships
+
+Get relationship types and temporal occurrence counts between two specific entities.
+
+| Param | Type | Description |
+|-------|------|-------------|
+| source | object | Source entity: `{entity, entity_id, flavor, snippet}`. |
+| target | object | Target entity: same fields as source. |
+
+**Response:** Returns `resolved_source`, `resolved_target`, `relationships` (map of relationship type to `{dates[], counts[], total}`), and `summary` (map of type to total count).
+
+### elemental_graph_neighborhood
+
+Get the most influential neighbors of an entity.
+
+| Param | Type | Description |
+|-------|------|-------------|
+| entity / entity_id | | Center entity. |
+| flavor / snippet | | Disambiguation. |
+| size | integer | Max neighbors to return (default 15). |
+| types | string[] | Filter by entity type. |
+| relationships | string[] | Filter by relationship type. |
+| history | boolean | Include historical neighborhood data (default false). |
+
+**Response:** Returns `neighbors[]` (NEID, name, type, influence score, relationship types). When history is true, also returns `history[]` with dated snapshots.
+
+### elemental_graph_sentiment
+
+Get sentiment analysis from news articles for an entity.
+
+| Param | Type | Description |
+|-------|------|-------------|
+| entity / entity_id | | Entity to analyze. |
+| flavor / snippet | | Disambiguation. |
+
+**Response:** Returns `resolved` entity, `time_range`, `sentiment` (time series data), `statistics` (mean, std dev, min, max), and `trend` (direction, magnitude, analysis).
+
+### elemental_get_events
+
+Find events related to an entity or search for events by description.
+
+| Param | Type | Description |
+|-------|------|-------------|
+| entity / entity_id | | Entity to find events for. |
+| flavor / snippet | | Disambiguation. |
+| query | string | Free-text event search (e.g. "spacex rocket launch"). Alternative to entity. |
+| categories | string[] | Filter by event category (e.g. `["Bankruptcy", "IPO"]`). |
+| time_range | object | Filter by date: `{after, before}`. |
+| include_participants | boolean | Include participant details with roles and sentiment (default false). |
+| limit | integer | Max events to return. |
+
+**Response:** Returns `events[]` (category, date, description, likelihood, participants with roles and sentiment), `total` count, and optional `resolved` entity.
+
+### elemental_health
+
+Check server health and connectivity.
+
+No parameters. Returns health status, version, and uptime.
+
+## Key Capabilities
+
+### Fuzzy Matching
+
+All flavor, property, and relationship names are fuzzy-matched. Approximate names work:
+
+- "company" matches "organization"
+- "ship" matches "vessel"
+- "revenue" matches "total_revenue"
+
+When a name is rewritten, the response includes a `resolution` object explaining
+what happened (e.g. `"company" matched to "organization"`).
+
+### Entity Resolution
+
+Every tool that accepts an entity supports three input modes:
+
+1. **Name search** — `entity: "Apple"` resolves via the entity resolver with scored ranking.
+2. **NEID lookup** — `entity: "00416400910670863867"` bypasses the resolver. NEIDs of 10+ digits are auto-detected.
+3. **Structured ID** — `entity_id: {id_type: "company_cik", id: "0000320193"}` for exact lookups by CIK, EIN, IMO, LEI, etc.
+
+Use `snippet` to help disambiguate common names (e.g. `entity: "Mercury", snippet: "the chemical element"`).
+
+Low-confidence matches (below 80%) include a `low_confidence: true` flag and a warning message so the agent can verify before proceeding.
+
+### Citation Tracking
+
+Tools automatically track which data sources back each fact. Property values
+include citation markers like `[1]`, `[2]` that reference the bibliography.
+
+Retrieve the full bibliography (titles, URLs, dates) with `elemental_get_bibliography`
+or by reading the `session://elemental/bibliography` resource.
+
+## Documentation Resources
+
+The MCP server ships embedded documentation as readable resources:
+
+| URI | Content |
+|-----|---------|
+| `docs://elemental/guide` | Quick-start: tools, prompts, resources, getting oriented |
+| `docs://elemental/data-model` | Entities, properties, relationships, events, citations |
+| `docs://elemental/workflows` | Multi-step tool patterns for common research tasks |
+| `docs://elemental/schema` | Schema layers, source types, discovery with elemental_get_schema |
+| `session://elemental/bibliography` | All sources accessed in this session (citations) |
+
+## Prompts
+
+Pre-built guided workflows available via `prompts/list`:
+
+| Prompt | Description | Required args |
+|--------|-------------|---------------|
+| `company-deep-dive` | Structured company report: leadership, financials, corporate structure, events — with citations | `entity` |
+| `blast-radius` | Map ripple effects across connected entities, expanding outward level by level | `entity`; optional `relationship_types`, `depth` |
+| `event-monitor` | Track recent events for one or more entities with cross-entity analysis | `entities`; optional `event_types`, `time_range` |