ecosystem dependencies

---

title: Ecosystem Dependencies acronyms: [] created: 2026-08-06 updated: 2026-08-06 type: architecture tags: [infrastructure] confidence: high source_files:

• docs/architecture/ecosystem-dependencies.md
• README.md
• spec/xibalba-shield-v1.md

---

Ecosystem Dependencies

This page is the wiki-facing cross-repository dependency map for INTEGRITY-LATEST, Xibalba Shield, and Integrity MVP. It reflects the canonical architecture note in docs/architecture/ecosystem-dependencies.md, the root README stack description, and the Shield v1 specification.

Table of contents

• Ownership and runtime boundaries
• Dependency direction
• Project responsibilities
• Source of truth

Ownership and runtime boundaries

INTEGRITY-LATEST is the protocol trust backend. It owns the SDK, Behavioral Commitment Chain policy and commitment pipeline, Oracle/AIS scoring, user API, protocol contracts, chain conventions, and wiki memory source of truth.

xibalba-shield is a separate endpoint-security product and evidence producer. It discovers AI agents and tools running on devices or networks, enforces local security policy, and feeds signed evidence into the Integrity Protocol trust pipeline. It is not a second reputation backend, not the Integrity Health vertical, and not an on-chain scoring layer.

integrity-mvp is the web presentation and operator-workflow layer. It consumes INTEGRITY-LATEST services directly for protocol identity, reputation, telemetry, BCC, user, and chain data, while also surfacing Shield workflows and endpoint-security evidence.

Dependency direction

The intended stack is:

integrity-mvp -> xibalba-shield -> INTEGRITY-LATEST

integrity-mvp also consumes INTEGRITY-LATEST APIs directly.

The dependency boundary is one-way: INTEGRITY-LATEST must not import, call, or require either Shield or MVP. A Shield implementation failure must not alter AIS computation, Merkle batching conventions, chain schemas, or protocol anchoring. An MVP failure must not interrupt either backend layer.

Project responsibilities

Project	Owns	Consumes
INTEGRITY-LATEST	SDK, BCC, Oracle/AIS, user API, contracts, chain conventions, canonical wiki	No Shield or MVP code
xibalba-shield	Endpoint discovery, local policy enforcement, guardrail hooks, endpoint evidence	Public INTEGRITY-LATEST SDK/BCC/telemetry/Oracle/chain interfaces
integrity-mvp	Web presentation, operator workflows, generated read-only wiki browser	INTEGRITY-LATEST APIs/contracts directly; Shield evidence and security workflows

Source of truth

The normative Shield product boundary is spec/xibalba-shield-v1.md. Current Shield implementation status lives in the separate xibalba-shield repository README. Cross-package wire shapes inside INTEGRITY-LATEST remain governed by docs/INTERFACE_CONTRACT.md.

The canonical wiki content source remains WIKI_SCHEMA.md: INTEGRITY-LATEST/docs/wiki is authored directly; Integrity MVP's /wiki route and the GitHub Wiki are generated, read-only projections.