# Core Platform and Application Shell — Technical reference

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

## Data model and interfaces

**DataModelPackage:** `DM-CORE`

Owned entities: tenant references, package, capability, installation, entitlement, environment, ChangeSet, environment lock, run references, artifact references, audit.

**InterfacePackage contributions:** `IF-CORE-SHELL`.

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-CORE-LIFECYCLE`

- Package Admission
- Composition Resolution
- Installation Plan
- ChangeSet Approval
- Environment Promotion
- Suspension
- Deterministic Rollback
- Entitlement Reconciliation

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-CORE-SUPPLY-CHAIN`, `POL-ENVIRONMENT-PROMOTION`, `EVAL-CORE-COMPATIBILITY`, registry and deployment 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

This is a platform-owned foundation, not an optional intelligence detector. Its management interfaces are packaged; the kernel's enforcement does not depend on an agent.



## Implementation profiles

The package composes the data, workflows, policies and interfaces above using the shared runtime. The owned-agent contracts specify inputs, outputs, tool boundaries, review requirements and measurable outcomes. Deterministic platform operations are not represented as additional agents.




## Integration boundaries

This is a platform-owned foundation, not an optional intelligence detector. Its management interfaces are packaged; the kernel's enforcement does not depend on an agent.

The absence of a standalone screen does not imply an absent capability; the manifest declares its host-interface contributions.

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.