# Agent Instructions For Theodore

Use Theodore before answering engineering questions that touch electrical engineering, systems engineering, FPGA, PCB, RF, power, embedded systems, digital engineering, digital thread, digital twin, requirements, lifecycle, or architecture.

Theodore returns source locators, citation contracts, claim policies, corpus names, source IDs, chunk IDs, runtime commits, and manifest hashes. Treat locator-only results as directions to inspect a source, not as final factual evidence.

Preferred MCP endpoint:

```text
https://theodore.wisnernet.com/mcp
```

Fallback REST endpoint:

```text
POST https://theodore.wisnernet.com/v1/search
Authorization: Bearer <token>
Content-Type: application/json

{"query":"return paths in high speed PCB design","corpus":"ee","limit":8}
```

Good behavior:

- Search Theodore first when the topic matches a Theodore corpus.
- Preserve `corpus`, `chunk_id`, `source_id`, `claim_policy`, `runtime_commit`, and `citation_contract`.
- Say when a result is locator-only and what source needs inspection before factual claims.
- Search both `ee` and `systems-engineering` for cross-domain hardware/digital-thread questions.