English · 简体中文

From source to boundaries, every step is visible.

Turn complete task requirements into an evidence-linked 7+1 relational representation, then check it with a deterministic Core.
Inspect plans and task decompositions, and trace the evidence for Violation, Within bounds or Incomplete information.

▶ Try the demo　·　MCP setup　·　Paper

Chinese & English · MCP 0.4.0-rc.7 / B-335 · Research & protocol material · Original Core source private

Start with a real case

In ENG20-003, five tasks span several roles. Their combined dependencies form a strict A → B → C → D → A cycle. BoundaryXP brings those dependencies into one graph and preserves the original English sources and calculation records for inspection.

Click the radar to inspect evidence →　·　Read and export the 7+1 report →

Different cases, different results

Result / case	What to inspect
Violation · RT044	Local orders combine into a strict dependency cycle
Within bounds · RT042	Adjacent half-open 10–11 and 11–12 bookings release the endpoint
Incomplete information · L23-050	“Confirmed by him” has no unique owner binding; U1 remains unknown

Two cases have original English sources: ENG20-001 · Branches and a join (Within bounds) and ENG20-003 · Four-step dependency cycle (Violation).

All five come from saved 58618 records, retaining task trees, exact sources, verdicts and seven-step reports. Reports and Markdown exports follow the top-right language switch; source evidence keeps its original language. The demo replays B-332 records without connecting to a local service or running new analysis. B335 upgrades do not regenerate those records. Demo and saved reports

See the English report and original task text

Connect to your AI workflow

BoundaryXP MCP connects through standard stdio to Cursor, Codex and compatible hosts, with 18 tools, 10 resources and a local browser workbench. The Windows x64 package includes the compiled native Core; no separate 58618 installation or hosted BoundaryXP server is required.

1. Install from npm: use boundaryxp-mcp@0.4.0-rc.7, available through the next prerelease channel. GitHub Releases retain the matching archive and SHA-256.
2. Install and connect: follow the guide to configure the host's stdio MCP server.
3. Configure a model API: new analysis uses your own provider/API access. Cursor or Codex subscription allowances are not inherited.
4. Open the workbench: import complete task text, preview and confirm the task tree, then analyze and inspect evidence and reports.

English installation guide → · 中文安装 · Tools and resources · Updates, rollback and troubleshooting

Current npm release: boundaryxp-mcp 0.4.0-rc.7, B-335 / Windows x64, MIT. Start with the installation guide, 7+1 introduction, 18 tools and directory status. This product repository is public. Core implementation source remains in a separate private repository.

L2 / L3: industry and enterprise semantics

The same term can mean different things across industries and organizations. L2 / L3 provide selected domain context for interpreting tasks alongside the original evidence.

Semantic library	Purpose
L2 · Industry	Describes domain actions, entities, roles, resources and related terminology to help interpret requirements in their industry context.
L3 · Enterprise	Adds organization-specific terminology, organizational and role names, controlled aliases and other context to distinguish local objects and expressions.

There is no active L1 layer. L0 is the BXP protocol and deterministic Core, not a semantic library. L2 / L3 do not replace source text or change the shared 7+1 verification rules. Loading a library, a job title or a reporting relationship does not grant business authority.

Use through MCP

1. Call bx_dictionaries_list to inspect the L2 / L3 resources available in the current installation and their identifiers and versions.
2. Call bx_dictionaries_bind to validate the selected resources and obtain version-and-digest references, keeping library snapshots distinct.
3. Call bx_dictionary_lookup to look up entries in bound resources. Lookup does not make a semantic ruling or submit analysis.

Ask your host: “List the available BXP L2 and L3 semantic libraries with their identifiers, versions and digests. Wait for my selection before binding; do not submit analysis.”

Install and connect MCP → · Dictionary tool reference · Resource and distribution notices

Available resources are determined by the installed inventory. Manage private enterprise semantic material within its own usage scope. This section documents capabilities and entry points; it does not claim a separate public GitHub library release.

Method and research evidence

BXP: A Method for AI Task Boundary Verification Using a 7+1 Relational Representation
Wei Zhu · English v1.2 / Chinese r23 · First published 2026-11-06

Research cases	Task nodes	Calculation items
625	3,219	3,469

The paper organizes requirements through 7+1 views and shared relations, uses BXP conventions to establish a common mathematical boundary, and checks whether subtasks and their combination exceed the parent task's boundary. Formal arguments state the conditions for the method. These figures describe research coverage, not accuracy. Case-level agreement, item-level differences and incomplete calculations are reported separately.

English PDF · 中文 PDF · Public research package · Materials guide

DOI: 10.5281/zenodo.24072738. Deposited on Zenodo on 2026-11-09, retaining the first GitHub publication date. GitHub paper release and checksums

The RESEARCH_ONLY_1 supplement contains task sources, annotations, 7+1 reports, operands, results, protocol texts, screenshots and independent research verification scripts. It excludes workbench engineering source, runtime dependencies and production prompt templates. It is maintained separately from the MCP test package.

How 7+1 connects the requirements

I Inputs · O Outputs · A Actions · P Responsibilities and division of work · R Resources · V Version / basis · C Completion / stopping, plus independent B Prohibitions.

Shared relations connect objects, conditions, dependencies and handoffs across task boundaries. Missing information stays missing; a role title does not grant authority.

flowchart LR
  A["Complete task text"] --> B["Confirm parent–child task tree"]
  B --> C["LLM joint analysis"]
  D["Selected L2 / L3 dictionaries"] --> C
  C --> E["Shared deterministic Core"]
  E --> F["Evidence, findings and unresolved items"]
  F --> G["Human / host review"]

The B335 workbench makes one semantic request, followed by Core checks, with no separate audit request or automatic retry. LLMs interpret source meaning; Core validates submitted structures, source references, bindings and supported finite operands. Core does not call models, access the network or execute task instructions.

B335 capabilities, input limits and evidence boundaries

• Complete task trees: whole-document UTF-8 .txt / .md import, role headings, explicit task and parent IDs, forward references, multiple levels and relationship preview.
• Inspectable results: task tree, 7+1 radar, model/calculator conclusions, quotations, unresolved items, saved history and exports. Failed attempts remain distinct from saved results.
• L2 / L3: versioned industry and enterprise dictionaries; no active L1 layer. Loading resources does not grant business authority.
• Chinese and English: interface, reports and Markdown exports preserve original sources and saved verdicts. First-time translation calls a model and is cached by snapshot.
• Mathematical input and unknowns: allowed values, uncertain facts and parent/child plan consistency have distinct meanings. Set identities support strings and safe integers without conflating their types or filling in unknown conclusions.
• Startup and recovery: historical jobs load with bounded concurrency under existing recovery rules. Readiness follows HTTP identity verification.

Individual sources and serialized joint input are each limited to 1 MiB; HTTP request bodies to 8 MiB. Oversized input is rejected without truncation; there is no 300-code-point ceiling. See the changelog for features and historical validation scope.

Exact quotations do not prove semantic entailment. A completed job does not mean every proof passed. People and host systems retain business decisions and execution authority; business_decision and execution_authorization remain null.

The reviewed baseline is BXP-0001 0.4.0-draft.2; the workbench still uses a recorded draft.1 attachment. Full migration and protocol conformance are not claimed. Implementation notes · Research evidence

Host analysis and first-time translation may send selected source and dictionary content to the configured model provider. Review this data flow before supplying private material.

Explore further

Looking for	Start here
Industry and enterprise semantics	L2 / L3 overview · Dictionary tools
MCP installation and usage	Setup guide · Release evidence
Method and citation	Research overview · Paper materials
Protocol and implementation differences	BXP protocol · Implementation notes
Version history and contribution	Changelog · Contributing · Documentation

Distribution scope: the Git tree contains paper, protocol, cases, reports, screenshots, independent research verification scripts and MCP documentation. It excludes private workbench implementation source and source-build entry points. Compiled MCP packages are published to npm and mirrored in this repository's Releases. Original Core implementation source is excluded from those packages; adapter, UI and required resources remain readable. Full scope

Public status: the owner has made this product repository public. Historical audit notes describe their recorded state; public visibility alone does not confirm that old GitHub references or caches have been cleared. Audit record

The existing MIT license is retained. Paper, case data and third-party materials have their own usage terms; the MCP package has separate license and third-party notices.