@yottagraph-app/aether-instructions 1.1.18 → 1.1.20

package/skills/elemental-api/schema.md

@@ -12,7 +12,7 @@ The schema defines the data model: what **entity types** (flavors) exist and wha
 ## Key Concepts
 
 - **Flavors** = Entity types. Each entity belongs to exactly one flavor.
-  - Examples: "ship" (FID 1), "organization" (FID 10), "person" (FID 9)
+  - Examples: "organization" (FID 10), "person" (FID 9), "financial_instrument" (FID 3)
   - Identified by a Flavor ID (FID) — a small integer
 - **Properties** = Attributes that entities can have. Each property has:
   - A Property ID (PID) — a small integer
@@ -30,8 +30,8 @@ There are two schema endpoints with different levels of detail:
 | `GET /elemental/metadata/schema` | fid, name only | pid, name, type only |
 
 **Use `/schema`** (recommended) when you need:
-- Human-readable display names (e.g., "Ship" vs "ship")
-- Units of measurement (e.g., "m", "kg", "knots")
+- Human-readable display names (e.g., "Organization" vs "organization")
+- Units of measurement (e.g., "m", "kg")
 - Which flavors a property applies to (`domain_findexes`)
 
 **Use `/elemental/metadata/schema`** when you just need basic FID/PID to name mappings.
@@ -48,28 +48,6 @@ There are two schema endpoints with different levels of detail:
 2. **Find entities of a type** → `POST /elemental/find` with `is_type` expression
 3. **Get property values** → `POST /elemental/entities/properties` to fetch values for those entities
 
-## Common Properties by Entity Type
-
-This is a quick-reference for writing first-pass code. **The schema endpoint
-is the source of truth** — always call `GET /schema` to get actual PIDs and
-confirm which properties exist in a given deployment. Property availability
-varies by dataset.
-
-| Entity Type | Common Properties |
-|---|---|
-| **organization** | `name`, `country`, `ticker`, `industry`, `business_sector`, `sic_code`, `state_of_incorporation`, `mailing_address`, `business_phone`, `company_cik` |
-| **person** | `name`, `country`, `nationality`, `birth_date`, `position`, `person_cik`, `job_title` |
-| **financial_instrument** | `name`, `ticker`, `security_type`, `instrument_type`, `cusip_number` |
-| **document** (SEC filings) | `name`, `title`, `form_type`, `filing_date`, `report_date`, `accession_number`, `form_type_detail` |
-| **article** | `name`, `title`, `sentiment` |
-| **event** | `name`, `category`, `date`, `description`, `likelihood` |
-| **location** | `name`, `fixedLatitude`, `fixedLongitude` |
-
-**Relationship properties** (type `data_nindex`) link entities to each other.
-Common ones for organizations: `acquires`, `owns`, `competes_with`,
-`partnered_with`, `does_business_with`, `is_part_of`, `issues`, `has_subsidiary`.
-For people: `works_at`, `head_of`, `is_director`, `is_officer`, `is_colleague_of`.
-
 <!-- BEGIN GENERATED CONTENT -->
 
 ## Endpoints
@@ -102,7 +80,7 @@ GET /schema
 **Response:**
 
 ```json
-{"flavors": [{"findex": 1, "name": "ship", "singular_display_name": "Ship", "plural_display_name": "Ships"}, {"findex": 10, "name": "organization", "singular_display_name": "Organization", "plural_display_name": "Organizations"}], "properties": [{"pid": 8, "name": "name", "display_name": "Name", "value_type": "data_cat"}, {"pid": 22, "name": "length", "display_name": "Length", "unit": "m", "value_type": "data_float"}]}
+{"flavors": [{"findex": 9, "name": "person", "singular_display_name": "Person", "plural_display_name": "People"}, {"findex": 10, "name": "organization", "singular_display_name": "Organization", "plural_display_name": "Organizations"}], "properties": [{"pid": 8, "name": "name", "display_name": "Name", "value_type": "data_cat"}, {"pid": 15, "name": "industry", "display_name": "Industry", "value_type": "data_cat"}]}
 ```
 
 ---
@@ -210,7 +188,7 @@ Returns comprehensive schema information including all entity types (flavors), p
 
 #### Guidance
 
-Response is wrapped in a 'schema' container object. Access flavors and properties via response.schema.flavors and response.schema.properties. Flavors contain: fid (unique identifier), name (e.g., 'ship', 'aircraft'). Properties contain: pid (unique identifier), name (e.g., 'latitude', 'name'), type (e.g., 'data_float', 'data_int', 'data_cat', 'data_nindex').
+Response is wrapped in a 'schema' container object. Access flavors and properties via response.schema.flavors and response.schema.properties. Flavors contain: fid (unique identifier), name (e.g., 'organization', 'person'). Properties contain: pid (unique identifier), name (e.g., 'name', 'industry'), type (e.g., 'data_float', 'data_int', 'data_cat', 'data_nindex').
 
 #### Responses
 
@@ -231,7 +209,7 @@ GET /elemental/metadata/schema
 **Response:**
 
 ```json
-{"op_id": "40dc4cd9-f1b2-4b5c-85d0-c7c61256e5d9", "follow_up": false, "schema": {"flavors": [{"fid": 1, "name": "ship"}, {"fid": 2, "name": "handset"}, {"fid": 10, "name": "organization"}], "properties": [{"pid": 1, "name": "mmsi", "type": "data_cat"}, {"pid": 8, "name": "name", "type": "data_cat"}]}}
+{"op_id": "40dc4cd9-f1b2-4b5c-85d0-c7c61256e5d9", "follow_up": false, "schema": {"flavors": [{"fid": 9, "name": "person"}, {"fid": 10, "name": "organization"}, {"fid": 3, "name": "financial_instrument"}], "properties": [{"pid": 8, "name": "name", "type": "data_cat"}, {"pid": 15, "name": "industry", "type": "data_cat"}]}}
 ```
 
 ---
@@ -279,10 +257,11 @@ Entity type (flavor) with human-readable display names
 
 | Field | Type | Description |
 |-------|------|-------------|
+| description | string | Semantic description of what this flavor represents |
 | findex | integer | Unique flavor identifier (same as fid in other endpoints) |
 | name | string | Flavor name (internal identifier) |
-| plural_display_name | string | Human-readable plural name (e.g., "Ships") |
-| singular_display_name | string | Human-readable singular name (e.g., "Ship") |
+| plural_display_name | string | Human-readable plural name (e.g., "People") |
+| singular_display_name | string | Human-readable singular name (e.g., "Person") |
 
 ### SchemaProperty
 
@@ -290,6 +269,7 @@ Property with display name, unit, and domain information
 
 | Field | Type | Description |
 |-------|------|-------------|
+| description | string | Semantic description of what this property represents |
 | display_name | string | Human-readable property name |
 | domain_findexes | integer[] | Flavor IDs (findexes) that can have this property |
 | name | string | Property name (internal identifier) |

package/skills/elemental-api/articles.md

@@ -1,386 +0,0 @@
-# Articles & Mentions
-
-Articles are one significant source of data for the Knowledge Graph. A **mention** is a specific reference to an entity within an article, capturing the context and sentiment of that reference.
-
-## When to Use
-
-- You need to find news coverage about an entity
-- You want mention counts or volume over time
-- You have a specific article ID (ARTID) or mention code (MCODE) and need full details
-- You want to read the actual text or summary of an article
-- You need article metadata: publication name, date, URL, trustworthiness scores
-
-## Key Concepts
-
-- **ARTID**: Unique identifier for each article.
-  - Format: 20-character numeric string (same format as NEIDs)
-  - Example: `05433395856363393596`
-- **MCODE**: A unique identifier for each mention, linking entity + article + context.
-  - Format: `{neid}:{artid}` with colon separator
-  - Example: `00416400910670863867:05433395856363393596`
-- **Mention Detail**: Includes the snippet, publication, sentiment, and other metadata
-- **Mention Counts**: Aggregated counts over time buckets, useful for tracking media attention
-- **Article Detail**: Full metadata including title, summary, publication info, and scores
-- **Article Text**: The actual content of the article (when available)
-
-## Important Limitations
-
-⚠️ **Volume Warning**: A single entity may have tens of thousands of associated articles. Avoid querying all articles for an entity over long time periods.
-
-**Recommended approach:**
-1. Start with mention counts to understand volume
-2. Use mention endpoints to identify specific mentions of interest
-3. Then retrieve full article details only for those specific articles
-
-## Tips
-
-- Start with mention counts to understand volume, then drill into specific mentions
-- Filter by time range to avoid overwhelming results for high-profile entities
-- Use neighborhood mentions to see what else was mentioned alongside your target entity
-- Article text may not be available for all articles (depends on licensing)
-- Use trustworthiness and page rank scores to assess source quality
-
-<!-- BEGIN GENERATED CONTENT -->
-
-## Endpoints
-
-### Get article detail
-
-`GET /articles/{artid}`
-
-Get detailed information about an article by its ID. Response is cached for 1 hour (articles are immutable).
-
-#### Guidance
-
-Response is wrapped in a 'detail' container object. Access article data via response.detail.
-
-#### Parameters
-
-| Name | Type | Required | Description |
-|------|------|----------|-------------|
-| artid | string | yes | Article ID |
-
-#### Responses
-
-| Status | Description |
-|--------|-------------|
-| 200 | Article detail (`GetArticleResponse`) |
-| 400 | Invalid ARTID (`Error`) |
-| 404 | Article not found (`Error`) |
-| 500 | Internal server error (`Error`) |
-
-#### Example
-
-**Request:**
-
-```
-GET /articles/05433395856363393596
-```
-
-**Response:**
-
-```json
-{"detail": {"artid": "05433395856363393596", "publication_date": "2026-01-28T15:56:47Z", "title": "Apple's Cook says he's 'heartbroken' by Minneapolis events...", "summary": "The article details two fatal shootings by federal agents...", "batch": "7f302ee6808d7c45a09aed07c93ec785", "source": "7f302ee6808d7c45a09aed07c93ec785", "url": "https://www.cnbc.com/2026/01/28/...", "mentions": [{"neid": "00315863961550087877", "artid": "05433395856363393596"}], "topics": [], "events": ["00526686651102446795", "01090525413205193094"], "publication_name": "cnbc.com", "publication_home_url": "http://www.cnbc.com", "trustworthiness": 0.664, "original_publication_name": "CNBC", "tone": "neutral", "title_factuality": "accurate", "tone_objectivity_score": 0.533, "title_factuality_score": 7.133, "syndication_score": 1}}
-```
-
----
-
-### Get article text
-
-`GET /articles/{artid}/text`
-
-Get the full text content of an article by its ID. Response is cached for 10 minutes.
-
-#### Guidance
-
-This endpoint returns plain text, NOT JSON. Parse the response as text, not as a JSON object.
-
-#### Parameters
-
-| Name | Type | Required | Description |
-|------|------|----------|-------------|
-| artid | string | yes | Article ID |
-
-#### Responses
-
-| Status | Description |
-|--------|-------------|
-| 200 | Article text |
-| 400 | Invalid ARTID (`Error`) |
-| 500 | Internal server error (`Error`) |
-
-#### Example
-
-**Request:**
-
-```
-GET /articles/05433395856363393596/text
-```
-
-**Response:**
-
-```
-Apple CEO Tim Cook said he was "heartbroken" by the situation in Minneapolis...
-```
-
----
-
-### Get mentions for entities
-
-`GET /mentions/lookup`
-
-Get list of mention codes (MCODEs) for named entities in a neighborhood within a time interval. Response is cached for 5 minutes.
-
-#### Parameters
-
-| Name | Type | Required | Description |
-|------|------|----------|-------------|
-| interval_start | string | yes | Start time of interval (RFC3339) |
-| interval_end | string | yes | End time of interval (RFC3339) |
-| neid | string[] | yes | Named Entity ID(s) in the neighborhood |
-
-#### Responses
-
-| Status | Description |
-|--------|-------------|
-| 200 | List of mention codes (`GetMentionsResponse`) |
-| 400 | Invalid parameters (`Error`) |
-| 500 | Internal server error (`Error`) |
-
-#### Example
-
-**Request:**
-
-```
-GET /mentions/lookup?interval_start=2026-01-01T00:00:00Z&interval_end=2026-02-01T00:00:00Z&neid=00416400910670863867
-```
-
-**Response:**
-
-```json
-{"mcodes": [{"neid": "00416400910670863867", "artid": "05433395856363393596"}, {"neid": "00416400910670863867", "artid": "02706389331155211812"}]}
-```
-
----
-
-### Get mention counts over time
-
-`GET /mentions/lookup/counts`
-
-Get bucketed counts of mentions for entities in a neighborhood within a time interval
-
-#### Parameters
-
-| Name | Type | Required | Description |
-|------|------|----------|-------------|
-| interval_start | string | yes | Start time of interval (RFC3339) |
-| interval_end | string | yes | End time of interval (RFC3339) |
-| neid | string[] | yes | Named Entity ID(s) in the neighborhood |
-| numBuckets | integer | no | Number of time buckets |
-
-#### Responses
-
-| Status | Description |
-|--------|-------------|
-| 200 | Bucketed mention counts (`GetMentionCountsResponse`) |
-| 400 | Invalid parameters (`Error`) |
-| 500 | Internal server error (`Error`) |
-
-#### Example
-
-**Request:**
-
-```
-GET /mentions/lookup/counts?interval_start=2026-01-15T00:00:00Z&interval_end=2026-01-20T00:00:00Z&neid=00416400910670863867&numBuckets=5
-```
-
-**Response:**
-
-```json
-{"buckets": [{"start": "2026-01-15T00:00:00Z", "width_hours": 24, "count": 51}, {"start": "2026-01-16T00:00:00Z", "width_hours": 24, "count": 28}]}
-```
-
----
-
-### Get mention details for a neighborhood
-
-`GET /mentions/lookup/detail`
-
-Get detailed information about all mentions for entities in a neighborhood within a time interval. Response is cached for 15 minutes.
-
-#### Parameters
-
-| Name | Type | Required | Description |
-|------|------|----------|-------------|
-| interval_start | string | yes | Start time of interval (RFC3339) |
-| interval_end | string | yes | End time of interval (RFC3339) |
-| neid | string[] | yes | Named Entity ID(s) in the neighborhood |
-
-#### Responses
-
-| Status | Description |
-|--------|-------------|
-| 200 | List of mention details (`GetMentionLookupDetailResponse`) |
-| 400 | Invalid parameters (`Error`) |
-| 500 | Internal server error (`Error`) |
-
-#### Example
-
-**Request:**
-
-```
-GET /mentions/lookup/detail?interval_start=2026-01-28T00:00:00Z&interval_end=2026-01-29T00:00:00Z&neid=00416400910670863867
-```
-
-**Response:**
-
-```json
-{"details": [{"neid": "00416400910670863867", "artid": "06794762728091918955", "publication_date": "2026-01-28T14:01:17Z", "snippet": "...stiff competition from other major players such as YouTube and Apple...", "sentiment": 0, "explanation": "Apple is mentioned as a competitor in the music-streaming market...", "topics": [], "trustworthiness": 0.508, "original_publication_name": "Spotify", "tone": "Neutral", "title_factuality": "True", "tone_objectivity_score": 0.563, "title_factuality_score": 3.889, "events": ["06942391178010057368"]}]}
-```
-
----
-
-### Get mention detail
-
-`GET /mentions/{mcode}/detail`
-
-Get detailed information about a specific mention by its MCODE. Response is cached for 15 minutes.
-
-#### Guidance
-
-Response is wrapped in a 'detail' container object. Access mention data via response.detail.
-
-#### Parameters
-
-| Name | Type | Required | Description |
-|------|------|----------|-------------|
-| mcode | string | yes | Mention code in format NEID:ARTID |
-
-#### Responses
-
-| Status | Description |
-|--------|-------------|
-| 200 | Mention detail (`GetMentionDetailResponse`) |
-| 400 | Invalid MCODE format (`Error`) |
-| 404 | Mention not found (`Error`) |
-| 500 | Internal server error (`Error`) |
-
-#### Example
-
-**Request:**
-
-```
-GET /mentions/00416400910670863867:05433395856363393596/detail
-```
-
-**Response:**
-
-```json
-{"detail": {"neid": "00416400910670863867", "artid": "05433395856363393596", "publication_date": "2026-01-28T15:56:47Z", "snippet": "Apple CEO Tim Cook said he was 'heartbroken'...", "sentiment": -0.75, "explanation": "CEO Tim Cook expressed heartbreak...", "topics": [], "trustworthiness": 0.664, "original_publication_name": "CNBC", "tone": "neutral", "title_factuality": "accurate", "tone_objectivity_score": 0.533, "title_factuality_score": 7.133, "events": ["07189853443333370710", "07880710486873721498"]}}
-```
-
-## Types
-
-### ArticleDetail
-
-The article detail
-
-| Field | Type | Description |
-|-------|------|-------------|
-| artid | string | Article ID |
-| batch | string | Processing batch identifier |
-| events | string[] | Event IDs mentioned in this article |
-| mentions | `Mcode`[] | List of entity mentions in article |
-| moz_rank_score | number | Publisher's Moz rank value (0 to 1) @Minimum 0 @Maximum 1 |
-| original_publication_name | string | Original publication name when known (e.g., when article is syndicated) |
-| page_rank_score | number | Publisher's page rank value (0 to 1) @Minimum 0 @Maximum 1 |
-| publication_date | string | Publication date of the article @Format date-time |
-| publication_home_url | string | Home URL of the publication in which the article was published @Format uri |
-| publication_name | string | Name of the publication in which the article was published |
-| source | string | Article source identifier |
-| summary | string | Article summary |
-| syndication_score | integer | Syndication score indicating article distribution |
-| title | string | Article title |
-| title_factuality | string | Article title factuality classification |
-| title_factuality_score | number | Publisher's title factuality score (0 to 1) @Minimum 0 @Maximum 1 |
-| tone | string | Article tone classification |
-| tone_objectivity_score | number | Publisher's tone objectivity score (0 to 1) @Minimum 0 @Maximum 1 |
-| topics | `ArticleTopic`[] | Topics associated with this article |
-| trustworthiness | number | Trustworthiness score (0 to 1) @Minimum 0 @Maximum 1 |
-| url | string | Original article URL @Format uri |
-
-### GetArticleResponse
-
-Response containing detailed information about an article
-
-| Field | Type | Description |
-|-------|------|-------------|
-| detail | `ArticleDetail` |  |
-
-### GetMentionCountsResponse
-
-Response containing bucketed mention counts over time
-
-| Field | Type | Description |
-|-------|------|-------------|
-| buckets | `Bucket`[] | Time buckets with mention counts |
-
-### GetMentionDetailResponse
-
-Response containing detailed information about a mention
-
-| Field | Type | Description |
-|-------|------|-------------|
-| detail | `MentionDetail` |  |
-
-### GetMentionLookupDetailResponse
-
-Response containing detailed information about multiple mentions
-
-| Field | Type | Description |
-|-------|------|-------------|
-| details | `MentionDetail`[] | List of mention details |
-
-### GetMentionsResponse
-
-Response containing mention codes for a lookup query
-
-| Field | Type | Description |
-|-------|------|-------------|
-| mcodes | `Mcode`[] | List of mention codes (NEID, ARTID pairs) |
-
-### Mcode
-
-A tuple of (NEID, ARTID) representing one or more mentions of a Named Entity in an Article
-
-| Field | Type | Description |
-|-------|------|-------------|
-| artid | string | Article ID |
-| neid | string | Named Entity ID |
-
-### MentionDetail
-
-The mention detail
-
-| Field | Type | Description |
-|-------|------|-------------|
-| artid | string | Article ID |
-| events | string[] | Event IDs that this mention is associated with |
-| explanation | string | Explanation of sentiment analysis |
-| moz_rank_score | number | Publisher's Moz rank value (0 to 1) @Minimum 0 @Maximum 1 |
-| neid | string | Named Entity ID |
-| original_publication_name | string | Original publication name when known (e.g., when article is syndicated) |
-| other_neid | string | NEID of the other entity in a relationship mention |
-| other_relation_type | string | Type of relationship with the other entity |
-| page_rank_score | number | Publisher's page rank value (0 to 1) @Minimum 0 @Maximum 1 |
-| publication_date | string | Publication date of the article @Format date-time |
-| sentiment | number | Sentiment score for the mention (-1 to 1) @Minimum -1 @Maximum 1 |
-| snippet | string | Text snippet containing the mention |
-| title_factuality | string | Article title factuality classification |
-| title_factuality_score | number | Publisher's title factuality score (0 to 1) @Minimum 0 @Maximum 1 |
-| tone | string | Article tone classification |
-| tone_objectivity_score | number | Publisher's tone objectivity score (0 to 1) @Minimum 0 @Maximum 1 |
-| topics | `ArticleTopic`[] | Topics associated with the article |
-| trustworthiness | number | Trustworthiness score (0 to 1) @Minimum 0 @Maximum 1 |
-
-<!-- END GENERATED CONTENT -->

package/skills/elemental-api/events.md

@@ -1,145 +0,0 @@
-# Events
-
-Events are significant occurrences involving entities: mergers, acquisitions, lawsuits, executive changes, product launches, and other newsworthy happenings. Events are extracted from article content and link multiple entities and articles together.
-
-## When to Use
-
-- You want to know what happened to/with an entity (not just mentions)
-- You want to see how different articles reference the same event(s), and understand that many articles may duplicate information about the same event(s).
-- You want to see what entities participated in an event, and what their roles were.
-
-## Key Concepts
-
-- **Event ID (EVEID)**: Unique identifier for each event.
-  - Format: 20-character numeric string (same format as NEIDs)
-  - Example: `08640179941787350436`
-- **Event Roles**: Entities participate in events with roles (e.g., acquirer, target, plaintiff)
-- **Event Summary**: Brief description of what occurred
-- **Event Date**: When the event happened (may differ from article publication date)
-
-## Tips
-
-- Multiple articles may reference the same event
-- Check entity roles to understand the nature of involvement
-
-<!-- BEGIN GENERATED CONTENT -->
-
-## Endpoints
-
-### Get events for an entity
-
-`GET /events/lookup`
-
-Get list of event IDs (EVEIDs) where an entity participates within a time interval. Response is cached for 5 minutes.
-
-#### Guidance
-
-Event IDs returned may not all be immediately retrievable via /events/{eveid}. Some events may return 404 due to event processing timing or data availability. Handle 404 responses gracefully.
-
-#### Parameters
-
-| Name | Type | Required | Description |
-|------|------|----------|-------------|
-| interval_start | string | yes | Start time of interval (RFC3339) |
-| interval_end | string | yes | End time of interval (RFC3339) |
-| neid | string | yes | Named Entity ID |
-
-#### Responses
-
-| Status | Description |
-|--------|-------------|
-| 200 | List of event IDs (`GetEventsForEntityResponse`) |
-| 400 | Invalid parameters (`Error`) |
-| 500 | Internal server error (`Error`) |
-
-#### Example
-
-**Request:**
-
-```
-GET /events/lookup?interval_start=2026-01-28T00:00:00Z&interval_end=2026-01-29T00:00:00Z&neid=00416400910670863867
-```
-
-**Response:**
-
-```json
-{"event_ids": ["07880710486873721498", "07189853443333370710", "01188063638449369172"]}
-```
-
----
-
-### Get event detail
-
-`GET /events/{eveid}`
-
-Get detailed information about an event by its ID. Response is cached for 15 minutes.
-
-#### Guidance
-
-Response is wrapped in a 'detail' container object. Access event data via response.detail.
-
-#### Parameters
-
-| Name | Type | Required | Description |
-|------|------|----------|-------------|
-| eveid | string | yes | Event ID |
-
-#### Responses
-
-| Status | Description |
-|--------|-------------|
-| 200 | Event detail (`GetEventResponse`) |
-| 400 | Invalid EVEID (`Error`) |
-| 404 | Event not found (`Error`) |
-| 500 | Internal server error (`Error`) |
-
-#### Example
-
-**Request:**
-
-```
-GET /events/08640179941787350436
-```
-
-**Response:**
-
-```json
-{"detail": {"eveid": "08640179941787350436", "name": "event|Apple plans to release a foldable device...|2026", "date": "2026", "description": "The new design and engineering changes in the iPhone Air could pave the way...", "category": "Product Development", "likelihood": "Medium", "severity": 0, "speculative": false, "participants": [{"neid": "00416400910670863867", "sentiment": 0.5, "explanation": "The launch of new products...", "role": "company", "snippet": "Apple is gearing up for the most extensive refresh...", "artid": "07521758285625650094"}]}}
-```
-
-## Types
-
-### EventDetail
-
-The event detail
-
-| Field | Type | Description |
-|-------|------|-------------|
-| artids | string[] | Article IDs where this event was found |
-| category | string | Category of the event |
-| date | string | Date of the event |
-| description | string | Description of the event |
-| eveid | string | Event ID |
-| likelihood | string | Likelihood assessment of the event |
-| name | string | Name of the event |
-| participants | `EventParticipant`[] | Participants in the event |
-| severity | integer | Severity level of the event |
-| speculative | boolean | Whether the event is speculative |
-
-### GetEventResponse
-
-Response containing detailed information about an event
-
-| Field | Type | Description |
-|-------|------|-------------|
-| detail | `EventDetail` |  |
-
-### GetEventsForEntityResponse
-
-Response containing event IDs for an entity
-
-| Field | Type | Description |
-|-------|------|-------------|
-| event_ids | string[] | List of event IDs |
-
-<!-- END GENERATED CONTENT -->

package/skills/elemental-api/llm.md

@@ -1,18 +0,0 @@
-# LLM (Ada)
-
-Ada is the AI assistant integrated into the Query Server, capable of answering natural language questions about the Knowledge Graph.
-
-## Status: Not Currently Available
-
-⚠️ The LLM/Ada endpoints are currently **excluded** from this skill because they are not functional in the current deployment. This documentation is a placeholder for when the feature becomes available.
-
-## Intended Use Cases (Future)
-
-- Natural language queries about entities ("Tell me about Apple's recent news")
-- Conversational exploration of the Knowledge Graph
-- AI-assisted analysis and summarization
-
-<!-- BEGIN GENERATED CONTENT -->
-
-
-<!-- END GENERATED CONTENT -->