Sources, Integrations, and Evidence Foundation
Sources, Integrations, and Evidence Foundation
On this page
Connectors, source versions, provenance, object mapping, evidence, files, corrections, and invalidation. 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-EVIDENCE · Type: Business capability · Documentation: 1.0
Marketplace listing · Technical reference
An imported document is evidence, not a verified business conclusion. Email and document findings are reviewed through BND-FINDINGS, just like meeting findings.
User guide
- Authorize a connector and preview the sources and permissions it exposes.
- Inspect imported email, document or media versions, their provenance and business-object links.
- Correct a source or mapping; inspect the dependent findings marked stale and the resulting reprocessing activity.
Screens owned by this package
- Meeting — Context —
SCR-MTG-05. - Meeting — Files & Versions —
SCR-MTG-06. - Meeting — Activity —
SCR-MTG-07. - Administration — Sources & Integrations —
SCR-ADM-03.
Contributions to other screens
- My Development — Evidence & History — owned by
BND-DEVELOPMENT; this package contributes analysis or interface content. - Meeting — Audio & Transcript — owned by
BND-MEETING; this package contributes analysis or interface content. - Commercial Intelligence — Stakeholders — owned by
BND-COMMERCIAL; this package contributes analysis or interface content. - Project Execution — Acceptances — owned by
BND-SCOPE; this package contributes analysis or interface content. - Ethics & Compliance — Cases — owned by
BND-ETHICS; this package contributes analysis or interface content. - Administration — Platform Operations — owned by
BND-AIOPS; this package contributes analysis or interface content.
Configuration
| Setting | Purpose and behavior |
|---|---|
| Source selection | Choose mailboxes, folders, calendars and systems with explicit inclusion and exclusion rules. |
| Object resolution | Bind canonical identifiers and require review for ambiguous identity or project matches. |
| Correction propagation | Set reprocessing scope and review handling for derived artifacts invalidated by a new source version. |
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-EVIDENCE, WFP-EVIDENCE-FOUNDATION, 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
- Core Platform and Application Shell —
BND-CORE. - Organization, Identity, Access, and Governance —
BND-ORG.
Direct consumers: Meeting and Conversation Intelligence, Finding Lifecycle, Evidence Assurance, and Review, Commercial Intelligence, Project and Portfolio Execution, Scope, Contract, SOW, and Acceptance Alignment, Relationship and Trust Intelligence, Ethics and Compliance Review, Evidence Search Assistant, Reports, Scheduling, and Governed Exports.
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 connector adapters, document extraction profiles and business-object mappings without replacing source provenance or bypassing inherited permissions.
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.
- Compare release manifests, permission changes and migrations against the current lock.
- Test package behavior and affected dependent workflows with representative, authorized evidence.
- Promote the signed release after approval and record the resulting lock.
- 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.