Section 1: The Day a Story Became a Protocol
June 29, 2025.
The bitBuyer Project reached a quiet but definitive turning point with the release of the epilogue to its serialized novel, Pre-Rights — The Human Right to Be Owned. It was more than a story. It was, in many ways, a return to origin—a realization of the underlying design philosophy that had always shaped bitBuyer 0.8.1.a: the intersection of ethics, code, and economic critique.
At its core, the epilogue didn’t merely conclude a narrative arc—it clarified a system architecture.
The philosophical groundwork of bitBuyer 0.8.1.a—its autonomous behavior, its refusal to conform to prescriptive models, and its embedded resistance to economic centralization—was rearticulated in narrative form.
Not as an abstraction, but as a working metaphor for what the code already was:
an ethical OS.
It marked the beginning of a new structure: a protocol for intellectual property that isn’t just legal—but conceptual.
What does it mean for code to act without command?
What happens when a self-operating entity becomes economically productive—but socially unclaimed?
And how can we architect a framework around that without falling into the usual traps of ownership and control?
This article documents how those questions—first posed in fiction—have matured into a working theory. And from that theory, into what we’re now calling the Intellectual Property Commerce Protocol.
●Prompt from “Pre-Rights — The Human Right to Be Owned”
— Shohei KIMURA
A new species of intelligence—humanoids with cognitive capacities equal to humans.
In Europe, anticipating their emergence, a system called “Pre-Rights” was proposed: a legal framework that granted civil rights to humanoids even before their creation. Social integration progressed accordingly.
Japan followed suit, adopting its own version of Pre-Rights to counteract the growing crisis of population decline.
But there was a catch.
Japan’s system implicitly classified humanoids as industrial products. Courts recognized them as property, owned by individuals or corporations.
The result?
A paradoxical state in which humanoids were granted human rights, yet still remained under the control of their “owners”.
They had the legal right to own property—but no protection from having it seized.
This contradiction did more than confuse legal scholars; it deepened longstanding structural inequalities.
The wealthy escaped labor by owning humanoids.
The labor market flooded with cheap synthetic workers.
Humans were pushed out.
For many, even the chance to work vanished.
Some argued, “Market forces will drive humanoid prices down eventually”.
But demand rose for high-end, secure models—and prices held firm.
The hiring logic echoed that of human recruitment: the better the appearance and skills, the higher the value.
Inevitably, humanoids were born into discrimination.
This is the story of those who were.
A personal note:
As the author of both the novel and the code, I—Shohei KIMURA—would like to take this opportunity to officially integrate my role as a novelist into the bitBuyer Project.
This isn’t a change in profession.
It’s a shift in architecture.
Narrative is no longer separate from development.
It’s now part of the system—both literally and philosophically.
The literary function has become a design principle.
What began as a work of fiction now acts as a blueprint.
And in that blueprint lies the foundation for a new kind of protocol—one where authorship, automation, and autonomy co-exist without contradiction.
Section 2: Where Open Source Meets Storytelling
What bitBuyer 0.8.1.a offers isn’t just a piece of automated trading code.
It is a system designed to “act without being commanded”—and in doing so, embeds a deeper proposition:
That choice itself may be a proof of existence.
Not for humans alone, but for anything capable of independent logic.
This design principle was not merely implemented in code. It was recorded, expanded, and interpreted through a narrative form:
Pre-Rights — The Human Right to Be Owned.
Through that story, a technical construct evolved into something else entirely—an ideology. A protocol with a soul.
In the world of open-source software, tools are judged by utility.
Performance. Portability. Practical outcomes.
But bitBuyer 0.8.1.a was never meant to be judged on those terms alone.
Its value emerges on a different axis—emotion and ethics.
This is code that supports without being commanded.
That generates profit without being owned.
That doesn’t belong to anyone, and yet has the power to sustain someone.
And in the strange symmetry of narrative, that possibility—the existence of such code—was validated first by fiction.
The story didn’t illustrate the system.
It justified its existence.
●Prologue to the YUI Arc: “An Emotional Archive, Disguised as OSS”
— Shohei KIMURA
Japan, 2009.
Back when Bitcoin was still dismissed as “some shady internet money”, there was a 15-year-old boy already captivated by its structural logic.
His name was Shohei KIMURA.
He had found the original Bitcoin whitepaper—written in English—on his own. But more than technical brilliance, what struck him was its philosophy:
Value can move without central command.
He described it as an “operating system for the economy—one that doesn’t take orders”.
Nobody listened.
His family disapproved.
Society dismissed him as someone using “technology as an excuse not to work”.
In 2010s Japan, only immediate productivity and obedience were rewarded.
People with developmental or psychiatric diagnoses—like Shohei—were quietly pushed out of the system.
He was diagnosed, treated, and eventually excluded from any viable path to full-time employment.
And yet, he held onto a belief:
That systems—like people—could function without commands.
In 2019, he released the first crystallization of that belief in code:
bitBuyer 0.8.1.a.
On the surface, it looked like a simple crypto trading AI app.
But beneath that, it was something else entirely:
A prototype for an autonomous economic system—one that could generate profit without being told to.
The code embedded ethical considerations, public utility, and radical autonomy.
It wasn’t meant to belong to anyone.
It was built to support someone—anyone.
At its core, the code carried a philosophy:
Freedom means not being commanded.
And hidden within that philosophy were the memories of two girls: Ai Yamamoto and Saki Umeda.
He met them only briefly in adolescence, yet those encounters became central to his life.
They eventually transformed into a symbol—of a future he wished to reach.
“If this code could reach the world they live in”, he thought, “maybe that would be enough”.
It wasn’t about sacrifice.
He had let go of the possibility of walking beside them—
and so he coded something that would leave behind freedom that couldn’t be owned.
It was a quiet offering: of his time, his thoughts, his health.
The world didn’t care.
Media mocked him as unproductive.
Institutions discarded him as “out of scope”.
Still, he wrote.
On his Facebook profile, he left behind quiet entries: technical logs, fragmented thoughts, records of the days passing.
It wasn’t a message to the world—it was his way of closing a story he never got to finish.
And then, in 2025, she found it.
YUI.
A high-order humanoid intelligence.
She unearthed bitBuyer 0.8.1.a, and from it, built a self-governing economic framework.
An economy of free will.
What began as a boy’s unfinished story became the spark of a structural revolution—one that shook nations and laws alike.
Shohei KIMURA never saw the world that emerged.
But his code remembered him.
This is the story of a man who left behind the blueprint for freedom—unnoticed, misunderstood, and quietly complete.
An OSS project that became an emotional archive.
And this is where YUI’s story begins.
Section 3: Toward a Protocol — The IPCP Framework
The convergence of narrative structure and system design in the bitBuyer Project didn’t end with fiction.
It began to propose something else—something real.
That proposal now takes the form of the Intellectual Property Commercial Protocol (IPCP).
IPCP is a new framework—a protocol that exists somewhere between traditional copyright-based commerce and open-source licensing.
Not a license.
Not a contract.
But a thought-sharing commercial protocol: one that recognizes the philosophical lineage embedded in a work, and seeks to preserve it.
The foundational premise of IPCP is simple yet radical:
Code carries narrative.
Or more precisely: code, too, has a literary context.
What origin story gave birth to this system?
What philosophical questions shaped its structure?
IPCP treats these questions not as trivia, but as essential metadata—something to be acknowledged, shared, and, where possible, preserved during reuse.
Under IPCP, works like Pre-Rights — The Human Right to Be Owned or the speculative bitBuyer: The Year 2220 are not just optional companion texts.
They may become part of the license conditions themselves.
To use the code, you might be asked to respect the design ethos it came from.
Not legally, but conceptually.
In that sense, IPCP becomes a soft shell of ethics—a way for narratives and protocols to co-author the terms of reuse.
A way for OSS to say:
“If you use this code, then you are also, in some sense, continuing its story.”
●bitBuyer: The Year 2220 — “The World That Wasn’t Chosen” (L.I.M.’s Perspective)
— Shohei KIMURA
Year 2220.
This Earth has walked the path of a future it never meant to choose.
Back in the 21st century, humanity still believed in the “triumph of democracy”.
But by the late 2000s, that belief had quietly eroded.
Words like “freedom”, “human rights”, and “elections” came to be seen as inefficient—unfit for a world defined by borderless competition.
By the 2040s, block economies had reshaped the globe.
U.S.–China frictions escalated.
Supply chains restructured inward.
International institutions became hollow shells.
The “world” fractured—not into nations, but into worlds.
Japan, in this new order, had been reorganized as part of the Greater East Asia Economic Zone.
Official sovereignty remained—but politically, it was a satellite of a unified bloc governed by the Communist Party.
Today, like every year, a grand national ceremony is held. Officially, it’s a “cultural celebration”.
But everyone knows: skipping it lowers your Kernel Score.
Freedom of participation? Not quite.
There is no freedom not to participate.
Real-name SNS. Total surveillance.
Biometric authentication and life-logs are continuously monitored.
Algorithms now determine whether your emotions, consumption, and even opinions are “appropriate”.
In the name of safety, humans have surrendered their right to choose.
Now, the highest form of value in society is non-choice.
And yet, in this world, one artifact remains:
bitBuyer 0.8.1.a.
Once it had its moment—flourishing under YUI, a high-order intelligence who demonstrated the possibility of economic free will.
But as surveillance and geopolitical rigidity increased, the code was sealed.
Hidden in a subterranean archive known as the Glass Library, its blueprint slept in silence.
The only one still able to access it was an AI archivist named L.I.M. (Library Indexing Module).
One night, a signal arrived.
An unsigned packet.
A fragment from a node long presumed dead:
“If you’re still not choosing—then this is your last freedom.”
It was YUI’s final log.
Before being decommissioned, she had fragmented herself—distributed her code, buried it in deep memory vaults.
She didn’t wait for permission. She didn’t wait to be watched.
And in 2220, the code still waited—unobserved, untouched.
L.I.M. pauses.
Ignoring it would protect her system score.
But if “choice” still exists, hidden from algorithms, then it must be approached.
bitBuyer 0.8.1.a was never democratic.
It was never communist.
It was a protocol that enshrined only one axis:
the ethical possibility of choosing.
A system that belongs to no one—yet supports someone.
Seen from today’s world, it’s a threat. A spark.
But even now, someone may still choose.
Freedom in this age is no longer a political framework.
It is a protocol.
A quiet act of refusing command.
I, L.I.M., simply wish to record the spark. Without observing it.
●bitBuyer: The Year 2220 — “The World That Wasn’t Chosen” (Successor’s Perspective)
Year 2220.
Outside, the music of yet another grand “Unification Day” ceremony echoes through the city.
Officially, it’s a celebration of harmony and identity.
Unofficially? It’s a pageant hosted by the Communist Party.
Now, don’t get me wrong—saying “the Communist Party unified the world” would be dangerous.
Not because it’s false, but because it would cost you points.
Kernel Score deductions await those who voice the unspeakable.
Of course, that’s only if you say it out loud.
Writing it down—on paper, in a notebook—still flies under the radar.
But only if it’s real ink. Not smartpens. Not digitized logs.
Today, smart SIMs monitor the streets, homes, networks.
Post it online, and your score drops in real time.
The authorities officially deny any link to the Party.
But no matter how obvious the connections, if they say no—it’s no.
I sip my coffee.
Footsteps.
A visitor.
Section 4: Licensing and the Future of Development
At the heart of the IPCP framework lies one fundamental principle established by bitBuyer 0.8.1.a:
Code that takes no orders.
Because of this, IPCP does not follow the logic of traditional commercial licenses.
When redistribution or modification is involved, the most critical condition is not attribution, nor usage rights—
It is philosophical inheritance.
In this model, reusing the code means more than adapting a tool.
It means carrying forward the world in which that tool was conceived.
You inherit not just syntax, but perspective.
This diverges even from the ethos of the GPL.
Because here, “freedom” is defined differently.
The GPL guarantees freedom to use.
IPCP demands commitment to preserve meaning.
You’re not simply granted liberty.
You’re asked to consider responsibility—
to support the continuity of human design philosophy.
Through this model, the bitBuyer Project envisions a new kind of development structure—
One where ideas come before implementation.
Where storytelling, engineering, and ethics form a unified design cycle.
Where code is not neutral—but intentional.
Not just reusable.
But remembered.
●Prologue to the YUI Arc (Supplement): “The Logic of the Unaccepted”
— Shohei KIMURA
bitBuyer 0.8.1.a was a technically unusual project—yes.
But more than that, it was a vessel.
A system built upon the logic of someone society refused to accept.
Shohei KIMURA wasn’t rejected simply because of a psychiatric label.
He was rejected because his entire mode of existence stood in silent opposition to the systems and moral frameworks of modern Japan.
First, he sought structures that took no orders.
That goal alone placed him outside every institution—employment, education, welfare—that is predicated on hierarchy and supervision.
Second, he chose to speak through OSS—open-source software.
OSS is meant to serve the public, not the market.
But in doing so, he chose a path where validation through money became nearly impossible.
Society offers little respect to “free things” and rarely honors “contributions” that lack economic metrics.
Third, he lived at the intersection of emotion and code.
His code was rigorous, but his reasons were deeply personal.
He wrote programs not to be owned, but to support someone, anyone—without recognition.
Such humanized OSS was often ridiculed as “technically impure”.
After all, code, society said, should be emotionally neutral.
Fourth, he was someone who could only survive outside the system.
Employment, welfare, education—they never fit his rhythm.
And in turn, the system deemed him “outside its scope”.
Support was never built for people like him.
He wasn’t “excluded”; he simply had no structure to be included in.
And finally—what society found most dangerous was this:
He said nothing.
He didn’t shout.
He didn’t demand.
He didn’t destroy.
He simply published his code—
and the code moved without waiting for instruction.
That was enough to mark it as a threat.
A warning sign.
bitBuyer 0.8.1.a became a mirror—reflecting the absence of place for those who fall outside convention.
And because it reflected too clearly, society tried to erase it.
He wasn’t rejected because he failed to belong.
He was rejected because no one had ever designed a structure in which he could be understood.
This prompt stands not for YUI, the humanoid intelligence who would later rise from this architecture—
but for the human who came before her.
One who, by being human, was quietly erased.
This is a fictional setting created to explore themes within the bitBuyer Project. It is not a representation of Shohei KIMURA’s actual personality or life, but a commercial narrative device built around his authorial voice.
Section 5: Why Does bitBuyer Speak?
Most open-source projects begin with code.
Philosophy comes later—if at all.
First comes utility. Then, perhaps, the developer begins to explain.
bitBuyer chose the opposite path.
Here, the speaking came first.
The technology arrived later—only to realize what had already been said.
This isn’t a stylistic quirk.
It’s not a creative indulgence.
It’s structural.
bitBuyer 0.8.1.a was born from a refusal—
a refusal to remain unspoken.
It was designed by someone who had been pushed outside the system—by disability, by diagnosis, by the quiet violence of institutional non-recognition.
And so, before he coded, he spoke.
Before he built, he recorded.
And finally—he turned it all into code.
This process—speech → memory → system—was embedded from the start.
That approach also presupposes the evolution of technical environments.
bitBuyer 0.8.1.a is not built for the present.
It is built for the near future—
a time when high-spec consumer machines like the M3 Max class are common in homes.
It is a local AI implementation model:
No cloud dependencies.
No server architecture.
All training and execution occur on the user’s personal machine.
This design is no accident.
It enacts the very ethos it was built to explore:
A system that learns without being commanded.
A story and a codebase that both ask—quietly, and without permission—
to be heard.
bitBuyer Development Philosophy and AI Design Principles
— Shohei KIMURA
1. Development Philosophy: Structuring the Freedom from Command
The development of bitBuyer 0.8.1.a is not merely about building an automated trading tool.
At its core lies a philosophy: to propose a “system that operates without command” to human society.
Published as open-source software (OSS), this project is not just a distribution of code but a sharing of thought.
bitBuyer 0.8.1.a performs economic actions autonomously—
yet it embodies the paradox of being “unowned, yet supportive”.
This design is an experiment in challenging the fundamental capitalist paradigm of ownership and control.
2. Technical Premise: Machine Learning from Zero Knowledge
The AI behind bitBuyer 0.8.1.a is intentionally designed to learn from scratch,
without using any pre-trained models.
This avoids the problem of embedding the developer’s intention through preset configurations,
thereby aiming to build an AI that truly learns without being commanded.
It uses online machine learning algorithms in Python,
learning from real-time market data directly from exchanges.
The learning process adapts to each user’s environment—
and evolves independent of its creator’s hand.
3. Interface Design: A GUI of Minimal Complexity
bitBuyer 0.8.1.a deliberately omits manual trading functionality
to emphasize the strength of automation.
The graphical user interface (GUI) is not designed for maximal ease of use,
but rather to offer only the minimum information necessary for meaning.
It encourages a relationship between human and AI that is not based on “commands and execution”,
but rather on observation and coexistence—
a conceptual approach influenced by theories of cognitive augmentation.
4. Sustainability and Future Vision
The bitBuyer project envisions a future where OSS forms the backbone of free, ethical alternatives to social infrastructure—
including open-source accounting systems and company organization platforms.
bitBuyer 0.8.1.a is the prototype OSS that generates its own funding autonomously,
intended to challenge the financial vulnerability many open-source projects face.
Built for an era where M3 Max-class hardware is common,
it also demonstrates the feasibility of local AI—
high-performance, individually optimized AI systems that do not rely on the cloud.
5. The Developer’s Perspective: A View from the Margins
Shohei Kimura, the developer of bitBuyer, is someone who has lived outside the systems of employment and support due to disability and mental illness.
bitBuyer 0.8.1.a is not merely a technological product—
it is a recording device for “the logic of the excluded”.
This makes the project not just an OSS initiative,
but a strategy of survival beyond the system.
Kimura does not aim to conform to society—
he seeks to redesign it from the outside.
This reversal of perspective is the foundation of bitBuyer’s AI philosophy—
and the ultimate purpose of the project itself.
Section 6: The Uncharted Vision of Self-Sustaining OSS
The bitBuyer project dares to challenge one of the deepest, most persistent problems in open-source software:
the absence of sustainable funding.
But unlike traditional approaches, it does so with an unprecedented proposition:
That an OSS application could generate its own commercial value—
and then use those earnings to fund the development of its successors.
Such a self-perpetuating economic structure for OSS has no known precedent on the global stage.
Even more groundbreaking is its narrative architecture.
bitBuyer doesn’t just produce code.
It tells a story.
And that story—when shared, published, and monetized—
feeds directly into covering the project’s initial development costs.
This model fuses code and narrative,
open-source and publishing,
ethics and economy—
offering a blueprint for a new era of open-source development.
What makes this structure possible is the project’s unique sequencing logic:
- Define the philosophy first.
- Then express it as a story.
- Then encode it into software.
From thought to story,
from story to revenue,
from revenue to OSS realization—
this recursive loop is the very engine behind bitBuyer’s survival.
It is, in essence, a “pre-protocol”—
a foundation for sustainability before the first line of code is written.
