Business Frameworks

Lists every Business Frameworks node: handle, title, layer, token count, price, whether it is free, and whether its decision rule can be run on numbers. Business Frameworks is operating judgement for running a business from launch to about $50M in revenue: value, cash flow, risk (the cost of capital) and growth, down to ten decision rules. Call this first, once, to choose which node answers the question; pass `branch` to see one branch only. Free. Do not use it for businesses above about $50M in revenue, for tax, legal or accounting treatment, or for market data: it holds judgement and rules, not figures about any company.

{
  "type": "object",
  "properties": {
    "branch": {
      "description": "One of: equation, value, cash-flow, risk, growth, decision, market. Omit for the whole catalogue.",
      "type": "string"
    }
  },
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

Returns one node's text with its public citations, child handles, related handles and a cite-as line; `variant` chooses full (the default: lede, conditions, reasoning) or terse (the lede alone) at the same price. The free layer (the equation, the branch roots, value/15s and the decision-method nodes, marked free in bf_catalogue) costs nothing; every other node costs its catalogue price ($0.02 to $0.05, USDC on Base over x402), charged once per call and only when the text is returned. Call it with a `path` from bf_catalogue when the user's question needs that node's reasoning or decision rule; read the free parent before buying a child, and use bf_resolve when the question is broad enough to take several nodes. Do not call a paid path to see what it contains: the catalogue line says what it covers; and do not use it to run a rule on numbers, which is bf_apply_decision.

{
  "type": "object",
  "properties": {
    "path": {
      "type": "string",
      "description": "Node path from bf_catalogue, e.g. \"risk\" (free) or \"risk/decide/hurdle\" (paid). A full handle is accepted."
    },
    "variant": {
      "description": "full (default): lede, conditions and reasoning; terse: the lede alone. The same price either way.",
      "type": "string",
      "enum": [
        "full",
        "terse"
      ]
    }
  },
  "required": [
    "path"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

Returns the input schema, an example input and the price for one of the applied decisions (reinvest or distribute, build or run for cash, cash cycle, runway, owner pay, hurdle rate, concentration, pace of growth, price, adjacency; and, in the market branch, verdict, pricing power, binding node, rent, shock). Free. Call it before bf_apply_decision to learn which numbers the rule needs and what each one means; without `decision` it lists them all. Do not guess missing inputs to fill the schema: ask the user for the figures the business actually has.

{
  "type": "object",
  "properties": {
    "decision": {
      "description": "Decision path, e.g. \"risk/decide/hurdle\". Omit to list the ten.",
      "type": "string"
    }
  },
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

Runs one decision node's rule on the numbers you send and returns the computed figures, a verdict, the actions in order, the check to keep and the node text with its citations. Deterministic: the result comes from the published rule, not from a model. Costs the decision's catalogue price ($0.05, USDC on Base over x402); the input is checked first, and an input the rule cannot use is refused without charge. Call it when the user has the figures for a specific decision in a business under about $50M in revenue and wants the rule's answer for them; get the schema from bf_decision_schema first. Do not call it with invented or placeholder figures, and do not treat the verdict as tax, legal or investment advice.

{
  "type": "object",
  "properties": {
    "decision": {
      "type": "string",
      "description": "Decision path from bf_decision_schema, e.g. \"cash-flow/decide/runway\"."
    },
    "input": {
      "type": "object",
      "propertyNames": {
        "type": "string"
      },
      "additionalProperties": {},
      "description": "The figures, shaped as that decision's input_schema."
    }
  },
  "required": [
    "decision",
    "input"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

Quotes the minimal set of nodes that answers a broad task — a decision bundle, a market (chain) bundle or a cross bundle — with its price, the sum of its nodes' catalogue prices, stated before anything is paid. Deterministic and free: a named bundle or decision wins, then the input fields sent, then the authored patterns of the question; on ambiguity it returns candidates with their task lines, and with no match the task lines to choose from. Call it when the user's question takes more than one node (a whole decision with its context, a supply chain read, a shock traced to a seat), passing the question, revenue_usd and chain_position when known; then buy the quote with bf_read_bundle or read nodes one at a time with bf_read_node. Do not use it for a single term or a single rule, which bf_catalogue and bf_read_node answer more cheaply, and do not treat a quote as an answer: it names the nodes and the price, nothing more.

{
  "type": "object",
  "properties": {
    "question": {
      "description": "The task in the user's words (up to 2,000 characters).",
      "type": "string",
      "maxLength": 2000
    },
    "revenue_usd": {
      "description": "Annual revenue in US dollars, to pick the scale band.",
      "type": "number"
    },
    "chain_position": {
      "description": "Where the business sits on the chain being read: binding_upstream, binding_downstream, at_binding or unknown.",
      "type": "string"
    },
    "decision": {
      "description": "A decision path when the task is one decision, e.g. \"cash-flow/decide/runway\".",
      "type": "string"
    },
    "bundle": {
      "description": "A bundle id from a task line, when the caller already knows which.",
      "type": "string"
    },
    "inputs": {
      "description": "The figures already in hand, by field name; the resolver reads the names, not the values.",
      "type": "object",
      "propertyNames": {
        "type": "string"
      },
      "additionalProperties": {}
    }
  },
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

Returns the nodes of one bundle in order — the central node full, the supporting nodes terse — with citations and a cite-as line per node, on one settlement at the quoted price (the sum of the nodes' catalogue prices, $0.05 to about $0.20, USDC on Base over x402). Pass the bundle id from bf_resolve or bf_catalogue, and a band to add the scale band for the business's revenue. Call it after bf_resolve has quoted the bundle and the user accepts the price; the quote's url is the same resource over HTTP. Do not call it to browse: the quote already lists the nodes and the price, and a narrow question is cheaper node by node through bf_read_node.

{
  "type": "object",
  "properties": {
    "bundle": {
      "type": "string",
      "description": "Bundle id from bf_resolve or bf_catalogue, e.g. \"runway\"; the quote url is accepted too."
    },
    "band": {
      "description": "A scale band to add, by slug (\"1-5m\") or label (\"$1–5M\"); omit for the bundle without a band.",
      "type": "string"
    }
  },
  "required": [
    "bundle"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}