> For the complete documentation index, see [llms.txt](https://faction-os.gitbook.io/faction-os-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://faction-os.gitbook.io/faction-os-docs/.spec_system/archive/sessions/phase08-session02-unified-erasure-contract-and-inventory/implementation-notes.md). # Implementation Notes **Session ID**: `phase08-session02-unified-erasure-contract-and-inventory` **Package**: Cross-cutting **Started**: 2026-05-31 00:47 **Last Updated**: 2026-05-31 02:20 *** ## Session Progress | Metric | Value | | ------------------- | ------- | | Tasks Completed | 24 / 24 | | Estimated Remaining | 0 hours | | Blockers | 0 | *** ## Task Log ### 2026-05-31 - Session Start **Environment verified**: * [x] Bundled analyzer script confirmed current session `phase08-session02-unified-erasure-contract-and-inventory` * [x] Prerequisites confirmed with bundled `check-prereqs.sh --json --env` * [x] Directory structure ready * [x] Cross-cutting package context confirmed * [x] No database layer configured for this session *** ### Task T001 - Verify analyzer state and Phase 08 routing **Started**: 2026-05-31 00:46 **Completed**: 2026-05-31 00:47 **Duration**: 1 minute **Notes**: * Analyzer state resolved current phase 8 and current session `phase08-session02-unified-erasure-contract-and-inventory`. * Session 01 is listed as completed in `.spec_system/state.json` and the analyzer output. * Phase 08 routing matrix assigns unified erasure contract and inventory work to S0802. * Spec package field is `Cross-cutting`, so protocol, server, Worker, docs, and Phase 08 artifacts are in scope. **Files Changed**: * `.spec_system/specs/phase08-session02-unified-erasure-contract-and-inventory/implementation-notes.md` - Created implementation log scaffold and recorded environment verification. **BQC Fixes**: * Not applicable - setup verification only. *** ### Task T002 - Review storage and non-erasure boundaries **Started**: 2026-05-31 00:47 **Completed**: 2026-05-31 00:49 **Duration**: 2 minutes **Notes**: * Reviewed `docs/privacy-and-security.md`, `docs/release.md`, `docs/api/README_api.md`, server README, Worker README, protocol README, and relevant ADRs. * Confirmed current cleanup and recovery flows are narrow: browser reset clears browser context only, Worker leave/disconnect clears browser socket or local context only, diagnostics recovery removes stale listener PID files and malformed spool entries only, and CLI uninstall restores or removes hook settings only. * Confirmed current storage boundaries include local memory, settings, lifecycle, project root, sessions, logs, backups, valid spool entries, browser localStorage, replay fragments, exports, archives, scan/runtime memory, Worker Durable Object participants, recent events, authority hashes, idempotency metadata, and future hosted placeholders. * Confirmed docs already require Phase 08 Session 02/03/04 evidence before any trusted unified erasure claim. **Files Changed**: * `.spec_system/specs/phase08-session02-unified-erasure-contract-and-inventory/implementation-notes.md` - Recorded boundary review. **BQC Fixes**: * Trust boundary enforcement: Review established that later contract output must expose labels, docs paths, counts, and booleans only, not raw paths, tokens, payloads, logs, backups, exports, replay buffers, diagnostics, or room data. *** ### Task T003 - Create implementation notes and confirm non-destructive scope **Started**: 2026-05-31 00:47 **Completed**: 2026-05-31 00:49 **Duration**: 2 minutes **Notes**: * Created this implementation note scaffold before code edits. * Confirmed this session will add contracts, inventory, read-only mappers, tests, and documentation only. * Confirmed this session will not add destructive deletion, purge, reset, clear, Worker room deletion, local/browser erasure controls, or end-user trusted-erasure UX. **Files Changed**: * `.spec_system/specs/phase08-session02-unified-erasure-contract-and-inventory/implementation-notes.md` - Added task log and non-destructive scope confirmation. **BQC Fixes**: * Failure path completeness: Established up front that any later helper must represent unsupported and planned states explicitly instead of silently treating incomplete coverage as erasure. *** ### Task T004 - Create protocol erasure vocabulary and unsupported claims **Started**: 2026-05-31 00:49 **Completed**: 2026-05-31 01:02 **Duration**: 13 minutes **Notes**: * Added `packages/protocol/src/erasure.ts` with shared Phase 08 docs paths, boundary families, owners, statuses, authority labels, dry-run labels, confirmation labels, partial-failure labels, audit labels, verification labels, blocked payload labels, unsupported claims, and negative-claim action labels. * Added guard helpers for each exported vocabulary and an exhaustive `assertNeverErasure` helper. **Files Changed**: * `packages/protocol/src/erasure.ts` - Added protocol-owned erasure vocabulary and type guards. **BQC Fixes**: * Contract alignment: Centralized literal arrays and guards prevent package-specific erasure string drift. *** ### Task T005 - Add release-scoped storage-boundary inventory rows **Started**: 2026-05-31 01:02 **Completed**: 2026-05-31 01:05 **Duration**: 3 minutes **Notes**: * Added inventory rows for local home, archives, memory, settings, lifecycle, project-root state, logs, backups, valid and malformed spool posture, exports, diagnostics, scan/runtime memory, browser settings, replay, War Room hints, auth hints, Worker Durable Object state, workspace files, and future hosted placeholders. * Each row carries owner, status, authority, dry-run, confirmation, verification, audit, docs, blocked payload labels, release handoff scope, and no-overclaim wording. **Files Changed**: * `packages/protocol/src/erasure.ts` - Added `ERASURE_STORAGE_BOUNDARY_INVENTORY` and row metadata. **BQC Fixes**: * Trust boundary enforcement: Inventory rows carry blocked payload labels and warnings so raw path, token, room, log, backup, export, replay, diagnostic, and workspace contents remain out of summaries. *** ### Task T006 - Add summary builders, lookups, guards, and negative-claim helpers **Started**: 2026-05-31 01:05 **Completed**: 2026-05-31 01:08 **Duration**: 3 minutes **Notes**: * Added deterministic inventory summary builders sorted by boundary id. * Added lookup helpers, summary counts, `classifyErasureUnsupportedClaim`, and `canClaimTrustedUnifiedErasure`. * Summary output exposes labels, docs paths, counts, booleans, statuses, and blocked category names only. **Files Changed**: * `packages/protocol/src/erasure.ts` - Added summary and negative-claim helpers. **BQC Fixes**: * Error information boundaries: Negative-claim helper returns stable unsupported-claim labels and docs paths rather than raw runtime details. *** ### Task T007 - Export erasure contract from protocol barrel **Started**: 2026-05-31 01:08 **Completed**: 2026-05-31 01:09 **Duration**: 1 minute **Notes**: * Exported the new erasure contract module through the package barrel. * Consumers can now import erasure vocabulary and helpers from `@factionos/protocol`. **Files Changed**: * `packages/protocol/src/index.ts` - Added `export * from "./erasure.js";`. **BQC Fixes**: * Contract alignment: Prevents server and Worker adapters from duplicating protocol internals. *** ### Task T008 - Create read-only server erasure inventory mapper **Started**: 2026-05-31 01:09 **Completed**: 2026-05-31 01:16 **Duration**: 7 minutes **Notes**: * Added a server-local inventory adapter that derives summaries from protocol inventory rows. * The adapter covers FactionOS home, session archives, memory, settings, lifecycle, project-root state, logs, backups, valid and malformed spool posture, exports, diagnostics, scan runtime memory, and LLM runtime memory. * The adapter accepts optional presence/count inputs but does not inspect filesystem paths, read payloads, delete files, clear state, or expose raw paths. **Files Changed**: * `apps/server/src/lib/erasureInventory.ts` - Added read-only server erasure inventory snapshot and boundary helpers. **BQC Fixes**: * Resource cleanup: No resources are acquired by the mapper. * Trust boundary enforcement: Output exposes location labels and counts only, with `rawPathsExposed: false`, `readsPayloads: false`, and `mutatesFilesystem: false`. * Failure path completeness: Unknown presence is explicit when callers do not provide boundary state. *** ### Task T009 - Create read-only Worker erasure inventory mapper **Started**: 2026-05-31 01:16 **Completed**: 2026-05-31 01:22 **Duration**: 6 minutes **Notes**: * Added a Worker inventory adapter for Durable Object participants, recent events, authority hash metadata, idempotency metadata, room revisions, and browser-hint adjacency. * The adapter accepts optional counts and stale/duplicate metadata but never reads room payloads, exposes raw authority tokens or hashes, mutates Durable Object storage, or claims destructive runtime. **Files Changed**: * `apps/warroom/src/erasureInventory.ts` - Added read-only Worker erasure inventory snapshot and boundary helpers. **BQC Fixes**: * Trust boundary enforcement: Worker snapshot carries explicit `rawAuthorityTokensExposed: false`, `rawAuthorityHashesExposed: false`, and `rawRoomPayloadsExposed: false`. * Concurrency safety: Room revision and idempotency metadata are treated as inventory labels/counts only, not mutation or replay controls. * Error information boundaries: Snapshot output uses storage labels and counts, not request bodies, room payloads, client details, or authority values. *** ### Task T010 - Write protocol vocabulary and guard tests **Started**: 2026-05-31 01:22 **Completed**: 2026-05-31 01:27 **Duration**: 5 minutes **Notes**: * Added Vitest coverage for unique erasure vocabulary arrays, docs paths, blocked payload labels, unsupported claims, and guard helpers. **Files Changed**: * `packages/protocol/tests/erasure.test.ts` - Added protocol vocabulary and guard tests. **BQC Fixes**: * Contract alignment: Tests detect duplicate labels and missing guard coverage. *** ### Task T011 - Write protocol inventory completeness tests **Started**: 2026-05-31 01:27 **Completed**: 2026-05-31 01:30 **Duration**: 3 minutes **Notes**: * Added coverage for archives, memory, settings, lifecycle, browser state, Worker state, replay/export buffers, diagnostics, logs, backups, valid spool, workspace files, and future hosted placeholders. * Tests verify each row has owner, status, authority, dry-run, confirmation, verification, audit, docs, blocked payload labels, and no-overclaim wording. **Files Changed**: * `packages/protocol/tests/erasure.test.ts` - Added inventory completeness tests. **BQC Fixes**: * Contract alignment: Tests compare required release boundary ids to exported inventory ids. *** ### Task T012 - Write protocol negative-claim tests **Started**: 2026-05-31 01:30 **Completed**: 2026-05-31 01:32 **Duration**: 2 minutes **Notes**: * Added tests proving browser reset, Worker leave, diagnostics recovery, CLI uninstall, manual file removal, local archive cleanup, valid spool cleanup, and one-boundary cleanup cannot be classified as trusted unified erasure. **Files Changed**: * `packages/protocol/tests/erasure.test.ts` - Added negative-claim helper tests. **BQC Fixes**: * Failure path completeness: Unsupported claims return explicit stable reasons and docs paths. *** ### Task T013 - Write server inventory tests **Started**: 2026-05-31 01:32 **Completed**: 2026-05-31 01:38 **Duration**: 6 minutes **Notes**: * Added server helper tests for FactionOS home, archives, memory, settings, lifecycle, project-root state, logs, backups, valid/malformed spool posture, exports, diagnostics, scans, and runtime memory. * Tests verify summaries are sanitized, counts are bounded, and temporary marker files are not mutated. **Files Changed**: * `apps/server/tests/erasureInventory.test.ts` - Added read-only server inventory tests. **BQC Fixes**: * Resource cleanup: Tests use a temp marker file and assert the helper leaves it untouched. * Trust boundary enforcement: Tests assert raw paths, prompt text, backup payloads, export payloads, and diagnostic payloads are absent. * Failure path completeness: Tests assert unknown and malformed counts remain explicit and bounded. *** ### Task T014 - Write Worker inventory tests **Started**: 2026-05-31 01:38 **Completed**: 2026-05-31 01:44 **Duration**: 6 minutes **Notes**: * Added Worker helper tests for Durable Object participants, recent events, authority hash metadata, idempotency metadata, stale authority records, duplicate decision records, room revisions, and browser-hint adjacency. * Tests assert no raw authority tokens, authority hashes, room payloads, prompt bodies, or local paths appear in serialized output. **Files Changed**: * `apps/warroom/tests/erasureInventory.test.ts` - Added read-only Worker inventory tests. **BQC Fixes**: * Trust boundary enforcement: Tests assert raw token/hash/payload exclusion. * Concurrency safety: Tests keep idempotency and room revision data as metadata counts only. * Failure path completeness: Tests assert absent and unknown Worker state remains explicit without erasure claims. *** ### Task T015 - Create unified erasure inventory artifact **Started**: 2026-05-31 01:44 **Completed**: 2026-05-31 01:51 **Duration**: 7 minutes **Notes**: * Added the Phase 08 human-readable inventory artifact with every release-scoped local, browser, Worker, workspace, and future hosted boundary. * Captured owner, status, authority, dry-run expectation, verification plan, non-erasure examples, blocked payload categories, and Session 03/04/08 handoff notes. **Files Changed**: * `.spec_system/PRD/phase_08/unified_erasure_inventory.md` - Created release-scoped trusted-erasure inventory artifact. **BQC Fixes**: * Error information boundaries: Artifact lists blocked payload categories and safe-output limits without including raw examples. * Contract alignment: Artifact points back to protocol-owned `packages/protocol/src/erasure.ts`. *** ### Task T016 - Update privacy and security documentation **Started**: 2026-05-31 01:51 **Completed**: 2026-05-31 01:55 **Duration**: 4 minutes **Notes**: * Added Phase 08 erasure inventory posture to privacy/security docs. * Documented that `P06-S07-ERASURE` remains open and that reset, leave, diagnostics recovery, uninstall, manual file removal, archive deletion, export deletion, backup pruning, and one-boundary cleanup are not trusted unified erasure. **Files Changed**: * `docs/privacy-and-security.md` - Added inventory reference, cleanup-vs-erasure wording, and personal-data boundary posture. **BQC Fixes**: * Error information boundaries: Docs name blocked categories and safe labels without raw local values. * Contract alignment: Privacy docs now point to the protocol contract and inventory artifact. *** ### Task T017 - Update release documentation **Started**: 2026-05-31 01:55 **Completed**: 2026-05-31 01:57 **Duration**: 2 minutes **Notes**: * Added release-gate wording for Session 02 erasure contract evidence. * Documented that the new protocol, server, Worker, and inventory artifacts prove inventory/read-only summary posture only, not deletion or trusted erasure. **Files Changed**: * `docs/release.md` - Added Phase 08 Session 02 evidence and no-claim release wording. **BQC Fixes**: * Contract alignment: Release docs separate inventory evidence from runtime deletion evidence. *** ### Task T018 - Update API documentation **Started**: 2026-05-31 01:57 **Completed**: 2026-05-31 02:00 **Duration**: 3 minutes **Notes**: * Added API docs section clarifying Session 02 is a contract and inventory only, not an API route. * Distinguished local exports, archives, diagnostics, recovery, browser reset, Worker leave/reset/disconnect, and CLI uninstall from future trusted erasure contracts. **Files Changed**: * `docs/api/README_api.md` - Added erasure inventory and cleanup boundary section. **BQC Fixes**: * Failure path completeness: Docs now explicitly state that no DELETE, purge, Worker room deletion, hosted account deletion, or public replay takedown endpoint is shipped. *** ### Task T019 - Update protocol package documentation **Started**: 2026-05-31 02:00 **Completed**: 2026-05-31 02:03 **Duration**: 3 minutes **Notes**: * Documented `src/erasure.ts` as the protocol-owned source for erasure vocabulary, inventory rows, blocked payload categories, unsupported claims, summary builders, and negative-claim helpers. * Added protocol-first consumption rules and Session 03/04 handoff wording. **Files Changed**: * `packages/protocol/README_protocol.md` - Added Phase 08 erasure contract ownership section. **BQC Fixes**: * Contract alignment: Package docs now require consumers to import from the protocol barrel and avoid duplicating boundary labels. *** ### Task T020 - Update server and Worker package documentation **Started**: 2026-05-31 02:03 **Completed**: 2026-05-31 02:07 **Duration**: 4 minutes **Notes**: * Documented the server erasure inventory helper as read-only coverage for local state families. * Documented the Worker erasure inventory helper as read-only coverage for Durable Object state families and Session 04 handoff. * Both docs explicitly state no destructive erasure behavior is shipped by these helpers. **Files Changed**: * `apps/server/README_server.md` - Added server inventory helper boundary and Session 03 handoff wording. * `apps/warroom/README_warroom.md` - Added Worker inventory helper boundary and Session 04 handoff wording. **BQC Fixes**: * Contract alignment: Server and Worker docs now consume the protocol-owned erasure inventory instead of inventing local claims. * Error information boundaries: Docs emphasize labels and counts only, with no raw paths, tokens, hashes, room payloads, or filesystem payloads. *** ### Task T021 - Run focused Vitest coverage **Started**: 2026-05-31 02:07 **Completed**: 2026-05-31 02:11 **Duration**: 4 minutes **Notes**: * Ran focused Vitest coverage for protocol, server, and Worker erasure inventory files. * First run failed because several inventory warnings did not explicitly include non-erasure wording. * Updated protocol inventory warnings for lifecycle, valid spool, diagnostics, scan runtime memory, browser settings, browser War Room hints, and Worker/browser hint adjacency. * Reran focused tests successfully: 3 files passed, 12 tests passed. **Files Changed**: * `packages/protocol/src/erasure.ts` - Tightened non-erasure warning wording found by tests. **Command Outcomes**: * `npm test -- packages/protocol/tests/erasure.test.ts apps/server/tests/erasureInventory.test.ts apps/warroom/tests/erasureInventory.test.ts` - Passed after wording fixes. **BQC Fixes**: * Failure path completeness: Inventory warnings now explicitly say non-erasure for cleanup-like flows. * Contract alignment: Tests enforce no-overclaim wording. *** ### Task T022 - Run affected TypeScript typechecks **Started**: 2026-05-31 02:11 **Completed**: 2026-05-31 02:13 **Duration**: 2 minutes **Notes**: * Ran affected TypeScript typechecks for protocol, server, and Worker workspaces. **Command Outcomes**: * `npm --workspace packages/protocol run typecheck` - Passed. * `npm --workspace apps/server run typecheck` - Passed. * `npm --workspace apps/warroom run typecheck` - Passed. **BQC Fixes**: * Contract alignment: Typechecks validated package imports and exported contract types. *** ### Task T023 - Run docs, whitespace, ASCII, LF, and diff validation **Started**: 2026-05-31 02:13 **Completed**: 2026-05-31 02:18 **Duration**: 5 minutes **Notes**: * Ran Biome formatting on the new and touched TypeScript files. * Ran targeted no-overclaim scan for shipped/available trusted-erasure wording across touched docs. * Ran ASCII and CRLF scans across touched code, docs, and spec files. * Ran `git diff --check`. * Reran focused tests and affected typechecks after formatting. **Command Outcomes**: * `npx biome format --write ...` - Passed; formatted 7 files and fixed 5. * Targeted no-overclaim `rg` scan - Passed with no matches. * ASCII scan - Passed. * CRLF scan - Passed. * `git diff --check` - Passed. * Focused Vitest rerun - Passed, 3 files / 12 tests. * Protocol, server, and Worker typecheck rerun - Passed. **BQC Fixes**: * Contract alignment: Formatting and checks were rerun after documentation and code edits. * Error information boundaries: No-overclaim scan found no shipped/available trusted-erasure wording. *** ### Task T024 - Record command outcomes and handoff notes **Started**: 2026-05-31 02:18 **Completed**: 2026-05-31 02:20 **Duration**: 2 minutes **Notes**: * Recorded final command outcomes, changed files, residual risks, and Session 03/04 handoff notes. * Trusted unified erasure is still not shipped. This session delivered contracts, inventory, read-only helpers, tests, and documentation only. **Files Changed**: * `.spec_system/PRD/phase_08/unified_erasure_inventory.md` - Added Session 02 inventory artifact. * `.spec_system/specs/phase08-session02-unified-erasure-contract-and-inventory/tasks.md` - Marked all implementation tasks complete. * `.spec_system/specs/phase08-session02-unified-erasure-contract-and-inventory/implementation-notes.md` - Recorded implementation log and closeout summary. * `packages/protocol/src/erasure.ts` - Added shared erasure contract, inventory, summaries, guards, and negative-claim helpers. * `packages/protocol/src/index.ts` - Exported erasure contract. * `packages/protocol/tests/erasure.test.ts` - Added protocol erasure tests. * `apps/server/src/lib/erasureInventory.ts` - Added read-only server inventory helper. * `apps/server/tests/erasureInventory.test.ts` - Added server inventory tests. * `apps/warroom/src/erasureInventory.ts` - Added read-only Worker inventory helper. * `apps/warroom/tests/erasureInventory.test.ts` - Added Worker inventory tests. * `docs/privacy-and-security.md` - Added erasure inventory posture and open finding wording. * `docs/release.md` - Added Session 02 release evidence and no-claim wording. * `docs/api/README_api.md` - Added API cleanup-vs-erasure boundary section. * `packages/protocol/README_protocol.md` - Added protocol erasure ownership docs. * `apps/server/README_server.md` - Added server helper boundary docs. * `apps/warroom/README_warroom.md` - Added Worker helper boundary docs. **Command Outcomes**: * `bash /home/aiwithapex/.codex/skills/apex-spec/scripts/analyze-project.sh --json` - Passed and resolved current session. * `bash /home/aiwithapex/.codex/skills/apex-spec/scripts/check-prereqs.sh --json --env` - Passed. * `npm test -- packages/protocol/tests/erasure.test.ts apps/server/tests/erasureInventory.test.ts apps/warroom/tests/erasureInventory.test.ts` - Passed after wording fixes, then passed again after formatting. * `npm --workspace packages/protocol run typecheck` - Passed before and after formatting. * `npm --workspace apps/server run typecheck` - Passed before and after formatting. * `npm --workspace apps/warroom run typecheck` - Passed before and after formatting. * `npx biome format --write ...` - Passed. * Targeted no-overclaim `rg` scan - Passed with no matches. * ASCII scan for touched files - Passed. * CRLF scan for touched files - Passed. * `git diff --check` - Passed. **Residual Risks**: * `P06-S07-ERASURE` remains open; no runtime deletion, purge, Worker room deletion, hosted account deletion, public replay takedown, or end-user erasure controls were introduced. * Future hosted identity, storage, analytics, push, public replay, and remote-access rows are placeholders only because those runtimes remain disabled, unavailable, or future-scoped. * Server and Worker helpers are read-only inventory mappers; they do not verify live filesystem or Durable Object deletion. **Session 03 Handoff**: * Use `packages/protocol/src/erasure.ts` as the required inventory and vocabulary source before adding local/browser runtime controls. * Implement dry-run, explicit confirmation, deletion, idempotency, partial-failure reporting, redacted audit output, and verification for local and browser boundaries. * Keep valid spool, backups, workspace files, exports, archives, logs, diagnostics, memory, settings, lifecycle, browser replay, and browser hints separate in previews and audit records. **Session 04 Handoff**: * Use Worker inventory rows for participants, recent events, authority hashes, idempotency records, room revisions, and browser-hint adjacency. * Either implement and validate Worker Durable Object erasure under the agreed authority model or keep Worker storage in explicit no-claim status. * Do not treat Worker room authority as hosted identity or browser leave/reset as Worker erasure. **BQC Fixes**: * Contract alignment: Final closeout keeps inventory evidence separate from runtime deletion evidence. * Failure path completeness: Residual no-claim status and next-session requirements are explicit. *** ## Session Closeout Summary Session implementation complete. | Metric | Value | | ----------------------- | -------------------------------------------------------------------- | | Tasks Completed | 24 / 24 | | Focused Tests | 3 files / 12 tests passed | | Typechecks | protocol, server, warroom passed | | BQC | Non-erasure wording fixes applied across protocol inventory and docs | | Trusted Unified Erasure | Not shipped; remains a Phase 08 no-claim | Run the validate workflow step to verify session completeness. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://faction-os.gitbook.io/faction-os-docs/.spec_system/archive/sessions/phase08-session02-unified-erasure-contract-and-inventory/implementation-notes.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.