gpd-map-research

Parallel agents map a physics research project by documenting theory, computation, methodology, and status concurrently. This workflow generates a standardized suite of files for governance, reproducibility, and collaboration within a designated research map directory.

A research map is a structured documentation suite of seven standardized files like FORMALISM.md, ARCHITECTURE.md, and VALIDATION.md. It facilitates project onboarding by providing consistent, traceable documentation that enables rapid planning and collaboration across physics research teams.

Generating structured documents like FORMALISM.md and REFERENCES.md requires executing a multi-agent orchestration workflow. Four parallel mapper agents write seven predefined documents to a .gpd/research-map directory, capturing the project's formalism, references, architecture, structure, conventions, validation, and concerns.

Yes, mapping research requires a defined contract context and a dedicated research map directory named .gpd/research-map. The parallel mapper agents write the seven standardized documentation files directly to this location to ensure consistent project traceability and governance.

You should refresh a research map after major theoretical or computational progress, or when onboarding new collaborators to an existing project. Re-executing the parallel agents updates the seven structured documents to reflect the latest project state and maintain accurate traceability.

If a parallel mapper agent fails during orchestration, the workflow handles it gracefully through partial completion and retry options. The orchestrator provides a final summary, allowing you to retry failed agents without losing the documentation progress already written to the research map directory.