Modeling rules

Whatever you would otherwise repeat in every prompt goes in once, and every run reads it.

Company rules

Where the dashboard shows a Company knowledge page. Otherwise see The single rules field.

  • Dashboard, Company knowledge, Add, Rule. Choose what the rule sets (Units, Hole method, Material or Other), type the value, then Publish. The first publish asks "Publish to all <n> members?" and shares the rules with the organization.
  • Mandatory makes a rule hold for every member. Each rule CADABRA measures has the switch in the list: units, hole method and material.
  • Add, Default sets a value new parts start from, such as a material. Mandatory on a default locks the default, never the request: a member who asks for something else in a prompt gets it.
  • Rules sent from the task pane and norms learned from members’ work appear as suggestions. Publish applies one, Reject drops it, and Retire in a rule’s menu stops it applying to everyone’s work.
  • Where offered, Add, Document uploads a rules or standards document for CADABRA to read. Each shows its revision and whether it is read.
  • An admin publishes, and so does a member the Team page gives the Standards owner role. Everyone else sees each rule, with a padlock on mandatory ones, on the dashboard and in the task pane. Admins never see members’ personal memory.

The single rules field

  • Task pane: Settings, then Modeling standards. Edit rules opens the editor, which counts characters as you type and saves with Save standards. Clear empties it after confirming "Clear your saved standards?"
  • Dashboard: /dashboard/standards, the card headed Company modeling rules. Save rules saves, and the line beside it then reads "The Agent uses these on its next run." On a later visit it reads "Last updated" with the date, and "You have unsaved changes." while an edit is pending.

Both write the same field. There is no per-project or per-document version of it.

How much fits

The single field holds 60,000 characters. The dashboard textarea stops accepting input at that point; the service refuses a longer body outright rather than storing a truncated set of rules.

That is roughly a full modeling standards document.

Rules that change what gets built. Each line is a decision the model would otherwise make on its own.

- Units: millimeters, 2 decimal places. Angles in degrees, 1 decimal place.
- Clearance holes for metric socket screws: M3 3.4, M4 4.5, M5 5.5, M6 6.6. Never model a nominal-diameter clearance hole.
- Fillets: 2 mm on internal machined corners, 1 mm break on external edges, unless the prompt gives a radius.
- Material default: 6061-T6 for machined aluminium parts, 304 stainless for hardware brackets. Set it on the part, not just in a note.
- Feature names: <Op>_<Purpose>, e.g. Cut_MountSlot, Boss_BearingSeat. No Extrude1, no Cut-Extrude2.
- Sheet metal: 1.5 mm 5052, bend radius equal to thickness, K-factor 0.44.

How a run uses them

The rules text is appended to the instructions CADABRA sends with every turn, under the heading Company modeling rules, introduced with one line: "Org standards. Apply to every part, assembly and feature you create or modify, unless the user overrides."

So Agent Mode builds to them without being reminded, and the read-only modes can be asked about them. Asked whether a model meets the rules, CADABRA audits instead of applying: it works through every rule that bears on what it inspected and reports each as met, not met, or not determinable, names what it inspected, and says where the rules are silent. A rule it did not check is never reported as passing.

When a rule and a prompt disagree

The prompt wins. "Apply to every part, assembly and feature you create or modify, unless the user overrides" is the instruction the rules arrive with, so asking for a 5 mm fillet where the rules say 2 mm gets you 5 mm, for that turn only. Nothing about the saved rules changes, and the next turn is back on 2 mm.

The one exception is a published company rule made Mandatory: it holds against the prompt on what CADABRA measures, and the reply names the rule.

Two rules that contradict each other are a different problem. When both carry checks, publishing refuses the pair and the dashboard asks which one to keep. Two prose rules are not compared, and the model picks one, so read the review list before publishing.

Who the rules apply to

On a plan with Drawings access and an organization on the account, the rules are stored against the organization, so one person editing them changes what everyone in that organization gets. Drawings access is Enterprise today. On every other plan the rules are stored against your own account only.

The panel caches the rules for 5 minutes. An edit made in the task pane takes effect on the next run on that machine; an edit made on the dashboard or on someone else's machine can take up to 5 minutes to reach a panel that is already open.

Turning an existing standards document into rules

Attach your modeling standard as a PDF or a text document to a prompt in the panel, and the attachment chip in the transcript carries a Save as standards button. It rewrites the document as the durable rules an assistant can follow, keeping every number, tolerance, code and standard reference verbatim, and dropping prose, revision tables and approvals. It shows "Reading…" while it works, then "Saved as your modeling standards."

If the document distils to more than 60,000 characters even after a second, tighter pass, nothing is saved and CADABRA tells you the size it reached. Split the document, or paste the part you want.

Attachments covers the file limits for that upload.

What this field does not do

  • It does not set drawing conventions. Title blocks, projection and notes come from drawing standards.
  • It does not change the SOLIDWORKS document unit setting.
  • It holds against a prompt only for a published rule set to Blocking, and Blocking needs a check CADABRA measures. Every other rule yields to the prompt, and nothing audits your existing files unless you ask.