spw.quest

Pivot a line

Change one slot, keep the rest, and see the line before you go. Forms, side by side shows what each slot does.

The line

bane builder{fail.constrain}

a line you wrote

  • new
subject
builder
body
fail.constrain
charge
bane

An operator in front

  1. ~
  2. ?
  3. !
  4. *
  5. .
  6. ^
  7. #
  8. @
  9. &
  10. =
  11. %
  12. $
Add to what it holds

Back to bane builder[profile]{fail.constrain}

Families it belongs to

Other lines about builder

31 lines one change away

Drop a slot to read what the line says without it.

near: a line sharing a slot uses it · common: common on the shelf

charge the charge in front

  1. boon builder{fail.constrain}

    swap to boon

    • swap
    lands
    Not on the shelf yet.
  2. bone builder{fail.constrain}

    swap to bone

    • swap
    lands
    Not on the shelf yet.
  3. bonk builder{fail.constrain}

    swap to bonk

    • swap
    lands
    Not on the shelf yet.
  4. honk builder{fail.constrain}

    swap to honk

    • swap
    lands
    Not on the shelf yet.
  5. builder{fail.constrain}

    drop the charge in front

    • drop
    lands
    Not on the shelf yet.

subject the word

  1. bane folio{fail.constrain}

    swap to folio

    • swap
    • common
    lands
    Not on the shelf yet.
  2. bane theory{fail.constrain}

    swap to theory

    • swap
    • common
    lands
    Not on the shelf yet.
  3. bane principle{fail.constrain}

    swap to principle

    • swap
    • common
    lands
    Not on the shelf yet.
  4. bane practice{fail.constrain}

    swap to practice

    • swap
    • common
    lands
    Not on the shelf yet.
  5. bane ?builder{fail.constrain}

    ? wonder in front

    • mark
    lands
    Not on the shelf yet.
  6. bane ~builder{fail.constrain}

    ~ potential in front

    • mark
    lands
    Not on the shelf yet.
  7. bane ^builder{fail.constrain}

    ^ ascension in front

    • mark
    lands
    Not on the shelf yet.
  8. bane &builder{fail.constrain}

    & subject in front

    • mark
    lands
    Not on the shelf yet.
  9. bane $builder{fail.constrain}

    $ substrate in front

    • mark
    lands
    Not on the shelf yet.

mode the lens

  1. bane builder[character-card]{fail.constrain}

    add character-card

    • add
    • near
    lands
    Not on the shelf yet.
  2. bane builder[living-component]{fail.constrain}

    add living-component

    • add
    • near
    lands
    Not on the shelf yet.
  3. bane builder[profile]{fail.constrain}

    add profile

    • add
    • near
    lands
    Not on the shelf yet.
  4. bane builder[prompt-packet]{fail.constrain}

    add prompt-packet

    • add
    • near
    lands
    Not on the shelf yet.

body what it holds

  1. bane builder{slot.identity}

    swap to slot.identity

    • swap
    • near
    lands
    Not on the shelf yet.
  2. bane builder{tune.serialize}

    swap to tune.serialize

    • swap
    • near
    lands
    Not on the shelf yet.
  3. bane builder{context.surface}

    swap to context.surface

    • swap
    • near
    lands
    Not on the shelf yet.
  4. bane builder{material.image}

    swap to material.image

    • swap
    • near
    lands
    Not on the shelf yet.
  5. bane builder

    drop what it holds

    • drop
    lands
    Not on the shelf yet.
  6. bane builder(fail.constrain)

    turn its walls to ( )

    • walls
    lands
    Not on the shelf yet.
    why
    what it holds becomes the scene
  7. bane builder<fail.constrain>

    turn its walls to < >

    • walls
    lands
    Not on the shelf yet.
    why
    what it holds becomes where it goes
  8. bane builder[fail.constrain]

    turn its walls to [ ]

    • walls
    lands
    Not on the shelf yet.
    why
    what it holds becomes the lens
  9. bane builder{fail,constrain}

    hold the parts together

    • turn
    lands
    Not on the shelf yet.
    why
    commas keep parts apart and present at once
  10. bane builder{fail;constrain}

    hold the parts in order

    • turn
    lands
    Not on the shelf yet.
    why
    semicolons put the parts in a sequence
  11. bane builder{fail ~> constrain}

    make the parts a path

    • turn
    lands
    Not on the shelf yet.
    why
    ~> carries each part on to the next without collapsing them

projection where it goes

  1. bane builder{fail.constrain}<receipt>

    add receipt

    • add
    • common
    lands
    Not on the shelf yet.
  2. bane builder{fail.constrain}<china>

    add china

    • add
    • common
    lands
    Not on the shelf yet.

Constructs · Specimens · Take one line apart · Learn it a mark at a time