aria-identity-architecture

Map corporate records to canonical JCN identities and resolve EDINET and securities code changes.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Yoshi-Dai-1/ARIA --skill aria-identity-architecture
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aria-identity-architecture
Source: https://github.com/Yoshi-Dai-1/ARIA/tree/main/.agent/skills/aria-identity-architecture
Command: npx skills add https://github.com/Yoshi-Dai-1/ARIA --skill aria-identity-architecture

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

ARIA's identifier architecture ensures a consistent corporate identity across JCN, EDINET codes, and securities codes, preventing data fragmentation when codes change due to mergers or reorganizations.

Core Features & Use Cases

  • Three-layer identity hierarchy (JCN, EDINET Code, 5-digit securities code) with stable upper levels anchoring downstream data.
  • Code-change scenarios handling: automated mapping, former codes retention, and aggregation bridge to maintain historical linkage.
  • Deterministic data lineage: preserves RAW data and enables cross-reference via the master/catalog/index layers.
  • Reference to KEY_STRUCTURE.md provides authoritative grounding for identities and mappings.

Quick Start

Map all corporate records to the canonical JCN-based identity and automatically resolve EDINET and securities code changes.

Frequently Asked Questions about aria-identity-architecture

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I maintain corporate identity when EDINET codes change after a merger?

To maintain corporate identity when EDINET codes change, apply a deterministic identity management workflow that maps new codes to a canonical JCN. This retains former codes and uses an aggregation bridge to keep historical linkage and prevent data fragmentation.

What is the best way to stabilize JCN and securities code mappings across master data?

The best way to stabilize JCN and securities code mappings is a three-layer identity hierarchy anchoring downstream data with stable upper levels. This enables deterministic data lineage by preserving RAW data and cross-referencing through master, catalog, and index layers.

How does the aggregation bridge handle former EDINET codes during corporate reorganizations?

The aggregation bridge handles former EDINET codes during reorganizations by retaining historical mappings. It ensures data consistency across evolving structures by providing historical references that link former codes back to the canonical identity.

Can I resolve securities code conflicts across different catalogs without losing historical data?

Yes, you can resolve securities code conflicts without losing historical data by preserving RAW data and applying cross-reference mappings across master and catalog layers. The architecture retains former codes to ensure deterministic lineage during code changes.

When do I need to apply a deterministic identity workflow for corporate identifiers?

You need to apply a deterministic identity workflow for corporate identifiers when mergers occur, EDINET codes change, or corporate structures evolve. It prevents cross-system confusion by providing authoritative mappings and historical references across master data.