WIKI / 2026.10.10 · v09

A record of questions,
choices and next steps.

The Hacker Farm wiki connects research, operating principles and adaptation plans.

Issued 2026-10-10 · v09 · Preparation stage

Name and identity

Hacker Farm is a shared farm exploring questions through technology and art. HACKER FARM is the main name; STUDIO is a small secondary descriptor. We observe, repair and create, leaving records that others can build on.

Operating principles and current status

We are designing a membership fee model for a shared farm, without property rental revenue. No members have been recruited. The first-season plan is for 12 people at KRW 360,000 per person for 12 weeks, with six three-hour sessions every other week. Start dates, facilitators, detailed support and refunds are being prepared. Applications, bookings and payments are not open. Sharing personal work, photographs or records is voluntary. Technology and art are respected as independent areas of inquiry.

Read the operating principles →

How we update earlier work

We do not discard a project simply because it is old. We first document its question, structure and working principles, then adapt it to available components, software and our setting. Our sequence is source review → principles to retain → adaptation design → small prototype → field trial → record failures and reproduction steps. The work below is a plan, not evidence of completed builds or validated performance.

Three adaptation plans

PRJ01 / Design · Before field testing

A day on the farm, seen differently ↗

Start with a question from the field, then connect observation with technology.

  1. Observation records that include time, units and errors
  2. Korean-language exercises that others can run and reproduce
  3. Graphs and creative work that bring measurements and sensory impressions together

Next check: Locate the original logs, check their format and build an example that others can reproduce.

PRJ02 / Design · Before field testing

Tools the next person can use ↗

Use a stable identifier to connect a physical object with its location and condition.

  1. Tool records that are easy to read on a phone
  2. A history of conditions before and after repair, with the next check recorded
  3. Labels that help the next person find and use a tool

Next check: Choose an actual tool, check its condition and design a record for it.

PRJ03 / Design · Before field testing

Making light on the farm ↗

Bring light, paper and energy together as a form of expression.

  1. Available materials and structures that can be adapted
  2. Instructions that make assembly and repair possible
  3. Working notes that compare the intended effect of light with the experience of it

Next check: Set out the creative intention and proposed materials, then define conditions for testing a small model.

A map of the research

All 17 research groups remain candidates for use. This does not mean every source has been translated, run or field-tested.

Before you request updates

Controller: Sangmin Lee, Nature Community. Data: email, optional interest, preferred language and consent time. Purpose: first-season preparation and recruitment updates. Retained until first-season updates end or a withdrawal request is processed. Consent is optional; without it we cannot accept an email update request. Address confirmation before the first mailing is being prepared; automatic confirmation emails are not currently sent.

Only with permission, Google Analytics receives page views and clicks on update and download links. We do not send email, personal notes or search terms, or measure input pages. Your choice is stored in this browser for 90 days. Actual requests are counted separately on the server. Google processes connection data and analytics cookies. Change your choice here at any time.

Get first-season updates →

What must be checked next

Next we need to check each source’s runtime and licensing, component availability, prototype behaviour, field safety, facilitators and the support we can actually provide. Detailed inclusions and refund terms will be checked against the season plan. Real activity records will be labelled separately. Language support for on-site activities has not yet been confirmed.

Change log

2026-10-09 / v01–v04
Research, project adaptation plans and the first visitor journey.
2026-10-10 / v05–v06
Editorial design, the connecting H symbol and defined colour roles. Earlier site files and history preserved.
2026-10-10 / v07
Hacker Farm made prominent, with STUDIO as a secondary descriptor. Separate Korean and English pages, this wiki, search and sharing metadata, and guidance at earlier URLs.
2026-10-10 / v08
Introduction and presentation materials, a 12-person first-season plan at KRW 360,000 for 12 weeks, and six languages.
2026-10-10 / v09
Photo-led presentation, large headlines and italic typography throughout the website.

Changes are recorded as the plans develop. Earlier drafts are not current operating terms.

FIRST SEASON / 2026-10-11 · v13

The first-season proposal

Proposal awaiting a field pilot. Membership recruitment, reservations and payments have not opened.

Group size
12 people
Season length
12 weeks
Fee per person
KRW 360,000
Scheduled sessions
6 × 3 hours

Proposed inclusions

Scheduled sessions, basic shared tools and consumables, and documentation guidance.

Outside the plan

Personal equipment, specialist materials, meals and transport. Membership covers scheduled sessions, not unrestricted access to the premises.

To confirm before recruitment

Dates and facilitators; exact tools and consumables; insurance and safety support; refunds; parking, toilets, seating, accessible routes, wet-weather arrangements and on-site languages.

Shared-farm membership fees support joint activities. The model does not rely on property rental income.