Tosven is in pilot. Early access conversations are open for the first companies. Apply

Wiki and portal

Documentation that knows when it is out of date

Knowledge is a wiki where a page can carry live figures and lists from the system itself. Each page has an owner, flags itself when its source changes, and can be shared with a customer as a filtered view.

4
kinds of live block: card, balance, list, measure
2
reasons a page flags itself to its owner
1
human signature on every agent edit
0
copied figures stored inside a live page

A wiki on the same database as the work it describes

Read the documentation

A separate wiki goes stale the day it is written. The procedure names a price that has changed, the customer page quotes a balance from last quarter, and nobody knows which pages can still be trusted. Knowledge sits on the same database as the ledger, the customer records and the record types you define. A page can therefore show the current figure itself, and can notice when the data it cites has moved.

Every page has an owner and a review date. When the date passes, or when the data behind a live block changes, the page is flagged to its owner with the reason. Readers see a Verified badge with a date and a name, or nothing. The same pages are what agents read before they act, and a page can be published to a customer through a link that shows only what is meant for them.

Knowledge

Every page shows whether it can be trusted

The page list groups pages by their state. Verified pages carry a date and an owner. Pages whose review date has passed or whose cited data has changed wait for their owner, and published pages show who can see them.

Sample data · page list, Kaarna Group

What Knowledge does

01

Pages with live data

Embed a record card, a customer's open balance, a filtered list of records or a Lens measure in a page. The block stores the query, so the page always shows the current value.

02

Resolved for each reader

A live block is computed under the rights of the person reading the page. Someone without access sees No access in its place, never a zero and never another reader's cached figure.

03

Stale detection

A page flags itself when the data it cites has changed since it was last verified, or when its review date has passed. The flag names its evidence and goes to the page owner.

04

Verified badges

The owner confirms a page until a chosen date. Readers see Verified with the date and the name. The warning itself is shown only to people who can edit the page.

05

Agent edits under signature

An agent can propose a change to a page as a decision card showing the difference. Nothing is written until a person with edit rights signs, and the edit is recorded under that person.

06

A filtered view for customers

Publish a page to a customer through a share link. Only content cleared for external readers is served, live blocks are frozen to a dated value first, and unpublishing ends access at once.

07

Hybrid search

Search combines exact word matching with meaning-based matching and merges the two rankings. Results are filtered by permission before they are ranked, so a title you may not open never appears.

08

The knowledge base agents read

Agents retrieve from the same pages, under their manager's permissions, and every retrieval is logged. Sensitive pages are excluded, and an agent takes figures from the system, never from page text.

09

Versions on every save

Each save writes a version in the same transaction. If two people edit one page, the second save is stopped with the name and time of the first, and nothing is merged silently.

In practice

Three pages, followed through a working day

01

A page notices its source has changed

An account plan cites a customer's open balance, and a credit note changes that balance.

  1. 09:10Sara NyströmPosts a credit note against invoice INV-2026-0418 for Nordlys AB.
  2. Next dayLaura VirtanenReceives one review card for the account plan: cited data changed · Customer balance.
  3. 08:20Laura VirtanenOpens the page. The live block already shows the new balance, the text beside it does not.
  4. 08:26Laura VirtanenCorrects the paragraph and saves. A new version is written with her name.
  5. 08:27Laura VirtanenVerifies the page until 31.01.2027. Readers see Verified · 15.10.2026 · Laura Virtanen.
02

An agent proposes an edit, a person signs it

The reminder procedure is out of step with how reminders are now sent, and an agent drafts the correction.

  1. 07:40Collections agentProposes an update to the page Payment reminder procedure, with the difference shown.
  2. 08:05Jonas BergEdits another paragraph of the same page and saves before the card is reviewed.
  3. 08:06Collections agentThe card is marked out of date because the page changed. Nothing was written.
  4. 08:30Collections agentProposes the update again, based on the current version of the page.
  5. 08:45Elina KoskinenReads the difference and signs. The page is saved under her name with the card reference.
03

A page is shared with a customer

Operations wants the customer to read the agreed service terms without sending a file by email.

  1. 13:00Jonas BergChooses Share page on Service terms · Nordlys AB.
  2. 13:00Jonas BergPublishing is refused: the page contains one live block, which is named in the message.
  3. 13:02Jonas BergFreezes the block. It becomes static text stamped with the value, date and his name.
  4. 13:03Jonas BergPublishes and sends the link to Sanna Lind at Nordlys AB.
  5. 13:40Sanna LindOpens the link and reads the page. Internal links and author details are not shown.

Sample data

Live blocks

A page stores the question, the system supplies the answer

A live block holds a query and a caption, never a result. When the page is opened the block is resolved for that reader through the same gated readers the rest of Tosven uses. The caption is mandatory, because it is what search finds. There is no shared cache between readers, so one person's figure cannot reach another.

  • 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 Builder type through a saved filter
  • Measure: a Lens figure or table with its state and as-of time
Freshness

Staleness is derived from facts, not set by hand

Nobody ticks a box to mark a page stale. Tosven compares the data behind each live block with what it was when the page was last verified, and checks the review date. A daily check opens at most one review card per page and reason. Signing the card creates a task for the owner. There are two ways out: verify or edit.

  • Reason one: cited data changed since the last verification
  • Reason two: the verified-until date has passed
  • Twenty edits in a day still produce one card, not twenty
  • Pages without an owner have their own list and can be reassigned
Customer portal

What a customer sees is decided by structure, not by care

The portal renderer has no code path that can resolve live data, so an internal figure cannot leak through it. A page can be published only when all of its content is cleared for external readers. The share link is checked on every view. The pilot shares single pages. A multi-page portal with sign-in is on the roadmap.

  • Publishing refuses a page with live blocks and lists them
  • Freezing turns a block into static text with value, date and author
  • Internal links become plain text and authorship details are removed
  • Unpublishing revokes every share link in the same step
Search and agents

One knowledge base for people and for agents

Search runs a word index and a meaning index side by side and merges the ranks. Scope is filtered first and each returned block is checked again against live permissions. Agents use the same retrieval under their manager's rights. A question about a policy goes to Knowledge. A question about an amount goes to Lens, because numbers are never taken from page text.

  • Permission filter before ranking, and a second check on the results
  • Pages above the sensitivity threshold are never indexed for meaning
  • Every retrieval is written to an audit log with the blocks returned
  • Search results cite the page and the block they came from

In the field · Facilities maintenance company

Site instructions that stay in step with the contracts

A facilities maintenance company runs hundreds of sites, each with its own access rules, service levels and contacts. The instructions live in shared folders and a wiki that the office updates when it has time. A technician arrives with last year's key procedure. A customer asks which visits are included, and the answer depends on which file the coordinator opens. When a contract is renewed with new terms, nobody knows which pages still quote the old ones.

In Tosven each site page carries a live list of the open service contracts for that site, defined as a record type in Builder, and the customer's open balance for those allowed to see it. When a contract record changes, the page is flagged to its owner with the reason. Coordinators see a Verified date on every instruction. The agreed service terms are published to the customer as a page, with the values frozen and dated.

With separate tools

  • Site instructions in folders, with no sign of when they were last checked
  • Contract terms copied into the wiki and forgotten when the contract changes
  • Customers receive service terms as an email attachment that soon diverges
  • New coordinators ask colleagues which document is the right one

In Tosven

  • Each instruction shows Verified with a date and the name of its owner
  • The page lists the contracts live and is flagged when one of them changes
  • The customer reads the agreed terms on a shared page with dated values
  • Search returns only what the person may open, with the source block cited

A working day

Sample data
  1. 07:15A coordinator opens the site page for Harju Tekniikka Oy and sees the access procedure, verified until 31.01.2027.
  2. 09:40A contract record is renewed with a new response time. The site page that lists it is flagged to its owner.
  3. 11:10The owner updates the paragraph on response times, saves and verifies the page for another three months.
  4. 13:30Operations freezes the contract list on the service terms page and shares it with the customer's contact.
  5. 15:50A new employee searches for the key handover rules and gets the verified page first, with the paragraph cited.

Status

Where it stands today

Live in pilot
  • Page editor with a version on every save and conflict protection
  • Live blocks: record card, customer balance, record list, Lens measure
  • Stale detection with a review card and a task for the page owner
  • Verified badge with owner and review date
  • Agent page updates as proposals that a person signs
  • Single-page share link for customers, with frozen values
On the way
  • Multi-page customer portal with sign-in
  • Image upload on pages
  • Version history screen
  • Semantic search on a production embedding provider, with reranking
  • Search across pages and channel messages together
  • Customer answers drawn only from published pages, with citations

Frequently asked

Questions and answers

hello@tosven.com

What is a live data block?

It is a part of a page that shows current data from Tosven: one record, a customer's open balance, a filtered list of records or a Lens measure. The page stores only the query and a caption. The value is fetched each time the page is opened, under the rights of the person reading it.

How does a page know it is out of date?

There are two signals. The data behind a live block has changed since the owner last verified the page, or the verified-until date has passed. Both are computed from facts in the database. Tosven does not yet judge whether the prose itself contradicts the data, so a page without live blocks relies on its review date.

Can a customer see internal information through the portal?

The shared view is built so that it cannot. A page is published only if all of its content is cleared for external readers. Live blocks must be frozen to a dated value first, and the portal renderer contains no code that reads live data. Access is checked on every view and ends when the page is unpublished.

Can agents change our documentation on their own?

No. An agent can propose a full new version of a page as a decision card that shows the difference. A person with edit rights must sign it. If the page changed in the meantime, the proposal is voided and nothing is written. Agents have no tool for deleting pages.

What is not available yet?

In the pilot the customer view is a single shared page, not a portal with navigation and sign-in. Images cannot be uploaded to pages, and there is no screen for browsing version history although every version is stored. Search over channel messages and the production embedding provider for semantic search are also on the roadmap.

Early access

Be among the first companies.

Tosven is in pilot. Tell us about your company and the tools you use today in a few sentences, and we will say plainly whether it is a fit.

sales@tosven.com · No card details and no commitment.