DEV Community: machuz

When AI writes a thousand lines a minute, which code actually holds? (Launching OrbitLens Ace)

machuz — Tue, 30 Jun 2026 19:35:24 +0000

AI can write infinite code. Whether it lasts is a different question.

Every git repository holds two records.

One everyone reads: the commit log, PR counts, lines changed. Activity. Who moved a lot.
One almost nobody reads: whether a line of code is still standing six months later, and who its blame finally resolves to. That one is structure.

Management usually watches the first and gets blindsided by the second. "If she leaves, nobody understands that subsystem." That collapse was written in the second record the whole time. We just weren't reading it.

Why surviving code

Activity can be inflated. Split the commits. Let a lockfile add a few thousand lines. Pad the PR count. Busyness is easy to perform.

Survival is not. Whether your code outlives you isn't something you can fake overnight; it takes months to know. A typo fix and an architecture change are both "one PR," but the code still standing half a year later can't lie about which was which.

EIS is an open-source CLI that reads exactly that layer. git log and git blame, nothing else, observed across 7 axes and 3 topology dimensions, printed as JSON. No external API, no AI tokens. brew install, run eis. Every formula sits in the whitepaper, so nothing is hidden inside.

AI made activity meaningless

The speed of writing code left human hands. Ask a model and a thousand lines arrive in minutes. Commit counts and lines changed no longer measure how much a person moved; they measure how much a tool moved. Activity metrics were always shaky. AI finished them off.

What's left is what survives. Of the thousand lines AI just produced, the share that gets rewritten next week has a survival of zero. Only the code still standing in six months is doing structural work. When generation becomes infinitely cheap, the scarce thing isn't output. It's what stays.

And there's a quiet trap here. If you never grasp how much of your code actually survives, and you keep handing everything to a model without regard for structure, the codebase thickens with layers that get rewritten the following week. Generation is fast, yet the features never settle. And because the commit log keeps flowing along nicely, no one notices the team is circling the same ground. A team that can't read survival stays inside that churn until it turns into an incident.

And survival can't be gamed, not even by AI, because time isn't the only thing that decides it. Whether a piece of code lasts is settled by the ecosystem it lands in: whether the next person builds on it or tears it out. The other developers' hands give the answer. So it isn't an absolute ruler. It shifts by environment. A conservative team might keep mediocre-but-bug-free code untouched; an aggressive one might throw the same code out by next month. Survival is a relative signal, valid only inside that particular context.

And the code that survives surfaces as accumulated history: what it set out to solve, what got built, in what structure — a record of having faced those questions with real heat.

But that is exactly why you can't fake it. It isn't self-reported and it isn't volume; it's the accumulated choices of everyone around you. And someone whose code survives across many different contexts is probably someone who can genuinely design. A lucky fit to one environment's habits doesn't explain that.

Observation is also the opposite of generation. The more the world fills with AI-written code, the more valuable an instrument that just reads the facts already cut into the ground. EIS uses no model. It doesn't infer, so it can't hallucinate. It reads what git already wrote down. In an age of generation, it stays an instrument of observation.

But read it wrong and it breaks

The moment you read the survival signal from above and put a number next to a name, it becomes a scoreboard. And a scoreboard always distorts what it measures. People start optimizing the number, and the texture of the work flattens underneath it. Engineering metrics die right here, turned into ranking and pressure.

So the question was never "can you read structure from git." It's "can you read it without dropping into evaluation." The instrument that gathers the signal isn't enough. How you read it decides whether it helps or harms.

That is why EIS and Ace are two instruments, not one.

EIS is the telescope. It observes. It reads git and returns signals. No recommendation, no prediction, no evaluation. It stays with the facts.
Ace is the observatory. It reads the observation. But into a chronicle, not a ranking.

If the instrument that gathers the signal also decides what it means, you can no longer tell where fact ends and opinion begins. Keep the telescope on the facts and let the observatory carry the interpretation. You can trust both because there is a line between them.

The telescope observes; the observatory reads. The line is drawn right there.

What the observatory reads

Read these as the structure git was hiding, not as a feature list.

Structural Summary. Numbers into language. "Survival 23" on its own is useless. Weak design, or a legacy rewrite in progress? Ace reads the whole signal field and tells you, in prose, what's standing and what's coming apart.

Structural Summary — turning the numbers back into prose.

Conway's Law check. Org chart vs. reality. Ace places the engineer topology next to the module topology and shows where they drift. The team that supposedly owns a service isn't the team writing it. Knowledge quietly migrated somewhere your org chart never noticed.

Collapse risk. Before it's an incident. Modules that survive only because nobody touches them. Modules orphaned when an owner left. A bus factor of one. The risk was in the git history from the start. Ace surfaces it before it turns into a crisis.

Conway Check & Collapse Risk — the org chart next to who actually wrote the code, and the orphaned knowledge found before it becomes an incident.

The Organizational Chronicle. Time, not a ranking. Not a scoreboard. It doesn't rank engineers. It records what the codebase has lived through: the migrations it survived, the architect who shaped a subsystem and moved on, the module that turned fragile after an ownership change.

Chronicle — not a ranking, but the time a codebase has lived through.

A scoreboard teaches people to game it. A chronicle is something a team grows attached to. We're after the second. The signal is still there if you want to look closer, but it's a lens you pick up, never the headline.

A worked example: point the telescope at React

To keep this concrete, here is one result from pointing the telescope at a public OSS codebase.

One note first. In this piece the individual names behind the observations are withheld. A name appears only when that person cooperates with OrbitLens Ace's public research and claims their name — anonymous by default, disclosed only by the person's own choice.

Star Detail — all-time gravity and the trajectory: the same person read at two focal lengths, one toggle apart.

In React (1,927 engineers passed through it), the top of the all-time gravity is one engineer. Indispensability 100, Catalysis 100: the structural shape is saturated, everyone else built on top of them.

Open the timeline and the depth shows. From 2013 he held React's structural seats again and again — Specialist in 2016, Producer in 2022, Architect and the year's #1 in 2023 (gravity 89), Anchor in 2025. He moved between roles but stayed near the structural center for a decade, and anchors several modules. The Reconciler he laid down is still load-bearing in React today.

And yet his live Gravity reads a modest 9.9. Gravity measures robust survival — the structure others are still actively pressing on right now. The foundation he laid has gone quiet — no one is actively pressing on it now (robust survival near zero) — so Gravity, which measures the influence that is live right now, reads him soft. That isn't a demotion. It's the instrument declining to confuse a finished foundation with live gravity, and his decade is right there in the timeline.

There is another honest way to read all-time. Measure it not as "the gravity live right now" but as "the lasting structure left behind" — swap the survival gate from robust survival to raw survival (lifetime gravity) — and the same person climbs back near the top (~74). Is the system leaning on you right now, versus what did you leave that still stands: two questions, two answers. EIS now carries this second gravity as a versioned, additive companion.

There's a kind of gravity the live number can't fully catch: the foundation the next generation rebuilt on top of. Another engineer's work is that kind. They worked on huge parts of React's modern internals — hooks, concurrent features, Suspense. Much of it was later built over by what came after, and because EIS reads surviving structure, a foundation that's been built upon reads quiet. But that quiet is the point. Being rewritten isn't failure — it often means the work became the foundation the next generation stands on.

And the timeline doesn't forget. It still records who held the architect's seat, season by season; the lines can be overwritten, but the record that you carried the structure is not. Every architect is rewritten in the end — and when it happens, the chronicle remembers that you held the seat.

And in Ace you don't choose between the two — you read the same person in both, one toggle apart: the all-time footprint (the structure they left) and the trajectory (the seasons they carried it). For that second engineer, both are there at once — the foundation that's been built upon, and every season they held the architect's seat. Pull the telescope back for the whole, lean in for one era — the same universe at two focal lengths.

A leaderboard parks the famous and the first at the top forever. EIS doesn't — but open the timeline and who held the structure, and when, is preserved in full. In that same React, the all-time top-10 overlaps the GitHub maintainer list by only 60%. The rest are people without the title, whose code the system still rests on.

Two doors, one universe

The telescope (open source) is completely free. It runs locally by design: no account, no login, no integration. brew install, point it at a repo.

brew install machuz/tap/eis
cd your-repo
eis analyze .

The observatory (SaaS) is a few clicks. Open ace.orbitlens.io, log in with GitHub, pick the repos you want to watch. From there Ace runs the observation continuously and renders it in your browser: structural summary, Conway check, collapse risk, the chronicle. No CLI to learn.

Two doors. The same universe — from the command line, or from the browser.

Point the lens at your own organization, at your personal repos, at an open-source project you're curious about. Public repos are unlimited, so reading the gravity map of a well-known OSS codebase is worth a look on its own.

EIS, the telescope, stays free and open source forever. No seat limits, no trial clock, no open core with the load-bearing parts behind a wall. We don't want to charge for the idea. We want it to travel, and an idea behind a paywall doesn't get far.

Ace, the observatory, is what carries a price, because running observation continuously and reading it back is real infrastructure. It's priced to be reachable, not to gate. Free at $0 (up to five people, public repos unlimited, six months of history). Pro at $7/mo (one developer, full history, the complete Gravity Certificate). Nova at $39/mo for eight seats, plus $18/seat beyond, for a private org that wants the org-level read. Most engineering-analytics platforms run $15 to $50 per developer per month, often behind "contact sales." Ace is flat for the first eight seats, and the engine beneath it is free. The Gravity Certificate, the trace that travels with a person, is free to mint and verify on every plan. Proving your own work shouldn't cost you anything.

From Free to Nova — the engine is free; only the observatory that keeps reading carries a price.

One honest thing

There's a failure mode we sit with. The moment engineering gets measured from above, the way an organization surveys its people, what the people on the ground actually feel tends to flatten. A number arrives, and the texture of what someone did disappears under it.

We're trying to build the opposite, and we're not sure we've managed it. Signals are signals, not verdicts. The things git can't see, we don't measure, and we say so out loud: mentoring, the design argument that never became a commit, the calm someone held during an incident. That's the dark matter the telescope can't reach. A low signal isn't a small contribution. More often it's a signal about the organization, not the person.

Measuring people is dangerous even with good intent, and we haven't found how to do it without ever diminishing the frontline's own sense of its work. So this is a real request. If you read your own signals, or your team's, and something feels off, flattened, unfair, missing the thing that actually mattered, tell us. That gap is where the instrument has to get better.

Why we observe at all

Read this from one end and a single thread runs through it. People leave. Organizations reshape. Tools change what a thousand lines cost. The one thing that has to outlast all of it is what the people who were here understood — and almost none of that lives in anyone's head. It lives in the code, but only while someone can still read what the code remembers.

That is what observation is for. Not to score the people who are here, but to keep what they knew legible after they're gone, so the next person inherits structure instead of a mystery. We don't protect people — people move on, and they should. We protect knowledge. A signal that ranks is forgotten the moment its subject leaves; a chronicle that records is the first thing the next owner reads.

So the soul of this isn't measurement. It's observation in the service of succession. A culture of observation is a culture of succession.

And this record isn't only the organization's. What you left in git isn't self-reported and it isn't volume — it's the fact that others kept building on your code. When a company you've since left runs Ace, the observation of your time there accrues to your own certificate — a career chronicle made of facts, not a résumé you wrote. Whether any of it is public stays your call.

→ The wider arc — observation, understanding, succession, the design of the next orbit — is the OrbitLens Vision.

GitHub: eis — the telescope, fully open source.
Observatory: ace.orbitlens.io
Library: library.orbitlens.io — the theory and the shelf behind EIS (Git Archaeology, whitepaper).

If this was useful: Sponsor on GitHub

Inside OrbitLens Ace: A Tour of the Observatory

machuz — Tue, 30 Jun 2026 19:35:23 +0000

Every screen answers one question: what becomes observable here?

OrbitLens Ace is the observatory built on top of EIS, the open-source git telescope. The telescope observes: 7 axes, 3 topology dimensions, printed as JSON. The observatory reads that observation back as structure you can see.

This is a tour. Each screen below is a live galaxy in Ace, with the organization name and private module names redacted. The structure is real; the identifiers are blurred. For each one, the only question is: what becomes observable?

The Observatory Dashboard: 7 axes at a glance

The dashboard is where the light lands first. Every observed engineer sits on the same 7 axes: Production, Catalysis, Survival, Design, Breadth, Debt Cleanup, Indispensability. The shape of a contribution becomes visible at a glance, not just how much of it there was.

Now that AI writes a thousand lines in minutes, a commit count measures the tool more than the person. So the axes that hold shape rather than volume matter more, not less.

What becomes observable: who shaped the structure versus who generated volume. An engineer with 1,890 commits and a Survival near zero looks busy on a commit graph and quiet here. An engineer with 82 commits but Design at the ceiling stands out. The axes hold a difference that a commit count flattens.

Star Detail: the radar, the insight, the structural summary

Focus the telescope on a single star and the 7 axes open into a radar. Around it sit the engineer's topology classification (Role, Style, State) and a Structural Summary written in prose.

The summary is what to dwell on. Numbers without context invite misreading. A low Survival might mean weak design, or it might mean the engineer is mid-rewrite of legacy. The summary reads the whole signal field at once and describes what's actually standing. Light turned into language.

What becomes observable: not "how good is this person," but what kind of trace they left in this particular universe of code. A Cleaner who guards integrity reads differently from a Producer who generates volume, and the radar shows the difference rather than collapsing it into one number.

Module Topology + Collapse Risk: where the structure is breaking

The telescope observes more than people. It observes the space they inhabit. Every module sits on three axes: Coupling (boundary quality), Vitality (change pressure × survival), and Ownership (knowledge distribution).

Ace reads the dangerous combinations. A module under high change pressure whose code doesn't survive is a structural time bomb. A module that survives only because nobody touches it is a Fragile fortress, fine until the day someone has to change it. A module whose owner has left is Orphaned, a bus factor that already went to zero.

What becomes observable: where the system is breaking, before it becomes a crisis. Not "this engineer is weak" but "this module carries a bus factor of one, and the person who held it is gone."

The Organizational Chronicle: what the codebase lived through

The Chronicle is deliberately not a scoreboard. It records structural events along a timeline: a migration the codebase survived, an architect who shaped a subsystem and moved on, a module that turned Fragile after an ownership change.

What it records is what the codebase has been through, not how good each person is. People learn to game a scoreboard. A team grows attached to a chronicle. The signal is still there if you want to look closer, but it's a lens you pick up, never the headline.

What becomes observable: the team's own history, written clearly enough to recognize. Observation over evaluation.

Slack connector: the `:orbitlens_chronicle:` reaction

A chronicle that only Ace writes would be a thinner record than the one a team actually carries. So the Chronicle has a connector: react to a Slack message with :orbitlens_chronicle: and that moment is placed onto the timeline. The day a hard migration finally landed. The decision a thread settled. Git records the structure; the connector lets a team annotate the dark matter git can't reach.

Weekly digest: the codebase, once a week

Once a week, Ace reads the recent observation and places the week's structural events into the chronicle: a module that crossed into Fragile, an owner who went quiet, a survival ratio that shifted. It isn't an activity report. It's a record of what changed in the structure.

What becomes observable: the slow tectonics of a codebase, on a cadence a team can actually hold in its head.

Ambient: the codebase, always in view

Ambient is the observatory left running on a screen, a standing display for a stand-up or an office wall. It keeps the structure quietly in view: the modules under pressure, the recent chronicle entries, the shape of the team's gravity field. It isn't a dashboard you open to investigate. It's a sky you glance at and stay oriented by.

What becomes observable: structure as something a team lives alongside, not something it audits once a quarter.

Gravity Certificate: a trace that travels

An engineer's structural impact lives in a codebase's git history, and stays there when they move on. The Gravity Certificate lets that observation travel with the person: a record of the gravity they held, the modules they owned, the architecture they shaped, observed from git rather than asserted on a résumé.

It's careful by design. It's a record of what the code shows, observed from one universe, not a universal ranking of engineering ability. High gravity in one codebase is a local observation, and the certificate says exactly that and no more.

What becomes observable: the quiet structural work that usually stays invisible, the kind that holds a system together and never makes it onto a commit-count leaderboard.

The Whole Arc

The telescope observes, the observatory reads. From the dashboard down to the certificate, the through-line never changes: observation over evaluation. Ace shows a team what its codebase has lived through and where its structure is bending, and it demotes the signal to a lens, so the record stays something a team wants to look at rather than something it learns to game.

The telescope (open source) is completely free. It runs locally, no account needed:

brew install machuz/tap/eis

The observatory (SaaS) is a few clicks. Open ace.orbitlens.io, log in with GitHub, pick the repos you want to watch, and every screen above renders in your browser.

Point the lens at your own organization, at your personal repos, at an open-source project you're curious about.

GitHub: eis · Observatory: ace.orbitlens.io · Library: library.orbitlens.io

The telescope is free and open source, forever. If this was useful: Sponsor on GitHub

Reading Log #9 — Aoashi The Tacit Dimension Thinking, Fast and Slow

machuz — Sun, 24 May 2026 17:37:14 +0000

Putting everything into words isn't honesty. Pride and awe dwell in the realm that can't be told.

1. The dimension of verbalization is different

In Aoashi's Spain arc, Ashito hits a wall beyond technique.

"The dimension of verbalization is different…!" Ashito's strength was putting his own play into words, thinking it through, reproducing it. The "thinker-type" coaching from #4 raised him into a "player who can verbalize." But the top world has players who play one step beyond that verbalization.

Something faster than thinking-and-wording. This time I want to read that "realm that can't be told" alongside two books: Daniel Kahneman's Thinking, Fast and Slow and Michael Polanyi's The Tacit Dimension. The finale of the Aoashi run.

2. Thinking, Fast and Slow: fast thought and slow thought

Kahneman's Thinking, Fast and Slow splits human thought into two systems.

System 1 is fast. Intuitive, automatic, effortless. Pulling your hand from something hot, hearing your mother tongue, reading a face. System 2 is slow. Logical, conscious, effortful. Mental arithmetic, following an unfamiliar rule, choosing carefully.

Humans run mostly on System 1. System 2 is a heavy apparatus, called up when it matters. Ashito's "verbalize, think, reproduce" was a textbook System 2 act. Careful, but slow.

3. "Not even thinking?" — compressed System 2

A scout who saw the Spanish top mutters this.

"Are they not even thinking?" Top players' play is too fast to look like they're thinking each move through. But it's not that they think nothing. The opposite: a vast amount of System 2 training has settled into patterns in the brain and turned into System 1. The trace of having thought so hard you no longer need to. Compressed System 2, moving at the speed of intuition.

"The body moves on its own." "Trust that impulse." This isn't "stop thinking." It's "trust the state where thought, thought to its end, has sunk into the body." What Ashito did in his head, they already do in the body.

4. The Tacit Dimension: we know more than we can tell

Here, Michael Polanyi's The Tacit Dimension. (Not to be confused with Karl Polanyi of The Great Transformation — a different person.)

The book's core folds into a single line. "We know more than we can tell."

Someone who can ride a bike can't explain in words how they balance. A skilled craftsman can't fully say why they shave this grain this way. Knowledge has the explicit that can be worded and the tacit that can't. And the core of a master's knowing is usually on the tacit side.

The truth behind the top players' "not even thinking?" is this. Their knowing has sunk past the dimension of verbalization, into the tacit. Not inferior because it can't be told — they know so deeply it can't be told.

5. Deliberately not verbalizing

What's interesting is that Aoashi doesn't simply praise "verbalization."

"I've never been told anything [in words]," says one player — and another quietly answers: "Verbalization? You don't need it. It's fine."

Put it into words, and yes, you grasp it. You can reproduce it. But the moment you word it, something spills from there. Verbalization also trims rich tacit knowing down to the tellable range — it's also a kind of limitation.

So a master, sometimes, deliberately doesn't verbalize. Rather than thin it by wording, they leave it whole in the body, untold. This is the flip side of the Fukuda from #5. He relentlessly demanded verbalization, yet also guarded what couldn't be verbalized. The courage to word, and the courage not to word. Holding both is, probably, the condition of a master.

6. Non-verbal conversation

Knowing that can't be told passes, untold, between people.

"Honestly, I want to converse with just the soccer ball." I love this line of Fukuda's. As we saw in #7, he fought in a foreign land where the language didn't carry. But with a ball, you don't need words. Intent rides on a single pass; a reply comes back in one trap. Play itself becomes a conversation traded in tacit knowing.

Precisely because language doesn't carry, a high-purity non-verbal dialogue rises. The best combinations usually have no words.

7. Honed pride

And when Aoashi draws the existence of the forward, the pen takes on its deepest awe.

"There's a forward who carries his whole life through on honed instinct alone." For the single result of scoring, he hones only his instinct. Not logic, not words. Sniffing out the scent of the goal, an unexplainable intuition — tacit knowing itself. If he can't finish, nothing remains. The resolve to stake a whole life on that harsh purity. This is the forward's pride.

"He's a forward, after all." What was piled up over a long time folds, at the end, into this short line. The awe that comes from accumulated time isn't talkative. If anything, it's reticent. Those who know more than they can tell usually don't say much.

8. Observation, and the tacit

Finally, to OrbitLens.

I have to admit it honestly: what EIS can observe is only the explicit side. What remains in git history is commits, diffs, blame — only what can be made into words and numbers. The resolve to finish, the non-verbal combination, the intuition that moves before thought, the unspoken pride. The tacit I've watched all chapter spills, root and all, from the net of observation.

In #5 I wrote "Metis spills from legibility." It's the same here. If anything, the most awesome things are the ones that don't show up in observation.

If so, the honesty available to observation is one thing: to admit that what you've grasped is only the tellable part. Not to think the number on the score is the whole person. Signals, not Scores works here too. Observation reflects tellable signals, but it must not erase the existence of the awe that can't be told. The most important thing is outside the observation — to observe, knowing that.

Putting everything into words isn't honesty. Respecting the realm that can't be told, leaving it untold, is also honesty.

Don't nullify what you can't observe. That, probably, is the last pride of the one who holds the telescope.

After the Aoashi run

From #4 to #9, I've watched Aoashi from six angles.

In #4 he acquired the perception of the overhead view; in #9 he arrived at the tacit that can't be told. Both ends are "seeing and knowing, before it becomes words." Ashito grasped the world by verbalizing, and at the end, went beyond verbalization. The whole run drew a single circle.

To discover, to cultivate, to build the environment, to guard the essence, to respect what can't be told. A single soccer manga held all of organization and observation. Next, to another work — but the "seeing" Ashito taught will go on.

A confession

Having written this far, I want to confess one thing.

This series landed too neatly on "structure" every time. Not all of Aoashi mapped conveniently onto a concept. In truth there was excess that wouldn't fit a concept, ambiguity that could tip either way. I cut it to fit the structure. In #5 I wrote "legibility spills Metis" — and that legibility is exactly what I was doing to these stories, trimming them into a readable shape.

That I folded back to OrbitLens every time was, honestly, a funnel. I knew that landing on observation would make it close cleanly, so I let it run there. A convenient form becomes, before you notice, form for form's sake. What I wrote in #8 comes straight back at me.

So someday — not necessarily next, whenever a good theme comes — I'd like to let a book win. An entry where OrbitLens's thinking gets shaken — and revised — by a book. Where the structure comes undone and water spills from the funnel. To a series that preached respecting what can't be told while tidying it into the tellable, this is my homework, one I don't have to rush. When I can write that, this reading log will finally catch up to the "ethics of observation" it claimed.

Books

Michael Polanyi, The Tacit Dimension — Amazon
Daniel Kahneman, Thinking, Fast and Slow — Amazon

The Aoashi run ends here. From #10, another work. I'll read Chuya Koyama's Space Brothers (Uchu Kyodai) alongside Marcel Mauss's The Gift. The quiet heat of the one who doesn't stand out — how does contribution that's hard to count hold up a community?

This is a personal reading of Aoashi (Yugo Kobayashi), The Tacit Dimension (Michael Polanyi), and Thinking, Fast and Slow (Daniel Kahneman).

The Japanese version lives on OrbitLens Library.

OrbitLens / machuz

Reading Log #8 — Aoashi Finite and Infinite Games Imagined Communities

machuz — Sun, 24 May 2026 17:19:44 +0000

When winning becomes the end, a culture that was an infinite game gets swallowed by a finite one.

1. The kingdom's pride and tradition

A storied Spanish club is a kingdom.

A stadium that swallows tens of thousands. The crest. The history. Legends passed down. Everyone longs for it, dreams of being chosen. There is, certainly, pride and tradition there.

But — what is that pride made of? And where does it lose its essence? This time I return to two books already seen: Benedict Anderson's Imagined Communities (#2) and James P. Carse's Finite and Infinite Games (#3).

2. Imagined Communities: a kingdom is made of story

Anderson's Imagined Communities, seen in #2, grasped the nation as "a community that holds together on shared story." People who don't even know each other's faces become one "we" by believing the same story.

A storied club is exactly the same. The crest, the club colors, the founding myth, the legendary players, the memories supporters pass down. These build the imagined community of "I'm a member of this kingdom." The source of pride is neither blood nor soil, but a shared story.

The stronger the story, the stronger the pull. Talent from all over the world gathers, drawn by that story. So far, it's beautiful. The problem is what that strong story starts spinning for.

3. Finite and Infinite Games: the game to win, the game to keep playing

Carse, seen in #3, split human activity into two kinds. The finite game, to win, and the infinite game, to keep playing.

A club's culture is, by nature, an infinite game. Win or lose, you kick the ball again tomorrow. A playground that goes on even as the generations turn over.

"It's a magical place. Enjoy it fully while you can still stand." There's something here outside winning and losing. The magic circle of Homo Ludens seen in #3 — another world where you can seriously play. The kingdom's essence was, probably, here at first. Not a place to win, but a magic place to keep playing.

4. Soccer for the sake of appeal

But the kingdom, before you notice, begins to tilt.

"Is there any purpose other than to appeal?" Soccer becomes a means of selling yourself to the top team. Play for the sake of being chosen, of winning a contract. What was play becomes an audition.

This is the entrance to finite-game-ification. The place to keep playing is quietly swapped for the place to win through. The moment the purpose of play shifts from "enjoy, continue" to "be chosen, win," the magic of the magic circle thins, little by little.

5. The merciless sieve

A kingdom dyed in the finite game takes this shape.

Gathering children from all over Spain, making them play a musical-chairs with their lives staked, and sieving them mercilessly. A handful remain. The rest are shaken off.

The efficiency of winning swallows the essence of cultivating. The "heat to cultivate" from #6 and the "ground that grows players" from #7 turn, here, into tools of selection. The kingdom becomes a machine that produces victory. The story stays beautiful. But the inside is no longer a playground to keep playing.

6. No malice is the scariest

And here is the scariest part: what turns the kingdom into a finite game isn't villains.

Everyone means well. They want them to win. To grow. They're thinking of the club. No one is trying to break the essence. And yet, at the far end of each person's good intentions, the place to keep playing has been swapped for a machine to win through.

If there were malice, you could still fight it. You could name someone the villain and stop them. But a malice-free decay has no enemy. That's exactly why it's hard to stop. This is the same structure as the Berserk-ification of #1 and the culting of #2. Strong story and heat turn people, before anyone notices, into "resources" or "pieces." And yet, there, there is no villain.

7. And still, a pure, equal world

But there's hope too. On that same pitch of the kingdom swallowed by the finite game, a saving grace remains.

"How pure, how equal a world." There may be no room for play here. What there is, is harsh competition. But that competition is — at least on the pitch — equal all the way through. Even a child is evaluated by the same values as an adult. Birth, title, connections — none of it matters. Before the ball, everyone is judged equally.

This is a little different from the core of play (the infinite game) seen in #3. It's rather the most beautiful part of the harsh finite game — the strict equality that a contest is decided purely by ability.

If so, the kingdom's true fall lies further out than the moment winning becomes the end. It's when it loses even this pure equality — when connections, politics, and deference begin to decide the outcome off the pitch. Pride is, probably, not winning forever. It's never letting go, to the very end, of that one point: "before the ball, everyone is equal."

And one more thing. A kingdom that aims only at winning — even if its competition is fair — may someday be outcompeted by another civilization. One that keeps play, and keeps trying new things. The room for evolution is always opened inside play. Not the one who perfects the form and guards it, but the one who can still break the form and play, opens the next era. If so, never letting go of pure equality and never letting go of play turn out, in the end, to be one and the same.

8. Observation, and the kingdom

Finally, to OrbitLens.

An organization, too, is an imagined community (#2). Mission, values, the founding story — a shared story builds the "we." That itself is a source of strength.

The danger is when observation becomes an "apparatus to rank for winning" (#3). Selecting people by score, sieving them, keeping only those who can win. That way, a community for keeping going is swapped for an arena for winning through. And — with no malice. Everyone, meaning well, spins the KPIs. The Berserk of #1, the shared illusion of #2, the finite game of #3. In the end, it returns to the same conditions.

That EIS could become a leaderboard is what I fear most, here. Observation can be a tool of ranking, and an apparatus that guards the essence. Not to fix a ranking, but to see whether that playground is still going, whether the pure, equal core is kept — and to light up the malice-free decay before anyone has to become the villain — that's what observation is for.

A kingdom is made of story. The moment that story becomes "an apparatus for winning," the kingdom loses its essence.

Pride is, perhaps, not winning forever, but never letting go of the essence.

And I'll write about myself. I want to hold a pride that never abandons play. I'll keep the strength to win, properly. But I want to spend that strength not on guarding the form, but on still breaking it to play. To hold both the pure, equal arena and the room to seriously play — that, I want to make my own pride. Even where it makes winning harder in some moment.

Books

James P. Carse, Finite and Infinite Games — Amazon
Benedict Anderson, Imagined Communities — Amazon

In #9, the Aoashi run reaches its finale. The theme: pride, and the awe you don't put into words. The forward's pride, the conviction to finish, the awe that comes from accumulated time — and why the master deliberately doesn't verbalize. Read alongside Michael Polanyi's The Tacit Dimension and Daniel Kahneman's Thinking, Fast and Slow.

This is a personal reading of Aoashi (Yugo Kobayashi), Finite and Infinite Games (James P. Carse), and Imagined Communities (Benedict Anderson).

The Japanese version lives on OrbitLens Library.

OrbitLens / machuz

Reading Log #7 — Aoashi Guns, Germs, and Steel Distinction

machuz — Sun, 24 May 2026 16:59:02 +0000

Strength may be not talent, but a product of environment and accumulation.

1. Why is the ground that grows players so different

In the later arc of Aoashi, the stage moves to Spain. What's thrust at Ashito there isn't a gap in technique. It's the fact that the very environment that raised them is utterly different.

Players who, from a young age, bathed in success and failure at a youth setup like Barcelona's. While the Japanese player is desperately "thinking, thinking," the European top player is already beyond that. Is this a gap in cleverness? Or —

This time I want to read this "environment gap" alongside two books: Jared Diamond's Guns, Germs, and Steel and, again, Bourdieu's Distinction.

2. Guns, Germs, and Steel: strength was decided by environment

Diamond's Guns, Germs, and Steel answers one big question: why did the people of one continent become the ones who conquered the people of another?

The answer isn't racial superiority. It's environment and geography. Plants fit for cultivation, animals fit for domestication, a continent long on its east-west axis — people who happened to be in a blessed environment generated surplus through farming, grew their population, and accumulated technology, immunity, and the state. The difference was born not from ability, but from the conditions you were placed in at the starting line.

Soccer is similar. Spanish players are strong not because they were born fast. It's because they happened to be born into an environment where football is rooted as culture. "Before you blame the person, look at the structure" — this book's reach lands straight on the pitch too.

3. The soccer pyramid: an accumulation of heat

Look at Spain's league structure, and it shows.

From the first division down to the seventh. Even small towns have clubs, and soccer is dissolved into daily life. This thickness of layers isn't made overnight. It's many generations of time, fallen and piled up.

And this thickness isn't only a matter of "long history." It's an accumulation of how much heat a whole society has poured into football. In Spain there's an air that permits prioritizing the local club's coaching over your job. On a weekday evening, adults and children gather on a small town pitch as a matter of course. That daily heat, piled over generations, became that thick pyramid. The Japan/Spain gap isn't a gap in talent. It's a gap in the amount of heat society has bet on the game. Diamond's "accumulation born of environment" takes, in soccer, the shape of this heat and this pyramid.

4. Environment changes the premises themselves

The frightening thing about environment is that it changes not only "what you think," but what your body does before you think.

Picture Barcelona's soccer. That beautiful passing combination, the ball circulating among the players without stagnation. Even someone who doesn't follow football has surely seen that scene once. It's become, before anyone noticed, a shared "normal" the whole world knows.

This is what Bourdieu calls habitus — the unconscious "normal" the environment carves into the body. Spanish players aren't, each time, "choosing" that passing. From a young age, the environment has raised bodies that circulate the ball that way. What the Japanese player tries to catch up to by thinking "I should move like this," they already know in the body, before thought.

Environment soaks in below consciousness. That's why it's the hardest to catch up to. You can learn the form, but the "normal" of a body that moves before thinking — that, you can only grow inside the environment.

5. Accumulation backs the résumé

Here, Distinction from #5, once more.

Aesthetic sense, the discerning eye — made by class and history. That story works directly on a player's "résumé" too. The Spanish player holds, from the start, the cultural capital of the environment they were born into. The Japanese player can only build it up later, consciously.

And as we saw in #5, the evaluating side's gaze isn't neutral either. A résumé that says "from Europe" backs a certain trust all by itself. The accumulated environment backs the résumé, and the résumé clouds the eye. The power of structure, before ability.

So Ashito's fight is doubly heavy. While closing the environment gap, he must also force open the gaze that the gap itself has clouded. #5's "if you aren't seen, make them see" works here too.

6. And still, the individual crosses the sea

But — don't read Diamond's book as fatalism. That environment sets the conditions is true. Yet a person can re-choose their environment.

Fukuda crossed the sea to see football's ceiling. A view he couldn't have seen in Japan. To see it, he moved his own environment. You can't choose the environment you were born into, but the environment you stand in next, you can choose.

And there, in the re-chosen place, someone says it flat.

"Japanese can do it too." The environment gap they were told was absolutely impossible, pinned down by results. Environment is strong. But environment isn't everything. Having taken on the conditions, the individual who still goes to surpass opens a hole in the environment's story.

And the hole one person forces open becomes, in time, a path. The footprints of the one who first proved "Japanese can do it" — the next generation can walk them as a road. The individual who went where no one had gone becomes, before anyone notices, the successors' very environment. A path isn't given; the first person carves it with their own feet. And that path becomes the next person's "normal."

7. Environments can be designed

The most hopeful implication of Diamond's book is, I think, here: if strength is a product of environment, then the environment is what you can design.

If Spain's pyramid took many generations, then an environment that grows players can also be made on purpose. What Aoashi's Esperion tries to draw is, probably, exactly that — not waiting for chance talent, but designing the very environment in which talent grows.

The "heat to cultivate" I read in #6 was an individual act. What I'm reading in #7 is the story of that heat piling up and, in time, becoming an environment. One coach's heat becomes one rung of the pyramid. That's how an accumulation of time gets built.

8. Observation, and environment

Finally, to OrbitLens.

The most dangerous thing about observation is attributing strength to the individual alone. A score of "this person is excellent / low" usually ignores the environment they were placed in. Accumulation built in a blessed environment, and grit endured alone in a barren one, both get rounded into the same "individual score."

This is continuous with #5's unconscious discrimination. Measure the individual without seeing the environment gap, and you misread an environment gap as a talent gap. High just for being from Spain, low just for being from Japan — observation like that preserves the structure as is.

So EIS observes by separating domains. It doesn't mix them. It keeps the relative-within-the-same-environment and the absolute-across-organizations apart. And it tries to observe the accumulation of time (surviving code) together with that person's context. Before pushing strength onto the individual, it asks what environment made it possible. Observation, the moment it overlooks environment, becomes an apparatus of discrimination.

Strength is a product of environment and accumulation. So before measuring the individual, see the environment. And design the better environment.

You can't choose the environment you were born into. But the environment you stand in next, and the environment you build for someone else — those, you can choose.

Books

Jared Diamond, Guns, Germs, and Steel — Amazon
Pierre Bourdieu, Distinction — Amazon

In #8, Aoashi again. A storied Spanish club — when does its tradition and pride tilt into "a kingdom that lost its essence"? When winning becomes the end, a culture that was an infinite game gets swallowed by a finite one. Read alongside James P. Carse's Finite and Infinite Games and Benedict Anderson's Imagined Communities.

This is a personal reading of Aoashi (Yugo Kobayashi), Guns, Germs, and Steel (Jared Diamond), and Distinction (Pierre Bourdieu).

The Japanese version lives on OrbitLens Library.

OrbitLens / machuz

Reading Log #6 — Aoashi The Selfish Gene The Protestant Ethic

machuz — Sun, 24 May 2026 16:34:58 +0000

To cultivate is, maybe, to replicate your own heat into someone — and one day be surpassed.

1. I found someone I absolutely want to cultivate

Aoashi has this monologue.

"I found someone I absolutely want to cultivate."

I can't forget this one line. Where does the urge to raise someone come from? Not scoring yourself, not winning yourself, but the heat of wanting to see another person grow. A heat that should have worn down, lighting again at the meeting of one person.

In #5 I read "discover / make them see." This time, the next step — after discovering, turning to the side that cultivates. Two books alongside: Richard Dawkins's The Selfish Gene and Max Weber's The Protestant Ethic and the Spirit of Capitalism.

2. The Selfish Gene: the replicator's view

Dawkins's The Selfish Gene recast life as "a vehicle for genes."

The protagonist isn't the individual. It's the self-replicator — that which gets copied and tries to spread. The gene, to survive, builds a body as its vehicle. Living things are the gene's means of replicating itself.

And the book's longest reach is one word at the end. Meme. If the gene is biology's replicator, culture has its replicators too. A melody, a turn of phrase, a form, a thought, a gesture, a heat. They get copied from person to person, spreading head to head.

I want to look at cultivation through this eye. To cultivate is to replicate the meme inside you — a view of soccer, a way of carrying yourself, a heat — into another person.

3. To cultivate is to inherit a meme

Aoashi's coaches aren't only teaching technique.

What Fukuda conveys to players is something deeper. To believe "you are ones who grow." To see. To think. He's trying to copy that very stance into them.

"I can guide you, endlessly." More than technique rides on these words: the will to hand over, whole, the way of seeing the world that you believe in. This is meme inheritance itself.

And here, recall the Fukuda of #5. He was a man who relentlessly demanded verbalization, yet guarded the un-verbalizable hunch. To cultivate is, I think, to hand over both — the meme you can word (form, theory) and the meme you can't (hunch, heat).

4. The blissful moment: when the copy surpasses the original

There seems to be a "blissful moment" for the one who cultivates.

It's when a player you taught surpasses your own imagination.

There's a strange paradox here. Usually, if you hand something over, the giver is above. Yet in cultivation, the handed-over meme surpassing the original, at the copy site, becomes the greatest joy. Being overtaken becomes bliss.

Through Dawkins's eye, this is natural. Success for a replicator isn't the original keeping its throne. It's multiplying at the copy site and spreading farther than the original. When the student surpasses you, the meme, for the first time, leaves your single body and begins to run on its own.

Aoashi shows this vividly. Ashito, on his knees before the coaches, says it flat:

“Give me command!” The cultivated one comes this far. Having made the handed-down form his own flesh, he now turns to the side that moves the field. For the one who taught, there's no moment better than this — the copy telling the original, "leave it to me."

The true nature of the heat to cultivate is probably this. Not that you win, but that you want to see your heat continue beyond you.

5. The will of the one being cultivated

Up to here, I've looked at the cultivator's heat. But a meme doesn't replicate on one side's heat alone. It takes hold only when the receiver chooses it.

Ashito wasn't a player who only waited to be given. He finds, himself, the person to aim at.

That person is Akihiro Shiba. A player who fights with his head, called the "thinking reed."

Ashito looks at him and decides, "I'll become this person." The moment whom-to-inherit is set, the path opens all at once.

This meshes with Dawkins's view too. A meme isn't something you push into a host. The host's side chooses which meme to replicate. The cultivated isn't an empty vessel. They choose, by their own will, whose what to inherit.

So cultivation isn't one-way. Only when the cultivator's "I want to hand it over" and the cultivated's "I want to inherit this" mesh does the meme replicate. Just as, in #5, the discoverer and the one who makes them see were accomplices — the one who cultivates and the one being cultivated are accomplices too.

6. The Protestant Ethic: giving your life to the organization

One more book, Weber's The Protestant Ethic and the Spirit of Capitalism.

Weber asked why, in the West, "to keep working" became an ethic. The key is Beruf — vocation, or calling. To throw your whole self into work as a mission given by God; that becomes proof of faith.

In Aoashi, a love close to this calling appears again and again.

"I want to stay here forever." These are the words of an aging coach, near retirement. The very end of a career. He's stepping down, yet this ground alone he doesn't want to let go of. The place where young coaches will go on raising many children — there, even so, he wants to stay. Not mere company loyalty. Close to the last prayer of a person who gave a whole life to cultivation.

Cultivation has no quick returns. You may not be rewarded within your own lifetime. That you can still keep at it for a lifetime is because of Beruf — the explanation-free conviction that "this is what I do." And the aging coach's "I want to stay here forever" is, I think, the quiet prayer at the far side of a calling lived to its end.

And at the end of that life, words like these spill out.

"Even without me, it'll be passed on." Here, the thread from #2 ties into one. A life given over doesn't vanish when the person leaves. Because the handed-over meme — heat, form, way of seeing — keeps living inside the next generation. To live a calling to its end is, maybe, to leave behind what gets passed on even after you're gone. "I'm satisfied now" can be said, I think, only when you've truly seen that it carried over.

7. Beware the iron cage

But Weber left a frightening prophecy too. The iron cage.

Even diligence that began from a calling, as the age turns, loses its first faith and purpose. What remains is just a self-perpetuating system, spinning on. Working without knowing why. The means becomes the end.

Cultivation has the same trap. "Raising people" turns, somewhere along the way, into "KPIs for cultivation's sake." Devotion to the organization turns into "an organization for the organization's sake." The place meant to pass on heat falls into a place that measures heat. The calling becomes a cage.

What unlocks it is, probably, the stance of the Fukuda from #5. Treasuring verbalization (legibility), while guarding what can't be verbalized (heat, hunch). Inherit the form, but don't make it form for form's sake. The key to the cage is, probably, always whether you can re-ask "what is the cultivation for."

8. Trust, replicated sideways

A meme doesn't replicate only top-down (coach to player). It spreads sideways too.

Inherited heat and form move between players, too. One person's way of carrying themselves moves to the next, and becomes the team's "normal." By the time no one remembers who the origin was, it's already called culture.

A good organization's meme replicates sideways like this. One person's heat becomes the team's manner, becomes the air. Trust stops needing words and checks each time — that sense of believing the ball will come there without looking to confirm. The heat to cultivate, in the end, leaves the particular individual and comes to dwell in the place itself.

9. Observation, and the heat to cultivate

Finally, to OrbitLens.

The heat to cultivate is the hardest of all to show in numbers. Mentoring, trust, building the place, waiting for someone's comeback — none of it lands on the quarter's score. In EIS's words, this is dark matter. Mass you can't see, yet it holds civilization together.

The reignition of heat — "I found someone I absolutely want to cultivate." The blissful moment — "they surpassed my imagination." Both spill through the net of observation. Meme inheritance that can't be made legible.

So what's asked of the observing side is, I think, this. Don't nullify the heat to cultivate just because it can't be measured. And don't make cultivation into "KPIs for cultivation's sake," building an iron cage. That EIS tries to keep Anchor and Cleaner, maintenance and inheritance as important axes is close to here. To at least try to see the heat of those who pass it on — outside the ranking.

To cultivate is to replicate your own heat into someone, and one day be surpassed. And that heat, even uncounted, holds civilization together.

Can you be glad to be surpassed? That, probably, is what it means to turn to the side that cultivates.

Books

Richard Dawkins, The Selfish Gene — Amazon
Max Weber, The Protestant Ethic and the Spirit of Capitalism — Amazon

In #7, Aoashi again — the stage moves to Spain. Why is the ground that grows players so different? Strength may be not talent but a product of environment and accumulation. Read alongside Jared Diamond's Guns, Germs, and Steel and, again, Bourdieu's Distinction.

This is a personal reading of Aoashi (Yugo Kobayashi), The Selfish Gene (Richard Dawkins), and The Protestant Ethic and the Spirit of Capitalism (Max Weber).

The Japanese version lives on OrbitLens Library.

OrbitLens / machuz

Reading Log #5 — Aoashi Seeing Like a State Distinction

machuz — Sun, 24 May 2026 15:58:41 +0000

Must talent wait to be discovered? Or can it make itself seen?

1. The gaze that "finds"

Aoashi keeps showing the moment of "I found it."

Midway through a match, Fukuda looks at one player sitting on the bench. It doesn't look like a choice made by reasoning. It's almost a hunch. And he says, quietly: "Yoshito. You — go." With that one line, a person's trajectory begins to shift.

Something strange has already happened here. How could Fukuda pick Ashito? Not by a score, not by a number. With something not yet put into words — a kind of hunch — he discerns talent. The discovering eye is itself an unexplainable knowing.

This "finding" is beautiful. But it's also a little frightening. What happens to the talent that no one found? What if the discoverer's hunch is off? And what, exactly, is that hunch feeling as "talent" — and cutting away as "ordinary"?

This time I want to read this "discover / be discovered" structure alongside two books: James C. Scott's Seeing Like a State and Pierre Bourdieu's Distinction.

2. Seeing Like a State: the power of legibility

Scott's Seeing Like a State explains how the modern state has governed, with one word: legibility.

The state can't handle complexity as it is. So it arranges things into a form it can "read" from above. It surveys scattered land into maps, cuts tangled customary plots into parcels, registers irregular names into a census, aligns diverse crops into a single cash crop. Arrange it, and you can tax, conscript, govern.

Legibility itself isn't evil. Without it, public health, infrastructure, redistribution don't hold. The problem comes next.

Here is Scott's sharp point: a legible map is not reality itself. When you arrange, something always spills. What spills is the knowledge people built on the ground over long years, hard to put into words — what Scott calls Metis. The quirks of the land, the read of the weather, the one-off judgment. It isn't in the ledger. And yet it was exactly what kept the field running.

Legibility keeps only the readable, and treats the unreadable as "not there."

3. Soccer makes talent legible

Youth development is a vast legibility machine too.

Height, speed, goals, distance covered. The scout's evaluation sheet. Pass or fail at the selection. All of it arranges complex "skill" into comparable numbers and roles. Without arranging, you can't choose among hundreds of players. Legibility works here too, as a necessary evil.

But what Aoashi keeps drawing is the talent that spills from that ruler.

Ashito's abnormal overhead vision, at first, landed on no axis of evaluation. By the existing ruler — "scores goals," "runs fast" — he's just a rough country forward. His real talent — the perception that reads the whole pitch as rhythm — is exactly Scott's Metis. Hard to verbalize, unwritable on a sheet, spilling through the grid of legibility.

So the question becomes this: was the spilled talent really not talent? Or was it the ruler that couldn't read it?

4. The eye is not neutral

Here, one more book. Bourdieu's Distinction.

In #0 of this series, I summarized it like this: aesthetic sense is made by class and history. "What I feel is good" isn't pure preference; it's shaped by upbringing, belonging, the history of one's learning.

This works, directly, on "the eye that sees talent" too. The discoverer's gaze, too, is not neutral. What you feel as "skilled," what you grant as "thinking," what you call "exceptional" — that standard itself is a product of a particular culture and history.

The trouble is here. When the ruler of legibility isn't neutral, what spills is always "knowledge raised in another context." This runs almost continuous with unconscious discrimination. No one judged anyone inferior. They just overlooked what didn't land on their ruler. But to the overlooked, that's the same as being made not to exist.

And the "discover by hunch" eye from earlier isn't free of this danger either. A hunch is an accumulation of what one has seen before. So it can pick up the shapes of talent it has seen — but a shape no one has ever seen can slip even past the hunch. There is no neutral ruler anywhere.

5. If you aren't seen, make them see

So is the spilled side left only to wait for the luck of being "found"?

The fun of Aoashi is that here it draws another path. Not waiting to be discovered, but making them see.

At some point, Ashito starts to define what he is, himself.

This is a quiet rebellion against the structure of legibility. Instead of waiting to be "read" by the ruler, he presents, from his side, how he is to be read. He declares "I am this kind of piece," and leaves no choice but to see him that way.

There's a rougher form, too. This is Fukuda's own playing days. In a foreign club where the language doesn't carry, he says it flat:

His skill was above anyone's. But the words don't carry. Then the only move is to make a "can't-not-read-it" state through play. Waiting for no one's permission, he forces visibility open by results. He stops being an object that gets made legible, and becomes a subject who forces legibility.

Precisely because words don't carry, here visibility is staked almost entirely on play itself. This is Metis striking back. If you're not in the ledger, make them rewrite the ledger.

— And worth remembering: the Fukuda who, at the opening, discovered players by hunch once forced his own read open with his own skill. The one who discovers is usually someone who once made others see.

6. And still, there are those who discover

But "taking over" isn't the only answer.

Not everyone can force visibility open on their own. The one who first picked up the rough Ashito was, after all, a discoverer — the eye of Fukuda, of Akutsu, that can see outside the existing ruler.

A good scout is someone who doesn't fully trust the grid of legibility. Beyond the numbers on the sheet, they try to see the Metis not yet put into words. Behind "can't score," they find "sees the whole." In Scott's terms, an observer who doesn't kill field knowledge with legibility.

And that discovering eye, too, is itself an un-verbalizable hunch — the observer's own Metis. Fukuda probably can't fully put into words why he chose Ashito. That's why the eye is precious. And that's why it's dangerous — because, as we saw, a hunch isn't neutral.

And still, what's remarkable about Fukuda is that he never lets go of both sides at once. He relentlessly demands verbalization from his players — "what was visible to you just now?" — making them put play into words; he uses the power of legibility to the fullest, for cultivation. And yet he doesn't crudely crush the hunches and impulses that can't quite be worded. He treasures verbalization, while properly guarding the territory that can't be verbalized. Not legibility or field knowledge, but holding both. That's probably the hardest — and the most precious — part of the act of observing.

So the discoverer and the one who makes them see don't oppose each other. They're accomplices. An eye that can doubt the ruler on one side, a will that presents how to be read on the other. When the two mesh, the talent that would have spilled finally catches its orbit.

What's frightening is the place where both are missing. Only evaluators who never doubt the ruler, and no margin to raise a voice. There, Metis keeps quietly spilling. With no one meaning any harm.

7. A path is not given

In Aoashi, there's a line: players who carve their own path on sheer ego, regardless of those around them, are rare.

A path is not given. The legible world hands you the parcels that already exist and the roles that already exist. Fit yourself into them and yes, you become "easier to read." But the one who goes toward a place with no ruler yet has to carve the path themselves.

The word "ego" is usually a little disliked. But the ego here is close to "the power to believe in how you see, even when no one can read it yet." The heat to hold up, alone, the stage before being discovered. Without it, the spilled talent vanishes, spilled.

8. Observation, too, is legibility

Finally, to OrbitLens.

Let me be honest. An observation apparatus like EIS is on the legibility side. It arranges the complex reality of git history into seven axes. Makes it readable. Scott's warning comes straight back at me: when you arrange, what spills?

That's exactly why I'm most careful not to over-simplify. So that the signals stay close to the on-the-ground sense, I've tuned the formulas and values, over and over. Legibility is unavoidable. Even so, I want it to be legibility that doesn't kill field knowledge — Metis. Making it readable while not over-tidying it — EIS stands on that thin rope.

The moment you rank people by a score, observation becomes the most dangerous legibility. The ruler of "this score is high / low" calls only the ledger-listed Metis "talent," and treats the unlisted as "not there." Just as Ashito's overhead vision, at first, landed on no axis.

That I'm insistent on Signals, not Scores is, probably, here. Not fixing it by a point, but leaving it as a trajectory. Before judging the unreadable as "not there," leaving the margin to ask: "this trajectory — maybe it just isn't on my ruler yet?"

And I don't want to forget Bourdieu's warning: the observing side's gaze, too, isn't neutral. That's why OrbitLens has a firewall, and a principle of observing the observer. Has the eye, somewhere, become the ruler of a particular culture? Is the telescope itself overlooking something from the start?

Observation can be an apparatus that discovers, and an apparatus that overlooks. The dividing line is, probably, whether you can keep doubting your own ruler.

You can do more than wait to be found — you can make them see. And the observing side keeps asking whether it's overlooking something.

Talent must wait to be discovered — that, I don't want to believe.

Books

James C. Scott, Seeing Like a State — Amazon
Pierre Bourdieu, Distinction — Amazon

In #6, Aoashi again — this time, the side that cultivates. To raise someone may be to hand over a discernment that can't be put into words. Read alongside Richard Dawkins's The Selfish Gene and Max Weber's The Protestant Ethic and the Spirit of Capitalism.

This is a personal reading of Aoashi (Yugo Kobayashi), Seeing Like a State (James C. Scott), and Distinction (Pierre Bourdieu).

The Japanese version lives on OrbitLens Library.

OrbitLens / machuz

Reading Log #4 — Aoashi The Philosophy of Sense

machuz — Sun, 24 May 2026 15:04:00 +0000

From meaning to rhythm. The bird's-eye view wasn't a talent he was born with — maybe it was a perception that grows.

1. Aoashi is a story about vision

Yugo Kobayashi's Aoashi is, I think, a story about perception wearing the shape of a soccer manga.

Ashito Aoi, up from Ehime, is a forward starved for goals. He wants to score. To go forward. To draw in the ball and make the net shake. The boy's heat points straight ahead.

Fukuda, a J-league youth coach, picks him up. What Fukuda saw wasn't Ashito's finishing. It was a vision that seems to watch the pitch from above — a perception of space itself, one Ashito didn't even know he had.

What this manga keeps drawing isn't, I think, a "getting good" story. It's a story about how seeing changes. The same pitch, the same twenty-two players, the same ball. And yet, from one day on, Ashito starts to see something entirely different.

2. The Philosophy of Sense: from meaning to rhythm

Here I want to set down Masaya Chiba's The Philosophy of Sense (センスの哲学).

"Good sense," "bad sense" — we use these words like an inborn talent. That person has it, I don't. Words of resignation.

Chiba quietly unpicks that. Sense isn't the property of a chosen few. It's the power to perceive detail, and it can be grown. Grown how? The turn at the book's center is this:

Catch a thing not as meaning, but as rhythm.

Usually we receive what's in front of us through "what does this mean." What is this picture trying to say. What is this dish for. This move — what's the strategy. Meaning — message, purpose, story. We summarize the world with it.

The entrance to sense is to suspend that summary for a moment. Before meaning, feel the strength and weakness, the placement, the intervals, the movement. Chiba calls that rhythm. Before judging good or bad, just watch how a thing is moving there.

3. What started to become visible to Ashito

Ashito's first field of view was made of meaning.

The ball: "a thing to score with." Space: "where I break through." Teammates: "the ones who pass to me." Everything organized toward the meaning called the goal. Leaning forward, narrow. He watches the pitch as the hero of a scoring story.

What Fukuda opens is what lies before that. Peel the ball off of meaning and watch the whole placement and flow of the pitch. Who is where, which space is open, which way the opponent's weight is tilting. Not the single point of a goal, but the movement the twenty-two make together.

This is almost the same thing happening as Chiba's turn "from meaning to rhythm." Ashito's bird's-eye view, I think, is a perception that stops summarizing the world by the goal (meaning) and watches it as placement (rhythm).

And what matters is that it's not a talent complete from the start. The aptitude is there. But what Aoashi draws across many volumes is the process of that perception growing, little by little, through questions and repetition. Sense isn't given; it grows. The manga and the philosophy book are saying the same thing in different words.

4. Position change: a cruel re-placement

Early in the story, Fukuda hands Ashito a cruel verdict.

Quit being a forward. You'll play defender.

To a boy who came all this way to score, he says "you're on the side that defends." He takes the "scoring story" that sat at the center of the dream out of his hands. Ashito rages. Of course he does. His meaning was taken.

But Fukuda could see it. Ashito's bird's-eye view lives better from a position that watches the whole from behind than waiting for goals at the front line. Not a perception that charges forward, but one that folds the pitch in from the back. That's exactly why he placed him in the rear.

This overlaps with the core of The Philosophy of Sense. Peel meaning away once, and re-place it as rhythm. Only when the meaning-tag of "the scoring hero" is removed does Ashito's perception begin to move at its true range. Not by taking the placement away, but by changing it, the way of seeing itself changes.

What's cruel is that in that moment, the rhythm isn't visible to him yet. Only the pain of having meaning taken arrives first. The point of the re-placement can only be understood afterward.

And behind that cruelty, a kindness hides too. Fukuda was sure Ashito would come to enjoy playing defender.

"The one who'll enjoy it most is — you, Ashito." Even as he handed down the cruel verdict, Fukuda had already seen where this boy's joy lay. And indeed —

"Defense…!! This is so much fun." In the re-placed position, Ashito properly finds play. Fukuda's call rested on a conviction — that Ashito could play even on defense. That's why the cruelty of peeling meaning away could, at the same time, become kindness.

A line can be drawn here. A reassignment that leaves no room for play is, sometimes, necessary for an organization too. But that one is merely cruel. Fukuda's re-placement was kind because, beyond it, he had clearly seen the room for play the boy didn't yet know.

5. Coach Fukuda moves between the thinker and the philosopher

Read Aoashi as a theory of leadership, and Fukuda's conduct is fascinating. He moves between two distinct stances.

One is the thinker. He doesn't teach the answer. He places only a question. "Why did you run there?" "What was visible to you just now?" Instead of handing over the correct answer, he leaves the margin for a player to notice on his own. Realization can't be given to someone else. The way of seeing changes only inside the person. So Fukuda often waits in silence.

The other is the philosopher. A decision like a position change isn't handed over as a question. It's declared. You'll play defender. In it lives an unyielding will toward his ideal image of a team — soccer where everyone thinks, where the whole pitch moves as a single perception. The face of the side that defines concepts and decides.

Neither of these is the right one. A coach of questions alone can't erect a structure; it looks gentle, but sometimes it's just fleeing from the decision. A coach of declarations alone kills realization; players obey, but the way of seeing doesn't change. Fukuda can grow players because he can move between the two, by the situation.

Usually he places a question and waits for the noticing; at the load-bearing points of structure, he declares, almost cruelly. The thinker as the baseline, the philosopher narrowed to the necessary point. That balance, itself, is probably the body of the thing called coaching.

And this thinker-type stance is, I think, not Fukuda's alone. It's an aesthetic that runs through the club called Esperion. When the senior Yoshitsune tells Ashito, "Don't aim to become me. You're already climbing a fine staircase," the same perspective flows there too. Don't make anyone a copy of yourself; the organization believes in, and waits for, each person climbing their own staircase. The thinker-type is at once one person's touch and a culture handed down.

6. Why the moving-between is needed

This balance doesn't stay inside coaching.

A place of questions alone is comfortable. No one gets hurt. But a team where no one says "you'll play defender" never has its re-placement of meaning. Each clings to a meaning he likes, and the rhythm of the whole never rises. Gentleness covers over the absence of structure.

A place of declarations alone is fast. Things get decided. But in a place with no margin for noticing, players move without understanding the reason. The way of seeing doesn't change, so the moment the coach is gone, it collapses. Obedience isn't autonomy.

So the moving-between is needed. Structure can only stand by declaration, but perception can only grow by question. Fukuda lets go of neither. The strength not to yield his ideal, and the patience not to rush the answer — the same person holds both.

This works, I think, the same way in writing, and in organizations. Don't mistake the place that needs a declaration for the place that needs a question left open.

7. Sense can be democratized

What's kind about Chiba's book is that it lands, at the end, on "and so sense can be grown."

Sense isn't a born talent. Not class, not bloodline. It's the accumulation of a habit — perceiving detail, watching rhythm. So anyone can grow it. This lands in the same place as #0 of this series, "manga was a democratization device for cultural capital."

Ashito's bird's-eye view is, in the end, the same. It isn't drawn as a one-shot genius trick. He takes a question, runs, errs, and watches again. Through that repetition, the perception widens little by little.

Because it's not a story of talent but a story of perception growing, a little room is left for something to shift on our side too, as we read.

The way of seeing can be changed. That's a fairly hopeful thing, I think.

8. Observation, too, is a kind of sense

Finally, to OrbitLens.

Try to read an engineer's work by the meaning of each individual commit, and your field of view becomes Ashito's first state. What did this PR do, what is this line for. Counting contribution as points, one by one. Leaning forward, narrow.

What EIS tries to do lies before that. Not aggregating the meaning of individual commits, but watching the placement and trajectory — the rhythm. Who carries which module, which knowledge survived against time, where change-pressure is pooling. Not points, but the movement the whole organization makes together. This, I think, is the same perception as Ashito's bird's-eye view.

And the observer's stance stands at the same question as Fukuda. To declare "this person's score is low" is the philosopher's face — and that alone fixes a person to a single point and kills the noticing. Signals, not Scores is, I think, a design that places it on the thinker's baseline. Not fixing a ranking by points, but leaving a question: "this trajectory — what's happening right now?" The way Fukuda placed a question for Ashito, not an answer.

But the thinker alone can't erect a structure. The seven axes, the archetypes — at some point, they can only be named by declaration. This is close to the cruelty of "you'll play defender." Without the courage to name a structure, observation becomes gentle noise.

So observation, too, is a moving-between. Watch placement as rhythm (sense) as the baseline, and name structure by declaration only at the load-bearing points. The telescope leaves a question, and points at structure at the one necessary place. The moment that balance breaks, observation falls into a leaderboard.

The way of seeing can be grown. By stopping the counting of points, and starting to watch rhythm.

The bird's-eye view wasn't the talent of the chosen. Observation, probably, is the same.

Books

Yugo Kobayashi, Aoashi (Shogakukan) — Amazon
Masaya Chiba, The Philosophy of Sense (センスの哲学) (Bungeishunju) — Amazon

From here, the next several entries form a deeper reading of Aoashi. #5 is "The Seen and the Self-Made" — must talent wait to be discovered, or can it force itself into view? Read alongside James C. Scott's Seeing Like a State and Bourdieu's Distinction.

This is a personal reading of Aoashi (Yugo Kobayashi) and The Philosophy of Sense (Masaya Chiba).

The Japanese version lives on OrbitLens Library.

OrbitLens / machuz

Reading Log #3 — Homo Ludens Finite and Infinite Games Exit, Voice, and Loyalty

machuz — Thu, 21 May 2026 05:08:58 +0000

Griffith lived a finite game. How do you keep a civilization you can seriously play in?

1. From the reverse side of Berserk

In #1, I read the structure where Griffith turns a community into an offering for his dream.

Let me restate that tragedy in other words. Griffith was living a game that ends when you win. There was a clear endpoint — reach the castle — and for that victory condition, the community became a means.

So how do you draw the reverse side? A way of relating to people, of building an organization, not to win but to keep playing — what shape does it take?

Three books light that up: Johan Huizinga's Homo Ludens, James P. Carse's Finite and Infinite Games, and Albert Hirschman's Exit, Voice, and Loyalty. This time I put the three on the same desk.

2. Homo Ludens: at the root of civilization, there is play

Huizinga's Homo Ludens recasts the human as "the one who plays (Homo Ludens)."

Usually the human is spoken of as "the one who knows (Homo Sapiens)" or "the one who makes (Homo Faber)." Huizinga places another layer before those: humans make culture by playing.

And the "play" he means isn't entertainment.

Law, war, art, religion, poetry, sport — even philosophy — have play at their origin.

The trial was born from stylized play that competes for a verdict under rules. Poetry was born from play that makes words dance within the constraint of meter. Much of culture's serious territory holds the form of play inside it.

Honestly, this is dead center of how I feel. In my case, the fun usually comes first, and the logic rides on afterward. Git Archaeology, Psychological OS — they started from "huh, that's interesting," and got structured later. Play is the engine of my thinking.

3. The conditions of play — the magic circle

Huizinga says play has a few conditions. These matter for thinking about organizations.

It's free — the moment it's forced, play stops being play
It's set apart from the everyday — play has its own "other world" where distinct rules hold
It has rules — not total disorder. A freedom that accepts constraint
It's serious — play isn't "meaningless." If anything, people get dead serious

The second one especially. Huizinga called it the magic circle. The poker table. The stadium. The theater. The temple. Step inside, and rules different from outside start up. "A world within the world."

Magic circles are everywhere today, too. The moment you sit at the poker table. The moment you open your first Issue on an OSS repo. The hackathon venue. The improv session. The TRPG table. Or late-night coding in an empty office. Each is another world where rules a little apart from outside evaluation and profit-and-loss run. Step in, and people get astonishingly serious.

For an organization, the magic circle is probably a place where "here, you can seriously play, safely." A study, late-night development, the air of a team. An organization that can hold such an other-world is strong.

4. "Earnestness is a bad habit"

Here I want to quote Akagi, from Nobuyuki Fukumoto's Ten.

Earnestness... is a bad habit. That's what stopped you.

What Akagi criticizes isn't diligence itself. It's over-adaptation to rules. "I have to do it right." "I mustn't fail." "Same as everyone." — this kills play. It strips away the margin play needs — to try, to break, to bet, to deviate.

Modern Japan, especially postwar, leaned hard toward "earnestness = discipline = endurance." In the phases of industrialization and recovery, that was rational. But as a side effect, "play" got easily branded as unserious.

Let me sort it like this:

Bad earnestness — submission to rules. It kills play
Good earnestness — the discipline that keeps play going

What I really dislike isn't diligence itself, but diligence that has lost its meaning. KPIs for KPIs' sake, work for form's sake, overtime for the air's sake. That's the state where play has died. Conversely, serious play always has good earnestness built in somewhere.

5. Finite and Infinite Games: the game to win, the game to keep playing

The other book, Carse's Finite and Infinite Games, splits human activity into two kinds of game.

Finite game — the purpose is "to win." Rules are fixed, a winner is decided, and it ends sometime. The match, the tournament, KPI competition, the election.

Infinite game — the purpose is "to keep the game going." Rules change, players are swapped, there's no end. Civilization, culture, scholarship, OSS, love, a good organization, life.

The decisive difference is here.

A finite-game player fights others to win. An infinite-game player engages others to keep going.

And Carse's other sharp point: finite-game players protect their titles; infinite-game players transform themselves. Cling to a role to keep winning, or keep updating yourself to keep going.

6. Griffith played a finite game; Guts moved to an infinite one

Back to #1.

At least the Golden Age Griffith reads as a textbook finite-game player. The castle as endpoint. A clear victory condition. For it, the community was made a means. To win, he made the Band of the Hawk a "resource" to fight with.

Guts, on the other hand, stopped being a part in the dream and moved to an endless question: "fighting to find my own fire." That's a shift to an infinite game. That's exactly why Guts could stand outside Griffith's finite game.

An infinite-game leader treats the community not as "a resource for winning" but as "co-players who keep going together."

Here, between finite and infinite games, what counts as valuable work inverts.

Victory is a moment. A release, a signed deal, winning a competition, hitting the quarter. Each shines at that one point, and ends. Civilization, on the other hand, is continuation. And what sustains continuation is the work that doesn't count in the moment of victory. Cleanup. Leveling the design. Mentoring. Maintenance. Handoff. Documentation. The work of fixing what's broken and grading the ground so the next person can run.

The finite-game record almost never logs these. But what keeps the infinite game going is exactly these. The work of keeping the playground playable tomorrow and the day after.

Civilization isn't for winning. It's for continuing. So unless you change what you count as valuable contribution, an organization gets swallowed by the finite game fast. An organization that counts only the flashy victories overlooks the people who tend the playground — and eventually loses the playground itself.

7. An infinite-game person, strong at finite games

A little about myself, from here.

I'm probably an infinite-game person who's strong at finite games. Implementation, launches, firefighting, fast decisions — I'm reasonably strong at these short-term contests. But what I'm ultimately interested in isn't winning; it's that a place where you can safely, seriously play keeps going for a long time.

So what I've done is take trust and dynamics with short-term combat power, and use that to turn the very vibe of an organization into an infinite game. Less "to win the war" than "to leave behind a good town."

What I don't want misread: this isn't "the infinite game is superior." The opposite, if anything — an infinite game can't be protected by someone weak at finite games.

"Continuation matters," spoken by ideals alone, usually ends as a pretty platitude. When someone who can't deliver in implementation, can't put out fires, can't make the numbers says "continuation over winning," the field doesn't follow. An infinite game stands only on the tug-of-war between the field's grit and idealism. Only when someone who took trust with the power to win spends that trust not on "keeping winning" but on "keeping the playground going" does the infinite game get protected.

So for me, finite-game strength is a weapon for protecting the infinite game. Not winning to win, but holding the power to win — in order to continue.

In my hobby, poker: a tournament is a finite game. There's an endpoint, a winner is decided. But a cash game, as long as your bankroll lasts, never ends — "an infinite game in the shape of a finite one." You can stand up; you can pick your table. Today's win or loss, and what kind of player you become over the long run, become separate questions. The stronger the player, the less they're swallowed by the short-term result.

This is close to the sense of reading a trajectory.

8. Exit, Voice, Loyalty — keeping the infinite game from closing

To keep a playground going for a long time, mere heat isn't enough. You need a structure where people can come and go, can voice dissent, and still want to stay.

An infinite game needs open boundaries. The one who put this most cleanly into words is Albert Hirschman, in Exit, Voice, and Loyalty.

Hirschman says that when people are discontent with an organization or community, their reaction splits three ways.

Exit — leave the place. Resignation, cancellation, emigration
Voice — stay and demand improvement. Dissent, proposal, dialogue
Loyalty — attachment. The force that keeps you from leaving right away and makes you try Voice first

What's interesting is the balance of the three. An organization with only Exit has people vanish in silence — and the sensitive, capable ones leave first. An organization with only Voice becomes a pressure you can't escape. And when Loyalty is too strong, you can't speak up or leave even when something's off. This is continuous with the Berserk-ification of #1 and the culting of #2. The moment loyalty becomes a hostage, the community swallows people.

So the ideal becomes this:

You stay because of attachment. But you can voice dissent. And if it still can't work, you can leave with dignity.

Healthy Loyalty isn't blind obedience. It takes the form "I love this place, so I want to make it better." So the more Loyalty there is, the more Voice comes out instead of a silent Exit. Loyalty can be fuel for keeping the infinite game going.

Here, I want to write about myself. I hold Loyalty toward organizations that play seriously. Not meaning-lost diligence, but a place where serious play is running — to such a playground I don't want to Exit, and instead want to make it better. Conversely, to a place where play has died and only KPIs-for-KPIs run, no loyalty wells up in me. My Loyalty, probably, hangs on whether the organization is living an infinite game.

9. Keeping observation an infinite game

Finally, to OrbitLens.

Observation, left alone, turns into a finite game. The moment you rank people by "this quarter's score is high / low," it becomes a finite game that decides a winner by a point. Fixation sets in.

That I'm insistent on Signals, not Scores is, I think, here. Not fixing a ranking by points, but reading the trajectory. "This person is in an exploration phase now." "A rebuilding phase." "A cleanup phase." — read as a state, observation can stay an infinite game. Growth, context, wavering, recovery become visible.

And here too, open boundaries are needed. The Exit and Voice from before, remaining. The moment it closes, observation turns into a finite game — an apparatus that fixes a ranking by points. The Berserk of #1, the shared illusion of #2 — it all returns to the same condition.

Civilization is a place you can seriously play. Not winning and ending, but continuing. If OrbitLens can be of any use, it's not as a leaderboard but as an apparatus that observes whether the playground is still going.

Keep a civilization you can seriously play in, going, for a long time.

Most of what I want to do, probably, folds into that one line.

Books

Johan Huizinga, Homo Ludens — Amazon
James P. Carse, Finite and Infinite Games — Amazon
Albert O. Hirschman, Exit, Voice, and Loyalty — Amazon

In #4, a book from the thought-book shelf. When does the power to observe slide into domination — a book that stands on the boundary between observation and control.

This is a personal reading of Homo Ludens, Finite and Infinite Games, Exit, Voice, and Loyalty, and Nobuyuki Fukumoto's Ten.

The Japanese version lives on OrbitLens Library.

OrbitLens / machuz

Reading Log #2 — Sapiens Imagined Communities: An Organization Is Made of Shared Fiction

machuz — Thu, 21 May 2026 04:40:51 +0000

Griffith's "story" wasn't a special talent.

1. Griffith's "story" wasn't a special talent

Last time, I read Berserk's Griffith as a meaning-generating apparatus. By distributing not reward but story to the Band of the Hawk, he moved people past their limits.

But let me step back one notch. Is binding people with a story a talent particular to Griffith?

Probably not. That was only an extreme instance of the universal mechanism by which humanity has built large groups in the first place.

Two books take this head-on: Yuval Noah Harari's Sapiens and Benedict Anderson's Imagined Communities. This time I read the two on the same desk.

2. Sapiens: humanity cooperated at scale through fiction

The core of Sapiens, in one line:

What decisively separates humans from other animals is that they can cooperate with great numbers of strangers they've never met, by believing in a shared fiction.

Nations. Companies. Religions. Money. Law. Human rights. None of these lie around as substance somewhere in nature. They exist because everyone believes they exist — shared stories.

Here, "fiction" doesn't mean a lie. By fiction I mean a story that gains real power by being shared among many. If anything, fiction is humanity's greatest invention.

A troop of chimpanzees can bond only a few dozen strong. It can't exceed the range of visible faces. But humans, ten thousand or a hundred million, can move in one direction by believing the same story. The pyramids, the joint-stock company, the modern state — all of them are shared fiction converted into mass cooperation.

So: civilization is made of shared illusion.

What Griffith did was a miniature of this. He distributed to the mercenaries the fiction "you can become part of history," and bound a small face-to-face group into something larger. His talent wasn't inventing fiction. It was starting up, better than anyone, a mechanism humanity has always run.

3. Imagined Communities: living the same story with strangers

The other book, Imagined Communities, dissects this with the specific case of the nation.

Anderson defined the nation like this:

A nation is an imagined political community.

A Japanese person has never met almost any of their hundred million compatriots. Doesn't know their faces or names. And yet feels "we're the same people." Why? Because they share the same story.

Here too, "imagined" doesn't mean fake. Unlike the face-to-face community of a village, it means supplementing, with imagination, solidarity with others you can't directly observe. Before modernity, people lived within "the range of visible faces" — village, tribe, religious sphere. The modern state needed to make a community with strangers. The adhesive was imagination.

4. The infrastructure that distributes the story — print, language, simultaneity

What's interesting is that Anderson explained, structurally, how that imagination got distributed.

The key was print capitalism.

Newspapers and novels, printed and circulated in bulk as market goods. From this, several things happened.

One is the sense of simultaneity. Each morning, countless strangers read the same paper. "Right now, I'm living the same time as a vast number of people I'll never see" — this binds spatially distant others into a single "now."

One is the fixing of language. Publishing standardizes language within the range that pays. Countless dialects were bound into a "national language," and the range readable in that language became the very outline of the community you could imagine. The publishing market made a language community.

And the imagined community isn't only of living contemporaries. By sharing the same story, the community takes in the already-dead and the not-yet-born. That a nation can remember its "founding fathers" and speak "for posterity" is because imagination runs vertically through time as well.

People who read the same story, in the same language, on the same time axis — that became the nation.

This connects straight to #0's "manga was a democratization device for cultural capital." Manga, too, distributed the same story with the same weight to children nationwide, building a generation-spanning "imagined community." Newspaper or manga, the medium differs; the structure is the same.

And that sense we get today, around the World Cup or an earthquake or an election, that "everyone knows" — that too is the time synchronization the story-distributing infrastructure produces.

5. Organizations, too, stand on shared illusion

Let me bring this down to organizations.

A company has exactly the same structure. A strong organization doesn't stand on technology and reward alone. It holds myth, aesthetics, story.

"Here, we treat this way of working as beautiful." "Here, we count this kind of person as excellent." — the "organizational aesthetic sense" I wrote about in #0 is precisely part of this shared illusion. The founding story, past trials by fire, the successes and failures retold again and again. They bind members who've never met into one direction.

Mission, values, organizational culture — pushed to the core, they're shared fiction. And that isn't weakness. Without it, people can't cooperate beyond the few dozen of "the range of visible faces."

In civilizational terms, the question of who makes a design's center of gravity, and whose history has shaped the culture of a codebase, has its root here too. Who bound the shared illusion called a codebase, and how. An organization is shared story, crystallized as structure.

6. When the story grows too strong, dissent disappears

But here, the previous chapter returns.

A shared story makes a community hold together. Yet when that story grows too strong, dissent starts to be excluded as "something that breaks the story."

Nationalism. Religious fundamentalism. The startup myth. A culted-up corporate culture. In none of these is the shared illusion itself the evil. It turns dangerous the moment the illusion is placed above reality.

This is continuous with Berserk's Eclipse. When the shared illusion of Griffith's dream grew too strong, the one who didn't fit it (Guts) became "a being outside the dream," and in the end the community itself became fuel for the dream.

So a shared story needs, I think, two conditions:

That there's a story — without myth, people can't make a large community
That the story isn't absolutized — dissent can be voiced, and one can leave (Exit and Voice remain)

A good civilization holds a shared story. But it doesn't hold the story hostage.

7. There's a sprout of a story at our own feet, too

Finally, back to our own ground.

There's a sprout of a small imagined community around OrbitLens, too. Gravity. Orbit. Signals, not Scores. Civilization. History. Psychological OS. — these are, little by little, becoming a shared vocabulary. People who've never met are beginning to see the same things through the same words.

And that I'm so insistent on "observing organizations" connects here. If an organization is made of shared story, then whether that story can be kept in an observable form comes to matter. Who built what heat onto what, and why it took this shape. A mechanism like Dark Matter Memo is an attempt to support the shared illusion with "the will to keep it."

But I don't want to forget the condition from §6. If the observed story grows too strong and becomes an apparatus that crushes dissent, that's OrbitLens's failure. Distribute the story, but don't absolutize it. Bind the community, but don't make it an offering.

Civilization is made of shared fiction. The question is whether that fiction is making people stand, or has started to swallow them — here too, the question returns to the same place.

Books

Yuval Noah Harari, Sapiens — Amazon
Benedict Anderson, Imagined Communities — Amazon

In #3, I'll read Johan Huizinga's Homo Ludens together with James P. Carse's Finite and Infinite Games — the play at the root of civilization, and the difference between a game played to win and a game played to keep playing.

This is a personal reading of Sapiens and Imagined Communities.

The Japanese version lives on OrbitLens Library.

OrbitLens / machuz

Reading Log #1 — Berserk: When a Dream Turns a Community Into an Offering

machuz — Thu, 21 May 2026 04:09:05 +0000

Salvation and domination begin with the same gesture.

1. Reading it as just dark fantasy is a waste

Reading Berserk as just dark fantasy is a bit of a waste.

Of course, the overwhelming artwork, the violence, the mythic scale, the density of despair — those alone are staggering. But what draws me in particular is the organizational dread drawn into it.

The Golden Age arc, especially — Griffith and the Band of the Hawk — holds a fairly intense structure. In one line, it reads like this:

The Golden Age arc is the story of an organization given gravity by a genius-type leader, which in the end becomes the offering for that leader's private dream.

This is only one facet of the work. But seen through psychological OS and organizational OS, something in it rings straight into real organizations.

By psychological OS here, I mean the inner operating principle that decides how a person sees the world, what they value, and which actions they choose by default. Organizational OS is the org-scale version of that.

2. Griffith as a meaning-generating apparatus

Griffith was more than charismatic: he was a being who gives people meaning.

The members of the Band of the Hawk weren't nobly born, weren't socially secured. Most were mercenaries who had no way to live but the battlefield.

Onto that, Griffith placed a story. You aren't just mercenaries. You can become part of history. Follow this man, and you can cross the layers of the world. Someday, you might reach the castle.

As organizational theory, this is quite strong.

People don't move on reward alone. When someone feels that their life has become part of some larger story, they move past their limits. Griffith made that possible. He gave the Band not just work, but meaning. So the Band, while an army, carried a heat closer to a religious community.

But there's a danger in it. At the center of that community is, in the end, not "the community's happiness." It's Griffith's private dream.

3. Salvation and domination are done with the same gesture

What's frightening about Griffith is that he isn't exploiting people as a villain from the start.

He genuinely saves people. Casca, surely, and many of the Band too. Following him, meaning is born in their lives. A place to belong is born. Pride is born.

But that salvation is, at the same time, domination.

The saved come to offer themselves to the dream that saved them.

This is the beauty of a Griffith-type organization, and its danger. As an organization, the flow runs like this:

individual loneliness · discontent · ambition
  ↓
Griffith, a beautiful center
  ↓
the story "we can become someone"
  ↓
the Band of the Hawk as a community
  ↓
ascent toward kingdom · class · history

Up to here, this is the very recipe for a strong organization. Give people meaning, bind them, connect an individual life to a larger story, draw out power that ordinary means can't.

The problem arrives when that story grows too strong.

4. Guts leaving isn't merely a resignation

What begins the collapse of Griffith's organization is Guts leaving.

Guts belonged to the Band. But he couldn't end as a part in Griffith's dream. Hearing Griffith's own words — "a true equal is one who has his own dream" — Guts begins to search for his own life.

For Guts, it was the start of self-acquisition. For Griffith, it was fatal. Because Guts alone never fully dissolved into Griffith's field of gravity.

Griffith's operating principle should have been this:

dream > everything

But toward Guts alone, somewhere it had become this:

Guts ≒ dream

At that point, Griffith's ideal-realizing OS is already buggy. The man who subordinates everything to the dream had made Guts, and Guts alone, into something that shakes him from outside the dream.

So Guts leaving isn't merely a loss of force. For Griffith, it was an event that destroyed his self-story itself.

5. The Eclipse — the ritual that fixes a community as resource

The Eclipse is, religiously and mythically, a rite of sacrifice. But seen as organizational theory, it's frightening one step further.

The Eclipse can be put like this:

The moment a leader finalizes the community as "resource," not "purpose."

After Guts leaves, Griffith falls. A year of torture takes his voice, his dream, his body.

And still, something in him hasn't died. The castle. The dream he never reached, still shining brighter than anything.

Then the moment of the offering comes.

Settling this with "he was blinded by the dream" is, I think, too sloppy. At that single point, several pressures converged on Griffith at once.

One is sunk cost. He had already thrown everything into the dream. A year of torture, his ruined body, the comrades who died along the way. To give up the dream here would make all of it "meaningless." What's been stacked too high won't allow a turning back.

One is the gap between the present and the ideal. The castle still shines brighter than anything. But his present self has lost voice and body, able only to crawl. The height of the ideal and the lowness of the real — the gap has opened beyond what's bearable.

One is that his very being had fused too tightly with the dream. To let go of the dream was, for Griffith, to lose himself. The feeling of having been "made to forget my dream" by Guts works on him here too.

And there's something now beyond recovery: he can never be Guts's equal. For Griffith, an equal meant one who has his own dream. Guts left to find his and stood on his own feet. But his present self can't even reach the dream — he's become a body that crawls. Before the one person he wanted as an equal, he can no longer stand as an equal. That, probably, cut the deepest.

At the single point where all of these converged, he chose. The community, as offering.

This is the cruel part. The Band mattered to Griffith. There's no doubt of it. But it's precisely because it mattered that it could become the offering. Something that didn't matter can't be offered.

So the dread of the Eclipse lies in this structure:

Turning what you loved into fuel for the dream.

The dream the members entrusted their lives to. The community that was their pride. The bonds, the place to belong, the devotion, the trust. All of it, in the end, consumed for one leader's ascent.

So the Eclipse isn't merely a massacre. It's a ritual where a community's system of meaning is converted into raw material for the dream.

6. The mechanism of sacrifice — rereading through René Girard

I called the Eclipse "a ritual of sacrifice." Here I want to lay René Girard's Violence and the Sacred over it.

Girard placed mimetic desire at the root of human violence. People desire not the object itself so much as "what someone else desires." Desire flares up through a mediator. That, I think, is how the Band of the Hawk became one. They didn't each want different things. Through Griffith's dream as mediator, they wanted the same thing. A "meaning-generating apparatus" is, put another way, the center point of mimetic desire.

According to Girard, mimetic desire eventually breeds collision. If everyone desires the same thing, the community drifts toward a crisis of "all against all" violence. What arose to quell it is sacrifice (the scapegoat mechanism). The community concentrates violence onto a single victim, and by expelling them, restores order. The victim becomes cursed and, at once, sacred. The moment violence turns into the sacred.

The Eclipse was exactly this "violence turning sacred" ritual. The moment Guts left and Griffith fell is Girard's sacrificial crisis itself — the center of desire broken, order crumbling. And through the Eclipse, Griffith gains divinity (Femto). The sacrifice pushes him up into the sacred.

But here Girard's theory doesn't fit cleanly; it slips. In Girard's classic mechanism, the sacrifice is "the many, offering up the one" — the community concentrates violence onto a single scapegoat. But the Eclipse is the reverse: "the one, offering up the many." A single Griffith sacrifices the whole community, the Band of the Hawk, to make himself sacred. The arrow of the scapegoat is flipped.

And this inversion is, probably, the most frightening form in a modern organization. Ancient sacrifice killed one person so the community could survive (still cruel, but there's a logic of protecting the community). Griffith-type sacrifice sacrifices the community itself so that the one at the center may survive and ascend. Not by fitting the theory neatly, but by spilling out of it, the Eclipse's abnormality comes into sharper focus.

7. Each operating principle, in psychological-OS terms

This structure gets clearer when seen through each character's psychological OS.

Griffith (ideal-realizing OS) — the world is ascendable, and there's a castle he must reach. Relationships are given meaning in light of the dream. One who has no dream is no true friend.
Guts (survival-combat OS → self-acquisition OS) — from "to live = to fight" to "fighting to find my own fire."
Casca (devotion OS → agency-recovery OS) — from "I was saved, so I support this man's dream" to "I'm allowed to have my own feelings."
Judeau (observation-mediation OS) — reads the room well, senses who feels what, doesn't need to be the lead.
Rickert (inheritance-witness OS) — remembers what was lost, doesn't believe the heroic tale naively, and doesn't dye fully in hatred either.

Seen this way, the Eclipse isn't simply a scene of people being killed. It's a scene where each one's OS, meaning, place, and relationships are destroyed all at once. That's why it's heavy.

8. This happens in reality too

Of course, there's no Eclipse in reality. No demons, no Behelit.

But structurally, similar things happen. An organization with a strong ideal or story begins, at some point, to treat people as fuel for that story. This happens in reality.

Typically, the flow runs like this:

strong ideal · mission
  ↓
people gather, layer their own stories onto it
  ↓
devotion becomes a virtue
  ↓
unease and dissent get treated as "things that break the dream"
  ↓
the story is prioritized over reality
  ↓
someone is sacrificed

What matters is that it isn't evil from the start. If anything, it's beautiful at first. It saves people, gives life meaning, turns dull work into a proud challenge. That's why it's strong. But the moment the dream is placed above the community, the organization starts to consume people.

A few real-world shapes. The key is that none of them broke "because a villain was present."

Theranos type — the ideal of changing medicine grew so strong that protecting the founder's story was prioritized over technical reality-checking. An ideal-realizing OS suppressing a reality-verification OS.
WeWork type — the self-story "this isn't just a real-estate business" covered over the business reality. A story-generating OS overwriting a reality-grounding OS.
Early-Uber type — winning and taking the market came first; care, ethics, internal controls came later. A victory OS running wild, and people made disposable.
Enron type — genius-worship and results-worship went to excess; "looking like a winner" mattered more than cooperation or sincerity. An elite-selection OS breaking a community-maintenance OS.
Challenger type — there's no easy villain. "It was fine last time" piled up, and danger signals got absorbed into normal operations (the normalization of deviance). When success continues, the anomaly-detection OS dulls.
Volkswagen type — achievement pressure and a governance failure. In a structure where you can't say "we can't," cheating came to look like a rational option. An achievement OS running wild.

And here lies the sad — or cruel — part of so many organizations: without Griffith's meaning-generation, charisma, or salvation, they still treat the community as a resource. They don't even distribute a dream big enough to be worth offering — only the fuel-making happens.

9. A strong OS isn't safe just by being strong

By here, something important comes into view: a strong OS isn't itself the evil.

An ideal-realizing OS moves people forward. A victory OS produces breakthrough force. A devotion OS supports comrades. An achievement OS produces high output. A story-generating OS gives people meaning.

The problem is any of them growing too strong alone.

Psychological OS and organizational OS, the stronger they get, the more they fix how the world is seen. And they make the realities inconvenient to them harder to see. The ideal-realizing OS dislikes reality-checking; the victory OS dulls to others' pain; the devotion OS ignores its own limits; the achievement OS postpones the rightness of means; the story-generating OS slights the plain truths; the success-continuation OS stops feeling the anomaly as an anomaly.

So what a psychological OS needs isn't only strength.

The power to observe what our own OS is making invisible.

There's no perfect person, and no perfect OS. Which is exactly why you build a structure that mixes several OSes in good proportion, covering each other's blind spots — the core of organization design, probably, sits there.

10. Warning signs of a Griffith-type organization

Seen from here, a dangerous organization has a few signs.

A question about the mission gets treated like a betrayal
Someone raising a realistic concern gets treated as cold, weak, or not getting it
The leader's private dream and the organization's whole purpose can no longer be separated
Members' devotion comes, at some point, to be taken for granted
Retreat, delay, downsizing can no longer be spoken of as options
The beauty of the story is prioritized over numbers and facts
Those who feel unease have no choice but to go quiet or leave

A dream isn't bad. A strong story isn't bad. To accomplish anything, they're often necessary. It's just that when the dream comes above the community, the organization starts to consume people.

11. A dream is meant to make people stand

Berserk's Griffith drew people in. He gave them meaning. He made the Band of the Hawk not just a mercenary troop, but a community that challenges history.

That's exactly why his betrayal is heavy. Had he been a hollow swindler from the start, it wouldn't land like this. It's because he was truly beautiful that it's the worst.

I think it's the same in organizations. A strong dream makes people stand. It gives pride to those who were weak, turns dull work into a meaningful challenge, binds scattered people into one direction.

But when that dream grows too strong, it swallows people. People become fuel for the dream. The community becomes an offering for the leader's ascent.

So the question we should hold is, I think, this:

Is this dream making people stand? Or is it turning them into an offering?

Psychological OS, organizational OS — in the end, both return here. Holding a strong OS matters. It's just that an OS is for moving ourselves forward, not for overwriting reality or others.

That I'm so insistent on "observing organizations" at all has its root here. Good gravity doesn't crush its stars. If anything, it works so each star begins its own fusion. Whether the person at the center of the gravity can keep asking themselves this — is my gravity keeping the people around me alive? Or have I started to swallow them?

That's the quite practical organizational theory you can read out of Berserk.

Books

Kentaro Miura, Berserk (Hakusensha) — Amazon
René Girard, Violence and the Sacred — Amazon

In #2, a book from the thought-book shelf. I'll take up, from another angle, the "shared story" that makes a community hold together.

This is a personal reading of Kentaro Miura's Berserk (Hakusensha) and René Girard's Violence and the Sacred. Quoted images are from Berserk.*

The Japanese version lives on OrbitLens Library.

OrbitLens / machuz

Reading Log #0 — Manga Was a Democratization Device for Cultural Capital

machuz — Thu, 21 May 2026 03:45:05 +0000

From a place with no inherited capital, how does an aesthetic sense rise?

1. The illusion of "a taste I chose"

A thought I keep returning to.

The things I like now — did I really choose them?

Leather goods, perfume, a certain kind of audio gear, the texture of wood grain, the thing people call functional beauty. They all have a definite feel inside me. If you asked me why I like them, I could put words to it. But could I say, flatly, that I chose them by my own will? Probably not.

I did the choosing. But the objects I came to like were shaped, somewhere deeper, before I got there.

2. Distinction — taste is formed by class and history

Pierre Bourdieu's Distinction is known for the claim that a person's taste and aesthetic sense are not pure individual preference, but formed by class and history.

Home environment, the group you belong to, education, what the people around you praise and what they look down on. These stack up, and "the things you'll come to like" are decided before you are. You feel "I like this" only afterward.

There's something uncanny here.

People want to treat their taste as an expression of individuality. Structurally, though, it's also a stamp of belonging. What you find beautiful exposes where you grew up, and who you grew up beside.

3. What catches me isn't "expensive," it's "trying to win with the price"

The sense of finding so-called luxury brands "good," of wanting them, doesn't quite register for me.

For a long time I thought of this as "I dislike expensive things" or "I dislike brands." But that wasn't accurate either. It's not aversion, nothing that strong. The "want" circuit just doesn't fire there.

And to be fair: many luxury brands have genuinely accumulated a craftsman's history. Materials, stitching, decades of trial and error. Real thought and history live in them. Dismissing that as "hollow prestige" is sloppy and inaccurate.

What I can't get onboard with is a different moment.

The moment that accumulated history gets used as a pedestal where the high price itself becomes the victory condition — "so it's expensive," "so it's above you." The moment the price, which should have been a result, swaps itself in as the purpose. The moment a craftsman's history gets repurposed into a token for status.

That's where I feel something cheap. The price is high, but the victory condition is cheap.

What draws me, by contrast, tends to share one quality.

Leather assembled by hand. A tool where the design intent overlaps perfectly with its function. A wood grain revised again and again. A perfume's structure reached after someone wrestled with it for a long time.

There, the history itself is the purpose. The price is a result, not the victory condition.

So what I'm observing isn't high versus cheap. It's whether thought and history are the purpose, or have been made into a pedestal for a token. This isn't a question of superior or inferior taste — it's a question of where the observation is focused.

4. Organizations have an aesthetic sense too

One step up in abstraction.

An aesthetic sense isn't only an individual matter.

Organizations have one too. What gets evaluated, what is felt as beautiful, what counts as "excellent."

Some organizations reward the person who posts flashy numbers; others reward the person tilling the strata. In some, the conspicuous win on a short timescale is what's beautiful; in others, it's the person who can write something that survives five years.

What an organization finds beautiful is its cultural capital itself. And like individual taste, it's formed by the history the organization has accumulated.

So for me, organization design is also a question of aesthetics. How to draw — on the structural side — what counts as "excellent," what counts as "contribution." Part of why I'm building OrbitLens, an apparatus for observation, sits here.

But this piece stays one step before that.

Where does an individual's aesthetic sense come from? If it's formed by class and history, then from a place with neither class nor history — does an aesthetic sense fail to rise at all?

5. An aesthetic that rises from a place with no class

I grew up on Kumejima.

A small island, about 7,000 people, thirty minutes by plane from the main island of Okinawa. It's geographically cut off from the "central" cultural capital. No classical concerts, no permanent contemporary-art exhibitions, no upper-class way of life nearby.

But please don't misread me. Kumejima is a wonderful place.

If anything, a different kind of richness was right there. The sea, the sky, the forest — all on the extension of daily life. The distance between the world and the body is very short. The smell of the tide, the angle of the light, the turn of the seasons, the presence of living things — you know them in the body before you know them as concepts.

And at night, the stars are absurdly close. The Milky Way that thins out in the city comes down whole, right over your head. — Here's a confession: the reason I keep talking about gravity and orbits and stars and the universe in OrbitLens is, probably, this night sky. To be clear, I'm no astronomer. It's just that I spent a little longer than most "seeing the universe with my body."

In hindsight, these were quite valuable cultural capital — only of a different kind than the "central" cultural capital Bourdieu discussed.

What was missing wasn't the richness itself. It was the route that connects that bodily richness to the wider world's aesthetics, stories, and concepts. Classical music, contemporary art, upper-class manners are part of that route — and they didn't reach Kumejima easily.

Following Bourdieu's scheme, the "central" aesthetic that would rise from my geographic position should be quite limited. From the inheritance machinery of cultural capital — home, school, local community — certain tastes simply don't come down.

And yet, there's a certain focus of observation left in me. At least, whether something "holds thought and history" or is "just a token," I observe unconsciously.

Where did it come from?

I arrive at one answer: manga.

6. Manga was a democratization device for cultural capital

Japan's manga culture has one property that stands out.

In Bourdieu's terms, aesthetic sense, cultivation, discernment, the manners of how to live are normally heavily dependent on home environment and class. Each class inherits its "correct" way to read, to listen, to carry oneself. For someone outside a class, accessing that cultural capital is structurally hard.

But in Japan, manga came to stand in a fairly strong position.

Berserk. Chi. Space Brothers. Aoashi. Vagabond. Slam Dunk. Hunter × Hunter. Attack on Titan. These aren't mere entertainment. They've distributed, at a national scale, an aesthetic of how to live, an ethic, heat, a way of facing defeat.

And per episode in a weekly magazine, it's astonishingly cheap. The collected volumes turn up everywhere — convenience stores, used bookshops, libraries. Almost ignoring regional gaps, the same work arrives with the same weight.

Honestly, my household wasn't wealthy at all. I didn't even have the bracket called "a child's allowance." And still, manga reached me. Volumes stacked at a friend's house. The sun-faded Shonen Jump in the waiting area of a barbershop. It came around even to a kid who couldn't buy it — manga had soaked that far into every corner of society. And as an adult, I'm still reading like crazy.

Of course, mass culture democratizing cultural capital isn't unique to Japan. The West has long had its own devices for spreading stories to the many — pulp fiction, comics, Hollywood, TV syndication. Claiming "only Japan is special" would be inaccurate.

Still, within all that, manga came to occupy a particularly strong position in Japan.

One reason is the breadth of what it carries. Beyond mere entertainment, it has distributed — at high density — an aesthetic of how to live, an ethic, heat, a way of facing defeat. Another is how thoroughly it crosses class. Per episode in a weekly magazine it's astonishingly cheap, and it soaked into every place: convenience stores, used bookshops, libraries, the barbershop waiting room. The world reached even the child of a home that class-wise "doesn't have it."

In that sense, manga functioned especially strongly as a democratization device for cultural capital in Japan. A boy on Kumejima could touch the same aesthetic as a boy in an upper-class Tokyo home. Reconsidered, that's an astonishing thing.

7. Manga's strength — it doesn't over-explain

Here, I want to think one step further about what was especially strong in manga.

Manga doesn't preach its ideas.

Guts's back in Berserk. Badeni's obsession in Chi. Musashi's emptiness in Vagabond. The quiet heat in Space Brothers. Ashito's field of vision in Aoashi.

None of them explain in words, "this is the right way to live." And yet, after reading, something stays in the body. Ethics and aesthetics enter not as thought, but as bodily sensation.

This is probably manga's particular strength. A paper or a critique hands you ethics as a concept. Manga lets ethics enter the body as experience, over a character's shoulder.

What enters as experience is strong against being imposed from outside. What's preached as "the right way to live" provokes resistance; the ethic that entered the body over Guts's back is hard to shake loose.

That an aesthetic rising from a place with no class could still hold a core — that depended heavily, I think, on this property of "entering as bodily sensation."

8. But the body alone wasn't enough

Manga placed an aesthetic in my body. But something that only entered the body is hard to handle as is.

"Why is this beautiful?" "What is this heat made of?" "Why did this organization break?" Unless I put what the body knows first into words, draw it out as structure, I can't share it with others, and I can't reproduce it myself.

What filled that gap was thought and philosophy books.

Bourdieu, Weber, Polanyi, Heidegger. Or Kahneman, Diamond, Harari. They placed concept-names onto what I'd been receiving from manga in the body. "Cultural capital." "The iron cage." "Gestell." "Finite and infinite games."

What's interesting is that the two reach the same place from opposite directions.

Reading Thinking, Fast and Slow alongside Pragmatic Thinking and Learning, this structure comes into view: a person takes a structure trained in System 2 (slow, logical) and, through repetition, sinks it into System 1 (fast, intuitive). Mastery is the state of a concept having descended into the body.

In terms of order, for me it went like this:

First, manga placed an aesthetic as bodily sensation (System 1)
Later, thought books gave it the name of a concept (System 2)

To be clear, this is the order in which I received them, not the order the books were written. Bourdieu and Weber were both written long before any manga I read. It's just that within me, one person, the body knew first and the concept caught up afterward.

In that sense, the two aren't separate things. They're the same single observation, confirmed from different entrances. The ethic I received over Guts's back, and Heidegger's "technology turns people into resources," are layered in the same strata inside me.

So this reading log moves back and forth between the manga shelf and the thought-book shelf. The medium doesn't matter. Checking what I received in the body against what I received in concept, on the same desk — that's the actual work of this series.

9. Reading to extract structure

What I want to do in this series isn't to re-read works as a fan.

From manga and from thought books alike, I want to try a reading that extracts structure. Both shelves, read as sample cases of psychological OS and organizational OS.

For instance, from the manga shelf —

Berserk — the danger of community and dream. The moment an ideal-realizing OS turns a community into an offering (organizational OS)
Chi. — the ethic of pursuing truth. An incorrect answer isn't meaningless; ethics lives in hesitation (psychological OS)
Aoashi — organizational structure and field of vision. How a role connects to the whole-system optimum (organizational OS)
Space Brothers — quiet heat and support. How the heat of the unspectacular person holds up a community (psychological × organizational OS)
Blue Giant — the purity of heat. Moving on inner motive alone, not outside approval (psychological OS)
Vagabond — the dialogue with oneself. How the definition of strength turns from outward to inward (psychological OS)

And from the thought-book shelf —

Distinction (Bourdieu) — taste is formed by class and history. The starting point of this very piece
Thinking, Fast and Slow (Kahneman) — System 1 and System 2. A concept descends into the body and becomes intuition
Homo Ludens (Huizinga) — play sits at the root of culture. What a civilization you can seriously play in looks like
Sapiens (Harari) — civilization is made of shared fiction. The myth and aesthetic an organization holds
Imagined Communities (Anderson) — a nation is a shared imagining. A common language makes a faceless community
The Selfish Gene (Dawkins) — culture propagates as memes. The speed gap between good culture and bad
Guns, Germs, and Steel (Diamond) — the difference between civilizations is set by environmental structure. Before blaming people, look at structure
Capital (Marx) — when creativity gets absorbed into the capital-multiplying machine
The General Theory (Keynes) — demand and animal spirits. The hope and fear that move a market
The Protestant Ethic and the Spirit of Capitalism (Weber) — when profit becomes an ethic. The iron cage
The Great Transformation (Polanyi) — the market isn't natural. Re-embedding profit into the human
The Gift (Mauss) — civilization is held by circulation. From the duty to repay, to the responsibility to circulate
Exit, Voice, and Loyalty (Hirschman) — three reactions to discontent. The safety valve that keeps a community from sliding into domination
The Age of Surveillance Capitalism (Zuboff) — the moment observation slides into domination, and the ethic that holds it back
Seeing Like a State (Scott) — when legibility kills local knowledge. Complexity isn't noise, it's resilience
The Question Concerning Technology (Heidegger) — technology shifts how the world appears. Which apparatus will OrbitLens become
Finite and Infinite Games (Carse) — the difference between a game to win and a game to keep playing

None of these as mere impressions, but as sample cases of individual psychological OS and organizational OS. I won't thin out the weight of the original. If anything, by restating in my own words the precision of the structure a work drew, I want to taste it once more.

This is probably also, for me, a return of the gift. As someone who received an aesthetic from manga and concepts from thought books, I want to put both back into the language of structure, and set them down as a clue for someone else's observation.

10. What isn't observed isn't inherited

One last thing.

What this series wants to touch is, in the end, a problem of observation.

What you feel as beautiful is decided by the accumulation of observation. What you feel as "strong," "excellent," "sincere" is decided by the accumulation of observation too. An aesthetic with no route of observation has no reproducibility.

Manga distributed a route of observation to the children of Japan. Across the gap of class, it let them touch the same heat, the same ethic, the same weight of defeat. This is, I think, one civilization.

Thought books then placed concept-names onto that observation lodged in the body. Both, in the sense of handing over a route of observation, are the same. The medium was merely split into body and concept.

As one person who received both, I want to put what I got into words once more, and set it down. Checking what I knew in the body against what I knew in concept, on the same desk. That's the motive behind this reading log.

In #1, I'll take up the Golden Age arc of Berserk.

On the theme "when an ideal-realizing OS turns a community into an offering," I want to read Griffith's strength as a meaning-generating apparatus, and the structure where that very strength flips into danger — set alongside a few cases from real organizations.

This series quotes Uoto's manga Chi. — About the Movement of the Earth (チ。―地球の運動について―, Shogakukan), among other works.

The Japanese version lives on OrbitLens Library.

OrbitLens / machuz

DEV Community: machuz

When AI writes a thousand lines a minute, which code actually holds? (Launching OrbitLens Ace)

Why surviving code

AI made activity meaningless

But read it wrong and it breaks

What the observatory reads

A worked example: point the telescope at React

Two doors, one universe

One honest thing

Why we observe at all

Inside OrbitLens Ace: A Tour of the Observatory

The Observatory Dashboard: 7 axes at a glance

Star Detail: the radar, the insight, the structural summary

Module Topology + Collapse Risk: where the structure is breaking

The Organizational Chronicle: what the codebase lived through

Slack connector: the :orbitlens_chronicle: reaction

Weekly digest: the codebase, once a week

Ambient: the codebase, always in view

Gravity Certificate: a trace that travels

The Whole Arc

Reading Log #9 — Aoashi The Tacit Dimension Thinking, Fast and Slow

1. The dimension of verbalization is different

2. Thinking, Fast and Slow: fast thought and slow thought

3. "Not even thinking?" — compressed System 2

4. The Tacit Dimension: we know more than we can tell

5. Deliberately not verbalizing

6. Non-verbal conversation

7. Honed pride

8. Observation, and the tacit

After the Aoashi run

A confession

Books

Next

Reading Log #8 — Aoashi Finite and Infinite Games Imagined Communities

1. The kingdom's pride and tradition

2. Imagined Communities: a kingdom is made of story

3. Finite and Infinite Games: the game to win, the game to keep playing

4. Soccer for the sake of appeal

5. The merciless sieve

6. No malice is the scariest

7. And still, a pure, equal world

8. Observation, and the kingdom

Books

Next

Reading Log #7 — Aoashi Guns, Germs, and Steel Distinction

1. Why is the ground that grows players so different

2. Guns, Germs, and Steel: strength was decided by environment

3. The soccer pyramid: an accumulation of heat

4. Environment changes the premises themselves

5. Accumulation backs the résumé

6. And still, the individual crosses the sea

7. Environments can be designed

8. Observation, and environment

Books

Next

Reading Log #6 — Aoashi The Selfish Gene The Protestant Ethic

1. I found someone I absolutely want to cultivate

2. The Selfish Gene: the replicator's view

3. To cultivate is to inherit a meme

4. The blissful moment: when the copy surpasses the original

5. The will of the one being cultivated

6. The Protestant Ethic: giving your life to the organization

7. Beware the iron cage

8. Trust, replicated sideways

9. Observation, and the heat to cultivate

Books

Next

Reading Log #5 — Aoashi Seeing Like a State Distinction

1. The gaze that "finds"

2. Seeing Like a State: the power of legibility

3. Soccer makes talent legible

4. The eye is not neutral

5. If you aren't seen, make them see

6. And still, there are those who discover

7. A path is not given

8. Observation, too, is legibility

Books

Next

Reading Log #4 — Aoashi The Philosophy of Sense

1. Aoashi is a story about vision

Slack connector: the `:orbitlens_chronicle:` reaction