cleverb/bearing
BEARING: an EOCR-based decision system — recover, elicit, anchor, and enforce the decisions governing a codebase, so architectural intent is discoverable at generation time rather than only enforceable at commit time.
Conduct a structured, pressure-tested interview with a human at the moment an agent hits genuine architectural ambiguity, and record the answer as a candidate decision. Use when intent is missing or ambiguous and you cannot proceed safely without asking, or when a human asks to resolve and document a decision. Applies the deletion test and an explicit authority check before anything is recorded.
Help a repository try BEARING, establish a small amount of useful decision context, and evaluate whether it is worth continuing. Use when asked to onboard, pilot, or evaluate BEARING. Offers an adaptable path rather than imposing an experimental protocol.
Recover evidence of undocumented architectural decisions from commit history, PR descriptions, tickets, and code comments into reviewable shadow candidates. Use for a manual or scheduled audit, or opportunistically when ordinary work exposes missing decision ancestry. Never writes to the authored decision record directly.