parallel-fanout

Distribute user interactions into three deterministic parallel sub-skills using entropy-derived seeds.

60|13|Updated Dec 22, 2025
One-click install
npx skills add https://github.com/plurigrid/asi --skill parallel-fanout
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: parallel-fanout
Source: https://github.com/plurigrid/asi/tree/main/ies/music-topos/.codex/skills/parallel-fanout
Command: npx skills add https://github.com/plurigrid/asi --skill parallel-fanout

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill dispatches every user interaction into a deterministic, parallel fanout across three roles, enabling scalable, balanced processing with GF(3) conservation.

Core Features & Use Cases

  • Interaction entropy seed: Derives seeds from interaction properties.
  • GF(3) triad fanout: Generator, Coordinator, Validator split into three parallel branches.
  • Deterministic outcomes: Same seed yields identical branching results across runs.

Quick Start

Trigger a triadic fanout for a single interaction and observe the three parallel results.

Frequently Asked Questions about parallel-fanout

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

FAQPage Schema
How does parallel fanout distribute work across multiple processes?

Parallel fanout divides a single interaction into three concurrent branches—generator, coordinator, and validator—using entropy-derived seeds to ensure deterministic, balanced processing across all branches with identical results on repeated runs.

What is GF(3) conservation and why does it matter for parallel task dispatch?

GF(3) conservation ensures balanced triadic splitting where outputs from all three parallel branches maintain mathematical closure. This guarantees merged results are consistent and verifiable regardless of task domain—sonification, database, proof, or game logic.

Can I use deterministic fanout for tasks beyond sonification and databases?

Yes. The Skill applies deterministic parallel fanout across task domains including sonification, derivation, REPL, database, proof, and game execution, provided your interaction generates an entropy seed for triadic branching.

How does SplitMix64 entropy seeding ensure reproducible parallel results?

SplitMix64 derives deterministic seeds from interaction properties, so identical inputs always produce the same three-way branch assignments and outputs. This enables consistent parallel dispatch without randomness.

What happens if one of the three parallel branches fails or produces invalid output?

The validator branch detects inconsistencies and verifies GF(3) conservation across generator and coordinator outputs. Merged output verification catches branch failures before results are returned.