# Ethics and Compliance Review

Candidate alerts, segregated review, cases, policies, restricted analytics, and reviewer audit. 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-ETHICS` · **Type:** Business capability · **Documentation:** 1.0

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

Alerts are candidates for review, not findings of guilt. Private personal-development recommendations are governed separately by BND-DEVELOPMENT.

## User guide

1. Use the authorized review queue to inspect a candidate alert with evidence before and after the passage.
2. Check policy mapping, severity and confidence separately; record a reviewer assessment.
3. Dismiss, open a case or escalate under policy, with a reason and an audited disclosure boundary.

### Screens owned by this package

- [Ethics & Compliance — Review Queue](/documentation/packages/bnd-ethics/screens/intelligence-ethics-review-queue) — `SCR-ETH-01`.
- [Ethics & Compliance — Cases](/documentation/packages/bnd-ethics/screens/intelligence-ethics-cases) — `SCR-ETH-02`.
- [Ethics & Compliance — Policies](/documentation/packages/bnd-ethics/screens/intelligence-ethics-policies) — `SCR-ETH-03`.
- [Ethics & Compliance — Restricted Analytics](/documentation/packages/bnd-ethics/screens/intelligence-ethics-restricted-analytics) — `SCR-ETH-04`.
- [Ethics & Compliance — Reviewer Audit](/documentation/packages/bnd-ethics/screens/intelligence-ethics-reviewer-audit) — `SCR-ETH-05`.

### Contributions to other screens

- [Overview](/documentation/packages/bnd-overview/screens/home-overview) — owned by `BND-OVERVIEW`; this package contributes analysis or interface content.
- [Meeting — Findings](/documentation/packages/bnd-findings/screens/home-meetings-findings) — owned by `BND-FINDINGS`; this package contributes analysis or interface content.

## Configuration

| Setting | Purpose and behavior |
|---|---|
| Activation and reviewers | Explicitly authorize the restricted capability and assign qualified case reviewers. |
| Policy mapping | Bind current company policies, jurisdictions and evidence requirements. |
| Disclosure and aggregates | Configure segregation, minimum group sizes and controlled export permissions. |

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-ethics/technical-reference) identifies `DM-ETHICS`, `WFP-ETHICS-REVIEW`, 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

- [Organization, Identity, Access, and Governance](/documentation/packages/bnd-org) — `BND-ORG`.
- [Sources, Integrations, and Evidence Foundation](/documentation/packages/bnd-evidence) — `BND-EVIDENCE`.
- [Finding Lifecycle, Evidence Assurance, and Review](/documentation/packages/bnd-findings) — `BND-FINDINGS`.

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

Add policy taxonomies and specialized detectors with high-precision evaluation and human review. Extensions cannot broaden case access.

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 **installed restricted**. That activation rule belongs to this solution; it does not make every business capability mandatory for every Telynt deployment.