Computationally Yours · Handbook
Handbook · 06 · Week 2 · Srishti Manipal Interim 2026

Write the rules

The generative system worksheet. Turn your identity's manifesto into inputs, rules, parameters and seeded chance, then let the system make twenty works that could only be its own.

seed system · depth 7
When
Days 6–10 · 30 Nov – 4 Dec
Starts from
Manifesto, Part E
Becomes
README.md · system.md
Outputs
20 in outputs/digital
Tested at
Critique 2 · Day 10
—

What a system is

A generative system is a set of rules that makes work you could not have drawn one piece at a time, all of it recognisably in one language.

1

Inputs

What comes in: data, a drawing, a text, time, or nothing at all.

2

Rules

The steps, in order. This is where the identity's position lives.

3

Parameters

The dials: values you can change without changing the rules.

4

Chance

Controlled randomness from a seed, so any result can be made again.

5

Outputs

Many works, each saved with the seed and settings that made it.

  • The rules come from the manifesto. If a rule has no reason in the identity's position, question it.
  • You can explain every line. Codex can write the code with you, but at Critique 2 you explain each rule in your own words, without the screen.
  • Image generation is not a system. Prompting an AI image model, on its own, doesn't count. Your rules have to do the work.
A

Metaphor to rules

Day 6. Start from the metaphor you kept in the identity worksheet (Part H) and the lines you marked in the manifesto (Part E).

B

The diagram

Day 6, due by 3:30. Fill the five boxes here, then draw the diagram by hand on A3, boxes and arrows, and photograph it to diagram/system.jpg.

C

Technique

Days 6–7, during the clinics. Choose the technique that best carries the rules. Mark one, or two if they work together. Each is explained, with a live sketch, in Computational techniques.

D

Architecture

Day 7. Codex as collaborator: ask for a plan before any code. Paste your Parts A and B where marked.

I'm building a generative art system. Here is what it must do:

[paste Parts A and B]

Before writing any code, propose an architecture:
- the files and what each one is for,
- every parameter in a single config, with a sensible default and range,
- one seeded random number generator used for every random choice,
- an export that saves each output with its seed and parameters in the filename,
- a way to make many outputs in one run.

Explain how each of my rules maps to the code. Keep it small enough that I can read and explain all of it. Wait for my go-ahead before you write code.

Same seed, same work

seed 41822 + params.json → the identical output, every time

Name every file by what made it

outputs/digital/ 007_seed-41822_cell-10_deficit-1.5.svg
E

Parameter table

Day 8, due by 3:30. Every dial in the system, with the identity's reason for it. This table goes in your README.

ParameterWhat it controlsRangeThe identity's reason

Eight rows here. If you have more parameters than that, you may have too many; if fewer than three, the system may not vary enough.

F

Twenty variations

Day 8. Twenty Variations of Myself. Run twenty seeds or settings into outputs/digital. How far can the system change and still be this identity?

G

Codex as critic

Day 9. Ask Codex to judge the outputs against the manifesto, then decide for yourself what to keep.

Here is my identity's manifesto:

[paste manifesto version 2]

Here are my system's rules and parameter table:

[paste Parts B and E]

I've attached [describe or share] my twenty outputs. Act as a critic, not a collaborator:
- Which outputs carry the manifesto most clearly, and which least? Why?
- What looks like the default of the technique rather than the identity?
- Which rule is doing the most work, and which could be removed?
Don't suggest new features. Don't rewrite my voice.
H

Toward a material

Day 10. After Critique 2, choose your pathway. One medium is enough; no one has to make all three.

The one-page production plan is due by 3:30 on Day 10. Machine slots are booked from Day 11; see Machines.

—

Ready for Critique 2

Critique 2 asks: Does the system speak in the identity's voice, or could anyone's rules have made this?

Bring: the running system, 20 outputs, the parameter table, the authorship log, and the week's log on one A4 sheet.

—

A worked example

Anjana Rao's system, from the identity and manifesto examples. Abridged.

The deficit survey

Example
Metaphor
The survey grid as a sieve: each cell keeps the water that should be there.
Inputs
Annual rainfall for Bengaluru, 1990–2024 (CSV). One tank's boundary, traced from an old survey sheet as a polygon.
Rules
  1. Lay a survey grid over the tank boundary.
  2. For each year, take the deficit: the long-run mean minus that year's rainfall.
  3. Give each year one row of horizontal lines across the tank bed.
  4. Draw each row heavier as the deficit grows; years with surplus are drawn faintest.
  5. Stop every line at the boundary. Nothing is drawn outside what was measured.
  6. Write the year and the data source in the margin beside each row.
Parameters
NameControlsRangeReason
cellgrid size5–20 mthe scale a surveyor would walk
deficit_scalepen passes per 100 mm of deficit0.5–3absence drawn heavier than presence
jitterline wobble0–0.4 mma hand, not a machine
yearsfirst and last year1990–2024the span of the records
Chance
Only the jitter is random, from the seed. The data is never randomised: "no water I have not measured."
Technique
Data as material, on a geometric grid. Avoids the default by refusing colour and gradients.
Material
A2 pen plot. The pen's repeated passes make the deficit physical: heavier years are literally more ink.
Answers save in this browser