{
  "schema_version": "uw-systems-local-geo-v1",
  "catalog_id": "SYS-195",
  "route_id": "SYS-195",
  "language": "en",
  "revision": 1,
  "revision_status": "LOCAL_PROPOSED_NOT_SERVER_REVISION",
  "headline": "I do my part of the work — but what is it for?",
  "description": "A small digital task may leave a worker unable to see the whole result’s purpose. The article separately considers programmers, designers, operators and administrators: what each creates, communicates or confirms. Ordinary division of work is not labelled a criminal project, while limited knowledge does not erase a known action.",
  "master_filename": "ARTICLE_EN.md",
  "master_sha256": "9c83637902bf618025280bb0737d3b4f6befe7b9bdaa992edd391c640f0fad31",
  "short_answer": "Dividing digital work limits visibility of consequences. Programmers check mechanisms, designers shape messages, operators relay answers and administrators manage access within their roles; no component automatically confirms the whole purpose. Particular conduct, knowledge and authority need distinguishing while retaining pressure and real limits on choice.",
  "claims": [
    {
      "id": "C01",
      "text": "Dividing work can be ordinary and necessary; it limits visibility without erasing a known contradiction or distributing responsibility equally.",
      "status": "interpretation",
      "source_ids": [],
      "article_sections": [
        "II. Dividing work limits visibility without erasing conduct"
      ],
      "qualifiers": [
        "An unknown cannot excuse everything, and a suspected connection is not a proven contribution; no legal conclusion follows."
      ]
    },
    {
      "id": "C02",
      "text": "A mechanism meeting its specification does not establish a public promise’s truth or the whole service’s legal status; a check’s actual scope differs from a wider endorsement.",
      "status": "interpretation",
      "source_ids": [],
      "article_sections": [
        "III. Programmer: correct execution and a justified purpose"
      ],
      "qualifiers": [
        "Earlier checks do not certify new uses; a safe halt or dispute has not been established."
      ]
    },
    {
      "id": "C03",
      "text": "An understandable form includes the promise’s meaning; design differs from certifying an unknown authority, and asking who can confirm content requires no access to personal information.",
      "status": "interpretation",
      "source_ids": [],
      "article_sections": [
        "IV. Designer: an understandable form and the grounds for trust"
      ],
      "qualifiers": [
        "Designers may have limited influence; a professional question guarantees no calm response."
      ]
    },
    {
      "id": "C04",
      "text": "Reading approved wording differs from authorship, but the recipient receives a message in either case; its known content, knowledge and pressure on the speaker matter.",
      "status": "interpretation",
      "source_ids": [],
      "article_sections": [
        "V. Operator: a prepared script still addresses a person"
      ],
      "qualifiers": [
        "An approved script grants no ready permission to change it; employment conditions and risks need consideration."
      ]
    },
    {
      "id": "C05",
      "text": "Technical ability is not authority: who requested an action and in what capacity matters; an unexplained basis neither proves a crime nor permits taking resources for oneself.",
      "status": "interpretation",
      "source_ids": [],
      "article_sections": [
        "VI. Administrator: technical ability is not authority"
      ],
      "qualifiers": [
        "Unilateral interruption may affect users; the article determines no safe point for stopping."
      ]
    }
  ],
  "questions": [
    {
      "id": "Q01",
      "q": "Does dividing tasks prove a concealed criminal project?",
      "a": "Dividing work can be ordinary and necessary; it limits visibility without erasing a known contradiction or distributing responsibility equally.",
      "claim_ids": [
        "C01"
      ],
      "source_ids": [],
      "article_sections": [
        "II. Dividing work limits visibility without erasing conduct"
      ]
    },
    {
      "id": "Q02",
      "q": "What does a programmer’s successful check confirm?",
      "a": "A mechanism meeting its specification does not establish a public promise’s truth or the whole service’s legal status; a check’s actual scope differs from a wider endorsement.",
      "claim_ids": [
        "C02"
      ],
      "source_ids": [],
      "article_sections": [
        "III. Programmer: correct execution and a justified purpose"
      ]
    },
    {
      "id": "Q03",
      "q": "Why does a design’s meaning matter here?",
      "a": "An understandable form includes the promise’s meaning; design differs from certifying an unknown authority, and asking who can confirm content requires no access to personal information.",
      "claim_ids": [
        "C03"
      ],
      "source_ids": [],
      "article_sections": [
        "IV. Designer: an understandable form and the grounds for trust"
      ]
    },
    {
      "id": "Q04",
      "q": "Does a prepared script remove the question of an operator’s words?",
      "a": "Reading approved wording differs from authorship, but the recipient receives a message in either case; its known content, knowledge and pressure on the speaker matter.",
      "claim_ids": [
        "C04"
      ],
      "source_ids": [],
      "article_sections": [
        "V. Operator: a prepared script still addresses a person"
      ]
    },
    {
      "id": "Q05",
      "q": "Does technical access authorise every administrative action?",
      "a": "Technical ability is not authority: who requested an action and in what capacity matters; an unexplained basis neither proves a crime nor permits taking resources for oneself.",
      "claim_ids": [
        "C05"
      ],
      "source_ids": [],
      "article_sections": [
        "VI. Administrator: technical ability is not authority"
      ]
    }
  ],
  "sources": [
    {
      "id": "S1",
      "author": "Association for Computing Machinery; presentation Rasit O. Topaloglu",
      "title": "ACM Code of Ethics and Professional Conduct, copyright 2018, reproduced in ACM Code of Ethics and Implications for Artificial Intelligence",
      "url": "https://pok.acm.org/meetings/foils/Topaloglu19.pdf",
      "locator": "PDF zero-based pages 0–1,4–6,12–17,19–26 selected; used 1.3,2.5–2.6; exact short quote p6",
      "read_date": "2026-10-20",
      "rights_status": "COPYRIGHT_ACM_2018_ON_PAGE; full reproduction licence not established",
      "use": "Narrow professional-ethics paraphrase and short heading quote; not criminal law or verified current website edition. Main ACM pages returned 403; presentation date not inferred from filename."
    },
    {
      "id": "S2",
      "author": "Plato; Benjamin Jowett translation",
      "title": "Crito",
      "url": "https://classics.mit.edu/Plato/crito.html",
      "locator": "Header 19–28; selected continuous 72–118; epigraph is Socrates question in118",
      "read_date": "2026-10-20",
      "rights_status": "UNKNOWN",
      "use": "Brief question and bounded comparison of grounds for action; not a duty to imitate Socrates or sacrifice safety; no full-work reading claim"
    }
  ],
  "retrieval_limits": [
    "The text determines no national offence, permits no disclosure of restricted data and promises no safe refusal, report, pause or departure. Under an immediate threat, available protection takes priority over the exercise."
  ],
  "article_blocks": [
    {
      "block_id": "I",
      "section": "I. A small task does not explain the whole product’s purpose"
    },
    {
      "block_id": "II",
      "section": "II. Dividing work limits visibility without erasing conduct"
    },
    {
      "block_id": "III",
      "section": "III. Programmer: correct execution and a justified purpose"
    },
    {
      "block_id": "IV",
      "section": "IV. Designer: an understandable form and the grounds for trust"
    },
    {
      "block_id": "V",
      "section": "V. Operator: a prepared script still addresses a person"
    },
    {
      "block_id": "VI",
      "section": "VI. Administrator: technical ability is not authority"
    },
    {
      "block_id": "VII",
      "section": "VII. Confidentiality does not require ignorance of one’s function"
    },
    {
      "block_id": "VIII",
      "section": "VIII. New knowledge changes the question without rewriting the past"
    },
    {
      "block_id": "IX",
      "section": "IX. Professional ethics asks more than whether something works"
    },
    {
      "block_id": "X",
      "section": "X. Clarifying one’s role is a particular result already"
    },
    {
      "block_id": "LEAD",
      "section": "About this article"
    },
    {
      "block_id": "PRACTICE",
      "section": "What this means in practice"
    }
  ],
  "machine_content": {
    "summary": [
      {
        "text": "Dividing digital work limits visibility of consequences. Programmers check mechanisms, designers shape messages, operators relay answers and administrators manage access within their roles; no component automatically confirms the whole purpose. Particular conduct, knowledge and authority need distinguishing while retaining pressure and real limits on choice.",
        "evidence": [
          {
            "block_id": "II",
            "quote": "A status can pass through several hands. One person creates a mechanism, another labels the screen, and a third repeats the wording over the phone. Nobody authored the whole account alone. Nevertheless, a user encounters a connected message and acts on it. The author’s distinction is that distributed production does not mean there is no resulting act. Responsibility cannot simply be divided equally by the number of participants either. Authority, knowledge, influence and the assignment’s circumstances differ. A shared project name cannot replace examination of those differences."
          },
          {
            "block_id": "III",
            "quote": "Not every specialist can verify an external agreement or a recipient’s authority. Denis can state a truthful boundary: he confirms a particular behaviour of his component rather than the legal status of the whole service. This does not abandon professional quality. An overly broad endorsement can instead conceal the actual scope of a check. Saying that everything has been verified differs from identifying a verified function. Managers, colleagues and clients need that precision too, lest a local result be mistaken for an answer to a question nobody examined."
          },
          {
            "block_id": "IV",
            "quote": "Lena makes a screen understandable and accessible. That has professional value in its own right. Visual clarity, however, includes the meaning of a promise. A completion mark may be understood as confirming an event the designer never checked. The question is not whether a screen is attractive but what it communicates. Users need not guess how a team divides design, data and recipient relationships internally. The words and their presentation therefore need to be considered together, without making design itself a suspect profession."
          },
          {
            "block_id": "V",
            "quote": "Oleg receives approved answers. Working from a script is ordinary; it can prevent excessive promises and keep information consistent. A problem arises when a phrase contradicts what the operator already knows about a particular request. Reading another person’s wording differs from inventing it, but a recipient hears a message in both cases. Who set the answer, who can verify the issue, and what reliability does the speaker personally confirm? An operator’s title neither confers complete knowledge nor makes their words inconsequential."
          },
          {
            "block_id": "V",
            "quote": "Difficulty answering differs from being told knowingly to misrepresent. An unknown can be recognised within a permitted role; repetition cannot make a known false answer true. Fear of losing income, dependency and threats must remain part of the picture. The article neither proposes testing an employer through refusal nor treats calm outward speech as proof of voluntary participation. The assignment’s content, knowledge and pressure matter. A need for protection and a question about one’s action can coexist without producing one universal answer."
          },
          {
            "block_id": "VI",
            "quote": "Marina provides staff access. Her capabilities may exceed her assignment: having a technical tool does not authorise every use of it. An administrative action’s purpose concerns who requested it, in what capacity and for which agreed function. This article gives no methods for access, interference or concealment. It distinguishes a system resource from the right to control it. Work access does not become an administrator’s personal property, even where they have ethical concerns about a project."
          },
          {
            "block_id": "VIII",
            "quote": "Divided tasks do not distribute the capacity to act equally. A manager setting content and an employee performing one component may have different choices. This does not justify ignoring the worker’s contribution. It means not demanding control they lack. Participants can relay questions, but relaying is not consideration or correction. An absent quick reply does not always mean bad intent either. The state of a particular task differs from a judgement about everybody’s character along the chain."
          }
        ]
      }
    ],
    "topics": [
      {
        "text": "When the purpose of digital work is unclear",
        "evidence": [
          {
            "block_id": "I",
            "quote": "Imagine a service receiving people’s requests. Denis programmes a change in a request’s status. Lena designs a screen promising an answer. Oleg communicates with users through agreed wording. Marina administers team access. They are told that the service helps people forward requests to responsible organisations. Later, a question emerges: does the visible status mean that an authorised recipient actually accepted a request, or only that the service saved it internally? That is a question about a particular meaning, rather than proof of criminal intent throughout the team."
          },
          {
            "block_id": "I",
            "quote": "Each participant has a different field of view. Denis may know when a record changes without knowing who answers users. Lena sees a promise but not the agreement with its recipient. Oleg hears complaints without controlling the product. Marina knows access boundaries without knowing every business relationship. Full knowledge cannot be assigned by job title. A limited role, however, does not make a contradiction already known to someone disappear. Knowing that a particular action has been described inaccurately raises a separate issue requiring consideration."
          },
          {
            "block_id": "II",
            "quote": "A substantial product cannot be built by making every participant perform every function. Division allows different skills and protects information people do not need. Saying that one is not shown everything is therefore not itself evidence of criminal purpose. A more relevant question is whether the meaning of the part someone creates, speaks or confirms has been sufficiently explained. Demanding every commercial detail differs from understanding one’s own promise to a user."
          },
          {
            "block_id": "VIII",
            "quote": "Feeling insufficiently informed does not establish a concealed purpose. Uncertainty, communication error, changed use and deliberate concealment are different possibilities. The team might find an inaccurate term without discovering criminal aims. A different result is possible too. Descriptions can change in either direction when their grounds change. Clarification does not make the earlier experience imaginary or mean that everything is now known. Identify what changed while keeping the rest at its actual degree of certainty."
          }
        ]
      }
    ],
    "claims": [
      {
        "text": "Dividing work can be ordinary and necessary; it limits visibility without erasing a known contradiction or distributing responsibility equally.",
        "status": "interpretation",
        "evidence": [
          {
            "block_id": "II",
            "quote": "A substantial product cannot be built by making every participant perform every function. Division allows different skills and protects information people do not need. Saying that one is not shown everything is therefore not itself evidence of criminal purpose. A more relevant question is whether the meaning of the part someone creates, speaks or confirms has been sufficiently explained. Demanding every commercial detail differs from understanding one’s own promise to a user."
          },
          {
            "block_id": "II",
            "quote": "A status can pass through several hands. One person creates a mechanism, another labels the screen, and a third repeats the wording over the phone. Nobody authored the whole account alone. Nevertheless, a user encounters a connected message and acts on it. The author’s distinction is that distributed production does not mean there is no resulting act. Responsibility cannot simply be divided equally by the number of participants either. Authority, knowledge, influence and the assignment’s circumstances differ. A shared project name cannot replace examination of those differences."
          },
          {
            "block_id": "II",
            "quote": "It is particularly easy to confuse lacking information with lacking consequences. Someone may not know which error a particular user will encounter while knowing they are asked to confirm the unconfirmed. Conversely, general concern about a project does not establish that every ordinary task already serves harm. Both limits need to remain visible. An unknown cannot excuse everything, and a suspected connection cannot become a proven contribution. This supplies no legal conclusion; it preserves what actually needs an explanation."
          }
        ],
        "source_ids": [],
        "qualifiers": [
          {
            "text": "An unknown cannot excuse everything, and a suspected connection is not a proven contribution; no legal conclusion follows.",
            "evidence": [
              {
                "block_id": "II",
                "quote": "It is particularly easy to confuse lacking information with lacking consequences. Someone may not know which error a particular user will encounter while knowing they are asked to confirm the unconfirmed. Conversely, general concern about a project does not establish that every ordinary task already serves harm. Both limits need to remain visible. An unknown cannot excuse everything, and a suspected connection cannot become a proven contribution. This supplies no legal conclusion; it preserves what actually needs an explanation."
              }
            ]
          }
        ]
      },
      {
        "text": "A mechanism meeting its specification does not establish a public promise’s truth or the whole service’s legal status; a check’s actual scope differs from a wider endorsement.",
        "status": "interpretation",
        "evidence": [
          {
            "block_id": "III",
            "quote": "Denis can check that a change behaves according to agreed conditions. That is a significant technical result. Checking whether a system did what was requested does not establish the truth of the meaning its interface communicates. If internal storage is labelled confirmation of an external decision, a successful technical check cannot make the label accurate. No instructions about the product’s internal mechanics are needed here. The two questions are whether the mechanism meets its specification and whether the public statement corresponds to what actually happened."
          },
          {
            "block_id": "III",
            "quote": "Not every specialist can verify an external agreement or a recipient’s authority. Denis can state a truthful boundary: he confirms a particular behaviour of his component rather than the legal status of the whole service. This does not abandon professional quality. An overly broad endorsement can instead conceal the actual scope of a check. Saying that everything has been verified differs from identifying a verified function. Managers, colleagues and clients need that precision too, lest a local result be mistaken for an answer to a question nobody examined."
          }
        ],
        "source_ids": [],
        "qualifiers": [
          {
            "text": "Earlier checks do not certify new uses; a safe halt or dispute has not been established.",
            "evidence": [
              {
                "block_id": "III",
                "quote": "If the purpose changes later, an earlier assignment may no longer describe current use. New information cannot automatically be projected backwards to make a worker originally aware of everything. The initial innocuous account cannot close every later change either. The question belongs to a time and an action: what became known, what task is now proposed, and in what capacity must it be confirmed? This article cannot determine whether an immediate halt or argument with the client would be safe for Denis."
              },
              {
                "block_id": "III",
                "quote": "Reusing an existing component for an undisclosed task raises another question. Reuse is not inherently criminal; ordinary products change purposes and audiences. But an earlier check took place under particular conditions. It does not automatically certify a new promise or a different set of affected people. Denis might be asked to cite an old approval as confirmation of all current use. Preserving a technical result differs from certifying a new meaning assigned to it. This requires no repetition of the whole job without reason. It requires keeping the earlier conclusion within its actual scope."
              }
            ]
          }
        ]
      },
      {
        "text": "An understandable form includes the promise’s meaning; design differs from certifying an unknown authority, and asking who can confirm content requires no access to personal information.",
        "status": "interpretation",
        "evidence": [
          {
            "block_id": "IV",
            "quote": "Lena makes a screen understandable and accessible. That has professional value in its own right. Visual clarity, however, includes the meaning of a promise. A completion mark may be understood as confirming an event the designer never checked. The question is not whether a screen is attractive but what it communicates. Users need not guess how a team divides design, data and recipient relationships internally. The words and their presentation therefore need to be considered together, without making design itself a suspect profession."
          },
          {
            "block_id": "IV",
            "quote": "A designer does not become an expert on every project circumstance. But they may be asked to give an established appearance to something that remains the client’s promise. The boundary of authorship matters: producing design differs from certifying an unknown authority. Asking who can confirm the content concerns the task itself. It requires no access to private correspondence or personal information. An absent confirmation should not be hidden within more confident presentation. This is an ethical distinction rather than a ready-made legal classification of an image."
          }
        ],
        "source_ids": [],
        "qualifiers": [
          {
            "text": "Designers may have limited influence; a professional question guarantees no calm response.",
            "evidence": [
              {
                "block_id": "IV",
                "quote": "The effect on a user’s choice also matters. Clarifying a phrase may change an expectation rather than an aesthetic preference: an internal stage ceases to look like a final decision. Sometimes another responsible participant must supply an explanation. Lena may have little influence, and objection may carry real consequences. A professionally framed question will not necessarily receive a calm response. Limited influence does not make her solely responsible for the entire result either. Specific roles and facts are needed instead of an all-powerful designer or completely neutral decoration."
              }
            ]
          }
        ]
      },
      {
        "text": "Reading approved wording differs from authorship, but the recipient receives a message in either case; its known content, knowledge and pressure on the speaker matter.",
        "status": "interpretation",
        "evidence": [
          {
            "block_id": "V",
            "quote": "Oleg receives approved answers. Working from a script is ordinary; it can prevent excessive promises and keep information consistent. A problem arises when a phrase contradicts what the operator already knows about a particular request. Reading another person’s wording differs from inventing it, but a recipient hears a message in both cases. Who set the answer, who can verify the issue, and what reliability does the speaker personally confirm? An operator’s title neither confers complete knowledge nor makes their words inconsequential."
          },
          {
            "block_id": "V",
            "quote": "An operator may be caught between a user’s complaint and an instruction to maintain the company’s line. The complaint does not prove the user’s entire account. An internal instruction does not prove every answer true either. Oleg may know a limited fact: the relevant action has not been confirmed within his role. Retaining that boundary is more accurate than assuming knowledge he lacks or accusing an organisation on one conversation. This does not provide permission to change approved wording; actual employment conditions and risks need separate consideration."
          },
          {
            "block_id": "V",
            "quote": "Difficulty answering differs from being told knowingly to misrepresent. An unknown can be recognised within a permitted role; repetition cannot make a known false answer true. Fear of losing income, dependency and threats must remain part of the picture. The article neither proposes testing an employer through refusal nor treats calm outward speech as proof of voluntary participation. The assignment’s content, knowledge and pressure matter. A need for protection and a question about one’s action can coexist without producing one universal answer."
          }
        ],
        "source_ids": [],
        "qualifiers": [
          {
            "text": "An approved script grants no ready permission to change it; employment conditions and risks need consideration.",
            "evidence": [
              {
                "block_id": "V",
                "quote": "An operator may be caught between a user’s complaint and an instruction to maintain the company’s line. The complaint does not prove the user’s entire account. An internal instruction does not prove every answer true either. Oleg may know a limited fact: the relevant action has not been confirmed within his role. Retaining that boundary is more accurate than assuming knowledge he lacks or accusing an organisation on one conversation. This does not provide permission to change approved wording; actual employment conditions and risks need separate consideration."
              }
            ]
          }
        ]
      },
      {
        "text": "Technical ability is not authority: who requested an action and in what capacity matters; an unexplained basis neither proves a crime nor permits taking resources for oneself.",
        "status": "interpretation",
        "evidence": [
          {
            "block_id": "VI",
            "quote": "Marina provides staff access. Her capabilities may exceed her assignment: having a technical tool does not authorise every use of it. An administrative action’s purpose concerns who requested it, in what capacity and for which agreed function. This article gives no methods for access, interference or concealment. It distinguishes a system resource from the right to control it. Work access does not become an administrator’s personal property, even where they have ethical concerns about a project."
          },
          {
            "block_id": "VI",
            "quote": "An administrator may be told that approval exists at another level. Sometimes that is true. Sometimes the person relaying the request does not know the authority themselves. Reporting to one manager does not automatically establish rights over another party’s resource. Marina need not prove every organisational connection to name a narrow question about her assignment. Lacking a clear answer does not establish a crime. It means that a particular basis remains unexplained. Urgency, remote work and use of an intermediary do not prove wrongdoing by themselves either."
          }
        ],
        "source_ids": [],
        "qualifiers": [
          {
            "text": "Unilateral interruption may affect users; the article determines no safe point for stopping.",
            "evidence": [
              {
                "block_id": "VI",
                "quote": "People already relying on a service must remain visible. Unilateral interruption can affect users and colleagues who did not make the disputed decision. Ethical concern therefore supplies no permission to destroy a system, erase records or take information for oneself. Nor does user dependency create an indefinite obligation to follow every new demand. Maintaining service, changing one’s role and assessing danger are different questions. A general article determines no safe point for stopping and cannot replace competent explanation of particular obligations."
              }
            ]
          }
        ]
      }
    ],
    "limitations": [
      {
        "text": "The text determines no national offence, permits no disclosure of restricted data and promises no safe refusal, report, pause or departure. Under an immediate threat, available protection takes priority over the exercise.",
        "evidence": [
          {
            "block_id": "LEAD",
            "quote": "A programmer receives a small task. A designer needs to make a form clearer. An operator follows an approved script, while an administrator provides staff access. Each can see a part without knowing the purpose of the whole. Such division is often ordinary and necessary; it does not prove a criminal project. The difficulty arises when a function known to someone contradicts the client’s explanation, or they are asked to confirm something they do not know. This article examines all four roles and how divided tasks limit visibility of consequences. Its fictional request-handling service describes no actual company and explains no fraud techniques. We distinguish technical correctness, a message’s meaning, authority, knowledge and pressure. Readers need not investigate an entire organisation or establish their innocence by reading. The text determines no national offence, permits no disclosure of restricted data and promises no safe refusal, report, pause or departure. Under an immediate threat, available protection takes priority over the exercise."
          },
          {
            "block_id": "PRACTICE",
            "quote": "If considering work is currently safe, choose one assignment. Which event, message or authority belongs specifically to it? What do you know directly, what did a client say, and what remains unknown? There is no need to obtain missing proof or learn the whole organisation. This author-created exercise has no claimed proven efficacy. It proposes neither copying databases, bypassing access, covert testing, changing a running service nor destroying records. Immediate protection should not be delayed by it."
          },
          {
            "block_id": "PRACTICE",
            "quote": "Where help is needed, its object can be limited to a task’s purpose, a role or disclosure conditions. Do not assume a contact is safe because of an organisation’s name or a listener’s sympathy. Income, dependency and possible pressure remain real conditions of choice. A safe pause, refusal, report or exit cannot be promised. Sometimes the currently available result is a clearer distinction between known and unknown. Lacking every resource does not itself establish guilt."
          }
        ]
      },
      {
        "text": "Independent help guarantees neither confidentiality nor a result, and suitable assistance may be unavailable.",
        "evidence": [
          {
            "block_id": "VII",
            "quote": "Independent explanation also has limits. Before sharing information, the recipient’s role, competence, possible connections and consultation conditions matter. A professional label, sympathy or appealing contact form guarantees neither confidentiality nor a result. Suitable help may currently be unavailable. That is a real limitation, not something an instruction to find the right specialist immediately can erase. A close person can support someone’s choice without publishing their story or intervening without consent. Assistance should not become a new form of control."
          }
        ]
      }
    ]
  },
  "schema_org": {
    "@context": "https://schema.org",
    "@type": "Article",
    "identifier": "UW:SYS-195:en",
    "headline": "I do my part of the work — but what is it for?",
    "inLanguage": "en",
    "author": [
      {
        "@type": "Person",
        "name": "Andrey Zarinsh"
      },
      {
        "@type": "Person",
        "name": "Maria Evilkut"
      }
    ]
  },
  "production_compatibility": "NOT_RUN",
  "server_auto_acceptance": "NOT_RUN"
}