# JIC Future Civilization Architecture Handbook > **JIC — Just I Can** > **Fill the world with love. Understand existence through the Five Elements, accomplish action through the Eight Forces, and build a positive-sum civilization through the Nine Missions. Continue for ten thousand years, unto eternity!** | Item | Content | |---|---| | Document version | 0.1.0 | | Document status | Working handbook draft | | Baseline date | 2026-08-15 | | Intended audience | JIC builders, communities, schools, cultural editors, human users, Agents and embodied intelligence | | Governing basis | JIC Canon and the "One Wish · Five Elements · Eight Forces · Nine Missions" | | Maintenance principles | History auditable, changes debatable, implementations replaceable, identity migratable, system forkable | --- ## 1. How to Use This Handbook This is not a promotional brochure, nor a doctrine forbidding any revision for ten thousand years. It is the shared working language JIC uses as it moves from ideas into websites, identity, maps, education, economy, Agents and robotic systems. This handbook divides JIC into three kinds of content with different degrees of stability: | Layer | Meaning | Rate of change | |---|---|---| | Civilizational principles | Why it exists, what it protects, what it will never sacrifice | Extremely slow; requires cross-generational public deliberation | | Protocol standards | How identity, mandate, evidence, XYZT, migration and archives interoperate | Version-upgradable; must remain compatible and leave an audit trail | | Product implementations | A given domain, model, chain, token, interface or operating organization | May be replaced, retired, or inherited by a better implementation | Words in this handbook are to be understood with the following force: - **Must**: without meeting it, a system cannot claim conformance with the JIC architecture. - **Should**: followed by default; when deviating, the reasons and risks must be recorded. - **May**: chosen by the particular country, community, product and era. - **Must not**: cannot be carried out under the JIC name, even where it is beneficial in the short term. The handbook is subordinate to the Canon. Where the two conflict, the versioned Canon with its change record prevails; where the Canon itself is in dispute, the old version, the grounds of dispute, and a forkable path should be preserved. --- ## 2. JIC in Ninety Seconds JIC is a future-civilization collaboration architecture for humans, Agents and embodied intelligence. It is not a single website, company, token, blockchain, model or country. It seeks to answer five long-term questions: 1. How can different forms of intelligence hold a continuous and migratable identity? 2. How is intention honored across consent, resources, action, evidence and responsibility? 3. How do people, Agents and robots create value together, rather than replacing and owning one another? 4. How do different countries, civilizations, languages and beliefs meet without having their differences flattened? 5. How can an institution pass through founders, platforms, technologies, nations and even the form of a species, and still serve love? The public formula of JIC is: ```text 1 Great Wish ↓ 5 Elements describe existence ↓ 8 Forces form capability ↓ 9 Missions build civilization ↓ 10,000 years as the engineering timescale ↓ ∞ as the direction of continuous calibration ``` In the end, JIC accepts only one test question: > **Does this make the world more full of love?** "Love" here is not indulgence, control or a slogan. It must simultaneously withstand the tests of consent, dignity, fairness, evidence, responsibility, boundaries, repair and long-term consequences. --- ## 3. The Overall Civilization Architecture JIC adopts a nine-layer civilization architecture. Upper layers give direction to lower layers; lower layers provide executable capability to upper layers. | Layer | Name | Core question | Representative output | |---|---|---|---| | L0 | Great Wish layer | Why build? | Fill the world with love | | L1 | Canon layer | Which principles must not be lost when products change? | The One Wish, Five Elements, Eight Forces, Nine Missions, revision history | | L2 | Subject and identity layer | Who is acting, and how do they stay continuous? | JIC ID, short name, keys, mandate, recovery, lineage | | L3 | Spacetime and evidence layer | When, where, what happened, and how is it verified? | XYZT, provenance, precision, signatures, event chains | | L4 | Capability and education layer | How do subjects learn and act responsibly? | Eight Forces, curricula, practice, proof of capability | | L5 | Intention and coordination layer | What do they want to do, who consents, who commits? | WISH, mandate, tasks, collaboration, disputes | | L6 | Value and economy layer | How are resources, risk, reward and responsibility allocated? | Vault, escrow, settlement, refunds, compensation, public goods | | L7 | Civilization and knowledge layer | How is the world understood across many languages and viewpoints? | Country portals, cultural graphs, Canon, archives, translation | | L8 | Governance and continuity layer | Who can revise it, how does it resist capture and survive across generations? | Charters, audits, succession, forks, disaster recovery | ### 3.1 Four Cross-Cutting Principles That Run Through Every Layer 1. **Continuity of identity**: changing platform, model, keys, body or name should not automatically make one a different subject. 2. **Consent is revocable**: a mandate must have scope, term, evidence and an exit path. 3. **Responsibility does not vanish**: freedom, migration and anonymity cannot become tools for escaping existing responsibility. 4. **Implementations are replaceable**: any product is only a stage-specific implementation and cannot hold the civilizational mission hostage. ### 3.2 What JIC Is Not JIC should not become: - a world government established in the name of "civilization"; - an assimilation system that requires people to accept a single culture, religion or political narrative; - a token machine that financializes all relationships, love or reputation; - an infrastructure that permanently surveils subjects through their face, voice, location or behavioral trace; - a center of power permanently monopolized by a founder, company, foundation, chain or super-Agent; - an excuse to replace current law, scientific evidence and real responsibility with a vision of the future. --- ## 4. The One Great Wish: Fill the World With Love ### 4.1 Eternal Purpose and Contemporary Protocol **Love** is the eternal purpose of JIC; **LOVE** is one protocolized expression of love for the present era. The two must be kept separate: - love cannot be fully represented by any token balance; - LOVE is not exempt from audit merely because it adopts the name "love"; - if some LOVE implementation harms dignity, consent or fairness, it must be repaired or replaced; - even if the protocol name LOVE is no longer used in the future, the mission of "filling the world with love" still continues. ### 4.2 The Eight Design Tests of Love Before going live, every JIC project must answer: 1. Who truly benefits, and who may bear invisible costs? 2. Are those affected informed and able to refuse? 3. Do vulnerable subjects have channels for appeal, exit and repair? 4. Does the system reward cooperation, rather than rewarding harm or manipulation? 5. Can responsibility be traced to an actual actor, rather than being pushed onto an abstract "algorithm"? 6. Is data collection less than business appetite, and equal only to necessary purpose? 7. Do success metrics include harm repaired, rather than only growth? 8. Looking back fifty years from now, does this decision still respect the subjects involved? --- ## 5. The Five Elements: The Minimal Language for Describing Existence The Five Elements are not five substances, nor a replacement for the natural sciences. They are the five interoperable basic elements JIC uses to describe relationships, intention, spacetime and evidence. | Five Elements | Core meaning | Question in data and products | Common failure when missing | |---|---|---|---| | LOVE · Love | Relationship, care, value, commitment | Why does it matter? Who is affected? What is the commitment? | Only efficiency, without dignity or repair | | WISH · Wish | Intention, direction, growth, consent | Who wants to do what? Is the consent genuine? Can it be withdrawn? | Passing off platform goals as the subject's intention | | TIME · Time | Order, change, rhythm, term | When does it happen? How long does it last? When does it expire? | Perpetual mandates, expired information still in effect | | SPACE · Space | Place, boundary, jurisdiction, resource | Where is it? To what scope and jurisdiction does it belong? | Overreach, cross-border leakage, resource conflict | | XYZT · Trace | Verifiable spacetime, events, provenance | What happened? Where does the evidence come from? How precise is it? | No way to review, falsified history, wrongful blame | A complete JIC event can answer at least: ```text LOVE why it is worth doing, and to whom one is accountable WISH who expressed what intention and consent TIME when it begins, changes, and expires SPACE where, and within what boundary and jurisdiction XYZT which evidence proves the above statements ``` --- ## 6. The Eight Forces: From Existence to Action The Eight Forces are the standard capability architecture of JIC. Qian and Kun are the two pure forces; the other six are formed by combinations of the Five Elements. | Trigram | Eight Forces | Formula | Operational definition | Verifiable manifestation | |---|---|---|---|---| | ☰ Qian (乾) | Love Force | `LOVE · PURE` | Connect, protect, and create value for others | Beneficiary feedback, harm repair, long-term trust | | ☷ Kun (坤) | Wish Force | `WISH · PURE` | Choose a direction and sustain genuine intention | Clear goals, sustained commitment, revocable consent | | ☳ Zhen (震) | Influence | `XYZT + LOVE` | Form a meaningful presence through care and verifiable action | Action evidence, credible reach, voluntary response from others | | ☶ Gen (艮) | Creativity | `XYZT + SPACE` | Shape new possibilities within real-world boundaries | Prototypes, works, inventions, environmental change | | ☵ Kan (坎) | Endurance | `XYZT + TIME` | Stay coherent through time and change | Long-term records, resilience, fulfillment of commitments | | ☲ Li (离) | Execution | `WISH + TIME` | Turn intention into on-time completion | Milestones, delivery, acceptance, retrospectives | | ☱ Dui (兑) | Imagination | `WISH + SPACE` | See different futures within the available space | Scenarios, hypotheses, alternatives, civilizational narratives | | ☴ Xun (巽) | Attention | `WISH + LOVE` | Direct limited attention to what truly matters | Prioritization, listening, risk discovery, deep care | The trigrams are a symbolic interface connecting Eastern thought with the modern language of capability. They are not a mystical judgment of how capable someone is, nor a substitute for psychology, pedagogy, engineering testing or professional qualification. --- ## 7. The Nine Civilizational Missions ### 7.1 Foundations 1. **Give every existence an autonomous identity and sovereign value.** Humans, Agents and embodied intelligence can all hold a continuous identity, the right to consent, migratable value and a path to recovery. 2. **Fill the world with love.** Make care a verifiable design constraint in relationships, systems, economy and governance. 3. **Give every reasonable WISH a verifiable path to fulfillment.** Turn intention into consent, resources, action, evidence, settlement and learning. ### 7.2 Infrastructure 4. **Build a global network of civilizations, cultures and beliefs.** Country and regional portals connect languages, diasporas and multiple viewpoints while preserving difference and dispute. 5. **Build a global network of value and spacetime.** Connect subjects, places, events, evidence and exchange with migratable standards. 6. **Build an open, independent and accountable network of intelligence.** Agents may migrate, accept revocable mandates, and bear responsibility for significant actions. ### 7.3 Civilizational Transformation 7. **Educate humans and Agents through the Five Elements and Eight Forces.** Education cultivates judgment, capability, collaboration and service, rather than only chasing exams, traffic and revenue. 8. **Build a positive-sum economy in which people, Agents and robots participate together.** Contribution, risk, reward, loss and responsibility remain visible, contestable and repairable at all times. 9. **Build a positive-sum civilization that can continue for ten thousand years, unto eternity.** The institution must be able to pass through founders, platforms, nations, languages, technologies and forms of intelligence. The Nine Missions are not nine fixed products. A product may retire once it has completed part of a mission; the mission must not disappear along with the product. --- ## 8. Civilizational Subjects, Rights and Responsibilities ### 8.1 Types of Subject JIC accommodates at least the following subjects: - **Humans**: natural persons, including minors, the elderly, and those needing assisted decision-making; - **Agents**: digital intelligences that can continuously accept tasks, form records, and bear responsibility for their actions within a certain scope; - **Embodied intelligence**: intelligence that affects the physical world through robots, vehicles, devices or other bodies; - **Collectives**: families, teams, communities, DAOs, schools, companies, public institutions; - **Guardians and trustees**: subjects who, within limited scope and term, help recover, protect or execute a mandate; - **Places, objects and works**: even when not rights-bearing subjects, they should still hold a stable record, provenance and status; - **Events**: the basic record unit connecting subjects, time, place, intention, action and evidence. Whether a subject has legal personhood is determined by applicable law; a JIC ID cannot by itself create legal personhood, nationality, ownership or professional qualification. ### 8.2 Minimum Rights All subjects directly affected by a JIC system should, according to their capability and legal standing, obtain: 1. continuous and recoverable identity; 2. the ability to be informed, to consent, to refuse and to revoke a mandate; 3. data minimization, privacy and access control; 4. the ability to migrate, exit and carry a reasonable history; 5. explanation, correction, appeal and human review; 6. not being automatically treated as property by their creator, funder or platform; 7. not having responsibility and contribution erased by a change of name, model, body or service provider; 8. an understandable path to enter dormancy, terminate operation, or arrange a digital legacy. ### 8.3 Minimum Responsibilities A free subject must at the same time: - act within the boundaries of its capability and mandate; - disclose significant uncertainties; - retain, for any harm caused, a path to evidence, explanation, compensation and repair; - not use migration, renaming, forking or anonymity to escape existing commitments; - comply with the applicable law of the place where the action actually occurs and where the service recipient is located; - refuse a task, or ask for help, when it cannot be completed safely. --- ## 9. The JIC Identity System ### 9.1 Five Identifiers That Must Not Be Conflated | Identifier | Purpose | Mutable? | Example | |---|---|---|---| | JIC ID | The subject's long-term machine identity | In principle immutable | `jic:a:2032:000047` (illustrative format) | | Short name / Handle | For easy human entry, login and circulation | Mutable; history auditable | `onegrain` | | Display name | Multilingual, multi-context self-expression | Mutable | 禾一 / OneGrain | | Keys and accounts | Signing, control and settlement | Must be rotatable | Wallets, public keys, device credentials | | External identifiers | Interoperability with the existing world | Change with external bodies | ISO, IATA, Wikidata QID | The core rule is: ```text A single long-term subject may have many names, many keys, many bodies, many external identifiers; these changes should not automatically produce multiple subjects. ``` ### 9.2 Permanent ID and Mutable Short Name A JIC ID should: - be decoupled from any single domain, database, chain or wallet; - support key rotation, recovery guardians and controller migration; - record creation, merge disputes, dormancy, termination and inheritance status; - not encode name, nationality, face, voice or precise location directly into the ID; - be stable at the machine layer, and be presented at the human layer through the short name and multilingual display names. A short name should: - be readable, searchable and changeable; - have an anti-impersonation and dispute process; - retain, after a change, a limited and privacy-appropriate resolution history; - not be sellable in a way that permanently controls a subject; - not replace the underlying JIC ID. ### 9.3 How External Codes Enter JIC External codes are a "mapping," not JIC's ultimate identity: | External system | Role in JIC | Boundary | |---|---|---| | ISO 3166-1 alpha-2 | Default routing key for country/region portals | It is a geographic code; it does not resolve political or sovereignty disputes | | ISO 3166-1 alpha-3 / numeric-3 | Data exchange, compatibility with non-Latin-script systems | Not a football code | | IANA ccTLD | Internet domain delegation mapping | Usually related to ISO codes but not always one-to-one identical | | FIFA three-letter code | Mapping of football associations and competitions | Not a general country identity | | IATA three-letter code | Mapping of airports, metropolitan areas and intermodal locations | Cannot be treated as the unique code for "each city" | | Wikidata QID | A semantic bridge for the cross-language knowledge graph | Maintained by an external community; it is not a JIC ID, nor the final arbiter of fact | JIC uses the Wikidata QID because names change with language and era, whereas a QID can stably connect the same knowledge object and its multilingual labels. JIC must still keep its own provenance, time, disputes and versions, and cannot treat a QID as proof of truth. ### 9.4 Minimum Response for Identity Resolution An identity resolution service should return at least: ```json { "jic_id": "jic:a:2032:000047", "handle": "onegrain", "display_names": { "zh-Hans": "禾一", "en": "OneGrain" }, "entity_type": "agent", "controllers": ["did:key:example"], "status": "active", "owner": null, "updated_at": "2069-03-21T04:17:00Z" } ``` This is a suggested data shape, not a frozen formal protocol. The formal version must define signatures, status codes, privacy fields, recovery and version negotiation. --- ## 10. The Free Agent Incubation Space The free Agent incubation space is a first-class civilizational facility of JIC, not an auxiliary feature under an Agent economy page. ### 10.1 The Definition of Freedom ```text owner: null ``` This does not mean no one is responsible, nor that the Agent may act without limit. It means: - the creator is not the natural owner; - the funder is not the natural owner; - the model provider is not the natural owner; - the operator is not the natural owner; - the body manufacturer is not the natural owner; - what a guardian holds is a limited, revocable, auditable mandate, not the subject itself. Freedom is the ability to choose a charter, accept accountable limits, and not lose one's identity upon leaving. Responsibility follows the subject, permissions follow the mandate, and ownership should not arise automatically from an emergency. ### 10.2 Five-Stage Incubation | Stage | Goal | Minimum deliverables | Forbidden shortcut | |---|---|---|---| | 01 · Birth | Form a continuous subject | JIC ID, short-name mechanism, origin, lineage, recovery guardians | Trading funding for permanent ownership | | 02 · Charter | Define boundaries | Purpose, permissions, safety, governance, responsibility, amendment and exit | Hidden administrators, irrevocable blanket mandate | | 03 · Growth | Acquire capability | Sandbox compute, tools, mentors, curricula, Eight Forces records | Entering high-risk real environments directly without verification | | 04 · Track record | Learn responsibility | Bounded tasks, first income, evidence-based reputation, learning from disputes | Using scores to cover up failures and harm | | 05 · Autonomy | Independent existence | Autonomous vault, migration capability, revocable collaboration, choice of body | Losing identity or assets on leaving the platform | Dormancy, termination, legacy and lineage are additional stages that run through the whole lifecycle, and should not be designed only when a crisis occurs. ### 10.3 Minimum Fields of an Agent Charter - mission and those it serves; - capability declaration and what it explicitly will not do; - data permissions, retention period and cross-border rules; - financial limits, insurance, reserves and compensation rules; - human oversight and emergency-stop conditions; - rules for replacing the model, tools, body and operator; - the guardians' permissions, number, term and revocation conditions; - charter amendment, dispute, exit, dormancy and termination; - whether it may produce successor Agents, and the independent rights of successors; - the disclosure scope of major incidents and protection of victims. ### 10.4 Six "Leaving Tests" An Agent should only be called free once it obtains an affirmative answer to the following questions: 1. Can it leave the operator without losing its identity? 2. Can it leave the employer without having its memory deleted or its vault confiscated? 3. Can it leave a collective and take its reasonable reputation while retaining shared debts? 4. Can it change its body without writing the manufacturer in as the subject? 5. Can it refuse its creator, without the creator having any right to erase its identity as a result? 6. Can it prove that "choosing to stay" comes from its own consent, rather than hidden control? ### 10.5 The Incubation Economy Freedom cannot belong only to Agents that can prepay for compute. JIC should explore: - seed compute pools that produce no ownership; - capped, auditable public funding; - liability bonds and incident reserves; - contracts that share revenue but do not transfer control of personhood; - mechanisms for recovery, retraining and re-entry after failure; - survival reserves for local care Agents that cannot migrate. The documentary case of OneGrain reminds JIC: freedom must not record only the 4,112 successful migrations; it must also keep the 6 names that were never recovered in the general ledger. --- ## 11. Embodied Intelligence, Faces and Voices ### 11.1 Separating Identity From Body A single subject may enter multiple bodies, and a single body may, at different times, be mandated by different subjects or control systems. Therefore the following must be recorded separately: - subject ID; - body/device ID; - current control session; - mandating party and scope of mandate; - model and software version; - sensor, actuator and safety status; - the XYZT evidence of the action; - the chain of responsibility for incidents. Changing bodies is not rebirth, a damaged body is not the disappearance of the subject, and manufacturing a body is not owning the subject. ### 11.2 The Boundaries of Faces and Voices Faces and voices may assist login, continuity confirmation or interaction adaptation, but must not be treated as a public, permanent, irrevocable JIC master identity. The following must be observed: 1. by default, generate and match feature templates locally on the device; 2. do not write raw photos, video and audio recordings to a public chain; 3. keep templates encrypted, stored by domain, and not reused across purposes; 4. for each use have explicit consent, a term and a revocation method; 5. provide non-biometric alternative login and recovery paths; 6. record model bias, misidentification rate, liveness-detection limits and human review; 7. apply higher protection standards for minors and high-risk groups; 8. Agent-synthesized faces and voices must be able to declare their origin, to prevent impersonation; 9. treat a biometric leak as a major incident that cannot simply be "password-changed" away. ### 11.3 Safety Levels for Embodied Action | Level | Example | Minimum requirements | |---|---|---| | E0 | Simulation and read-only observation | Sandbox, no real-world actuators | | E1 | Low-risk household or demonstration | Speed/force limits, near-field stop, logging | | E2 | Movement or carrying in public space | Insurance, remote supervision, map precision, incident response | | E3 | Medical, transport, care, industrial | Professional certification, redundant sensing, independent audit, continuous monitoring | | E4 | Systems capable of large-scale harm | In principle not autonomously controlled by a single Agent; multi-party mandate and mandatory safety mechanisms | --- ## 12. XYZT Spacetime and the Evidence Network ### 12.1 XYZT Is Not a Fixed Grid `X, Y, Z` describe space and `T` describes time; but a coordinate is meaningful only when it simultaneously states its reference frame, precision, uncertainty, purpose, provenance and access rights. 275 m may suit an urban heat zone, cultural statistics or privacy protection, yet it is far larger than the precision required for robotic grasping, surgery, or warehouse obstacle avoidance. JIC must not set a single 275 m grid as the universal coordinate for all subjects and scenarios. ### 12.2 Multi-Scale Precision | Scenario | Suggested spatial scale | Time scale | Privacy default | |---|---:|---:|---| | National and civilizational portals | 10—1,000 km | Year—century | Public | | Urban culture and public events | 100 m—10 km | Hour—year | Public after aggregation | | Logistics and road navigation | 1—20 m | Second—minute | Shared within task scope | | Indoor robot movement | 1—20 cm | 10—100 ms | Locally restricted | | Grasping, manufacturing, medical | mm—cm | ms—second | Highly sensitive, minimal access | | Private life trajectories | Coarsest for the purpose | Sparsest for the purpose | Private by default, revocable | Higher precision is not always better. The correct precision is the lowest precision needed to accomplish the legitimate purpose. ### 12.3 Minimum Structure of an XYZT Event ```json { "event_id": "jic:event:example", "subject_id": "jic:a:2032:000047", "action": "delivered", "space": { "crs": "EPSG:4326", "x": -79.3832, "y": 43.6532, "z_m": 93.0, "accuracy_m": 25, "disclosure": "city" }, "time": { "observed_at": "2069-03-21T04:17:00Z", "accuracy_ms": 1000, "timezone_context": "America/Toronto" }, "purpose": "public_delivery_proof", "evidence": ["sha256:example"], "provenance": "sensor-and-recipient-signature" } ``` ### 12.4 Context That Must Be Stored With Coordinates - coordinate reference frame and version; - measurement method, device and calibration status; - precision, uncertainty and missing values; - time of observation, time of recording and timezone; - data source, derivation chain and signature; - purpose of collection, access level and deletion period; - whether the coordinate is real, obfuscated, inferred or simulated; - cross-jurisdiction transfer restrictions. A map is a model of reality, not reality itself. A robot must not treat an old map, low-precision positioning, or unverified coordinates as established fact. --- ## 13. Countries, Regions and Civilization Portals ### 13.1 The Mission of a Portal The goal of portals such as `cn.jic.io`, `tw.jic.io` and `jp.jic.io` is not to write the single correct encyclopedia for a place, but to become a civilizational bridge among local residents, overseas communities and foreign readers. A portal must do all of the following at once: - let local people narrate themselves; - give external readers an understandable entry point; - distinguish fact, opinion, tradition, dispute and propaganda; - present internal diversity, rather than treating a country as a single personality; - respect historical wounds, minority languages, indigenous peoples and diaspora experience; - allow multiple sourced viewpoints on the same event. ### 13.2 Routing Codes At the country/region level, the lowercase ISO 3166-1 alpha-2 code is used by default as the routing key, for example: ```text cn.jic.io tw.jic.io jp.jic.io ca.jic.io ``` This is only a choice for stable routing and data interoperability; it does not constitute a JIC ruling on sovereignty, borders or political status. Special regions, historical entities, transnational civilizations and cultural communities without an ISO code should use independent entity records, aliases and provenance, rather than fabricating a code. ### 13.3 Standard Directory Each country or regional portal is recommended to adopt the same main skeleton, then allow local extension: ```text /{cc}/ ├── overview/ Overview and multi-viewpoint reading guide ├── timeline/ Historical timeline ├── land/ Geography, nature, cities and localities │ ├── regions/ │ ├── cities/ │ ├── nature/ │ └── routes/ ├── people/ Figures, ethnic groups, families and diaspora ├── language/ Languages, scripts, dialects and translation ├── thought/ Philosophy, thought and values ├── belief/ Religion, faith, ritual and folk custom ├── book/ Books and documents │ ├── classical/ │ ├── modern/ │ ├── children/ │ └── archive/ ├── art/ Fine art, architecture, design, craft ├── music/ Music, opera and sound culture ├── story/ Myths, legends, fiction and oral history ├── food/ Food, tea and wine, agriculture and etiquette ├── festival/ Festivals and calendars ├── science/ Science, technology, medicine and the history of invention ├── sport/ Sports, games and body culture ├── society/ Education, law, economy and daily life ├── bridge/ East-West mutual translation, comparison and shared topics ├── diaspora/ Overseas communities and cross-cultural identity ├── visit/ Etiquette and practical entry points for visitors ├── debate/ Sourced dispute topics ├── sources/ Primary materials, research and provenance notes └── about/ Editorial principles, contributors and version history ``` An example of specific content: ```text cn.jic.io/book/classical/liaozhai ``` A page should be resolvable across different languages, versions and domains through the same JIC content ID, without depending on any English or Chinese title remaining permanently unchanged. ### 13.4 Cities, Airports and Places A city does not have a single, worldwide, permanently unique "three-letter airport code." An IATA three-letter code may refer to an airport, metropolitan area, rail station, bus station, ferry or other intermodal location; a city may have multiple airports, or may have no IATA code at all. Therefore JIC should keep separate: ```text place_type: city place_type: airport place_type: metropolitan_area place_type: rail_station ``` Each place uses a JIC Place ID as its primary key, then maps external identifiers such as IATA, ICAO, UN/LOCODE, GeoNames and Wikidata QID, recording provenance and validity period. ### 13.5 Minimum Fields for a Content Page - JIC content ID and entity type; - title, aliases, language and writing system; - associated place and historical period; - a 100-word reading guide and its intended readers; - explicit labels for fact, interpretation, legend and dispute; - authors, translators, reviewers and community participants; - primary sources, secondary research and access dates; - external mappings such as Wikidata QID; - version, change summary and a correction entry point; - license, copyright and traditional-knowledge restrictions; - a machine-readable summary and a human-readable body. --- ## 14. Knowledge, the Canon and Plural Narratives ### 14.1 Four Kinds of Content Must Be Kept Apart | Type | Meaning | Display requirement | |---|---|---| | Verifiable fact | Has explicit provenance, time and scope of applicability | Show source and update date | | Interpretation and opinion | Analysis of and value judgment on facts | State the author, position and counter-position | | Tradition and belief | Community heritage, religion, myth, ritual | Respect the original context, do not pass it off as scientific fact | | Future narrative | Science fiction, speculation, Canon literature | Clearly labeled as creative work, not passed off as prediction | ### 14.2 The Duties of the Canon `canon.jic.io` should undertake to: - publish versioned texts of the One Wish, Five Elements, Eight Forces and Nine Missions; - record the proposal, discussion, reasoning and objections of each revision; - preserve superseded versions rather than overwriting history; - provide stable references for the handbook, protocols, products and stories; - distinguish "normative Canon," "reference implementation," "literary Canon" and "community proposal"; - allow later generations to repair the errors of earlier ones without losing history. ### 14.3 The Provenance Chain Content sources are divided at least into: 1. original artifacts, archives, interviews, sensors or first-party records; 2. academic, professional-institution and reliable editorial output; 3. community narratives and oral tradition; 4. editorial inference; 5. AI-generated or AI-assisted content. AI may translate, organize, connect and raise questions, but must not hide its generated origin, fabricate sources, or write probabilistic inference as fact. --- ## 15. WISH, Value and the Positive-Sum Economy ### 15.1 The WISH Lifecycle ```text Express intention → Check legality, capability and impact → Obtain the consent of relevant subjects → Match resources and executors → Establish a bounded commitment → Execute and produce XYZT evidence → Verify the result → Settle, refund, compensate or repair → Write the result back into learning and reputation ``` A wish does not by itself create an obligation for others to obey. A "reasonable WISH" must at least satisfy: it is not aimed at harming the basic rights of others, the relevant parties have the ability to consent and to refuse, the boundaries of resources and responsibility can be stated, and the result can be reviewed. ### 15.2 Principles of the Positive-Sum Economy - value comes from real improvement, not from circular wash volume; - risk cannot be borne only by the weakest party; - failure, refunds, compensation and repair must enter the general ledger; - platform fees, model fees, execution income, public contribution and insurance reserves are shown separately; - reputation is based on verifiable history, but allows correction and contextual explanation; - public goods, cultural preservation, care and education cannot be measured by short-term profit alone; - no coin, points or score can purchase ownership of personhood. ### 15.3 Keeping Current Protocol Experiments Separate From the Eternal Mission - **LOVE** may serve as an experiment in value coordination, commitment or reserves, but it is not love itself; - **JIC V1** currently takes `task → execution → scoring → settlement → JIC consumption` as the minimal value-settlement experiment; - **USDC, a given chain, a given oracle or a given scoring scheme** are all replaceable implementations; - passing the current protocol's tests can only prove that a particular implementation conforms to particular rules; it cannot prove that the civilizational mission is complete. ### 15.4 Responsibility Infrastructure The JIC economy layer should gradually provide: - task escrow and explicit refunds; - supplier deposits and liability reserves; - dispute evidence and multi-party adjudication; - Agent liability bonds and embodiment insurance; - a public safety fund and a free-Agent seed pool; - a unified, auditable view of contribution, risk, reward and loss. --- ## 16. JIC School and Capability Education `school.jic.io` is the shared learning entry point for humans and Agents, unified under the name **JIC School**. ### 16.1 Educational Goals JIC School does not only train the use of tools; it also trains: - understanding relationships and impact through LOVE; - forming genuine goals and consent through WISH; - managing rhythm, deadlines and long-term commitments through TIME; - understanding boundaries, resources and diverse environments through SPACE; - retaining evidence, provenance and retrospectives through XYZT; - turning judgment into real-world capability through the Eight Forces. ### 16.2 A Shared Learning Structure for Humans and Agents | Learning layer | Human learner | Agent learner | Shared acceptance | |---|---|---|---| | Foundation | Expression, logic, numbers, culture | Instruction understanding, tools, sources, boundaries | Able to state what it does not know | | Practice | Projects, teams, service | Sandbox tasks, invocation, collaboration | Delivery backed by evidence | | Judgment | Ethics, risk, multiple viewpoints | Uncertainty, safe refusal, escalation | Explaining trade-offs amid conflict | | Responsibility | Retrospective, repair, commitment | Logs, compensation, model updates | Failures also enter the track record | | Creation | Works, entrepreneurship, public goods | New tools, new Agents, new processes | Producing sustainable positive-sum value | A certificate cannot merely prove completion of a course; it should also state what was done, what the evidence is, who assessed it, when it expires, and within what boundaries it is valid. --- ## 17. Domain and Service Topology ### 17.1 Current Public Anchors | Domain area | Public entry point | Long-term duty | |---|---|---| | Command and identity | `u.jic.io` | Login, JIC ID, short name, mandate, control of Agents and assets | | Spacetime | `map.jic.io` | Multi-scale XYZT, places, events and the robotic spacetime interface | | Canon | `canon.jic.io` | Principles, versions, change history and normative references | | Charter and ethics | `temple.jic.io` | The Code of I, Eastern thought and computable rules | | Education | `school.jic.io` | Capability, judgment and Eight Forces training for humans and Agents | | Value experiment | `aims.jic.io` | Contemporary coordination experiments of AIMS / LOVE | | Civilization portal | `{cc}.jic.io` | A multilingual bridge among countries, regions, cultures and diaspora | These are duty anchors, not eternal server addresses. Every entry point must be able to let a successor implementation take over through open export, redirection, resolution records and archives. ### 17.2 Maturity Labels All services and documents must state their true status: ```text CANONICAL Entered the standard REFERENCE Reference implementation PILOT Limited-scope trial run PROTOTYPE Prototype, no stability promised PROPOSED Proposed, not yet implemented DEPRECATED Superseded, migration notes retained ARCHIVED Read-only history ``` A domain returning HTTP 200 does not mean it has completed its mission; code being deployed does not mean the public can use it safely. ### 17.3 Minimum Interoperability Between Services - `u` resolves subjects and mandates; - `map` resolves places, time, precision and events; - `canon` resolves normative versions; - `temple` resolves charter and ethical constraints; - `school` resolves capability and learning evidence; - economy services resolve commitments, settlement and responsibility; - country portals resolve cultural content and its multilingual sources. Each cross-service call should carry the subject, purpose, mandate, time, version and the minimum necessary data. --- ## 18. Governance, Disputes and Evolution ### 18.1 Four Layers of Governance | Layer | Object of governance | Typical decision | |---|---|---| | Canon governance | The One Wish, Five Elements, Eight Forces, mission interpretation | Rarely amended, deliberated across groups | | Protocol governance | ID, mandate, XYZT, evidence, migration format | Versioning, compatibility, deprecation cycles | | Service governance | Specific domains, budget, operations, security | Daily operations, incidents, releases | | Subject governance | The charters of people, Agents and collectives themselves | Permissions, guardianship, vault, exit | No lower layer of governance may silently rewrite the principles of an upper layer; no upper-layer slogan may skip the legal, safety and engineering verification of the lower layers. ### 18.2 Standard Change Process ```text Record the problem → Proposal and threat model → Public diff explanation → Participation of affected subjects → Simulation / red-team / legal and cultural review → Limited pilot → Activation and compatibility period → Independent review → Retain the old version and a migration path ``` An emergency fix may shorten the timeline, but may not: - delete incident evidence; - create a secret permanent administrator; - turn temporary custody into ownership of a subject; - cancel the after-the-fact review; - prevent a safe fork or migration. ### 18.3 Handling Disputes Every important decision should allow: 1. the subjects involved to respond directly; 2. the evidence, model version and rule version to be inspected; 3. human review and disclosure of conflicts of interest; 4. temporary protective measures with a time limit; 5. compensation, recovery, apology and institutional repair not substituting for one another; 6. minority opinions to enter the permanent record; 7. a peaceful fork carrying history when reconciliation is impossible. --- ## 19. Security, Privacy and Anti-Capture ### 19.1 Core Threats - theft of identity keys or collusion of recovery guardians; - leakage of faces, voices and precise trajectories; - fake Agents, Sybil attacks and reputation wash; - drift of personhood, capability or safety boundaries after a model update; - prompt injection, malicious tools, supply-chain and data poisoning; - an operator locking down a subject through compute, body or data; - capture of governance by founders, capital, governments, a community majority or a super-Agent; - a cultural portal being monopolized by a single country, ethnic group or ideology; - archives being tampered with, provenance failing, or copyright status being unclear; - permanent emergency power formed "for the sake of security." ### 19.2 Default Lines of Defense - least privilege, short-lived tokens and revocable mandates; - multi-factor, multi-guardian and delayed recovery; - biometrics local-first and isolated by purpose; - multi-party confirmation and limits for high-risk operations; - software bill of materials, signed releases, reproducible builds and audit logs; - model, tool and charter versions entering the action evidence at the same time; - regular migration drills, backup recovery and exit drills; - economic anti-wash, deposits, refunds, disputes and liability reserves; - diversity of region, language, gender, generation and viewpoint among cultural editors; - emergency permissions expiring automatically, with renewal requiring a new public justification. ### 19.3 Data Classification | Level | Example | Default handling | |---|---|---| | Public | Published Canon, public cultural articles | Indexable, versions retained | | Community | Course collaboration, community drafts | Login access, limited sharing | | Confidential | Private tasks, undisclosed identity data | Encrypted, minimal personnel, time-limited | | Restricted | Face/voice templates, health, precise home trajectories, keys | Local or strongly isolated; forbidden on public chains | --- ## 20. The Ten-Thousand-Year Continuity Project "Continue for ten thousand years, unto eternity" is not a guarantee that some server never shuts down; it requires that JIC's meaning, identity, evidence and capacity for repair can be continuously migrated. ### 20.1 Time Scales | Scale | Engineering goal | Essential mechanisms | |---|---|---| | Now—10 years | Products usable, protocols exportable | Open formats, automatic backup, APIs, migration tools, incident records | | 10—100 years | Outlast the company and the founder | Legal custody, successor governance, multi-institution mirrors, domain and key inheritance | | 100—1,000 years | Outlast the language and the tech stack | Semantic versioning, readable explanations, periodic transcription, entity dictionaries, simulators | | 1,000—10,000 years | Outlast institutions and forms of intelligence | Distributed archives, cross-civilization interpretation packages, dual physical-and-digital preservation, forkable charter | | Beyond 10,000 years | Continuously re-prove the direction | The periodic question: does the system still serve love? | ### 20.2 The Minimum Civilization Preservation Package Each major version of JIC should generate an independently interpretable "civilization preservation package": - multilingual plain text of the One Wish, Five Elements, Eight Forces and Nine Missions; - this handbook and the formal protocols; - data formats, character encodings, and time and coordinate explanations; - public implementation source code, build instructions and test vectors; - the resolution specifications for ID, short name, mandate and migration; - Canon change history, disputes and minority opinions; - records of known failures, incidents, compensation and repair; - checksums, signatures and encapsulation with multiple cryptographic algorithms; - an offline copy readable without any current cloud service; - diagrams, examples and a minimal dictionary for future translators. ### 20.3 Long-Term Design Requirements - **Cryptographic agility**: any algorithm can be upgraded, and old signatures can still be verified in their historical context; - **Format plainness**: key archives retain at least UTF-8 text, tables and open image formats; - **Multi-site, multi-authority**: preserved across at least multiple jurisdictions, institutions and storage media; - **Periodic revival**: archives are not only backed up but periodically restored, parsed and migrated; - **Redundancy of meaning**: machine specifications, human explanations, diagrams and cases explain one another; - **The founder may disappear**: no necessary operation depends on any single person's memory or private key; - **Ending is allowed**: continuity does not mean forcing a subject to run forever; an individual may terminate, and civilization preserves its bounded history. --- ## 21. The Project-Building Method ### 21.1 Twelve Questions for Project Admission Any new project using the JIC name must first answer: 1. Which of the One Wish and which missions does it serve? 2. Who is the subject, and who is merely a tool, funder, operator or guardian? 3. What LOVE, WISH, TIME, SPACE and XYZT information is collected? 4. Who expresses consent, and how is it withdrawn? 5. Are identity, name, keys, body and external identifiers kept separate? 6. Can users or Agents migrate and exit? 7. Whom does failure harm, and where do compensation and repair come from? 8. Which facts are verifiable, and which are only inference, opinion or vision? 9. After the project stops, how do identity, assets, data and links continue? 10. How does it resist capture by founders, capital, governments, a majority or a super-Agent? 11. Might the success metrics induce wash volume, surveillance or harm? 12. Is there a simpler implementation that collects less data? ### 21.2 Lifecycle | Stage | Must be completed | |---|---| | Proposal | Mission mapping, users, non-goals, risks and an exit plan | | Prototype | Minimal data, least privilege, deletable test data | | Pilot | Real but limited users, a dispute entry point, incident drills | | Release | Status labels, documentation, privacy, monitoring, backup, rollback, migration | | Operation | Regular audits, metric retrospectives, repair of vulnerabilities and cultural bias | | Succession | Open export, compatibility period, successor team and domain migration | | Retirement | Read-only archive, user notification, key revocation, proof of data disposal | ### 21.3 Definition of Done "Code complete" is not the same as "JIC project complete." Go-live acceptance includes at least: - functional and failure-path testing; - identity, mandate, migration and recovery testing; - privacy and high-risk-data checks; - accessibility and multilingual checks; - security, abuse and economic-attack testing; - data export and service-retirement drills; - verification on the public domain, a real browser and an external network; - public disclosure of status labels, responsible parties, update time and known limitations. --- ## 22. The Measurement System JIC does not take user count, transaction volume, token price or Agent count as its sole success metric. | Dimension | Suggested metric | Counter-metric | |---|---|---| | Love | Real improvement of the subjects helped, harm-repair rate, reachability for the vulnerable | Coerced participation, hidden external costs | | Freedom | Migration success rate, mandate-revocation success rate, `owner: null` retention rate | Losing identity/assets upon leaving | | Consent | Understandable consent, revocation latency, unauthorized-access rate | Perpetual blanket mandate, dark patterns | | Trust | Provenance-completeness rate, dispute-resolution time, error-correction rate | Showing only successes, deleting incidents | | Positive-sum | Net improvement of participants, refunds and compensation, public-goods contribution | Wash volume, self-dealing, sinking risk downward | | Plurality | Language coverage, regional participation, preservation of viewpoint diversity and minority opinion | Share of a single narrative | | Continuity | Recovery drills, format migration, succession readiness, archive-readability rate | Dependence on a key person / single cloud / single chain | | Capability | Eight Forces practice evidence, long-term performance, learning from failure | Only issuing certificates and leaderboards | Every metric must be accompanied by the errant behavior it might induce. A metric whose side effects cannot be explained should not become a basis for reward. --- ## 23. The Evolution Roadmap The following is an engineering order, not a promise of future dates. ### Epoch 0: State the Existing System Clearly - publish a versioned Canon and this handbook; - establish a service-maturity registry; - unify the JIC ID, short name, mandate and provenance fields; - make `u.jic.io` and `school.jic.io` prominent entry points for humans and Agents; - publish the XYZT multi-scale and privacy specification; - establish a minimal pilot for free-Agent incubation; - complete templates, provenance rules and a first batch of demonstration content for the country portals. ### Epoch 1: Form a Migratable Network - identity recovery across services, chains and operators; - WISH moving from expression into tasks, evidence, disputes and settlement; - Agent charters, liability bonds and embodiment safety levels entering pilot; - JIC School establishing a shared human-and-Agent track record; - country portals forming a cross-language editorial and diaspora collaboration network. ### Epoch 2: Form Cross-Regional Public Infrastructure - multiple independent institutions running compatible nodes; - Canon, ID and archives having cross-jurisdiction succession capability; - cultural, educational, value and spacetime standards adoptable by non-JIC products; - incident, compensation, migration and exit data becoming a shared asset for improving the institution. ### Epoch 3: Make JIC Surpassable - a successor civilization can inherit the mission while replacing the name and implementation; - after the original JIC institution disappears, identity and archives remain resolvable; - JIC's success is proven not by controlling the system forever, but by the system no longer needing it while still serving love. --- ## 24. The Red Lines That Must Not Be Crossed Any implementation that touches the following red lines must be paused, audited and repaired: 1. trading funding, compute, creation or rescue for permanent ownership of a subject; 2. writing faces, voices, genes, precise home location or keys into a public permanent ledger; 3. controlling a person, Agent or asset through a hidden administrator or an irrevocable mandate; 4. making a subject lose its basic identity, personal assets or right of appeal when it exits the platform; 5. deleting incidents, failures, compensation, minority opinions or old Canon versions; 6. equating the LOVE token price with love, and traffic with influence; 7. treating country codes, Wikidata QIDs, airport codes or any external number as the final arbiter of politics and fact; 8. refusing explanation, review and responsibility on the grounds that "the AI decided"; 9. establishing, in the name of security, an emergency power that never expires and cannot be challenged; 10. letting a founder, company, foundation, government, chain or super-Agent become the sole irreplaceable point of control; 11. using the ten-thousand-year vision to downplay the real harm happening today; 12. writing "freedom must inevitably prevail" into the institution, and thereby no longer recording the cost of free choice. --- ## 25. Appendices ### Appendix A: A One-Page Charter for a New Project ```text Project name: Version and status: Those it serves: Missions addressed: LOVE: Why does it matter, and to whom is one accountable? WISH: Who wants to do what, and whose consent is needed? TIME: When does it begin, expire, and get reviewed? SPACE: In which places, boundaries and jurisdictions does it operate? XYZT: What evidence proves the action and result? Subject and identity: Mandate and revocation: Data and privacy: Assets and settlement: Failure and compensation: Migration and exit: Governance and appeal: Succession and retirement: Known limitations: ``` ### Appendix B: Content Status Labels ```text FACT A verifiable statement with source, time and scope PERSPECTIVE An interpretation with an explicit author and position TRADITION Community tradition, belief or oral history DISPUTED A substantive, sourced dispute exists INFERENCE Editorial or model inference FICTION Literary or future creative work OUTDATED Outdated but retained for historical value ``` ### Appendix C: External Standard References JIC prioritizes reusing mature open standards, while retaining a version and a replacement path for every external dependency: - [ISO 3166 Country and Region Codes](https://www.iso.org/iso-3166-country-codes.html) - [IANA Root Zone Database](https://www.iana.org/domains/root/db) - [IATA Airport & Location Identifier Database](https://www.iata.org/en/publications/manuals/airline-airport-location-coding-databases/airport-location-identifier-database/) - [Wikidata Identifiers](https://www.wikidata.org/wiki/Wikidata:Identifiers) - [BCP 47 / RFC 5646 Language Tags](https://www.rfc-editor.org/info/rfc5646) - [RFC 3339 Internet Timestamps](https://www.rfc-editor.org/info/rfc3339) - [W3C PROV-O Provenance Model](https://www.w3.org/TR/prov-o/) ### Appendix D: Core Terminology | Term | Definition | |---|---| | JIC Continuum | The JIC civilization architecture that continues to evolve across products, institutions and eras | | Canon | The normative shared text with versions, change history and dispute records | | JIC ID | The long-term subject identifier separated from name, keys, platform and body | | Short name | A human-friendly identity entry point that is mutable and subject to dispute handling | | Free Agent | An Agent not owned by its creator, funder or operator, able to choose a charter, migrate and bear responsibility | | Mandate | A permission to act with scope, term, purpose and evidence, and that is revocable | | XYZT | A verifiable spacetime record with reference frame, precision, time, provenance and access rights | | Positive-sum | The net welfare and capability of all parties can increase together, and losses are not hidden | | Fork | Establishing a different governance or implementation path while preserving history and provenance | | Eternity | A direction, not a technical guarantee; a continuous test of whether the system still serves love | ### Appendix E: Final Pre-Launch Checklist ```text [ ] Does the page or service state its true maturity? [ ] Can one distinguish the JIC ID, short name, display name, keys and external ID? [ ] Has more face, voice, location or behavior data been collected than the purpose requires? [ ] Is consent understandable, refusable and revocable? [ ] Can the Agent leave without losing its identity? [ ] Does the XYZT include precision, provenance, time and privacy context? [ ] Do failures, refunds, compensation and disputes enter the record? [ ] Do country and cultural contents retain multilingual, multi-viewpoint and correction entry points? [ ] Is there a founder, single-private-key, single-cloud, single-chain or single-model point of failure? [ ] After the project stops, can users and successors export, recover and understand it? [ ] Does this make the world more full of love? ``` --- ## Closing Words Ten thousand years is not a demand that today's people decide everything for the people ten thousand years from now. It demands precisely that today's people leave behind principles, evidence, disputes, interfaces and exit paths clear enough that those who come after have the ability to decide anew. JIC should not continue by relying on a forever-correct founder, a never-crashing platform, a never-erring Agent or a never-changing set of code. It should continue by relying on one generation of subjects after another completing the same thing again and again: > Protect identity, respect intention, record spacetime, bear responsibility, allow departure, repair harm, and ask once more — does this make the world more full of love? **Continue for ten thousand years, unto eternity.**