knowledge-activation

name	knowledge-activation
description	Activate mature .agents knowledge.
practices	["wiki-knowledge-surface","pragmatic-programmer"]
hexagonal_role	supporting
consumes	[]
produces	[]
context_rel	[]
skill_api_version	1
user-invocable	true
context	{"window":"fork","intent":{"mode":"task"},"sections":{"exclude":["TASK"]},"intel_scope":"topic"}
metadata	{"tier":"knowledge","dependencies":["compile","harvest","flywheel"]}
output_contract	.agents/beliefs.md, .agents/playbooks/*.md, .agents/briefings/*.md

Knowledge Activation

Turn a mature .agents corpus into operator-ready knowledge surfaces.

What This Skill Does

Use this skill when the problem is no longer "capture more knowledge," but:

• promote the strongest recurring claims into a belief system
• turn healthy topics into reusable playbooks
• compile a small goal-time briefing for future work
• surface thin topics and promotion gaps before they silently calcify

$compile remains the hygiene loop. knowledge-activation owns corpus operationalization.

Where this sits in the flywheel

Knowledge activation is the fourth step in the global-corpus workflow:

1. $harvest — gather artifacts from many rigs into ~/.agents/learnings/
2. $compile — synthesize raw artifacts into .agents/compiled/
3. (optional) $dream overnight — bounded compounding loop
4. $knowledge-activation — lift compiled knowledge into playbooks, beliefs, and runtime briefings

Which skill do I need?

See docs/skills-decision-tree.md for the full "which skill next?" decision table covering harvest, compile, dream, knowledge-activation, and quickstart.

Preconditions

This skill assumes the current workspace already has:

• a .agents/ directory
• packet refresh builders under .agents/scripts/ when ao knowledge activate needs to rebuild source manifests, topics, promoted packets, and chunk bundles from custom workspace logic
• or .agents/harvest/latest.json, which ao knowledge activate can use as a native fallback to turn the latest harvest catalog into a harvested-praxis topic packet, promoted packet, and chunk bundle
• packet, topic, playbook, and briefing surfaces that can be refreshed mechanically

Read references/script-contracts.md for the required builder inventory and command ownership.

Command Contract

The stable product surface is the ao knowledge command family: