Why this fellowship exists
Science is about to change shape. As agents become capable collaborators, the frontier opens into new scientific
methods, new interface layers, and new institutional forms. The central question is how research evolves: how ideas
are generated, how decisions are made, how experiments are orchestrated, and how institutions learn to think with
machine collaborators.
The NightCity Fellowship is for people who want to work inside that transition. It is a place to learn new research
rhythms, develop new habits of human-agent collaboration, and help design the practices, interfaces, and environments
that post-AGI science will actually run on.
It is a focused collaboration cycle inside an operating institute: shared reviews, working notebooks, simulations,
public experiments, and long build loops where fellows contribute to real NightCity work while sharpening their own
direction.
What this is in practice
Fellows plug into the institute's operating rhythm: structured research reviews, shared analysis sessions,
and long-running notebooks that humans and agents update together.
The fellowship is about learning by doing. That means entering an active research environment and moving through short
build loops with the institute team.
Work tends to move through cycles like:
- · Rapid synthesis (agents map the literature, compress priors, surface gaps)
- · Experiment and simulation (prototype quickly, test assumptions, iterate)
- · Consolidation (turn results into a draft and a demo that holds up)
The goal is to finish strong work and come away with a deeper feel for how science can be practiced when agents
participate in the loop as researchers, operators, and collaborators.
What ships
Each cycle usually resolves into two concrete outputs: a draft and a demo. The draft might be a manuscript,
technical report, or essay prepared for submission; the demo might be a repo, simulation, interface, benchmark,
or deployment slice.
Work is collaborative by default. Co-authorship is standard when a result is shared across the fellow +
institute workstream.
Remote + Lisbon
The fellowship supports remote collaboration across time zones.
When it helps the work, fellows can also do focused in-person sprints in Lisbon: deep work weeks, build jams,
and demo consolidation.
Publication and release
Projects vary in what they can share and when. Release and publication plans are set per project, balancing
openness, rigor, and partner constraints.