Skip to main content
This guide takes one authoritative document through the complete Source-to-Knowledge path.

​
Goal

At the end, your Project will have:
  • the original document preserved as a Source;
  • one or more reviewed Knowledge pages;
  • provenance that links important claims back to the Source;
  • a cited chat answer that verifies the result.
The example uses a customer renewal policy.

​
1. Prepare the document

Choose the document that people currently treat as authoritative. Before uploading it:
  • remove obsolete drafts from the batch;
  • make the title and effective date visible;
  • include the owner of the policy;
  • check that tables and scanned pages are readable;
  • separate unrelated policies when possible.
Do not combine a current policy and an old replacement draft without clearly labeling both.

​
2. Upload to Sources

Open Knowledge → Sources and upload the file. Cromo accepts Source files up to 50 MB. You can upload supported documents, spreadsheets, presentations, text formats, and images. Watch the Source status. Processing converts the file, extracts useful facts, and prepares candidate Knowledge. A failed upload can be retried after correcting the file.

​
3. Inspect the Source

Open the Source preview and confirm:
  • the correct file was uploaded;
  • pages and sections are readable;
  • the title and origin are accurate;
  • no sensitive content entered the wrong Project.
If the Source is wrong, fix it before approving derived Knowledge.

​
4. Review the proposal

Open Knowledge → Review. Select the proposed page or update. For a renewal policy, pay particular attention to:
  • notice periods;
  • monetary thresholds;
  • responsible roles;
  • approval requirements;
  • exceptions;
  • effective dates.
Open each important provenance reference. If a statement is unsupported or merges two different rules, edit or reject it.
A fluent summary is not evidence of correctness. Approve the content only after checking the underlying Source references.

​
5. Publish and connect

After approval, open the page in Knowledge → Pages. Improve the page for future readers:
  • use a clear title;
  • add headings for standard path, exceptions, and ownership;
  • link related customer, contract, or escalation concepts;
  • preserve the Source references;
  • remove duplicated wording that could drift.
Use Graph to confirm the page connects to the expected concepts.

​
6. Verify in chat

Open Chat in Ask mode and ask a question that requires the new page:
For an enterprise renewal worth €150,000, when must the review start, who owns the commercial proposal, and what evidence is required? Cite the policy.
Open the citations. Compare the answer with the Knowledge page and original Source. If the answer is incomplete, determine which layer needs work:
  • missing evidence → add or replace a Source;
  • unclear explanation → edit the Knowledge page;
  • missing structured records → create a Data model and table;
  • inconsistent procedure → update the process and create a Skill.

​
7. Maintain trust

When the policy changes:
  1. add the new authoritative Source;
  2. review the proposed Knowledge update;
  3. check Skills and Workflows that use the policy;
  4. test cited questions again;
  5. remove obsolete Sources only after confirming no required Knowledge depends on them.

​
Review checklist

  • The Source belongs in this Project.
  • The document is current and readable.
  • Dates, thresholds, owners, and exceptions are accurate.
  • Important claims have provenance.
  • The Knowledge page stands on its own.
  • A cited chat question returns the expected answer.
  • Dependent Skills and Workflows were checked.