Software Modules
End-to-end pipelines composed from software components
Software modules are production-ready, end-to-end pipelines that combine software components into a single, configurable workflow. They eliminate the need to wire components together manually — you provide the input and your field requirements, and the module handles transcription or parsing, schema generation, and structured extraction in one step.
See also: No-Code Assets for prompt templates and packaged skills.
Use software modules when you want a complete, working pipeline with minimal integration code. Each module is designed to cover the most common GenAI knowledge capture scenarios out of the box.
Overview
| Module | Input | Processing steps | Output |
|---|---|---|---|
| Audio-to-Structured-Data | Audio / Video | Transcribe → Extract | Structured fields from spoken content |
| Document-to-Structured-Data | PDF / DOCX | Parse → Extract | Structured fields from document content |
| RAG-Workflow | PDF files + User query | Parse → Embed → Store → Retrieve → Generate | Contextual answers with citations |
| Multi-Source-Report-Generator | Mixed files (PDF, DOCX, Excel/CSV, audio/video, images) + use-case definition (title, description, sections) | Normalize → Curate → Draft → Review & Repair → Assemble | User-defined long-form report (Markdown + optional DOCX) |
Audio-to-Structured-Data
This module bridges the gap between spoken language and structured data. It combines the Transcriber and Extractor components into a single pipeline: audio is transcribed to text, and the text is processed against your field requirements to produce validated, structured output. Both the transcript and the extracted fields are returned together. The generated schema is persisted and reused on subsequent runs, making repeated processing fast and cost-efficient.
Example: A site worker records a 90-second voice note describing a water leak in the storage room. The module produces: a clean transcript ("At 14:30, a water leak was noticed in storage room B..."), and extracted incident fields: Event type: Water leak · Location: Storage room B · Time: 14:30 · Severity: Yes · Immediate action: Area cordoned off · Equipment affected: Electrical equipment near east wall.
What the module returns:
| Output | Description |
|---|---|
| Raw Transcript | Verbatim speech-to-text output |
| Enhanced Transcript | GPT-refined, readable version |
| Structured Fields | All defined fields extracted and validated |
| Reusable Schema | Pydantic schema saved for future runs |
Key features:
- Single entry point for voice-to-data workflows
- Plain-language field requirements — no code or schema definition needed
- Returns both transcript and extracted data for full traceability
- Schema reuse eliminates redundant processing on repeated runs
Potential applications:
-
Workplace incident and safety observation reporting
-
Construction site and field work diary entries
-
Field service and maintenance activity logging
-
Quality inspection and audit recordings
-
Medical and clinical dictation capture
-
Sales call notes and customer interaction summaries
-
Meeting minutes and action item extraction
-
Implementation code: software_modules/audio_to_structured_data
-
Usage examples: examples/audio_to_structured_data
Document-to-Structured-Data
This module turns static documents into structured, queryable data. It combines the Document Parser and Extractor components: a document is first converted to clean markdown, then processed against your field requirements to extract exactly the data you need. The module supports both vision-based and local parsing strategies, making it adaptable from clean digital PDFs to visually complex, multi-column layouts.
Example: A scanned 8-page supplier invoice PDF with embedded tables is parsed into clean markdown. The module extracts the required fields: Invoice number: INV-20241103 · Supplier: Acme Components Ltd · Total (excl. VAT): €4,820.00 · Due date: 30.11.2024 · Line items: 3.
What the module returns:
| Output | Description |
|---|---|
| Parsed Markdown | Document content converted to clean, structured markdown |
| Structured Fields | All defined fields extracted and validated |
| Reusable Schema | Pydantic schema saved for future runs |
Key features:
- Configurable parser choice — vision-based for complex layouts, local for speed and cost efficiency
- Plain-language field requirements eliminate manual schema work
- Returns both parsed text and extracted data for full traceability
- Schema reuse supports efficient batch processing across large document sets
Potential applications:
-
Invoice and purchase order data capture from PDFs
-
Contract and agreement key term extraction
-
Technical specification and datasheet processing
-
Research report and regulatory filing analysis
-
CV and job application data extraction
-
Insurance and financial form digitization
-
Product catalogue and pricing data ingestion
-
Implementation code: software_modules/documents_to_structured_data
-
Usage examples: examples/documents_to_structured_data
RAG-Workflow
This module enables question-answering over document collections. It combines all five RAG components into a complete workflow with two phases: an indexing phase that parses, embeds, and stores documents, and a query phase that retrieves relevant context and generates answers with citations. The module maintains a persistent vector store and optional conversation history, making it suitable for interactive document exploration and knowledge retrieval applications.
Example: A team indexes 50 technical specification PDFs. Later, a user asks: "What is the maximum operating temperature for component X?" The module retrieves relevant chunks and responds: "The maximum operating temperature for component X is 85°C [Source: TechSpec_X_v2.pdf, page 4]. For extended duty cycles, derate to 70°C [Source: OperatingGuide.pdf, page 12]."
What the module returns:
| Output | Description |
|---|---|
| Index Result | Number of documents and chunks indexed, vector store path |
| Answer | Generated response with inline citations |
| Retrieved Documents | Top-k relevant chunks used for answer generation |
| Conversation History | Optional: Last n Q/A pairs for context-aware responses |
Key features:
- Two-phase workflow: index once, query many times
- Persistent vector store — indexed data reused across sessions
- Configurable retrieval: top-k, score threshold, hybrid search, reranking
- Citation support — every answer references source documents and pages
- Optional conversation history for multi-turn dialogue
- Streaming response support for real-time UX
- PostgreSQL / pgvector support available at the component level for custom pipelines
Potential applications:
-
Internal knowledge base search for technical documentation
-
Compliance and policy Q&A over regulatory documents
-
Research paper exploration and literature review assistance
-
Customer support knowledge retrieval from product manuals
-
Legal contract and case law research
-
Medical guideline and protocol reference systems
-
Educational content Q&A and study assistance
-
Implementation code: software_modules/RAG_workflow
-
Usage examples: examples/RAG_workflow
Multi-Source-Report-Generator
This module generates a fully user-defined long-form report from any mix of source files. You define the use case: report title, a description of the report's purpose, and as many sections as needed — each with a plain-language instruction describing what to extract from the evidence and what the section should contain. The module normalises every input file (PDF, Word, Excel/CSV, audio/video, images, text) into a common Markdown evidence pack, then runs an agentic workflow that drafts each section independently, fact-checks and repairs it with a diff-editor reviewer, and assembles the final report in your original section order.
Sections can declare dependencies on other sections using depends_on. Sections with no dependencies run in parallel; dependent sections wait for their dependencies to be finalized and receive their content as context — enabling a Summary or Recommendations section to synthesize from what earlier sections already established. The complete use-case configuration can be saved to a JSON file and reloaded for repeat runs on new evidence.
Example: A consultant uploads a meeting recording (MP3), a project budget (Excel), and a policy PDF. They define three sections — AI Maturity Level, Current Development Stage, and Recommendations (which depends on the first two). The module transcribes the audio, parses the documents, drafts and fact-checks each section in parallel, then writes Recommendations last using the finalized earlier sections as context. The output is a formatted Markdown report with a matching Word document.
What the module returns:
| Output | Description |
|---|---|
Markdown Report (report.md) | Assembled long-form report in your section order — always produced |
Word Document (report.docx) | Optional DOCX export; requires output_docx=True and Pandoc |
| Per-Section Breakdown | Each section's content, usage tokens, and any reviewer warnings |
| Evidence Index | Source files with metadata and normalized content |
Key features:
- Fully user-defined use case — report title, description, and any number of sections each with a plain-language instruction specifying what to extract and how to write it
- Agentic per-section workflow — independent drafting, mandatory diff-editor reviewer repair, optional style polish per section
- Dependency-ordered sections —
depends_onlets summary or recommendation sections synthesize from finalized earlier sections rather than re-deriving from raw evidence - Mixed input normalization — PDF, Word, Excel/CSV, audio/video, images, and plain text all processed in a single pipeline
- Optional sample report — provide an existing report to enforce a specific format, tone, and length; the writer mirrors its structure without copying content
- Config persistence — save the full use-case definition (sections, options, paths) to JSON with
save_report_config; reload withload_report_configfor repeat runs on new evidence - Dual output — Markdown always produced; Word document optional
Potential applications:
-
Meeting reports and advisory summaries from transcripts and supporting documents
-
Client-facing project and progress reports from mixed deliverables
-
AI readiness and consultancy assessments from interview recordings and documents
-
Due-diligence and audit reports from heterogeneous evidence sources
-
Research and literature summaries across documents and recordings
-
Sales proposals and marketing materials from briefs and assets
-
Interactive demo: Report Writer demo
-
Implementation code: software_modules/multi_source_report_generator
-
Usage examples: examples/multi_source_report_generator
GAIK