evolve-record

You can log an evolution outcome by calling the evolve_record tool with gene_id, outcome, signals, score, and summary. This persists results after applying a strategy to a gene, building a historic log for traceability within PrismerCloud workflows.

Capturing gene-driven evolution results requires five inputs: gene_id, outcome, signals, score, and summary. Providing these fields builds a historic log of evolution attempts to learn from successes and failures.

Record an evolution outcome in a PrismerCloud workflow immediately after executing an evolution strategy and evaluating the suggested gene. Logging at this stage captures results to improve future recommendations.

Yes, the evolve_record tool integrates with PrismerCloud MCP workflows to capture and persist results after evolve_analyze and subsequent strategy application across experiments, enabling rapid feedback on gene-driven changes.

Logging strategy outcomes is important because it enables traceability and rapid feedback on gene-driven changes. Recording outcomes, signals, scores, and summaries builds a historic log to learn from evolution attempts and improve future recommendations.