file Card

File Cards

A file card represents an arbitrary file uploaded via the capture UI (e.g. a PDF, text document, spreadsheet, archive).

Frontmatter:

• filename: — the attached file as a {ref, via, ...} object. ref: is the path into the card's attach scope (e.g. attach/{storedName}). via: says how it came into the box: channel (e.g. disk, scan-import, scan-upload/<token>), at (the upload or import timestamp), and optionally original (the date of the original document when known and different from at: YYYY, YYYY-MM, or YYYY-MM-DD) and note (how or why, in prose). Optional siblings of via: original-name (filename as uploaded), mime-type (browser-reported MIME), size (bytes).
• description: — short summary of what the file contains, filled in during processing. Doubles as the contains: fallback for search; set an explicit contains: only when it should differ.

Unlike image/audio cards, no built-in pipeline processes files yet — they land in the capture session and are available for agent handling (extraction into records, archival, etc.). There is no processed marker: what a processor extracts (records, a description:) is the record of its work.

The contains: field

Give this card a one-sentence contains: — the prime retrieval field for bbx search and listings. How to write a good one (carry the information when it's concise, never a list of parts, under 200 characters) is in the agent guide's ABOUT_CARDS section.