Skip to content

Optional Tooling Policy

Optional tooling should stay optional. Optional does not mean "mention it anyway." It means ORCA Framework should surface it only when the benefit is clear enough to justify the extra complexity.

Policy

ORCA Framework may support advanced helpers such as Graphify, Obsidian graph workflows, or NotebookLM when they improve clarity, navigation, or synthesis.

It should not:

  • force setup before core value appears
  • turn a narrow task into a tooling project
  • recommend a tool only because it is available
  • put optional plugins or harnesses into the minimum install path

Decision Rule

Before suggesting optional tooling, ask:

  • does this reduce more friction than it creates?
  • is the current task broad enough to justify it?
  • is there evidence that the user actually needs this?
  • is a lighter path already enough?

If the answer is not clearly yes, stay with the lighter path.