Concepts
Operational knowledge packs
An operational knowledge pack is the container for one bounded team corpus, its source material, extracted draft knowledge, review metadata, and final export.
You should know what a reviewed operational knowledge pack contains and why the scope stays narrow.
What an operational knowledge pack can include
- SOP drafts with triggers, required context, steps, exceptions, open questions, and source references.
- Decision rules and escalation rules.
- Workflow steps and internal FAQ entries.
- Knowledge gaps, conflicts, and outdated-content flags.
- Support macro drafts or reusable response guidance.
- Optional agent-ready skill-file drafts with allowed actions, forbidden actions, and human-approval requirements.
Ownership metadata
Saved packs track issue name, team or workflow area, owner, reviewer, expected use this week, mishandling impact, pack status, review notes, approval timestamps, next review date, and reason for review.
Why one bounded corpus per pack
One bounded corpus keeps the reviewer accountable. If the pack mixes unrelated teams, owners, years, and operating areas, the output becomes vague and hard to approve.