Architecture and Decision Contracts
Understand the shared KabuForge services from registered factors to risk-constrained order intents.
One explicit decision pipeline
Python, CLI, desktop GUI and MCP call shared application contracts. Factor outputs inform strategy decisions; risk controls and execution constraints apply after target construction.
Registered research extensions
Trusted code registers factors with IDs, versions and mandatory validators. Strategies select registered implementation identities. Unknown or duplicate identities fail; configuration cannot request arbitrary Python imports or evaluation. The default strategy registry includes composite_factor version 1.
Planning is a boundary
ApplicationService validates configuration and returns an immutable plan. It cannot submit an order, write a ledger or contact a broker. Planning records explicit clocks, snapshot hashes, research marks, quotes, instruments and account state.
Local simulation and agent access
Historical backtests and paper workflows simulate locally. The agent facade adds bounded paths, JSON-schema validation, credential scanning, durable receipts and SQLite audit state. Real broker transport remains unverified and real order submission is disabled.
Applies to: v0.1.1 · Public source docs/en_US/ARCHITECTURE.md
Reviewed · KabuForge