{
  "id": "axiomao:organization-profiles",
  "edition": "0.1",
  "language": "en",
  "status": "proposed",
  "title": "Organization profiles",
  "description": "Describe a concrete organization, its authority, state, evidence, and unresolved questions.",
  "canonical": "https://axiomao.org/en/organization-profiles/",
  "published": "2026-10-14",
  "sections": [
    {
      "id": "profile",
      "heading": "A profile is a scoped description",
      "paragraphs": [
        "An organizational profile records a particular design or deployment under a named taxonomy version. It should identify the organization’s purpose, responsible owner, operating environment, authority boundary, and evidence date. A proposed design, an implemented mechanism, and observed operation require distinct status labels.",
        "Profiles support comparison without pretending that two systems are equivalent because they use the same framework. The same software can run under different mandates, permissions, resource allocations, and human review arrangements. Those choices can change practical autonomy more than the name of the model provider."
      ]
    },
    {
      "id": "illustration",
      "heading": "Illustrative research office",
      "paragraphs": [
        "Consider a proposed research office that maintains a bibliography and prepares evidence reviews. Its owner selects a subject area and a compute allocation. The system chooses approved questions, records sources, prepares analysis, and requests human approval before publication. This example is illustrative; it is not a report of an existing Axiom AO deployment.",
        "The profile would state that research planning is delegated, external publication is supervised, and source documents are read-only. It would identify persistent questions, accepted analyses, pending corrections, and resource records. Agent composition would remain a separate field: one agent or several could implement this arrangement."
      ]
    },
    {
      "id": "evidence",
      "heading": "Describe uncertainty explicitly",
      "paragraphs": [
        "For each substantial claim, identify whether its basis is configuration, source inspection, a controlled test, or operating evidence. Configuration may establish intended limits; only suitable observations show whether those limits were respected during work. An uninterrupted demonstration cannot establish recovery after a crash.",
        "Unknown values are useful information. Record missing measurements, unavailable review, and untested scenarios rather than inferring favorable answers. When a mandate or implementation changes, update the profile and retain its previous version so that earlier results can be interpreted against the conditions that actually applied."
      ]
    }
  ],
  "references": [
    {
      "label": "Hübner, Sichman & Boissier (2002). A Model for the Structural, Functional, and Deontic Specification of Organizations in Multiagent Systems",
      "url": "https://moise.sourceforge.net/doc/publications/Hubner-sbia2002.pdf"
    },
    {
      "label": "Xu et al. (2024). TheAgentCompany",
      "url": "https://arxiv.org/abs/2412.14161"
    }
  ],
  "related": [
    "https://axiomao.org/en/taxonomy/",
    "https://axiomao.org/en/organization-archetypes/",
    "https://axiomao.org/en/evaluation-methods/"
  ]
}