zicato-lineage

Trace zicato inner-harness evolution across epochs and generations from lineage records.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you understand how a zicato inner harness evolved across epochs and generations without confusing structural lineage with tournament outcomes or starting new experiments.

Core Features & Use Cases

  • Epoch Overview: List epochs, inspect their baselining relationships, and identify promoted and rejected generations.
  • Lineage Analysis: Read lineage records to trace parent-child edges, winners' spines, challengers, rejection reasons, scoring deltas, and recombined generation provenance.
  • Conversation Comparison: Use the dashboard to compare two generations' behavior on the same board entry through side-by-side conversation views.
  • Use Case: When investigating why a harness reached its current state, trace its cross-epoch history, distinguish champion-versus-challenger results from lineage relationships, and compare parent and child runs.

Quick Start

Use the zicato lineage skill to inspect the workspace's epoch list and lineage record, then compare a board entry across two generations in the dashboard.

Frequently Asked Questions about zicato-lineage

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

FAQPage Schema
How do I trace harness evolution across epochs and generations?

To trace harness evolution across epochs and generations, inspect canonical lineage records and compare generation behavior to identify parent-child provenance, promoted generations, and rejected runs. This clarifies how the inner harness reached its current state.

What is the difference between tournament outcomes and structural lineage in generation analysis?

Structural lineage maps parent-child provenance and recombined generation edges across epochs, while tournament outcomes represent champion-versus-challenger results and scoring deltas. Distinguishing them prevents confusing baseline relationships with rejection reasons.

Do I need the zicato dashboard to compare board-entry conversations side-by-side?

Yes, comparing two generations' behavior on the same board entry requires the zicato dashboard. It provides interactive side-by-side conversation views to evaluate parent and child runs directly through the virtual-environment CLI.

How do I review rejected or promoted generations within a specific epoch?

To review rejected or promoted generations within an epoch, list the epoch's baselining relationships and inspect the lineage records. This reveals winners' spines, challengers, and rejection reasons without starting new experiments.

Can I interpret tournament analysis results without starting new experiments?

Yes, you can interpret tournament analysis results by reading existing lineage records to trace winners' spines and scoring deltas. This allows cross-epoch history analysis and tournament interpretation without starting new experiments.

What workspace lineage data is needed for cross-epoch history analysis?

Cross-epoch history analysis requires workspace lineage data containing canonical lineage records and baselining relationships. Combined with the zicato virtual-environment CLI, this data enables parent-child provenance tracing and generation behavior comparison.