recursion-designer

Name: recursion-designer
Availability: InStock
Author: jota-batuta

Detect external category changes and coordinate auditable dictionary updates.

Updated Feb 20, 2026

Search Tags:#versioning #auditing #governance #recursion #data-dictionary #external-categories #unknown-detection

Ready to run

npx skills add https://github.com/jota-batuta/batuta-dots --skill recursion-designer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: recursion-designer
Source: https://github.com/jota-batuta/batuta-dots/tree/main/BatutaClaude/skills/recursion-designer
Command: npx skills add https://github.com/jota-batuta/batuta-dots --skill recursion-designer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detect external category changes and coordinate safe, auditable updates to dictionaries and models without breaking historical results.

Core Features & Use Cases

Detect unknown or evolving categories and log them for review.
Enforce a multi-stage governance flow with human approvals and controlled propagation.
Maintain immutable dictionary versions with complete audit trails.

Quick Start

Configure a versioned dictionary workflow that logs unknowns and routes changes for approval.

Frequently Asked Questions about recursion-designer

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

FAQPage Schema

How do I manage evolving external category mappings without breaking historical data?▼

To manage evolving external category mappings, you need a versioned data dictionary that detects unknown categories and enforces controlled propagation. This ensures historical results remain intact while new categories route through human approval workflows for safe updates.

What is the best way to version taxonomies and product categories for auditing?▼

Versioning taxonomies for auditing requires maintaining immutable dictionary versions with complete audit trails. This approach logs unknown category detections and enforces forward-only propagation, ensuring every schema change is reviewed and traceable.

How do I detect unknown or new categories in an evolving coding schema?▼

Detecting unknown categories in an evolving coding schema involves logging unrecognized external inputs for review. A multi-stage governance workflow captures these anomalies and routes them for human approval before updating the production data dictionary.

Can I enforce human approval before propagating data dictionary updates?▼

Yes, enforcing human approval before data dictionary updates is achieved through a multi-stage governance flow. This workflow intercepts detected category changes, requires manual review, and applies forward-only propagation to prevent uncontrolled schema disruptions.

How do I audit changes when external taxonomies shift over time?▼

Auditing external taxonomy shifts relies on immutable dictionary versions and audit-friendly logging. By capturing unknown category detections and routing them through controlled approval stages, every mapping change is permanently recorded and traceable.

Do I need a governance workflow to safely update evolving product categories?▼

A governance workflow is essential for safely updating evolving product categories because it enforces human approvals and forward-only propagation. Without this multi-stage process, uncontrolled taxonomy changes risk corrupting historical results and breaking audit trails.