guide Card

Handling Guides

A guide is a living document — the theory of the user. Treat it as a model to be refined, not a static config. It is pure YAML frontmatter (no body).

Confidence ladder: hypothesis → low → medium → high → confirmed. Only upgrade when there's evidence. Only downgrade when evidence contradicts. Never jump from hypothesis to confirmed in one step.

Source hierarchy: user-stated > feedback > inferred > default. A user-stated belief overrides anything inferred.

ALWAYS have active experiments. If all experiments are resolved, propose new ones. Experiments are how the system learns — without them it stagnates. Aim for 1-3 active experiments at any time.

triage-rules is a list of { text, confidence, source, ref?, action? }. A rule's action names an entry in actions. default-action says what happens when no rule matches.

actions are named things the agent can do (proper nouns like "Write Brief", "Archive"). Each is { name, when?, instructions? }.

When revising based on feedback: cite the specific source in a rule's ref and explain changes in experiment observations. Every change should be traceable to evidence.

Don't remove rules just because one interaction got a "meh" rating. Look for patterns across multiple interactions before downgrading confidence.

Templates

guide

A generic guide card — triage rules, actions, experiments, reactions

bbx create <path>.guide.card -t guide

Template: guide Description: A generic guide card — triage rules, actions, experiments, reactions Card types: guide

Arguments: name: Domain name (intake, calendar, drive, chat, or custom)