SmartyJohnway/tw-market-live-data-intelligence

English | 繁體中文
> Local-first, governed Taiwan-market evidence for an operator and an AI
> assistant — validate first, preview bounded work, then explicitly authorize
> one execution where the capability permits it.
ProductVersion = 1.0.0. The current stable release is v1.0.0
(GitHub Release).
The published prerelease history is v1.0.0-rc.1
(GitHub Release),
and the earlier stable GitHub Release was v0.1.0. The current development
line now uses Unified Request/Result/Audit V3 as the preferred authority while
retaining V1/V2 compatibility. Phase G G1/G2 runtime capabilities have passed
bounded controlled-live acceptance; Phase H has one active TPEx attention route; broader
Roadmap Phase G/H scope remains explicitly incomplete. This is a local-first
evidence workbench, not a realtime trading product.
Why TW-Market
AI discussion needs evidence with identity, source, timestamp, caveat, and
execution provenance — not an unqualified price claim. This workbench gives a
human operator a governed local path from request validation to an AI-ready
handoff, while retaining a separate audit package.
Quick start
NOT_INITIALIZED is the normal fresh-install state. A Security Master update
is an explicit operator action and may use official external acquisition:
Open the loopback Workbench at /workbench/.
For an MCP host, start the separate stdio launcher:
A governed 2330 workflow
1. Create or select an installation-local Watchlist, then add 2330.
2. Compose a Unified Market Evidence Request and validate its identity.
3. Preview the planned operation and its capability boundary.
4. Explicitly authorize and confirm one bounded execution only when the
preview is executable.
5. Read the canonical Result and Audit Package, or export the AI-ready
handoff for continued discussion.
Core capabilities
- **Identity-aware requests:** Mode A validates targets against the
installation-local Taiwan Market Identity Service.
- **Bounded execution:** Mode B previews, explicitly authorizes, and executes
one request only when its governed capability is executable.
- **Auditable handoff:** Mode C creates a canonical Result, separate Audit
Package, and AI-ready Markdown without dispatching another market source.
- **Persistent Watchlists are supported:** installation-local Watchlists have immutable
revisions, optimistic concurrency, and explicit preview/commit mutation.
- **Official research evidence:** eligible TWSE/TPEX common shares support the
latest completed official material-disclosure batch and latest available
monthly revenue (TWD, unit thousand), using official CSV with an explicit
governed official JSON fallback.
Unified MCP
The MCP surface has exactly six governed tools:
market_describe_capabilities, market_validate_request,
market_preview_request, market_read_result,
market_export_ai_handoff, and market_fetch_evidence.
Request v3 is preferred; Request v1 and v2 remain accepted compatibility
contracts. New governed materializations default to Result v3 and Audit Package
v3, while historical V1/V2/V3 packages remain readable without rewriting. See the
V1 historical public contracts and
current AI usage guide for request, result, and
handoff semantics.