← StrattaCONTENT HISTORY

Update to Stratta

Snapshot Oct 24, 2026 · 13:15 UTC · version 1.18.0

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save Stratta and check future changes in Following.

Up to 10 plugins free · no card required.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Write the terrain chapter of a report (situation, geology, groundwater, boreholes, hazards, constraints) from a Stratta site sheet, one sentence per fact with its source and date, register answers kept apart from design values. Trigger phrases: \"chapitre terrain\", \"chapitre situation\", \"decris le site\", \"site chapter\", \"conditions du terrain\".",
  "included_files": [],
  "name": "site-chapter",
  "skill_md_contents": "---\nname: site-chapter\ndescription: Write the terrain chapter of a report (situation, geology, groundwater, boreholes, hazards, constraints) from a Stratta site sheet, one sentence per fact with its source and date, register answers kept apart from design values. Trigger phrases: \"chapitre terrain\", \"chapitre situation\", \"decris le site\", \"site chapter\", \"conditions du terrain\".\n---\n\n# Terrain chapter\n\nUse this skill when the user needs the part of a report that describes the site: the\ngeotechnical report's situation chapter, the terrain chapter of a project basis, the\nsite paragraph of an offer. The site sheet already holds what the public registers say,\nwith a source and a date on each fact; the chapter is that sheet, written in prose,\nwithout adding a single value.\n\nDo not use it to interpret the ground (a retained soil parameter is a decision of the\ndossier, not a fact of the sheet), and do not use it when the dossier has no site: say\nso and offer `scan_site`.\n\n## Before writing\n\n1. `list_skills`: an office version named `site-chapter` replaces this one.\n2. `load_dossier`, then `get_site_context` on its `siteId`. When the chapter needs the\n   boreholes, `get_boreholes` (nearest first; `withStrataOnly` when only logged strata\n   matter).\n\n## What to produce\n\nMarkdown, in the user's language, ordered as the sheet is: situation (address, parcel,\nelevation), geology, boreholes and groundwater, natural hazards, contamination and water\nprotection, other constraints (noise, radon, zoning, forest), actions (seismic zone and\nground class, snow, wind).\n\nOne sentence per fact, then its provenance in brackets: the register that answered, the\ndate of the answer, and the clause when the fact carries one:\n\n- `established`: state it. \"La parcelle repose sur des alluvions recentes (cadastre\n  geologique VD, 2026-09-14).\"\n- `indicative`: state it with the reserve the register itself puts on it, and mark\n  `[A confirmer]`. \"La classe de sol de fondation indiquee par la carte est C, carte non\n  precise a l'echelle de la parcelle (SIA 261 §16.2, p. 51) [A confirmer par sondage].\"\n- `uncovered`: say the register did not answer, in one line, marked `[A etablir]`.\n\nFor boreholes: their number in the radius, the nearest with its distance and depth, how\nmany have logged strata, the measured water levels with their dates. No interpolation\nbetween boreholes: the sheet's cross-section is an interpretation and says so.\n\n## Rules\n\n- A fact of the sheet is a register's answer. It never becomes a design value in this\n  chapter; if the dossier retained one, cite the decision `(#xxxxxx)` in a separate\n  sentence.\n- Keep the date. A fact without its date reads as permanent, and a cadastre changes.\n- Do not complete a missing topic from general knowledge of the region.\n- Do not conclude on the feasibility of the structure.\n\n## After drafting\n\nName the `[A etablir]` and `[A confirmer]` items in one list, with what would settle each\n(a borehole, a cantonal request, a site visit).\n"
}

SHA-256 of public snapshot: c1d5c94095d64a9f65e7364350954fb5fd6ee9873f70391e5854dd5c2bb4a0cc