ENTITY-FINANCE

ENTITY v3.4.0 executable Finance implementation package.

Current core compatibility: ENTITY v3.4.1 — Protocol Origin Lineage & Sovereign User Bootstrap. The sealed domain-package payload remains v3.4.0 and was requalified unchanged against v3.4.1.

This repository configures the one ENTITY Global Passport for finance workflows. It does not define a separate passport protocol and does not modify ENTITY core semantics.

ENTITY · v3.4.1 core release · Global Passport documentation · Domain packages

What this package is for

Use ENTITY-FINANCE as the starting point when you need a governed passport and provenance layer around financial-domain assets, messages, rights, evidence or settlement-related state while keeping authority, custody, market observations and economic consequences explicitly separated.

The v3.4 package includes mappings for ISO 20022, FIX and LEI. Those mappings describe correspondence; ENTITY does not redefine the external standards or turn mapped data into legal entitlement, accounting fair value or settlement finality by itself.

Typical evaluation paths include:

• binding provenance and scoped authority to financial-domain records or instruments;
• carrying rights and evidence through downstream processing or derived outputs;
• recording provider/custody changes without treating infrastructure possession as sovereign authority;
• composing jurisdiction, privacy, trust and technical profiles inside one Global Passport.

Deploy the package

Required deployment facts:

• organization
• jurisdiction
• authority_source
• settlement_policy

deployment.example.json is intentionally non-production until every CONFIGURE-ME value is replaced with organization-specific facts.

Select package → configure organization facts → connect systems/data → ingest → verify passport → run conformance → deploy

Verify locally

python tools/verify_package.py

The verifier checks the repository inventory and the package/source-release binding.

Release binding

• Core source: blackmore-technology-group/ENTITY PR #41
• Source head: 2d7529fbadb4dd04840d62b751294bf9a7f70ed5
• Release snapshot: 3ff0e51ca2daabf50bc517e9c6e3438e8c150f1560cca6c99621621e3c855a90
• Package SHA-256: 768dd87fd5a29c7e2679fc2b0d4b172b8613712b148336d8fba91a3b92d0d466

Go deeper

• ENTITY v3.4.1 core
• Developer portal
• Engineering evidence
• Open contributor tasks

Truth and compliance boundary

External standards remain externally authoritative and are mapped, not redefined. Package verification does not establish regulatory compliance, objective external truth, legal title, settlement finality or accounting fair value. Provider custody does not create ENTITY authority.

Deployment-specific legal, regulatory, accounting, security and market-infrastructure determinations remain the responsibility of the deploying organization.