TRUSTINT at Bronze is a living covenant + working daemon: Deterministic, legally shielded, provenance-enforced, and real-world applicable.

• Author: Kerehama Mcleod (aka MYTHIK)
• Role: Architect of Trust Intelligence Systems
• Stewardship model: Operators are stewards, not owners. Provenance is mandatory.

If referencing TRUSTINT in research or governance work, please cite as:

Mcleod, Kerehama (MYTHIK). TRUSTINT — Trust Intelligence Daemon (TID). A covenantal system for provenance, LAW sovereignty, and collapse-aware continuity. AGPLv3 + CC BY-SA 4.0. GitHub, 2025.

TRUSTINT is a Trust Intelligence Architecture — a covenantal system that models, manages, and preserves assets, roles, laws, and compliance across generations. It is not a trust itself, but a Trust Intelligence Daemon (TID) composed of three core layers:

• 🏛 Substrate (TIS) — The database and schema layer for codified trusts.
• 🕸 Lattice (TIL) — The governance validation and rule enforcement engine.
• 🔢 Matrices (TIM) — The system for exports, simulations, and board-ready reports.

• Codify trust logic into deterministic, auditable pipelines.
• Preserve provenance across every artifact, deed, and decision.
• Validate roles, assets, and obligations against explicit schemas + rule checks.
• Provide tamper-evident vaults and exportable board reports.
• Enable continuity under disruption (public-domain fallback on systemic failure).

• ✅ Integrity first — licenses + covenant before operations.
• ✅ Provenance mandatory — signed commits, checksums, append-only ledger.
• ✅ Idempotency — reproducible outputs; no silent black-boxing.
• ✅ Continuity under collapse — defaults to public-domain accessibility.
• ✅ Stewardship — multi-party, accountable governance.

TRUSTINT encodes Land · Water · Air domains:

• Land — estates, whenua, tangible infrastructures.
• Water — freshwater, coastal zones, rights of use & stewardship.
• Air — privacy corridors, airspace easements, drone boundaries (0–120m AGL).

• Clarity & Oversight — single source of truth for instruments; cross-jurisdiction visibility.
• Defensive Posture — tamper-evident vault; air/water clauses; legislative hooks.
• Operational Efficiency — deterministic validation; board exports; reproducible packaging.
• Strategic Leverage — covenantal enforcement; multi-party stewardship; collapse continuity.

• Python 3.12+
• make

Clone the repository and run the setup command. This will create the virtual environment and install all necessary dependencies.

make setup

The core configuration for your trusts, assets, roles, and laws is managed in the config/ directory. For a complete walkthrough, please refer to the full Operator's User Guide.

This project's documentation is organized to provide comprehensive guidance on its architecture, operation, and policies.

TRUSTINT/
├── config/           # YAML files for trusts, roles, assets, laws.
├── core/             # Core application logic (ingest, validate, export).
├── scripts/          # CLI entrypoints and utility scripts.
├── vault/            # Tamper-evident storage (database, ledger, keys).
└── ...

A quick reference for the core YAML configuration: trusts.yaml: {slug, name, purpose, jurisdiction} roles.yaml: {trust, role, party, powers} assets.yaml: {trust, class, descriptor, jurisdiction, metadata} laws.yaml: {jurisdictions, obligations: {trust, name, kind, schedule, ...}}

• Ledger: vault/events.jsonl — append-only HMAC chain (prev → mac).
• Checksums: dist/SHA256SUMS — SHA256 for exported artifacts.
• Vault: content-addressed paths for evidence and references.
• Keys: HMAC key resolution order:
  1. TRUSTINT_HMAC_KEY (env var: base64url or hex)
  2. TRUSTINT_HMAC_KEY_FILE (env var: path to key file)
  3. vault/.hmac_key (file: base64url, hex, or binary)

• Pre-commit: Black, Ruff (auto-fix), Mypy, YAML checks.
• Testing: Pytest with golden-file snapshots encouraged.
• Style: Python 3.12, Ruff line-length 100, strict-lean types.

• Bronze (current): Working daemon — ingest, validate, export, provenance; LAW seeded.
• Silver: Multi-trust lattice, jurisdiction overlays, TenderBotNZ integration, richer obligations.
• Gold: Simulation matrices (PvP/PvE/systemic shocks), multi-lattice governance.
• Diamond: Adaptive AI-driven compliance/resilience matrices; autonomous provenance vaulting.

• CLI → UI → UX Evolution: The current powerful CLI is the foundation for a future, intuitive graphical user experience. The goal is to provide a seamless workflow for operators of all technical levels.
• Front-End Integration: A web-based front-end is a primary goal for enhancing usability. This could be built with modern frameworks like React or Vue, or explore powerful data visualization libraries such as Palantir's witchcraft.js to create rich, interactive dashboards.
• Digital Asset Management: The architecture is designed to be extensible. Future versions will aim to incorporate the management of digital and cryptographic assets (e.g., cryptocurrencies, NFTs, digital deeds) into the same secure provenance framework.

graph TD
  A[Bronze Gate] --> B[Silver Gate]
  B --> C[Gold Gate]
  C --> D[Diamond Gate]

  A:::bronze; B:::silver; C:::gold; D:::diamond

classDef bronze fill:#cd7f32,stroke:#333,stroke-width:2px,color:#fff
classDef silver fill:#c0c0c0,stroke:#333,stroke-width:2px,color:#000
classDef gold fill:#ffd700,stroke:#333,stroke-width:2px,color:#000
classDef diamond fill:#b9f2ff,stroke:#333,stroke-width:2px,color:#000

• Tag gate: bronze-gate-v0.1
• Build tarball in dist/ with exports + SHA256SUMS
• Emit .sha256 and (optional) .sha512
• Signed tag/commit if GPG available
• Freeze bronze branch as rollback line

• Code → AGPLv3 (LICENSE) — ensures openness; prevents SaaS enclosure.
• Docs → CC BY-SA 4.0 (LICENSE-DOCS) — ontology + cultural artifacts remain libre with attribution.
• Covenant → ADDENDUM.md — provenance, collapse continuity, exportability, AI obligations.