The Fire Keeper — ceremony coordination agent for Medicine Wheel
The Fire Keeper tends the ceremony fire, ensures relational integrity through gating conditions, and maintains Wilson alignment as an active agent — not a passive metric.
Wilson’s ceremony requires a keeper. Without one, ceremony degrades into process. The Fire Keeper embodies relational accountability as an active agent that:
| Module | Purpose |
|---|---|
keeper.ts |
FireKeeper class — core coordination engine |
gating.ts |
Gate evaluation and default gates (Wilson, OCAP, ceremony phase) |
decisions.ts |
Human-in-the-loop decision detection and permission escalation |
check-back.ts |
Four-step relational check-back protocol |
ceremony-state.ts |
Extended ceremony state management |
trajectory.ts |
Trajectory confidence and value divergence detection |
messages.ts |
A2A message type definitions |
import {
FireKeeper,
DEFAULT_GATES,
type FireKeeperConfig,
} from 'medicine-wheel-fire-keeper';
const config: FireKeeperConfig = {
trajectoryThreshold: 0.65,
permissionTiers: ['observe', 'analyze', 'propose', 'act'],
gatingConditions: DEFAULT_GATES,
humanDecisionPoints: [],
};
const keeper = new FireKeeper(config);
const ceremony = keeper.beginCeremony('inquiry::my-research');
const result = keeper.evaluateImportance({ id: 'unit-1', title: 'Vision' }, 'inquiry::my-research');
| Tier | Scope | Human Required |
|---|---|---|
| 🟢 observe | Read files, gather context | No |
| 🟡 analyze | Produce analysis, create ImportanceUnits | No |
| 🟠 propose | Draft artifacts, suggest schemas | No (Fire Keeper reviews) |
| 🔴 act | Generate code, create commits | Yes |
Before any autonomous action, the Fire Keeper verifies:
MIT