Knowledge
Wiki pages with live data blocks, owners and review dates, agent edits under signature and a share link for customers.
Knowledge is the wiki of Tosven. It sits on the same records as Ledger, Customers and Builder, so a page can show a current figure and notice when the data it cites has changed. This page covers pages, live blocks, freshness, agent edits, sharing with a customer, and search.
Pages and versions
A page is built from blocks: headings, paragraphs, bulleted and numbered lists, checklists, tables, code, quotes, dividers and links. You add a block from a menu that opens when you type a slash.
- A version on every save. Each save stores a version of the page.
- No silent merge. If two people edit the same page, the second save is stopped and shows who saved first and when. You choose between your version and the saved one.
- Export. When you export a page, live values are frozen with their date and your name.
Images cannot be uploaded to pages yet, and there is no screen for browsing earlier versions, although every version is stored. On the way
Live blocks
A live block stores a question and a caption, never a result. The value is fetched each time the page is opened, under the rights of the person reading it.
| Block | What it shows |
|---|---|
| Record card | Title, number and status of one record |
| Customer balance | Overdue, not yet due and net open amounts |
| Record list | Up to 20 rows of a record type, through a saved filter |
| Measure | A Lens figure or table, with its state and as-of time |
- The caption is required. Search finds the block by its caption.
- Per reader. A reader without access sees "no access" and the kind of block. They never see a zero or another reader's figure.
A Lens board is a Knowledge page whose measures are live blocks. See Lens.
Freshness and verification
Every page has an owner, who verifies it until a date they choose. Readers then see a Verified badge with the date and the owner's name, or nothing.
Nobody marks a page stale by hand. Tosven derives it from two facts:
- Cited data changed. The data behind a live block is different from what it was when the page was last verified.
- Review date passed. The verified-until date is in the past.
The warning is shown only to people who can edit the page, and it names its evidence. A daily check opens at most one review card per page and reason. Signing that card creates a task for the page owner. There are two ways out: verify the page again, or edit it.
Sample data: Sara Nyström posts a credit note against INV-2026-0418 for Nordlys AB. The next day Laura Virtanen, who owns the Nordlys AB account plan, gets one review card. The live block already shows the new balance. She corrects the paragraph beside it and verifies the page until 31.01.2027.
Tosven does not judge whether your prose contradicts the data. A page without live blocks relies on its review date.
Agent edits under signature
An agent can propose an update to a page as a decision card that shows the difference.
- A person signs. Nothing is written until a person with edit rights on the page signs the card. The edit is recorded under that person, with the card reference.
- Stale on change. If the page changes before the card is signed, the proposal is voided and nothing is written.
- Always reviewed. Agents cannot edit pages on their own and have no tool for deleting them.
Agents also read Knowledge before they act, under their manager's permissions. Every retrieval is logged, and an agent takes figures from the system, never from page text. See Agents.
Share a page with a customer
In the pilot the customer portal is a single-page share link, opened without an account.
Check the content
A page can be shared only when it is published and all of its content is cleared for external readers.
Freeze live blocks
Publishing refuses a page that contains live blocks and lists them. Remove each one or freeze it. Freezing turns the block into static text stamped with the value, the date and your name.
Share the link
Send the link to your contact. Access is checked on every view.
Unpublish to end access
Unpublishing revokes every share link in the same step.
On the shared page, internal links become plain text and author details are removed. The shared view cannot read live data, and it has no comments, search or navigation.
On the way
A multi-page customer portal with sign-in, and customer answers drawn only from published pages with citations, are planned.
Search
Search combines exact word matching with meaning-based matching and merges the two rankings.
- Permission first. Results are filtered by what you may open before they are ranked, and checked again before they are shown. A title you may not open never appears.
- Citations. A result points to the page and the block it came from.
- Sensitive pages. Pages above the sensitivity threshold are not indexed for meaning.
Meaning-based search on a production provider with reranking, and one search across pages and channel messages, are on the way. On the way
Next steps
- Lens: the measures you can place on a page as live blocks.
- Builder: record types that appear in pages as lists and cards.
- Decisions and approvals: how a proposed page edit is signed.