Skip to main content

Knowledge Modules

A Knowledge Module is a saved package of guidance — voice, rules, and preferred methods — that Engenerate can apply during chat. Instead of repeating the same instructions every time, you save them once and turn the module on when you need it.

What Knowledge Modules Are For​

Knowledge Modules are useful when you find yourself repeating the same guidance across conversations, such as:

  • repeatable project or firm standards you want applied consistently
  • discipline-specific judgment (a subject area you want Engenerate to reason about the way your team does)
  • engagement playbooks, like a specific safety review process you run on certain jobs

Discipline vs Playbook​

TypeWhat it isExample
DisciplineA subject-matter lens Engenerate applies to a conversationYour firm's hydrology approach
PlaybookA process or engagement overlay that layers on top of any disciplineA specific safety review protocol

You can combine a Discipline with a Playbook — the Discipline shapes the subject-matter judgment, and the Playbook shapes the process on top of it.

Creating a Knowledge Module​

Knowledge Modules are created in Settings → Knowledge Modules → New. When you create one, you'll fill in:

  • Name — a short label for the module
  • Description — when to use the module ("Use when…" / "Use for…"); also helps Engenerate decide whether to bring it in automatically
  • Knowledge — the rules and guidance the module should follow
  • Resources (optional) — project or library documents to pin when the module is forced on

Save the module once you're done. Output Templates and Review Rubrics are chosen separately in chat (Plus menu / rubric badge), not stored as module defaults.

Creating or Editing a Module in Chat​

You can also build a Knowledge Module directly in a conversation using Do mode, instead of filling in the form by hand:

  • From the menu: open the chat + menu → Knowledge Modules, then choose Create in Chat (or a module's Edit in Chat action). Engenerate switches to Do mode and starts authoring.
  • By asking: in Do mode, just say something like "Create a Knowledge Module for USACE ATR reviews based on USACE ATR policy."

When you name a reference (for example a specific policy or standard), Engenerate finds the matching document in your libraries, reads it, and drafts the module's Name, Description, and Knowledge grounded in that source. Any reference documents it used are attached to the module automatically — you don't have to paste document IDs, and it won't invent them. If it can't find a matching reference, it drafts from general knowledge and tells you no source was attached.

Engenerate then shows a proposal card. Review it and click Save to My Knowledge Modules to save it as a new personal module. Editing in chat produces an updated copy (your original stays as-is), and the references from the module you edited are carried over.

note

Creating and editing modules in chat is available only in Do mode and only when the feature is enabled for your workspace.

Using Knowledge Modules in Chat​

Open the chat + menu, go to Capabilities → Knowledge Modules, and check on any Disciplines or Playbooks you want for the current session. You can turn on any number of modules at once.

When modules are forced on, a small Knowledge Module icon appears in the chat footer. Click it to open a read-only preview (name, description, rules, and attached resources). From there you can Remove the module from the force list, Edit it in the form dialog, or Edit in Chat (switches to Do mode). If more than one module is forced, the icon opens a short list so you can pick which one to inspect.

Engenerate can also bring in a relevant module on its own, even if you haven't explicitly selected it — so a module you've saved may still shape an answer without being forced on.

In Do mode, if you ask to edit "the KM" while multiple modules are forced and you don't name one, Engenerate asks which module to edit before loading it.

How Conflicts Are Resolved​

When guidance from more than one place applies to the same conversation, Engenerate resolves it in plain, predictable order:

  • modules you select or force always take priority over Engenerate's built-in defaults
  • among the modules you force, the one you turn on later refines or overrides an earlier one when they disagree

Writing a Good Description​

The description is what helps you — and Engenerate, when deciding whether to bring a module in automatically — recognize when a module applies. A good description:

  • says when to use the module ("Use when..." or "Use for...")
  • names concrete situations rather than abstract goals
  • stays short — a sentence or two is usually enough
  • optionally adds a short "Not for..." line when there's a clear case the module shouldn't apply

Example​

West Virginia Runoff Standards (Discipline)

  • Description: "Use for stormwater/runoff calculations on West Virginia sites. Not for other states."
  • Domain rules: apply the West Virginia Stormwater Management Manual's runoff coefficients and detention sizing method.

With this module turned on, an Analyze question about detention pond sizing for a West Virginia site will apply the state-specific method instead of a generic default — while the same question about a site in another state would fall back to Engenerate's default approach.

Availability​

Knowledge Modules may not be available on every account or workspace.