Business Frameworks

io.github.matryoshka-paradigms由 GitHub 帳號 matryoshka-paradigms 發布v2026.10.31更新於 Nov 1, 2026

Operating judgement for businesses under $50M revenue. Free top layer; nodes and bundles over x402.

已驗證Streamable HTTP可網頁執行知識與記憶商業與電商

概覽

AI 產生的概覽

遠端 MCP 伺服器,提供付費的商業經營框架:瀏覽目錄、讀取節點、報價並購買節點包,還能用你的數字執行決策規則。

可以做什麼
  • 列出框架節點目錄,含代號、層級、token 數、價格與是否免費
  • 讀取單一節點及其引用,可選完整、精簡或欄位化版本
  • 檢視某項決策的輸入結構、範例輸入、價格與適配紀錄
  • 用你提供的數字執行決策規則,回傳計算結果、結論、依序行動與檢查項
  • 為廣泛任務報價最小節點組合,給出定價節點包
  • 依序讀取已報價節點包中的節點及引用
適用情境
適合商業經營類問題,例如價值、現金流、風險、現金跑道、定價、成長節奏與市場鏈條,讓助理依據已發布的框架而非即興作答;且可接受按節點或節點包支付數美分。
執行需求
遠端 streamable HTTP 端點,不需本機套件、帳號或 API 金鑰。付費節點、可套用決策與節點包需要 x402 用戶端,以及你自行提供並掌控的錢包,以 Base 上的 USDC 支付。用戶端應送出標明自身身分的 User-Agent 標頭,因為部分預設簽章會被 403 拒絕。
安裝前請注意
付費呼叫會產生費用:較深節點 0.02–0.05 美元,可套用決策 0.05 美元,節點包一律 0.05 美元,皆從你的錢包以 Base 上的 USDC 結算。端點會記錄付款標頭、付款地址與交易。作者即賣家,內容不構成法律、稅務或投資建議。送到套用介面的數字由已發布規則計算。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Business Frameworks,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式,或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南,先向你展示發布者、端點和登入方式,經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/io.github.matryoshka-paradigms%2Fbusiness-frameworks/install.md,並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前,先告訴我它的發布者、端點和登入方式,等我確認。不要把 API 金鑰寫進命令或我會提交的檔案;問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

{
  "mcpServers": {
    "business-frameworks": {
      "type": "http",
      "url": "https://business-frameworks.matryoshka-paradigms.workers.dev/mcp"
    }
  }
}

README

Business Frameworks — agent skill

Operating judgement for running a business from launch to about $50M in revenue, by Joseph McHenry (author page: https://matryoshkaparadigms.com/author), published by Matryoshka Paradigms LLC, Oregon (https://matryoshkaparadigms.com/), packaged as an Agent Skill. The skill tells an agent how to read the free top layer, how to pick the one deeper node that answers a narrow question or the quoted bundle that answers a broad one, and how to pay over x402 with the user's approval.

Ask narrow, pay per node; ask broad, get a quoted bundle at USD 0.05, stated before you pay.

What is in this repository

PathWhat it is
skills/business-frameworks/SKILL.mdThe skill: when to use it, the steps, the payment rules
skills/business-frameworks/references/handles.mdHandles, token counts, prices and the twenty bundles copied from the catalogue
.claude-plugin/marketplace.json, plugin.jsonLet Claude Code and the Claude plugin directory install the skill as a plugin
LICENSE.mdMIT for the files in this repository; the free layer CC BY-ND 4.0; paid node text all rights reserved
OVERVIEW.mdWhy an agent should use the nodes, in compute terms, with the measured table
measurement/The with-and-without measurement: method, questions, runner, results (answer keys withheld; they restate paid rules)
evals/A suite for claude plugin eval: the free layer with the plugin and without, re-runnable by anyone on their own account (see evals/README.md)

There is no code here: no scripts, hooks, MCP servers or binaries. The skill makes HTTPS requests to one host, business-frameworks.matryoshka-paradigms.workers.dev. (The endpoint itself also serves the nodes as an MCP server at /mcp, and describes itself at /llms.txt, /.well-known/x402 and /openapi.json; the skill needs none of them.)

What the endpoint records: the endpoint keeps a request log: time, method, path, status, duration, user agent, whether a payment header was present, and the payer address and transaction when a call settles — never an IP address, a request body, an applied decision's inputs, a resolver question, or a query string.

Install

  • Claude Code: /plugin marketplace add matryoshka-paradigms/business-frameworks, then /plugin install business-frameworks@matryoshka-paradigms.
  • Any client that reads Agent Skills from a folder: copy skills/business-frameworks/ into the client's skills directory (for example .agents/skills/ or ~/.claude/skills/).
  • Pin it. Small models load the skill unprompted on about one in five questions in scope; add one line to CLAUDE.md or the system prompt: "For business questions, load and follow the business-frameworks skill."

What it costs and who pays

Seventeen nodes are free. Sixty-seven deeper nodes cost $0.02 to $0.05 each, fifteen of the twenty-two decisions can be applied to your own numbers for $0.05, and a bundle — the nodes a broad task takes, quoted free first — costs a flat $0.05 with or without its scale band, paid in USDC on Base over x402. Nothing on the endpoint costs more than $0.05 a call. Payment needs an x402 client and a wallet you supply and control. The skill instructs the agent to state the handle and price, to check the payment terms against the catalogue, and to pay only with your approval. Without a wallet the free layer and the free input schemas still work.

What to check before you install

  1. Read SKILL.md. It is the whole skill.
  2. Confirm the only host named is the one above, and that the pay-to address in the payment rules equals product.pay_to in the live catalogue.
  3. Pin the tagged release you reviewed (this one is v0.5.1) if you want the text you reviewed to be the text that runs.
  4. The skill ships no code. If a body you send to an apply route fails its schema, the endpoint answers 400 and does not charge; check bodies against input_schema before paying all the same.

Limits

Scope is businesses up to about $50M revenue. This is not legal, tax or investment advice. The author is the seller.

If a request is refused with 403 and error 1010. Send a User-Agent header that names your client. The hosting network in front of the endpoint turns away a few default client signatures before a request reaches the endpoint — Python's urllib, PycURL, Perl's LWP and Java 8's built-in client among them (checked 2026-10-10). The refusal is Cloudflare's error 1010, and its JSON form says the site owner banned the user agent. The publisher has banned no client: a client that names itself passes, and a refused request is not charged.

Changes

  • 0.5.1 (2026-10-31) — a patch from the first outside review of 1.5 (four reviewing models, one blind). No node text changed. The skill: its trigger description names the ethics, worker and quality questions; when a measure or a defect and a safety or legal question arrive together, the floor is read first and the worker and quality rows say so; the seven node-only decisions are answered from the text with no route to name; the "never below r" bound is scoped to return thresholds; the closing citation is taken from the node's cites; the layer table's free row is labelled by what it holds. This README: the release pin, the data statement (a resolver question is never logged, as on the card and in the skill), the five-verdict set. Endpoint build 2026.10.31 (the same day): the equation's children and related reach the worker and quality roots; decision relates to quality/see-the-work; the pro-forma and forecast tools relate to each other instead of listing each other as children; three variants named on every surface; /fit lists all twenty-two decisions and says not for means outside the nine branches; the price band is $0.01–$0.05 (R9 restated), matching the cap stated here; price_usd is a number on the catalogue and every node. server.json at 2026.10.31.
  • 0.5.0 (2026-10-30) — document version 1.5 on endpoint build 2026.10.30: two vectors. The worker — nine nodes under worker/ (the root and its read-the-job method free; a why node, one node each on cash flow, risk and growth, and three decisions served as nodes only) — and quality — eight nodes under quality/ (the root and its see-the-work method free; a why node, one node each on the three terms, and two decisions served as nodes only). No other node's text changed; three related lists gain a link. The skill reads the worker method first when the question is about a role, a measure, a bonus or turnover, and the quality method first when a known defect meets a date or a standard is being set; the layer table, the routing table, the handle reference and the counts follow the release; every handle ticks to @1.5 and 1.4 stays readable at @1.4. server.json at 2026.10.30 for the MCP Registry.
  • 0.4.0 (2026-10-29) — document version 1.4 on endpoint build 2026.10.29: the ethics vector — eight nodes under ethics/ (the root and its feasibility method free; a why node, one node each on risk, cash flow and growth, and two decisions served as nodes only) — and one sentence in the equation's honest limit. The skill reads the ethics floor first when the question is whether something may be done at all; the layer table, the routing table, the handle reference and the counts follow the release; every handle ticks to @1.4 and 1.3 stays readable at @1.3. server.json at 2026.10.29 for the MCP Registry.
  • 0.3.1 (2026-10-26) — the author page (https://matryoshkaparadigms.com/author) and the publisher, Matryoshka Paradigms LLC (Oregon), named in this README, OVERVIEW.md, DECISIONS.md, the skill's metadata and the plugin manifest, so that an agent reading the repository reaches the same author and organization entities as the card, the endpoint and the site. No change to the skill's steps, shapes or payment rules; document version 1.3 and endpoint build 2026.10.22 unchanged.
  • 0.3.0 (2026-10-22) — document version 1.3 on endpoint build 2026.10.22. Three decision rules re-worded where small models misread them (the runway floor as one number with the reserve part of it; reinvestment funded from the whole balance, the reserve-first reading named as excluded; the gross and the net cash cycle both named, the tie-up on the gross) — every handle is @1.3, the 1.2 and 1.0 texts stay readable at their own handles. A third variant of every node, ?variant=agent: the accepted text as fields (scope, inputs, rule, action, check, reasoning, units, a worked example, the applied route, the recheck, and two strings to paste — recheck_note and closing_citation), the same price; bf_read_node takes it too. Every bundle at a flat USD 0.05, band included, and the access sentence re-stated on every surface; the per-payment cap in the skill falls to USD 0.05. The skill's step 8 says how to answer with a node in hand (the decision in one sentence, the first step, the reason, the next check, the offer to write the recheck into the user's notes, the citation last) and sends figures to the applied route rather than computing by hand. The six MCP tools declare output schemas; the payment-required tool result carries the 402's facts; openapi.json carries real response examples for the applied routes.
  • 0.2.0 (2026-10-10) — document version 1.2 on endpoint build 2026.10.10: 59 nodes (32 re-cut in one shape — lede, conditions, reasoning — and served full or terse at the same price; 27 new: the market branch with its why node, six method nodes, four scale bands, six chain patterns and five applied decisions, and the free decision branch on parameters, extension and effort). Twenty quoted bundles behind a free deterministic resolver (POST /resolve). The skill routes narrow questions to one node and broad ones to a quote, adds the market and bundle rows to its table, raises the per-payment cap to USD 0.25 for bundles, and states the two variants. Every handle is @1.2; the 1.0 text stays readable at @1.0. The MCP server has six tools. 0.1.4's skill fix and evals/ are included.
  • 0.1.4 (2026-10-10) — the skill body no longer writes a dollar sign directly before a digit: Claude Code reads $0, $1 and $5 in a skill as argument placeholders, so on a load with arguments the prices, the payment cap and the scale bands reached the model rewritten (found by the eval suite). Amounts now read USD 0.05. evals/ added: a suite for claude plugin eval, free layer only. The skill and this page now ask clients to send a User-Agent header: the host's edge refuses some default client signatures with 403, error 1010, before a request reaches the endpoint.
  • 0.1.3 (2026-10-09) — the skill asks /fit before paying and follows its verdict; the shapes name the JSON 402 body, body_check, HEAD → 402 and the versioned route; the endpoint's data statement (above) is stated in the skill. Endpoint 1.2 deployed the same day: a request log as stated, JSON 402 bodies with the payment terms, the fit block, /llms.txt, /.well-known/x402, /openapi.json, an MCP server at /mcp, and one URL spelling per paid route. The nodes are unchanged at 1.0.
  • 0.1.2 (2026-10-08) — icon; the payment rules say the skill never reads, holds or transmits a key.
  • 0.1.1 (2026-10-08) — OVERVIEW.md and the measurement; the description says to use the skill even when the figures are given; step "say what the framework does not supply"; the pin line.
  • 0.1.0 (2026-10-07) — first release.

來源:README.md,提交 3ace21e

工具

6

bf_catalogue

Business Frameworks: catalogue

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.

輸入參數branch

bf_read_node

Business Frameworks: read a node

Returns one node with its citations and a cite-as line; `variant` chooses full (the default), terse (the lede alone) or agent (the same text as fields: scope, inputs, rule, action, check, units, example, the applied route, the recheck, and two strings to paste: recheck_note and closing_citation) at the same price. Free nodes (marked in bf_catalogue) cost nothing; the rest cost their catalogue price ($0.02 to $0.05, USDC on Base over x402), charged once per call, only when the node is returned. Call it with a `path` from bf_catalogue when the question needs that node's rule; prefer variant agent when you will answer from it (the decision in one sentence, the first step, the reason, the next check, the offer to write the recheck into the user's notes, then closing_citation last). Read the free parent first; use bf_resolve when the question takes several nodes. Do not call a paid path to see what it contains: the catalogue line says what it covers; a rule on numbers is bf_apply_decision.

輸入參數path必填variant

bf_decision_schema

Business Frameworks: decision input schema

Returns the input schema, an example input, the price and the fit record (what the framework does for this decision by model, before paying) 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.

輸入參數decision

bf_apply_decision

Business Frameworks: apply a decision rule

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. When the question gives figures for a decision, the applied route computes them; the answer reports its result and does not recompute it. Do not call it with invented or placeholder figures, and do not treat the verdict as tax, legal or investment advice.

輸入參數input必填decision必填

bf_resolve

Business Frameworks: quote the bundle for a task

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 — one flat price, USD 0.05, with or without its scale band — 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.

輸入參數bundleinputsdecisionquestionrevenue_usdchain_position

bf_read_bundle

Business Frameworks: read a quoted bundle

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 (a flat $0.05 for every bundle, band included; 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.

輸入參數bandbundle必填

版本歷史

5
  1. v2026.10.31最新Nov 1, 2026
  2. v2026.10.30Oct 31, 2026
  3. v2026.10.29Oct 30, 2026
  4. v2026.10.26Oct 29, 2026
  5. v2026.10.10Oct 12, 2026

評分

已滿足適用檢查項的 90%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通必需25 分
  • 已宣告認證方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分

    請在儲存庫或註冊中心條目中宣告授權條款。