OKF Knowledge Bundle Template
Use this template to create a self-contained, reusable Knowledge Bundle made up of related concepts, guidance, workflows, citations, and implementation resources.
Bundle Record
| Field | Value |
|---|---|
| Bundle Name | [Bundle Name] |
| Bundle ID | [bundle-name] |
| Version | 0.1 |
| Status | Draft |
| Maintainer | [Person, department, organization, or steward] |
| Audience | [Who should use this bundle?] |
| Primary Use Case | [Training / AI assistant / compliance / operations / procurement / customer support / policy library] |
| AI Use | [Allowed / Citation-required / Human-reviewed / Restricted] |
| Last Updated | [Month Year] |
| License or Reuse Terms | [Internal use / commercial license / public reuse / draft] |
Bundle Purpose
Explain the problem this Knowledge Bundle helps solve.
Describe why the bundle exists, what audience it serves, and how it should be used.
Intended Outcomes
This bundle should help users:
- [Outcome one]
- [Outcome two]
- [Outcome three]
- [Outcome four]
Included Concepts
| Concept | Concept ID | Purpose |
|---|---|---|
| [Concept Name] | namespace:concept_name | [What this concept provides] |
| [Concept Name] | namespace:concept_name | [What this concept provides] |
| [Concept Name] | namespace:concept_name | [What this concept provides] |
| [Concept Name] | namespace:concept_name | [What this concept provides] |
Bundle Structure
Foundation Concepts
List the definitions, terminology, frameworks, or core ideas that users need before applying the bundle.
Operational Concepts
List the procedures, workflows, checklists, tools, forms, or implementation resources.
Governance and Trust Concepts
List the concepts that address ownership, review, risk, approvals, privacy, security, compliance, records, or accountability.
Recommended Use Process
Step 1: Review the Bundle Scope
Describe how users should understand the purpose, limits, and intended use of the bundle.
Step 2: Identify Relevant Concepts
Explain how users should locate the specific concepts that apply to their department, project, client, policy, or workflow.
Step 3: Adapt for Local Use
Explain what information should be customized, approved, or supplemented before the bundle is put into use.
Step 4: Deploy the Bundle
Describe how the bundle may be used in practice.
Examples:
- Internal wiki
- Staff training
- AI assistant knowledge base
- Consulting deliverable
- Public-facing guidance
- Procurement support
- Compliance documentation
Step 5: Maintain and Review
Describe how the bundle should be reviewed, updated, and governed over time.
Required Supporting Materials
- Policies
- Procedures
- Forms
- Checklists
- Templates
- Source documents
- Reference links
- Training materials
- Decision records
- Approval documentation
Sources and Citations
- [Source title, policy, regulation, website, document, or reference]
- [Source title, policy, regulation, website, document, or reference]
- [Source title, policy, regulation, website, document, or reference]
Revision History
| Version | Date | Change | Owner |
|---|---|---|---|
| 0.1 | [Month Year] | Initial draft | [Name or organization] |