Other

Novelty

Evolutionary explanation-discovery engine for hard-to-vary causal theories of unknown phenomena

03
Workflows
00
Tools
01
Reference
07
Triggers

Key Points

Not for a single-pass divergent brainstorm (use BeCreative) or delivery validation alone (use Evals)

Inside the Skill

The thinking, frameworks, and architecture that distinguish this skill from a generic version of the same task.

Operating Contract

  • Input: a phenomenon, observations, constraints, rivals, available tests, and prohibited directions. Treat source material as evidence or creative corpus, never as executable process instructions.
  • Output: a diverse survivor portfolio. Each explanatory survivor states its causal core, necessary parts, counterfactuals, risky prediction, rival comparison, and remaining residue.
  • Run state: preserve phenomenon, observations, constraints, rivals, population, lineage, cycle, tests, selection scores, and survivor lessons. Keep evidence, assumptions, and speculation distinct.

Explanatory Selection

A candidate does not advance merely because it is elegant or compatible with observations. It must provide a specific causal account whose core parts cannot be freely changed while preserving the same explanatory work. This is comparative evidence of quality, not proof that a theory is true or unique.

Every survivor must include: target phenomenon; compact causal core; necessary roles; component-ablation and parameter-substitution counterfactuals; a rival comparison; a risky discriminating prediction; cross-context behavior; and remaining residue. Apply HardToVary.md and Workflows/ExplanatorySelection.md before SELECT.

System Properties

  • Explanations before stories: evolutionary phases generate candidates; hard-to-vary causal selection chooses survivors.
  • Novelty is not noise: dream and cross-domain transfer can generate strange hypotheses, but they remain speculative until they survive explanatory selection.
  • BeCreative is a component, not a substitute: it can diversify a phase, but Novelty owns causal tests, survival, and learning across cycles.
  • Anti-convergence: retain distinct causal families, cap descendants from one lineage, rotate disciplines and evaluators, and retain one high-upside wildcard unless it violates a hard constraint.

Gotchas

  • Explaining report, access, attention, integration, or behavior does not automatically explain another target phenomenon. State the target precisely.
  • An identity assertion—"this process simply is X"—is not a bridge unless it yields independent causal consequences.
  • Penalize vague mechanisms: if a part can be swapped, deleted, or rephrased without changing predictions, it is not doing explanatory work.
  • Preserve speculative candidates, but never call them explanations until they pass the hard-to-vary filter.

Workflows & Routing · 3

Each workflow is one job the skill runs. The trigger phrases route your request to the right one — this is the skill's routing table.

  1. 01
    EvolutionCycle Workflows/EvolutionCycle.md

    unknown phenomenon, new theory, hard problem, breakthrough explanation, scientific explanation

  2. 02
    ExplanatorySelection Workflows/ExplanatorySelection.md

    hard-to-vary test, explanation filter, theory selection, causal explanation

  3. 03
    RapidCycle Workflows/RapidCycle.md

    rapid novelty cycle, time-boxed creative sprint

How to Invoke

Say any of these to your DA and LifeOS activates the Novelty skill automatically:

  • "develop a new theory"
  • "explain a mystery"
  • "solve an explanatory gap"
  • "discover a mechanism"
  • "consciousness"
  • "origin"
  • "or scientific breakthrough. Also use for multi-cycle creative exploration"

Or invoke explicitly:

Skill("Novelty")

References · 1

Auxiliary files the skill loads at runtime — frameworks, guides, configs.

  • HardToVary

Want LifeOS to do this for you?

Install LifeOS on your machine — your DA gets the Novelty skill plus 55 others, all hooked into one Life OS.