Shadow

In plain words: What-if simulator overview

Designed 2 min read 9 glossary terms 12 connected pages
The short version written for the Snayu team

The planned area (What-if Simulator, or Shadow) for holding isolated candidate possibilities with exact parentage, assumptions and evidence, so a branch is never mistaken for the real world.

Why read it: Read this before building branching experiments, alternative-generation or isolated trial workspaces.
  1. 1Two roles: Dancer generates alternatives; Hunter challenges one candidate.
  2. 2A branch cannot merge, deploy or promote; real changes go through the normal owner with approval.
  3. 3Deleting a directory does not clean up processes, leases or credentials; cleanup needs a receipt.

Designed No branch, workspace or collapse path ships.

Words on this page, decoded click one for its card

EvaluatorWhat-if Simulator
Where it sits in LychD

What-if Simulator Shadow

Tries alternatives in isolation without touching reality, then proposes the best for review.

It's like: A flight simulator.

Click a dot to open that part's card.

Glossary page In the network

In this section 2 pages

Dancer Alternative generator (Dancer) The planned role (Dancer) that takes one request and opens several alternative approaches under one declared angle, returning each with assumptions, requirements, unknowns and sources, without ranking them. open → Hunter Candidate challenger (Hunter) The planned role (Hunter) that reviews one fixed candidate in a separate run, pointing to unsupported assumptions, missing evidence and rule violations, and naming what observation could settle each. open →
The original text Underlined words open their plain-English card.

In the shadow of one world, other worlds take form.

A branch can feel like the whole present world: its context, files, tools, traces, and feedback all agree. The SepulcherBody sees something narrower—a candidate possibility with pinned parentage and an unspent claim on reality. ShadowWhat-if Simulator keeps that distinction inspectable.

Possibility with lineage

ShadowWhat-if Simulator keeps track of possibilities and their parentage as one Extension DomainPlug-in Area. Within it, a Shadow Realm holds the speculative state and declared workspace topology of one active branch. That tells the reader which possible world is being explored and where it came from. Changed files are still candidate state; separate owners supply container and executor identity.

The branch record pins its base, parentage, assumptions, required state, unknowns, evidence, artifact references, budget, status, and resource owner. Vikalpa is used here as a literary correspondence for a possibility fashioned apart from actuality while it awaits measurement. Its explicit uncertainty and honest handling come from project law, not from the source term. Phantasma is ShadowWhat-if Simulator's isolated expansion mode; evaluation remains elsewhere.

ShadowWhat-if Simulator is Designed; no operational branch, workspace, or collapse path ships. ADR 31 owns the design, and State of Work records delivery.

Choose an office

Dancer opens alternatives through a declared Shadow Lens, an operational Posture, without ranking or choosing among them.

Hunter reviews one named candidate in a separate InvocationJob Request, exposing missing evidence and boundary failures without inventing its replacement.

Their attributable handoff preserves lineage, assumptions, challenges, evidence requests, and uncertainty. SpellweaverWorkflow Engine and GraphStep Map own ordering, fan-out, and joins.

Improve the exploration strategy

The designed strategy contract lets an experiment pin how it chooses branches and stops. Recorded histories can supply a bounded comparison before another material attempt. Follow DriftEvaluator's history replay and pilot to prepare the evidence and distinguish a replay result from fresh execution. A revised strategy enters later work through its owner; it cannot change the ongoing experiment's pinned procedure.

Nothing crosses by acclaim

When a branch is ready to propose a real change, ShadowWhat-if Simulator may package an inert Vision or Promotion Request with its lineage. The target's ordinary effect owner then checks current state and the required evidence, prepares rollback, obtains WardSecurity Desk and HitLApproval Step or eligible preauthorization, and applies and verifies the effect. That passage is what lets a possibility affect the world. The branch itself cannot merge, deploy, publish, purchase, restore, or promote.

A rank or “winner” inside the experiment remains only a search result. Failed and ineligible branches retain required findings, artifacts, provenance, and residue before cleanup. Branch Reaper names that cleanup discipline and its receipt. Deleting a directory cannot settle processes, leases, credentials, ports, or shared effects.

Jujutsu may suit a future tracked-change workspace, but it supplies no execution sandbox. Unsafe execution requires its own admitted boundary.