# Role-Aware and Executive Overview

Role-aware summaries, materiality, cross-domain KPIs, exceptions, interventions, and executive briefings. 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-OVERVIEW` · **Type:** Business capability · **Documentation:** 1.0

[Marketplace listing](/marketplace/bnd-overview) · [Technical reference](/documentation/packages/bnd-overview/technical-reference)

Overview cannot display a domain whose package is absent or whose data the viewer cannot access. It reports detected signals, not an unexplained universal health score.

## User guide

1. Select your authorized scope and review changes, exceptions and evidence coverage.
2. Inspect the domain indicator that needs attention and follow it to its owning package.
3. Use the briefing to prioritize review; manage assigned work in Actions rather than treating Overview as a duplicate task list.

### Screens owned by this package

- [Overview](/documentation/packages/bnd-overview/screens/home-overview) — `SCR-OVR-01`.

### 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

| Setting | Purpose and behavior |
|---|---|
| Role composition | Select the indicator contributions relevant to each business role. |
| Materiality | Define attention thresholds, trend windows and exception rules. |
| Coverage | Require sufficient and current evidence before showing a comparable indicator. |

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](/documentation/packages/bnd-overview/technical-reference) identifies `DM-OVERVIEW`, `WFP-ROLE-OVERVIEW`, 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

- [Finding Lifecycle, Evidence Assurance, and Review](/documentation/packages/bnd-findings) — `BND-FINDINGS`.
- [Decisions, Commitments, Actions, and Follow-Up](/documentation/packages/bnd-work) — `BND-WORK`.

Other compatible packages can consume its declared capabilities without changing ownership.

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

Contribute compatible KPI widgets, domain summaries and drill-down links through interface slots.

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](/documentation/developers/package-authoring).

## 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](/documentation/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.