Write a deliverable
Have your agent write the document the project must produce, review it, sign it, export it to Word.
A project ends with a document: a project basis, a use agreement, a geotechnical report, a verification note. The deliverable is that document, kept in the dossier section by section, each section with what it rests on. Your agent writes it from what the dossier knows; you review, correct and sign.
Open the document
Tell your agent, on a dossier you have already named:
draft the project basis
It calls draft_deliverable, which opens the document and hands it the plan: one section per
chapter, each with what belongs there and what is already written. Asking twice for the same
document on the same dossier returns the same document, never a second one.
You can also open it by hand: the dossier's Livrables tab, Ouvrir un document (open a document), then the kind. There are five:
| Kind | What it is | The default plan comes from |
|---|---|---|
| Project basis | The conditions the design rests on | SIA 260, clause 2.5 |
| Use agreement | What the owner and the engineer agree on | SIA 260, clause 2.2 |
| Geotechnical report | Situation, investigation, model, parameters, foundations, risks | the usage of Swiss reports |
| Verification note | The dossier reviewed question by question | the PDF note the dossier prints |
| Other | A document with a free plan | a single section |
If your organization validated a plan of that kind on the Methods page, the plan is the office's, not Stratta's: its chapters, in its order. See Your organization’s methods. The plan is frozen when the document opens: editing the plan afterwards does not reshuffle a half-written document.
What the agent writes, and what it cannot write
For each section the agent calls write_section with the text and its sources: a decision
or a piece of evidence of the dossier, a fact of the site sheet, a clause it read, a page of an
attachment. A section without a source is not saved. That rule is what makes the document
worth signing: every sentence of substance rests on something the dossier holds.
When the dossier has nothing for a section, the agent marks it to establish, with what is missing and who can supply it. It prints as a gap, never as a plausible sentence.
Each section carries one of three states:
- to establish: nothing in the dossier yet;
- current, unmarked: written, with its sources;
- to review: a source changed since (see below).
Review and correct
Livrables tab, then the document. Each section shows its text, its sources, its state. Écrire or Modifier (write, edit) opens the section: the text, the "nothing in the dossier for this section" box, and the sources, picked among the dossier's decisions and evidence and the clauses the agent read, or typed as a clause ("SIA 267 § 9.5.2").
A section you rewrite counts like one the agent rewrote: same sources, same rule.
Put in review, sign
The status selector at the top of the document has three positions:
- Brouillon (draft): being written.
- En revue (in review): to be read by a senior. The document appears under À valider (to validate) on the dossiers home page of the whole organisation.
- Signé (signed): validated, it no longer changes. Only an owner or an admin signs, from the application; an agent cannot. Only an owner or an admin reopens a signed document too, and the history keeps the date of the withdrawn signature. A signed document is neither written nor deleted any more, and only they can delete the dossier that holds it; asking for a new one of the same kind opens another.
Signing does not remove the closing line: the document was prepared by an agent from the dossier, to be validated and signed by the responsible person. Stratta signs nothing.
Export
Exporter (export) at the top of the document, then:
- Word (.docx). If your organization deposited a report on the Methods page, the document comes out inside that report, as if someone had filled it in by hand: theme colours and fonts, styles, headers and footers with the logo, cover page, heading numbering. Each kind of paragraph takes the look of your report: headings, body text, bullets, numbered lists, quotes, captions, and tables in your table style. The cover receives the deliverable's title and date when it has fields for them; a job number Stratta does not know is marked "to establish". The table of contents lists the deliverable's chapters, and Word recomputes its page numbers on opening (accept the field update). Without a deposited report, a plain Word in Heading 1 to 3, which your organization styles itself. The downloaded file is kept for a quarter of an hour only.
- Markdown (.md). The same text, with the "to establish" and "to review" marks in clear, so a search finds them.
Both exports end with the licence of each norm cited, as your copy prints it: watermark and copyright.
A Word export weighs five requests on your quota.
When a source moves
A section knows what it rests on, and keeps note of it. When what it cites moves, it goes to review, with the reason written out:
- a decision retaken or edited ("We retain 30°" replaced by a new decision);
- a piece of evidence or a decision deleted from the dossier;
- a new site survey that changes a cited fact;
- a new edition of a norm that changes a cited clause.
A signed document does not move: what was signed is what was read.
Two gestures bring a section back: rewrite it (you, or the agent, which sees the reason in
draft_deliverable), or Relue, je garde (reviewed, keep it) when the text still holds despite the change.
From your agent, in one conversation
draft the project basis for the Morges hall
The agent reads the project-basis method (yours, if your organization wrote one), opens the
document, writes each section from the decisions, the site facts and the clauses it read, and
hands you the list of gaps. It does not paste the document into the conversation: it is on the
dossier page.
pick the project basis back up, sections to review first