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.
Wiki and portal
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.
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
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
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.
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.
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.
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.
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.
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.
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.
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.
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
An account plan cites a customer's open balance, and a credit note changes that balance.
The reminder procedure is out of step with how reminders are now sent, and an agent drafts the correction.
Operations wants the customer to read the agreed service terms without sending a file by email.
Sample data
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.
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.
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.
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.
In the field · Facilities maintenance company
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.
Works with
A Lens board is a Knowledge page. Pinned measures are live blocks that resolve for each reader.
Governed AI agentsAgents read from Knowledge before they act, and propose page updates that a person signs.
Metadata engineRecord types defined in Builder appear in pages as live lists and record cards.
Status
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.
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.
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.
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.
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
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.