Fields and relations
Text, number, money, date, select and link fields, plus child tables for lines. A link points to a real record, such as a customer or an order, never to a copied name.
Metadata engine
Builder turns one definition of fields, relations, lifecycle and permissions into a form, a list, an API, an agent tool and a Lens measure. It is configuration inside the product, so upgrades do not break it.
A rental company tracks handovers. A maintenance company tracks site visits. A consultancy tracks permits. Standard software offers two answers: a spreadsheet beside the system, or a custom development project that has to be repaired at every upgrade. Builder is the third answer. You describe the record type once, in the product, and Tosven treats it like one of its own.
The definition holds the fields, the links to other records, the lifecycle and who may read or write what. From it Tosven derives validation, storage, lists with filters, permission checks, the audit trail and the tools an agent may use. Customers, the CRM module, runs on the same engine. Your own types therefore share its database, its permissions and its audit trail from the first record.
Builder
Each type has a state of its own. Drafts can change freely. A published type keeps its field keys and field types for good. Built-in types are maintained by Tosven, and retired types stay readable.
Sample data · record types
Text, number, money, date, select and link fields, plus child tables for lines. A link points to a real record, such as a customer or an order, never to a copied name.
A type is either simple or documentary. Documentary records move from draft to submitted to cancelled, and a submitted record changes only in the fields you allow.
Read, write, delete and approve are granted per type. Row filters and field redaction are applied inside the data layer, so lists, API responses and agent output all obey them.
Every type gets a list with filtering, sorting and paging. One filter language serves lists, display conditions and access rules, and an unknown field is an error, never a silent gap.
Choose a unique id or a series such as SV-{YYYY}-{####}. The number is assigned in the same step that creates the record, from a counter per type and period.
Every change is written to one audit log with the changed fields, the actor and the definition version. Each change also emits an event that other modules can react to.
Described fields become search, read and propose tools for agents. An agent's proposal is a draft that a person submits. Tools for deleting or for changing permissions are never generated.
Mark a field as indexed or unique and Tosven builds the index at publish time. Existing duplicates are reported before the rule applies, with the rows that cause them.
Definitions are published as versions. Adding a field takes effect at once. Tightening a rule first runs a scan of existing records and shows what would break.
In practice
Jonas Berg wants site visits recorded against customers and orders, not in a shared spreadsheet.
After three months the team wants a mandatory meter reading on every site visit.
Sanna Lind asks in the shared customer room for a follow-up visit at Nordlys AB.
Sample data
In most systems a new record type means a table, a screen, an endpoint, a permission matrix and a report, written separately and kept in step by hand. In Builder all of them are compiled from the same definition and cached by its version number. When the definition changes, everything derived from it changes in the same step.
Each field carries one of four classes: public, internal, restricted or secret. That single flag decides who sees the value, whether it appears in default list columns, whether it may feed semantic search, and whether an agent tool may return it. Because redaction happens in the data layer, there is no screen, export or tool that forgets to apply it.
A field with a description becomes part of a tool an agent can call: search, read, propose a new record, propose a change. Links are resolved by search, and a search returns at most fifty rows. Number and money fields are designed to become Lens measures with the same permissions and the same drill to the record. Measures for your own types are on the way.
Custom code breaks because the vendor cannot see it. A Builder definition is data that Tosven reads on every release. A published field key and field type never change silently. Renaming or retyping is an explicit operation. Tosven never deletes a published field of a built-in type. It deprecates the field, reapplies your additions after an upgrade and flags anything left without a home.
In the field · Equipment rental company
An equipment rental company hires out lifts, compressors and site cabins. Its real process is not in any standard module: a unit is reserved, handed over with a checklist and photos, returned, inspected and sometimes charged for damage. In most companies that process lives in paper forms, a shared spreadsheet and the memory of the yard staff, while the invoice is written somewhere else by someone who was not there.
With Builder the company defines four record types: Equipment unit, Rental contract, Handover inspection and Damage report. Each links to the customer in Customers. The yard works from lists filtered by state. A damage report submitted at return carries the unit, the contract and the amount, so whoever prepares the invoice sees the inspection behind the charge. Nothing was programmed, and the next release leaves the types intact.
Works with
Company, person and opportunity are Builder types. Your own types link to them directly.
Governed AI agentsEach described type gives agents search, read and propose tools, inside their manager's permissions.
Analytics and reportingNumber and money fields are designed to become measures that drill back to the record.
Status
No. Builder does not run scripts or custom code. It is a closed set of field kinds, lifecycle models, filters and permissions, the same set Tosven itself is built on. That limit is deliberate. Everything you configure can be validated, secured, audited and carried through an upgrade, which arbitrary code cannot promise.
They stay as they are. A definition is data, not code, and a published field key and field type never change without an explicit operation. Tosven does not delete published fields of built-in types. It marks them deprecated, reapplies your additions after the upgrade and flags anything that no longer has a place.
In the pilot, record types are defined together with the Tosven team and published through the engine, because the editor screen is not released yet. The engine underneath is in use: the Customers module runs on it. The editor, generated form layouts and custom fields on built-in types are listed under what is on the way.
Yes, and they are intentional. A type holds up to 100 custom fields, of which 15 can be indexed. Field keys and field types are fixed once published. These limits keep lists fast and stop a data model from decaying into hundreds of unused fields, a problem that is expensive to repair later.
Yes, within strict bounds. A described type gives agents tools to search, read and propose records. A proposal is a draft that a person submits. No generated tool deletes permanently, changes permissions or changes a definition, and an agent never has more access than its human manager. Ledger agent and Collections agent are the agents in production today.
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.