ps_symbol_create
Create directive symbols in a registry to define structured data entries for companies, people, events, sectors, tasks, knowledge, and queries with specific metadata requirements.
Instructions
Create a new directive symbol in the registry.
Symbol IDs follow the pattern:
Public companies: Ξ.{TICKER}.{PERIOD} (e.g., Ξ.NVDA.Q3FY25)
People: Ξ.I.{NAME}.{CONTEXT} (e.g., Ξ.I.JENSEN_HUANG.BIO)
Events: Ξ.E.{TYPE}.{ID} (e.g., Ξ.E.EARNINGS.NVDA.20241120)
Sectors: Ξ.S.{SECTOR}.{CONTEXT} (e.g., Ξ.S.SEMICONDUCTORS.2024)
Tasks: Ξ.T.{PROJECT}.{ID} (e.g., Ξ.T.PORTFOLIO_REVIEW.001)
Knowledge: Ξ.K.{DOMAIN}.{TOPIC} (e.g., Ξ.K.CHEMISTRY.WATER)
Queries: Ξ.Q.{DATASET}.{ID} (e.g., Ξ.Q.DEEPSEARCHQA.001)
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| symbolId | Yes | Unique symbol ID following namespace rules (e.g., Ξ.NVDA.Q3FY25) | |
| category | No | Category (auto-inferred from ID if not provided) | |
| who | Yes | Who needs this / who is the audience | |
| what | Yes | What is being analyzed or done | |
| why | Yes | Why this matters / purpose | |
| where | Yes | Scope (company, market, geography) | |
| when | Yes | Time context | |
| how | Yes | ||
| commanders_intent | Yes | Ultimate goal in one sentence - the north star | |
| requirements | Yes | MUST include these elements | |
| anti_requirements | No | MUST NOT include these elements | |
| key_terms | No | Terms that MUST appear in output | |
| tags | No | Freeform tags for filtering | |
| parent_symbol | No | Parent symbol ID for hierarchical symbols | |
| related_symbols | No | Related symbol IDs | |
| created_by | No | Creator identifier |