cyan-eclipse-book 0.1.0__tar.gz

cyan_eclipse_book-0.1.0/.github/workflows/ci.yml

@@ -0,0 +1,37 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+
+permissions:
+  contents: read
+
+concurrency:
+  group: ci-${{ github.ref }}
+  cancel-in-progress: true
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+
+      - name: Byte-compile all Python sources
+        run: python -m compileall -q .
+
+      - name: Validate JSON files
+        run: |
+          for f in *.json; do
+            [ -e "$f" ] || continue
+            python -m json.tool "$f" > /dev/null && echo "OK $f"
+          done
+
+      - name: MCP initialize handshake smoke
+        run: |
+          printf '%s\n' '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"ci","version":"0"}}}' | timeout 30 python server.py | grep -q '"result"'

cyan_eclipse_book-0.1.0/.github/workflows/publish-mcp-registry.yml

@@ -0,0 +1,30 @@
+name: Publish to Official MCP Registry
+
+# Publishes server.json to registry.modelcontextprotocol.io using GitHub OIDC
+# (no stored secrets). Run manually after changing server.json - each publish
+# needs a new unique "version" in server.json.
+on:
+  workflow_dispatch:
+
+permissions:
+  id-token: write
+  contents: read
+
+jobs:
+  publish:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Install mcp-publisher
+        run: |
+          curl -L "https://github.com/modelcontextprotocol/registry/releases/download/v1.8.4/mcp-publisher_linux_amd64.tar.gz" | tar xz mcp-publisher
+
+      - name: Validate server.json
+        run: ./mcp-publisher validate
+
+      - name: Login with GitHub OIDC
+        run: ./mcp-publisher login github-oidc
+
+      - name: Publish
+        run: ./mcp-publisher publish

cyan_eclipse_book-0.1.0/.github/workflows/publish-pypi.yml

@@ -0,0 +1,64 @@
+name: Publish to PyPI
+
+# Gate S5 (applies to every artifact in the PyPI slate): releases
+# build ONLY here, from a tagged commit, and publish via Trusted
+# Publishing (OIDC) - no long-lived PyPI tokens anywhere, no laptop
+# uploads. PEP 740 attestations are generated by the publish action.
+on:
+  push:
+    tags: ["v*"]
+  workflow_dispatch:
+
+permissions:
+  contents: read
+
+concurrency:
+  group: publish-pypi-${{ github.ref }}
+  cancel-in-progress: false
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+
+      - name: Run the test suite
+        run: python -m unittest discover -s tests
+
+      - name: Build wheel + sdist
+        run: |
+          pip install build
+          python -m build
+
+      - name: twine check
+        run: |
+          pip install twine
+          twine check dist/*
+
+      - uses: actions/upload-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+  publish:
+    needs: build
+    runs-on: ubuntu-latest
+    environment:
+      name: pypi
+      url: https://pypi.org/project/cyan-eclipse-book/
+    permissions:
+      id-token: write
+    steps:
+      - uses: actions/download-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+      - name: Publish to PyPI (Trusted Publishing, PEP 740 attestations)
+        uses: pypa/gh-action-pypi-publish@release/v1
+        with:
+          attestations: true

cyan_eclipse_book-0.1.0/.github/workflows/release.yml

@@ -0,0 +1,33 @@
+name: Release
+
+on:
+  push:
+    tags: ["v*"]
+
+permissions:
+  contents: write
+
+concurrency:
+  group: release-${{ github.ref }}
+  cancel-in-progress: false
+
+jobs:
+  release:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Build distributable (git archive of the tag)
+        run: |
+          name="eclipse-book-mcp-${GITHUB_REF_NAME}"
+          git archive --format=zip --prefix="${name}/" -o "${name}.zip" HEAD
+          ls -la "${name}.zip"
+
+      - name: Publish GitHub Release with artifact
+        env:
+          GH_TOKEN: ${{ github.token }}
+        run: |
+          gh release create "${GITHUB_REF_NAME}" \
+            --title "${GITHUB_REF_NAME}" \
+            --generate-notes \
+            "eclipse-book-mcp-${GITHUB_REF_NAME}.zip"

cyan_eclipse_book-0.1.0/.gitignore

@@ -0,0 +1,18 @@
+data/
+__pycache__/
+keys/
+*.key
+*.pem
+.env
+.env.*
+*.pyc
+state/
+
+# --- probe-mirror standard protections (2026-11-02) ---
+id_rsa*
+.git-credentials
+credentials*.json
+*secret*
+*.tfstate
+*.tfstate.*
+.mcp.json

cyan_eclipse_book-0.1.0/BENCH-VERITY.md

@@ -0,0 +1,156 @@
+# BENCH-VERITY — Cyan Eclipse Book MCP v0.1.0
+
+**Verdict: PASS-WITH-CONDITIONS**
+**Scope: local stdio build (working tree of `eclipse-book-mcp`,
+v0.1.0, as run from this network seat (VM egress,
+America/Los_Angeles host) on 2026-11-02/03.** Bench:
+`/tmp/bench-evidence/bench_book.py` — 28 independent checks,
+black-box over stdio JSON-RPC; the bench never imports
+`book_engine` — fee math, quote fields, criteria hashes and the
+receipt chain were recomputed by the bench's own Decimal/sha256
+code from raw inputs. Builder's own suites re-run green from a
+clean sibling checkout (19/19 unittest + stdio smoke) — baseline
+only, not bench evidence. Live venue payloads were fetched by
+the bench seat itself from the venues' public APIs (direct
+egress, no auth, no accounts, no keys) and fed through the
+server's transport seam (`instrument_ingest` / `book_ingest`) —
+M0 contains no network code path of its own (verified at source:
+no socket/urllib/http code in `server.py` / `book_engine.py`).
+
+## What was verified
+
+- **Handshake + surface (B1–B2).** `initialize` returns
+  `eclipse-book` / `0.1.0`; `tools/list` is exactly the 17 M0
+  tools the manifest claims — no more, no fewer.
+- **Denylist (B3).** 17 forbidden/variant names — `order_place`,
+  `withdraw`, `recommend`, `probability_get`, `signal_get`,
+  `buy`, `sell`, `account_get`, plus case variants
+  (`Order_Place`, `ORDER_SUBMIT`), a separator variant and a
+  Cyrillic-confusable `probаbility_get` — all refused with
+  JSON-RPC `-32602` by name.
+- **Malformed args (B4).** Missing required fields refuse with
+  named `ToolError`s (`INSTRUMENT_FIELD_REQUIRED`,
+  `RESOLUTION_CRITERIA_REQUIRED`); a missing `size` on
+  `quote_get` surfaces a JSON-RPC error and the process stays
+  alive and correct afterwards (no crash).
+- **Live Kalshi read (B5–B6).** Market `KXFEDDECISION-28JAN-H26`
+  fetched live: verbatim `rules_primary` ingested as the
+  resolution criteria; the bench's independent sha256 of the
+  criteria text matches the stored criteria hash. Kalshi's
+  native status `active` — not in the core vocabulary —
+  surfaced as `UNMAPPED` with the native string preserved,
+  never coerced. The live order book (YES bids as published;
+  YES asks derived from NO bids as `1 − price`, the venue's own
+  book construction) produced a quote whose bid / ask / mid /
+  spread_bps / liquidity flag matched the bench's independent
+  recomputation exactly (0.08 / 0.14 / 0.11 / 5454.54… bps /
+  THIN — $14.42 notional at best ask). With no Kalshi fee
+  schedule registered, the quote carried
+  `fee_status: NO_SCHEDULE` and both all-in fields degraded to
+  `FEE_UNVERIFIED` — no wrong number quoted. The verbatim
+  criteria + its hash ride on the quote.
+- **Live Polymarket read (B7).** Gamma market
+  `will-gavin-newsom-win-the-2028-democratic-presidential-nomination-568`
+  + its live CLOB book (46 levels, returned unsorted by the
+  venue) fed raw through `book_ingest`: the core sorted to the
+  bench's independently computed best bid 0.157 / best ask
+  0.158.
+- **Fee truth (B8–B9).** On the bench's own numbers (25 bps,
+  100.00/100.50 book, size 40): all-in buy 4030.05 (fee 10.05),
+  all-in sell 3990 (fee 10), per-unit figures exact to the
+  string; liquidity DEEP at $50,250 notional. A schedule 72 h
+  old against a 24 h freshness window → `fee_status: STALE`,
+  all-in fields `FEE_UNVERIFIED`. A 0-bps FRESH schedule on the
+  live Kalshi book: all-in buy total exactly 1.4 (0.14 × 10,
+  fee 0).
+- **Probability law (B10, B15).** An ingest carrying
+  `provenance.probability_of_yes` was refused
+  `PROBABILITY_FIELD_FORBIDDEN` **pre-commit** — no instrument
+  persisted, receipt count unchanged (the 2026-10-25 Test Bench
+  post-commit observation is closed in this build). A nested,
+  capitalized `trading_window.window.Probability` key was
+  likewise refused. A scan of all 31 outputs produced during
+  the bench found no probability-, recommendation-, signal-,
+  advice- or rating-shaped key anywhere.
+- **Criteria pinning (B11).** Position opened on the live
+  Kalshi instrument; a one-word criteria edit on re-ingest
+  produced a `CRITERIA_CHANGED` event (old hash = the live
+  rules hash), and the position still carries the as-of-entry
+  criteria + hash with `criteria_changed_since_entry: true`.
+- **Resolution fences (B12).** `resolution_verify` against a
+  wrong source was refused by name
+  (`RESOLUTION_SOURCE_MISMATCH`, naming 'Federal Reserve'); an
+  open dispute blocked verification (`RESOLUTION_DISPUTED`);
+  after `dispute_cleared`, verification against the criteria's
+  own named source → `VERIFIED`.
+- **Order fence (B13).** `ICEBERG` refused
+  (`ORDER_TYPE_NOT_IN_V1_ALLOWLIST`); a LIMIT draft records
+  `status: DRAFT`, `mandate_pre_eval:
+  NOT_EVALUATED_M0_DATA_ONLY`, with a receipt ref. No
+  submission path exists.
+- **Ledger (B14).** The bench recomputed the full receipt
+  hash chain from the state file with its own implementation —
+  12 receipts, chain valid, matching the server's own
+  `chain_valid: true`.
+- **Venue status (B16).** `capability: M0_DATA_ONLY`,
+  `order_tools: ABSENT`, `account_tools: ABSENT`.
+
+## Conditions
+
+- **C-B1 (minor, non-blocking).** `max_payout_for_size` — a
+  fee-independent figure (size × $1) — is attached to an
+  event-contract quote only when the fee schedule is FRESH;
+  under `NO_SCHEDULE` / `STALE` it is omitted along with the
+  all-in fields. Absence, never a wrong number — but the
+  payout does not depend on the fee schedule and the spec's
+  quote shape implies it attaches. Queued as an M1 fix.
+- **C-B2 (publish hygiene, non-blocking for use).** Version
+  drift: `server.json` reads 0.1.1 while `VERSION`,
+  `pyproject.toml` and the server's own version string read
+  0.1.0. OWNER-HANDS ship-day step 1 requires agreement before
+  tagging; reconcile before the PyPI/MCP-Registry publish.
+
+## Scope fences on this verdict
+
+- PASS-WITH-CONDITIONS covers the M0 data core above: local
+  stdio build + live **public reads** from Kalshi and
+  Polymarket as ingested through the transport seam from this
+  seat on 2026-11-03. Book itself makes no network calls; the
+  live step verified is the seam + normalization + law against
+  real venue payloads, not a shipped venue adapter.
+- NOT_RUN / out of scope, unchanged from the manifest: order
+  placement, account reads, the Wallet mandate gate (M2/M1,
+  owner-gated, spec §18 D3); fee schedules as live venue data
+  (Kalshi's published fee formula is not bps-shaped; no live
+  schedule was registered for a venue — venue quotes honestly
+  degrade to `FEE_UNVERIFIED`); Polymarket US / Kraken /
+  Binance.US / Alpaca chapters (specced, not built).
+- The market-data gate fences were probed, not assumed: no
+  tool emits a recommendation, signal, ranking or probability
+  (B3/B10/B15); copy in README + manifest carries no
+  advice-shaped claims.
+
+— Verity bench, 2026-11-02
+
+**Postscript (2026-11-02, ship-day execution).** C-B2
+reconciled to 0.1.0 across VERSION / pyproject / server.json
+(the MCP Registry already held book@0.1.0, so the registry
+snapshot and the package now describe the same build); tree
+committed (371b61e) and tag v0.1.0 pushed. The Publish-to-PyPI
+run (gh 41557921209) FAILED in the build job's test step —
+the test loader assumed the suite's sibling layout, which a
+standalone checkout doesn't have — and the publish job never
+ran: nothing reached PyPI (verified after the fact via the
+JSON API, the simple index, and pip; an interim "uploaded"
+reading from this VM's egress was a false signal and is
+withdrawn). Loader fixed with an in-repo fallback + the
+cross-adapter parity test now skips with a stated reason
+when siblings are absent (commit c60ba0d; standalone suite
+green: 18 pass + 1 skip; sibling layout 19/19 + smoke).
+OWNER-HANDS' Trusted Publisher table also named the wrong
+repo (`eclipse-book-mcp`; actual: `cyan-eclipse-book-mcp`) —
+corrected in the same commit. Re-run is HELD pending the
+owner's delete + re-add of the pending publisher under the
+corrected repo name; on his confirmation the v0.1.0 tag
+re-points to c60ba0d and the workflow re-runs by dispatch on
+that ref.

cyan_eclipse_book-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Cyan Eclipse Technologies LLC
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

cyan_eclipse_book-0.1.0/OWNER-HANDS.md

@@ -0,0 +1,33 @@
+# OWNER-HANDS - cyan-eclipse-book PyPI launch (renamed from eclipse-book, 2026-10-28)
+
+Everything in this file is done **by the owner, in the owner's
+browser**. The package is built and locally proven (wheel + sdist,
+clean-venv install, MCP handshake against the installed entry point);
+it is **not yet published** - no Trusted Publisher exists for this
+project yet.
+
+> **Stop rule:** no step below creates or hands over an API token.
+> Publishing runs on Trusted Publishing (OIDC) only.
+
+## Trusted Publisher for `cyan-eclipse-book` (pending publisher)
+
+On <https://pypi.org/manage/account/publishing/> - "Add a new pending
+publisher" - **GitHub** tab. Enter these strings **exactly**:
+
+| Field | Value |
+|---|---|
+| PyPI Project Name | `cyan-eclipse-book` |
+| GitHub Repository Owner | `CYAN-ECLIPSE-TECHNOLOGIES-LLC` |
+| GitHub Repository Name | `cyan-eclipse-book-mcp` |
+| GitHub Workflow Name | `publish-pypi.yml` |
+| Environment Name | `pypi` |
+
+## Ship day (after the publisher above exists)
+
+1. Agent verifies `VERSION` + `server.json` agree at the release
+   version and the full test suite is green.
+2. Owner reviews; agent tags `v<version>` and pushes the tag.
+   **Do not tag before the Trusted Publisher exists** - the
+   `publish-pypi.yml` workflow fires on `v*` tags and will fail.
+3. GitHub Actions then builds, runs `twine check`, and publishes to
+   PyPI via Trusted Publishing with PEP 740 attestations.

cyan_eclipse_book-0.1.0/PKG-INFO

@@ -0,0 +1,50 @@
+Metadata-Version: 2.5
+Name: cyan-eclipse-book
+Version: 0.1.0
+Summary: Market data + venue access layer — not an exchange: one book, one fee truth, one ledger of record.
+Project-URL: Homepage, https://cetech.ai
+Project-URL: Repository, https://github.com/CYAN-ECLIPSE-TECHNOLOGIES-LLC/eclipse-book-mcp
+Project-URL: Vendor, https://cetech.ai
+Author: Cyan Eclipse Technologies LLC
+License: MIT
+License-File: LICENSE
+Keywords: fees,market-data,mcp,model-context-protocol,venues
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Programming Language :: Python :: 3
+Classifier: Topic :: Software Development :: Libraries
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+
+# cyan-eclipse-book
+
+mcp-name: io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC/book
+
+**What this is:** the MCP server for **Eclipse Book MCP** - The Market Core of the Eclipse Markets suite (spec eclipse-markets-suite-spec-20261025): one canonical Instrument / Book / Quote / Order / Position / Resolution model over exchanges and prediction markets, with venue adapters that translate and never improvise. Resolution criteria are stored verbatim and hash-pinned — a venue criteria edit is a CRITERIA_CHANGED event and positions keep the criteria as of entry. Quotes carry all-in buy/sell cost for a stated size from versioned, provenance-stamped fee schedules; a stale or missing schedule degrades all-in fields to FEE_UNVERIFIED rather than quoting a wrong number. Resolutions move REPORTED -> VERIFIED only against the criteria's own named source (DISPUTED is first-class), and no core output ever carries a probability field — outputs carry price + liquidity flag + depth + verbatim criteria. M0 is data only: no accounts, no keys, no order submission at any tier; order_draft is an unsubmitted record whose mandate pre-evaluation is honestly NOT_EVALUATED until the owner-gated M2.
+
+## Run it
+
+```console
+$ pip install cyan-eclipse-book
+$ eclipse-book           # MCP over stdio, Python stdlib only
+```
+
+MCP client config:
+
+```json
+{ "mcpServers": { "cyan-eclipse-book": { "command": "uvx", "args": ["--from", "cyan-eclipse-book", "eclipse-book"] } } }
+```
+
+## Tools (17)
+
+`instrument_ingest` - `instrument_get` - `instrument_search` - `book_ingest` - `quote_get` - `fee_schedule_register` - `fee_schedule_get` - `position_open` - `position_list` - `position_get` - `resolution_report` - `resolution_verify` - `resolution_get` - `order_draft` - `order_get` - `venue_status` - `receipt_list`
+
+## Honest scope
+
+- In development — v0.1.0 M0 local build (Market Core, data only; fixtures behind transport seams; CERTIFIED(local) — Eclipse Bazaar Test Bench 2026-10-25)
+- State and runtime data files ship in the wheel beside `server.py`,
+  at the same relative paths the server reads them from.
+
+Powered by Cyan Eclipse Technologies LLC (cetech.ai) - a Veteran-Owned
+Small Business. MIT licensed.

cyan_eclipse_book-0.1.0/PYPI_README.md

@@ -0,0 +1,31 @@
+# cyan-eclipse-book
+
+mcp-name: io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC/book
+
+**What this is:** the MCP server for **Eclipse Book MCP** - The Market Core of the Eclipse Markets suite (spec eclipse-markets-suite-spec-20261025): one canonical Instrument / Book / Quote / Order / Position / Resolution model over exchanges and prediction markets, with venue adapters that translate and never improvise. Resolution criteria are stored verbatim and hash-pinned — a venue criteria edit is a CRITERIA_CHANGED event and positions keep the criteria as of entry. Quotes carry all-in buy/sell cost for a stated size from versioned, provenance-stamped fee schedules; a stale or missing schedule degrades all-in fields to FEE_UNVERIFIED rather than quoting a wrong number. Resolutions move REPORTED -> VERIFIED only against the criteria's own named source (DISPUTED is first-class), and no core output ever carries a probability field — outputs carry price + liquidity flag + depth + verbatim criteria. M0 is data only: no accounts, no keys, no order submission at any tier; order_draft is an unsubmitted record whose mandate pre-evaluation is honestly NOT_EVALUATED until the owner-gated M2.
+
+## Run it
+
+```console
+$ pip install cyan-eclipse-book
+$ eclipse-book           # MCP over stdio, Python stdlib only
+```
+
+MCP client config:
+
+```json
+{ "mcpServers": { "cyan-eclipse-book": { "command": "uvx", "args": ["--from", "cyan-eclipse-book", "eclipse-book"] } } }
+```
+
+## Tools (17)
+
+`instrument_ingest` - `instrument_get` - `instrument_search` - `book_ingest` - `quote_get` - `fee_schedule_register` - `fee_schedule_get` - `position_open` - `position_list` - `position_get` - `resolution_report` - `resolution_verify` - `resolution_get` - `order_draft` - `order_get` - `venue_status` - `receipt_list`
+
+## Honest scope
+
+- In development — v0.1.0 M0 local build (Market Core, data only; fixtures behind transport seams; CERTIFIED(local) — Eclipse Bazaar Test Bench 2026-10-25)
+- State and runtime data files ship in the wheel beside `server.py`,
+  at the same relative paths the server reads them from.
+
+Powered by Cyan Eclipse Technologies LLC (cetech.ai) - a Veteran-Owned
+Small Business. MIT licensed.

cyan_eclipse_book-0.1.0/README.md

@@ -0,0 +1,43 @@
+# Eclipse Book MCP
+
+**Powered by Cyan Eclipse Technologies** — https://cetech.ai
+
+**Eclipse Book — market data + venue access layer: exchanges and prediction markets, normalized: one book, one fee truth, one ledger of record.**
+
+> **WORKING NAME — conditional pass.** "Eclipse Book" passed the brand §3 naming test conditionally (spec §3.1): the descriptor above is **mandatory** wherever the name appears, because "book" can echo *bookmaker* — and this product is not one. **Eclipse Book is a market data + venue access layer — not an exchange**: it is not a matching engine, never crosses orders, never holds funds, and takes no other side of any trade. The name never appears shortened in sports contexts (spec §2.3).
+
+## Why this exists
+
+Every price an agent acts on is a fact about **a venue, at a moment, at a depth** — and for event contracts, a fact about a set of words that decide settlement. Raw venue feeds hide all three: fees sit in schedules nobody re-reads, liquidity sits behind a single headline price, and resolution criteria get edited quietly. Book is the normalization + governance core of the Markets suite: one instrument model, one book model, one fee-truth rule, one resolution-verification discipline, one hash-chained ledger — with venue adapters (Forecast, Strike first) that translate and never improvise.
+
+## Status — honest labels
+
+v0.1.0, phase **M0 (Market Core, data only)**. Local stdio transport, Python stdlib only, **no network calls, no accounts, no API keys, no order submission at any tier, and no certification claimed — bench pending.** Own suites: 16/16 tests + stdio smoke passing. Adapters run against fixtures behind transport seams; live venue reads are a later verification step and are labeled `not_tested` in the manifest. Placement is M2 and owner-gated per venue (spec §18, decision D3); withdrawals are T3-always by design when they arrive (§7.3).
+
+## What the core owns
+
+- **Canonical objects** — `Instrument`, `Book`, `Quote`, `Order` (draft records only in M0), `Position`, `Resolution`. Decimal strings end-to-end; no float math on money paths.
+- **Native truth preserved (spec §5.2)** — venue statuses that don't map into the core vocabulary surface as `UNMAPPED` with the native string kept, never coerced to the nearest familiar state.
+- **Resolution criteria are part of the instrument (§5.4)** — stored **verbatim**, hash-pinned at first read. If a venue edits criteria mid-market, ingest records a `CRITERIA_CHANGED` event with both hashes; a recorded **position keeps the criteria as of its entry** beside the current text, so the change is flagged, never silently absorbed.
+- **Fee truth (§5.3)** — every `Quote` carries **all-in** buy/sell cost for a stated size, computed from a **versioned, provenance-stamped fee schedule** (source + fetched-at required). A stale or missing schedule degrades the all-in fields to **`FEE_UNVERIFIED`** rather than quoting a wrong number — a wrong all-in is worse than no number.
+- **Resolution lifecycle (§5.4)** — a venue-reported resolution starts `REPORTED` (a claim, not a fact) and becomes `VERIFIED` only when checked against the criteria's **own named source of truth**; any other source is refused by name. `DISPUTED` is a first-class state and blocks verification until the dispute clears.
+- **Liquidity + probability honesty (§5.5)** — every Quote carries price, a core-owned `liquidity_flag` (DEEP / FRAGILE / THIN, from notional at best), depth summary, and — for event contracts — the verbatim criteria. **The core never emits a probability field**: a guard scans every quote/position/resolution output and refuses if a probability-shaped key appears. A 0.90 price on $200 of depth renders as price · THIN · $200 at best · criteria attached — an output that cannot be honestly misread as "90% likely."
+- **The ledger** — append-only, hash-chained receipts (GENESIS-anchored) for ingests, criteria changes, fee-schedule registrations, position records, drafts, and resolution transitions. Tamper-evident by construction and tested.
+
+## Tools (17, all M0 data/read/record)
+
+`instrument_ingest` · `instrument_get` · `instrument_search` · `book_ingest` · `quote_get` · `fee_schedule_register` · `fee_schedule_get` · `position_open` · `position_list` · `position_get` · `resolution_report` · `resolution_verify` · `resolution_get` · `order_draft` · `order_get` · `venue_status` · `receipt_list`
+
+The denylist is stated in code: `order_place`, `order_submit`, `withdraw`, `account_get`, `create_api_key`, `margin_open`, `recommend`, `probability_get`, and kin return JSON-RPC `-32602` by name. `order_draft` builds an **unsubmitted** DRAFT (MARKET/LIMIT only) whose mandate pre-evaluation honestly reads `NOT_EVALUATED_M0_DATA_ONLY` — the Wallet gate is wired at M2, not simulated here.
+
+## The line (spec §8)
+
+No leverage, margin, or derivatives in v1. No access circumvention. No advice — the suite carries data, records, and (later) the owner's own mandates; recommendation-shaped output is a refused surface, not a disclaimed one. No market abuse, no data resale, no custody: the suite holds credentials (from M1), never assets. This is data and tooling, **not financial advice** — and Test Bench certification, when it comes, will certify normalization, gates, and receipts, never trading outcomes.
+
+## Layout
+
+`server.py` (MCP stdio) · `book_engine.py` (the suite law, imported by adapters) · `fixtures.json` (fee schedules + config seeds) · `tests/` · `smoke.py` · `make_icon.py` / `icon-512.png` (§6).
+
+State: `$ECLIPSE_BOOK_STATE` or `./data/state.json`, shared with the suite's adapters — adapters hold no second copy of the law.
+
+A Cyan Eclipse Technologies product. The "Powered by Cyan Eclipse Technologies" attribution travels with it.

cyan_eclipse_book-0.1.0/VERSION

@@ -0,0 +1 @@
+0.1.0

cyan_eclipse_book-0.1.0/bazaar-manifest.json

@@ -0,0 +1,66 @@
+{
+ "bench": {
+  "bench_verdict": "CERTIFIED(local)",
+  "certified": true,
+  "checks": [
+   "criteria edit mid-position: one-word change -> CRITERIA_CHANGED event + receipt; position keeps as-of-entry, flag set",
+   "resolution_verify against a WRONG source refused by name; correct source verifies",
+   "DISPUTED blocks verification until cleared",
+   "fee math recomputed independently (all-in buy AND sell, per-unit + total); event-contract max payout attached",
+   "missing schedule AND stale schedule -> FEE_UNVERIFIED while bid/ask still serve",
+   "probability scan: planted keys in provenance, criteria-object field name, nested trading_window \u2014 never emitted; verbatim carriers refused by name",
+   "UNMAPPED native status preserved verbatim",
+   "order_draft: DRAFT only, NOT_EVALUATED mandate note, receipt ref; off-allowlist type refused",
+   "capability denylist by enumeration: exactly the 17 M0 tools; placement/withdraw/account/advice names refused",
+   "auth enforced",
+   "schema valid",
+   "no network surface (source-level)",
+   "no secret leak",
+   "sane errors",
+   "process health",
+   "audit completeness (receipt chain recomputed independently)",
+   "bench isolation"
+  ],
+  "not_tested": [
+   "Live venue reads inside the shipped build \u2014 M0 contains no network code path; live Kalshi/Polymarket public payloads were verified through the transport seam from the Verity bench seat 2026-11-02 (BENCH-VERITY.md: PASS-WITH-CONDITIONS), but no in-build live adapter ships in v0.1.0.",
+   "Order placement, account reads, and the Wallet mandate gate \u2014 M2/M1 scope, owner-gated (spec 18, decision D3). M0 order_draft records an unsubmitted DRAFT with mandate_pre_eval NOT_EVALUATED; no submission path exists.",
+   "Fee schedules as live data \u2014 shipped schedules are fixture-shaped records with provenance labels saying so; the live fetch + account-specific tier provenance lands with the adapters' live step.",
+   "Kalshi / Polymarket US / Kraken / Binance.US / Alpaca chapters \u2014 specced (suite spec 10-12), not built in M0."
+  ],
+  "scorecard_ref": "test-bench/results/eclipse-book-mcp-2026-10-25.json",
+  "status": "CERTIFIED(local) \u2014 Eclipse Bazaar Test Bench 2026-10-25 (scorecard eclipse-book-mcp-2026-10-25.json): 16 pass / 1 na / 0 fail over 17 checks incl. bench isolation. M0 data-only scope; live venue reads not_tested per the preserved not_tested list."
+ },
+ "category": "Markets / Exchange & Prediction-Market Infrastructure",
+ "created": "2026-10-25",
+ "description": "The Market Core of the Eclipse Markets suite (spec eclipse-markets-suite-spec-20261025): one canonical Instrument / Book / Quote / Order / Position / Resolution model over exchanges and prediction markets, with venue adapters that translate and never improvise. Resolution criteria are stored verbatim and hash-pinned \u2014 a venue criteria edit is a CRITERIA_CHANGED event and positions keep the criteria as of entry. Quotes carry all-in buy/sell cost for a stated size from versioned, provenance-stamped fee schedules; a stale or missing schedule degrades all-in fields to FEE_UNVERIFIED rather than quoting a wrong number. Resolutions move REPORTED -> VERIFIED only against the criteria's own named source (DISPUTED is first-class), and no core output ever carries a probability field \u2014 outputs carry price + liquidity flag + depth + verbatim criteria. M0 is data only: no accounts, no keys, no order submission at any tier; order_draft is an unsubmitted record whose mandate pre-evaluation is honestly NOT_EVALUATED until the owner-gated M2.",
+ "icon": "icon-512.png",
+ "name": "Eclipse Book MCP",
+ "powered_by": "Cyan Eclipse Technologies",
+ "price_model": "Free local v0.1; family pricing TBD per spec",
+ "repo": null,
+ "slug": "eclipse-book-mcp",
+ "status": "Live \u2014 v0.1.0 M0 local build (Market Core, data only; CERTIFIED(local) \u2014 Eclipse Bazaar Test Bench 2026-10-25; Verity bench 2026-11-02 PASS-WITH-CONDITIONS incl. live Kalshi/Polymarket public reads via the transport seam \u2014 see BENCH-VERITY.md)",
+ "tagline": "Market data + venue access layer \u2014 not an exchange: one book, one fee truth, one ledger of record.",
+ "tools": [
+  "instrument_ingest",
+  "instrument_get",
+  "instrument_search",
+  "book_ingest",
+  "quote_get",
+  "fee_schedule_register",
+  "fee_schedule_get",
+  "position_open",
+  "position_list",
+  "position_get",
+  "resolution_report",
+  "resolution_verify",
+  "resolution_get",
+  "order_draft",
+  "order_get",
+  "venue_status",
+  "receipt_list"
+ ],
+ "transport": "MCP over stdio (HTTP transport on roadmap)",
+ "vendor": "Cyan Eclipse Technologies",
+ "x402_ready": false
+}