Which version applies?
The template changed in March. The agreement went out in February. Nobody can answer without opening the file.
Every agreement is built from versioned clauses and typed fields. What gets signed is structured data — searchable, traceable, and linked to the obligations it creates.
§4 Ersättning
Signaturer
Åtaganden
The problem
The template changed in March. The agreement went out in February. Nobody can answer without opening the file.
“Which agreements have notice longer than three months?” means someone has to read them. Full-text search finds the word, not the term.
The agreement says three posts. Nothing says anything when they do not arrive.
Template, clause, field, intake, signature, obligation. The same data all the way through.
01
The identity is slug plus version. Publishing v3 never touches v2 — agreements already sent keep pointing at their own text.
02
Negotiation happens by picking among pre-approved variants, not by rewriting text. Who may pick is set per clause.
03
An amount is SEK, a share is a percentage, a point in time is a date.
04
A single-use link to a form. Every field maps to a variable — nothing lands in free text.
05
Anyone can start. Only a registered statutory signatory can conclude the agreement. The power of attorney is itself an agreement in the system.
06
Fulfilment is attested by a person, never by the system. Every attestation lands in a log that can only grow.
Lifecycle
Personal data is physically separated and read through a single function. Every access is logged in the same transaction — they cannot come apart.