--- id: context.sdk.lark-resources kind: procedure mediaType: text/markdown --- # Lark Resource Materialization Lark documents can contain evidence that is not present in the readable text body. Context handles these resources mechanically during `captureLark`; the Agent does not download, summarize, or reconstruct them itself. ## Resource policy | Resource | Default capture behavior | |---|---| | Image and attachment | Download the original file and link it from the Markdown projection. | | Sheet | Read the complete selected sheet, render a Markdown table, and retain a CSV snapshot. | | Base | Read the selected table/view with pagination, render a Markdown table, and retain a canonical JSON snapshot. | | Whiteboard and diagram | Retain a readable preview plus the raw structured export. | | Synced block | Resolve the exact source block, project its body, and retain a Markdown evidence snapshot. | | Poll | Preserve exported options and metadata as non-interactive Markdown; warn when the export omits them. | | Bookmark, citation, sub-document, chat, and generic embed | Preserve a stable navigation reference and provenance. | | Video | Preserve a stable reference by default; download only when `resources.videos` is `bundle`. | Required inline resources fail closed when their stable identity, bytes, or complete structured data cannot be obtained. When the remote API explicitly confirms that a referenced whiteboard or diagram no longer exists, Context preserves an unavailable-resource notice with the reason code `document.resource.source-missing`, reports a warning, and continues capture; it does not pretend that the deleted content was materialized. When the current identity can read the document body but the API explicitly returns `authorization/permission_denied` for an embedded resource, Context records `document.resource.permission-denied`, keeps the stable resource identity in the audit layer, renders the same unavailable-resource notice, and continues with a warning. Missing scopes, transient network errors, malformed payloads, and unclassified authorization failures still block capture. Reference-only resources remain explicit in the capture report. Unknown non-empty XML blocks stay auditable in the raw XML and receive a warning; the CLI does not infer their meaning. Document and resource reads share one access identity. Context first uses the user identity; it falls back to the bot identity only when user credentials are unavailable, never when the source denies permission or reports missing scopes. This prevents a capture from mixing document text read by one identity with attachments read by another. A bot fallback is reported in the capture result and remains subject to the bot's own access boundary. ## Storage lifecycle Resources have three distinct locations: ```text sources/lark// ├── .md ├── manifest.json └── assets// ├── source.xml ├── capture-report.json └── materialized/** knowledge/assets//. dist//others/assets//. ``` - `sources/` is the captured source and audit layer. `source.xml` preserves the structured source, one `capture-report.json` closes fidelity and resource handling for the document, and `materialized/` contains downloaded files and structured exports. Resource descriptors are consolidated in the report; capture does not create one metadata file per embedded resource. - The date-level `manifest.json` is a compact inventory. It records hashes, asset roles, the report path, and status summaries without duplicating the complete report. - `knowledge/assets/` contains only resources referenced by approved pages. Paths are content-addressed, so identical bytes are reused and changed bytes produce a new identity. Review apply rewrites page links mechanically; verification compares the underlying content identity, so this deterministic path projection does not count as a change to a verbatim section. Markdown files below `knowledge/assets/` remain evidence resources and are never interpreted as approved knowledge pages or structure views. - `others/assets/` is the portable package projection. Build copies only resources referenced by selected package pages and rewrites their relative links. Audit-only source files are not distributed. Deleting an approved page allows unreferenced `knowledge/assets` files to be cleaned. A missing approved or packaged resource is a verification error rather than a silent broken link. Source assets are part of the reproducible evidence snapshot and should not be ignored when the workspace is versioned. Repositories with many binary source assets can use Git LFS for `materialized/` while keeping Markdown, XML, JSON, and CSV directly reviewable in Git. The workspace must remain private when the captured source or screenshots are access-controlled. ## SDK configuration Defaults are suitable for ordinary documents: ```ts captureLark({ source: handbook }); ``` Projects can opt into bundled video and adjust deterministic byte limits: ```ts captureLark({ source: handbook, resources: { videos: "bundle", maxBytesPerResource: 20 * 1024 * 1024, maxTotalBytes: 200 * 1024 * 1024, }, }); ``` The limits are capture constraints, not semantic filters. Context does not decide which resources are important from their business content. ## Agent behavior Use the capture command returned by the current Route. Inspect the structured resource summary and fidelity diagnostics; do not manually edit `sources/`, `knowledge/assets/`, or package links. Required materialization failures other than a confirmed source-side deletion or an explicit resource-level permission denial must be resolved by recapturing after access or source problems are fixed. Accepted failures remain visible as warnings and unavailable-resource notices; they are never represented as downloaded evidence. Review shows available previews, references, and warnings so the human or managed policy can assess the page with its non-text evidence.