KNOWLEDGE LIBRARY
What the Knowledge Library is
The Knowledge Library is the project memory Typewiser writes from. Whenever the platform generates a section, or the Typewiser Assistant answers a question, it looks here for the facts it needs. Everything Typewiser knows about your project comes from what you put in this library.
Every project has its own library, and the two are inseparable. A file you upload to one project is never used in another. It stays private to that project, visible only to people you have added as collaborators and to users who hold admin rights in your organisation.
A single file in the library is a knowledge document. It can be almost anything relevant to the proposal: the call text, a project concept note, a technical report, an earlier proposal, partner descriptions, a budget, a publication, a market study.
The quality of what Typewiser writes depends on the quality, the relevance and the structure of what you upload. A thin library does not block you. If information is missing, Typewiser still generates text and does the best it can with the project context available. It simply has less to work with, so the draft comes back more generic. The more you provide, the closer the output is to what you want to say.
How Typewiser uses knowledge libraries
Typewiser reads the library in advance, section by section, to work out whether it has what each one needs.
Knowledge validation
Every section of a proposal template carries a set of concepts: the specific pieces of information that section has to cover. Knowledge validation is the check Typewiser runs to see whether those concepts appear anywhere in your uploaded documents.
This is the first thing Typewiser does when you start a new project and it runs a validation again every time the library changes, so the context stays updated as you add material during drafting. While the check is running, the status icon shows a ☕ steaming cup. That means Typewiser is reading and evaluating your library. Wait for it to settle before you judge the result.
Reading the result
When validation finishes, Typewiser leaves a comment against each section telling you what it found. There are two outcomes.
- Green. Typewiser found the concepts the section needs. You can go ahead and generate with confidence.
- Red. Some concepts are missing, and the comment lists exactly which ones.
A red comment is a recommendation to improve the knowledge library. You have three ways forward:
- Upload knowledge documents that cover the missing concepts.
- Run an interview, where the Typewiser Assistant asks you targeted questions and saves your answers into the library as new knowledge.
- Generate anyway, then fill the gaps by hand. Typewiser writes the section with whatever it has.
Treat the list of missing concepts as your shopping list for the next upload. It is the most precise instruction you will ever get about what your library is short of, because it comes from the template itself rather than from your own guesswork.
How to add knowledge documents
There are three main routes to add knowledge documents in Typewiser.
- When you create a project. Typewiser asks you to build the library straight away. Select Choose files and pick the files from your computer.
- From a knowledge library comment. While you are working in the editor, every knowledge library comment carries a library icon 📚. Select it to add documents without leaving the section.
- From the tool bar. The knowledge library is always accessible by clicking the 📚 icon on the tool bar, at the top right side corner of the Typewiser editor.
What happens after you upload
Typewiser runs File Validation before it reads anything. This confirms that each file can be processed and reports every one as validated or not. Once the files pass, the upload completes and knowledge validation begins on the new material.
What knowledge documents should be uploaded?
Different parts of a proposal call for different evidence. The quickest way to decide what your library is missing is to look at the section you are about to write.
| If you are working on | Material that tends to help |
|---|---|
| Excellence or significance | Scientific background notes, literature reviews, state of the art analysis, technical white papers, proof of concept summaries, patent landscapes, extracts from publications |
| Impact | Market analysis, customer interview summaries, business plan, policy alignment notes, sustainability analysis, competitor analysis, commercialisation plan |
| Approach or implementation | Work package overviews, methodology descriptions, Gantt notes, descriptions of the team, partners and stakeholders, descriptions of facilities and other resources |
These are examples, not a required list. Different templates and different calls ask for different things.
It makes no difference whether the information sits in one large document or is spread across twenty small ones. Typewiser reads the whole library and searches it for the concepts each section needs. Organise the files in whichever way is easiest for you to keep up to date.
Typewiser supports common text and audio formats. The upload dialog states this at the point where you choose your files.
How to manage the knowledge library
Treat the library as a curated source of truth, not a dump folder. Every document you add becomes part of what Typewiser believes about your project. An outdated description of a project's objectives does not sit harmlessly next to the current one, it competes with it. A noisy library produces generic or inconsistent text. This is the most common reason for disappointing output, and it is almost always fixable.
| Upload | Avoid |
|---|---|
| The latest version of a document | Information that has since been superseded |
| The clearest version, written to be understood | Messy notes with no context around them |
| The most factual version, with figures and evidence | Contradictory versions of the same fact |
| The most structured version | Material unrelated to this proposal |
Review material before you upload it
Check that the content really carries the message you want the section to make. Part of a document is often better than the whole of it. If you need one method from a twenty page paper, upload that method and the introduction, not the full paper. The full paper brings in a great deal of material that has nothing to do with your proposal, and Typewiser has no way of knowing which pages you meant.
Build the library in stages
Start with a small core set of high value documents, enough to draft the main narrative sections. A clear project concept note is the single most useful knowledge document you can provide, because it guides the whole proposal. Expand the library with more specialised material as particular sections ask for it.
Building in stages has a second benefit. When you add documents a few at a time, you can see which ones changed the output, and you learn what this template actually responds to.
Review the output, then improve the library
The library is not a setup task you finish before writing. Draft a few sections, read them, and look for text that is weak, too generic, or thin on support. Then add or replace knowledge documents and generate again.
The weakness in the text usually tells you what is missing:
- If the innovation sounds vague, the library needs more technical detail or more state of the art evidence.
- If the commercial impact sounds broad, it needs more market or stakeholder evidence.
- If the approach feels thin, it needs more detailed implementation material.