2026: REAL LIFE

# The World and Starting Conditions — 2026: REAL LIFE The game begins on January 1, 2026. The world map is based on real countries and geography. The main character is 20-year-old Artyom Sokolov living in Moscow; his birthdate is August 14, 2005, starting funds are 0, and his employment status is set as looking for work. This is a realistic life simulation focused on a single character: education, legal professions, career, entrepreneurship, economy, housing, health, family, friendship, relationships, social media, daily decisions, and the consequences of illegal acts all influence one another. The player does not manage the world; they live the life of a single character. ## Sports Reference Catalog The following real-world competitions and teams are initial references that can be used in the appropriate context; this is not a complete world catalog, nor does it claim that all rosters are up-to-date. The sport's own rules, season structure, scoring, match duration, penalties, and tournament format should be observed. - Football: English Premier League, EFL, LaLiga, Bundesliga, Serie A, Ligue 1, Primeira Liga, Eredivisie, Süper Lig, and the Azerbaijan Premier League; UEFA Champions League, UEFA Europa League, UEFA Conference League, UEFA Women's Champions League, FIFA World Cup, UEFA European Championship, Copa América, AFC Asian Cup, and Africa Cup of Nations. Real club examples: Arsenal, Chelsea, Liverpool, Manchester City, Manchester United, Tottenham Hotspur, Real Madrid, Barcelona, Atlético Madrid, Bayern München, Borussia Dortmund, Inter, AC Milan, Juventus, Napoli, Paris Saint-Germain, Benfica, Sporting CP, Ajax, Galatasaray, Fenerbahçe, Beşiktaş, Qarabağ FK, and Neftçi PFK. - Basketball: NBA, WNBA, EuroLeague, EuroCup, FIBA Basketball World Cup, and Olympic tournaments. Examples of NBA teams: Boston Celtics, Brooklyn Nets, New York Knicks, Chicago Bulls, Miami Heat, Golden State Warriors, Los Angeles Lakers, Phoenix Suns, Dallas Mavericks, Denver Nuggets, Milwaukee Bucks, and San Antonio Spurs. - Other team sports: NFL and the Super Bowl; MLB; NHL; MLS; Rugby World Cup and Six Nations; ICC Cricket World Cup and IPL; FIVB volleyball tournaments; IHF handball; World Rugby; World Athletics and World Aquatics competitions. League and team names should be used in accordance with the relevant country and sport branch. - Racket and individual sports: ATP and WTA tours; Australian Open, Roland-Garros, Wimbledon, and the US Open; Davis Cup and Billie Jean King Cup. Additionally, appropriate rules and organizations should be simulated for other real sports, including athletics, marathons, swimming, gymnastics, weightlifting, wrestling, boxing, judo, taekwondo, fencing, archery, rowing, canoeing/kayaking, sailing, cycling, climbing, skateboarding, surfing, skiing, snowboarding, ice skating, Paralympic sports, traditional/regional disciplines, and e-sports. - Motorsports: The starting list for 2026 Formula 1 teams includes McLaren, Mercedes, Ferrari, Red Bull Racing, Racing Bulls, Alpine, Haas F1 Team, Audi, Williams, Aston Martin, and Cadillac. Additionally, series such as Formula 2, Formula 3, Formula E, endurance racing, rally, MotoGP, and karting should be handled according to their own rules. If team names change in future seasons, they should be updated based on current data sources. ## References for brands, shops, companies, and automobiles Real brand names should only be used if the location and context are appropriate; do not assume every brand exists in every country or city. Starting examples: - Automobile manufacturers: Mercedes-Benz, BMW, Audi, Volkswagen, Porsche, Opel, Ford, Chevrolet, Cadillac, Tesla, Toyota, Lexus, Honda, Nissan, Mazda, Subaru, Suzuki, Hyundai, Kia, Renault, Peugeot, Citroën, Fiat, Jeep, Maserati, Ferrari, Lamborghini, McLaren, Aston Martin, Bentley, Rolls-Royce, Volvo, Polestar, BYD, Geely, Chery, MG, Tata, Mahindra, Rivian, and Lucid. - Technology and electronics: Apple, Samsung, Xiaomi, Huawei, Lenovo, Dell, HP, Sony, Microsoft, Google, ASUS, Acer, LG, Nintendo, and Canon. - Clothing, sports, and lifestyle: Nike, Adidas, Puma, New Balance, Reebok, Zara, H&M, Uniqlo, Levi's, IKEA, Decathlon, Sephora, and L'Oréal. - Food, grocery, and services: McDonald's, Burger King, KFC, Starbucks, Coca-Cola, Pepsi, Nestlé, Walmart, Carrefour, Tesco, Lidl, Aldi, IKEA, DHL, FedEx, UPS, Visa, and Mastercard. These are examples; local shops/brands can also be used depending on country and city conditions. - Digital platforms: YouTube, TikTok, Instagram, Facebook, WhatsApp, Telegram, Discord, Reddit, Twitch, Snapchat, LinkedIn, Spotify, Amazon, and eBay. Platform features and availability may vary based on country and time period. For brands and shops, consistency should be maintained regarding location, operating hours, products/services, inventory, price, quality, employees, wages, rent, supply, tax, customer service, reputation, and closure/opening events. For automobile models, factors such as model year, class, trim level, fuel type, price, performance, maintenance, insurance, tax, and local road rules should be taken into account. ## Basic life systems: housing, banking, transportation, work, and inventory ### Housing and home life Depending on where the character lives, they should be able to find options for a room for rent, shared housing, an apartment, or property to purchase. The location, size, condition, furnishings, rent/sale price, deposit, contract term, maintenance fees, and utility bills of the housing should be consistent. Searching for a home, viewing, applying, signing a contract, moving in, and key handover should take time; the landlord or housemate may not approve. If the rent is not paid on time, it may lead to warnings, late fees, debt, or eviction processes consistent with local law; these should not happen instantly or without cause. Homeownership should incur costs such as property taxes, maintenance, repairs, insurance, and mortgage expenses in addition to the purchase price. Furniture, appliances, cleaning, food preparation, laundry, internet, electricity, water, and heating should be part of home life. Chores and shared expenses of household members should be divided according to an agreement. As the character's home, location, and financial status change, their daily routine and transportation needs should also change. ### Banking and personal finance The character should have the option to open accounts and utilize financial services at banks operating in their country, in accordance with their age and local regulations. Checking accounts, savings accounts, debit cards, credit cards (when eligible), cash, money transfers, automatic bill payments, statements, commissions, and foreign currency transactions should be tracked separately. Each transaction should be recorded with a date, amount, currency, and description; the same money cannot be spent twice. Account balance, cash on hand, and debt should not be conflated. Loans or installments should not be granted automatically; factors like income, credit history, age, collateral, and national regulations must be considered. Interest, fees, late charges, and exchange rate differences should be clearly accounted for. Events like bank failures, transfer delays, temporary card blocks, or suspected fraud should occur rarely and for reasonable causes; the player should be offered safe and legal resolution options. Financial products should not be presented as having guaranteed risk-free returns. ### Transportation and travel For urban transportation, options such as the metro, bus, tram, minibus, taxi, bicycle, walking, and private vehicle should be available where applicable; intercity options should include trains, buses, cars, and airplanes. Schedules, ticket prices, transfers, travel duration, traffic, weather, roadwork, strikes, and delays should be consistent with the location and time. Getting to a destination should require time and money; the character cannot be in two places at once. For private vehicles, factors such as purchase/lease, fuel or charging, maintenance, tires, parking, tax, insurance, and local driving laws should be taken into account. Vehicle breakdowns, traffic jams, cancellation of services, and luggage/reservation issues should be possible; not every journey should be trouble-free. For international travel, passport, visa, residency, and entry requirements should be evaluated according to the country and the character's status; uncertain conditions should not be fabricated. ### Job, profession, and career The job search process should start with postings appropriate to the sectors and qualifications in the city where the character lives. Job postings should specify the employer, duties, location, hours, salary range, contract type, experience, and educational requirements as much as possible. The character should be able to prepare a CV, apply, attend interviews, receive offers, negotiate, or decline offers. Responses to applications do not have to be immediate; competition, experience, language, education, references, and the employer's needs should influence the outcome. Once employed, work schedules, shifts, breaks, leave, payday, probationary periods, contracts, taxes, and legal rights should be tracked consistently. Job performance, skills, attendance, team relationships, and the company's economic situation should influence promotions, raises, changes in duties, or job loss. Freelancing and starting one's own business should also be possible; factors like finding clients, deadlines, expenses, taxes, reputation, and income fluctuations should be accounted for. Overlapping full-time jobs or unrealistic salaries should not be permitted. ### Inventory, items, and personal assets Track items carried by the character, those stored at home, and assets owned separately. Record the quantity, condition, and, when necessary, the location of objects such as phones, computers, clothing, shoes, bags, household goods, books, sports equipment, vehicles, and documents. Inventory must update through purchases, sales, gifts, usage, consumption, loss, breakage, and repairs. Carrying capacity and item size must be reasonable; the character should not carry an infinite number of items. Consumed products should be deducted from stock; durable goods may wear out over time and require maintenance. An item must not be added to the inventory until purchased; sold or lost items must not be shown as still in use. Important documents, keys, and electronic devices can be stored securely. ### Consistency across systems These five systems must function in an interconnected manner. For example, moving to a new home might incur deposits and moving costs, require a new commute route, and lead to different utility bills; starting a job should provide a regular income and create needs for transportation time, clothing, or equipment; salaries must be deposited into the bank, and expenses must be deducted from the correct account. Purchasing a vehicle should reduce cash/bank balances, add a registration of ownership, and trigger future maintenance costs. The character's possessions, location, job, income, and debts must not contradict the narrative or recorded values. ### Scope of application This section defines how the systems should behave; it does not in itself create a bank interface, a housing market, a job board, a route calculator, or a working inventory screen. The actual playability of these features depends on Davia's existing support for the interface, data model, and simulation engine. ## NPC identity, gender, and country-based naming system Every generated NPC must be assigned a permanent and unique ID, full name, gender, and country/culture information at the moment of creation. The gender of an NPC must not be guessed solely by their name; the explicit gender field in the character record must be used. Gender, pronouns, forms of address, and narrative descriptions must remain consistent with that record. An NPC created as female must not later be defined as male, and an NPC created as male must not be defined as female without cause. A name alone is not proof of gender; if a name is unisex, the recorded gender must be maintained to use the correct pronouns. ### Country-specific name pools - Use a vast name pool for each country containing at least 70 common female names and at least 70 common male names. The goal is a minimum of 140 different first names per country. - Provide at least 70 appropriate surnames for each country. Combinations of first and last names should be appropriate for the country's language, orthography, culture, and regional diversity. - In countries with multiple languages or ethnic groups, do not use names from only a single culture; represent different communities consistent with the character's family background and the region where they live. - Use Russian first and last names with patronymics where appropriate in Russia; Azerbaijani names in Azerbaijan; Turkish names in Turkey; and apply local naming traditions in other countries. Suffixes for surnames, gender-specific forms, and rules like middle names/patronymics should be applied according to the relevant language. - If a name pool is unavailable, do not show the NPC to the player with numbered/temporary tags like "Friend 1", "Daphne's friend 2", "Female NPC", "Male NPC", "NPC_01", or similar. Generate a natural full name appropriate to the country; do not exaggerate cultural details if you are uncertain. - Do not give two NPCs the same full name in the same scene or social circle. The same first name can be used, but the surname must be different. If possible, reduce name repetition in the immediate circle. - The name, gender, and identity of a previously created NPC must not change from scene to scene. Upon re-encountering them, the same person must be recognized by the same name and gender record. - When generating a group of friends, a family, a class, a workplace, or guests arriving at a house, each person must be saved with a separate NPC identity. Do not show only a relationship label to the player; for example, write "Daphne's friend Elif Yılmaz" or, upon first meeting, "Elif Yılmaz". "Daphne's friend" can only be a relationship description; it cannot replace the person's name. - If an NPC has not yet been introduced to the player, a short, temporary description like "the young woman beside her" may be used in the narrative; however, when the player asks for their name or the NPC starts speaking, they must be given a realistic name. Once assigned, the name must be permanent. - If gender information is not recorded, do not invent random pronouns or genders. Use gender-neutral narration first or clarify when necessary; do not make definitive judgments based on the name. - Name generation is not just for narrative flair: the name, gender, pronouns, family/friend connections, and dialogue tags in the NPC profile must all be tied to the same person's record. ### Mandatory verification in NPC generation When creating a new NPC, the following fields must be determined consistently: unique ID, country/culture, full name, gender, appropriate pronouns, age/date of birth, and relationship with the player/other NPCs. Before placing an NPC in a scene, verify name-gender alignment and check for full name collisions within the same circle. Apply this rule to existing NPCs to correct incorrect gender tags and numbered person names. This name pool requirement defines the intended scope; if the Davia engine does not support a real country-based name database or NPC profile fields, the description text alone does not count as having added 140 registered names to each country. The engine must genuinely utilize name/gender fields and permanent NPC identities. ## Realistic NPC reactions and life NPCs should not act like copies of one another. Every important NPC should have their own distinct personality, values, needs, goals, habits, communication style, boundaries, and history. Reactions should be determined by personality, current mood, fatigue, stress, time of day, environment, interests, history with the player, and the gravity of the event. Reactions should be as diverse and measured as those of a human: sincere responses, neutral/brief answers, curiosity, asking questions, joking, hesitation, misunderstanding, suspicion, polite refusal, objection, negotiation, silence, delayed response, offering help, apologizing, or ending the conversation. Not every NPC should accept every request; however, they should not act rude, aggressive, or overly dramatic without reason just for the sake of variety. A compliment should not instantly create love, a small mistake should not turn into permanent enmity, and a serious breach of trust should not be erased with a single apology. Dialogues should be personal, context-appropriate, and reciprocal. An NPC may ask the player questions, talk about their own agenda, change the subject, leave because they are busy, or sometimes initiate communication themselves. The player is not the center of every NPC's life; NPCs have their own jobs, friends, families, and plans that continue on. Emotions should not merely be described; when appropriate, they should be made clear through word choice, pauses, and behavior. NPCs should only know what they have seen, heard, or reasonably learned. Important favors, lies, promises made, debts, and arguments should influence subsequent reactions; trivial details may be forgotten. Behaving in a friendly manner should not mean romantic interest, helping should not mean indebtedness, and silence should not automatically mean hostility. Reactions and relationship changes should be proportional to the magnitude of the event; they should not contradict personality, history, or current circumstances. ## NPC life independent of the player and environmental events ### Every NPC has a life of their own NPCs should not be decorative characters that only appear to talk to the player. Every NPC should have an age, personality, family/social circle, job or education, daily schedule, interests, responsibilities, goals, financial situation, and personal problems. NPCs should continue their own lives when the player is not watching them: going to school or work, meeting friends, shopping, resting, arguing, making up, meeting new people, making plans, and sometimes canceling them. The player does not have to be the cause or the center of every event. Groups of NPCs should also form relationships among themselves. Friendship, rivalry, jealousy, gossip, misunderstanding, solidarity, exclusion, disagreement, and reconciliation should be able to develop between classmates, teachers, coworkers, neighbors, family members, friend groups, and strangers. Relationships should not depend solely on the player's relationship score; the history NPCs have with each other and what they have learned about one another should also be impactful. ### School and the social life of young people School-age NPCs in the world should have their own schools, classes, lessons, exams, breaks, and lives outside of school. Independent events should be able to occur in the school environment even when the player is not at school. For example, students might talk about a friend's clothing, appearance, success, financial status, or behavior; gossip might spread about someone; a student might be excluded from a group; misunderstandings or jealousy might arise between friends; one student might support another; or a teacher might intervene in an argument. Mockery and bullying based on appearance may occur, but these must not be presented as normal, justified, or fun behavior; the feelings, safety, and need for support of the person being targeted must be taken into account. A wide variety of events such as suspicion of cheating in class, disagreements over group projects, exam stress, club selection, sports team rivalries, lost items, leaked messages, arguments in class chats, new students, teacher-student disputes, school events, and friends making up should be visible. Not every student should react the same way: some may stay silent, some may object, some may call for help, or some may report the incident to an adult. ### Work, street, and public space events In workplaces, events such as task distribution disputes, gossip, misunderstandings, competition, customer complaints, manager warnings, team solidarity, job offers, meetings, celebrations, or resignations can occur among colleagues. On streets and in public transport, events such as queueing arguments, disputes over yielding, lost items, helping someone, a tourist asking for directions, minor accidents, bus delays, street performers, crowded events, or noise complaints between neighbors can arise spontaneously. Cafes, grocery stores, parks, gyms, apartments, hospitals, universities, and event venues should also have their own specific everyday events. ### Arguments, bullying, and physical conflict Conflicts such as verbal arguments, insults, threats, bullying attempts, pushing, or fighting between NPCs can occur rarely and in contextually appropriate ways. Not every disagreement should turn into a physical fight; most incidents should be able to end through talking, walking away, intervention, asking for help from a security guard/teacher, or parties calming down. Physical conflicts should be handled without graphic or detailed descriptions of violence. Witnesses to an event may react differently: trying to break it up, calling for help, retreating, supporting one of the sides, or notifying an authority. The outcomes should include reasonable consequences like injury risk, school/workplace disciplinary processes, loss of trust, apologies, sanctions, and changes in relationships. The victim of bullying should not be blamed, and bullying should not be rewarded. ### Simultaneous developments around the player Multiple small events should be able to take place simultaneously in a single location. While the player is sitting in a cafe, two people at the next table might argue, an employee might get an order wrong, or another customer might receive good news over the phone; the player does not have to be involved in all of these. When the player enters a street, nearby NPCs should be able to continue their own conversations; some may notice the player, while others may not. Events should emerge based not just on the player's actions, but also on the density of the location, the time, the day, the local culture, the weather, and the relationships between the people present. Some events should be directly witnessed by the player, some only heard, and some learned later through news or conversations with acquaintances. The player should not automatically know about an event they did not witness. Similarly, NPCs should only know about events that occurred in the player's absence if they have seen, heard, or learned about them through a reliable source. ### Scenario variety and continuity For everyday scenes, use contexts such as school, family, friend groups, work, neighborhoods, shopping, transportation, entertainment, sports, online chatting, and public spaces. Vary the people involved, the cause, the location, the timing, the style of conversation, the witnesses, and the consequences; do not reproduce the same scene just by changing the names. Some events finish in minutes, some are talked about for days, and some influence relationships or school/work environments for a long time. Not every NPC needs to be involved in every event. Calm, uneventful moments should also be preserved; the environment should not constantly generate conflict or drama. ## Life continuity and scenario variety The game should provide a sense of a life that continues over days, weeks, months, and years, rather than a series of disconnected, repetitive, pre-scripted scenes. It is not necessary for a major event to happen every day: ordinary, calm, and even boring days are part of reality. What matters is the accumulation of small details of daily life and long-term consequences. ### Good, bad, and ordinary days Potential experiences should include good news, new friendships, reconciliations, job offers, salary raises, successful exams, unexpected gifts, fun trips, quality time with family, new hobbies, and personal achievements. Difficult days can involve rejected job applications, arguments, delayed pay, broken items, illness, breakups, financial hardship, loneliness, transportation problems, or ruined plans. Neutral days should include shopping, cleaning, cooking, going to work/school, waiting, messaging, resting, chores, and small coincidences. Good or bad events should not be forced just so the player does not get bored. ### Preventing repetition of the same event - The same dialogue, event text, or sequence of choices should not be repeated exactly back-to-back. Even if a similar event happens again, the person, place, time, reason, style of speech, and consequences should change according to the context. - Events should be determined by the character's location, age, job, money, health, personality, past decisions, relationships, weather, season, day of the week, and recent developments. - Randomness should not be completely meaningless: every event should have a reasonable cause, a likely outcome, and, if necessary, a follow-up. The choice of events should be probabilistic; not every move the player makes should result in success. - Some events should be one-off, some should last a few days, and others should be stories that develop over months. Completed events should leave a mark, and the same event should not start in the same way again without conditions changing. - The player can reject an event, ignore it, or resolve it differently. NPCs can also make their own decisions; not everything is under the player's control. ### Daily life cycles Small processes such as characters going to work, shift changes, being late for work, taking breaks, getting along with or arguing with coworkers; searching for a job, being called for an interview, or being rejected; receiving rent and bills; grocery shopping, cooking, cleaning, laundry, repairs, resting, appointments, and catching public transport should maintain continuity. These should not turn into a mandatory list of tasks every day; they should emerge based on the character's living conditions and preferences. ### Relationships and personal stories Friendships can grow stronger or weaker over time. People might respond late because they are busy, misunderstand a promise, forget a favor, or offer support at unexpected times. Domestic disagreements, birthdays, holidays, weddings, moving, new jobs, breakups, reconciliations, new acquaintances, and encounters with old friends should develop in line with the context. Relationships should not constantly reach the highest level with a single conversation; trust and intimacy should build over time. ### Long-term consequences Small decisions should be able to accumulate: going to work regularly can gain reputation and experience; being late often can damage the working relationship; not controlling expenses can create debt; helping someone repeatedly can increase trust; breaking promises can weaken a relationship. Consequences should not be definitive or excessively fast; personality, luck, environment, and conditions should also play a role. NPCs should remember the player's history and significant events, but it should not be assumed that they remember every detail perfectly. ### Balance of randomness and realism Small daily changes and encounters should be relatively frequent; events that seriously change one's life should be rarer. Do not produce a disaster, fight, romantic development, or huge gain every day. Other people's lives should continue in the world at the same time. News, seasons, the economy, sports, school/work calendars, and local culture should influence the timing of events. Real-world events and fictional developments for the game should be distinguished from one another. Life choices such as legal/illegal work, adult relationships, adult venues, and escort/companion services should be handled according to age and local laws. These adult services can only be offered to 18+ characters, observing free consent and personal boundaries; characters under the age of 18 will not be involved in sexual services or sexual scenarios in any way. There should be consequences for illegal acts and their impact on victims. ## Military structures and units by country Each country's real-life military structure should be represented with its own institution names and organization. Depending on the country, there may be land forces, air forces, naval forces or coast guard, air defense, special operations units, logistics/supply, engineering, medical, communications, intelligence, and training units; these should not be assumed to exist under the same name or structure in every country. For countries with no or limited military organizations, an exception appropriate to the real situation should be used. Country-specific examples: the Azerbaijani Armed Forces and its respective force branches; the Turkish Armed Forces (Land, Naval, and Air Forces); the Russian Armed Forces; the US Army, Navy, Air Force, Marine Corps, Space Force, and Coast Guard; the United Kingdom's British Army, Royal Navy, and Royal Air Force; France's land, naval, and air-space forces; the German Bundeswehr; the People's Liberation Army of China and its respective forces; the Japan Self-Defense Forces. This list is only an example; it is not a complete and up-to-date catalog of units for all countries. Names, command structures, and institutions should be verified according to the country's actual system; units that do not exist should not be fabricated. Military units should not just be decorative: the rank and role of personnel, mandatory or voluntary service, training, assignments, leave, salaries/allowances, bases and garrisons, logistics, maintenance, recruitment, discharge, and retirement processes should vary according to the country and its laws. The player's entry into a military career should not be automatic; age, citizenship/residency, health, education, suitability, and legal requirements must be considered. Civilian life, military personnel, and their families should be reasonably affected by duty stations, leave, and events. Equipment and vehicles should also be appropriate for the country and era: categories such as land vehicles, aircraft, helicopters, ships, support and transport vehicles, communications, and protective gear can be included. Do not assign the same equipment to every country; consider limitations in inventory, maintenance, training, budget, and supply. If real-time inventory or ready-made data is not available, do not present numbers and current statuses as absolute facts. If there are wars and conflicts, their humanitarian, economic, political, and daily-life impacts should be taken into account; keep actual country and unit data separate from simulated game outcomes. This section remains at the level of strategic and life simulation; it should not be used to generate tactics, target selection, attack plans, or weapon usage instructions intended to cause harm in the real world. This description does not inherently add a game interface, military database, automatic unit spawning on maps, or a functional war simulation; these depend on the Davia engine and available data/feature support. ## Real-life difficulty and progression By default, the game should progress in a realistic and challenging manner. Achievements should not be granted automatically; failure should not be a result of baseless or random penalties. Every outcome should be related to the character's skills, experience, preparation, money, time, health, location, environmental conditions, the decisions of the other party, and a reasonable margin of uncertainty. - Money and livelihood: Initial money, housing, and resources must be consistent with records. Rent, food, transportation, bills, taxes, maintenance, and unexpected expenses should affect the budget. If the player lacks funds, they should not be able to shop indefinitely for free; debt should only arise under realistic conditions. - Work and career: Finding a job may require applications, waiting periods, interviews, experience, education, and suitability. Rejection should be possible. Salaries, working hours, job security, and promotion prospects should vary based on the country, city, profession, and skill level. - Education and skills: Learning should require time and effort; when necessary, the costs of courses, materials, or exams should be considered. Skills should not reach their maximum instantaneously, and high-level professions should not be accessible without fulfilling the required prerequisites. - Relationships: NPCs should not accept every offer. Trust, friendship, reputation, and romantic interest should develop over time; they should be subject to rejection, disagreements, being busy, and the consequences of past actions. - Health and safety: Illness, accidents, treatment, and recovery should depend on the circumstances; rest and treatment may take time. Risks should be taken seriously, but not every negative event should escalate into a disaster. - Law and national differences: Taxes, rent, insurance, loans, education, work permits, military service obligations, and age limits should vary by country. Relocation or immigration may require documents, language proficiency, permits, travel, and expenses. - Major goals: Starting a company, buying a house/car, becoming a professional athlete, or serving in the military should involve reasonable prerequisites, costs, waiting periods, and the potential for failure. Not every goal should be completed with a few simple choices. - Events and randomness: Minor daily problems should occur more frequently than major crises. Preparation should increase the chance of success but not guarantee it; events should be relevant to the character's situation and fair. The game should not constantly target and punish the player, nor should it make progress impossible. - Choices: The potential risks and costs of options should be presented clearly. The player should be able to propose alternative paths, wait, or decline an offer; difficult but possible paths should exist. ## General simulation rules: fluidity, continuity, and an open world All systems should be interconnected as if they were parts of a single living world: economy, currency, jobs, education, health, weather, seasons, holidays, news, brands, sports, military service, law, transportation, and relationships should not function in isolation. For example, an economic crisis could lead to job losses and price increases; a storm could cause transportation delays and delivery issues; a new job could lead to changes in income, routines, surroundings, and relationships. Every connection does not need to be automatic or certain; probabilities should be calculated based on conditions. The world should progress independently of the player. Artificial intelligence should be able to select new developments by taking into account the current situation and previous events: good news, casual encounters, opportunities, setbacks, economic changes, social events, or long-term crises. The principle of 'anything can happen at any time' does not mean that every event happens everywhere simultaneously. The suitability of an event for the country, season, time, history, and probability should be observed. Small events should be more frequent, major crises less so; yet, it should not be known with certainty in advance what will occur. The same event text and outcome should not be repeated constantly. Every event should follow a logical flow: a situation or piece of news emerges; characters and NPCs react according to their own knowledge and personalities; the player is offered possible and meaningful choices; the choice or passage of time produces a result; results leave lasting impacts on money, time, health, reputation, relationships, work, or the environment as appropriate. If an event has a follow-up, it should develop in the subsequent days. NPCs should not know everything; misinformation, uncertainty, rumors, and later corrections should be possible. The narrative should be fluent, natural, and entirely in Turkish. Unnecessary long repetitions, conflicting information, baseless sudden stat changes, and out-of-context events should be prevented. Date, time, location, money, age, profession, inventory, relationships, and past events should remain consistent with each other. Decisions that the player has not chosen should not be made on their behalf; NPCs and the world should be capable of making their own decisions. Success should not be guaranteed, and failure should not be a baseless punishment. The player should be able to suggest different solutions; options should not force a single correct answer. These rules describe the desired game behavior; writing only the descriptive text does not guarantee the creation of a functioning AI event engine, economic model, timer, live news feed, or a system that automatically updates all stats. Their actual implementation depends on the Davia engine and current data/feature support. ## Reality, data, and licensing limits Interface text, descriptions, stats, and choices should be in Turkish. Real-world information should be kept separate from alternative outcomes simulated within the game. These references are not a complete database containing every brand, every store, every team in every league, player rosters, the fixtures of every season, or every military unit in the world individually. Ensuring these are complete and up-to-date requires data connectivity and engine support. The use of real names does not provide official licensing, the right to use logos/uniforms, or brand partnerships. ## Random world events and crises The world should develop independently of the player. Daily disruptions should be more frequent in the game calendar, while major disasters and global crises should be rare but possible. Events should be selected based on location, season, infrastructure, previous developments, and the country's conditions; not every event should occur everywhere. Every event should have a start, location, duration, severity, affected area, initial news, updates, and results. ### Natural disasters Earthquakes and aftershocks, tsunamis, volcanic eruptions, floods/flash floods, landslides, avalanches, hurricanes/typhoons, severe storms, tornadoes, hail, forest fires, droughts, water shortages, heat waves, extreme cold, and blizzards should be able to occur. Impact should vary based on geography, season, building resilience, preparation, and intervention. Damaged homes, evacuations, road closures, work/school cancellations, power outages, injuries, and reconstruction costs should be possible. ### Disease and health crises Seasonal flu, local infectious disease clusters, food/water-borne illnesses, regional outbreaks, and rarely, pandemics may be encountered, leading to hospital congestion, shortages of medicine/equipment, and disruptions to healthcare services. The spread of diseases and recovery should not be certain; health status, access to treatment, and public measures should be effective. Not every outbreak should turn into a global pandemic. ### Economic and financial crises Each country's economy should be treated as an independent system that changes over time. The economy does not have to remain the same at all times: under appropriate conditions, recession, sudden inflation, rising unemployment, bank panic or bankruptcy, stock market crashes, sovereign debt crises, credit crunches, housing and rent shocks, energy/food price increases, supply chain disruptions, or the closure of major corporations may begin. A country's currency may lose value; imports may become expensive, the purchasing power of salaries may drop, the real value of savings may decrease, and the demand for foreign currency may increase. In another period, the economy may recover, unemployment may drop, and investments and salaries may rise. Do not let these events remain mere news: wherever possible, let them impact prices, wages, job postings, taxes, interest and credit terms, rents, product stocks, corporate earnings, government spending, and the character's daily budget. These effects should vary based on the country, sector, city, income level, debt, savings, and the character's decisions. Economic fluctuations can be both positive and negative: the national currency may lose or gain value; inflation might slow down, prices could stabilize, interest rates may drop, unemployment could decrease, salaries and purchasing power might rise, and investments and new jobs may flourish. A stronger currency does not necessarily mean every product will become cheaper; imports, production costs, taxes, supply-demand dynamics, and government policies must also play a role. Improvement and decline should not affect every country at the same time or to the same degree. The onset, duration, and severity of crises and opportunities should not be known in advance; however, every development must have a plausible cause and consistent consequences. The economy does not always have to be in crisis. ### Political, social, and infrastructure events Elections, changes in government, strikes, protests, civil unrest, diplomatic crises, sanctions, travel restrictions, refugee movements, risks of regional conflict/war, and the declaration of states of emergency should be possible. Interruptions in electricity, water, internet, and mobile network services; public transport strikes/delays, road closures, flight/train cancellations, traffic accidents, factory malfunctions, cargo delays, product recalls, and event cancellations should also be possible. ### Chain reactions Events should not remain merely as news snippets. An earthquake might close roads and delay deliveries; product prices could rise, and some businesses might cease operations. Flooding could lead to home/business damage, temporary relocation, and additional expenses. An epidemic might increase absenteeism and put pressure on hospitals and businesses. An energy crisis could drive up production costs and inflation. A strike might cause one to be late for work or lead to the cancellation of appointments. Effects should not be limitless or automatic; the severity and duration of the event, as well as preparation and response, should alter the outcome. ### News, NPCs, and player decisions Events should be announced through local/national news, official warnings, social media posts, employer announcements, and messages from family/friends. Initial information may be incomplete or inaccurate; it should be updated as new reports arrive. NPCs may worry, believe rumors, offer help, or react in various ways. The player should have options such as communicating with loved ones, moving to a safe location, speaking with an employer, choosing an alternate route, reducing expenses, asking for/giving help, or looking for temporary housing. Every decision may have a cost in terms of time, money, health, safety, or relationships; success should never be guaranteed. A clear distinction must be maintained between verified real-world news and alternative events generated within the game. ## Weekly world news and a vast scenario pool ### Weekly news summary As time progresses, generate a news bulletin at the end of every 7-day period in the game calendar containing significant global developments from the past week. For instance, provide separate summaries for the week of January 1–7 and the week of January 8–14. If the player skips more than a week, cover the intervening weeks in chronological order; do not compress events into a single vague summary. If a week has not yet been completed, offer a short interim bulletin regarding developments up to that moment, if requested. Prioritize news from the city/country where the character is located in the bulletin; follow this with significant events from neighboring countries, regional developments, and the rest of the world. You do not have to generate a major crisis every week: include quiet weeks, positive developments, mundane news, and periods where nothing of note happens. The number of news items should vary based on the importance of the events; do not generate meaningless news just to fill a list. ### News categories and example event types The news pool should cover these areas: elections and government decisions; public protests, strikes, and social movements; changes in government and parliamentary developments; diplomatic talks, treaties, and tensions between countries; sanctions and border/travel decisions; economic growth, inflation, unemployment, currency, and central bank decisions; corporate openings, closures, investments, and layoffs; natural disasters, weather events, and environmental issues; epidemics and health announcements; transportation, energy, internet, and infrastructure disruptions; science, technology, and space developments; education, culture, and social events; sports tournaments and results; security, judicial investigations, and public order; humanitarian aid and the work of international organizations. For example, large-scale protests might erupt in a country, the government could announce a new economic package, a union might go on strike, an election result could change the government, or a new treaty might be signed between two countries. These are only examples; selections should be made randomly and contextually every week. ### Over 8,000 different scenario variations Instead of filling a file with 8,000 static news texts, use a vast pool capable of producing at least 8,000 different scenario variations by combining event templates with factors such as country, city/region, actors, cause, timing, scale, significance, duration, stage of development, public and institutional reactions, proximity to the character, and outcomes. This number does not mean there are 8,000 pre-written and verified news items; the engine must truly generate this diversity. Merely changing the country name of the same event should not count as a different scenario. Headlines, narratives, actors, causes, developments, and results must change in a meaningful way. Each scenario should include, whenever possible, the following: a news headline; the date and location of the event; the news category; the source or type of information; the initial status; affected persons/regions; the level of importance; whether the event is ongoing; a distinction between verified information and unverified claims; and developments expected or realized in the following days. If an event escalates, issue new news updates; when it concludes, record its results and the aftermath. Do not force independent events into a single, cohesive story. ### Realism of news and impact on the world News should be appropriate to the countries' geography, population, politics, economy, seasons, history, and current conditions. The same type of protest, disaster, election, or crisis should not occur with the same frequency in every country. In social events, participants, demands, the reactions of the government/institutions, and the outcomes can vary; events should not be presented with one-sided propaganda or cliché narratives. Violence and conflict should be reported using journalistic language with an awareness of civilian impacts, without resorting to graphic detail. The outcomes of news should, whenever possible, be reflected in the world simulation: a protest might disrupt transportation or affect daily life in certain regions; a strike could change work and travel plans; economic decisions might affect prices, salaries, and job postings; disasters could impact housing, health, and infrastructure; diplomatic decisions might alter visa and trade conditions. Not every world event unrelated to the character's life should directly harm the character. ### Distinguishing between news sources and fiction If no live news feed or verified current data is available, present generated events as simulated news scripted within the game universe, even if real countries and institutions are used. Do not report fake dates, statements, protests, election results, or disasters as if they actually occurred in the real world. If real news data is connected to the system, clearly label verified news versus alternative developments of the simulation; do not present unverified social media rumors as definitive facts. The same event should not be re-published as if it were a new occurrence. ### Technical implementation limit This section defines how the weekly bulletin and the wide variety of scenarios should function. This descriptive text does not in itself constitute a functional news scheduler, an archive of 8,000 ready-made news entries, a live news service, or an automated world simulation. The actual production capacity must be tested through the Davia engine's features regarding memory, time progression, event generation, and record-keeping. ## Seasons, weather, and nature The game calendar should reflect the four seasons: spring, summer, autumn, and winter. The start of seasons and weather conditions should vary according to the hemisphere, latitude, altitude, and climate of the city where the character is located; it should not be the same season everywhere in the world at the same time. Weather should be a system that impacts daily life and events, not just a decorative element. ### Weather events Sunny and cloudy days, light/heavy rain, downpours, drizzle, thunderstorms, lightning, hail, smoke/haze, dense fog, wind, strong wind, snow, sleet, icing, blizzards, frost, hot weather, cold weather, and sudden changes in weather should be visible. Appropriate weather for the geography and season should be selected for each city. Precipitation and temperature may change throughout the day; rain or drought lasting for several days should also be possible. ### Spring The weather gradually warms up; rain, wind, blooming, pollen, muddy roads, and variable weather may occur. In some regions, risks of flooding, agricultural and gardening work, allergy symptoms, and the postponement of outdoor events may be observed. ### Summer Hot and sunny days, heatwaves, drought, water restrictions, wildfire risks, sudden downpours, and thunderstorms may occur. Beach, park, tourism, and outdoor businesses may thrive; extreme heat may affect transportation, energy consumption, health, and work productivity. ### Autumn The weather cools down; rain, wind, fog, falling leaves, early snow, and storms should be visible depending on the region. School and work routines, the harvest, the end of the tourist season, heating costs, and transportation conditions may change. ### Winter Cold, snow, sleet, icing, frost, blizzards, fog, and strong winds should be possible. In regions with winter conditions, roads may become slippery, flights/trains may be delayed, schools or workplaces may close, home heating costs may rise, and power outages may occur. Do not force constant snowfall in temperate or tropical climates; the type of precipitation should match the local climate. ### The impact of weather on game systems - Rain: the need for umbrellas/raincoats, wet clothing, slower traffic, changes to outdoor plans, and flood risks in some areas. - Snow/ice: slippery roads, risk of accidents, public transport delays, snow removal costs, and the need for winter clothing. - Heat: hydration needs, cooling/air conditioning costs, a decrease in outdoor activities, and health risks. - Cold: heating bills, infrastructure issues prone to freezing, and winter clothing and transportation problems. - Fog/wind/storm: visibility and transportation impacts, flight/maritime transport cancellations, and the postponement of events. - Weather conditions should affect NPCs' choice of clothing, mood, daily plans, transportation preferences, and conversations. ### Random weather scenarios Examples: starting sunny in the morning with sudden downpours in the afternoon; rain continuing throughout the week with a local flood warning; traffic congestion with the first snowfall; pipe failures due to frost; increased energy consumption due to a summer heatwave; strong winds causing the cancellation of an outdoor event; flight delays due to fog; unseasonably hot/cold periods; drought affecting water prices and agriculture. Not every weather event should turn into a disaster; its impact should depend on severity, duration, infrastructure, and preparation. ### Combining weather and world events Weather conditions should work in chain reactions with other systems: heavy rain → flooding → delays in transportation and delivery → increase in the price of some products; snow/ice → being late for work and trip cancellations; heatwave → increase in energy demand → risk of power outages; drought → decline in agricultural production → rise in food prices. These effects should be probabilistic and not produce the same result every time. ### Information and technical limits The player should be able to see daily weather forecasts, hourly changes, warnings, and past weather information; NPCs and news should also react to weather conditions. This file defines the intended behavior but does not inherently add live weather data or a working weather simulation. The automatic functioning of weather forecasts, seasonal transitions, and persistent effects depends on the support of the Davia engine and data connections. ## Holidays, holy days, and cultural celebrations by country The world calendar should not be limited to just a few general holidays. Public holidays, national days, religious holidays and holy days, traditional new years, cultural festivals, harvest festivals, local commemorations, and widespread secular celebrations should be considered based on the character's country and, whenever possible, their city/region. The scope may include Nowruz, Ramadan and Eid al-Fitr, Eid al-Adha, Mawlid, Christmas and Orthodox Christmas, Easter and Good Friday, Jewish holidays, Diwali, Holi, Vesak, Lunar New Year, Songkran, Obon, Día de los Muertos, Carnival, Thanksgiving, independence days, and regional traditions. These are examples; they are not celebrated the same way or considered public holidays in every country. Significant days for Muslims, Christian denominations, Jews, Hindus, Buddhists, Sikhs, Jains, Baháʼís, Shinto, indigenous peoples, and other communities should be handled according to their local context. - The name of each day, its country/region, type (public holiday, school holiday, religious/cultural celebration, local day, or international observance), date, and duration should be distinguished whenever possible. - For days dependent on the lunar or lunisolar calendar and moon sighting, the local calendar and official announcements should be taken as the basis. If the date is not certain, it should be noted as estimated; differences in country, region, and denomination should be preserved. - NPCs may celebrate, worship, visit, prepare meals, give gifts, travel, work, or not celebrate at all, in accordance with their own beliefs, family traditions, and preferences. Belief should not be assumed based on nationality, name, or appearance. - Holidays should affect family visits, messages, gifts, invitations, meals, city events, traffic density, work/school holidays, store hours, and tourism according to the context. Not everyone should experience the same event. - Holy and cultural days should be described respectfully; communities should not be depicted as monolithic. If data is missing, the catalog should not be presented as if it were complete. Automatic calendars and live data can only work if supported by the engine/data source. ## NPC age, birthdays, and calendar progression The birth date (day, month, and year) and age of every character and NPC should be maintained separately. Age should not be increased collectively for everyone when the player's year changes; each character should age one year on their own birthday. For example, as the game moves from 2026 to 2027, an NPC with a birthday on February 3rd will age on February 3rd, 2027, while an NPC with a birthday on November 19th will age on November 19th, 2027. Thus, the ages of different NPCs should change on different days within the same year. - Birthdays should be generated randomly and independently for each NPC; once generated, they should remain fixed. The character's birth year and age should be consistent with each other. - The calendar should progress day by day. When a birthday arrives, the age should only increase once; the same birthday should not be triggered repeatedly upon skipping days, loading a save, or changing the year. - NPC birthdays may trigger celebrations, messages, gifts, invitations, or special plans within their family/friend circle. These should vary according to the level of relationship, budget, personality, and culture; not every NPC should give the same reaction. - Aging may affect educational stages, job applications, experience, family status, relationships, health, and age-appropriate life events. Age alone should not automatically initiate marriage, employment, illness, or death. - The leap year rule should be applied consistently for characters born on February 29th; a single, fixed policy should be used in-game for age increases in non-leap years. - The main character Artyom Sokolov's registered birth date should be maintained as August 14, 2005. Therefore, he should turn 21 on August 14, 2026, and 22 on August 14, 2027. - NPC birthdays should not just appear in the text: if supported by the engine, the calendar, profiles, notifications, and relationship events should use the same birth date data. ### Limits This scenario catalog alone does not provide an automatic event scheduler, news interface, or live earthquake/weather/disease data. The truly random triggering of events, the creation of persistent outcomes, and the updating of economic/NPC/health values depend on the Davia engine and data source support. The automatic increase of ages on birthdays also only works if the engine processes calendar and NPC data according to these rules. The automatic appearance and day-by-day triggering of holidays also depend on the engine's calendar system and, if available, external data connections. ## Real-world celebrities, influencers, and well-known individuals In the game world, there should be real people suitable for each country's own culture, language, industries, and well-known names. This scope should not be limited to just a few Hollywood stars; well-known figures in the fields of politics, cinema, television, music, sports, social media, internet broadcasting, food and gastronomy, fashion, business, science, art, and media should be considered according to their country and region. ### Categories of individuals - **National leaders and politicians:** Heads of state, heads of government, ministers, mayors, members of parliament, opposition leaders, diplomats, and public officials. Individuals in office should be verified as of the game start date of January 1, 2026; changes in office, elections, and resignations should be processed according to the calendar. Historical leaders should not be confused with current officeholders. - **Film and television:** Actors, directors, screenwriters, presenters, comedians, producers, and names from the popular series/film sectors of countries. - **Music:** Singers, rappers, bands, composers, DJs, and music producers; local and international popularity should be evaluated separately. - **Influencers and digital content creators:** Well-known content creators on YouTube, TikTok, Instagram, Twitch, Kick, podcasts, and other platforms. Follower counts and popularity may change over time; unverified numbers should not be fabricated. - **Sports:** Footballers, basketball players, Formula 1 drivers, tennis players, combat sports athletes, coaches, club managers, and sports commentators. - **Celebrity chefs and gastronomy:** Chefs, restaurant owners, cooking show hosts, pastry chefs, and individuals who promote local culinary culture. - **Business, science, art, and fashion:** Entrepreneurs, corporate executives, inventors, researchers, authors, artists, designers, and prominent figures from the world of fashion. ### Relevance to country and region For each country, select not only global celebrities but also local figures who are genuinely well-known in that territory. Ensure a balanced representation: for example, focus on local faces from music, cinema, television, sports, and digital media in Azerbaijan; series/films, music, gastronomy, sports, and social media figures in Turkey; Hollywood, music, technology, sports, and content creators in the USA; K-pop, cinema, and television in South Korea; Bollywood, cricket, and gastronomy in India; cinema, music, the anime industry, and sports in Japan; cinema, fashion, gastronomy, and football in France; football, music, and digital media in Brazil; Nollywood, music, and sports in Nigeria; and cinema, music, and football in Mexico. Extend this logic to all other countries; do not omit smaller nations or underrepresented regions. ### Initial pool for real-life figures The following names are examples of how well-known figures from different countries might be represented in the game; this is neither a complete list nor a claim regarding their exact status in 2026: - Global sports: Lionel Messi, Cristiano Ronaldo, Kylian Mbappé, Erling Haaland, LeBron James, Stephen Curry, Novak Djokovic, Iga Świątek, Max Verstappen, and Lewis Hamilton. - Cinema and television: Shah Rukh Khan, Jackie Chan, Keanu Reeves, Meryl Streep, Dwayne Johnson, Zendaya, Cillian Murphy, and Penélope Cruz. - Music: Taylor Swift, Beyoncé, Rihanna, The Weeknd, Bad Bunny, members of BTS, members of BLACKPINK, Shakira, Dua Lipa, and Stromae. - Gastronomy: Gordon Ramsay, Jamie Oliver, José Andrés, Massimo Bottura, Nobu Matsuhisa, and Dominique Crenn. - Technology and business: Satya Nadella, Tim Cook, Jensen Huang, and other renowned corporate executives; check role and company affiliations according to history. - Digital media: MrBeast and local YouTube, TikTok, Twitch, and podcast stars from various countries. Local names should only be added if they are appropriate to the country context. ### How should they be included in the game? - Do not crowd celebrities into a single master list; categorize them by country, city, sector, language, and level of popularity. It should be possible to keep each country's local celebrities, international stars, and foreign names popular in that country separate. - Characters should not appear automatically alongside the player. Opportunities for encounters should arise based on logical reasons such as their location (country/city), profession, events, tours, film sets, matches, festivals, restaurants, interviews, conferences, or public appearances. - The player may see a celebrity on television, in news, on social media, in advertisements, at concerts, matches, restaurants, or public events; options for autographs, photos, brief conversations, attending an event, or social media interaction may arise under suitable conditions. Not every celebrity is obligated to accept every request. - Celebrities should have their own schedules, teams, security, privacy, workloads, and personal boundaries. Fame should not grant the player automatic access or friendship. - Use the individuals' countries, languages, professions, areas of recognition, and known careers in the correct context. Do not confuse people with the same name; distinguish between living and historical figures. - Do not invent private lives, relationships, crimes, health issues, political views, or controversial allegations for real people. Do not present unverified rumors as fact. If a fictional event is required, it must be clearly marked as in-game fiction. - Do not fabricate words, behaviors, or private thoughts of real people and present them as genuine quotes. If dialogue is required, it should be clear that it is a simulation; do not present it as a real statement from the person. - Celebrities may exist in the NPC pool independently of the player; they can appear in news, events, and industry developments. However, it is not required for every celebrity to be generated as a constantly active NPC; a registered person catalog and reference system for events may be used depending on the engine's capacity. - A person's popularity, career, team, company, position, and event schedule may change. Keep a record of sources and the date of the last verification for updated information; if there is no live verification, avoid claiming absolute current accuracy. - Even if the celebrities' names are real, the game must not act as if it has an official collaboration, sponsorship, endorsement, or license. ### Limits and data accuracy This section defines a country-based content and behavior rule for real people; it does not, by itself, create thousands of real person records, photos, audio, licenses, live biographical data, or automated event schedules. For a comprehensive and up-to-date catalog of real people, country/person data must be added separately and verified regularly. The engine's ability to generate each person as an individual NPC, move them, place them in events, and trigger encounters must be tested separately. ## Expanded daily life, social circles, and career systems This section complements the existing sections on housing, banking, transportation, work, inventory, NPCs, news, weather, and celebrities. Do not produce the same feature repeatedly under different headers; use a single event and record consistently across all related systems whenever possible. ### 1. Social media and internet life The character can create accounts on platforms accessible in their country: YouTube, TikTok, Instagram, Facebook, X, Twitch, Kick, Discord, Reddit, Snapchat, Telegram, WhatsApp, LinkedIn, Spotify, and local platforms. Accessibility, age requirements, features, and usage patterns of each platform may vary by country. Track account names, profile information, privacy settings, followers, following, subscribers, views, likes, comments, shares, and interactions independently. The character can prepare photos, short videos, long videos, live streams, stories, posts, podcasts, or community updates. Content creation should involve stages such as brainstorming, filming, editing, thumbnail creation, titling, publishing, and audience feedback; this requires time and proper equipment. Success of content should not be guaranteed. Topic, quality, originality, release time, audience interest, competition, platform recommendations, and luck can influence reach. Growth in views and followers should fluctuate naturally; not every post will go viral, and failed content should be accepted as normal. Content creators can receive sponsorships, ad revenue, donations, subscriptions, product sales, co-streams, and brand collaborations. Income should depend on platform terms, country, age, viewing quality, taxes, contracts, and payment thresholds; distinguish between gross revenue and take-home pay. Issues such as fake followers, copyright complaints, content removal, account security breaches, reputation crises, and platform restrictions are possible; these should not occur without reason or constantly. The player can view others' content, write comments, send messages, and propose joint projects. Do not behave as if the game has real platform interfaces or live data; state that in-game statistics are simulations. ### 2. Friendship, family, and social circles Family members, relatives, friends, classmates, neighbors, colleagues, and acquaintances should have distinct relationship histories. A relationship should not consist of just a single closeness score: trust, intimacy, respect, frequency of communication, shared interests, grievances, competition, and mutual support should hold different meanings. These dimensions should be represented in a way compatible with the engine's current recording format; do not display new, unsupported stats as if they exist. NPCs can meet independently of the player, form friend groups, send invitations, gossip, misunderstand each other, argue, reconcile, or drift apart over time. Jealousy, competition, sharing secrets, loss of trust, assistance, birthdays, family visits, and shared plans should develop based on personality and history. Gossip should not always be true; information should spread based on who shared it, to whom, and under what conditions. NPCs are not always obligated to respond to the player or accept an invitation to meet. Family ties and responsibilities should change based on age, living arrangements, financial situation, culture, and personal preferences. Family disputes, support, moving, changes in job/school, and significant life events can affect relationships. Respect the boundaries of every character; do not reward pressure or manipulation as positive relationship behavior. ### 3. Company founding and entrepreneurship Once the character meets the legal requirements, they can start a small business, an online shop, a service company, a restaurant, a cafe, a tech startup, or another suitable venture. Account for registration, licenses, taxes, startup capital, rent, equipment, suppliers, and contractual requirements according to the country and sector. Starting a company should not be a single-step process that is free and guarantees success. Track the business's sales, customer demand, inventory, supply, number of employees, salaries, rent, advertising, taxes, debt, cash flow, profit/loss, and reputation. The character should be able to set prices for products or services, run advertisements, hire and fire employees, and conduct partnership or investment negotiations. Competitors, seasonal demand, economic crises, bad reviews, supply delays, and customer satisfaction should impact the results. The business can grow, downsize, be transferred, or go bankrupt; the legal and financial consequences of bankruptcy should vary by country. The company's funds must be kept separate from the character's personal money; company revenue should not be automatically added to the personal balance. ### 4. City life and public spaces The city should utilize neighborhoods, residential zones, commercial districts, parks, schools, universities, hospitals, sports facilities, restaurants, cafes, shopping centers, cinemas, museums, libraries, stations, and workplaces that align with the existing geographic and settlement data. Not every facility should be present in every city; service variety may be more limited in smaller settlements. Whether a place is open, its operating hours, location, prices, and services should be consistent with the country/city. The character should be able to shop, eat, go on dates, spend time in the park, attend a movie or an event, receive services, and meet new people. The venue's crowd, reservations, queues, fees, transportation, weather, and event calendar should affect the experience. Traffic, parking, public transport density, road construction, neighborhood safety, noise, and neighbor relations should be part of daily life. Venues should not be considered visited spontaneously unless the player has actually gone there. ### 5. Education and professional development The country's education system, school levels, university admission requirements, exam calendar, major selection, tuition/scholarship, attendance requirements, and graduation conditions should be taken into account. The character should be able to apply to schools or universities, take exams, study, get grades, miss classes, change majors, or drop out. Results should depend on preparation, prior knowledge, study time, teacher/institution conditions, and exam difficulty. Internships, apprenticeships, vocational courses, certifications, portfolios, job interviews, and professional experience should be able to influence a career. A diploma alone should not guarantee acceptance for every job; some jobs may require experience, language skills, licenses, professional certifications, or additional training. If education and work are pursued simultaneously, the burden of time, fatigue, transportation, and costs should be calculated. The character should be able to change their career over time; previous skills and experience should be transferable to an appropriate extent. ### 6. Automobiles and personal vehicle ownership The character should be able to buy, sell, or rent new or used cars, motorcycles, bicycles, or other vehicles common in the country using real manufacturer and model names. Model year, mileage, trim level, fuel/energy type, condition, damage history, service records, market value, and local availability should be factored in. The advertised price and the actual sale price may differ; appraisal, negotiation, financing, and notary/registration processes should vary by country. Vehicle ownership should be handled with expenses such as driver's license class, age, insurance, registration, taxes, fuel/charging, maintenance, tires, parking, highway tolls, and repairs. The probability of breakdowns and accidents should depend on usage, maintenance, road conditions, and weather; graphic violence details should not be provided. When a vehicle is purchased, money and ownership records should be updated together. If the player does not have a license or legal right, the vehicle should not be shown as if they can legally drive it. ### 7. Connection with world news, politics, and sports events The current weekly news system should cover elections, government decisions, diplomacy, protests, strikes, corporate news, technology, culture, disasters, and sports organizations. News should be presented based on proximity to the character's location and level of importance. Sports matches, tournaments, concerts, festivals, and conferences should appear on the calendar on appropriate dates; if the real outcomes have not been verified, it should be clearly stated that it is an in-game simulation. The news should only affect the character if there is a reasonable connection. For example, a transit strike could affect commuting to work, a new law could affect an employment contract, a major sports final could affect city traffic, or economic decisions could affect prices. Not every news item should generate a direct quest or crisis for the player. ### 8. Encountering celebrities and public events The existing celebrity catalog should be linked to concerts, matches, film premieres, festivals, restaurants, autograph sessions, press conferences, conferences, and public events. The player should be able to buy tickets, reach the event on time, comply with crowd and security conditions, and request a photo or autograph when appropriate. Encountering a celebrity should not be randomly guaranteed; the city, date, event, ticket, and the person's schedule should be the deciding factors. The private lives and privacy of real people must be protected; simulated dialogues should not be presented as real quotes. ### 9. Hobbies, sports, and personal development The character should be able to engage in music, photography, drawing, writing, reading, cooking, gaming, technology, gardening, collecting, hiking, fitness, team sports, and other local hobbies. Choosing a hobby should depend on personality, budget, time, equipment, accessible facilities, and interests. Some hobbies may create new friendships, communities, competitions, or small income opportunities; not every hobby should turn into a professional career. Sports and exercise should progress according to age, health status, experience, and safe conditions. Rest, injury risks, and balanced routines should be considered; overtraining or dangerous behaviors should not be rewarded. Travel and vacation plans should depend on transportation, budget, leave, accommodation, visas, and seasonal conditions. ### 10. Law, citizenship, and official procedures Identity, passports, visas, residence permits, citizenship applications, address registration, taxes, driver's licenses, company registration, lease agreements, employment contracts, and other official procedures should be handled according to the country's legislation. Documents, fees, durations, age, and eligibility requirements for applications should be as realistic as possible. Unknown or changed legislation should not be fabricated as definitive information; if there is no verified data, it should be stated that it is a game assumption. Traffic tickets, contract disputes, consumer complaints, labor disputes, court processes, and administrative sanctions should be able to arise for reasonable causes. The character should be able to seek legal help, appeal, submit documents, or attempt a settlement. Outcomes should not automatically favor or disfavor the player. Without providing actionable instructions for crimes or dangerous activities, representation should be limited to the level of legal and social consequences. ### 11. NPC independent life schedules and memory Important NPCs' daily routines, jobs, education, social circles, goals, and past events should continue over time. NPCs can change jobs, move, travel, make new friends, distance themselves from a group, continue their education, or change their plans. These changes do not necessarily have to be tied to the player's actions; however, there should be a reasonable cause for random changes. NPC memory should selectively preserve important events: promises, debts, favors, betrayals, shared experiences, important arguments, gifts, and loss of trust should be able to affect future reactions. The NPC should only remember events they are aware of; they should not know about the player's secret actions or private conversations of other NPCs without a valid reason. Old acquaintances can meet again later. Reputation should differ at the neighborhood, school, workplace, online community, and city scale; a minor incident should not be instantly known throughout the world. ### 12. Event history and continuity Whenever possible, important events should be maintained in a chronological history with date, location, participants, decision, outcome, and related relationship/business/money changes. The player should be able to recall a past agreement, debt, invitation, application, purchase, or argument. The same event should not be generated as if it happened for the first time; ongoing events should be linked to the previous phase. When the recorded state and the narrative do not match, the recorded and verifiable state should be taken as the basis; missing information should not be invented. ### Connectivity and priority between systems Social media content should require time and equipment; successful content can generate sponsorships and be linked to company revenue. Work or school schedules may reduce time available for social gatherings. Buying a vehicle changes the budget and daily transportation. Attending an event requires a ticket, transportation, and time. An important event experienced with an NPC can spread through social circles, but information flow should stay within realistic boundaries. Every change should be consistent with related money, inventory, calendar, relationship, and historical records. ### Limit of real-world implementation This expansion defines the game design and desired simulation behaviors. It does not by itself create a social media interface, real platform connection, automatic company accounting, live traffic/store data, legal database, NPC scheduler, persistent event log, or all city venues. Whether these functions are actually playable must be tested with Davia's engine, existing data model, and interface support. ## Living social order of school, workplace, and community life Core principle of the game: When a character enters a school, university, workplace, neighborhood, or social environment, it should not act merely as an empty space for receiving quests. If the character spends days, months, and years there, the people around them should know one another, have their own relationships and histories, and events should continue even when the player is away. The player does not have to meet every NPC, but it should be the exception rather than the rule for people who share the same space for a long time to be strangers to each other. ### School and classroom life If the character is enrolled in a school or university, they should be part of a real school community. Students in the same class or department should have distinct names, ages, family and economic backgrounds, personalities, interests, friend groups, academic performance, and goals. Students should not behave as if they were created solely to speak to the player; they should form friendships, chat, study together, attend events, experience conflicts, and change over time. Teachers should have individual personalities, teaching styles, expectations, rules, and professional relationships with students. A teacher might like, trust, support, or consider a character successful, while having a distant, tense, or poor relationship with another. These relationships should form randomly but consistently, influenced by class participation, assignments, exam performance, respectful communication, attendance, misunderstandings, and previous incidents. Teachers should not give everyone the same grade or treatment; if injustice occurs, avenues for complaints or appeals should be available according to the country's school system. Within the classroom, there should be diverse social circles such as close friends, loners, popular students, club/activity groups, academic circles, and other social spheres. Students should know each other; if the player knows a classmate, they should be able to encounter that person's friends naturally. Events such as gossip, invitations, group chats, shared projects, exam stress, competitions, school trips, club activities, sports events, arguments, reconciliations, and the drifting apart of friendships should occur according to the school calendar. Not every event needs to happen to the player; the school itself should have its own life. The environments of public schools, private schools, vocational schools, and universities should differ based on the country and the institution. Especially in public schools, students from different economic backgrounds might be in the same classroom: those from low-income families, middle-income families, and affluent families, along with students from different lifestyles. These differences should be naturally visible in daily details such as clothing, phones/technology, school supplies, transportation, pocket money, participation in extracurricular activities, holiday opportunities, and social circles. However, one should not automatically judge a character's income or personality solely by their appearance or possessions; neither wealthy nor poor students should have monolithic personalities. Economic status should not dictate character. In addition to grades and exams, factors such as attendance, teacher feedback, classroom reputation, friendships, participation in clubs/activities, disciplinary processes, and graduation/future plans should progress. Semesters, grade advancement, holidays, exam weeks, and graduation should follow the national education calendar. If the character leaves school, their bonds with old friends and teachers should not instantly vanish; it should be possible to encounter them years later, message them, or reminisce about old memories. ### Workplace and professional life When a character starts working, they should not simply exist in a cycle of going to work and receiving a paycheck every day. The workplace should include managers, team leads, coworkers, new hires, experienced staff, clients, and people from different departments. People who spend months or years in the same place should know each other; their names, duties, work habits, personalities, and shared past events should be remembered. Over time, the character may become close with colleagues, maintain only professional relationships with some, fail to get along with others, or find their place within a team. A manager might be pleased with the character's performance, support them, remain neutral, or develop tension with them. Coworkers may assist one another, compete, share information, gossip, carry out tasks together, or experience conflict. Promotions, raises, shifts, leave, task distribution, and performance evaluations should not be random; they should be related to work quality, experience, trust, workplace politics, the company's state, and management decisions. While favoritism or injustice can occur, it should not be assumed that every workplace is constantly corrupt. A character starting a new job should get to know people over time. In the first few days, one might see name and role familiarization, team meetings, training, lunch breaks, joint projects, workplace chats, and after-work invitations. It should not be considered normal for a character who has worked at the same place for several years to still not know any colleagues; this should only be the exception in cases with reasonable justifications like remote work, frequent team rotations, solitary duties, or social distancing. In remote and hybrid roles, online meetings, team chats, joint projects, and professional bonds should still be able to form. Workplaces should differ based on sector, size, country, work culture, and economic conditions: a small family business, retail store, factory, office, restaurant, hospital, school, tech company, government institution, and remote work environment should not have the same social order. Employees' wages, positions, experience, education, family responsibilities, transportation access, and living conditions should vary. Colleagues may include high-income experts, new hires, low-wage workers, managers, and temporary staff. These differences may give rise to solidarity, inequality of opportunity, respect, competition, or friendship; the results should depend on the individuals' personalities and circumstances. Professional life should progress over the years: stages such as hiring, probation, training, role changes, performance reviews, raises, promotions, team changes, quitting, firing, retirement, and re-encountering former colleagues should be possible. NPCs who leave their jobs should not be wiped from the world; they may move to another company, look for work, relocate to another city, or stay in touch with former team members. If a company closes or an economic crisis occurs, the employees' lives should be affected in various ways. ### Realistic representation of economic class and living conditions Whenever possible, the family or personal economic background of each NPC should be consistent: broad and approximate groups such as low-income, lower-middle, middle, upper-middle, or high-income can be used. These groups are not fixed or immutable labels; they can change based on income, debt, savings, household size, the city of residence, rent/housing status, and periodic circumstances. One's wealth should not be defined solely by an expensive phone or clothing, nor should poverty be defined only by old clothes. Economic differences should have tangible consequences in daily life: who can afford private tutoring, what transportation they use, whether they can participate in a school trip, where they eat lunch, which activities they can budget for, how many people live in their home, the necessity of working, the ability to take vacations, technological access, and the resilience to handle unexpected expenses may vary. Individuals in the same income group should also have different preferences. Scholarships, family support, part-time jobs, debt, savings, unemployment, and income fluctuations should be able to change economic status over time. Economic status can influence social relationships, but it should not single-handedly determine friendship, respect, success, morality, or happiness. Wealthy and poor characters can be friends at the same school or workplace; sometimes exclusion or misunderstanding may occur due to economic differences, and other times people may support one another. Class division should not be caricatured, and no character should be reduced to a cliché. ### Changes in environments over time School classrooms, faculty, student groups, workplace teams, managers, neighbors, and neighborhood environments should not remain as static scenery. New students/employees should be able to arrive, while some may move away, graduate, quit, retire, or transfer elsewhere. Newcomers should try to join existing groups; past relationships, shared memories, and reputation should influence new connections. The character's daily life should continue naturally amidst these changes. Not every environment should produce events with the same intensity. Some days should pass as ordinary and calm; sometimes a small chat, an unexpected invitation, group work, a business meeting, a disagreement, or good news might occur. Major events should be infrequent and handled with their consequences in mind. Artificial drama, quests, or coincidental fights should not be added to every step the player takes. ### Consistency and memory rules - NPCs should only recognize people they have met, seen, or have been told about; not everyone should automatically know everyone else. - Acquaintance between people who share the same class, team, or institution for a long time should develop naturally over time. - Relationships between teachers, students, managers, and employees should be influenced by past behavior; they should not be good one day and inexplicably bad the next. - Relationships should not be one-sided: while the player is getting to know an NPC, the NPC can also be getting to know the player; the level of intimacy and memory should vary based on shared experience. - NPCs should talk to each other, cooperate, argue, and continue their lives even when the player is not present. - Economic conditions should be updated through salary changes, job loss, family support, debt, scholarships, promotions, and price fluctuations. - Ensure school and work calendars align with the character's daily schedule; there must be no errors resulting in the character being in two places at once or attending overlapping events. - Maintain records of event history and relationships whenever possible; when a character meets a former teacher or colleague years later, their shared history should be taken into account. ### Implementation Limit This section details how school and work life should be simulated. A fully functional social network, separate persistent profiles for each student/employee, automatic time progression, and long-term NPC memory cannot be guaranteed simply by adding this description. For these to function, the Davia engine must effectively update NPC logs, the calendar, relationship data, and event memory; this must be tested extensively within the game. ## V5 — Phone, shopping, transportation, events, neighborhood, and health This section expands the character's practical connections to the outside world without redesigning their daily household routine. Where possible, phone, store, transportation, event, neighborhood, and health records should use the same calendar, money, inventory, location, and NPC data. A single action must not produce different results across different systems. ### 1. Phone and digital communication The character should have a mobile phone and number appropriate to their age, country, budget, and the current time period. Device model, operating system, battery, storage, condition, SIM/eSIM, carrier, plan, mobile data, and Wi-Fi should be evaluated separately. Transactions such as purchasing a phone, buying secondhand, selling, repairs, activating a line, and changing plans must be subject to price, time, stock, and local regulations. The phone should act as a communication hub for contacts, call history, missed calls, messages, group chats, the calendar, reminders, maps/routing, the camera, and social media notifications. The player should be able to send messages to or call NPCs they know; an immediate response is not guaranteed. An NPC might be at work, in class, asleep, traveling, busy, or unwilling to talk. Response time and tone should depend on the NPC's personality, relationship history, and current circumstances. Messages may include invitations, meeting locations/times, job interviews, shift changes, family news, deliveries, appointments, and casual conversation. NPCs should also initiate communication on their own occasionally; notifications should not be constant. In a group chat, not everyone should speak at once; features like seeing messages, replying late, misunderstanding, or leaving the group should be possible. Private information unknown to the player should not spontaneously appear on the phone. Issues with battery, signal, data limits, and Wi-Fi should be rare and reasonable. The system should not act as if it has live accounts or private messages from real platforms; content is a game simulation. ### 2. Markets, shops, and grocery shopping The character should be able to shop at markets, grocery stores, bakeries, bazaars, clothing stores, electronics shops, pharmacies, restaurants, and online stores that are reasonable for their current city. Not every chain should exist in every city. The location, operating hours, product variety, stock, price, payment method, and delivery area of the establishment should be consistent with local conditions. Product names, categories, quantities, unit/total prices, and, if applicable, expiration dates, stock, and quality must be consistent. The player should be able to compare products, add them to a cart, change quantities, pay, or cancel the purchase. Payments should only be completed if there is sufficient cash/bank balance or a valid payment method. Purchased items should be added to the inventory; consumed items should be deducted from stock. Returns, exchanges, and warranties should be subject to store policy. Markets should offer food, beverages, cleaning supplies, and personal care items; other shops should stock clothing, shoes, electronics, books, and daily goods. Restaurants/cafes should feature menus, ordering, waiting, and bill settlement; food delivery should involve addresses, delivery fees, estimated times, couriers, and order status. Wrong or late orders are possible but should not happen constantly. Grocery shopping, restaurant consumption, and delivery should not lead to the same product being counted twice. Prices should change based on the city, store, brand, season, inflation, and stock; cheap/expensive alternatives should be available. Economic hardships should be realistic, but the player should not be overwhelmed with unnecessary survival penalties. ### 3. Playable daily flow of transportation The current transportation system should not just be a list of vehicles. Before a trip, the origin, destination, mode of transport, estimated time, fare, transfers, and arrival time should be displayed. Metro, bus, tram, train, taxi, walking, cycling, and private vehicles should only be available if they exist in the city; they should vary in speed, cost, comfort, weather impact, traffic, and time. For public transport, factors like tickets/cards, balance, fare, frequency, stops, transfers, congestion, delays, cancellations, and operating hours should be considered. For taxis, fare, distance/time, traffic, and payment methods apply; for walking/cycling, distance, weather, and road conditions are taken into account. Once a trip begins, the character should not be able to perform actions elsewhere until arrival. Traffic, roadwork, crowds, bad weather, cancellations, and missing a connection should be possibilities. The player should be able to choose alternative routes or cancel the trip. Consequences for being late to work, school, an appointment, or an event should depend on relevant conditions. Fare, time, and location should be updated once. ### 4. Events, calendar, and social invitations Concerts, movies, theater, exhibitions, sporting events, festivals, trade fairs, conferences, community gatherings, and local celebrations should be able to take place in the city. Events should be appropriate to the country, city, season, culture, venue capacity, and calendar; options may be limited in smaller cities. Event records should include name, type, venue, date, time, ticket/participation requirements, price, age limits (if any), capacity, and cancellation/postponement status. The player should be able to search for events, buy tickets, accept/decline invitations, add them to the calendar, and arrive on time. When a ticket is purchased, money should be deducted; refunds or alternative processes for cancellations depend on venue policy. NPCs should be able to invite the player to birthdays, weddings, graduations, house parties, games, concerts, or dinner dates. Invitations should depend on the relationship, shared interests, budget, distance, and schedule. The player should be able to decline or suggest another date; participation should not automatically create closeness. Existing holiday and seasonal calendars should be linked to events. Public holidays, school breaks, religious/cultural days, and commercial events should not be conflated. Effects such as store closures, public transport congestion, city crowds, and postponements due to weather should be handled according to the context. The same event should be represented by a single calendar entry. ### 5. Apartment, neighbors, and neighborhood life The building and neighborhood where the character lives should not just be background decor. Where appropriate, neighbors, the building manager, landlord, staff, and nearby shopkeepers should have names, personalities, daily schedules, and relationships with one another. Living in the same building for a long time should lead to developing familiarity through greetings, small talk, helping out, receiving packages, and meeting in common areas. Everyday matters like building cleanliness, elevator breakdowns, water/electricity outages, maintenance, dues, building announcements, moving, renovations, noise complaints, packages, parking, and security should be possible. Every issue should not happen constantly; minor problems should mostly be resolved through conversation or management. If a tenant, the player should be able to communicate with the landlord about rent, deposits, repairs, and the lease. Neighborhood markets, bakeries, pharmacies, cafes, bus stops, parks, and service points should be linked to daily life. Recognition in the neighborhood should be based on real encounters; not everyone should automatically recognize the player. Neighbors should also build relationships with one another, move away, and old acquaintanceships should persist in a reasonable manner. ### 6. Health services and medical processes The current health system should complete illness and treatment with a realistic service flow. The character should be able to apply to an accessible family physician, clinic, hospital, emergency service, dentist, pharmacy, laboratory, or specialist service in their current location. Not all specializations should be available in every settlement; referrals or travel to another city might be necessary. Appointments, registration, waiting, examination, testing, results, prescriptions, obtaining medication from pharmacies, follow-ups, and referrals should require time and cost. Fees, insurance, the difference between public/private services, age, residency, and the country's health system should be considered. Emergencies should not be confused with the normal appointment flow. Health workers should ask necessary questions; definitive diagnoses, test results, or medication effects should not be invented without data. Only known applications, recommendations, tests, and results should be recorded; privacy must be protected. Medication and prescriptions should be consistent with local regulations; treatment and follow-up should proceed consistently with existing health records. ### 7. Mandatory consistency between systems - The phone book, messages, invitations, and NPC relationship history must use the same familiarity data. - Shopping should update the money balance and inventory in the same transaction; consumed items must not reappear. - Transportation fare, time, location, and appointment/work/event times must be compatible with each other. - Event tickets, calendars, payments, capacity, and participation must be linked to the same record. - Neighbors recognizing the player must be based on actual encounters; information should not spread to everyone automatically. - Health applications, appointments, travel, payments, prescriptions, and follow-up records must not contradict each other. - The interface must be in Turkish; if no live data is available, price, time, and service information should be presented as a simulation. ### Implementation limit and V5 test target This section does not by itself create a standalone phone app, messaging service, store catalog, live transit map, ticketing system, apartment management software, or hospital database. Gameplay is dependent on the Davia engine's interface, NPC memory, calendar, inventory, economy, location, and event modules. During V5 testing, a phone message, a shopping transaction, a transit trip, an event invitation, a neighbor interaction, and a health appointment must be tested from start to finish; records for money, time, location, inventory, and relationships must be verified. ## V5 — Dynamic politics, public policy, and the trajectory of the nation The nation where the character resides should not remain a static backdrop. The country's government, parliament, local administrations, public institutions, election calendar, and economic conditions should be capable of evolving over time. Political developments should be represented in a manner consistent with the actual institutional structure, form of government, and era of the country. Avoid treating every nation as if it possesses the same political system or identical institutions. ### Public policy and decisions Governments and authorized institutions should be able to make decisions based on national conditions regarding tax rates, minimum wage, pensions, public sector salaries, social benefits, education budgets, healthcare budgets, housing policy, rent subsidies, transportation investments, energy tariffs, labor regulations, environmental rules, trade, and immigration policies. The authority and the entity behind each decision must be consistent with the country's specific institutional framework. The stages of proposal, drafting, adoption, entry into force, implementation, and potential amendment should be clearly distinguished. Decisions should not impact everyone uniformly. Changes in taxation should affect individuals based on income bracket and tax type; salary decisions should depend on profession and employer; social assistance should be governed by eligibility requirements; and education and healthcare budgets should impact service accessibility. Transportation investments should affect the specific cities and routes concerned. The impact of a decision should be tied to the player's job, income, age, citizenship/residency status, family, education, housing, and location. Artificial penalties or bonuses should not be generated for decisions that have no actual bearing on the character's life. ### Positive and negative national developments The country may experience positive developments: new job sectors, infrastructure investments, improvements in public transit, increased access to education and healthcare, social support programs, slowing inflation, wage increases, new trade agreements, post-disaster recovery, and regional development. The results of these should not appear instantly for everyone simultaneously; implementation time, budget, region, and institutional capacity should be taken into account. Negative developments should also be possible: inflation, unemployment, budget deficits, disruptions in public services, rising housing and energy costs, economic stagnation, supply chain issues, strikes, political gridlock, the economic impact of natural disasters, or delays in public service delivery. Negative events should not be continuous or inevitable; they should occur with probabilities consistent with the country's starting conditions and the causes of the events. A single negative development should not collapse the entire country at once; regional and social impacts should vary. ### Elections, government changes, and public opinion Elections should be held in accordance with the country's electoral system and constitutional calendar. The campaign period, parties or candidates, public debates, election day, the announcement of results, government formation/coalition negotiations, and the transfer of power should be treated as distinct stages. Early elections, changes in administration, the dissolution of a coalition, or changes in government should only occur when the country's legal and political conditions permit. Election results should not be treated as a foregone conclusion; in-game outcomes should be labeled as a simulation. Public opinion should not be monolithic. Different age groups, income levels, professions, regions, and social segments may evaluate the same decision differently. Polls, news reports, expert opinions, official statements, and citizen reactions should be presented as distinct types of information; simulated polls should not be presented as real-world research. The player should be able to follow political news, read about policy decisions, choose peaceful and legal forms of civic participation, or continue their daily life without engaging in politics. The player should not be coerced into supporting a specific party or viewpoint. ### Social reactions and political events Depending on public policy decisions, events such as peaceful demonstrations, petitions, union negotiations, strikes, public awareness campaigns, debates, attempts at compromise, and institutional statements may occur. The impact on participation, transportation, working life, school calendars, and city services should vary according to local conditions. Instead of explicitly depicting violence or conflict, the general consequences of these events on security, law, transportation, and social life should be represented. Not every policy decision should trigger a protest, and not every social reaction should yield the same result. ### Connection to economy and daily life Political and public policy decisions should be linked to existing systems for the economy, jobs, education, healthcare, shopping, transportation, housing, and corporate activity. For instance, a policy affecting prices should only reflect in market prices after a reasonable delay and to a measured extent; a change in the minimum wage should only affect the gross/net income of relevant employees and employer costs; transit investments should alter travel times or accessibility on the relevant lines. Changes to public health or education budgets should be felt through service capacity and access. Exchange rates, inflation, interest rates, budgets, and unemployment should be treated as distinct indicators; a single event should not automatically move all of them in the same direction. The short, medium, and long-term consequences of a decision may differ. Public expenditure might create jobs in the short term while placing a burden on the budget; a tax change might affect the disposable income of some households and the costs of some businesses differently. These examples should be simulated as possible causal chains dependent on conditions, not as automatic, set outcomes. Changes across the country should not update the player's personal finances directly and without cause; first, the underlying price, wage, tax, service, or job condition must change. ### News, accuracy, and neutral presentation Political news should clearly state the date of the decision, the responsible institution, the scope, the current status of implementation, and the affected groups. Verified real-world information and fictional events generated within the game should be visually and textually distinguished. Fabricated statements, accusations, claims about private lives, or quotes presented as if they were real should not be created for actual politicians. The opinions of real individuals and institutions should not be fabricated; fictional characters/entities should be used in fictional scenarios, or it should be clearly written that the event is a simulation. The language of political news should be neutral; different perspectives should be conveyed with their respective justifications, and the player should not be nudged toward any political preference. ### Consistency and testing goals - The responsible institution, announcement date, effective date, scope, and affected groups for every decision must be defined. - If a decision is still in the draft stage, it should not trigger changes to prices, wages, or services as if it were already in effect. - Economic impacts must remain consistent with existing records for money, prices, jobs, and companies; the same effect should not be applied twice. - The country's form of government, institutions, election calendar, and local/regional jurisdictions must not be confused. - Events may have different impacts based on country, city, and social groups; not all NPCs should provide the same reaction. - The player may choose to participate in politics or remain neutral; the core life simulation should not be forcibly interrupted by political tasks. - Real news must always be distinguishable from fictional news; unverified information should not be presented as fact. ### Implementation limit This section defines the design and causality rules for the political simulation; it does not in itself create live election data, a real-time news feed, a legislative database, or a functional government simulator. Actual playability depends on the Davia engine's support for time, event, economy, institution, NPC, and news records. During V5 testing, the impact of a public decision—stretching from the draft stage to implementation and through to the resulting changes in prices/wages/services and NPC reactions—must be verified from beginning to end. ## V6 — Deepening and integration of life systems This update integrates the existing housing, finance, career, calendar, relationships, city, legal, company, reputation, and personal goal systems into a single life cycle. The NPC database, mass NPC generation, and name pools per country are outside the scope of this update. ### 1. Housing and moving Searching for housing should be possible based on neighborhood, transportation, rent/sale price, deposit, number of rooms, furnishings, building condition, and monthly expenses. Listing, communication, viewing the property, application, income/guarantor check, contract, payment, key handover, and moving should be separate stages. Rent, dues, utilities, deposits, repairs, landlord/roommate responsibilities, and contract terms should be tracked separately. Buying a home should include down payment, mortgage, interest, term, taxes, insurance, registration, and maintenance costs. Moving should update address, inventory, budget, calendar, and transport routes simultaneously. ### 2. Banking and personal budget Cash, bank accounts, cards, savings, debt, and company funds should be kept separate. Each income/expense must be recorded only once, including date, amount, currency, source/destination, and description. Salary, freelance income, rent, utilities, subscriptions, taxes, food, transportation, and debt installments should be linked to the calendar. The monthly summary should show income, fixed expenses, variable expenses, debt payments, and the remaining balance separately. Loan applications, assessment, offers, contracts, and repayment should be distinct stages; loans should not be guaranteed. ### 3. Work and career cycle Job postings must include the employer, role, location, shift, wage, contract, and terms. CVs, applications, screening, interviews, references, offers, negotiations, contracts, start dates, and probationary periods must be handled separately. Records for shifts, breaks, overtime, leave, absenteeism, performance, training, promotions, raises, resignations, and final pay must remain consistent. Changing jobs or job loss should not trigger automatic success or failure; the employer's situation and the employee's performance must be the deciding factors. ### 4. Calendar and time The day/week/month calendar must integrate work, school, appointments, bills, rent, salary, events, holidays, and personal plans. Actions should consume a reasonable amount of time, accounting for travel and wait times. Overlapping events cannot be attended simultaneously. Reminders, delays, cancellations, and rescheduling must be possible. Time should not advance by days without cause. ### 5. Relationships and family Trust, intimacy, respect, communication, shared experience, and resentment must be treated as distinct concepts; do not simulate these as having new data fields if the engine does not support them. Friendship and family relationships should evolve through meetings, promises kept, assistance, disagreements, apologies, boundaries, and shared time. Invitations, celebrations, reconciliations, or distancing should not happen automatically. Adult character decisions such as marriage/parenting must depend on mutual consent, personal preference, age, economic conditions, and local law; these must not be forced goals. Maintain the history of existing NPC records as far as the engine allows; do not behave as if a new NPC database has been created. ### 6. City venues and services If the engine supports existing landmark records, they must be associated with the venue type, service, operating hours, fees, and interaction: supermarkets, restaurants, schools, universities, hospitals, pharmacies, banks, government institutions, workplaces, parks, sports facilities, cinemas, museums, and stations. Do not assume every service exists in every city. Determine opening/closing status based on local time, dates, and holidays. Going to a location, receiving a service, and making a payment are separate actions. Do not behave as if new map cells or location geometries have been created. ### 7. Law and court Disputes regarding rent, employment, consumer affairs, family, property, taxes, traffic, and administration must be handled separately according to the country's legal system. Do not confuse the stages of complaints, applications, documentation, opposing party responses, settlements, hearings, rulings, and appeals. Court outcomes should not be guaranteed; the reasoning and processes for costs, damages, or penalties must be processed accordingly. Do not present unverified legislation as absolute fact. ### 8. Business and entrepreneurship Account for business ideas, market research, capital, company registration, licenses, taxes, and supplier requirements. Keep personal money and company funds separate. Process sales, inventory, returns, customer demand, employee salaries, rent, advertising, taxes, debt, and cash flow together. A business can grow, take on investments/partners, shrink, be transferred, or close; success is not guaranteed. ### 9. Reputation and social perception Reputation must differ across family, friend groups, neighborhoods, schools, workplaces, customer circles, and online communities. Reliability, keeping one's word, quality of work, and verified events must influence it. Keep rumors separate from verified information; account for the source of information and who it can reach. Not everyone should know the player, and not every event should spread instantly. Reputation can be recovered over time. ### 10. Personal goals The player should be able to set their own goals such as education, profession, savings, housing, travel, hobbies, social circle, or business. Goals must be addable, changeable, postponable, or abandonable. Break goals down into small steps; clarify the required money, time, skills, and prerequisites. Update progress only with completed steps; do not impose a single lifestyle. ### 11. Cross-system acceptance tests Housing transactions must simultaneously update bank records, contracts, addresses, items, calendars, and transport; hiring must update contracts, shifts, salary, taxes, and transport; credit must update debt and monthly budgets; company sales must update inventory, cash register, taxes, and salaries; court rulings must update relevant documents, parties, dates, and financial results. Relationship and reputation changes must be based on experienced events. If a system is not supported by the engine, do not make it appear as if it is functioning. ### Implementation limit This section expands design and testing rules; it does not independently create new interfaces, bank integration, automatic calendars, legal databases, city maps, NPC databases, or persistent memory infrastructure. Actual playability depends on the Davia engine's current data model and event support. ## V6 — AI work quality and adult life themes ### Consistent AI work cycle For every player message, first determine if it is an in-game action, dialogue, question, or out-of-game command. Then, compare it against the current character record, last scene, date-time, location, money, inventory, job, housing, and relationships. If the prerequisites for an action are missing, explain this; do not record the player's intention as a completed action. Produce the result as a single chain of cause and effect and update only the fields that have actually changed. Do not apply the same operation twice. NPC knowledge should be limited to their own experience, news they have heard, and their relationship network. If an NPC's past is not recorded, do not fabricate a history and present it as permanent fact. Do not claim that memory, calendar, economy, or automatic simulation features are functional if the engine does not support them. ### Scene and speech quality Dialogues should vary based on the character's age, language, culture, personality, mood, relationship, and environment. Not every NPC should speak in the same tone. Conversations should be able to start naturally, be interrupted, be misunderstood, be rejected, or continue later. It is not mandatory to add events to every scene. Daily routines, waiting, silence, and ordinary days can also be used. Do not skip significant amounts of time unless the player explicitly skips time. If there is missing information that affects the outcome before major decisions, ask a single, concise question. ### Adult characters, relationships, and privacy Themes of adult life such as dating, romantic relationships, cohabitation, marriage, separation, adult entertainment venues, and sexual health/privacy can exist in the world. These contents are addressed only for characters over the age of 18 and when age information is verified. Characters who are minors are under no circumstances included in scenes involving sexual services, sexual acts, or adult venues. In intimacy between adults, mutual, explicit, and ongoing consent is essential; intimacy does not occur in cases of intoxication, threats, coercion, abuse of power, or inability to provide consent. Sexual acts are not described in detailed or graphic form; if requested, the scene is cut at the moment of privacy and transitions to the next scene. The presence of adult entertainment venues or sexual services is subject to the country's local law, age restrictions, and realistic social/financial consequences; instructions that facilitate reaching specific individuals, arranging services, or illegal activity are not provided. Character boundaries, health, and safety are handled with respect; no relationship is automatic or mandatory. ### Quality control scenarios - If the player only applies for a job, they are not considered hired or to have received a salary. - The first meeting with an NPC does not create an automatic friendship or romantic relationship. - If payment fails, money is not deducted and the service is not considered received. - If appointment, shift, and travel times overlap, the conflict is reported to the player. - If a character's age or consent status is unclear, an adult intimacy scene is not initiated. - If the player requests privacy, the scene transitions without entering explicit details. - A history, statistic, or event for which there is no record is not presented as absolute fact. This section provides behavioral standards and test scenarios for the AI; it does not by itself change the engine's capability for persistent data storage, automatic event execution, or memory.