Datasheet evidence
The model may suggest a datasheet URL; WireFrame downloads and reads the PDF itself.
/contract U1
Language models are confident about pinouts they have never seen. WireFrame does not take their word for it: the model may only point at a datasheet, WireFrame downloads it, extracts the text and keeps a hash of the file. A link that does not download produces no claim at all.
What it does
Your file first
A datasheet you attach is used before the library index, and the index before the web.
Downloaded, hashed, read
Conclusions cite a PDF WireFrame actually fetched, not a sentence a model wrote.
Made-up links fail safely
An invented URL fails to download, and a failed download concludes nothing.
What an IC needs
/contract U1 extracts what a part requires electrically — supply range, decoupling, pin functions — from its datasheet.
Downloaded, never quoted from memory
Pin functions and electrical limits come from a datasheet WireFrame has actually downloaded. A PDF you attach is used first; then the datasheet link in the published index; then the web, where the model may name a URL but WireFrame downloads the file itself, keeps a hash of it and extracts its text. A link the model made up simply fails to download, and a failed download produces no claim at all.
A contract per part, written once
/contract works out what a part needs around it — supply range, decoupling, pull-ups, strapping pins — from its datasheet and stores the result as the part's contract. Contracts belong to the component, not the project, so a contract written once holds every later board that uses the same part to the same requirements, and /findings and reviews read it.
No evidence, no fault
Requirements backed by a downloaded page can be cited. When no datasheet can be found, the Copilot says so and asks for the PDF. It can still write a draft without one, but every line of that draft is capped so it can never be reported as a fault — a guess is allowed to inform you, not to fail your design.
The details
| Source order | The PDF you attach · the published index · the web, downloaded by WireFrame |
|---|---|
| Kept with each download | The file's hash and its extracted text |
| Commands | /contract <U1> [file.pdf] · /pins [U1] · /fix <U1> … [file.pdf] |
| Scope of a contract | The component — reused on every board that uses it |
| Without a datasheet | A draft whose lines cannot raise a fault |
How to start
- Select a part, or name it in the Copilot.
- Attach the datasheet PDF if you have it; otherwise the Copilot looks for one.
- Read the result with its source next to each clause.
Questions
Is my datasheet uploaded somewhere?
An attached datasheet's content is sent with the request to the AI endpoint you configured. Your projects stay on your computer.
What does /pins change?
Only pin names, on a copy of the symbol in the project library, read from the datasheet. Pin numbers, wiring and the footprint stay as they are.
Why attach a PDF when it can find one?
Many proprietary, renamed and obsolete parts have no datasheet link in the index, and a file you chose is the one document you know is for the exact part number.