Industry Solution Composition Contracts

An IndustrySolution assembles compatible capability bundles, sector defaults and interface contributions. It references package-owned functionality instead of embedding business execution in the kernel. The Technology Consulting & Delivery composition is documented separately.

2. Composition Hierarchy

flowchart TB
    P["Package\nOne technical artifact"] --> B["CapabilityBundle\nOne coherent business capability"]
    B --> S["IndustrySolution\nCertified sector baseline"]
    S --> C["CustomerConfiguration\nSolution plus private overlays"]
    C --> L["EnvironmentLock\nExact deployed digests"]

3. CapabilityBundle

A CapabilityBundle is technically distributed as a ConfigurationBundle. It normally contains or references:

• one or more DataModelPackage artifacts;
• one or more WorkflowPackage definitions;
• agents and model-capability requirements;
• tools and connectors;
• policies and evaluation packages;
• interface, route, navigation, widget, command, and report contributions;
• dependencies, extension points, compatibility, lifecycle, and data-disposition rules.

Examples include Meeting Intelligence, Commercial Intelligence, Project Execution, Scope and SOW Alignment, Relationship and Trust, Search Assistant, and Reports.

4. IndustrySolution

An IndustrySolution is a signed, versioned, non-executable composition artifact. It references compatible capability bundles and supplies the sector defaults that turn them into one coherent product experience.

It defines:

• required, default, restricted, recommended, optional, alternative, and conflicting bundles;
• compatible version ranges and resolved certification baselines;
• standard sector data models and relationships;
• workflows and review patterns;
• roles, permission profiles, and responsibility mappings;
• navigation order, screen composition, dashboards, and report catalog;
• taxonomies, classifiers, KPIs, thresholds, and materiality rules;
• connector profiles and field-mapping templates;
• language, model-capability, runtime, and infrastructure requirements;
• qualification suites, gold sets, and minimum production gates;
• installation, migration, update, removal, and rollback behavior;
• support, licensing, documentation, and end-of-life terms.

An Industry Solution contains no customer evidence, user directory, credentials, tenant secrets, or organization-specific business records.

4.1 Bundle Membership Roles

8. CustomerConfiguration

A customer does not fork or edit the Industry Solution. Telynt creates a CustomerConfiguration that records the selected solution version and separate customer-owned changes.

Technology Consulting & Delivery Intelligence 2.3
+ Customer data-model extensions
+ Customer workflows and approval rules
+ Customer navigation and dashboard overlays
+ Customer-private agents and models
+ Marketplace security enrichment
- Optional bundle deliberately disabled
= CustomerConfiguration

The customer layer records:

• selected and disabled optional bundles;
• approved alternatives and replacements;
• private packages and organization overlays;
• customer policy, role, threshold, language, and connector bindings;
• migration and compatibility status against the source Industry Solution;
• deviations from the certified baseline;
• evaluation evidence and approvals.

Publisher upgrades never overwrite customer packages. The compatibility resolver calculates whether each overlay remains valid, requires migration, conflicts, or blocks the proposed solution update.

10. Marketplace Representation

The Marketplace distinguishes:

• Industry Solutions — complete certified sector configurations;
• Capability Bundles — coherent functional modules;
• Enrichment Bundles — additions to installed capabilities;
• Packages — agents, models, workflows, data models, tools, connectors, interfaces, policies, and evaluations.

When linked to an authorized Telynt installation, an Industry Solution displays:

• INSTALLED with exact version;
• PARTIALLY_INSTALLED with present and missing bundles;
• UPDATE_AVAILABLE with affected customer overlays;
• COMPATIBLE;
• COMPATIBLE_WITH_PREREQUISITES;
• UPGRADE_REQUIRED;
• CONFLICT;
• BLOCKED_BY_POLICY;
• LICENSE_INCOMPATIBLE;
• NOT_COMPATIBLE;
• DEPRECATED or REVOKED.

The installation plan shows bundle additions, removals, replacements, permissions, data migrations, navigation and screen changes, model and hardware requirements, evaluations, licensing, resource impact, deviations from the certified baseline, and rollback behavior.

Composition records and versions

The solution manifest records membership, required capabilities, compatible ranges and activation policy. The environment lock records exact resolved releases and digests. Documentation versions describe a release line; they are not a substitute for a verified installation lock.

Documentation and navigation

Platform Documentation owns generic contracts. Developers owns authoring and qualification procedures. Each Marketplace package owns its implementation and user reference. Solution documentation explains integration, sector settings and end-to-end work, linking canonical package articles. These relations are generated from the composition and ownership registry.