Skip to content
Willder

Willder documentation

Your first useful answer.

Bring one document and one question your team needs to answer. A launch plan or decision note is a good place to start.

Before you start

You need access to a Willder workspace and permission to write to the scope you choose. Ask your workspace administrator if you cannot upload or see the right scope.

1Choose where the knowledge belongs

Open Memory and select the scope for your project or team. A scope determines where information belongs and who can access it. Use a project scope for project knowledge.

Keep your question specific: “What launch date did we agree on for Project Atlas, and what is still undecided?”

2Add the source

Choose Upload and select a PDF, DOCX, image or text file. Start with a short, current document that names the project and records the decision clearly.

Uploads enter a processing queue. An accepted upload may take time to appear in memory. If the first search is empty, allow processing to finish before trying again.

3Ask in the same scope

Use the Ask view in Memory. Name the project and ask for one decision, owner or deadline. If the answer is incomplete, narrow the question and check that the right source was uploaded to the selected scope.

Try this in Memory → Ask
What launch date did we agree on for [project name]?
Summarize the decision, the owner and anything still undecided.
Include the supporting facts and source details available. If the evidence is missing or conflicting, say so.

4Check before you act

  • Compare names, dates and decisions with the original document.
  • Inspect any supporting facts and source details the answer provides.
  • Treat missing evidence or conflicting facts as a reason to ask the owner.
  • Keep human review for decisions that affect customers, money or access.

An answer is useful when your team can verify it. Retrieval can miss information; a confident answer alone is not proof.

Use it in your workflow

Try the same question through an external agent using hosted MCP. Start with a read token. Add write access only when the workflow needs to save new knowledge.