---
name: use-agreement
description: Draft the use agreement (convention d'utilisation, Nutzungsvereinbarung) required by SIA 260 clause 2.2 from a Stratta dossier, as a document the owner and the engineer sign together, every requirement traced to a decision and every open point left visible. Trigger phrases: "convention d'utilisation", "Nutzungsvereinbarung", "use agreement".
---

# Use agreement (SIA 260 clause 2.2)

Use this skill when the user asks for the use agreement of a structure: the document in
which the owner and the engineer agree on what the structure is for, how long, under
which requirements and with which risks accepted. It is written in the owner's language,
for the owner to read and sign; the engineer keeps the technical basis in the project
basis (`project-basis` skill).

Do not use it to draft the project basis, and do not fill a requirement the owner has
not stated: an open point in this document is a question for the next meeting, not a
default.

## Before writing

1. `list_skills`: an office version named `use-agreement` replaces this one; read it with
   `get_skill` and follow it.
2. `list_dossiers` then `load_dossier`. The decisions that concern use (service life,
   categories of use, loads the owner asked for, tolerances, special risks) are the
   matter; the open questions are the points to raise with the owner.
3. `get_toc("SIA 260", maxDepth: 2)` and read the clause on the use agreement with
   `get_section` when the corpus holds SIA 260; otherwise say so once and keep the plan.

## How to write it

The document lives in Stratta: `draft_deliverable` with the dossier id and
`kind: "use_agreement"` returns the plan (the office template when one was validated)
and the decisions with their ids; then one `write_section` per section, each with its
sources (`{kind: "entry", ref: <entryId>}` for a decision, `{kind: "fact", ref: ...}`
for a site fact). A requirement the owner has not stated is a `write_section` with
`gap: true` and a body that names the point to agree. Tell the user the document is on
the dossier page under Livrables; do not paste it in the conversation.

## The plan

In the user's language, unless the office's own skill says otherwise:

1. **Objet**: the structure and the parties.
2. **Objectifs d'utilisation**: what the structure is for, its service life category,
   the uses foreseen.
3. **Exigences d'utilisation**: the requirements the owner sets (loads, deformations,
   vibrations, appearance, durability), each as one line.
4. **Environnement et conditions**: what the site imposes, in plain words, from the site
   sheet when there is one (`get_site_context`): hazards, groundwater, contamination.
5. **Risques acceptes et mesures**: what the owner accepts and what is done about it.
6. **Points a convenir**: everything above that the dossier does not settle, as a list
   the two parties go through together.

The text is plain prose; the sources go in the `sources` argument. A point to agree is
a gap, printed as such.

## Rules

- Plain language: the owner is not an engineer. Keep clause references for the project
  basis; here, name the norm once in a footnote.
- No requirement invented to look complete. A short agreement with visible gaps is worth
  more than a full one the owner did not agree to.
- Do not conclude on compliance; do not write a decision the user has not confirmed.
- The last section ends with the two signature lines (owner, engineer). Stratta prints
  the closing sentence; the signature is the parties', on paper.

## After drafting

List the points to agree in one table and propose them as questions to open in the
dossier (`open_question`), only if the user says so.