Core Platform and Application Shell
Core Platform and Application Shell
On this page
Tenant runtime, package composition, entitlements, shell, ChangeSets, environments, promotion, rollback, and audit foundations. 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-CORE · Type: Platform foundation · Documentation: 1.0
Marketplace listing · Technical reference
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.
User guide
- Open the installation plan to inspect package additions, removals, permissions and migration impact.
- Review a ChangeSet against the current environment lock, then promote the approved release through Testing and Staging.
- Use the deployment history to compare locks and select an admissible rollback or forward-recovery plan.
Screens owned by this package
This package does not introduce a standalone business screen. It contributes the shared shell and operational bindings.
Contributions to other screens
- Administration — Platform Operations — owned by
BND-AIOPS; this package contributes analysis or interface content.
Configuration
| Setting | Purpose and behavior |
|---|---|
| Environment topology | Assign isolated Development, Testing, Staging and Production targets and their release approvers. |
| Package trust | Select trusted publishers, signature policies and approved private registries. |
| Promotion gates | Require compatibility, policy and migration checks before activation. |
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-CORE, WFP-CORE-LIFECYCLE, 0 owned agents, 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
This platform-owned foundation requires the Telynt kernel. It is not an independently removable replacement for kernel security or execution.
Direct consumers: Organization, Identity, Access, and Governance, Sources, Integrations, and Evidence Foundation, AI, Platform, Audit, and Security Operations, Product Help and Contextual Guidance.
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 shell slots, declared capabilities and compatible package types. Extensions cannot bypass the kernel's identity, authorization, audit or isolation controls.
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.