04 / BUSINESS AI CAPABILITY PACK
The client should own more than a Prompt or a demo.
FDE Delta assembles the approved business decisions, context, task method, platform implementation, evaluation, permissions, adoption support, and operating responsibilities into a reviewable and maintainable capability package.
Explore the five asset families ↓CLIENT-OWNED ASSET SYSTEM
One capability package. Five asset families. Only the approved scope is included.
A complete operating capability may draw from all five families, but every engagement does not promise every asset. The assembly makes each component reviewable, assignable, and explicitly included, conditional, excluded, or unresolved.
Exploded asset assembly · not a process, maturity model, mandatory bundle, repository screenshot, or proof of delivery.
POSSIBLE PACKAGE CONTENTS
Scope-bound · evidence-linked · owner-assigned · versioned
POSSIBLE PACKAGE CONTENTS
A1Decision Assets
- PURPOSE
- Preserve the business problem, selected opportunity, value logic, scope, exclusions, and human decisions.
- REPRESENTATIVE ASSETS
- Business Reality Diagnostic
- AI Opportunity Portfolio
- Prioritized Use-Case Brief
- Value Hypothesis
- Executive Decision Memo
A2Capability Assets
- PURPOSE
- Define the portable business capability and any approved implementation form.
- REPRESENTATIVE ASSETS
- Business AI Capability Specification
- Business Context Pack
- Skill or Instruction Package
- Workflow Package when separately authorized
- Platform Adapter
- approved connector or supporting script when required
A3Assurance Assets
- PURPOSE
- Make quality, permissions, risks, human control, failure, and recovery inspectable.
- REPRESENTATIVE ASSETS
- Evaluation Suite
- Golden Test Set
- Permission Matrix
- Risk and Failure Register
- Human Approval Design
- Fallback and Recovery Runbook
- Known Limitations
A4Adoption Assets
- PURPOSE
- Help named users understand, use, correct, and adopt the capability in real work.
- REPRESENTATIVE ASSETS
- User Playbook
- Role-Based Usage Guide
- Training Materials
- Change and Adoption Plan
- Champion Enablement Pack
A5Operating Assets
- PURPOSE
- Define administration, ownership, releases, improvement, migration, and retirement.
- REPRESENTATIVE ASSETS
- Administrator Runbook
- Version and Release Process
- Operating and Ownership Model
- Usage and Value Review Definition
- Improvement Backlog
- Retirement and Migration Guidance
Status grammar · definitions only · not assigned to any example asset
- INCLUDED BY APPROVED SCOPE
- CONDITIONAL
- EXCLUDED
- UNKNOWN
VISIBLE SEMANTIC EQUIVALENT
- A1Decision Assets
Preserve the business problem, selected opportunity, value logic, scope, exclusions, and human decisions.
Business Reality Diagnostic · AI Opportunity Portfolio · Prioritized Use-Case Brief · Value Hypothesis · Executive Decision Memo - A2Capability Assets
Define the portable business capability and any approved implementation form.
Business AI Capability Specification · Business Context Pack · Skill or Instruction Package · Workflow Package when separately authorized · Platform Adapter · approved connector or supporting script when required - A3Assurance Assets
Make quality, permissions, risks, human control, failure, and recovery inspectable.
Evaluation Suite · Golden Test Set · Permission Matrix · Risk and Failure Register · Human Approval Design · Fallback and Recovery Runbook · Known Limitations - A4Adoption Assets
Help named users understand, use, correct, and adopt the capability in real work.
User Playbook · Role-Based Usage Guide · Training Materials · Change and Adoption Plan · Champion Enablement Pack - A5Operating Assets
Define administration, ownership, releases, improvement, migration, and retirement.
Administrator Runbook · Version and Release Process · Operating and Ownership Model · Usage and Value Review Definition · Improvement Backlog · Retirement and Migration Guidance
Possible package components · not promises, current artifacts, or a universal checklist.
COMMITMENT FOLLOWS SCOPE
Different engagement stages carry different delivery commitments.
The package is assembled from the approved business outcome, engagement boundary, evidence standard, and ownership need. A diagnostic should not quietly promise production implementation; a capability Sprint should not imply enterprise-wide rollout; adoption support should not promise automatic ROI.
If an asset family is not required by the approved outcome, exclude or defer it explicitly—do not imply it is included.
OWNERSHIP BY DESIGN
The capability must remain ownable after the consultant leaves.
Handover is not a closing ceremony. Ownership must be designed into the package through named authority, source location, platform dependencies, acceptance evidence, release controls, recovery, and lifecycle decisions.
AUTHORITY
- BUSINESS OWNER
- owns the business outcome, scope, acceptance, and stop decision.
- TECHNICAL ADMINISTRATOR
- owns approved platform configuration, access, and technical operation.
SOURCE
- SOURCE & REPOSITORY
- identifies the authoritative specification, context, tests, Runbooks, and version history.
- ADAPTER DEPENDENCIES
- records platform-specific components, permissions, licenses, and portability limits.
OPERATION
- RELEASE & ROLLBACK
- defines who may release, pause, revert, or recover the capability.
- REGRESSION EVIDENCE
- preserves the test set, expected behavior, thresholds, and acceptance authority.
LIFECYCLE
- INCIDENT & SUPPORT PATH
- names escalation, support, fallback, and business-continuity responsibility.
- MIGRATE OR RETIRE
- defines when and how the capability is changed, transferred, archived, or stopped.
No critical asset without a source, owner, acceptance basis, and lifecycle path.
Package inclusion status says whether an asset belongs in an approved scope. Claim type says what kind of evidence or judgment supports a statement. They are different dimensions.
PACKAGE INCLUSION STATUS
- INCLUDED BY APPROVED SCOPE
- the governing engagement scope explicitly requires the asset.
- CONDITIONAL
- a named Gate, permission, dependency, or decision must be satisfied first.
- EXCLUDED
- the governing scope explicitly places the asset outside the engagement.
- UNKNOWN
- inclusion has not been decided or lacks authority/evidence.
CLAIM / EVIDENCE TYPE
- FACT
- accepted generic method definition or observed implementation state with source.
- HYPOTHESIS
- client-specific need, package composition, portability, value, operating, or adoption assumption requiring validation.
- UNKNOWN
- missing scope, source, data, access, permission, owner, evidence, acceptance, support, or lifecycle information.
- RECOMMENDATION
- bounded next package or ownership decision, never a fabricated asset, result, approval, or promise.
GATE 04 / PACKAGE DEFINITION
A package is ready to define only when its scope, evidence, ownership, and lifecycle are explicit.
- 01APPROVED BUSINESS OUTCOME AND USE-CASE BOUNDARY
- 02NAMED ENGAGEMENT SCOPE AND EXCLUSIONS
- 03ASSET-FAMILY INCLUSION DECISIONS
- 04ACCEPTANCE EVIDENCE AND AUTHORITY
- 05SOURCE, OWNER, PLATFORM, DATA, AND PERMISSION BOUNDARIES
- 06RELEASE, SUPPORT, MIGRATION, AND RETIREMENT PATH
Approved outcome + explicit package scope + acceptance basis + ownership continuity
CAPABILITY_PACKAGE_DEFINITIONGate eligibility authorizes package definition only. It is not proof of build, integration, acceptance, transfer, production readiness, or business value.
This page defines a public delivery model. It does not create a Capability Pack, Skill, Workflow, client artifact, platform implementation, or production commitment.
OPEN A CONVERSATION
Build something worth testing.
For AI-native products, global GTM, or independent projects, choose a channel below.