JIM Content — CLAUDE.md

What is JIM?

JIM (Junctional Identity Manager) is Tetron’s self-hosted enterprise Identity Lifecycle Management (ILM) platform. It synchronises identity data between connected systems through a central “metaverse” hub. Built with .NET 9.0, Blazor Server (MudBlazor), and PostgreSQL. Deployable via Docker, including air-gapped environments.

Authoritative Context Document

For up-to-date technical details, architecture, status, and terminology, reference:

GitHub: https://github.com/TetronIO/JIM/blob/main/docs/JIM_AI_ASSISTANT_CONTEXT.md
Raw (for fetching): https://raw.githubusercontent.com/TetronIO/JIM/refs/heads/main/docs/JIM_AI_ASSISTANT_CONTEXT.md

Fetch this document (via WebFetch using the raw URL) before making substantive changes to JIM content on this site.

Key Facts for Content Accuracy

Status: Active development, approaching v0.9 stabilisation
License: Source-available (free non-production, commercial for production)
Stack: .NET 9.0, EF Core, PostgreSQL 18, Blazor Server, MudBlazor
Auth: OpenID Connect (OIDC) with PKCE — no local accounts
Deployment: Docker containers, air-gapped capable, one-command installer
Language: British English (en-GB) throughout — synchronisation, authorisation, behaviour, etc.

Core Scenarios

Joiner/Mover/Leaver (JML) automation
Attribute writeback to HR systems
Centralised entitlement management
Domain consolidation and migration
Identity correlation across disparate systems

Available Connectors

LDAP / Active Directory (full CRUD, import & export)
File (CSV/Text, import & export)
Planned: SCIM 2.0, SQL databases, PowerShell, REST/Web Services

Key Capabilities

14 API controllers, 120+ endpoints (Swagger at /api/swagger)
78 PowerShell cmdlets for automation
Scheduler with cron/interval triggers
Credential encryption (AES-256-GCM at rest)
Change history/audit with timeline UI
Sync outcome graph with causal tracing

Content in This Directory

_index.md — Main JIM product page on tetron.io
Images referenced via shortcode (source images in assets/images/)

Writing Guidelines

Keep marketing tone — this is the public-facing product page, not developer docs
Use British English spelling consistently
Verify any technical claims against the AI context document linked above
Screenshots use the resized-figure shortcode (images must be in assets/images/)