zicato-manage-epochs-and-rounds

Clarify zicato epoch boundaries, evolve rounds, and generation lineage.

4|2|Updated May 14, 2026
One-click install
npx skills add https://github.com/pedapudi/zicato --skill zicato-manage-epochs-and-rounds
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: zicato-manage-epochs-and-rounds
Source: https://github.com/pedapudi/zicato/tree/main/skills/zicato-manage-epochs-and-rounds
Command: npx skills add https://github.com/pedapudi/zicato --skill zicato-manage-epochs-and-rounds

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents confusion about zicato's epoch boundaries, outer evolve rounds, inner tournament rounds, generation lineage, champion evaluation modes, and contract-driven auto-epoching.

Core Features & Use Cases

  • Epoch Mental Model: Explains epochs as sealed evaluation contracts containing the board, proposer brief, scoring, harness identity, proposer configuration, and operator goal.
  • Round and Lineage Attribution: Distinguishes outer evolve rounds from inner tournament rounds and clarifies champion/challenger versus parent/child terminology.
  • Epoch Operations: Guides safe inspection and use of epoch list, new, close, switch, set-goal, and garbage-collection operations.
  • Evaluation and Journaling: Interprets full, fast, and fast-degraded champion evaluation modes, mandatory pre-run hypotheses, outcomes, and round event logs.
  • Use Case: When a contract file changes or an operator needs to inspect why a generation was promoted, use this Skill to identify the relevant epoch, round, lineage relationship, and journal evidence without launching an expensive live evolution run.

Quick Start

Ask the zicato skill to explain whether a contract change created a new epoch and identify which outer round minted a specified generation.

Frequently Asked Questions about zicato-manage-epochs-and-rounds

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is a zicato epoch and how does contract hashing affect epoch boundaries?

A zicato epoch is a sealed evaluation contract containing the board, proposer brief, scoring, and harness identity. Contract-hash auto-epoching automatically creates new epoch boundaries when the contract file changes, ensuring evaluation provenance remains frozen and traceable.

How do I distinguish between outer evolve rounds and inner tournament rounds in zicato?

Zicato separates outer evolve rounds, which drive the overall generation lineage, from inner tournament rounds, which evaluate champion versus challenger pairs. This distinction clarifies parent-child relationships and accurately attributes generation promotion to the correct round.

How can I inspect zicato generation lineage without launching an expensive live evolution run?

You can inspect generation lineage safely using read-only CLI commands to list epochs, identify the relevant round, and review structured experiment journals. This approach prevents costly live runs while still attributing champion promotion provenance accurately.

What are the differences between full, fast, and fast-degraded champion evaluation modes in zicato?

Zicato champion evaluation modes range from full, which provides complete scoring, to fast and fast-degraded, which offer quicker but less comprehensive assessments. These modes determine how tournament outcomes are interpreted and recorded in the experiment journal.

What guardrails do I need to follow when managing zicato epoch operations like close and switch?

Zicato epoch operations require read-only CLI inspection, frozen epoch contracts, and strict adherence to live-run and virtual-environment guardrails. Following these precautions prevents unintended mutations and ensures safe epoch list, close, switch, and garbage-collection operations.