{
  "vercy": "1.0-draft",
  "publication": {
    "status": "research-draft",
    "adjudicationStatus": "unreviewed",
    "publishableCanonical": false,
    "generatedAt": "2026-09-12T08:21:12Z",
    "providers": [
      "Codex"
    ],
    "breadth": "recalled by Codex without web access - no source was read",
    "missingProviders": [],
    "pass": 2,
    "cost": {
      "grok": {
        "seconds": 33.0,
        "error": "Reading additional input from stdin...\nOpenAI Codex v0.153.4\n--------\nworkdir: R:\\02_PROJECTS\\02_Meta_Models_Platforms\\Ver.cy\\current\\thing-registry-backlog\nmodel: gpt-6-astra\nprovider: openai\napproval: never\nsandbox: read-only\nreasoning effort: none\nreasoning summaries: none\nsession id: 01a094b3-b59f-7e90-be46-5f20b2f7bb14\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: call forwarding\nSense to describe: (none recorded)\nDomain code: ACT.ACT\nAlso known as: (none)\n\n\nContext for this batch of 1001 things:\n# Batch 043: 1001",
        "usd": 0.0,
        "recall": true
      },
      "codex": {
        "seconds": 72.1,
        "error": "Reading additional input from stdin...\nOpenAI Codex v0.153.4\n--------\nworkdir: R:\\02_PROJECTS\\02_Meta_Models_Platforms\\Ver.cy\\current\\thing-registry-backlog\nmodel: gpt-6-astra\nprovider: openai\napproval: never\nsandbox: read-only\nreasoning effort: none\nreasoning summaries: none\nsession id: 01a094b3-b592-7633-8146-b40c3c795372\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: call forwarding\nRegistry id: vr.tr.call-forwarding\nPlane / domain: ACT / ACT.ACT\nRegistry definition: (none recorded)\nNames folded into this entry: ("
      }
    },
    "enrichment": {
      "pass": 3,
      "engine": "claude",
      "producedAt": "2026-10-06T12:00:00Z",
      "ingestedAt": "2026-10-06T08:50:36+00:00",
      "fields": [
        "agent_conduct",
        "ethics",
        "owners"
      ]
    },
    "gate": {
      "passed": true,
      "version": "1.0",
      "at": "2026-10-07T10:10:29+00:00",
      "evidence": [
        "completeness 1.00",
        "sense: Wikidata description",
        "2 live sources",
        "review by codex: pass"
      ]
    }
  },
  "metaModel": {
    "id": "THING-Q240215",
    "registryId": "vr.tr.call-forwarding",
    "name": "call forwarding",
    "version": "0.1.0-research.1",
    "entryKind": "thing",
    "family": "Thing Registry",
    "domain": [
      "ACT.ACT"
    ],
    "status": "research-draft"
  },
  "canonicalUrl": "https://ver.cy/models/thing/q240215/",
  "model": {
    "registry_id": "vr.tr.call-forwarding",
    "name": "call forwarding",
    "purpose": "Enable an agent to recognise call forwarding, assess when and where it redirects incoming calls, and determine which configuration or diagnostic actions are authorised.",
    "definition": "Call forwarding is a telephony service that redirects an incoming call addressed to one destination to another destination, either unconditionally or when a specified condition is met.",
    "scope_statement": "This model owns call forwarding as an activity and configured telephony behaviour that redirects calls addressed to one called identity toward another destination, including its conditions, routing consequences, control and verification.",
    "in_scope": [
      "The called identity, forwarding destination and party authorised to control forwarding",
      "Unconditional and conditional forwarding rules and their activation state",
      "Evaluation of forwarding conditions and selection of destinations",
      "Forwarding chains, conflicts and termination conditions",
      "Configuration changes and evidence of actual forwarding outcomes"
    ],
    "out_of_scope": [
      "General telephone network transport and signalling implementation",
      "Transfer of an already established call",
      "General call distribution, queue management and simultaneous ringing",
      "Voicemail recording, storage and retrieval",
      "Number portability and permanent reassignment of telephone numbers",
      "Provider-wide billing and account administration"
    ],
    "distinguishing_features": [
      "An incoming call is addressed to an original called identity, while a forwarding rule directs it toward another destination.",
      "Forwarding depends on a configured rule or service state; manually placing a new outgoing call does not constitute forwarding.",
      "Unconditional forwarding does not depend on the original destination failing to answer; conditional forwarding requires a specified condition to be met.",
      "Forwarding redirects an incoming call attempt rather than transferring an already established conversation.",
      "Forwarding preserves the distinction between the original called identity and the destination; number reassignment changes which service the number identifies."
    ],
    "characteristics": [
      {
        "name": "Original called identity",
        "kind": "relation",
        "unit_or_values": "Telephone number, extension or other supported called address",
        "why_it_matters": "Identifies which incoming calls fall under the forwarding rule."
      },
      {
        "name": "Forwarding destination",
        "kind": "relation",
        "unit_or_values": "Destination address and its associated service or endpoint, where known",
        "why_it_matters": "Determines where qualifying call attempts are redirected."
      },
      {
        "name": "Forwarding condition",
        "kind": "category",
        "unit_or_values": "Unconditional, busy, no answer, unreachable or an explicitly documented service-specific condition",
        "why_it_matters": "Separates forwarding modes and identifies the evidence needed to trigger each rule."
      },
      {
        "name": "Configuration state",
        "kind": "state",
        "unit_or_values": "Unconfigured, configured but disabled, enabled or unknown",
        "why_it_matters": "A stored destination alone does not establish that forwarding is active."
      },
      {
        "name": "No-answer delay",
        "kind": "measurement",
        "unit_or_values": "Seconds; not applicable or unknown where appropriate",
        "why_it_matters": "Defines when a no-answer rule becomes eligible and supports timed verification."
      },
      {
        "name": "Condition evaluation point",
        "kind": "relation",
        "unit_or_values": "Named network service, PBX, application or endpoint responsible for evaluating the condition",
        "why_it_matters": "Explains whose interpretation of busy, no answer or unreachable governs the decision."
      },
      {
        "name": "Rule precedence",
        "kind": "relation",
        "unit_or_values": "Documented ordering or override relationship among applicable rules",
        "why_it_matters": "Allows the agent to identify the effective route when multiple rules could apply."
      },
      {
        "name": "Forwarding hop count",
        "kind": "measurement",
        "unit_or_values": "Number of observed redirections, with observation coverage recorded",
        "why_it_matters": "Helps distinguish a direct redirection from a chain and investigate possible loops."
      },
      {
        "name": "Observed call outcome",
        "kind": "state",
        "unit_or_values": "Redirected, destination ringing, answered, rejected, failed, timed out or unknown",
        "why_it_matters": "Separates successful redirection from successful completion of the call."
      },
      {
        "name": "Control authority",
        "kind": "relation",
        "unit_or_values": "Authorised subscriber, administrator or delegated controller and applicable permission scope",
        "why_it_matters": "Determines who may inspect or change forwarding for the called identity."
      }
    ],
    "affordances": [
      "Inspect the effective forwarding configuration for a called identity.",
      "Explain which forwarding rule applies to a specified incoming-call situation.",
      "Enable, disable or change forwarding within the agent's granted authority.",
      "Check destination validity, rule conflicts and potential routing loops before a change.",
      "Run authorised test calls and compare observed routes with intended behaviour.",
      "Restore a recorded prior configuration when an authorised change produces an unacceptable outcome."
    ],
    "agent_conduct": {
      "may": [
        "Set up or change call forwarding on lines the agent is authorized to manage, at the subscriber's request.",
        "Explain forwarding options and their costs."
      ],
      "must_not": [
        "Forward someone's calls to another number without the subscriber's knowledge and consent.",
        "Use forwarding to intercept calls or one-time passcodes.",
        "Forward emergency or care lines to unmonitored destinations.",
        "Hide active forwarding from the line's subscriber."
      ],
      "requires_human": [
        "Changing forwarding on a shared, business or emergency line."
      ]
    },
    "ethics": {
      "considerations": [
        "Covert forwarding enables fraud and surveillance, including account takeover.",
        "Missed forwarded calls can mean missed emergencies."
      ],
      "affected_parties": [
        "Subscribers",
        "Callers",
        "People relying on emergency lines"
      ]
    },
    "owners": {
      "steward": "The subscriber of the line; the telephone service provider operates the service.",
      "master_systems": [
        "Telephone service provider subscriber records"
      ]
    },
    "what_it_is_for": [
      "Call forwarding is used in personal and organizational telephone services to route incoming calls to an alternative destination.",
      "It supports continuity when a person is unavailable, a line is busy or calls need to reach another location."
    ],
    "standards_and_regulation": [
      "Recommendation I.252.1, issued by the International Telecommunication Union Telecommunication Standardization Sector, specifies the call forwarding unconditional supplementary service.",
      "Recommendation I.252.2, issued by the International Telecommunication Union Telecommunication Standardization Sector, specifies the call forwarding busy supplementary service.",
      "Recommendation I.252.3, issued by the International Telecommunication Union Telecommunication Standardization Sector, specifies the call forwarding no reply supplementary service."
    ],
    "failure_modes_and_hazards": [
      "Unauthorized forwarding can expose confidential conversations or divert calls intended to verify identity.",
      "Incorrect destinations or forwarding loops can prevent callers from reaching the intended recipient.",
      "Forwarded calls can incur unexpected charges under the applicable service tariff."
    ],
    "facets_not_applicable": {
      "recognition": "Call forwarding is a network behavior whose operation cannot be established from visual appearance."
    }
  },
  "sources": [
    {
      "id": "wikidata",
      "title": "Wikidata item Q240215: call forwarding",
      "url": "https://www.wikidata.org/wiki/Q240215",
      "url_status": "live",
      "what_it_supports": "identity and sense of the item",
      "checked_by": "wikidata-api"
    },
    {
      "id": "wikipedia-en",
      "title": "Wikipedia: Call forwarding",
      "url": "https://en.wikipedia.org/wiki/Call_forwarding",
      "url_status": "live",
      "what_it_supports": "general description of the item",
      "checked_by": "wikidata-api sitelink"
    }
  ],
  "structure": {
    "bundles": [
      {
        "id": "called-identity-and-destination",
        "name": "Called identity and destination",
        "description": "Establishes which incoming calls are subject to forwarding and where they are intended to go.",
        "rationale": "Forwarding can only be recognised by relating the original called identity to a distinct routing destination.",
        "layers": [
          {
            "id": "original-call-addressing",
            "name": "Original call addressing",
            "description": "Locates the identity and service to which callers initially address calls.",
            "findings": [
              {
                "id": "forwarding-subject",
                "name": "Forwarding subject",
                "description": "Record the original called address and the line, extension or service whose forwarding behaviour is being modelled.",
                "questions": [
                  {
                    "text": "Which called address brings an incoming call within this forwarding configuration?",
                    "kind": "definition",
                    "id": "forwarding-subject-q01"
                  },
                  {
                    "text": "Does the rule apply to this address alone or to other addresses associated with the same service?",
                    "kind": "boundary",
                    "id": "forwarding-subject-q02"
                  }
                ]
              }
            ]
          },
          {
            "id": "destination-resolution",
            "name": "Destination resolution",
            "description": "Identifies the configured target and how its address is interpreted.",
            "findings": [
              {
                "id": "resolved-forwarding-target",
                "name": "Resolved forwarding target",
                "description": "Record the destination as entered, its resolved address where available and whether it denotes an endpoint or another routing service.",
                "questions": [
                  {
                    "text": "What destination is configured, and how does the forwarding service interpret its address?",
                    "kind": "definition",
                    "id": "resolved-forwarding-target-q01"
                  },
                  {
                    "text": "What evidence confirms that this destination reaches the intended recipient or service?",
                    "kind": "provenance",
                    "id": "resolved-forwarding-target-q02"
                  }
                ]
              }
            ]
          }
        ]
      },
      {
        "id": "forwarding-conditions",
        "name": "Forwarding conditions",
        "description": "Captures the circumstances under which an incoming call should be redirected.",
        "rationale": "An agent must distinguish a configured rule from a rule whose triggering condition actually holds.",
        "layers": [
          {
            "id": "condition-semantics",
            "name": "Condition semantics",
            "description": "Makes the meaning and evaluator of each forwarding condition explicit.",
            "findings": [
              {
                "id": "trigger-interpretation",
                "name": "Trigger interpretation",
                "description": "Record whether forwarding is unconditional or conditional and the service-specific meaning of each condition.",
                "questions": [
                  {
                    "text": "Which condition triggers forwarding, and what does the responsible service count as satisfying it?",
                    "kind": "definition",
                    "id": "trigger-interpretation-q01"
                  },
                  {
                    "text": "Which component evaluates the condition, and where is that behaviour documented?",
                    "kind": "provenance",
                    "id": "trigger-interpretation-q02"
                  }
                ]
              }
            ]
          },
          {
            "id": "timing-and-effective-state",
            "name": "Timing and effective state",
            "description": "Determines whether a rule is active and when a timed condition becomes eligible.",
            "findings": [
              {
                "id": "rule-eligibility",
                "name": "Rule eligibility",
                "description": "Record enabled state, any supported activation window and the threshold and timing basis for no-answer forwarding.",
                "questions": [
                  {
                    "text": "Is the rule currently enabled and applicable to the incoming call under examination?",
                    "kind": "measurement",
                    "id": "rule-eligibility-q01"
                  },
                  {
                    "text": "For no-answer forwarding, what delay applies and which event starts that interval?",
                    "kind": "measurement",
                    "id": "rule-eligibility-q02"
                  }
                ]
              }
            ]
          }
        ]
      },
      {
        "id": "route-selection-and-chains",
        "name": "Route selection and chains",
        "description": "Explains the effective forwarding route when rules or downstream services interact.",
        "rationale": "A valid individual rule can still produce an unintended route through precedence, further forwarding or failure handling.",
        "layers": [
          {
            "id": "competing-call-treatment",
            "name": "Competing call treatment",
            "description": "Resolves interaction between forwarding rules and other incoming-call treatments.",
            "findings": [
              {
                "id": "effective-rule-selection",
                "name": "Effective rule selection",
                "description": "Record the established ordering between applicable forwarding rules and adjacent treatments such as call waiting, rejection or voicemail routing.",
                "questions": [
                  {
                    "text": "If unconditional and conditional rules are both configured, which one governs this call?",
                    "kind": "boundary",
                    "id": "effective-rule-selection-q01"
                  },
                  {
                    "text": "How do other enabled call treatments affect whether the forwarding condition is reached?",
                    "kind": "boundary",
                    "id": "effective-rule-selection-q02"
                  }
                ]
              }
            ]
          },
          {
            "id": "downstream-redirection",
            "name": "Downstream redirection",
            "description": "Tracks further forwarding and the conditions that stop the route.",
            "findings": [
              {
                "id": "chain-and-termination",
                "name": "Chain and termination",
                "description": "Record known forwarding hops, repeated destinations, applicable limits and what happens when a downstream destination cannot accept the call.",
                "questions": [
                  {
                    "text": "Does the destination forward again, and does the known route revisit an earlier address?",
                    "kind": "measurement",
                    "id": "chain-and-termination-q01"
                  },
                  {
                    "text": "What documented behaviour terminates a loop, excessive chain or failed destination attempt?",
                    "kind": "provenance",
                    "id": "chain-and-termination-q02"
                  }
                ]
              }
            ]
          }
        ]
      },
      {
        "id": "forwarding-control-and-consequences",
        "name": "Forwarding control and consequences",
        "description": "Connects configuration authority with the recipient, information and cost consequences of redirecting calls.",
        "rationale": "Changing forwarding changes who can receive incoming calls and may alter the information or charges associated with them.",
        "layers": [
          {
            "id": "configuration-authority",
            "name": "Configuration authority",
            "description": "Establishes who may change the rule and through which control surface.",
            "findings": [
              {
                "id": "authorised-rule-change",
                "name": "Authorised rule change",
                "description": "Record the controller's authority, supported configuration mechanism, requested change and recoverable prior state.",
                "questions": [
                  {
                    "text": "What authority permits this agent to change forwarding for the original called identity?",
                    "kind": "action",
                    "id": "authorised-rule-change-q01"
                  },
                  {
                    "text": "Which supported operation applies the requested change, and how can the prior configuration be restored?",
                    "kind": "action",
                    "id": "authorised-rule-change-q02"
                  }
                ]
              }
            ]
          },
          {
            "id": "recipient-information-and-charges",
            "name": "Recipient information and charges",
            "description": "Identifies consequential differences between receiving a direct call and receiving a forwarded call.",
            "findings": [
              {
                "id": "forwarded-call-consequences",
                "name": "Forwarded call consequences",
                "description": "Record supported evidence about identity presentation, forwarding indications, destination restrictions and applicable charge responsibility.",
                "questions": [
                  {
                    "text": "What caller identity, original called identity or forwarding indication will the destination receive?",
                    "kind": "provenance",
                    "id": "forwarded-call-consequences-q01"
                  },
                  {
                    "text": "Which destination restrictions and charge responsibilities apply to this forwarding route?",
                    "kind": "provenance",
                    "id": "forwarded-call-consequences-q02"
                  }
                ]
              }
            ]
          }
        ]
      },
      {
        "id": "forwarding-verification",
        "name": "Forwarding verification",
        "description": "Relates intended configuration to observed redirection and call completion.",
        "rationale": "A successful configuration response does not establish that calls are redirected correctly or answered by the intended destination.",
        "layers": [
          {
            "id": "configuration-confirmation",
            "name": "Configuration confirmation",
            "description": "Checks whether a requested forwarding configuration became effective.",
            "findings": [
              {
                "id": "effective-configuration-evidence",
                "name": "Effective configuration evidence",
                "description": "Record the requested state, service acknowledgement, subsequent readback and any unresolved difference between them.",
                "questions": [
                  {
                    "text": "What does the service report as the current forwarding destination, condition and enabled state?",
                    "kind": "measurement",
                    "id": "effective-configuration-evidence-q01"
                  },
                  {
                    "text": "What evidence distinguishes acceptance of the change request from activation of the requested behaviour?",
                    "kind": "provenance",
                    "id": "effective-configuration-evidence-q02"
                  }
                ]
              }
            ]
          },
          {
            "id": "call-path-testing",
            "name": "Call path testing",
            "description": "Uses authorised call attempts to assess trigger handling and downstream outcomes.",
            "findings": [
              {
                "id": "observed-forwarding-outcome",
                "name": "Observed forwarding outcome",
                "description": "Record test conditions, observed redirection, destination behaviour and limits on what the observation proves.",
                "questions": [
                  {
                    "text": "Under controlled triggering and non-triggering conditions, did the call follow the expected route and timing?",
                    "kind": "measurement",
                    "id": "observed-forwarding-outcome-q01"
                  },
                  {
                    "text": "Does the evidence establish redirection, destination ringing or an answered call, and which stages remain unobserved?",
                    "kind": "boundary",
                    "id": "observed-forwarding-outcome-q02"
                  },
                  {
                    "text": "If the observed route differs from the intended route, which authorised diagnostic or restoration action should follow?",
                    "kind": "action",
                    "id": "observed-forwarding-outcome-q03"
                  }
                ]
              }
            ]
          }
        ]
      },
      {
        "id": "evidence-and-external-alignment",
        "name": "Evidence and external alignment",
        "description": "What the world already says about this thing, gathered so the model can be checked against it.",
        "rationale": "A model that cannot be lined up against existing standards, identifiers and practice cannot be adopted by anyone who already uses them.",
        "layers": [
          {
            "id": "reported-evidence",
            "name": "Reported evidence",
            "description": "Findings from the breadth pass, kept separate from the structural claims.",
            "findings": [
              {
                "id": "evidence-confidence-notes",
                "name": "Check these first",
                "description": "Recalled without web access and unsourced; every item is a lead to verify.",
                "evidence": [
                  "This describes the conventional telephony sense; no narrower registry sense was supplied.",
                  "Standards are named from recall, without checking editions or their applicability to a particular network architecture.",
                  "Selective forwarding, timing limits, activation codes, and billing require provider-specific verification."
                ],
                "questions": [
                  {
                    "id": "evidence-confidence-notes-q01",
                    "text": "Which of these check these first hold for the sense of call forwarding this model covers, and on what evidence?",
                    "kind": "provenance"
                  }
                ]
              },
              {
                "id": "evidence-kinds",
                "name": "Kinds and varieties",
                "description": "Recalled without web access and unsourced; every item is a lead to verify.",
                "evidence": [
                  "Unconditional forwarding",
                  "Forwarding when busy",
                  "Forwarding when unanswered",
                  "Forwarding when not reachable",
                  "Selective forwarding based on caller or other configured rules"
                ],
                "questions": [
                  {
                    "id": "evidence-kinds-q01",
                    "text": "Which of these kinds and varieties hold for the sense of call forwarding this model covers, and on what evidence?",
                    "kind": "provenance"
                  }
                ]
              },
              {
                "id": "evidence-identifiers",
                "name": "Identifiers and schemes",
                "description": "Recalled without web access and unsourced; every item is a lead to verify.",
                "evidence": [
                  {
                    "scheme": "Mobile supplementary-service designations",
                    "value_or_pattern": "CFU, CFB, CFNRy, CFNRc",
                    "note": "Designate forwarding unconditional, on busy, on no reply, and on not reachable, respectively."
                  },
                  {
                    "scheme": "ITU-T E.164",
                    "value_or_pattern": "International telephone number of up to 15 digits",
                    "note": "Identifies forwarding destinations reachable through public numbering; private extensions and SIP addresses may also be used in applicable systems."
                  }
                ],
                "questions": [
                  {
                    "id": "evidence-identifiers-q01",
                    "text": "Which of these identifiers and schemes hold for the sense of call forwarding this model covers, and on what evidence?",
                    "kind": "provenance"
                  }
                ]
              },
              {
                "id": "evidence-standards-and-regulation",
                "name": "Standards and regulation",
                "description": "Recalled without web access and unsourced; every item is a lead to verify.",
                "evidence": [
                  "3GPP TS 22.082 specifies call-forwarding supplementary services at Stage 1.",
                  "3GPP TS 24.082 specifies Stage 3 signalling for call-forwarding supplementary services.",
                  "IETF RFC 3261 defines SIP, including redirection mechanisms used in IP telephony.",
                  "IETF RFC 7044 defines SIP History-Info for communicating request history, including retargeting."
                ],
                "questions": [
                  {
                    "id": "evidence-standards-and-regulation-q01",
                    "text": "Which of these standards and regulation hold for the sense of call forwarding this model covers, and on what evidence?",
                    "kind": "provenance"
                  }
                ]
              },
              {
                "id": "evidence-real-world-use",
                "name": "Real-world use",
                "description": "Recalled without web access and unsourced; every item is a lead to verify.",
                "evidence": [
                  "Route calls from an office number to a mobile phone.",
                  "Send unanswered or unreachable calls to voicemail.",
                  "Redirect calls to an answering service outside business hours.",
                  "Maintain contact when a user changes location or an endpoint becomes unavailable.",
                  "Route selected callers to an alternative destination."
                ],
                "questions": [
                  {
                    "id": "evidence-real-world-use-q01",
                    "text": "Which of these real-world use hold for the sense of call forwarding this model covers, and on what evidence?",
                    "kind": "provenance"
                  }
                ]
              },
              {
                "id": "evidence-measurements",
                "name": "Typical measurements",
                "description": "Recalled without web access and unsourced; every item is a lead to verify.",
                "evidence": [
                  {
                    "quantity": "No-answer interval before forwarding",
                    "typical_range": "Depends on the service and configuration",
                    "unit": "seconds"
                  },
                  {
                    "quantity": "Forwarded-call connection success rate",
                    "typical_range": "Deployment-dependent",
                    "unit": "%"
                  }
                ],
                "questions": [
                  {
                    "id": "evidence-measurements-q01",
                    "text": "Which of these typical measurements hold for the sense of call forwarding this model covers, and on what evidence?",
                    "kind": "provenance"
                  }
                ]
              },
              {
                "id": "evidence-failure-modes-and-hazards",
                "name": "Failure modes and hazards",
                "description": "Recalled without web access and unsourced; every item is a lead to verify.",
                "evidence": [
                  "Forwarding loops or excessive forwarding chains prevent completion.",
                  "An incorrect or obsolete destination sends calls to the wrong recipient.",
                  "Unauthorized changes divert calls, potentially exposing confidential conversations or voice-delivered authentication codes.",
                  "Forwarded call legs can incur unexpected charges, particularly across international or roaming routes.",
                  "Caller identity or forwarding-history information can be lost or displayed inconsistently across networks."
                ],
                "questions": [
                  {
                    "id": "evidence-failure-modes-and-hazards-q01",
                    "text": "Which of these failure modes and hazards hold for the sense of call forwarding this model covers, and on what evidence?",
                    "kind": "provenance"
                  }
                ]
              },
              {
                "id": "evidence-regional-variation",
                "name": "Regional variation",
                "description": "Recalled without web access and unsourced; every item is a lead to verify.",
                "evidence": [
                  "Activation codes, configuration methods, and available conditions differ among operators and telephone systems.",
                  "Charges and restrictions for domestic, international, and roaming-related forwarding vary by operator and jurisdiction.",
                  "Caller identification presentation on forwarded calls depends on network capabilities and applicable rules."
                ],
                "questions": [
                  {
                    "id": "evidence-regional-variation-q01",
                    "text": "Which of these regional variation hold for the sense of call forwarding this model covers, and on what evidence?",
                    "kind": "provenance"
                  }
                ]
              },
              {
                "id": "evidence-neighbours",
                "name": "Neighbouring kinds and how to tell them apart",
                "description": "Recalled without web access and unsourced; every item is a lead to verify.",
                "evidence": [
                  {
                    "name": "Call transfer",
                    "difference": "Transfer moves an already established or answered call to another party; forwarding redirects an incoming call under a service rule."
                  },
                  {
                    "name": "Call waiting",
                    "difference": "Call waiting alerts a busy subscriber to another incoming call rather than redirecting it."
                  },
                  {
                    "name": "Voicemail",
                    "difference": "Voicemail answers and records messages; forwarding can deliver a call to voicemail but does not itself record anything."
                  },
                  {
                    "name": "Simultaneous ringing",
                    "difference": "Simultaneous ringing alerts multiple destinations concurrently; forwarding redirects the call to an alternative destination."
                  },
                  {
                    "name": "Call routing",
                    "difference": "Routing broadly determines a call's path or destination; forwarding specifically redirects a call from its initially addressed destination."
                  }
                ],
                "questions": [
                  {
                    "id": "evidence-neighbours-q01",
                    "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of call forwarding this model covers, and on what evidence?",
                    "kind": "provenance"
                  }
                ]
              }
            ]
          }
        ]
      }
    ]
  },
  "openQuestions": [
    "Which authoritative sources should establish the shared definition of call forwarding across carrier, PBX and application services, and where do their definitions diverge?",
    "How do relevant implementations define busy and unreachable, particularly when call waiting, multiple registered devices or rejection features are active?",
    "Which rule precedence, forwarding-chain limits and destination-failure behaviours are documented for the services represented by this registry entry?",
    "Under which service and interconnection conditions are caller identity, original called identity and forwarding indications preserved or changed?",
    "Which destination restrictions, charge responsibilities and configuration verification mechanisms vary enough to require explicit service-specific extensions?"
  ],
  "statistics": {
    "bundles": 6,
    "layers": 11,
    "findings": 19,
    "questions": 30
  }
}
