NODE: yoru.space OPERATOR: Yume / callsign "yoru"

Signals In The Concrete Nocturnal Reconstruction Terminal

This node belongs to Yume—bar owner, late-shift tinkerer, half in the real city, half in the networks behind it. It isn't a finished portfolio; it's a rebuild in progress. A quiet interface watching the streets and slowly piecing itself back together from digital fragments: stray ideas, future projects, half-formed worlds. Think 3 AM ramen in a corner booth, wet asphalt outside, ghosted GitHub tabs, and Ghost in the Shell reruns humming from another monitor.

Case Files

Future Investigations / Empty Drawers

No shipped projects yet—only labeled slots. Each card is a memory-shaped placeholder, a hint at what this node wants to become once Yume has time and quiet between shifts.

CASE #01 / YORU-HUB
Fragmented · Not deployed
Portfolio · Core Node
Intended form: signal index

This file will track everything that actually ships: tools, writeups, and small worlds that start as notes on the bar counter after close. Today it's just a drawer with a nameplate, waiting for its first real piece of evidence that the operator builds things, not just atmospheres.

Planned stack: HTML · CSS · JS Slot reserved · 01
CASE #02 / NIGHT-LAB
Draft-only · Internal
Experiments & Prototypes
Intended form: glitch lab

A sandbox for broken UI, half-finished systems, and game fragments that only make sense at 02:47. Most of what lands here won't be pretty, but it will be honest—fragments of learning and tinkering instead of polished case studies.

Focus: Play & Practice Slot reserved · 02
CASE #03 / SIGNAL-LOG
Offline · Timeline empty
Writing & Devlogs
Intended form: narrative stream

A chronicle of what doesn't fit in a resume: false starts, reworks, nights when the bar is quiet enough to code, and small wins measured in “this finally feels right”. Each entry a fragment of how Yume sees tech, cities, and late-night building.

Format: Posts · Notes Slot reserved · 03
Dossier

Subject Record: Fragmented Operator

Less a full bio, more a reconstruction log. As projects land, this profile sharpens; for now, it's a series of tags, habits, and glimpses through neon glass.

Fragmented Profile
Yume / Callsign: yoru
Bar owner by day · nocturnal operator by night · slow-burn worldmaker
In the streets, Yume runs a small bar that collects people's stories. Online, under the callsign yoru, the same habit turns into code, interfaces, and small digital worlds. yoru.space is the link between the two: a side-channel to real life, a place to stash ideas, half-built tools, and quiet stories while the rest of the city works nine-to-five.

Not everything here will be finished. That's the point. This node respects work-in-progress energy—all the sketches, rewrites, and abandoned branches that never show up on official timelines but still shape how someone thinks and builds.
Known Activity
Serving drinks, listening to stories, sketching interfaces, studying networks and security, and slowly turning concepts into things other people can touch.
Last Seen
Location: bar back room / digital backstreets · Time: 03:xx · Status: headphones on, editor open.
Signal Outposts
GitHub: @yumedayou · more links will surface here once they feel like home, not noise.
Long-Term Plan
Turn this node from vibe into evidence: a portfolio full of shipped fragments— games, tools, interfaces—each one carrying a bit of this city-at-3 AM energy.
Incident Report

What Happened to the Old Network?

The story isn't fully documented, but there was a break: old nodes went dark, projects stalled, and this space came online as a recovery terminal instead of a finished showcase.

Filed internally · not yet disclosed
INC / “The Cutover”
There wasn't a single dramatic crash—no sirens, no red screens. Just a gradual drift: old plans stopped making sense, shifts at the bar got heavier, and the old idea of a neat, finished portfolio stopped matching the way Yume actually moves through the world.

So instead of resurrecting a dead layout full of projects that never shipped, Yume did something simpler and stranger: spun up yoru.space as a quiet, neon-lit buffer between “not yet” and “finally done”. A terminal you might find in the back of the bar, tracking fragments first, outcomes later.
Diagnostic Snippet
System Snapshot · Post-Event
The monitoring tooling isn't fancy. It's just honesty: late nights, limited energy, real life obligations, and an urge to build anyway. The incident isn't a disaster—just the moment where Yume admitted that slow, atmospheric, imperfect progress still counts as signal.

This node exists to catch that signal, even if it's just one fragment at a time.
Impact Old portfolio plans: archived · New node: online
Recovery In progress · paced by real life and ramen breaks
Visibility Public, but feels like you're early to the scene
Status Accepting new fragments · awaiting first shipped case
Field Reports

Logs From the Perimeter

Not full essays. Just timestamped fragments from around the edge of the network: setup notes, mindset shifts, and quiet milestones you can scroll through like old chat logs.

2025-11-19 · LOG 01
Yume spins up yoru.space as a reconstruction node instead of a portfolio
Setup Reframing Fragment: 01
2025-11-XX · LOG 02
Choosing which small project becomes the first “real” case file
Planning Triage Fragment: pending
20XX-XX-XX · LOG 03
Shipping under neon rain · turning a fragment into a world
Milestone Memory
Secure Line

Open a Channel to the Operator

For now, this is a static console. Later it can wire up to email or a tiny backend; today it's just a way of saying: you're allowed to reach out, even while the site is still a fragment.