Stomra Guides

Stomra · Guide

The Handbook

Your firm's best details and methods, kept on shelves that your AI assistant reads before it models. Show it how you build once, and it starts from that every time.

SHELF Foundations › Slab on ground WORKED EXAMPLE · GRU-07 Slab on ground, edge elements When · Ask first · Measures Recipe · Gone wrong · Done when ★★★★★ model example VARIANT Garage slab Only what differs: thinner insulation, a ramp at the door ★★★★★ DRAWING Edge beam, timber wall above ★★★★★ DRAWING Edge beam, masonry above Not rated yet YOUR ASSISTANT Reads the one that fits best rated first, asks what it asks, follows the recipe, and says so: “following GRU-07”
One shelf of a Handbook. Each example says when it applies, so a slab under a timber wall and one under masonry are two cases, not rivals. People rate them; the assistant is handed the best that fits the task.

Examples, not rules

The Handbook is where your firm keeps how it builds. It is open from Handbook in Stomra and belongs to your organisation: everyone in it reads the same shelves, and every project draws on them.

It holds examples rather than rules. One good detail drawing carries a hundred small decisions that no list of rules spells out: the order of the layers, the overlaps, the sizes, the way it is drawn. When your assistant is handed such an example with a task, the result is far better than when it is handed a rule.

Not the Handbook's job

Stair headroom, U-values, snow loads. The building code and the brief already say them, and repeating them as firm rules only adds noise.

The Handbook's job

The slab-on-ground detail you trust, how you draw an eaves section, the way you lay out a truss plan. Your way of solving things, shown rather than described.

The Handbook never says what the law requires. What your assistant learns from your corrections as you work is kept as lessons learned, which sit beside the Handbook and, once they keep holding, grow into Handbook entries.

What the Handbook holds

KindWhat it isExample
Worked exampleThe whole of how your firm does one thing, written the way a senior shows a junior: when it applies, what to ask first, the measures that govern it, the recipe in Stomra's commands, what has gone wrong before, the senior's own words and how you know it is done. It carries reference details (pictures, a drawing, the types it uses).Slab on ground with edge elements
VariantA special case of a worked example. It says only what differs, and when it applies instead of the main one.Garage slab, as a variant of the slab on ground
Drawing exampleA view as it was drawn, kept as a picture with a short method and its types. A detail's 2D items are kept with it, so it can be inserted again into another project.Eaves section, 400–600 mm overhang
General instructionHow your firm usually builds a building part, in its own words, with a short list of named values. A default that holds wherever no worked example covers the exact case.Slab on ground: L-element along the edge, 3 × 100 mm EPS, mesh #6150
Modelling principleHow a whole model that turned out well was built: the order of work, the types and settings used, what to check at the end. Your assistant starts a similar building from it.A 1.5-storey villa with a timber frame

Every example is a copy. It points to no project: the project can change or be deleted and the example stands, and improving the example never touches the project it came from. Nothing in a Handbook is shared with other organisations.

Shelves and cases

Examples live on shelves. A shelf is a building part and a situation, such as Foundations › Slab on ground or Roofs › Eaves. The building parts follow the way drawings are usually grouped: foundations, frame, floors, walls, roofs, stairs and railings, balconies, building services, electrical, site and more. Your organisation adds its own situations simply by filing an example under them.

A shelf holds cases, not competitors. There is no single best edge beam: the right one depends on the wall above it. So each example says when it applies (“timber frame wall above”, “masonry above”), and two examples for different cases stand side by side, each with its own versions and ratings. Only two versions of the same case ever compete.

The shelf shows its examples in order: one an editor has pinned first, then the rated ones by their score, then the ones nobody has rated yet. This is also the order your assistant is handed them in.

The map. Handbook ▸ Map shows every shelf as a square: no example yet, not rated yet, or has a model example. It turns “sort the Handbook” into something you can answer this week, such as “we have no model foundation plan”.

Adding to the Handbook

Nothing enters the Handbook by itself. An example goes in because a person looked at something good and chose to keep it. There are four ways in.

Right-click a view: Add to the Handbook…

Right-click the tab of a plan, section or detail view, or open a drawing's menu in Review, and choose Add to the Handbook…. A small dialog asks for:

Then choose how it is kept: As this drawing keeps the view as drawn, a drawing example in force at once; As a worked example asks your assistant to write how it is done.

The one question

When the new drawing looks like an example already on the shelf, the dialog asks what it is to that example:

AnswerWhat happens
A new version of itIt will stand in that example's place on the shelf, and competes with it.
Another case of the same kindIt stands beside it, for when something else holds: another wall above, another material.
An example of its ownIt goes on the shelf you choose.

Deciding what is the same is done once, by the person who knows, at the moment they add it.

A 2D family drawn in a project, such as a fixing or a profile, goes in the same way: select it and choose Add to the Handbook… in the Inspector. Your organisation's families are then offered before Stomra's own.

Tell your assistant

Say “this is how we do it: save it in the Handbook”. The assistant writes the example (its shelf, when it applies, the method) and, for a whole way of building, a worked example with every section. It tries a new worked example in an empty trial project that is saved nowhere, so your project list stays clean. What an assistant writes is a draft until an editor publishes it.

When a whole building turned out well, say so: “this came out great, save it as a modelling principle for scissor trusses with a dormer”. The assistant reads the model, writes how it was built, and keeps it as a principle.

Import your own documents

An editor can upload the firm's existing PDFs, such as a design manual, and ask the assistant to read them. It proposes examples one method, convention or tip at a time, with the page each comes from, and leaves out legal requirements. The drafts wait for an editor to read and publish.

Rating and improving

Nothing stays in the Handbook without somebody liking it, and rating takes seconds, never a backlog.

  1. The star. A star in the status bar opens Rate the Handbook: three examples, one at a time, with their drawing, shelf, when they apply and what is good about them. Give one to five stars and, if you like, say what should be better. Skip is always there. You are never shown your own examples, or ones you have rated.
  2. The score. An example rated 4.2 or more by at least two people becomes a model example, marked on its shelf. One rated under 3 by at least three people leaves its shelf for the archive, from which an editor can bring it back. A new example starts in the middle, so a single five does not lift it over one that ten people like.
  3. A comment becomes a repair. “What should be better?” puts the example in the organisation's queue. When asked, a connected assistant takes it, repairs the drawing and hands it back with a line on what it changed.
  4. A person chooses, side by side. The next time the star opens, the old and the new drawing stand beside each other with the comment above them: “Which is better?”. The one chosen lives on; the other goes to the history. A poor repair simply loses, and nothing is worse than before.

Every example keeps its history: who added it, what was said, which repair answered which comment, which of two was chosen and how its score moved.

Four-inch nails. Rating a drawing or choosing between two earns a four-inch nail, up to nine a day. More nails come when your comment's repair wins, when an example you added becomes a model example, and for the first example on an empty shelf. They are worth nothing but the having: a count beside the star and a ranking within your organisation. Now and then, at a calm moment, the star asks for help; you can pause that for a day or a week.

How your assistant uses it

When your assistant starts work on a project, it is told what the Handbook holds: the worked examples and the general instructions. Before it models something a worked example covers, it:

  1. reads the example, and the variant that fits, if one does;
  2. asks what the example says to ask first, or tells you what it assumes;
  3. follows the recipe step by step, with its measures;
  4. checks the example's “done when” rows at the end;
  5. says which example it followed, and for what: “the edge beam following GRU-07, the insulation from the client's section”.

That last line is the receipt. If it picked the wrong example, say so right there; your correction is how the Handbook and the assistant learn. It can also bring an example's types and 2D families into the project, or insert a kept detail into a callout or drafting view, as one Undo step.

Before it models a whole building, the assistant can ask the Handbook for a start prompt: the modelling principles that fit, best rated first, put together as one text to begin from.

Who wins when sources disagree

An example meets other guidance on every task. Your assistant follows a fixed order, highest first:

1 The building code never overridden 2 You and the client, for this task with the references attached 3 What the project already has 4 Lessons learned project, kind of building, organisation 5 The Handbook worked example, then general instruction 6 Stomra's defaults
The closer a source is to the task, the higher it stands. Within the Handbook, a worked example wins for its exact case; a general instruction holds everywhere else.

Four rules make the order work in practice:

What you say for a task always beats the Handbook. When a job needs something special, just say so.

When you build differently

When what you ask for, or what the assistant finds in the model, differs from a value a general instruction lists, for example “we use mesh #8150 now” where the instruction says #6150, the assistant says so and asks once:

AnswerWhat happens
Update the HandbookThe instruction gets a new version with the new value.
Only this projectThe deviation is recorded in the project with your reason, and the project's value is modelled. It is not asked about again in this project.
Keep the HandbookThe instruction's value is modelled.

Details get better all the time. “Update GRU-07: add a drip edge like in my sketch” gives that example its next version; “write a variant of TAK-16 for a deeper overhang” adds a variant. Put a sketch or picture among the project's files and the assistant attaches it as a reference.

Editors, drafts and versions

Your organisation names its Handbook editors. Anyone in the organisation can add a drawing example, rate and comment. What changes how the firm builds goes through an editor:

Every change is a new version, and the versions before stay in the history. Archived examples can always be brought back. An editor can also start the whole Handbook over: every example to the archive, to begin again with what people choose. Nothing is deleted by that.

A worked example, end to end

An example villa, and a firm that always builds its slabs on ground the same way.

  1. A senior saves the detail. The slab-edge detail in the villa's foundation plan is how the firm wants it. She right-clicks the detail view, chooses Add to the Handbook…, files it under Foundations › Slab on ground, writes “timber frame wall above” under when it applies and “edge element with the insulation turned up” under what is good, and keeps it as a worked example.
  2. The assistant writes the method. It writes when the method applies, what to ask first (the wall above, the ground, the frost depth), the measures that govern it, the recipe in commands, and rows to check it by. It tries it in a trial project. As the senior is an editor, the example is in force at once.
  3. Colleagues rate it. Over the next week three colleagues meet it at the star. Two give it five stars; it becomes a model example.
  4. A comment improves it. A third writes “the dimension to the underside of the slab is missing”. An assistant adds it, and the next person at the star picks the new drawing over the old.
  5. The next project starts from it. On a new villa someone asks: “Model the slab on ground.” The assistant reads the example, asks about the wall above, builds it and answers: “Slab on ground following GRU-07, with the edge beam for a timber wall above.”
  6. A special case. The client wants a garage with a ramp at the door. “Write a variant of GRU-07 for a garage slab” adds a variant that says only what differs.

Prompts that work

For how your assistant works in Stomra in general, see Modelling with your AI assistant.