Logic Context

Logic Context turns a Logic Fabric project into a Business Requirements Document (BRD) written in business language. Logic blocks become business rules, logic flows become system workflows, schedules become scheduled jobs and business processes become process definitions, each traceable back to the artifact it came from. Use it for handovers, audits, client sign-off and onboarding, and regenerate it whenever the project changes.

Logic Context only reads your project. It never changes it.

Generate a document

1. Sign in to Logic Context and open Generate.
2. Select the project and start generation. Sections appear as each one is finished.
3. Read the document. Each section shows whether it Passed quality review or Did not pass quality review.
4. Mark sections as approved as you review them, or select Give Feedback on a section to regenerate it with your comments, for example Add more detail on SLAs.
5. Use the chat panel (Ask about this BRD…) to ask questions or request changes to the document in plain language.
6. Select Export HTML to download a self-contained document that prints and shares without the app.

Completed documents are kept under History, where you can reopen earlier versions.

Document sections

A BRD has up to 11 sections. You can turn sections on or off, rename them and reorder them per project; at least one must stay on.

Section	What it documents
Business Processes	Each process: purpose and scope, stages, routing and transitions, personas and responsibilities, escalation rules, exception flows and process mining insights such as critical path and automation coverage.
Logic Flows	System workflows: procedure, actors, preconditions, postconditions and exceptions.
Logic Blocks	Business rules: validations, validation sets, formulas, decision tables and decision trees.
Schedules	What runs, when and why.
Events Definitions	The events the project defines and what they carry.
Event Handlers	Which flows respond to which events.
Configurations	Configuration values and what they control.
Localized Resources	Translated texts and their languages.
Service Connections	External services the project calls.
Recipes	Which logic runs when table rows change.
Data Model	The tables and columns the project uses.

Every documented artifact gets a stable ID, such as WF-001 for a workflow, so you can refer to requirements precisely. You can change the prefixes per project.

Settings

Open Settings and select a project. Only people with access to the project can view or change its settings.

Setting	What it does
Sections	Turn sections on or off, rename them and change their order.
Artifact ID Prefixes	The prefix used for each kind of artifact.
Audience	The writing style: General, Executive, Technical or Auditor.
Quality Gate	Review each section against quality criteria, with a Threshold (0–1) and Max retries (0–5). A section below the threshold is rewritten up to the retry count; if it still falls short, it is flagged rather than holding up the document. Turn on Override deployment defaults to use project-specific values.
Prompt Parameters	Output language for the prose (field names and codes stay as they are), a Glossary that maps terms to your own (for example Logic Flow to System Workflow), and Additional instructions.

How it behaves

• Runs as you. It documents only what you can read in Dataverse.
• Private jobs. A generation in progress can be viewed only by the person who started it.
• Project-scoped history and settings. History and settings are available only to members of the project.
• Business language. Field names and codes are translated into plain prose, while traceability keeps the link to the real artifact.

Example

Before handing a customer-service project to the client, you set Audience to Executive, map Logic Flow to Automated Procedure in the Glossary, and generate. You give feedback on Business Processes to explain the case escalation SLA in more detail, approve each section, and export the HTML for the steering committee.

Related

• Logic Agents overview
• Logic Guard
• Dependencies