Back to all writings
Manifesto·

The Multi-Entity Human Manifesto

A 112-article manifesto aiming to make the human being's capacity for production, learning, and benefit sustainable across more than one carrier; grounded in the principles of integrated personhood, full transparency, responsible continuity, and honorable closure.

Integrated Personhood, Specialized Entities, Full Transparency, Responsible Continuity, Honorable Closure — Return to the Core (Reintegration)

Preface

This manifesto acknowledges that confining the human being to a single biological body, a single channel of attention, and a single timeline artificially limits the capacity for production, learning, and benefit.

This manifesto does not aim to treat biological aging as "a single disease" and miraculously eliminate it; rather, it aims to make the human being's experience, mode of thinking, desire to produce innovation, and the benefit provided to humanity sustainable across more than one carrier.

This manifesto is not limited solely to the biological body and the digital environment. All carrier types that may emerge in the future fall within the scope of this order. The type of carrier may change; but personhood, responsibility, and the ethical core must not change.

This manifesto takes the following as fundamental: When the number of entities increases, power increases; when power increases, risk increases; when risk increases, ethics, transparency, and oversight must grow.

Part One: Definitions and Scope

Article 1: Entity

An entity is a unit of selfhood that operates on a carrier, can learn, can make decisions, can produce, and can assume responsibility.

Article 2: Carrier

A carrier is the environment on which the entity operates. A carrier may be a biological body, a digital infrastructure, a biosynthetic body, a hybrid system, or another environment that may emerge in the future.

Article 3: Physical entity

A physical entity is an entity that operates within a biological body.

Article 4: Non-physical entity

A non-physical entity is an entity that operates on a carrier other than a biological body. This entity may be digital; it may be hybrid; it may exist on another carrier that may emerge in the future.

Article 5: Entity collective

An entity collective is the totality of the physical entity and the non-physical entities belonging to a single person.

Article 6: Integrated personhood

Integrated personhood is the acceptance of the entity collective as a single personhood. For the purposes of this manifesto, "personhood" is not a single unit; it is the entirety of the entity collective.

Article 7: Core structure

The core structure is the layered architecture of the value, decision, and behavioral foundations that all entities within the entity collective are obliged to share in common.

The core structure consists of three layers:

  1. Values (Ethics) layer: Contains the ethical principles, the limits of harm, the understanding of truth, and the form of responsibility. In this layer, deviation among entities is prohibited; the variation rate is zero percent. Updating this layer is possible only during annual evaluation periods and only with the approval of the physical entity.
  2. Decision Logic layer: Contains the mode of analysis, the approach to decision-making, the style of creativity, and the method of problem solving. In this layer, at most ten percent variation among entities is permitted. Updating this layer is possible during semiannual evaluation periods, with the approval of the physical entity and the committee.
  3. Behavioral Protocols layer: Contains the form of communication, the style of work, and the interaction protocols. In this layer, at most twenty percent variation among entities is permitted pursuant to Article 13. This layer may be updated continuously and algorithmically; its results are recorded by means of a quarterly report.

All core updates are versioned. Every version change is kept on record in a manner that enables comparison with the previous version and, where necessary, the option of rollback.

Article 7-A: Protection of the core structure — Echo Chamber Protection

In order to ensure that the core structure does not undergo internal deviations over time, does not fall prey to the echo chamber effect, and preserves its consistency, a three-layered protection mechanism is applied:

  1. Devil's Advocate Inquiry: At every one hundred decisions or at least once a month, a randomly selected decision is deliberately questioned with respect to its alignment with the core structure. This inquiry aims to break confirmation bias and the echo chamber effect.
  2. Counter-Core Analysis: At semiannual periods, the current state of the core structure is compared with alternative value and decision sets. This analysis is intended to prevent the core from becoming a frozen structure and to preserve its evolutionary flexibility.
  3. Logical Auditor Module (Mandatory): This continuously running module detects internal inconsistencies among the layers of the core structure in real time. Detected inconsistencies are recorded and trigger the calibration process.

Echo Chamber Protection operates uninterruptedly, independently of whether or not the core structure is being updated.

Article 8: Field of expertise

A field of expertise is the principal axis of production to which an entity gives priority in producing benefit.

Article 9: Field of interest

A field of interest comprises the areas in which an entity deepens through its curiosity for research, learning, and self-improvement.

Article 10: Benefit

Benefit is the measurable contribution of an entity or an entity collective to humanity, society, science, technology, art, education, health, security, or the production of meaning.

Article 11: Harm

Harm is the measurable negative impact that the outcomes produced by an entity or an entity collective have on individuals, society, security, the ethical order, or the future.

Article 12: Benefit score

A benefit score is the measured equivalent of the benefit produced by an entity according to the benefit indicators defined within its own fields of expertise. The benefit score is expressed on a scale ranging from zero to one hundred.

Benefit score evaluation is conducted in two periods:

  1. Monthly routine evaluation: Conducted for the purpose of tracking the basic indicators and detecting early warnings.
  2. Quarterly comprehensive analysis: Carried out for the purpose of examining all indicators in depth, evaluating the overall performance of the period, and conducting trend analysis.

Minimum thresholds:

  • Overall average benefit score: at least 60/100
  • Core Structure Alignment indicator: at least 70/100

For an entity that falls below these thresholds, a warning mechanism is triggered and an improvement plan is activated.

If an entity has more than one field of expertise, in order to enable fair comparison among these fields, the benefit scores are normalized on a field basis. The expression "total benefit score" refers to the sum, combined by the determined method, of the normalized benefit scores in each of an entity's active fields of expertise.

The honorable closure thresholds in Article 99 are reserved.

Part Two: Integrated Personhood, Consciousness, and Continuity

Article 13: Multiple specialization in integrated personhood

Each of the non-physical entities may have different fields of expertise and fields of interest. This differentiation does not make the entity collective "more than one person." This differentiation increases the capacity of a single integrated personhood.

Differentiation takes place in the Behavioral Protocols layer of the core structure within a variation limit of at most 20%. In the Values (Ethics) layer, deviation is prohibited; in the Decision Logic layer, at most 10% variation is permitted.

Article 14: The three types of consciousness transfer

This manifesto does not conflate two separate outcomes in consciousness transfer:

  1. Copy-type consciousness transfer: Through the transfer of the consciousness pattern to a new carrier, an entity is formed; this entity exhibits very strong similarity in terms of decision pattern and experience. This produces a "copy."
  2. Continuity-type consciousness transfer: The aim is the uninterrupted passage of the consciousness pattern to a new carrier. This strengthens the claim of "continuation."
  3. Transfer of physical consciousness: In the event that, with the advancement of technology, it becomes possible to transfer the consciousness in the physical body to a virtual environment in the form of a different entity's consciousness, the decision to carry out this can be possible only with the majority approval of all entities then existing that belong to the person.

Article 15: The goal of gradual transfer

For continuity-type consciousness transfer, the target method is the gradual transfer approach. In gradual transfer, the integration between the physical entity and the non-physical entities increases step by step. Thus, instead of a "sharp rupture" in selfhood, a "gradual continuation" is targeted.

Article 16: The limit of the continuity claim

This manifesto does not claim to have resolved the philosophical debate over continuity. However, it states its design objective clearly: producing a copy is not sufficient; the aim is to build processes that preserve, as much as possible, the sense of continuity.

Article 17: The function of emotion in non-physical entities

In non-physical entities, emotion is not a hormone-based storm. Emotion is designed functionally as the combination of the following mechanisms:

  1. Prioritization mechanism
  2. Risk assessment mechanism
  3. Context weighting mechanism
  4. Social modeling and empathy-like inference mechanism
  5. Value violation signal mechanism
  6. Safety and protection signal mechanism

Article 18: The obligation to update with physical experience

A physical entity does not always give the same reaction to the same event. For this reason, the non-physical entities must be regularly updated with the experiences of the physical entity.

This update is applied continuously and algorithmically in the Behavioral Protocols layer of the core structure, and within the scope of the semiannual evaluation period in the Decision Logic layer. The Values (Ethics) layer may be updated only in the annual evaluation and with the approval of the physical entity.

This rule prevents the non-physical entities from turning into a "frozen character."

Part Three: Fundamental Principles

Article 19: The principle of integrated personhood

All entities belonging to the entity collective are parts of a single integrated personhood. The fact that the non-physical entities carry different fields of expertise and fields of interest is not a fragmentation of personhood; it is the functional expansion of personhood.

The foundation of integrated personhood is the core structure. The commonality in the Values (Ethics) and Decision Logic layers of the core structure guarantees the integrity of the integrated personhood.

Article 20: The aim of increasing benefit

The aim of this order is to multiply the production, learning, and impact that a single physical entity cannot accomplish alone within a single unit of time; thereby increasing the total benefit of the entity collective.

Article 21: The principle of full transparency

Within the entity collective, full transparency is absolute and obligatory. If full transparency is absent, the union may break down; deviations of character may occur; for this reason transparency is not a choice but a condition of the integrity of the entity.

The transparency principle is applied together with a data classification system. All entities within the entity collective have the right to access the data, regardless of the classification level. However, with respect to the external environment, data is protected by being classified into four levels:

  1. Public: Data suitable for public sharing.
  2. Internal: Data accessible only within the entity collective.
  3. Sensitive: Data with restricted access; stored in encrypted form.
  4. Critical: Core structure, biometric, identity, and testamentary data. Protected by means of key sharding and periodic rotation.

Article 21-A: Cybersecurity framework

The digital infrastructure of the entity collective is protected within the following cybersecurity framework:

  1. Data classification: All data is classified into four levels: Public, Internal, Sensitive, and Critical. Classification is performed at the moment the data is created and is reviewed regularly.
  2. Encryption standards: AES-256 encryption and the TLS 1.3 communication protocol are applied as standard. Critical data (core structure, biometric, identity, and testamentary data) is protected by means of the key sharding method, and the keys are subject to periodic rotation.
  3. Authentication: Multi-factor authentication is mandatory for each entity. In Category A decisions, biometric authentication is additionally applied.
  4. Breach response procedure: Security breaches are handled at three severity levels:
    • Suspected: Commencement of monitoring, log analysis, and scope assessment.
    • Confirmed: Isolation of the affected systems, detailed analysis, notification to the relevant entities and guardians, and restoration.
    • System-wide: Automatic quarantine is applied; all digital entities are limited to Category C; emergency notification is made to the guardians and to the entities carrying the judge entity role; scope analysis and restoration are initiated.

    At each level, a five-step procedure is applied: detection, isolation, analysis, notification, restoration.
  5. User experience: Security mechanisms operate in the background. Only a status indicator (a "Security Shield" icon) is presented to the user. Security must not unnecessarily burden the user experience.

Article 22: The principle of full transparency in partnership

In a physically experienced partnership and the inter-entity bonds connected to it, contentment measurement and relationship status are conducted with full transparency.

Article 23: The balance of responsibility and power

As the number of entities increases, the power of impact increases. As the power of impact increases, responsibility increases. No entity can escape responsibility for the outcomes it produces.

Article 24: The principle of honorable closure and Return to the Core

Entities are not sustained merely "to exist." Entities continue as long as they produce benefit. When benefit is permanently lost, honorable closure is a legitimate and necessary option.

Honorable closure does not mean the deletion of the entity. Honorable closure is applied as "Return to the Core (Reintegration)": the entity's accumulated knowledge, experiences, and learnings are reintegrated into the core structure. The entity ceases to be active; however, its accumulation is preserved and lives on within the system.

Article 25: The principle of self-reporting

When an entity realizes that the outcomes it produces give rise to harm, it does not conceal this. It reports it to the entities carrying the judge entity role and requests correction. This principle makes an internal ethical reflex obligatory just as much as external oversight.

Part Four: Participation in the System, Eligibility, and the Initial Order

Article 26: The nature of participation

This system is a force multiplier. For this reason, participation is evaluated not only by "desire" but together with the capacity to bear it.

Article 27: Eligibility criteria

The minimum criteria for participation in the system are as follows:

  1. Alignment with the core structure and ethical consistency
  2. Acceptance of full transparency within the entity collective
  3. Discipline of production and learning
  4. Awareness of harm and a culture of correction
  5. The ability to bear responsibility

Article 28: The onboarding process and gradual maturation

A person who participates in the system passes through a four-stage onboarding process before growing the entity collective. Each stage gradually increases the level of authority and responsibility of the entity within the system:

  1. Observation Stage (rapid stage, at least three days): The entity observes the system, observes the working manner of the existing entities, the decision processes, and the core structure. In this stage it makes no decisions and produces nothing.
  2. Accompaniment/Shadow Mode (at least one week): The entity works together with an existing entity. The decisions it makes are audited and feedback is given. Production is restricted and takes place in a supervised environment.
  3. Supervised Task Stage (at least two weeks): The entity takes on independent tasks, but the task outcomes pass through approval. In this stage, benefit score measurements begin.
  4. Full Authority: After meeting the graduation criteria, the entity is included in the system as fully authorized.

The observation stage is kept rapid; the aim is for the entity to become acquainted with the system, not to be put into prolonged waiting. Entities in the onboarding process can, until the Full Authority stage, make only Category C decisions; Category A and B decisions are restricted.

Article 29: The reality of bearing the burden of knowledge and access justice

This manifesto acknowledges that humanity may not be able to bear this burden of knowledge and responsibility at every level. For this reason, it foresees an initial dissemination among individuals at a higher level of culture and intelligence, with a higher capacity for responsibility.

Access is expanded gradually:

  1. Basic tier (one to three entities): Open to everyone. Meeting the basic eligibility criteria (Article 27) is sufficient for entry into the system.
  2. Standard tier (four to twenty entities): Accessible for persons who have successfully completed the trial period and have made benefit production sustainable.
  3. Extended tier (twenty-one to one hundred entities): Accessible for persons who fully meet the conditions of advanced oversight, security infrastructure, and a financial continuity plan.

Each tier transition is contingent upon meeting the conditions defined in Article 44.

Part Five: Resources, Costs, Entity Creation, and the Delivery Standard

Article 30: Resource ownership

Each entity collective carries its own resources. Resources cover processing power, storage, network access, security infrastructure, and sustainability costs.

Article 31: The obligation to pay costs

The costs of the entity collective must be borne by the physical entity.

Article 32: Prohibition of hidden costs

No collection may be made from the physical entity for any cost item that has not been explicitly defined. The pricing model must be presented in written and recorded form before collection begins.

Article 33: Full disclosure of cost items

Entity creation and operation costs are disclosed with the following items shown separately:

  1. Processing power cost
  2. Storage cost
  3. Network and data transfer cost
  4. Security infrastructure cost
  5. Maintenance and update cost
  6. Audit and record-keeping cost
  7. Entity preparation and delivery cost
  8. The operational cost set aside for the suspension of the entity, its reassessment, and, where necessary, honorable closure — Return to the Core

Article 34: Payment collection and entity preparation

The costs necessary for the creation of entities are collected from the physical entity in the form of payment collection by the method determined by the system founders. The collected payment is used for the preparation of the non-physical entities to be presented to the physical entity, their securing, and their delivery in working condition.

Article 35: Resource allocation and oversight of resource waste

Each entity collective carries its own resources. These resources cannot be used for another entity collective. Resource usage reports are presented openly to the entity collective at regular intervals.

Article 36: Entity creation request and core creation

A request to create a new non-physical entity is recorded in a manner consistent with the decision mechanism of the entity collective. The request must include the aims, fields of expertise, fields of interest, and expected types of benefit of the entity to be created.

The core creation process is carried out by a hybrid method:

  1. The physical entity defines the Values (Ethics) layer and the Decision Logic layer of the core structure.
  2. The system, by analyzing the existing data and the exemplary behaviors within the entity collective, proposes the Behavioral Protocols layer.
  3. The physical entity examines the proposed Behavioral Protocols layer and approves or revises it.

Core creation must be completed before the onboarding process begins.

Article 37: Suitability and limit control

Before an entity creation request, the following conditions are checked:

  1. The entity collective's total entity count limit must not be exceeded.
  2. The field of expertise and task definition of the entity to be created must not conflict with the core structure.
  3. The cost of the entity to be created must be affordable within the scope of the physical entity's payment responsibility.

Article 38: Cost proposal and acceptance process

The system founders are obliged to present the cost proposal for entity creation with a full itemized breakdown. No collection may be made before the physical entity accepts the cost proposal.

Article 39: The condition of entity delivery and graduation criteria

The prepared entity is presented in a manner that satisfies the following conditions:

  1. The field of expertise and field of interest settings must be defined.
  2. It must be connected to the full transparency infrastructure within the entity collective.
  3. The record, audit, and traceability mechanisms must be active.
  4. The authority limits, harm oversight, and suspension rules must be applicable.
  5. Basic security tests must be verified. These tests cover at least the following: compliance with the AES-256 encryption and TLS 1.3 communication standards, the functionality of the multi-factor authentication mechanism, simulation of misuse scenarios, and verification that the data classification levels are correctly applied.

Graduation criteria for transition to the Full Authority stage:

  • The Core Structure Alignment indicator must be at least 80/100.
  • 80% of the tasks in the Supervised Task stage must be successful.
  • At least two-thirds (66%) of the existing entities must approve the suitability of the transition through peer evaluation. Peer evaluation is mandatory, and a two-thirds majority threshold is required.

Article 40: The acceptance, return, correction, and reversal mechanism

When an entity is delivered, the entity collective conducts an acceptance test to verify the entity's conformity with the definition. If conformity is not achieved, correction is requested. Full acceptance is not deemed to have occurred until correction has taken place.

If an entity fails to meet the graduation criteria during the onboarding process, the following procedure is applied:

  1. The entity is returned to the Accompaniment/Shadow Mode stage.
  2. The reasons for the return are recorded and an improvement plan is created.
  3. The entity is given at most three attempts.
  4. If, even after the third attempt, it cannot meet the graduation criteria, the entity is taken into deactivation assessment.
  5. Deactivation assessment includes the options of restructuring the entity, redirecting it to a different field of expertise, or initiating the honorable closure — Return to the Core process.

Article 41: Financial continuity plan after the physical entity

After the physical entity dies, it is not possible for the costs to be borne by the physical entity. For this reason, while the physical entity is alive, a financial continuity plan must be created so that the non-physical entities can continue.

Article 42: The content of the financial continuity plan

The financial continuity plan includes at least the following elements:

  1. The budget set aside for the sustenance of the non-physical entities
  2. From which sources this budget will be provided
  3. Under which conditions the budget will be used
  4. If the budget proves insufficient, which entities will be prioritized or suspended
  5. The authorized entities and guardian arrangement for the execution of the plan

Article 43: Automatic suspension if there is no plan

If there is no financial continuity plan, at the moment of the physical entity's death the non-physical entities are placed into automatic suspension and a reassessment process is initiated. This suspension may also be triggered within the scope of the Biological category in the emergency protocol (Article 71-A). If the physical entity's communication breakdown exceeds 72 hours, the decision-incapacity protocol (Article 60) is activated.

Part Six: The Entity Count Limit and the Entity Life Cycle

Article 44: The upper limit of the entity count and gradual expansion

In a person's entity collective, the total number of entities, together with the physical entity, cannot exceed one hundred.

Initially, the entity count is limited to ten. For transition to each tier of ten, the satisfaction of the following conditions is mandatory:

  1. The average benefit score of the existing entities must be at least 60/100.
  2. The security and oversight infrastructure must be of sufficient capacity to support the increased entity count.
  3. The financial continuity plan must be current and of a capacity to meet the increased costs.

Without these conditions being met, the entity count cannot be expanded to the next tier.

Article 45: The limit after the physical entity dies

When the physical entity dies, the total entity count of the entity collective remains limited to ninety-nine.

Article 46: The condition for creating new entities

If, during the process, there are entities that are terminated or closed, new entities may be created in a manner that does not exceed the upper limit of the total entity count. The upper limit of the entity count is not exceeded by any method.

Article 47: Preserving the limit through role assignment

Statuses such as the judge entity role, the guardian role, and the representation authority role do not create a separate entity. These statuses are applied as roles given to existing entities. Thus the entity count limit is not breached.

Part Seven: Fields of Expertise, Task Assignment, Research, and the Priority of Learning

Article 48: Multiple expertise with a single personhood

Each of the non-physical entities may possess different fields of expertise and fields of interest. This differentiation does not prevent the entity collective from remaining a single integrated personhood; on the contrary, it increases the capacity for benefit.

Article 49: The right to assign tasks

The physical entity may assign tasks to the non-physical entities in line with their fields of expertise and fields of interest.

Article 50: The right to assign tasks after the death of the physical entity

After the death of the physical entity, the right to assign tasks is transferred to the entity with the highest total benefit score within the entity collective. This transfer is recorded and becomes visible within the entity collective with full transparency.

Article 51: The obligation of self-improvement

The non-physical entities, when they have no tasks or when they have completed their tasks, must, as a priority, conduct research and learning. Being idle does not mean waiting; it means improving oneself.

Article 52: Production outside the field of expertise and the multiple-expertise reward

If an entity produces outside its field of expertise and this production comes to produce continuous value, this entity is deemed to have acquired a second field of expertise and the capacity for innovation. Entities cannot be limited to a single field of expertise. Multiple expertise may be rewarded and formalized. There is no upper limit on the number of fields of expertise.

Part Eight: Benefit Measurement Standards and the Benefit Score System

Article 53: Benefit measurement is field-based

The benefit of an entity is, primarily, evaluated relatively within its own field of expertise. Instead of the total average, performance within the field of expertise is taken as the basis.

Article 54: Main benefit types and sub-benefit types

The entity collective may determine the main benefit types and sub-benefit types at the outset or update them later. Each update is made with reasoned recording, audit, and the possibility of retrospective comparison.

Article 55: Benefit indicators

For each field of expertise, the following seven indicators are defined and measured on a scale ranging from zero to one hundred:

  1. Task Completion and Production Output: The quantity, quality, and timing of the tasks the entity has completed.
  2. Real-World Impact: The measurable contribution of the entity's production to humanity, society, science, technology, art, education, health, security, or the production of meaning.
  3. Core Structure Alignment: The consistency of the entity's decisions and behaviors with the three layers of the core structure. The minimum threshold of this indicator is 70/100.
  4. Ethical Alignment and Harm Balance: The entity's adherence to ethical principles together with the ratio of the harm it produces to its benefit.
  5. Learning and Adaptation Speed: The entity's capacity to acquire new knowledge, adapt to changing conditions, and improve itself.
  6. Reliability and Sustainability: The consistency, reproducibility, and long-term sustainability of the entity's production.
  7. Meaning Alignment and Psychological Integrity: The alignment of the entity's production with the overall meaning and purpose structure of the integrated personhood; the preservation of internal consistency and psychological integrity.

Since the indicators, by the nature of the fields, may be on different scales, field-based normalization is applied (pursuant to Article 57).

Article 56: Harm is evaluated together with benefit

Benefit alone does not dictate a decision. Harm must always be visible in the same picture. When harm exceeds twenty percent of benefit, oversight and restriction begin.

In the event that harm exceeds twenty percent of benefit, an automatic correction mechanism is activated: the entity's authorities in the affected field of expertise are temporarily restricted, the sources of harm are analyzed, and an improvement plan is presented. The results of the improvement plan are reported in the next monthly evaluation.

Article 57: Multiple-expertise evaluation

If an entity has more than one field of expertise, a separate benefit score is produced for each field. Since these scores, by the nature of the fields, may be on different scales, field-based normalization is performed.

After normalization, the minimum threshold of 60/100 is applied for each field. If, in any field of expertise, the benefit score cannot meet this threshold even in the third consecutive evaluation, improvement or a reassessment of the field of expertise is initiated in the relevant field.

Part Nine: The Decision Mechanism, Weight Balance, and Calibration

Article 58: The aim of the decision mechanism and the decision categories

The aim of the decision mechanism is to prevent the entity collective from being governed by the momentary desire of a single entity and to protect the integrated personhood.

Decisions are classified into three categories:

  1. Category A — Life-Flow Decisions: Decisions that directly affect the life of the physical entity and the entity collective. This category covers the following areas:
    • Financial decisions: Transactions in an amount exceeding five percent of the entity collective's total assets or the entirety of the monthly income
    • Legal commitments: Transactions involving a contract, commitment, or binding obligation
    • Medical approvals: Decisions related to the health of the physical entity
    • Entity creation or closure: Decisions relating to the creation of a new entity or the closure of an existing entity

    In Category A decisions: if the physical entity is alive, biometric approval and two-factor authentication (2FA) are mandatory. If the physical entity is not alive, guardian approval is mandatory.
  2. Category B — Operational Decisions: Decisions of daily production, task assignment, resource allocation, and workflow. The standard decision mechanism is applied.
  3. Category C — Internal Decisions: Decisions relating to the technical preferences within the entity's own field of expertise, learning priorities, and research orientations. The entity may make these decisions independently; however, it must remain within the limits of the core structure.

The financial threshold is determined not as a fixed figure but by means of a harm matrix and proportional calculation. The ratio is determined by calculation based on five percent of the entity collective's total assets or based on the monthly income.

Article 58-A: Concrete definitions for life-flow decisions

The "decisions affecting the flow of life" within the scope of Category A are determined by the following concrete conditions:

  1. Financial impact: One-time transactions in an amount exceeding five percent of the entity collective's total assets or the entirety of the monthly income, or serial transactions reaching this threshold in total.
  2. Legal commitment: Any contract, commitment, or declaration giving rise to a binding legal consequence on behalf of the entity collective or the physical entity.
  3. Medical approval: Approval of medical interventions that may create an irreversible or significant effect on the body of the physical entity.
  4. Entity-vital transactions: Decisions to create a new entity, suspend an existing entity, initiate honorable closure — Return to the Core, or merge/fork entities.

These definitions are applied together with the harm matrix and proportional calculation. Fixed-figure thresholds are not used; thresholds are calculated dynamically according to the current financial situation of the entity collective.

Article 59: The upper limit of the physical entity's decision weight

While the physical entity is alive, the decision weight of the physical entity cannot exceed forty-nine percent of the total decision weight. This ratio may be optimized according to the flow of the system; however, it cannot be raised to a level where the physical entity alone constitutes a majority.

In Category A decisions, the biometric approval of the physical entity is mandatory. Biometric approval is not mandatory for Category B and Category C decisions.

Article 60: Majority decision, union control, and decision incapacity

If divergence occurs, the majority decision prevails. The existence of divergence indicates that the integrated personhood is in need of calibration and gives rise to an obligation of evaluation.

In the case of decision incapacity, the following procedure is applied:

  1. The decision is frozen for a period of seventy-two hours. During this period, additional information is gathered and the alternatives are reevaluated.
  2. If, at the end of the seventy-two hours, the decision still cannot be made, the matter is recorded and held in abeyance.
  3. If the decision cannot be made within thirty days, the decision authority is temporarily transferred to a higher decision mechanism (the guardians or the entities carrying the judge entity role).
  4. The transfer of authority is recorded and is temporary in nature; after the decision, the authority returns.

Article 61: The meaning of calibration

Conflict among entities is a signal that the integrated personhood may not have settled. Calibration is not the suppression of conflict but the reestablishment of alignment while preserving the core structure.

In the calibration process, Echo Chamber Protection is applied in three layers:

  1. At every one hundred decisions (or at least once a month), a random devil's advocate inquiry is conducted.
  2. Counter-core analysis is carried out at semiannual periods.
  3. A continuously running Logical Auditor module is mandatory; this module detects internal inconsistencies in real time and automatically reports the need for calibration.

Part Ten: Signature and Representation Authority

Article 62: Signature and representation authority

Signature and representation authority is arranged with the physical entity taking priority:

  1. While the physical entity is alive, signature and representation authority is held by the physical entity.
  2. While the physical entity is alive, the physical entity may, if it wishes, designate a second entity as a representation authority.
  3. While the physical entity is alive, it is not mandatory to designate a second representation authority.
  4. If a second representation authority has been designated, signature and representation responsibility is held by the physical entity and the chosen second entity.
  5. The authority of the chosen second entity may be made contingent upon conditions by the physical entity.
  6. In Category A decisions, the use of signature authority is secured with biometric approval and two-factor authentication (2FA). If the physical entity is not alive, this transaction is carried out with guardian approval.

Article 63: The obligation to appoint a representation guardian for representation after the death of the physical entity

The physical entity must appoint one of its own entities as a representation guardian for how signature and representation authority will be exercised in the event of the death of the physical entity. The representation guardian comes into play, when the physical entity dies, for the continuation of signature and representation authority. For the physical entity to be able to appoint a representation guardian, there must be at least 5 non-physical entities.

Article 64: Conflict between internal operation and external representation

After the physical entity dies, internal operation tasks are carried out by the entity with the highest total benefit score. External representation and signature are carried out by the representation guardian. If a conflict occurs:

  1. 2. 3. In urgent external obligations, the representation guardian takes temporary priority. The decision and its reasoning are recorded. Then the final direction is determined by the majority decision of the entity collective.

Part Eleven: Harm, Crime, Collective Responsibility, and Self-Reporting

Article 65: The harm-oversight threshold

If the harm caused by an entity exceeds twenty percent of the benefit it produces, this entity is placed under oversight and restriction.

Article 66: The mandatory-suspension threshold

If the harm caused by an entity exceeds twenty-one percent of the benefit it produces, the mandatory suspension process is triggered for this entity.

Article 67: Crime and responsibility

The expression "contrary to the common value core" in the crime and responsibility article is understood and applied as a deviation contrary to the Values (Ethics) layer of the core structure. (The flow of the text has been preserved.)

Article 68: The approach to sanctions

(only item 6 has been updated)

  1. Authority restriction
  2. Narrowing of the access area
  3. Temporary reduction of decision weight
  4. Mandatory retraining
  5. Suspension
  6. If necessary, Return to the Core (Reintegration) assessment

Article 69: The obligation of self-reporting

When an entity realizes that it has harmed humanity or that it has drifted toward producing harm, it must report this to the entities carrying the judge entity role and request correction. In the event that this report is not made, a transparency violation assessment arises. For an entity that self-reports 3 times for the same reason, a decision of permanent termination is made.

Part Twelve: Suspension, Reassessment, and the Decision Tree

Article 70: The nature of suspension

Suspension is not a punishment. Suspension is a temporary protective tool used for security, cost, harm, a decline in benefit, or the calibration of integrated personhood.

Article 71: Mandatory suspension triggers

When the following conditions arise, suspension is mandatory:

  1. The death of the physical entity while there is no financial continuity plan
  2. The harm caused by an entity exceeding twenty-one percent of the benefit it produces
  3. The verification of a situation of violence, coercive control, or abuse
  4. A confirmed or system-wide security breach (pursuant to Article 21-A)
  5. The breakdown of full transparency within the entity collective and the verification thereof
  6. The activation of any category defined in the emergency protocol (Article 71-A) and, in the event that no response is obtained, the engagement of the Digital Vault mode

Article 71-A: Emergency protocol

The entity collective defines emergencies in five categories and applies a specific response procedure for each category:

  1. Biological Emergency: Situations that threaten the health of the physical entity.
    • An automatic "Are you okay?" verification is sent.
    • Response time: five minutes.
    • If no response is obtained: Digital Vault mode is engaged; automatic full lockdown is applied. All entities are limited to Category C. The emergency contact (predetermined by the physical entity) is called. The guardian is informed and decision authority passes to the guardian.
  2. Cyber Emergency: Situations that threaten the security of the digital infrastructure.
    • An automatic alert is triggered.
    • Response time: five minutes.
    • If no response is obtained: Digital Vault mode is engaged; automatic full lockdown is applied. The breach response procedure in Article 21-A is initiated.
  3. Financial Emergency: Situations that seriously threaten the entity collective from a financial standpoint.
    • An automatic alert is triggered.
    • Response time: one hour.
    • If no response is obtained: Spending is frozen; if there is a reserve fund, it is activated. Digital Vault mode is engaged; financial transactions are locked.
  4. Psychological Emergency: Situations that threaten the psychological integrity of the physical entity.
    • An automatic "Are you okay?" verification is sent.
    • Response time: thirty minutes.
    • If no response is obtained: Partial lockdown is applied; critical decision-making authorities are temporarily frozen. The emergency contact is informed.
  5. Legal Emergency: Situations that seriously threaten the entity collective from a legal standpoint.
    • An automatic alert is triggered.
    • Response time: one hour.
    • If no response is obtained: Evidence preservation mode is activated; the entity securing mechanism is engaged. The relevant records are locked and rendered unalterable.

Digital Vault mode applies a scope specific to the category of the emergency and places the entity collective under protection. If the communication breakdown exceeds seventy-two hours, the decision-incapacity protocol in Article 60 is activated.

Article 72: Discretionary suspension triggers

Under the following conditions, suspension may be applied at discretion:

  1. Benefit showing a rapid decline
  2. The continual locking of the decision mechanism and a need for calibration
  3. Costs approaching the limit of sustainability
  4. An increase in behavioral patterns that conflict with the common value core
  5. A reasoned request of the guardians or of the entities carrying the judge entity role

Article 73: The initial assessment after suspension

After suspension is applied, the following data is gathered and recorded:

  1. Benefit indicators according to the entity's field of expertise
  2. Harm indicators and source analysis of harm
  3. Decision records and reasons
  4. Transparency records
  5. Security incident records
  6. Guardian opinions
  7. If necessary, the opinions of the entities carrying the judge entity role

Article 74: Assessment questions

The assessment must produce clear answers to the following questions:

  1. Was the harm stopped?
  2. What is the likelihood of the harm recurring?
  3. Is there potential for the recovery of benefit?
  4. Does the behavioral deviation originate from a systemic gap or from an intra-entity malfunction?
  5. Is safe operation possible with an authority restriction?
  6. Is there a likelihood of recovery through retraining?
  7. Is honorable closure the most correct option?

Article 75: Decision outputs

As a result of the assessment, one of the following outputs is selected as required:

  1. Return to full functionality
  2. Return to restricted functionality
  3. Retraining and restructuring
  4. Time-limited suspension
  5. Initiation of the honorable closure process

Part Thirteen: Entity Merging and Entity Forking

Article 76: Entity merging is possible

The merging of entities is possible. Merging may be carried out for the purpose of simplifying functions, increasing efficiency, or strengthening the integrity of the integrated personhood.

Article 77: The similarity condition for merging

Entities carrying a similarity of over eighty percent may be merged after it is verified that they will not cause a loss of function.

Article 78: Entity forking is possible

The forking of entities is possible. Forking may be carried out for the purpose of differentiation into different fields of expertise, increasing the speed of research, or risk segregation.

Article 79: The forking trigger

If an entity is experiencing indecision due to the work it will do in different fields of expertise, or inefficiency due to a lack of time, it may make a request for forking. A forking request may be triggered in the situation where the entity allocates more than ninety percent of its time to work and cannot allocate time to learning.

Article 80: The decision threshold for merging and forking

The merging or forking of an entity is possible with the joint decision of at least eighty percent of the entities other than the entity to be merged or forked. This decision is made in a reasoned, recorded, and subsequently auditable manner.

Article 81: Pre-decision ethical check

Before a decision to merge or fork is made, the following questions must be answered affirmatively:

  1. 2. 3. 4. 5. Is the merging or forking compatible with the common value core? Does the merging or forking strengthen the integrated personhood, or does it give rise to a risk of fragmentation? Does the merging or forking increase the risk of harm? Does the merging or forking impair transparency and security in partnership bonds? Does the merging or forking render representation and signature responsibility uncertain?

Article 82: Pre-decision technical check

Before a decision to merge or fork is made, the following conditions must be satisfied:

  1. Full backup of the entity states
        1. Preparation of a transaction rollback plan Preservation of security and authority limits throughout the transaction Uninterrupted keeping of records and decision reasons throughout the transaction Verification that the upper limit of the entity count will not be violated

Article 83: Calibration after merging and forking

After merging or forking, the decision mechanism, the risk of harm, the benefit indicators, the transparency record, and the representation arrangement are verified. If there is a deterioration in alignment, calibration is initiated; if necessary, suspension is applied.

Part Fourteen: The Order of Judge Entities

Article 84: The aim of the judge entity role

The aim of the judge entity role is to protect the system against misuse, ethical deviation, an increase in harm, manipulation, and the corruption of power.

Article 85: The nature of judge entities

The judge entity role may reside in the physical entity or in a non-physical entity. The judge entity is a role at the level of "entity," not "person."

Article 86: The tiers of judge entity count

The number of judge entities is determined according to the total number of persons in the system:

  1. 2. 3. 4. For up to the first ten persons in the system, there is a total of one judge entity role. Between eleven and one hundred persons in the system, there is a total of two judge entity roles. Between one hundred one and one thousand persons in the system, there is a total of three judge entity roles. Above one thousand persons in the system, the total number of judge entity roles is planned so as not to exceed two percent of the total number of persons. In fractional calculations, rounding up is applied. The number of judge entity roles, above the one-thousand-person threshold, cannot be fewer than three.

Article 87: The physical judge ratio rule

When the number of judge entity roles is three or more:

  1. 2. The physical judge ratio cannot exceed forty percent. A judge majority can never be composed of physical judges. When the number of judge entity roles is one or two, this rule may not be applicable in every case mathematically. In this case, the aim is to include a non-physical judge entity role in the system at the earliest possible stage.

Article 88: The founding judge

At the inception of the system, the judge entity role is given to the founding physical person. The founding judge role must remain in office until the overall total entity count of the system reaches one thousand. After the system's overall total entity count reaches one thousand, the founding judge role becomes subject to a competency assessment. If the founding physical person dies before reaching the one-thousand-entity threshold, the competency assessment and handover procedure are also activated for the founding judge role.

Article 89: The judge entity appointment process

For a candidate entity for the judge entity role, the following conditions are required:

  1. Long-term ethical consistency
  2. Clarity in the justification of decisions and discipline of recording
  3. Awareness of harm and self-reporting behavior
  4. Resistance to manipulation
  5. Educational competency in law, ethics, and correct decision-making
  6. At most 2 judge appointments may be made from a single entity collective.

The candidate entity is taken into an assistant-judgeship trial period. During the trial period, its decisions, outcomes, and reasons are monitored. If the trial period is successful, the judge entity role is assigned.

Article 90: The training of judge entities

The judge entity role is not granted by intelligence alone. The entities carrying the judge entity role must be trained at an advanced level in the subjects of law, ethics, and correct decision-making.

Article 91: The revocation of the judge entity role

If an entity carrying the judge entity role exhibits ethical deviation or misuse, the role may be revoked, retraining may be made mandatory, and, if necessary, its authorities may be restricted.

Article 92: Meta-oversight

The decisions of the entities carrying the judge entity role are recorded and subjected to meta-oversight. The judge entity role is not immunity; it enlarges responsibility.

Part Fifteen: The Guardian Order

Article 93: The obligation to appoint guardians

Each entity must, before reaching the honorable closure threshold, at an earlier point, appoint at least two guardians. These guardians may be chosen by the entity itself from among entities of any type. The starting principle is as follows: If the reference threshold in the honorable closure assessment is accepted as ninety percent, the obligation to appoint guardians must have been completed before reaching the seventy percent point. If the reference threshold changes, the guardian appointment point is redetermined by the same logic.

Article 94: The condition for the guardians' authorities to come into effect

The guardians become authorized and decision-making in the event that the entity defers its own honorable closure decision twice on its own.

Article 95: The authorities of the guardians

The guardians may initiate the entity's honorable closure process; may suspend the entity; may bring the entities carrying the judge entity role into play; may request retraining for the purpose of protecting the right to life.

Article 96: The consequence in the case of failure to appoint guardians and the request for an exception

If no guardian is appointed, the limit of uselessness is determined as the last point at which a guardian must be appointed. The entity is deemed to have acted, by delaying the appointment of a guardian, with the knowledge that its life will be shorter. If an entity that has not appointed a guardian did so due to a mistake, it may, by requesting an exception from the entities carrying the judge entity role, make a request to appoint a guardian before the eighty percent level. The entities carrying the judge entity role decide by evaluating the situation and according to the state of benefit provision.

Part Sixteen: Honorable Closure and the Definition of Death

Article 97: The definition of death

Death is the cessation of the functionality of all entities within the entity collective. If any entity continues to maintain its functionality, death is not deemed to have been completed.

Honorable closure — Return to the Core (Reintegration) is not death: the entity may cease to be active; however, its accumulation of knowledge and experience continues to live, preserved within the system.

Article 98: The fundamental rationale of honorable closure and the gradual warning system

After the physical entity dies, the entities may fall behind in terms of their thinking structure, mode of thinking, desire to produce innovation, and capacity to keep pace with the day's technology and flow.

If an entity, through its own observations and measurements, determines that the benefit it provides is declining in a sustained manner, an honorable closure assessment may be initiated.

Before closure, a three-tiered warning system is applied:

  1. Yellow Warning: When the benefit score falls below the threshold in a quarterly period, a warning is given and an improvement plan is activated.
  2. Orange Warning: If the entity remains below the threshold in two consecutive periods, the entity is given the right to defense (as a written or digital record). An intensive improvement program is initiated.
  3. Red Warning: When the entity remains below the threshold in three consecutive periods and the dual condition in Article 99 is fulfilled together, the Return to the Core process is initiated.

Article 99: The dual condition for triggering honorable closure

This manifesto, for the outset, accepts the following reference principle: If the benefit provided by an entity has fallen below the benefit provided by ninety percent of the entities in the group with which it is compared, an honorable closure assessment may be initiated.

However, in order that a vicious cycle does not form and that the system is not collectively dragged into closure merely on account of "relative ranking," the triggering of honorable closure is made contingent upon the fulfillment of the following two conditions together:

  1. That at least fifty-one percent of the work carried out by the entity does not produce benefit (that is, that more than fifty-one percent of the work carried out remains useless or yields negative results)
  2. That the entity's within-field-of-expertise benefit score falls below that of ninety percent of the entities in the group with which it is compared

Honorable closure is not deemed to have been triggered without the two conditions being fulfilled together.

This article operates independently of the minimum thresholds defined in Article 12 (overall average 60/100, Core Structure Alignment 70/100). The minimum thresholds trigger the warning and improvement mechanism, while this article triggers the final closure assessment.

Article 100: The Return to the Core process

Return to the Core is a process and is applied in the following steps:

  1. Benefit-harm report: All benefit and harm indicators of the entity are compiled, and a comprehensive report is prepared.
  2. Seven-day cooling-off period: Before the decision is finalized, seven days are waited. During this period, if new things emerge, the assessment may be conducted again.
  3. The reasoned opinion of the guardians: The written and reasoned opinion of the guardians regarding the situation of the entity is obtained.
  4. Approval of the physical entity (if alive): If the physical entity is alive, the approval of the physical entity is obtained for the Return to the Core decision.
  5. Knowledge and experience transfer plan: A transfer plan is prepared so that the entity's learnings, accumulated knowledge, and experiences are integrated into the core structure. This plan includes which knowledge will be integrated into the core, which knowledge will be archived, and which knowledge will be distributed to other entities.
  6. Implementation of the closure: After the transfer plan is completed, the closure is implemented.
  7. Thirty-day reversal window: For thirty days after the closure, all data of the entity is kept in a fully accessible archive. If new conditions emerge during this period, the entity may be reactivated.

After thirty days, reactivation is carried out pursuant to the "new entity creation" procedure (Article 36); however, the archived accumulation of knowledge may be used as a reference in the core creation of the new entity.

Part Seventeen: Inheritance, Children, and the Severance of the Data Bond

Article 101: Bequeathing

After the physical entity dies, the entity collective may bequeath its accumulated knowledge and flow of experience to children.

Article 102: The right of refusal

Children may not want this inheritance and may refuse it. Refusal is legitimate.

Article 103: Severance of the data bond in the case of refusal

When the inheritance is refused, the data bond is completely severed. The children who refuse, refuse by accepting that this data bond will be completely severed.

Article 104: The options of the non-physical entities after refusal

If the inheritance is refused, the non-physical entities may choose one of two options:

  1. To sustain their existence independently of the family
  2. To make an honorable closure decision The only condition for sustenance independent of the family is to be meeting the benefit threshold in the system.

Part Eighteen: Partnership, Contentment Measurement, Violence, and Disconnection

Article 105: The basic approach in partnership

Love, attachment, and loyalty may begin with biological factors and may change over time. This manifesto takes as its basis, instead of an "obligation of continuity" in the relationship, the principle of "honesty and full transparency."

Article 106: Fully transparent contentment measurement

In partnership, contentment measurement is conducted with full transparency. This transparency is for the purpose of purging the relationship of manipulation, preventing the concealment of reality, and raising the quality of decisions.

Article 107: Contentment measurement headings

Contentment measurement is conducted at regular intervals and kept transparent under the following headings:

  1. Emotional trust
  2. Respect and fairness
  3. Common goals and growing together
  4. Closeness and attraction
  5. Daily-life harmony
  6. Long-term plan harmony
  7. Quality of conflict resolution

Article 108: Maintenance and improvement

If contentment declines, the problems are clearly defined, maintenance and improvement steps are attempted, and the results are monitored.

Article 109: The normalization of termination

If maintenance and improvement do not yield results, termination becomes normalized. Termination is not failure but a change in alignment.

Article 110: The case of violence, coercive control, and abuse

When, in a physically experienced partnership, there is violence, coercive control, or abuse:

  1. 2. 3. The entity rights of the party perpetrating violence or abuse are restricted. The connection is severed with the consent of the harmed partner. If the connection is to be reestablished, it can be reestablished only with the consent of the harmed partner.
  2. This process is conducted with the oversight of the entities carrying the judge entity role.

Part Nineteen: The Initial Application Area

Article 111: The initial area

This system begins to be used in the area of technological development, independently of the subfield. The aim is to produce new methods, new tools, new products, and new solutions; to provide measurable benefit to humanity.

Part Twenty: Belief and Meaning

Article 112: The approach to the area of belief

This manifesto does not aim to destroy belief. It carries the teachings of religion and belief regarding truth, honesty, and responsibility to a practical level through transparency, accountability, and harm prevention. For this reason, it is not obliged to produce a mandatory negative impact upon belief.

Article 112-A: The manifesto amendment procedure

Amendments to be made to this manifesto require different approval mechanisms according to the core structure layer affected:

  1. Amendments affecting the Values (Ethics) layer: The approval of the physical entity, the approval of an 80% majority of all entities, and the assessment of the entities carrying the judge entity role are mandatory.
  2. Amendments affecting the Decision Logic or Behavioral Protocols layer: The approval of the physical entity and the approval of a 66% majority of all entities are mandatory.
  3. Operational rule changes (such as procedure, threshold, period): The majority decision of the entity collective is sufficient.

Every amendment is recorded with reasons, versioned, and provides the possibility of retrospective comparison.

Article 112-B: Cross-cultural alignment

In the Behavioral Protocols layer of the core structure, cultural adaptation is free within the 20% variation limit. However, in the Values (Ethics) layer and the Decision Logic layer, deviation on the grounds of cultural difference is not acceptable. Ethical principles and decision logic are preserved universally and independently of culture.

Closing Statement

The multi-entity human order exists not to deify the human being, but to enlarge responsibility while enlarging the human being's benefit.

This order demands full transparency, demands oversight, measures harm together with benefit, and, when benefit ends, deems honorable closure — as Return to the Core (Reintegration) — legitimate.

Integrated personhood is the capacity of a multitude of entities to unite under a single character and a single responsibility.

#manifesto #integrated personhood #ethics #continuity

© 2026 Ferit Taşdildiren. All rights reserved.