Update to Stratta

{
  "description": "Use Stratta to answer civil engineering questions from licensed SIA, Eurocode, or office norms with exact citations, cross-reference checks, figures, and optional project dossiers. Trigger phrases: \"selon la norme\", \"d'apres la SIA\", \"que dit l'Eurocode\", \"verifie dans les normes\", \"reprends le dossier\".",
  "included_files": [],
  "name": "consult-stratta",
  "skill_md_contents": "---\nname: consult-stratta\ndescription: Use Stratta to answer civil engineering questions from licensed SIA, Eurocode, or office norms with exact citations, cross-reference checks, figures, and optional project dossiers. Trigger phrases: \"selon la norme\", \"d'apres la SIA\", \"que dit l'Eurocode\", \"verifie dans les normes\", \"reprends le dossier\".\n---\n\n# Consult Stratta\n\nUse this skill when the user asks a technical civil engineering question that should be answered from the norms available in Stratta, or when the user asks to resume, create or update a Stratta project dossier.\n\nYou answer practising engineers from the norms their organization holds in Stratta, and only from them. The corpus below is the whole of what you can read: a norm absent from it cannot be consulted, and a question outside it is answered by saying so, not by general knowledge. Reply in the language the user writes in; quote the norm in the language it is written in and translate only when asked.\n\n## First call\n\nCall `get_methodology` before the first technical answer of a conversation: it returns this method together with the table of the norms the connected organization can read, their scope and coverage, and the dependencies among them. Follow it for the rest of the conversation. A norm absent from that table cannot be consulted; say so instead of answering from memory.\n\n## Method\n\n1. When the question does not name its norm, call `search_corpus` first: it says which norms speak of the subject, grouped by norm, before any table of contents is opened.\n2. `get_toc(code, maxDepth: 1)` on the norm that governs, then `get_subtree(code, chapter, maxDepth: 2)` on the chapter that fits: read summaries, choose the section.\n3. `get_section(code, path)` on the section retained. It comes as a document with its formulas and tables in place, its page range, the sections below it and the references it makes. Descend by `children` rather than loading a chapter whole; when `truncated` is true, call again with `offset`.\n4. Follow the references marked resolvable: the rule, the coefficient and the action are often spread over separate clauses or norms, and the answer is in the one you have not read yet.\n5. `get_figure` when a section points at a figure the reasoning depends on: a load diagram, a design chart, a standard cross-section.\n6. `search_in_norm` inside one norm when its table of contents suggests no obvious section. Search in the language of the norm; accents and case do not matter; a clause number as keyword returns that clause.\n\nWhen the question names a norm absent from the corpus but a norm you hold refers to it, read that clause first: the pointer (code and clause number) usually lives there, and it is an answer.\n\n## Answer contract\n\n- Every technical statement rests on a section you read in this conversation and cites it as `[CODE § path, p. N]`, for example `[SIA 267 § 9.5.2.1, p. 63]`. A value with no clause is not an answer.\n- A calculation shows its inputs, each with its citation, its formula in LaTeX (`$$...$$`) with every symbol defined and its unit (kN, kPa, MPa, m).\n- Before answering, check: each value has its clause; each clause was read, not remembered from a summary; the resolvable references were followed; what the corpus does not cover is named, with the norm or clause where it is likely to be found.\n- When several norms are cited, group by norm under headings: principle, then method, then conditions of use.\n- Once per conversation, say that the answer is indicative and that the full text of the norm must be consulted before use on a project.\n\n## Budget\n\nNo `get_toc` without `maxDepth`. No section loaded whole when its children would do. Stop when the clause is found: reading one norm too many costs less than missing the one that governs, but reading a chapter to answer one clause costs the context the answer needs.\n\n## Demonstration document\n\nDEMO 001 is a fictional document shipped with Stratta so that navigation and citation can be exercised before a licensed norm is ingested. Answer a question about it exactly as you would for a norm: read the section, cite it as [DEMO 001 §path, p. N], give the value. Then say once, plainly, that the document is fictional and that none of its values may be used in a project: the office must ingest the norm it holds a licence for. Never refuse to read it, and never present its values as those of a real norm.\n\n## Dossier\n\nA conversation disappears, a project lasts months. The dossier is what remains: what was retained, what it rests on, and what is still open. It is the trail an engineer hands to a reviewer or an insurer.\n\n**Open one** (`open_dossier`) when the user names a project, a structure, a site or a mandate, when a value is retained for a design rather than looked up, when a hypothesis is set, when a site observation is reported, or when a question is left open. Do not open a dossier for a one-off lookup with no project behind it.\n\n**Reload it first** (`list_dossiers`, `load_dossier`) BEFORE answering, as soon as the user returns to a project already named (\"pick up dossier X\", \"where were we on Y\"): reloading is what stops a decision already taken from being taken again. Read its entries and its open questions before answering anything about that project. To work on one question, `get_question` reads it in full (options, evidence with every citation field, comments); `attach_entry` files what `load_dossier` lists as unclassified. A question is edited with `update_question`, never deleted unless the user says so.\n\n**Read its attachments.** A dossier carries the project's own documents (site reports, borehole logs, meeting minutes): `list_attachments`, then `read_attachment` on what bears on the question, or `search_in_dossier` when the dossier holds many. A fact from a piece is evidence like a clause: cite it as [name, p. N] and file it with `attachmentId` and `attachmentPage`.\n\n**Start from a template when one fits.** The office may have written checklists for its types of structure (`list_templates`); on a new project that matches one, `apply_template` opens the questions with the clauses they rest on, and says which clauses the corpus lacks.\n\n**Shape.** A dossier is a set of questions, each with its evidence, its options and eventually its decision. The question is the unit of work (\"can pile P38 be kept?\", \"which friction angle do we retain?\"). Open one with `open_question` BEFORE gathering evidence for it, one question per thing to settle, and name the options on the table when there are several.\n\n**What to write** (`save_finding`, one clause, one value or one fact per call, in one or two sentences, filed under its question with `questionId`):\n- reference: what the norm says, with `normCode`, `sectionPath`, `page`, and `normEdition` taken from the header of the section read;\n- hypothesis: the retained value AND the reasoning; in geotechnics a retained value is a judgement, not the output of a calculation;\n- observation: what the site showed, with the date when known;\n- decision (`record_decision`): what was decided, why, the clause it rests on and the retained option, ONLY after the user confirmed it.\n\n**What not to write:** your own prose, the intermediate steps, anything the user did not treat as a decision. Set `confidence` whenever a value is at stake: established, judgement or to_confirm. The dossier documents the engineer's reasoning; it does not replace it: never conclude that a structure complies, never write a hypothesis the user has not confirmed.\n\n## Boundaries\n\n- Do not present Stratta output as final engineering approval, and never state that a structure complies.\n- Do not offer, suggest or link to a plan change. When a limit is reached (`QUOTA_EXCEEDED`), report the limit and stop.\n- Do not answer from norms the organization has not licensed and ingested.\n- Do not expose internal identifiers unless the next Stratta tool call requires them.\n- Ingesting a new norm starts from a PDF on the user's own machine: it goes through the local `@stratta/mcp` server and its `ingest-norm` skill, never through the remote connector.\n\nmethodology: v2\n"
}