Package Manager (.eap) & Remote Registry

EasyEA Architecture Packages (.eap) are self-contained, versioned bundles delivering everything required to adopt an industry standard or custom corporate domain: taxonomies, seed elements, typed attributes, stereotypes, schemas, and pre-built executive dashboards.

The Admin Hub includes an integrated Architectural Marketplace connected to a secure remote registry.

1. Remote Package Registry & SHA-256 Verification

Inside Admin Hub ➔ Package Management, users browse catalog offerings synchronized via the registry’s index.json:

graph LR
    Reg[Remote Package Registry index.json] --> Down[Download .eap Archive]
    Down --> SHA[SHA-256 Checksum Cryptographic Verification]
    SHA --> Inst[1-Click Workspace Database Injection]

Cryptographic Verification: Prior to persisting assets into PostgreSQL, every downloaded .eap package is verified against the official SHA-256 checksum published in the manifest.
Zero-Downtime Installation: Injects reference elements and views instantaneously without requiring service restarts.
Safe Uninstall & Purge: Cleanly rolls back seed assets while safeguarding custom user relationships, or executes a total purge upon confirmation.

2. `.eap` Package Internal Anatomy

An .eap file is a structured archive holding:

my-custom-package.eap (ZIP Archive)
├── manifest.json              # Version, compatibility, author, and dependencies
├── metamodel_extensions.json   # Typed custom attributes, stereotypes, and rules
├── seed_elements.json         # Reference elements with APM metrics
├── seed_relationships.json    # Formal ArchiMate relationships between seed entities
├── seed_schemas.json          # Bundled graphical diagram layouts
└── seed_views.json            # Pre-configured executive dashboards

The `manifest.json` Specification

{
  "package_id": "corporate-fintech-core",
  "version": "1.4.0",
  "name": "Corporate FinTech Domain Model",
  "author": "Enterprise Architecture CoE",
  "min_easyea_version": "1.0.0",
  "description": "Standard banking domain model for PSD2, Open Banking, and Core Ledgers",
  "sha256": "8f4e2c1a9b3d5e7f...",
  "dependencies": [
    "bian-v12-banking"
  ]
}

3. Authoring Packages with Package Builder CLI

EasyEA supplies Python authoring tooling (tools/*_package_builder/) enabling architecture teams to compile .eap archives from spreadsheets, OpenAPI files, or Git models:

# Example: Building a corporate domain package
python3 tools/custom_package_builder/build_package.py \
  --source-dir ./domains/insurance-core \
  --output ./dist/corporate-insurance-core-v1.0.0.eap \
  --compute-checksum

The CLI inspects manifest schemas, validates unique element GUIDs, and computes the canonical SHA-256 checksum ready for publishing on internal corporate registries.