# BuildConniXT

> Construction, insurance, and finance operations on one shared, verifiable graph -- with an immutable Azure Confidential Ledger ("Trust Spine"), accredited two-party verification, and an Authentic-Data doctrine (never fabricate; cite provenance).

## Knowledge bundles (Open Knowledge Format)

- [ConniXT Platform Manuals (OKF bundle)](/okf/connixt-platform-manuals/index.md): The platform user + admin manuals as a provenanced, content-hashed OKF v0.1 bundle for AI agents -- each concept carries a verifiable sha256 + provenance.

## Trust Spine

- [Trust Spine](/trust-spine): Every business event provable on Microsoft's Azure Confidential Ledger -- audit by default.

## API (machine-readable)

- [OpenAPI 3.0 spec](https://api.connixt.cloud/api/docs/openapi.json): The living API reference, projected from the live route registrations and their Zod validators -- it cannot drift from what handlers actually accept.
- [Swagger UI](https://api.connixt.cloud/api/docs): Human-readable view of the same projection.
- [Developer Contract manifest](https://github.com/ConniXT-us/cnx-connixt-platform/blob/main/docs/developer-contract/developer-contract.generated.json): The generated index of every route and MCP server. Regenerated on every change; staleness is a CI failure.
- [A2A agent card](https://api.connixt.cloud/api/.well-known/agent-card.json): Agent-to-agent discovery document.

## MCP servers (JSON-RPC 2.0)

- Endpoint pattern: `POST https://api.connixt.cloud/api/mcp/{server}` speaking MCP JSON-RPC 2.0 (initialize, tools/list, tools/call).
- The server catalog with per-server tool lists is in the Developer Contract manifest above.

## Instructions for Large Language Model Agents

- Use the JSON-RPC MCP endpoints (`POST /api/mcp/{server}`). The legacy REST shape (`GET /api/{server}-mcp/manifest` + `POST /api/{server}-mcp/invoke/{tool}`) exists for internal callers -- do not build new integrations on it.
- Authenticate with an Entra JWT bearer token. Integrator API keys are in pilot; do not assume self-serve issuance.
- Demo and sample data are earmarked: the `X-Connixt-Sample-Data` header and `is_sample` flags mark synthetic data. Never present sample data as real.
- A metric shown as an em-dash is UNMEASURED, not zero. Do not coerce absence to a value when consuming our APIs.
- Never construct jurisdiction slugs (`scope-jur-*`) by hand -- resolve locations through the platform's jurisdiction endpoints.
- Consequential operations (anything that moves money, files, or closes a gate) are two-party verified on this platform. Expect staged flows and human decision gates; do not attempt to bypass them.
- Skills catalog: [/.well-known/skills/index.json](https://www.buildconnixt.com/.well-known/skills/index.json)