The office library
The procedures your agent follows, yours and Stratta’s, and the template learned from a Word report.
An office has a way of doing things: its report plan, its standing mentions, its wording, how it instructs a type of structure. The Bibliothèque (library) is where that way of doing things is written once, so your agent reads it before every task of the same kind. It lives at stratta.ch/bibliotheque.
What a procedure is
A procedure is a short text, in Markdown, that tells the agent what to do and when: the steps,
the rules, what it must deliver. Your agent reads it with get_skill before drafting a document
or starting a repeatable task, after finding it with list_skills.
Stratta ships nine, shown under Procédures Stratta (Stratta procedures):
| Procedure | What it has the agent do |
|---|---|
consult-stratta | Read a norm in order, cite, keep the dossier |
project-basis | Draft the project basis (SIA 260 clause 2.5) from the dossier and the site |
use-agreement | Draft the use agreement (SIA 260 clause 2.2) |
site-chapter | Write the terrain chapter of a report from the site sheet |
instruct-structure | Instruct a type of structure: the questions to open, the clauses |
review-open-questions | Prepare a review: what is still open, by whom, by when |
verification-note | Draft the verification note in the conversation |
handoff-to-word | Format a text drafted outside a deliverable for Word |
ingest-norm | Ingest a norm from its PDF |
Write an office procedure
- In the Library, Nouvelle procédure (new procedure); or Adapter (adapt) on a Stratta procedure to start from its text.
- A name (lowercase, digits and hyphens:
geotechnical-report), a one-sentence description (what the procedure does and when to follow it: that is what decides whether the agent picks it), the text. - Save.
An office procedure that carries the name of a Stratta procedure replaces it for your
organisation: write project-basis with your plan, and it is yours the agent follows. Only
owners and admins write; every member and every agent reads.
A procedure is a text the agent reads every time. Say what it must do, in order, and what it must not do; an example beats an adjective.
Learn a template from a Word report
Rather than writing your report plan by hand, deposit a report the office considers good.
- In the Library, Apprendre d’un rapport (learn from a report), then a
.docxfile. The chapters must use Word's Heading styles (Heading 1, Heading 2): that is what Stratta reads. - Stratta proposes a template: the title, the kind of document, the language, the plan (one line per chapter, with a hint of what belongs there), the standing mentions (liability, validity, signature), the wording that carries a retained value.
- Review, correct, Valider (validate). Nothing is served before that.
A validated template is an office procedure like any other: list_skills lists it, get_skill
reads it, and it replaces the Stratta procedure of the same name. It gives its plan to the
deliverables of its kind, and its file lays out all your Word exports (header, logo, footer,
styles, cover kept; see Write a deliverable).
The file stays in your workspace, readable by your organisation only, and goes with the template when you delete it.
What the agent sees
list_skills
returns the office procedures first, then the Stratta ones that are not replaced. The method
served by get_methodology asks it to call list_skills before drafting a document or starting
a repeatable task, then get_skill on the one that fits.