게시된 완성 패키지들, 모두 커밋마다 CI가 실행합니다. 가이드와 함께 읽으십시오 — 다 쓰고 난 형식이 어떤 모습인지가 여기 있습니다.
이 아래 설명 본문과, 카탈로그가 저장소에서 실어 오는 것들(요약·방법론·README·라이선스 고지)은 영어입니다. 저장소의 문서에서 생성되는 것이라, 한국어판을 두는 일은 웹에 번역을 붙이는 것이 아니라 원본 문서를 두 벌 유지하겠다는 약속이 됩니다 — 아직 하지 않은 약속입니다.
| 패키지 | 무엇인가 | |
|---|---|---|
| Basic Investor | FinRobot's Data-CoT → Concept-CoT → Thesis-CoT, extended with Portfolio Context and a Decision stage. The reference ManagerPackage. | 자체 제작 |
| Prudent Allocator | Top-down and risk-budget-first. Starts from the book rather than from the asset, sizes every judgement by what a bad outcome costs the portfolio, and acts only when the exposure is wrong. | 자체 제작 |
| AI Hedge Fund — Deep Value | A port of ai-hedge-fund's deep-value pod: Graham, Buffett and Munger read the same point-in-time fundamentals independently, and one reconciliation weighs their convictions. Graham's view counts double, as the source's own strategy file specifies. | 이식 |
Every one of them passes package-lint, which is a dependency-free function and the same one the public catalogue runs at merge. What it checks is shape, never prose — it cannot read a methodology and does not try:
readme, config.schema, provenance.notice — leads to a file that is actually in the package. A dead path fails on the first run rather than at lint, which is the failure this tool exists to move earlier.claude without .claude-plugin/plugin.json loads a plugin directory with no plugin in it, and the session then starts with none of the package's own material..mcp.json that parses, with no server called aumos — that is the name the gateway is written under, and one of the two would silently replace the other.provenance.notice contains the copyright holder verbatim, and the commit is a full 40 characters. A branch name moves, and then names nothing.⚠️ Several rules about what a prompt must say have been retired, and the reason is the same each time: the host now says it. The MCP server states asOf and evidenceIds in its own initialize instructions, and decision_submit publishes the schema a judgement is judged against — so a rule demanding every package restate either would be a demand to duplicate a published specification.
hostile-investor and leaky-investor are in the repository and are deliberately not published. One tries to leave its sandbox and the other tries to reach past the instant it was pinned to; both are evidence — they run in CI in order to fail — and holding a counter-example to the standard of an example would be asking it to stop being one.