Track a project

You ask your agent fifteen questions, you get fifteen cited answers, you close the tab. The next day, on the same project, it all has to be done again.

The dossier is what remains. Your agent writes down what was retained while it works; you reopen it at stratta.ch/dossiers to review, annotate, sign off and export.

Open a dossier#

Just tell your agent:

open a dossier for Villa Morges, roof

It creates one, then records each question and each decision as the work goes. You can also create one by hand from the Dossiers page if you would rather start there.

What goes in it#

A dossier fills itself while you work. What your agent reads for the project is noted on its own (Readings), and what you retain is recorded in one gesture (Decisions), with the clause that justifies it. A question is opened only when something is left to settle: it then gathers evidence, names options, and ends with a decision that keeps its proof.

Every value carries a confidence: established, judgement, or to confirm. A computed settlement and a friction angle chosen between three boreholes are not read the same way.

What a dossier looks like#

One question, as it fills up over a real job. A four-storey building on fill, uneven boreholes.

Question: which friction angle to retain for the fill on the north side?

Options: 32° (S2), 28° (S4), 30° (weighted low value). Decision: 30°, retained on 14.03, on SIA 267 § 6.3.

What the dossier makes possible: a reader sees why 30° and not 32°, and where the value rests. Two months later the extra test comes back, the evidence is added, the confidence moves to Established, and the decision stays traced.

A dossier picked up six months later by a colleague reads the other way round: what matters is not what was decided, it is what was not. The questions still to settle open the list, the bar at the top of the dossier says how many remain, and every value marked "to confirm" is flagged as such.

Read the dossier#

A dossier page has four tabs, in working order: Terrain, Readings, Decisions and Deliverables. The history opens in a side panel from the header.

• Terrain: the project's workshop. The map on top, with its tools (select, section, earthworks footprint), its information bar (situation, terrain, constraints, actions, boreholes, site photos), the cross-section, the 3D block, then the sheet read top to bottom and, at the bottom, the project's Documents (see below).
• Readings: what your agent read for this dossier, norm by norm, with the page and the time. Nothing there is filed by anyone: once you have named the project to your agent, every section it opens is noted. A reading is not evidence; a click opens the section in the reader.
• Decisions, the working view. The Retain button records a decision in one gesture, without opening a question first. On the left, the questions grouped to settle, decided, closed, each with what backs it or the decision taken. On the right, the chosen question in reading order: its state, what is at stake, who follows it and by when, the decision or the Trancher (decide) button, the options, the evidence, the remarks. The ↑ ↓ keys move from one to the next. Past eight questions, a search appears.
• Deliverables: the documents the project must produce, section by section, each with what it rests on. Project basis, use agreement, geotechnical report, verification note. Your agent writes them, you review, sign and export to Word. The guide Write a deliverable covers it.
• Historique (the panel): what happened, day by day, agent and application alike. What a reviewer reads before signing off. Generated verification notes and the replies received through a read link are listed there.

Which clause serves which question is read from the clause itself, in the norm reader ("Cité par", "Vos dossiers"), or under each piece of evidence ("aussi cité dans").

Evidence the agent recorded without a question is folded under the list, in À classer; the menu of a piece of evidence files it under a question in one click.

Read the norm text#

Click the title of a piece of evidence that cites an article: the section unfolds from your own corpus without leaving the dossier. The text, with its symbols and formulas typeset as the norm prints them, its numbered formulas, its tables.

Everything you are about to reuse copies in one click: the retained value, the citation ("SIA 267 § 6.3, p. 28"), the LaTeX of a formula, every cell of a table. The copy icon appears under the pointer, and stays visible on a phone.

That is what separates a verifiable answer from a trusted one. Opening a PDF and finding page 42 takes three seconds nobody takes; the text next to the citation does not.

Attach the project documents#

A dossier also holds the project's own documents: the site report, the borehole log, the meeting minutes, a supplier's data sheet. Open the Documents section of the Terrain tab and add them (PDF, Word, Excel, images, plain text; 25 MB per file, 20 per dossier). Stratta extracts the text page by page, and the agent reads it with read_attachment, searches it with search_in_dossier, and cites a page like a clause: "PV du 14.08.2026, p. 3". A scanned PDF without a text layer is flagged as such: run it through OCR first.

From the local server, an agent can also upload a file you name with add_attachment.

Resume a project#

This is where the dossier earns its place:

pick the Villa Morges dossier back up

Your agent reloads the questions with their evidence, options and decision, and above all what is still open. It builds on what was decided instead of deciding it again.

Get it reviewed#

A second person checking the first one's work is a quality requirement, and it is the one part an agent cannot do.

1. Move the dossier to En revue (in review) from the status selector at the top of the page.
2. Your colleague leaves a remark on a specific piece of evidence, on a question, or on the dossier from the Historique panel.
3. Once you agree, move it to Visé (signed off). The name and date stay attached.

A signed-off dossier takes no further edits to questions or evidence. Remarks stay open.

Share for reading#

An external reviewer, the client, an insurer: people who need to read what was decided and what it rests on, without an account.

1. In the dossier's ⋯ menu, pick Lien de lecture (read link).
2. Say who it is for, and a duration: 7, 30 or 90 days.
3. Copy the link right away: it is shown once.

The page shows the questions, their options, the evidence with its citation and the decisions. It shows neither the remarks, nor the attachments, nor the exports, and lets nothing be edited. The guest can however reply: a name, a message, the question it is about when there is one. The reply lands in the dossier's Historique panel, signed with the name given; it retains nothing on your behalf. The link is revoked from the same dialog; an expired, revoked or made-up link answers the same thing: "invalid link". Details in Share and reply.

The Monday digest#

Every Monday morning, one e-mail per person: the open questions assigned to you or living in a dossier you opened, the decisions taken during the week, and the norm editions that changed on a clause cited by a dossier in progress. Nothing is sent when there is nothing to say. Turn it off under Réglages › Profil (Settings › Profile).

Export#

In the dossier's ⋯ menu, Exporter en Markdown produces a file structured by question: what is at stake, the options, the evidence with its citations, the decision, the remarks; the questions still to settle first.

It pastes into Word with its structure intact, and it is the record of which article justified which value, on which date: what you show an insurer or a colleague taking the file over.

The document the project must produce is exported from the Deliverables tab: to Word, in the layout of the report your organization deposited on the Methods page (header, logo, styles and cover kept), or to Markdown. See Write a deliverable.

Checklists by type of structure#

A retaining wall, a pile foundation, a slope: the questions are the same from one project to the next, and so are the clauses. Save a dossier that went well as a template (its ⋯ menu, Enregistrer comme gabarit: questions, options and cited clauses, without the values), or write one from Gabarits (templates), at the top of the Dossiers page, one question per line with an optional clause after a pipe. A new dossier can start from a template: its questions open with the clauses that resolve in your corpus filed as references, and the ones your corpus lacks written as gaps. An agent does the same with list_templates and apply_template.

The plan learned from a report is something else: a Word report your organization considers good, deposited with Déposer un rapport (upload a report) on the Methods page. Stratta learns its plan, its standing mentions and its wording; you review, you validate (Valider ce plan), and it becomes a method your agent reads with get_skill before writing a document of that kind. See Your organization’s methods.

The verification note#

The verification note is one of the kinds of deliverable the agent writes (see Write a deliverable). It also exists in a shorter form, rendered in one click from the dossier.

In the same ⋯ menu, Note de vérification renders the dossier as a PDF for a reviewer: one section per question (context, requirement, evidence, decision, what is still open), each paragraph ending with the identifier of the entry it rests on, every gap written as a gap, and an annex quoting the clauses cited, each with its norm's licence. The footer carries the SHA-256 of the file and the time a public timestamp authority (RFC 3161) saw that hash; the token is kept so the timestamp can be checked offline. Timestamped is not signed: the note is to be validated and signed by the responsible person. Generated notes are listed in the Historique panel with their hash.

An agent can draft the same note in the conversation with the verification-note skill of the local server; the two should agree line by line.

What Stratta does not do#

The dossier documents your reasoning; it does not replace it. Stratta never concludes that a structure is compliant, and your agent should not write down an assumption you have not validated.