Knowledge System

Storage and readability

Confirm the file is accepted, then check whether its contents can be extracted or otherwise supplied in a supported form. An attachment badge alone does not prove readability.

Retrieval and task context

The relevant material must be selected and delivered to the task. Ask a narrow, verifiable question to check whether an answer actually uses the source.

Scoped memory

Memory Notes provide global, organization, project, folder, and conversation scopes. Do not assume every note or document belongs in every task.

Source authority

Keep provenance and revision in view. Generated summaries are aids to understanding; original evidence and operator authority remain controlling.

Make source use observable

Give the source a meaningful name and identify the section you want reviewed. Ask for a short quotation or precise passage reference, then check it against the original. If Friday cannot access the contents, supply a supported excerpt or ask your operator about processing. Do not ask it to fill gaps by guessing.

Ask Friday to guide you

In an authorized FridayLocalAI conversation, try:

Use only the attached document if its contents are available to you. Identify the document, summarize the section about [topic], and point to the supporting passage. If the content is unavailable, say so and help me check the attachment workflow.

Tell Friday what you can see and which step you have reached. If the instructions do not match your screen, say so; ask for the relevant Help topic or contact your operator. Friday cannot be assumed to see your screen or know your current settings.

Identify the question and its source

Knowledge work begins with a question and the material needed to answer it. A source may be a document, an excerpt, or information you type into the conversation. Identify the relevant source clearly and describe which part matters. Asking a narrow question first helps establish whether the response is grounded in the material you intended. For example, ask for the date under a particular heading or the difference between two stated requirements. Check the answer against the original. This is more informative than requesting a broad summary whose wording could have been generated from general background knowledge. Once source access is established for the relevant content, you can ask for a more substantial explanation or comparison with clearer expectations.

Storage is only one stage

An accepted upload means the application received material through a storage path. It does not, by itself, prove the model received readable contents. Different formats can require extraction, image handling, or another supported process. A preview that works in the browser may not establish the same access for the response workflow. Watch the available status and ask a checkable source question. If the content is unavailable, state that limitation rather than accepting a guessed answer. A small supported text sample can help isolate whether the problem is general or format-specific. Avoid repeatedly uploading private material without understanding the earlier result. Work with the operator when the source needs a different approved processing path.

Retrieval and relevance are separate questions

Material can be stored and readable without every part being relevant to every task. A useful response needs the appropriate context for the question. Identify the section, topic, or comparison you want rather than expecting an unlimited review of all stored information. Large or mixed source collections make it especially important to define the scope. Ask for references that let you inspect the supporting material. If the response cites the wrong section or omits a necessary source, correct the task context before continuing. Do not infer that the application has globally searched every document merely because an answer is confident. Context preparation is bounded by the available mechanisms and policies, and the user still needs evidence that the relevant material informed the result.

Memory serves a different purpose

Memory Notes can preserve guidance or information in an applicable scope, while documents remain sources to consult for their contents. A writing preference belongs to a different category of context from a technical specification. Keeping the distinction clear makes it easier to update guidance without confusing it with the original evidence behind a factual claim. Use the narrowest suitable scope for a note and verify the saved record. If a note summarizes a source, preserve enough provenance to understand its origin and limits. Do not allow a shortened memory entry to silently replace a detailed source when the distinction matters. A response may need both reusable guidance and a current source, and neither one grants permission to access unrelated information.

Review synthesis as well as quotation

A response can quote a passage accurately and still draw an unsupported conclusion from it. When asking Friday to compare or synthesize sources, request a distinction between what each source says, what follows directly, and what is interpretation. Check the important steps in the reasoning, especially when the sources differ or leave a question unanswered. For a practical exercise, provide two short descriptions and ask for agreements, differences, and unresolved questions. Review whether each comparison is supported. If one source is outdated, explain that context and ask how it affects the result. This develops a more useful knowledge workflow than treating every generated summary as a final authority simply because it includes a source reference.

Keep the workflow within its intended boundary

Source material can contain instructions written for another purpose. Those instructions do not automatically become commands from you to the application. State whether you want a summary, extraction, comparison, or explanation, and separate that request from the text being analyzed. An attached document is not permission to change files, contact services, or expand access. If the task involves proprietary information, confirm the processing and access arrangement with the operator. Private AI requires concrete handling decisions rather than assumptions based on a label. Preserve original sources and review important claims against them. FridayLocalAI is most useful as a knowledge workspace when it helps you organize questions, identify evidence, and make the remaining uncertainty visible instead of replacing that discipline with fluent but unverified text.