Product guides

Knowledge

Approved and versioned organizational facts, policies, examples, and standards, retrieved when a trigger says they are relevant.

A Knowledge entry stores something Opulent should remember about your organization: a citation standard, brand voice, deployment procedure, client rule, or approval policy. A trigger describes when to retrieve it.

Small, targeted entries are easier to retrieve correctly than one large manual. Load a citation standard during research and drafting, not during an unrelated infrastructure task.

Writing an entry

  1. 01State the rule, not the reasoningThe run needs what to do. Keep the justification short or elsewhere.
  2. 02Give the triggerDescribe when this should be loaded, so it arrives on the right runs and stays out of the wrong ones.
  3. 03Name the authorityIf the entry describes precedence between sources, say which one wins.
  4. 04Keep it smallOne rule per entry retrieves better than ten in a document.

Maintaining a large base

Opulent can maintain Knowledge at scale: finding duplicate entries, proposing a consolidated version, identifying conflicting guidance, preserving source and scope during a resolution, finding gaps in the current material, drafting a new entry from approved work, and reviewing pending suggestions before they become shared context.

Remove duplicates first, resolve conflicts next, then fill gaps. Conflicting guidance is worse than missing guidance, because a run will confidently follow one side of it.