TW-Market Live Data Intelligence

TW-Market Live Data Intelligence

English | 繁體中文

Local-first, governed Taiwan-market evidence infrastructure for human operators

and AI agents — validate first, preview bounded work, then explicitly authorize

one execution only when the current capability and route permit it.

Architecture at a glance

flowchart LR

H[Human / Operator] --> W[Unified Workbench] A[AI Agent] --> M[Six-tool MCP] W --> R[Unified Runtime] M --> R R --> V[Validate + Identity] V --> P[Preview + Route Bounds] P --> X[Explicit Authorization] X --> E[Execute Once] E --> S[Governed Official / Approved Sources] S --> O[Result + Audit + AI Handoff] L[Persistent Watchlists] --> W

Current stable release

TW-Market `v1.5.1` is the latest stable GitHub Release, published on 2026-11-04 (23:57 Asia/Taipei). ProductVersion: 1.5.1.

• Frozen source commit: 1f3666eefdca7e2e9a1c88099f802696bf7970d6
• Frozen source tree: d67e9bc1db34ff268b5b8d0f2a301d1a211df3b6
• GitHub v1.5.1 Release
• Windows Native ZIP
• Native SHA-256 sidecar
• Windows MCPB
• MCPB SHA-256 sidecar
• First-party dependency SBOM
• Publication manifest
• Verified publication record

The v1.5.1 tag/source and six published assets remain immutable under release governance. Later documentation-only commits on main are not new v1.5.1 release bytes. GitHub Immutable Releases platform enforcement is not asserted. Previous v1.5.0 remains a valid frozen historical release.

Why upgrade from v1.5.0? Windows Native operator experience

The main v1.5.1 improvement is a guided, operator-first Windows workflow verified across RMA-0 through RMA-11 — not simply an internal patch.

• Open the package-root `Launch-TW-Market.cmd` instead of starting with Python, PowerShell, source folders or manual service commands. The graphical first-run setup checks the external Python 3.13 x64 prerequisite.
• Set up once, operate daily: status cards for Local Runtime, Workbench, Security Master and Local MCP; explicit Start, Stop, Refresh, Diagnose and Open Workbench controls.
• Manage Security Master visibly: Install/Update, confirmation before official-source acquisition, clear restart guidance and a verified-TLS compatibility retry only when justified by current source evidence.
• Build requests without editing raw JSON: Workbench Request Builder, Compose, Validate and Preview; explain blocking conditions and offer bounded recovery guidance before authorization.
• Know exactly when data will be fetched: explicit Authorize, separate network confirmation, and Execute Once; then inspect Result/Audit and export an AI-ready Mode C handoff. Advanced technical payloads remain available but no longer dominate the primary journey.

See the complete Windows Native v1.5.1 guided workflow and RMA-0–11 evidence.

This is not a zero-dependency installer: Python 3.13 x64 is still required; Setup does not install Python or fetch market data; Security Master acquisition and any live evidence execution require explicit operator authorization. No scheduler, automated trading or realtime data guarantee is included.

Choose your path

For a 60-second orientation and first-run sequence, use the Operator Quick Start. The Native ZIP is the recommended operator path; source checkout is not the default installation path for every user.

For developer-only source checkout, python scripts/run_unified_workbench.py and python scripts/run_unified_market_evidence_mcp.py remain explicit advanced entry points; neither replaces the built Native bundle-root Launcher.

What TW-Market is

TW-Market is a governed evidence and research workbench for Taiwan-market data. It gives a human operator or AI agent a deterministic path from target identity and capability validation to bounded source acquisition, canonical Result/Audit materialization, citations, and an AI-ready handoff.

It is intentionally not a broker, autonomous trader, portfolio system, general-purpose crawler, or realtime-price guarantee.

Core product characteristics:

• Local-first: installation state, Security Master, Watchlists, evidence, and audit artifacts remain under explicit local control.
• Identity-aware: Taiwan cash instruments use ISIN as durable identity and MARKET:CODE as listing/routing identity.
• Preview before execute: validation and preview do not authorize network acquisition; execution is explicit, bounded, and auditable.
• Persistent Watchlists are supported: installation-local Watchlists use immutable revisions, optimistic concurrency, and explicit preview/commit mutation.
• Evidence, not conclusions: source authority, timing/currentness, missingness, caveats, and citations remain visible to downstream humans and AI.

Governed workflow

A typical 2330 flow is:

1. Create or select an installation-local Watchlist and add 2330.
2. Compose a Unified Market Evidence Request and validate identity/capability.
3. Preview the exact planned operation and its route boundary.
4. Explicitly authorize one bounded execution only if the preview is executable.
5. Read the canonical Result and Audit Package, or export the AI-ready handoff.

Unified Request v3 is preferred. Request v1/v2 remain supported compatibility contracts; historical supported Result/Audit packages remain readable without rewriting their canonical bytes or provenance.

The Unified MCP surface remains exactly six governed tools:

market_describe_capabilities, market_validate_request, market_preview_request, market_read_result, market_export_ai_handoff, and market_fetch_evidence.

See the AI usage guide and V1 historical public contracts for the current request/result/handoff semantics and compatibility boundary.

View the full Unified Workbench screenshot

Current evidence capabilities

Current governed product scope includes:

• installation-local Taiwan Market Identity Service and persistent Watchlists;
• official material-disclosure and monthly-revenue evidence for eligible TWSE/TPEx company common shares;
• selected bounded market-state, index-futures, institutional-flow, corporate-action, and recent-performance context where current Catalog and Routing authority make the requested market/target executable;
• canonical Result/Audit lineage, citations, timing/currentness semantics, and AI-ready Markdown handoff.

Capability support is not the same as route executability. A known instrument, schema, or capability does not by itself authorize source acquisition. Always validate and preview against the current Catalog and selected Routing.

Research evidence is intentionally bounded. It does not imply arbitrary history, realtime disclosures, a full-market scanner, financial_summary, investment advice, or trading signals.

Safety boundary

There is no automatic polling, scheduler, startup market fetch, Watchlist-driven automatic execution, trading, or order routing. There is also no silent source fallback or model-selected executor/URL. Missing evidence is not converted to zero, and execution success is not presented as a realtime guarantee.

Source/developer quick start

Use the primary source first-run sequence for dependencies, offline lifecycle initialization, Local Service, Workbench and MCP preflight. Initialization and Security Master activation are separate: identity-dependent operations fail closed while identity is unavailable, but health/UI/capability inspection can start after installation initialization. The source MCP stdio adapter requires the running loopback Local Service.

The release ZIP/MCPB installation paths are documented separately; keep those operator instructions distinct from this source/developer path.

MCP distribution and registry boundary

The published GitHub v1.5.1 Release includes the Windows MCPB and its SHA-256 sidecar. This local stdio package exposes exactly six governed tools.

The separate official MCP Registry identity, io.github.SmartyJohnway/tw-market-live-data-intelligence, was checked through the official live Registry API on 2026-11-05: its Latest active version is `1.0.0`. GitHub v1.5.1 publication does not imply Registry v1.5.1 publication; updating server.json requires separate authorization.

See MCP distribution for installation and Unified MCP Reference for the six tools.

Docker is a validated local linux/amd64 build/acceptance and provenance surface only. No Docker registry image is published for v1.5.1.

Documentation

Operator and product docs:

• Operator quick start
• Local Workbench guide
• Troubleshooting
• AI / agent usage guide
• AI discovery entry (llms.txt)
• Capability matrix
• Source matrix
• Documentation index

Engineering/governance front doors:

• PROJECT.md — current project/product authority
• ROADMAP.md — canonical Roadmap V3.2
• HANDOFF.md — current operational handoff
• AGENTS.md — repository and AI collaboration rules

Historical engineering and acceptance records remain available for audit and compatibility, but they are not a second current-product contract. Start with [Project History](docs/PROJECT_