Dossier tools

A conversation disappears, a project runs for months. These twenty-five tools let your agent write down what was retained into a dossier you reopen, annotate and export from stratta.ch/dossiers, and read and do everything the dossier page can read and do to a question.

You don't call them by hand. Your agent does, while it works, following the policy described in get_methodology.

---

What a dossier holds#

A dossier is a set of questions to settle, for example "Can pile P38 be kept?" or "Which φ'k do we retain for the fill?". The question, not the standalone entry, is the unit of work: it is what gets assigned, reviewed and closed.

A piece of evidence can be recorded before you even know which question it serves: it stays "unclassified", and you file it later from the app. Three kinds of evidence, and the distinction is not decoration:

In structural work a retained value is the output of a formula and recomputing it settles any argument. In geotechnics it is a judgement made between three boreholes that disagree, and the only thing reviewable six months later is the reasoning. Hence confidence:

• established: computed, or read directly from the norm
• judgement: chosen by you between several possible values
• to_confirm: provisional, needs a test or a check

Confusing the three is the professional fault this field exists to prevent.

---

list_dossiers#

Lists your organisation's dossiers, most recently touched first. Each row carries the entry count and, more importantly, the count of open questions, which is what points at the dossier to pick up.

No parameters.

---

open_dossier#

Opens a project's dossier, creating it if it does not exist yet.

Returns { dossierId, created }.

---

open_question#

Opens one question to settle in a dossier, before gathering evidence for it. A question is the unit of work: "Can pile P38 be kept?", "Which φ'k do we retain for the fill?". Evidence saved with save_finding and the eventual record_decision hang off it.

One question per thing to settle: never put a list of sub-questions in the body. A question that bundles eight cannot be assigned, answered or closed one at a time. Open eight questions.

Returns { questionId, created }.

---

list_attachments#

Lists the project attachments of a dossier (site reports, borehole logs, meeting minutes, data sheets), with their extraction status. An agent reads them before answering on a project.

---

read_attachment#

Reads the text of an attachment as a Markdown document, page by page, in windows.

---

search_in_dossier#

Full-text search over the attachments of one dossier, accents and case ignored.

---

list_templates#

Lists the dossier templates of the organization: checklists by type of structure, each a set of questions with the clauses they rest on. No parameter.

---

apply_template#

Opens the questions of a template in a dossier, with their options, and files every clause that resolves in the corpus as a reference entry under its question. A clause the organization cannot read is written into the question body as something to establish. Applying twice opens nothing twice.

---

draft_deliverable#

Opens the document a dossier produces (project basis, use agreement, geotechnical report, verification note, other) and returns its plan: one section per chapter, with its path, its title, a hint of what belongs there, its state (gap, current, stale, with the reason when a source moved) and an excerpt of what is already written. The plan is the office plan validated for that kind when there is one (Methods page), otherwise the one Stratta proposes. Also returns the decisions of the dossier with their ids, so write_section can cite them, and the site when there is one. Calling it twice on the same dossier and kind returns the same document, never a second one.

---

write_section#

Writes one section of the document: the text as it will be printed, and what it rests on. Every sentence of substance comes from a source the section lists: a decision or piece of evidence of the dossier (entry, the entry id), a site fact (fact, the fact key such as groundwater.level), a clause read (clause, "SIA 267 s. 9.5.2"), a page of an attachment (attachment, the id followed by #p12), a reading (reading). A section without a source is refused; when the dossier holds nothing for it, gap true and a body that says what is missing: the section is printed as something to establish. Replaces what the section held. A signed document is not written. When a source moves afterwards (a decision retaken, an entry deleted, a rescan of the site, a new edition), the section goes stale with the reason; rewriting it, or keeping it from the dossier page, brings it back.

---

save_finding#

Records one piece of evidence in a dossier. Your agent calls it as it works, not in a batch at the end: evidence saved when it is found carries the reasoning that produced it.

---

record_decision#

Records what you retained: the decision in one line, why, and the clause it rests on. Two ways to name the question: questionId when it already exists, or dossierId and question (what is settled, in one line) and the question is opened already decided, in the same call. The question leaves the open items and keeps its evidence; the decision becomes the entry a reviewer reads first.

Your agent only calls this once you have confirmed the decision, never on its own reasoning.

Returns { entryId }.

---

load_dossier#

Reloads everything a dossier holds: its questions with their evidence, options and decisions, then the evidence not yet filed under a question, then the comments. Open questions come first, read them before anything else and tell the user what is still open. Long texts are cut (an entry detail at 280 characters, a question body at 480): get_question gives them whole.

Just say "pick the Villa Morges dossier back up": your agent calls this before answering anything about the project, and builds on what was decided instead of deciding it again.

One of the two is required.

---

resolve_question#

Closes a question that stopped mattering without a decision: the variant was abandoned, the client withdrew the request, the point became moot. The question stays in the dossier, marked closed, with its evidence. To settle a question with an answer, call record_decision instead.

---

Reading one question at a time#

load_dossier is the resume: the whole dossier, shaped small, open questions first. It is the right first call and the wrong only call. What the dossier page shows and it does not: who a question is assigned to and by when, the ids an agent needs to act on an option or an entry, an entry's citation field by field rather than as one line, the comments with their author, the history. The next four tools serve that, one page at a time: when nextCursor is present, call the tool again with its value as cursor.

list_questions#

The questions of a dossier, with their status, assignee, due date, options (each with its id) and the title of the decision when there is one. The body is cut at 240 characters; get_question gives it whole.

get_question#

One question in full: its wording, status, options with their description, its decision, its evidence with every citation field (normCode, sectionPath, page, normEdition, attachmentId, attachmentPage) and the option each piece argues for, and the comments left on the question and on those entries, each with its author. Call it before adding anything to a question, so nothing is filed twice.

get_dossier_activity#

The history of a dossier, most recent first: who did what and when, from the app or from an agent, each line with the question or the entry it concerns.

list_exports#

The verification notes and journals exported from a dossier, with their SHA-256 hash, the trusted timestamp when one was obtained and the methodology version in force. The file is downloaded from the dossier page; the tool says a note exists and lets you check a hash you were sent.

---

Acting on a question#

Everything the dossier page can do to a question, your agent can do too, when you ask for it. Two of these tools are irreversible: delete_question and delete_option ask for your confirmation through the client before touching anything, like record_decision.

update_question#

Rewords a question, rewrites what is at stake, assigns it to a member of the organisation by e-mail address, or sets its due date. Only the fields given change; null clears the assignee or the due date. Status goes through record_decision and resolve_question.

add_option#

Adds one way of settling the question, when a variant comes up after it was opened. Idempotent on the name: the same words return the option already listed. Ten options per question at most. Returns { optionId, created }.

update_option#

Renames or describes an option, or marks it retained. Retaining one releases the others: a choice has one answer. Retaining here does not settle the question; record_decision does, and names the retained option itself.

delete_option#

Removes an option from a question. The evidence filed under it stays on the question. Irreversible: your confirmation is asked through the client, unless confirmed is true because you already gave it in the conversation.

delete_question#

Deletes a question from a dossier. Its evidence stays in the dossier, unfiled; its options, its comments and its decision go with it. A question that stopped mattering is closed with resolve_question; only a question opened by mistake is deleted, and only when you say so. Your confirmation is asked through the client.

add_comment#

Leaves a remark on the dossier, on a question or on an entry: a doubt about a value, a note for a colleague, the reason a piece of evidence was set aside. A comment is signed by the connected user and is not evidence: what the norm says goes through save_finding. A signed-off dossier still takes comments.

update_entry#

Corrects a piece of evidence or a decision in place: its wording, its value, its confidence, or the citation when the wrong clause was cited. Only the fields given change; page: null clears the page. The kind and the question do not change here.

attach_entry#

Files a piece of evidence under a question, and optionally under one of its options, or takes it out with questionId: null. This is how the "unclassified" pile of load_dossier empties: read it, find the question it answers, file it. A decision cannot be moved: it belongs to its question.

---

Limits#

To bound a looping agent, without any of it being billed:

A signed-off dossier takes no further entries or edits. Comments stay open: closing a dossier is not the end of the conversation about it.

---

What Stratta does not do#

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