FINAL DESIGN · 2026.07.22

Do not make them
fall in love.
Create a place where love can begin.

ROOMMATES is a seven-day life simulation about watching hiro and Aoi live together. You cannot command them. You can only give their guide, Dekopin, a small nudge to pass along.

7DAYS
28MOMENTS
2INDEPENDENT MINDS
The final Day 3 game screen showing the full 2LDK apartment, hiro, Aoi, resident status, and the prompt field for Dekopin
SCREEN 01Watch two lives unfold across the entire 2LDK apartment

Not getting exactly what you want
is what makes the story.

The player is never guaranteed a preferred outcome.

ROOMMATES IN 30 SECONDS

From controlling characters to watching over them.

The goal is not to find a perfect strategy. The core experience is deciding how much room to leave for two people to make their own choices.

01

Do not move them directly

The player cannot decide where they go or what they say. Their life belongs to them.

02

Offer only a nudge

Suggest something like “How about making dinner together?” to Dekopin—or simply keep watching.

03

Let them choose the outcome

They may accept, decline, modify, ignore, or initiate. Affection alone never forces romance.

Pixel animation of hiro walking in a blue shirt

WEB ENGINEER · 27

hiro

A little nervous, he is trying to find a comfortable rhythm in a new shared home.

Pixel animation of Aoi walking in a coral outfit

GRAPHIC DESIGNER · 26

Aoi

Excited by the new start, she is looking for natural moments to connect.

Pixel animation of the floating guide Dekopin

LIFE NAVIGATOR

Dekopin

A guide who receives your words and delivers them as safe opportunities—not commands.

WHAT HAPPENS IN ONE TURN

One sentence becomes one moment of life.

hiro and Aoi see the same room and emotional context, then decide independently without seeing each other's answer. Their choices are finally resolved into one coherent event.

STEP 1

Your words

Suggest a small opportunity

STEP 2

Dekopin checks

Shape it into a safe event

STEP 3

Two separate choices

Same moment, independent minds

STEP 4

An event happens

Resolve and record both choices

STEP 5

Life remembers

Update state, relationship, and memory

INDEPENDENT DECISIONS

“No” and “not quite like that”
are both valid story choices.

Every turn, each resident chooses one of five directions. Sometimes only one joins in. Sometimes both decide to rest.

AcceptACCEPT
DeclineDECLINE
ModifyMODIFY
Do something elseIGNORE
InitiateINITIATE
The final Day 3 event details where hiro declines while Aoi modifies the same suggestion
SCREEN 02 One suggestion, two different choices

DESIGNING SEVEN DAYS

Morning, noon, evening, night: 28 small moments.

A relationship is not decided by one dramatic event. It grows through small choices: resting, talking, missing each other, apologizing, and trying again.

DAY1
AMNOONEVENIGHT
DAY2
AMNOONEVENIGHT
DAY3
AMNOONEVENIGHT
DAY4
AMNOONEVENIGHT
DAY5
AMNOONEVENIGHT
DAY6
AMNOONEVENIGHT
DAY7
AMNOONEVENIGHT
TIER 0Watch or restAlways available
TIER 1Cook, watch, clean, talkEveryday opportunities
TIER 2Apologize or give a small giftAfter trust has grown
TIER 3A place to share feelingsOnly after Day 4 and when conditions are met

THE 2LDK THEY SHARE

The floor plan itself tells the story of their distance.

The living room and kitchen create chances to meet. Two private rooms preserve the right to be alone. The home makes both closeness and distance visible.

Floor plan of the 2LDK apartment with private rooms, living room, kitchen, bath, and balcony
⌂

Shared spaces

Places for conversation, cooperation, and chance encounters.

▣

Two private rooms

Places to decline, rest, think, and preserve personal space.

☀

Time of day

The same room offers different possibilities in the morning and at night.

↔

Fixed anchors

Residents currently move to event locations; free walking is a future idea.

STATE, RELATIONSHIP, MEMORY

Events do not disappear. They become context for the next choice.

Every turn updates the residents' condition, relationship, shared memories, and life log. Important moments can later be read as a complete article.

The final Day 3 memory article showing both residents' choices and reasons
SCREEN 03 Turn a passing moment into a readable memory
★EventEVENT
⚡Energy
!Stress
♥Affection
◆Trust
♡Romance
✦Memory

WHAT REMAINS AFTER SEVEN DAYS

Their ending and the way you supported them are judged separately.

The player is not scored on whether romance happened. The review asks what kind of environment you created while respecting both residents' autonomy.

The final result screen after seven days, showing the residents' ending and a separate support score for Dekopin
SCREEN 04 Their ending is theirs. The score is about how you helped.
DEKOPIN SCORE100POINTS
Respect for autonomy25 pts
Psychological safety25 pts
Care for the relationship20 pts
Pacing15 pts
Narrative richness15 pts

Romance is not a direct bonus. The score rewards respecting refusal, avoiding pressure, and supporting a story that feels like theirs.

HOW AUTONOMY STAYS SAFE

AI proposes. The game rules decide.

The resident agents and event director can make suggestions, but they cannot rewrite the world directly. The game engine checks consent, conditions, and numerical limits before saving anything.

PLAYERYouOffer a nudge
GAME VIEWGame screenA window into their life
SAFE CUEInput safety checkShape a usable event
INDEPENDENThiroChooses for himself
INDEPENDENTAoiChooses for herself
COORDINATEEvent directorResolve both choices
FINAL AUTHORITYGame engineValidate, update, save
01

Shape the input

Detect dangerous, coercive, deceptive, or system-directed requests and replace them with safe conversation or rest.

02

Share the same moment

hiro and Aoi receive the same state. Neither sees the other’s answer before deciding.

03

Protect refusal

Declining never secretly increases relationship values. Two-person events cannot happen with only one participant.

04

Validate the result

Clamp every value to 0–100 and recheck event changes and relationship conditions before saving.

INFORMATION BOUNDARY

Show only actions, dialogue, and shareable reasons.

Raw reasoning is neither displayed nor stored. The system keeps only the records needed to trace what happened.

✓ STORE
  • Safety-shaped suggestion
  • Actions and dialogue
  • Shareable reasons
  • Before/after state and life log
× DO NOT STORE
  • Raw reasoning
  • Internal summaries
  • Unaccepted predictions
  • Internal data unnecessary for the UI

CURRENT RUNTIME

How the public and local builds run

Both use the same game rules. The public build uses live AI; development can use Codex App Server or a safe deterministic fallback.

PUBLIC SITE

Production demo powered by GPT-5.6

A Cloudflare Worker advances the game and D1 stores one state per browser. Navigator, hiro, Aoi, and Director use GPT-5.6 Terra, with role-level safe fallback on failure.

React / ViteWorkerD1GPT-5.6 Terra
LOCAL DEVELOPMENT

AI connection with safe fallback

Codex App Server can run separate tasks for hiro, Aoi, and coordination. Only a role with a connection or output failure switches to fallback.

React / ViteExpressJSONApp Server / Mock

WHERE THE PROJECT STANDS

Separate what works now from what comes next.

This guide describes the current implementation. Planned improvements and longer-term ideas are listed separately.

NOW · IMPLEMENTED

What you can experience

  • Watch the 2LDK and suggest free-form or example prompts
  • Five independent choices for hiro and Aoi
  • State, relationship, memory, and life-log updates
  • Morning, noon, evening, night for up to 28 turns
  • Synchronous ×8 auto-advance
  • Four independent GPT-5.6 roles
  • Ending, recap, five-axis score, and full log
NEXT · DESIGNED / IN PROGRESS

What we want to improve

  • Move fast-forward processing into the background
  • Add progress, cancellation, and restart recovery
  • Search and summarize long-term memory
  • Add more relationship events and endings
FUTURE · CONCEPT

What is not available yet

  • Multiple users or account synchronization
  • Free walking, pathfinding, or furniture collision
  • Schedules that influence agent decisions
  • Save slots or comparison across past seasons

Final public build verified on July 22, 2026

Optimized for a short desktop demo. The public build uses one anonymous browser session with no sign-in, cross-device sync, or ranking.

QUALITY · ALL GREEN

618 automated tests

  • 548 server tests
  • 70 web tests
  • 0 known production dependency vulnerabilities
LIVE · VERIFIED

All four roles use live AI

  • Navigator / hiro / Aoi / Director
  • GPT-5.6 Terra explicitly configured
  • Production turn completion and persistence verified

PLAIN LANGUAGE GLOSSARY

A few friendly definitions

Agent

A decision-maker that acts as hiro or Aoi, reads the situation, and chooses an action.

Director

The coordinator that turns two independent choices into one consistent event.

Snapshot

A fixed package of the residents’ state, relationship, and memories at one moment.

Mock / fallback

A repeatable way to continue the same game rules when an external AI is unavailable.

SSE

A live update channel that reports the progress of Dekopin, both residents, and the Director in order.

D1

The database that stores one public game state for each anonymous browser session.

ROOMMATES · AUTONOMOUS LIFE SIM

Let their choices
belong to them.

You do not write the script. You create the space in which a story can emerge.

Play the current build