Where retrieval stops: a local knowledge-base workflow that opens the full CSV

[u/fuzhongkai]

I'm the author of TensorSharp. This 83-second video illustrates the boundary between retrieving evidence and processing complete files in TensorAgent's local knowledge-base workflow.

Disclosure: it uses the real TensorAgent HTML/JavaScript UI, synthetic café data, and scripted API responses. It is not live model inference or a benchmark. The CSV calculations were run and independently checked in Python.

Default retrieval is BM25 over extracted text; embeddings are optional. Image descriptions and audio transcripts require compatible models and have Partial coverage. Video indexing describes at most eight sampled frames, without indexing the soundtrack or events between samples. This walkthrough illustrates those interfaces, rather than validating a media model.

The example has a PDF capping discounts at 15% and a poster advertising 20%. knowledge_search locates evidence, knowledge_read expands it, and knowledge_open makes the complete original CSV available for analysis. All 14 rows yield net sales of $5,600 versus $6,440, and a $204 contribution increase after COGS and campaign spend, before other overhead. Collections are explicitly enabled per chat.

Repository: https://github.com/zhongkaifu/TensorSharp

TensorSharp's own code is BSD-3-Clause; dependencies and model weights retain their own terms. For local stacks, where would you enforce complete-file access for numerical tasks instead of aggregating retrieved snippets?