Create and Extend Packages

The Development Environment and SDK create versioned Telynt packages. Marketplace publishers and authorized customer teams use the same authoring tools. The Enterprise Platform operates their installed releases independently of an active authoring session.

Start from a declared capability

Choose whether the change introduces a new capability or enriches an existing one. Inspect the target package's documentation, extension slots, dependencies and permissions. Keep the publisher's base release intact and express customer-specific changes as a governed overlay or separate enrichment package.

AI-assisted authoring

Describe the requirement in natural language. The authoring assistant proposes editable data models, screens, workflows, bindings and tests. Review the schema diff, generated navigation, requested tool access and migration impact before accepting the draft. AI-generated proposals never directly modify Production.

Package contents

Declare stable identities for AgentPackage, WorkflowPackage, DataModelPackage, InterfacePackage, ModelPackage, ToolPackage, PolicyPackage and EvaluationPackage artifacts as applicable. A ConfigurationBundle composes compatible artifacts into a capability; an IndustrySolution composes bundles into a business solution.

Declare the capability's inputs and outputs, required dependencies, provided extension points, permission ceiling, configuration schema and supported runtime profiles. Domain names and identifiers belong to the defining package; do not duplicate another package's canonical model to avoid declaring a dependency.

Interfaces and navigation

An interface definition declares routes, labels, placement, slots, accessibility behavior and authorization conditions. One package owns a screen. An enrichment can contribute a panel or indicator through a declared slot without replacing the owner. The composed navigation is previewed against the complete installation, including absent and restricted capabilities.

Enrichment example

A specialist contract-knowledge package depends on Scope Alignment and adds clause taxonomies, evidence retrieval and comparison rules. It produces compatible findings and contributes a review panel through declared slots. Scope Alignment retains ownership of scope changes and contractual acceptance records. The extension cannot silently change another publisher's acceptance policy or expand reviewer access.

Test the whole composition

Exercise standalone contracts and the host integration: missing dependencies, denied permissions, invalid schemas, stale evidence, tool failure, repeated events, review rejection and package removal. Qualify the resulting environment lock rather than assuming independently passing packages always compose correctly.

Publish or keep private

Build signed artifacts with source revision, test results, migration and recovery information. Private packages stay in the organization's registry. Marketplace publication adds distribution, licensing and support metadata; it does not deploy or activate a package. See release qualification.