Knowledge Base

A knowledge base stores stable information that must be searched and shared repeatedly. The complete path is: create → add sources → check processing → compile knowledge cards → manage members and Wakers → validate in a new chat. Keep one-off requirements in the current task and role rules in the Waker profile or memory. Do not put every type of context into a knowledge base.

​

Open Knowledge Base

Path: left navigation → Capabilities & Resources → Knowledge Base.

The list distinguishes:

• Created by me: you own the knowledge base and can maintain sources, members, and settings.
• Shared with me: another owner granted access; available operations depend on your member permission.
• Featured: a product-provided read-only knowledge base. You can inspect and bind it to a Waker, but cannot edit its sources or cards. Availability depends on region and version.

Use one stable topic per knowledge base, such as “Product Manual” or “Customer Support Policy.” Separate unrelated topics so access, updates, and validation remain manageable.

​

Create a knowledge base

1. Select New Knowledge Base.
2. Enter a title that clearly identifies the topic and scope.
3. Open it and confirm that source, card, member, schedule, and settings entries are available.

Completion check: the knowledge base appears under Created by me, opens successfully, and has the intended title.

​

Use a Featured knowledge base

Featured knowledge bases are ready-to-use public or product knowledge:

1. Open Featured and review its description, scope, and last update.
2. Bind it from the knowledge base or from the target Waker's Knowledge settings.
3. The Waker receives read-only access. You cannot upload sources, edit cards, or manage members in the Featured item.
4. Start a new chat and test one known fact, one boundary case, and one unsupported question.

To add or revise material, create your own knowledge base and import sources you are allowed to use. A missing Featured tab can reflect account, region, version, or feature availability.

​

Add sources

Select Add source. The available source types vary by edition and version and can include local files and URLs.

​

Upload a local file

1. Select a file that meets the format and size requirements shown by the upload dialog.
2. Wait for upload and parsing to finish.
3. Open the source and confirm that its title, body, and pages were extracted correctly.

An uploaded file is not necessarily searchable. Wait until the page no longer reports uploading, processing, or failure.

​

Import a URL

1. Enter a complete https:// or http:// address.
2. Wait while QoderWake retrieves and processes the page.
3. Open the source and confirm that the content is the intended body, not a sign-in, error, or empty page.

Pages that require authentication, are available only on a private network, block retrieval, or depend on complex scripts may fail. When authorized, export the content to a supported file and upload it instead.

​

Organize and maintain sources

Use folders for topic, edition, or product line when the collection grows, but keep the hierarchy shallow. Include a version or effective date in titles when needed.

• Remove obsolete, duplicate, and conflicting versions.
• Identify the authoritative source when several documents describe the same rule.
• Re-upload or update a source when the original changes.
• Recompile and rerun validation questions after replacing or removing material.

​

Understand Sources and Cards

Sources are imported raw materials. Cards are structured knowledge compiled from those materials. A source can upload successfully while the new information is still unavailable for reliable retrieval because compilation has not run. Check both lists. Cards should be readable and should not turn headers, error pages, or duplicate paragraphs into official knowledge.

​

Configure and run compilation

Open Settings from the knowledge base sidebar.

​

Select a template

1. Open Compilation template.
2. Select a template appropriate to the source type and expected use.
3. Add a prompt only when you need to specify the knowledge to extract or exclude. Never include credentials or temporary tasks.

For a coding-standard knowledge base, for example, request cards about the technical stack, engineering rules, and architecture, while excluding recruiting and meeting content.

​

Compile manually

1. Open Compilation settings.
2. Confirm that all sources are complete, then select Start compilation.
3. Wait for completion and review Cards.
4. Compare several cards with their source material.

​

Compile automatically or on a schedule

Use automatic or scheduled compilation for frequently updated sources. Before enabling it, confirm that:

• the frequency will not produce unnecessary repeated work;
• compilation starts only after source processing completes;
• failures have a visible status and retry path.

Automatic compilation produces cards; it does not replace source-quality review or business acceptance.

​

Manage members

Open Members to review the owner and collaborators.

1. Invite only people who need this topic.
2. Grant view, edit, or management access according to responsibility.
3. Remove members when their role changes.
4. Recheck membership before uploading sensitive sources.

Only the owner or a member with management permission can change collaborators. Sharing a knowledge base does not assign it to every Waker.

​

Bind the knowledge base to Wakers

Use the Waker assignment entry in the knowledge-base list, or open a Waker → Knowledge Base.

1. Select only Wakers whose role requires the topic.
2. Confirm that source processing and compilation have completed.
3. Save the assignment.
4. Start a new chat and validate retrieval.

Too many unrelated knowledge bases create retrieval noise and can mix conflicting policies.

​

Validate knowledge

Test at least three question types:

1. A fact that exists: the answer is accurate and the basis can be checked.
2. A boundary or exception: the correct rule is used without mixing another topic.
3. A fact that does not exist: the Waker says the evidence is insufficient instead of inventing an answer.

Use a new chat after binding. Compare the answer with both the original source and compiled card. Completion check: existing facts are accurate and traceable, missing facts are not fabricated, and the same tests still pass after an update and recompile.

​

Update or delete

• Recompile after changing sources and inspect affected cards.
• Before deleting a source, confirm that it is not the only authoritative copy.
• Before deleting a knowledge base, unbind Wakers and check dependent Autonomous Work, Groups, and IM use cases.
• Deleting a knowledge base does not retract earlier replies or clear related chat history.

​

Troubleshooting