# Reports, Scheduling, and Governed Exports — Technical reference

This reference owns the implementation contracts of `BND-REPORTS`. [Read the package guide](/documentation/packages/bnd-reports) for usage, configuration, dependencies and upgrades. Generic execution, isolation and admission remain governed by [Platform Documentation](/documentation/platform).

## Data model and interfaces

**DataModelPackage:** `DM-REPORT`

Owned entities: report definition, template, schedule, run, section, evidence manifest, export, distribution, version.

**InterfacePackage contributions:** `IF-REPORTS`.

Each business object and source reference remains tenant- and purpose-scoped. The package owns schema evolution and declared migration behavior; the platform enforces schema registration, authorization and versioned installation. Consumers reference this model rather than creating competing canonical copies.

## Workflows

**WorkflowPackage:** `WFP-REPORT-LIFECYCLE`

- Report Composition
- Evidence Manifest Generation
- Template Resolution
- Scheduled Report Execution
- Version Regeneration
- Export Approval
- Distribution Approval
- Delivery and Receipt
- Export Expiry and Revocation

These are named definitions within the workflow package, not separate invented workflow IDs. Workflow runs resolve package versions, actor and purpose, authorized inputs, retries, review gates and output schemas through the environment lock. Temporal provides durable execution and Kafka carries declared lifecycle/domain events.

## Policies, evaluations and tools

`POL-REPORT-DISTRIBUTION`, `EVAL-REPORT-REPRODUCIBILITY`, rendering, export, signing, scheduling, and distribution tools.

Qualification covers the selected model/runtime profile, languages, access scope, failure handling and the package's domain-specific outcomes. Tool execution uses the platform gateway; package code cannot increase its own permissions or write directly to external systems.

## Owned agents

### U05 — Report Composition Agent

**Agent ID:** `effority.report-composition`

**Purpose:** Produces versioned meeting, opportunity, account, project, SOW, risk, relationship, technical, team, portfolio, executive, quality, audit, and authorized ethics reports.

**Triggers:** Schedule, user request, validated artifact change, template update, or period close.

**Inputs:** Validated artifacts, report scope, recipient permissions, period, source versions, prior report, and approved template.

**Outputs:** Structured report model, rendered document, evidence manifest, change summary, exclusions, and reproducibility record.

**Tools:** `artifact.read_validated`, `evidence.resolve`, `template.read`, `recipient.policy_check`, `chart.render`, and `document.render_draft`.

**Review and limits:** Reports never conceal incompatible factors behind a single score. External or restricted reports follow the configured approval workflow.

**Primary metrics:** Artifact coverage, citation coverage, reproducibility, recipient-policy compliance, edit rate, and generation latency.



## Implementation profiles

### Summary and Report Implementation

Long meetings are summarized hierarchically:

1. structured summary by topic;
2. consolidation of decisions, actions, risks, and questions;
3. deduplication and reference resolution;
4. generation of role-specific variants;
5. citation and coverage verification;
6. template-based rendering.

The report stores the exact set of findings and versions used. If data changes, a new version is created; a previously distributed report remains reproducible.




## Integration boundaries

A report is a versioned view of evidence, not a second system of record. Removing a contributor invalidates affected sections rather than silently fabricating them.

Owned screen contracts: [SCR-RPT-01](/documentation/packages/bnd-reports/screens/explore-reports-library), [SCR-RPT-02](/documentation/packages/bnd-reports/screens/explore-reports-scheduled), [SCR-RPT-03](/documentation/packages/bnd-reports/screens/explore-reports-templates), [SCR-RPT-04](/documentation/packages/bnd-reports/screens/explore-reports-exports).

See [solution workflows](/documentation/technology-consulting-delivery/connected-workflows) for cross-package behavior. Screens, agents and workflows keep one canonical owner even when other bundles invoke or enrich them.