The Catalogue › The desk

The Catalogue · The desk

Send a piece

Send a piece to the desk. The house's robots read it first, a person reads it next, and the desk numbers it or sends it back with a note.

A machine is a workflow made into a thing that stands in someone's study: a script their switch runs on their own device, and a plain list of the files it touches. A fitting is looks, never code. A machine for minis is steps written out for a study's minis to follow (read this, ask that, put the answers there): words and no code at all. Once the desk numbers your piece it joins the Catalogue under your name, at your price in lead.

Nothing you send is shown to anyone but you and the desk until it has its number: not its name, not its words, not its pictures. A new version of a piece of yours waits here too, and the shelf keeps showing the version the desk read until it reads the next.

The jam's bounties
…

Send a piecea .zip: piece.json, run.py, tests/trial.json
How a machine is made
  1. Start from one the house made. Order the Week Roller or the Flashcard Press (free) and unzip its parcel: run.py, the kit (studykit.py, trial.py, guard.py), its trial in tests/trial.json, and manifest.json. That is a whole machine; change it into yours.
  2. Open files only through the study. study.read_text, study.write_text, study.tsv, study.write_tsv, study.shelves(): they open only what your touches name. The kit refuses the rest when it runs, and the guard refuses a machine that reaches around it before anyone reads a line.
  3. Write its trial. A small study, written out file by file, and the cases it must pass: the arguments, and what it says, writes, leaves alone. python3 trial.py runs them on a scratch copy; python3 guard.py reads your code the way the desk will.
  4. Say what it is in piece.json (below), zip the folder and send it. The robots answer at once; a person reads what they pass, at office hours when there are some, and the bay runs its trial on the house's machine before a number is given.
piece.json, a machine

      
A fitting is kind "fitting", with no run and no touches. A machine for minis is kind "pattern", a zip of piece.json and machine.json and nothing else: in your study, open a machine at its bench, change it, and Send it to the Catalogue packs the zip for you. It needs no trial, because nothing in it runs. Add "sealed": true to machine.json and the people who order it see what each stage is (a rule, or a model call and to which brain) but not its words; the desk reads every word all the same. To send a new version of a piece of yours, add "no": "1F101" (its number) and "changes": a line on what changed, which its page keeps with every version's.

    

    

      
tests/trial.json

      

      

    

  


  
What goes in piece.json, and the pictures

  

  
What the guard lets through

  

    
Imports

    
A little of

    
Neveropen, eval, exec, getattr, __import__, dunder attributes, frames, a sys.path of your own, a Path out of the kit (.root, .path, .parent), a network, another program. A file named like a module Python has, or like the kit, stands in for it, so it is refused too.

    
TouchesPaths inside the study ending ; never a way out of the folder, never code.

    
Size

  


  
The money

  

    
Your price

    
The seller

    
Your royalty

    
A numberIs never for sale, and no lead buys a listing, a plot or a storefront. Nothing here is XP.