Computationally Yours · Handbook
Handbook · 13 · Documentation · Srishti Manipal Interim 2026

The daily log

One entry a day, in your own words, saying what the system did and what you decided. Over twenty days it becomes the record of how your identity's language was made.

seed log · depth 5
When
Every day, at pin-up
Length
Four fields, five minutes
Lives in
log.md in your repo
Filed
Form, by 3:30
Read by
You and the facilitator
01

Why log

A generative system is made of decisions, and most of them are forgotten by the next morning. The log keeps them.

It is the evidence that you, through your identity, authored the system: what Codex proposed, what you kept, and the reason your identity would choose one rule over another. At the end of the month it becomes the process section of your final submission, so nothing has to be reconstructed in the last week.

02

The entry

depth 2

Four fields, every day, in this order.

Field 1

Did

What changed in the system today. Name the rule, the parameter or the file, not just "worked on code".

Field 2

Decided

One choice you made, and why your identity would make it. This is the most important line.

Field 3

Image

One output from today, saved as log/day-07.png. A photo of a test or a plot counts.

Field 4

Stuck

One open question to start tomorrow with. If nothing is stuck, write what you are least sure of.

## Day 07 · Tue 1 Dec

**Did:**
**Decided:**
**Image:** log/day-07.png
**Stuck:** 

Write it yourself. You can ask Codex what changed in the repo today to jog your memory, but the Decided line has to be yours, in a sentence you could defend at critique.

03

Where it lives

The log sits in the same folder as your system, so you write it where you work.

your-identity/ ├── README.md ├── AGENTS.md ├── log.md one file, newest day at the bottom ├── log/ │ ├── day-01.png │ └── day-07.png ├── src/ └── outputs/

Add the day's entry during pin-up, then commit with the message log: day 07. The commit history then shows when each entry was written.

04

The 3:25 form

At the end of pin-up, paste the same entry into the daily form. That is how the facilitator reads all twenty.

  1. Open the form.

    The link is pinned in the studio WhatsApp group. Sign in with your @learner.manipal.edu account so your name is recorded.

  2. Pick the day, paste the four fields.

    Copy the text straight from log.md. Don't rewrite it for the form.

  3. Attach the image.

    The same file as log/day-NN.png.

  4. Submit by 3:30.

    If you miss a day, file it the next morning, dated for the day it describes. Don't save up a week and write it all at once; that record is worth less to you.

Only you and the facilitator see form entries. Three missing days in a row means a conversation, not a penalty.

05

At critique

On critique Fridays, bring the week's five entries printed on one A4 sheet, with the images small, and pin it beside your work.

  • Critique 1 · Day 5: Days 1–5. How the identity was found.
  • Critique 2 · Day 10: Days 6–10. How the system came to speak in that voice.
  • Critique 3 · Day 15: Days 11–15. What the material taught the system.

Reviewers read the sheet before you present, so your three minutes can go on the work itself.

06

Examples

The same day, logged two ways.

Useful
Did
Replaced the random walk with a flow field driven by Bengaluru rainfall, 1990–2024, one row of lines per year.
Decided
Line weight follows the rainfall deficit, not the total. The surveyor I am authoring records what is missing from the land, so thicker lines mean less water.
Image
log/day-07.png
Stuck
The plots read as weather, not loss. How do I make absence visible on the page?

A reader can follow the decision back to the identity's position, and tomorrow has a clear starting point.

Thin
Did
Worked on the code. Tried some data.
Decided
Changed the colours, looks better.
Image
None
Stuck
Nothing.

Nothing here could be recovered in three weeks, and "looks better" is a reaction, not a reason the identity holds.