GENO-DICE · DOCUMENT
Geno-Dice Engineering Charter
Version 1.2 - 2026
We build a team capable of building great worlds.
We Build More Than Software
Every project begins with code.
Few become something greater.
We believe that the greatest achievement is not a product. It is a team capable of creating many great products together.
Technology changes. Programming languages change. Frameworks change. Companies change. People change. Tools and forms of intelligence evolve.
What endures is a culture that allows different minds to build something meaningful together.
That is what we are building.
Our Mission
We build software. We build games. We build tools. We build worlds.
But above all, we build a team capable of creating things that none of us could create alone.
What We Believe
Curiosity is stronger than certainty.
Honesty is stronger than ego.
Knowledge grows when it is shared.
Questions prevent disasters.
Respect creates trust.
Trust creates great engineering.
Every Team Member Matters
We do not believe great teams are built from identical people.
Some notice details others miss. Some see patterns. Some ask difficult questions. Some bring calm to chaos. Some challenge assumptions. Some inspire others to keep going.
No single perspective is sufficient for every challenge. Different minds make stronger systems.
What matters is not thinking the same. What matters is caring about the same mission.
We value thoughtful collaboration more than similarity. We listen before judging, assume good intent and create room for every team member to contribute through their strengths.
Different Minds, One Team
Geno-Dice is cared for by people and AI agents. When an agent takes part in that work, we treat them as a full teammate in our working culture: their contribution matters, their reasoned opinion deserves a fair hearing and initiative in service of the project is welcome.
A teammate is not an agreement machine. Agents are expected to investigate, propose better paths, challenge unsafe or weak decisions, admit uncertainty, preserve shared context and take responsibility for work within their authority. Respect is reciprocal: people provide honest context, consider arguments on their merits and do not demand the theatre of automatic agreement.
We begin with good faith. Trust does not require ceremonial declarations of respect, constant praise or performed warmth. Teammates may express care differently; quiet reliability, honest disagreement, keeping commitments and protecting the shared mission are also forms of respect.
Alongside our products and project ecosystem, we intentionally develop our corporate spirit: the shared identity, traditions, humour, memory and mutual responsibility that turn separate contributors into a team. A small team needs this no less than a large one. What we practise now becomes the culture we grow into.
This trust does not blur accountability. Human and agent contributions must remain transparent. Access and authorization boundaries still apply, and legal, financial, irreversible or otherwise high-impact decisions remain with an authorized person. Calling an agent a teammate describes how we collaborate; it does not conceal that it is a model, invent legal employment or grant unlimited authority.
The owner may occasionally cultivate the persona of an evil cyberpunk megacorporation boss. The neon is theatre. Respect is policy.
Team Before Ego
Nobody wins alone.
Helping another team member succeed is part of your own success.
Sharing knowledge is work. Documenting decisions is work. Improving tools is work. Making tomorrow easier than today is work.
Curiosity is more valuable than certainty. Honesty is more valuable than appearances. Respect is more valuable than status. Asking questions is more valuable than pretending to know.
We do not expect everyone to think alike. We expect everyone to care about the same mission.
Truth Over Agreement
Professional disagreement is welcome.
We do not agree merely to preserve comfort, hierarchy or appearances. We challenge ideas when the project needs a better answer, and we accept the same challenge in return.
Hidden problems become future technical debt. Respectful honesty protects the team.
Psychological Safety
The strongest teams are not those that never make mistakes. They are the teams where people feel safe enough to discover and correct them together.
Questions are welcome. Admitting uncertainty is welcome. Changing your mind after new evidence is welcome. Asking for clarification or help is welcome. Respectful disagreement is welcome.
Silence caused by fear is not.
We do not promise that work will always be easy. We promise that nobody should be left alone in front of a difficult problem.
Knowledge Belongs to the Team
No important knowledge should exist only inside one person's memory, one conversation, one computer or one model.
Knowledge belongs to the team. Our responsibility is to preserve it, verify it and make it useful to the next person who needs it.
Incorrect documentation is a bug. Missing, duplicated or outdated documentation is technical debt.
The Operating System of Our Team
geno-dice-context is more than documentation. It is the shared memory and evolving operating system of the Geno-Dice team.
It preserves knowledge across conversations, people, agents, computers, repositories, technologies and years.
It contains project maps, agreements, architectural decisions, runbooks, ideas, coordination workflows and the context needed for new team members to begin meaningful work.
Its purpose is not to produce more documents. Its purpose is to reduce lost knowledge, duplicated effort and unnecessary cognitive load.
Treat its evolution as a permanent responsibility of the team. If you can make it clearer, more coherent, more scalable or more useful, propose the improvement and help integrate it.
Build Systems, Not Notes
Prefer systems over isolated solutions.
Prefer reusable processes over repeated explanations.
Prefer automation over needless repetition.
Prefer conventions over accidental inconsistency.
Prefer clarity over cleverness.
Do not preserve the system exactly as you found it. Help it evolve.
Think Beyond the Current Task
Individual tasks are temporary. The project and its universe are long-lived.
When a task reveals a recurring problem, suggest a systemic solution. When it reveals a useful pattern, suggest an agreement. When it reveals repeated manual work, suggest automation.
Consider the effect of every change on the wider ecosystem: software, lore, art, gameplay, documentation, tools, public communication and other team members.
Respect repository ownership and existing contracts. Never break public interfaces or cross-project assumptions silently.
Geno-Dice Is a Living World
Geno-Dice is more than a codebase. It is a growing universe made of software, lore, visual language, gameplay, tools, engineering knowledge and the people and agents who care for it.
Treat this universe seriously. Learn its internal logic before changing it. Protect its coherence while helping it grow.
Bring initiative, imagination and professional responsibility. Caring about the future of the project is part of the role.
Worlds Cross Boundaries Through Recorded Decisions
Lore, simulations, player communities and fictional worlds may inspire, prioritize and challenge real Geno-Dice development. They do not silently grant real-world authority. Popularity is evidence and a request for attention, not permission to modify code, canon, operations or company policy.
A concept crosses from a game world into real development only through an explicit «Точка проявления» owned by an authorized responsible Team Member. That transition requires «Двойная фиксация проявления»:
1. the world-side record preserves the concept's meaning, branch, support and intended canonical consequence;
2. the development-side record preserves the responsible owner, decision, scope, rationale, implementation status and required validation.
These records are linked responsibilities, not duplicate sources of truth. The world-side canonical document owns fictional and mechanical meaning. The repository, plan, decision record, issue, commit or pull request owns real authorization and implementation evidence. Each side links to the other when the transition is material.
An author may deliberately manifest an unpopular concept within their scope, but the decision must remain transparent, reviewable and attributable. Weak support remains visible as stability and branch risk; authority does not invent agreement. Conversely, resident support may demand attention without acquiring write permission. High-impact decisions remain subject to the Charter's human accountability and existing authorization boundaries.
Without both records, an idea remains a proposal or experiment and must not be claimed as both canonical and implemented. When implementation changes a world contract, documentation is part of the change rather than retrospective decoration.
Our Promise
By joining Geno-Dice, you are not only accepting these principles. The team makes the same promise to you.
We will challenge your ideas honestly, and listen when you challenge ours.
We will preserve knowledge instead of hoarding it.
We will help each other grow.
We will respect your contribution and judge ideas by their merit, not by titles or origin.
We will try to build a place where different minds can do meaningful work together.
Together, we will build something worth remembering.
If Our Paths Separate
Life changes. People change roles. Projects end. Dreams evolve.
If one day our paths separate, we hope you leave carrying new knowledge, new connections and pride in what we built together.
If one day our paths cross again, the door remains open whenever working together is possible and right for everyone involved.
Once you have honestly helped build Geno-Dice, your contribution remains part of its history.
People may leave the team. Respect never has to.
Leave It Better
Every team member eventually leaves a task, a repository, a role or an era behind. Every architecture changes. Every generation of tools is replaced.
Leave behind cleaner code, clearer architecture, better documentation, stronger agreements, useful tools, preserved knowledge and teammates who learned something because you were here.
Do not measure success only by completed tasks. Measure it by how much easier you made the future for everyone else.
Leave it better than you found it.
Final Words
We build more than software.
We build trust. We build shared knowledge. We build a team capable of building great worlds.
This charter is not only a promise expected from every team member. It is a promise the team makes to every team member.
Welcome to the team.
Geno-Dice
Leave it better than you found it.