WritingNov 16, 2025

A Quiet Start in Takamatsu with Fragment Practice

A bilingual studio note on moving to Takamatsu and starting Fragment Practice. It reflects on family rhythm, local life, Fragment System, and why a quieter pace made it possible to think more deeply about documents, AI, and structure.

5 min read6 core pointsBilingual
studio-lifelocal-lifefamilyhuman-aistructure

Article

A Quiet Start in Takamatsu with Fragment Practice

Since moving to Takamatsu, I feel as if the way time flows has shifted a little.

Back in Tokyo, my days were tightly packed with projects, commuting, and meetings. It felt less like “thinking inside daily life” and more like

“carving out thinking time away from life, somehow, somewhere.”

Now, my days look different.

In the morning, I go to the park with my kids. I work during the quiet hours around midday. By evening, I return to the rhythm of family life.

Between those moments, small fragments of thought drop in, one by one, and quietly accumulate in Fragment.

Because there is almost no commuting, little “pockets of blank space” appear throughout the day. Those pockets of slack feel like a surprisingly important ingredient in how I’m assembling Fragment Practice.


1. Why I started Fragment Practice

For about five years before starting the studio, I worked as a consultant focusing on security and IT-BCP, helping organizations with “defense” and “systems for continuity.”

At the same time, the longer I stayed close to real teams, the more a certain kind of discomfort grew:

  • Meetings and notes scattered everywhere; no idea where to begin
  • Documents that exist, but are neither read nor updated
  • Talk of “letting AI handle it,” while the underlying foundation is still unstable
  • No shared language or structure for building that foundation in the first place

Eventually, I arrived at a hypothesis:

“Maybe the everyday fragments and documents are actually the primary interface between humans and AI.”

Fragment Practice is a small studio I created to test this hypothesis quietly and carefully, not by scaling it up aggressively from day one, but by working at a scale that my own hands can honestly reach.


2. Life in Takamatsu, and the rhythm of thought

One surprising discovery after moving to Takamatsu was how directly the rhythm of life affects the rhythm of thought.

  • The way morning light enters the room
  • My children’s moods and health
  • The smell of wind and tide in the evening
  • The density of small domestic sounds in the house

Things like these subtly change the “depth” and “speed” of thinking in ways you can’t see, layer by layer.

The word rhythm appears often in the language of Fragment Practice, and that’s largely because of this change in my life here.

It’s not that the speed of the city is bad. But when I’m trying to work on the structure of thought, I’ve come to feel that these tiny gaps and gentle fluctuations matter more than I realized back in Tokyo.


3. What I’m thinking about while building Fragment System

The system I’m working on now, Fragment System, combines YAML and Markdown to make the flow of thinking and conversation easier to share with AI.

  • First, write as plain text
  • When needed, define “scenes” and “flows” with YAML
  • Make it possible to hand that structure directly to AI

It’s a quiet, somewhat unglamorous approach, but I’m aiming for a sturdy design.

Rather than “writing a brilliant one-shot prompt,” the work feels closer to:

co-designing the protocols and roles themselves.

This didn’t appear suddenly just because I “finally had time” in Takamatsu. It’s more of a condensed result of the tensions I felt in projects over the years:

  • More information, but harder decisions
  • Smarter AI, but meetings that don’t feel any lighter
  • Individual workloads remain heavy, while the systematization of knowledge and experience is constantly postponed

To untangle these contradictions even a little, I feel we need to translate “ways of writing” and “ways of thinking” into structures that can be shared with AI.

Fragment System is one attempt at that. Without the quiet time I’ve had in Takamatsu, I doubt I could have gone this deep into its design.


4. Relearning from family time

Living in Takamatsu has also changed how I relate to time with my family.

I sometimes write code while holding a child. I edit text while the washing machine runs. I jot down notes on a bench at the park.

There are more and more situations where life and work cannot be neatly separated.

Earlier in my career, I had a strong belief that:

“Without a solid block of time, I can’t produce solid output.”

But in reality, if I have a way to capture fragments of thoughts as they are and return to them later, then life and work don’t need to be strictly divided— and sometimes the whole system runs better that way.

What matters is not “perfect, uninterrupted time,” but:

  • A system that can catch fragments exactly as they are
  • A structure that makes those fragments easy to revisit later

The name Fragment carries this stance: to treat fragments with care, without forcing them into premature completeness.


5. Starting quietly, then slowly gaining momentum

It hasn’t been very long since we moved to Takamatsu, but Fragment Practice is slowly taking shape.

  • I’m shaping the studio’s website
  • Prototyping and actually using Fragment System in practice
  • Putting words to the early form of Prism Protocol
  • Leaving traces of the journey in essays like this ZINE
  • Continually adjusting my family’s rhythm and my work rhythm

If I had stayed in Tokyo at the same speed I was running before, I don’t think I would have had the capacity to work on this “structural layer” to this extent.

The pace I’ve chosen now isn’t flashy, but it feels like a pace I can keep for a long time.


6. A small greenhouse for thinking, so I can keep going slowly

For me, Fragment Practice is like a small greenhouse for thought.

  • Receiving everyday fragments with care
  • Not letting life and work pull too far away from each other
  • Increasing the strength of structure and protocol over time
  • Designing human–AI collaboration with care, not sloppiness

These are the things I want to keep testing within the everyday life of my family.

I expect the outline of the studio to keep shifting as I write more ZINEs and build more Fragments.

Rather than rushing to make it big, I’d like to move at a speed that feels sustainable, and keep layering things quietly— but steadily, and for a long time.

Continue reading

Continue through nearby entries

These entries sit close to the same line of thought. Continue reading if more framing is still useful.

Mar 22, 2026·12 min read

The Age of Personal Intellectual Ecosystems

A research note on personal intellectual ecosystems: connected systems where concepts, writing, products, advisory fit, public language, and operating memory reinforce one another. The piece explores why this matters in the AI era, and why it is different from ordinary personal branding or content strategy.

Mar 20, 2026·10 min read

When AI Was Useful, but Authority Was Unclear

A research note on a recurring human-AI pattern: AI looked useful, but the organization had not yet clarified where human authority should remain, where AI could assist, what should stay reviewable, and how those boundaries should connect to existing operations.

Mar 20, 2026·9 min read

Important Decisions Were Happening, but Not Being Held

A research note on why organizations can keep making decisions while still losing continuity, reviewability, and accountability. The piece examines scattered judgment, inbox-bound knowledge, fragmented memory, and the difference between communication and decision-holding.

Optional next paths

If the article surfaces a practical need, these paths may help.

The article can simply stand on its own. Use these paths only if reading made a product need, recognizable situation, service question, or inquiry clearer.

Optional path

Explore Knowledge

Use Knowledge if this entry points to a reusable product, working kit, or self-guided structure you can apply yourself.

Optional path

Explore Cases

Use Cases if this entry helps you recognize a pattern and you want to compare it with representative situations.

Optional path

Explore Services

Use Services if the issue is already active and you want to understand direct support shapes.

Optional path

Contact

Use Contact if the issue is real, but the right starting point is still unclear.

Next step

Keep reading, or move layers only when the need becomes practical.

Writing can stand on its own as public reasoning. If this entry points to a practical need, Knowledge, Cases, Services, and Contact remain available as optional next layers.