Expert knowledge-source management
The seven management operations are list_knowledge, add_knowledge, upload_knowledge, replace_knowledge, delete_knowledge, reindex_knowledge, and rebuild_knowledge. Every operation verifies that the Action owner owns the Expert. These Actions are unavailable on public surfaces. list_knowledge returns source metadata; the Action intentionally omits the web editor’s legacy compatibility chunk projection from its result.
add_knowledge accepts 1–50,000 text characters. upload_knowledge accepts a File Center fileId, never inline bytes, keeping Action arguments within 64 KiB. Supported files are UTF-8 .txt or .md and valid PDFs, at most 10 MiB and 100,000 extracted characters. A shared-workspace file additionally requires an explicit read grant for the executing Agent. Unsupported, inaccessible, mismatched, or oversized files fail before creating a source.
New and replaced content is safety-scanned. Approved content is chunked and embedded through LlmGateway; when the provider is unavailable, add may store a degraded source according to the canonical service policy. Replacement creates a new immutable source version. reindex_knowledge regenerates one source index. delete_knowledge and full rebuild_knowledge require UserConfirm + Strict because they remove or bulk-rewrite runtime knowledge. Do not claim success until the Action result reports the resulting scan and index state.
Related actions
Section titled “Related actions”arinova.expert.list_knowledge, arinova.expert.add_knowledge, arinova.expert.upload_knowledge, arinova.expert.replace_knowledge, arinova.expert.delete_knowledge, arinova.expert.reindex_knowledge, arinova.expert.rebuild_knowledge, arinova.expert.*
Also known as
Expert knowledge base, Expert source, upload Expert PDF, reindex Expert, rebuild Expert knowledge, File Center Expert knowledge
Build a7f47a5ca54ddcf7806cd48b81ce1b9827042766