@passioncode-ai/fabric-agent-adapter 0.32.1 → 0.34.0

package/CHANGELOG.md

@@ -1,5 +1,95 @@
 # Changelog
 
+## 0.34.0 - 2026-10-15
+
+The adapter is pinned at contract `d8146cf`. The profile kits now read what a lane reads (DEC-0083; FAA-45, contract
+CT-52): a model profile that reads what members, clients or the public send keeps an open-vendor model on its route,
+so the lane never runs on closed vendors alone, which refuse the content it exists to handle.
+
+### Changed
+
+- **Repin** from `82e1636` to `d8146cf`. Every vendored vector is byte-identical except `profile-vectors.json`.
+  `82e1636` stays a supported revision.
+- **`open-vendor` is descriptive** in `resolve_model_profile` / `resolveModelProfile` and in the doctor's `model_usable` /
+  `modelUsable`: a project's `modelClasses` never admit or exclude a model by it, and a model whose only class is
+  `open-vendor` is admitted on nothing. Both copies of the every-class rule answer the contract's shared
+  `model-admission.json` vectors.
+- **FAC-SEM-058 and FAC-SEM-060 are total on hostile input**, as the contract's became in DEC-0083's fix round: an
+  `instancePath` names an item by its index as written (a non-object before it no longer shifts it, and every model
+  counts at its own index), a duplicate id is what JavaScript's `Set` calls one (`1` and `true`, `null` and absent, are
+  two), and an id whose own `toString` member is data is shown as its JSON.
+
+### Added
+
+- **FAC-SEM-112** on a `profile-resolution`: a profile with `reads: ["user-content"]` has an open-vendor route — with
+  `fallback: none` its first model is `open-vendor` in the catalogue, with `between-turns` at least one is — and the
+  models the project's policy leaves must still give one, or the finding at `/resolved/models` names the policy.
+  `closed_user_content_route` / `closedUserContentRoute` name the models that would run on a closed route.
+- `creating-fabric-agents` asks in its grill which lanes read user content; `profile-selection.md` and the profiles
+  reference say how such a lane is declared and routed, and that a content refusal or an empty answer is a failed turn.
+
+### Fixed
+
+- **`make_profile_vectors.mjs` read the contract's newer fixtures vacuously.** Since DEC-0083 a profile fixture wraps
+  its document as `{description, kind, expect, input}`; the generator fed the wrapper to the rules, so every expectation
+  came out empty and the Node test passed without checking anything. It now unwraps them and stops when a fixture's own
+  `expect` disagrees with the contract's answer.
+- `resolve_model_profile` takes `catalogue` and `profiles` as optional, as the contract's resolver does, so an absent
+  catalogue resolves instead of raising.
+
+### Evidence
+
+- Both kits answer 72 rule cases (45 crafted: FAC-SEM-112 edges, the policy's outcome, hostile ids and indexes), 81
+  resolutions and 8 admission cases.
+- 51 planted defects (30 in Python, 21 in Node), all caught but two that cannot differ on JSON input: a redundant
+  type check, now removed from the code, and the Node message of a duplicate object id, which parsed JSON never
+  produces. A unit test covers `1` and `1.0` as one id, a case JSON written by JavaScript cannot hold.
+- Eval scenarios `lanes-that-read-user-content` and `user-content-open-vendor-route`.
+
+## 0.33.0 - 2026-10-15
+
+The adapter is pinned at contract `82e1636`. The estate kits now read contexts (DEC-0082; FAA-41, the RM-28 pilot): one
+agent placed on a machine for the person and for each organization it serves. Before this, at the old pin, a record
+placing one agent in two contexts was refused as a duplicate placement (FAC-SEM-074), and an organization's instance
+was checked against no share grant.
+
+### Changed
+
+- **Repin** from `1636fa9` to `82e1636`. Every vendored vector is byte-identical except `estate-vectors.json`.
+  `1636fa9` stays a supported revision.
+- **Placement and slot keys** in `fabric_estate.py` / `fabric-estate.mjs` carry the context: a placement is keyed by
+  agent and context (FAC-SEM-074), a secret slot by agent, slot and context (FAC-SEM-075). A secret fills a slot of an
+  agent placed in its own context. An absent `context` is `personal`; `null` is not absent.
+- **`placement_trust(record, machine, agentRef, context="personal")`** / `placementTrust(…, context)` answer for the
+  placement in that context. A caller that passes none gets the personal placement, as before.
+- **`estate-placement`** takes `{record, machine, package, context?}` and checks the placement in that context.
+
+### Added
+
+- **FAC-SEM-110**: a share grant (`principalKind: external`) is never in the `personal` context. Checked on each of an
+  estate record's `shareGrants[]`, and on a grant of its own with `grant_context_findings` / `grantContextFindings`.
+- **FAC-SEM-111**: an organization's placement names, in `grant`, a share grant of the record whose `context` is the
+  placement's, as written, and that the record does not revoke; a personal placement names none; a context that is not
+  `org:<orgId>` fails closed. Checked on a record and on an installation.
+- **An organization's slot is filled from its own machine**: an envelope names no context (FAC-SEM-075).
+- **`parse_context` / `parseContext`**: `personal`, `org:<orgId>` (`[A-Za-z0-9][A-Za-z0-9_-]{0,127}`), or nothing,
+  compared as written.
+
+### Fixed
+
+- **Every estate rule is total on hostile JSON**, as the contract's became in DEC-0082's fix rounds: an
+  `instancePath` names an item by its index as written (a non-object before it no longer shifts it), and a value whose
+  own `toString` member is data is shown as its JSON instead of throwing.
+- **A flaky board test** (FAA-43): the hold test of `com.effect_begin` lifted the hold on a 50 ms timer, so a slow runner
+  saw one begin instead of two. The fake board now lifts it right after the first held begin (`lift_holds_after`), in
+  the Python and the Node twin.
+
+### Evidence
+
+- Both kits answer 115 contract rule cases (19 hostile, built by `make_estate_vectors.mjs` from the contexts fixture),
+  28 grant-context cases and 19 `placementTrust` cases.
+- 28 planted defects, 14 per kit, all caught.
+- A new eval scenario, `estate-contexts`.
 ## 0.32.1 - 2026-10-14
 
 The `building-fabric-services` lifecycle reference is now the rule its readers follow (release iteration 1, N-12;

package/README.md

@@ -251,7 +251,7 @@ Scaffolding is non-destructive by default. It writes only the paths declared in
 The default pin for new bundles is [`fabric-contract.lock.json`](fabric-contract.lock.json):
 
 - version: `0.1.0`
-- commit: `1636fa97262f4a26e2086572d540c2ee701e0010`
+- commit: `d8146cfb0a1c74fc6432284c4356bb0c864b37b5`
 
 Every other mention of the default contract revision — this section, the skills' metadata, the
 skill card, `adapt_project.py` — must equal it; `python3 test/validate.py` fails a tree

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@passioncode-ai/fabric-agent-adapter",
-  "version": "0.32.1",
+  "version": "0.34.0",
   "description": "Create Fabric-compatible agents, run them as always-alive local services with dashboards (fabric-service/0.1), and adapt existing projects to the Fabric Agent Contract. This package is the installer CLI.",
   "scripts": {
     "test": "python3 test/validate.py && python3 -m unittest discover -s test -q && node --test 'test/*.test.mjs'"

package/plugins/fabric-agent-adapter/.claude-plugin/plugin.json

@@ -3,7 +3,7 @@
   "name": "fabric-agent-adapter",
   "displayName": "Fabric Agent Adapter",
   "description": "Create new Fabric-compatible agents, build them as always-alive local services with dashboards (fabric-service/0.1), and adapt existing projects to the Fabric Agent Contract through evidence-backed MCP, A2A, or local-runner provider bundles; and teach a coding agent to work in a project through Fabric (fabric-mcp, fabric_whoami, claim and release), with Claude Code session hooks.",
-  "version": "0.32.1",
+  "version": "0.34.0",
   "author": {
     "name": "PassionCode.ai",
     "url": "https://passioncode.ai/"

package/plugins/fabric-agent-adapter/skills/adapting-projects-to-fabric/SKILL.md

@@ -5,9 +5,9 @@ license: AGPL-3.0-only OR LicenseRef-PassionCode-Commercial
 compatibility: Requires filesystem access and Python 3.9+. Exact schema checks additionally need git, Node.js, pnpm, and the pinned fabric-agent-contract checkout (a public repository). Works without those tools in an explicitly degraded structural-check mode.
 metadata:
   author: PassionCode.ai
-  version: "0.32.1"
+  version: "0.34.0"
   contract-version: "0.1.0"
-  contract-commit: "1636fa97262f4a26e2086572d540c2ee701e0010"
+  contract-commit: "d8146cfb0a1c74fc6432284c4356bb0c864b37b5"
 ---
 
 # Adapting projects to Fabric
@@ -70,7 +70,7 @@ Use exactly:
 
 - contract version `0.1.0`;
 - repository `https://github.com/passioncode-ai/fabric-agent-contract`;
-- commit `1636fa97262f4a26e2086572d540c2ee701e0010`.
+- commit `d8146cfb0a1c74fc6432284c4356bb0c864b37b5`.
 
 This is the default for new bundles. When checking an issued legacy bundle, preserve its
 explicit supported lock and use that exact clean checkout. Never silently upgrade or

package/plugins/fabric-agent-adapter/skills/adapting-projects-to-fabric/references/profile-selection.md

@@ -57,7 +57,10 @@ Use when Fabric launches an installed process such as a coding CLI. Require:
 - project-scoped account selection outside the manifest.
 
 The user may choose the project's default terminal and override it per agent. Model choice
-stays inside the selected agent/provider; the Fabric profile remains model-agnostic.
+stays inside the selected agent/provider; the Fabric profile remains model-agnostic. The one
+exception is a lane that reads what members, clients or the public send: its model profile
+declares `reads: ["user-content"]` and has an open-vendor route (contract DEC-0083,
+FAC-SEM-112), whichever models the agent picks.
 
 ## Reject or defer
 

package/plugins/fabric-agent-adapter/skills/adapting-projects-to-fabric/scripts/adapt_project.py

@@ -21,10 +21,10 @@ import fabric_secrets as _secrets  # noqa: E402 - the contract's credential dete
 
 CONTRACT_VERSION = "0.1.0"
 CONTRACT_REPOSITORY = "https://github.com/passioncode-ai/fabric-agent-contract"
-CONTRACT_COMMIT = "1636fa97262f4a26e2086572d540c2ee701e0010"
+CONTRACT_COMMIT = "d8146cfb0a1c74fc6432284c4356bb0c864b37b5"
 # #region supported-contract-revisions — docs: README.md#contract-pin
 # Only this declaration may name a legacy revision in live files.
-SUPPORTED_CONTRACT_COMMITS = (CONTRACT_COMMIT, "f00a7685e3861c27f7899c033fb850a145a1708f", "a046f57cf46ea9e3da57ff8ce6a3ed4d26d8774b", "fe55fc67cba1a9e34a736da7d148d4fe2a8fbfa0", "b291bf09e0a9f9fd3c16cf540832cd021203b7d1", "0cacd08b0e95b6abf131eae1206b60792138bc3c", "2eb91c00e852d9c31d804310d38fad91589fcbac", "8e49fbd5fbbf230e32c1969cd24ac3c22422f0a5", "a83bec6b47776af688402c18efec507143061f68", "52da526d7cc1e063d74c5b520dbc03d0ace15246", "78b2da018d2c4bd9ac1bde1dc3b7f1a110a175f5", "623bf61358c339cb10297807b3f024b5d9f1f327", "23f9fda4c05f8a3852246ee98d4f2adf74ed0875", "9091d3d6606b0c4b5591a38c3674356a01fd7f55", "df55c8c54a23251342a7ee57ba95642b7eb39e61", "2ce392291c6668598d12cd38327e24696b5ca15c")
+SUPPORTED_CONTRACT_COMMITS = (CONTRACT_COMMIT, "82e163665e156a08aa3b92e4711015582c06162c", "1636fa97262f4a26e2086572d540c2ee701e0010", "f00a7685e3861c27f7899c033fb850a145a1708f", "a046f57cf46ea9e3da57ff8ce6a3ed4d26d8774b", "fe55fc67cba1a9e34a736da7d148d4fe2a8fbfa0", "b291bf09e0a9f9fd3c16cf540832cd021203b7d1", "0cacd08b0e95b6abf131eae1206b60792138bc3c", "2eb91c00e852d9c31d804310d38fad91589fcbac", "8e49fbd5fbbf230e32c1969cd24ac3c22422f0a5", "a83bec6b47776af688402c18efec507143061f68", "52da526d7cc1e063d74c5b520dbc03d0ace15246", "78b2da018d2c4bd9ac1bde1dc3b7f1a110a175f5", "623bf61358c339cb10297807b3f024b5d9f1f327", "23f9fda4c05f8a3852246ee98d4f2adf74ed0875", "9091d3d6606b0c4b5591a38c3674356a01fd7f55", "df55c8c54a23251342a7ee57ba95642b7eb39e61", "2ce392291c6668598d12cd38327e24696b5ca15c")
 # #endregion supported-contract-revisions
 INTEROP_KEY = "https://fabric.passioncode.ai/agent-contract/extensions/interop/0.1"
 MCP_REVISION = "2026-07-28"

package/plugins/fabric-agent-adapter/skills/building-fabric-services/SKILL.md

@@ -18,10 +18,10 @@ license: AGPL-3.0-only OR LicenseRef-PassionCode-Commercial
 compatibility: Python 3.9+ or Node.js 20+ for the kits; the probe needs Python 3.9+. launchd steps are macOS-only; Linux services install a systemd user unit and Windows ones a per-user Scheduled Task with the kits' writers. Dashboard handoff optionally uses Fabric Dashboards MCP link/host_status/open; without it, report unresolved host capability. The contract checkout is optional.
 metadata:
   author: PassionCode.ai
-  version: "0.32.1"
+  version: "0.34.0"
   contract-version: "0.1.0"
   extension: "fabric-service/0.1"
-  extension-commit: "1636fa97262f4a26e2086572d540c2ee701e0010"
+  extension-commit: "d8146cfb0a1c74fc6432284c4356bb0c864b37b5"
 ---
 
 # Building Fabric services
@@ -86,7 +86,8 @@ are in [`scripts/fabric_interop.py`](scripts/fabric_interop.py) and
 service checks each call's delegation token (DEC-0039): read [the delegation reference](references/delegation.md);
 the verifier is [`scripts/fabric_delegation.py`](scripts/fabric_delegation.py) /
 [`scripts/fabric-delegation.mjs`](scripts/fabric-delegation.mjs). A service on the operator's machines that
-applies the estate record (DEC-0055) verifies each revision first and trusts only the keys it certifies: read
+applies the estate record (DEC-0055) verifies each revision first and trusts only the keys it certifies, and runs an
+agent once per context, the person's or an organization's (DEC-0082): read
 [the estate record reference](references/estate-record.md). When Fabric chooses the service's runner and models
 (DEC-0046), or a project routes its work through an ordered list of runners (DEC-0026: the doctor's closed probe
 results, the route checks FAC-SEM-028…034), read [the profiles reference](references/profiles.md).

package/plugins/fabric-agent-adapter/skills/building-fabric-services/references/estate-record.md

@@ -1,10 +1,11 @@
 # The estate record — what the operator's machines are, signed by their passkey (DEC-0055)
 
 Fabric Agent Contract DEC-0055, `docs/specification/estate-record.md`, schema `schemas/estate-record.schema.json`,
-rules `FAC-SEM-072…076`. One revision of one person's estate lists:
+rules `FAC-SEM-072…076`, with contexts (DEC-0082, `docs/specification/contexts.md`, `FAC-SEM-110`, `FAC-SEM-111`).
+One revision of one person's estate lists:
 - the passkeys that sign it;
 - the machines, with their device keys and a certificate of each machine's hub key;
-- the packages placed on each machine;
+- the packages placed on each machine, each in a context: the person's own, or an organization's;
 - where each secret slot is filled from (by reference only);
 - share grants and revocations.
 
@@ -16,6 +17,7 @@ derived from its own digest. Python: [`scripts/fabric_estate.py`](../scripts/fab
 
 - Applying a revision
 - Trusting a delegation key
+- Contexts: one agent for you and for an organization
 - Checking a record you produce
 - What the kit does not do
 
@@ -51,7 +53,8 @@ It checks, in the order of the ER table:
    - The signature: ES256 or EdDSA, under a key validated first (a valid P-256 point; an Ed25519 key of full order).
 7. **The window.** At most 30 days. A revision may be issued up to 60 s ahead of the verifier's clock (DEC-0066,
    `CLOCK_SKEW_SECONDS`); earlier than that it is `not-yet-valid`.
-8. **The record's own rules.** A violation is `rule-violation` with its `codes`, `FAC-SEM-072…076` and `FAC-SEM-092`
+8. **The record's own rules.** A violation is `rule-violation` with its `codes`, `FAC-SEM-072…076`, `FAC-SEM-110`,
+   `FAC-SEM-111` and `FAC-SEM-092`
    (each passkey the record lists is a signing credential, its origins within its RP ID).
 
 Dates are strict RFC 3339: a `T`, an offset, and a day that exists. `:60` and a space are refused. Passkey JWK `x`
@@ -90,14 +93,40 @@ gate = fd.delegation_gate(audience=..., jwks=keys, issuer=..., effects=..., esta
   `{certified: true, machine, revision}` or `{certified: false, fault, detail}`. Both kits are held to the contract's
   `fixtures/vectors/hub-key.json` (`test/fixtures/contract/hub-key-vectors.json`).
 
+## Contexts: one agent for you and for an organization
+
+A placement and a secret placement carry a `context` (DEC-0082): `personal`, or `org:<orgId>` with an organization id
+of `[A-Za-z0-9][A-Za-z0-9_-]{0,127}`. Absent is `personal`; `null` is not absent. A context is compared as written:
+`Personal`, `ORG:x` or a trailing newline names no context. `parse_context(value)` / `parseContext(value)` answer
+`{kind: "personal"}`, `{kind: "org", org}` or nothing.
+
+- **One agent, once per context.** A machine may place the same `agentRef` for the person and for each organization;
+  placements are keyed by agent and context (FAC-SEM-074), and a secret slot by agent, slot and context (FAC-SEM-075).
+  A secret fills a slot of an agent placed on that machine in the secret's own context.
+- **An organization's instance runs under a share grant** (FAC-SEM-111). Its placement names, in `grant`, a share grant
+  of the record whose `context` is the placement's, as written, and that the record does not revoke. A personal
+  placement names no grant. A context that is not `org:<orgId>` matches no grant, so it fails closed.
+- **An organization's slot is filled from its own machine.** An envelope names no context, so a secret placed in an
+  organization's context has `from` equal to the machine it sits on (FAC-SEM-075).
+- **A share grant is never personal** (FAC-SEM-110). A grant to a principal outside the estate (`principalKind:
+  external`) is used in that principal's organization; `context: "personal"` on it is a finding, and an absent one
+  means not stated. `grant_context_findings(grant, at)` / `grantContextFindings(grant, at)` check one grant on its own.
+
+Every rule is total on hostile JSON, as the contract's are: an `instancePath` names an item by its index as written (a
+non-object before it does not shift it), and a value whose own `toString` member is data is shown as its JSON. Both kits
+answer the contract's contexts fixtures and variants of them (`test/fixtures/contract/estate-vectors.json`).
+
 ## Checking a record you produce
 
 `estate_record_rules(kind, value)` / `estateRecordRules(kind, value)` are the contract's rules, finding for finding:
-- `estate-record` (FAC-SEM-072…076);
+- `estate-record` (FAC-SEM-072…076, 110, 111);
 - `estate-record-revision` `{parent, next}` (072);
-- `estate-placement` `{record, machine, package}` (074, 075).
+- `estate-placement` `{record, machine, package, context?}` (074, 075, 111): the package placed on that machine in that
+  context, `personal` when `context` is absent.
 
-`placement_trust(record, machine, agentRef)` names the publisher keys a package verifier trusts for a placed package.
+`placement_trust(record, machine, agentRef, context="personal")` / `placementTrust(record, machine, agentRef, context)`
+names the publisher keys a package verifier trusts for the package placed in that context. A caller that passes no
+context gets the personal placement, as before contexts.
 
 ## What the kit does not do
 

package/plugins/fabric-agent-adapter/skills/building-fabric-services/references/profiles.md

@@ -11,6 +11,7 @@ Python: [`scripts/fabric_profiles.py`](../scripts/fabric_profiles.py); Node:
 
 - Resolving the model profile
 - Checking the documents
+- A lane that reads user content
 - Declaring and showing what applies
 - The doctor
 - Runner routes
@@ -27,7 +28,8 @@ resolution = fp.resolve_model_profile(catalogue=catalogue, profiles=estate_and_a
 
 The first level that names a profile wins: **request, agent, binding or project, estate default**. The project's
 `modelClasses` narrow the profile's models — a model stays only if every class the catalogue gives it is allowed — and
-never choose one. An empty result is `{"refused": "model-classes-empty", "policy": {id, revision}}`: refuse the launch
+never choose one. `open-vendor` is descriptive (DEC-0083): it is never checked against the policy, and a model whose
+only class is `open-vendor` does not stay. An empty result is `{"refused": "model-classes-empty", "policy": {id, revision}}`: refuse the launch
 and name the policy; never fall back to a model outside it. No level at all is `no-profile`; an id nobody offers is
 `unknown-profile`.
 
@@ -39,6 +41,27 @@ and name the policy; never fall back to a model outside it. No level at all is `
 Code, Kimi in Kimi Code, ChatGPT in Codex; a key route's allow-list is its own model profile; a key named by reference,
 never by value) and a recorded `profile-resolution` (it equals the order's answer).
 
+## A lane that reads user content
+
+A model profile names what the lane it serves reads (DEC-0083, `reads`): `user-content` — what a member, a client or
+the public sends (messages, questions, images, reviews, screenshots, voice); `operator` — only what the estate's own
+operator or its agents write; `web` — pages fetched from the open web. Absent is "not declared", which stays valid.
+
+A profile that reads `user-content` has an **open-vendor route** (FAC-SEM-112): with `fallback: none` (or any value the
+contract does not name) its first model is `open-vendor` in the catalogue; with `between-turns` at least one of its
+models is. Closed vendors refuse the content such a lane exists to handle, so a closed route alone skips the worst of
+it. Which models are `open-vendor` is the catalogue writer's fact; the service never keeps a vendor list of its own,
+and a model the catalogue does not hold counts as closed.
+
+- `profile_problems("profile-resolution", doc)` / `profileProblems(...)` answer FAC-SEM-112 beside FAC-SEM-060, on each
+  profile (`/profiles/<i>/models`) and on the resolution's outcome: when the resolved profile's own route is open but the
+  models the project's policy leaves are all closed, the finding is at `/resolved/models` and names the policy.
+- `closed_user_content_route(profile, catalogue)` / `closedUserContentRoute(profile, catalogue)` name the models that
+  would run on such a lane when none is open-vendor, or `None`/`undefined` when the route holds.
+- On such a lane a content refusal, or an empty answer to a non-empty request, is a **failed turn**: under
+  `between-turns` the runner moves to the next model; it never counts that answer as done.
+- `operator` and `web` carry no model rule in this revision; they let a lane say that it reads no user content.
+
 ## Declaring and showing what applies
 
 ```python
@@ -57,7 +80,8 @@ declaration (`configuration.declared`).
 and answers whether the runner is installed, which version answers and whether it is signed in. It runs only a bare
 catalogued binary found on `PATH`, only with the catalogued version argv (and `auth` argv), without a shell, within
 the entry's timeout (at most 5 s); an entry outside these rules is refused and nothing runs. `model_usable(model,
-catalogue, policy)` names why a model cannot be used here: not catalogued, or a class the project does not allow.
+catalogue, policy)` names why a model cannot be used here: not catalogued, a class the project does not allow, or
+only `open-vendor`, which admits nothing — the same admission the resolution applies.
 
 `probe` is the contract's closed probe result for that runner, the one Fabric's walk records (DEC-0026):
 `not-installed` (no catalogued binary on `PATH`), `not-responding` (the version probe did not answer in its bound,

package/plugins/fabric-agent-adapter/skills/building-fabric-services/references/protocol.md

@@ -1,6 +1,6 @@
 # fabric-service/0.1 — wire reference
 
-Pinned to `fabric-agent-contract` commit `1636fa97262f4a26e2086572d540c2ee701e0010`
+Pinned to `fabric-agent-contract` commit `d8146cfb0a1c74fc6432284c4356bb0c864b37b5`
 (`docs/specification/service.md`, DEC-0015; the usage report DEC-0021; Windows and Linux supervision
 DEC-0032 and DEC-0033; the operator channel DEC-0034 and DEC-0035; the embedded dashboard DEC-0036;
 delegation and the operator session's lifetime DEC-0039; the meter's call window DEC-0041; session handoff DEC-0042;