Evidence Search Assistant

Permission-aware retrieval, cited answers, saved questions, monitoring, and history. This package has its own data model, workflows and interface contributions. Its documentation applies wherever the package is installed, not only to one industry solution.

Overview

Package: BND-SEARCH · Type: Business capability · Documentation: 1.0

Marketplace listing · Technical reference

Search does not grant access to sources. Saved questions and report consumers recheck permissions at execution and disclosure time.

User guide

1. Ask a question scoped to the relevant project, customer or time range.
2. Inspect citations and source versions; distinguish an evidence-backed answer from an explicit abstention.
3. Save an authorized question or monitor and revisit its results when the underlying evidence changes.

Screens owned by this package

• Search Assistant — Ask — SCR-SEA-01.
• Search Assistant — Search Results — SCR-SEA-02.
• Search Assistant — Saved Questions — SCR-SEA-03.
• Search Assistant — Search History — SCR-SEA-04.

Contributions to other screens

Contributions are resolved through the package's declared interfaces and dependencies. A package does not take ownership of another package's screen.

Configuration

Configuration changes are versioned overlays. Preview the changed permissions, schemas, workflow bindings and interface contributions in Development; qualify them in Testing and Staging before authorized Production promotion. A business administrator configures permitted solution settings; platform deployment authority is separate.

Technical reference

The implementation reference identifies DM-SEARCH, WFP-SEARCH-ASSISTANT, 1 owned agent, interface contributions, policies and evaluation profiles. Shared platform services execute these definitions; they do not hard-code this package's business meaning.

Compatibility and dependencies

• Sources, Integrations, and Evidence Foundation — BND-EVIDENCE.
• Finding Lifecycle, Evidence Assurance, and Review — BND-FINDINGS.
• Organization, Identity, Access, and Governance — BND-ORG.

Direct consumers: Product Help and Contextual Guidance.

Dependencies declare compatible ranges; the installation resolver records exact signed versions and digests in the environment lock. This documentation's version is not an installed-package version. Before updating or removing the package, inspect dependent workflows, records, interface slots and retained artifacts. Never delete referenced evidence or silently remove a required capability.

Extensions and enrichment

Add retrieval profiles, domain vocabularies and answer templates while preserving source-level authorization and citations.

Extensions declare their own package identity, dependencies, provided capabilities and evaluation evidence. They preserve the publisher's original package and are qualified with the complete resolved composition. See the developer extension guide.

Versions and upgrades

The documentation describes the current 1.x solution composition and the package's declared capabilities. The exact installed package, model, prompt and schema versions are shown in the environment lock and run provenance; no historical release sequence is implied.

1. Compare release manifests, permission changes and migrations against the current lock.
2. Test package behavior and affected dependent workflows with representative, authorized evidence.
3. Promote the signed release after approval and record the resulting lock.
4. Roll back only when schema/data compatibility and retained artifacts permit it. Irreversible migrations require a tested recovery or forward-fix plan; completed external actions require compensation, not a software rollback.

Used in solutions

Technology Consulting & Delivery includes this package as mandatory. That activation rule belongs to this solution; it does not make every business capability mandatory for every Telynt deployment.