As missions progress, Genesis generates a large number of intermediate documents including data files, metadata definitions, instructions, and other artifacts that represent each step of the workflow. Document Flow organizes these materials to help engineers understand what the worker is doing and how the mission evolves from one phase to the next.

How Document Flow Is Organized

Document Flow displays each phase of the Blueprint as its own section. Attached to every phase is a set of documents created during that step. Each item is interactive, and clicking on a document opens it in a rich text viewer where engineers can inspect structure, formatting, and logic in detail.

This can include:

• Data files and extracted column structures
  
  
• Instructions generated by the worker
  
  
• Metadata fragments
  
  
• Model definitions
  
  
• Mapping documents
  
  
• SQL produced for downstream layers
  
  

The view makes it easy to see exactly what the system produced at each stage of execution.

Reducing Manual Documentation Work

Many of the artifacts generated during a mission are the same materials data engineers typically create by hand when building pipelines or preparing transformations. Genesis automates this work, producing consistent and well-structured documentation as part of the workflow. This reduces manual effort and accelerates development, especially for multi-phase ingestion or modeling tasks.

In the example shown, Genesis produced a metadata file for a dimension in the semantic layer. It includes field definitions, data types, and SQL. These materials are versioned and stored in the connected Git repository, creating a durable and repeatable record of how each layer was built.

Exploring Results Outside Document Flow

For users who want a more structured layout, the Results view provides an alternative option. Documents are grouped by phase and shown in a hierarchical list. Engineers can open any artifact to understand how the worker made decisions or generated specific model components.

Document Flow and Results offer two ways to inspect mission outputs, making it simple to trace every action performed by the system.

Why This Matters

• Clear visibility into every artifact created during a mission
  
  
• A complete audit trail of instructions, mappings, and model components
  
  
• Less manual documentation required from engineering teams
  
  
• All materials stored and versioned in Git for long-term access
  
  
• Multiple viewing modes to support different workflows
  
  

Document Flow delivers deep transparency into agent-driven work. By showing every document produced at each phase, Genesis ensures that complex workflows remain understandable, traceable, and aligned with engineering best practices.