How ikrgycloud/icms works
ICMS is a role-differentiated university management platform. Users sign in, receive an authority-bound session, and get an office- and role-specific workspace; they then use domain modules whose mutations are checked by the shared authority engine and recorded in an append-only audit ledger. Persona portals scope student, faculty, and parent data to the signed-in user. The README documents these flows and capabilities; some domain APIs are unsampled, so their internal call relationships are not expanded here.
Main entry points: main.py API Service · authority.py Authority Engine · api.ts API Client · App.tsx Workspace Shell
Components 23
Identity & Authority
- API Service
backend/main.py - Authority Engine
backend/authority.py - Authority Matrices
backend/matrices.py - Identity Models
backend/models.py
University Operations
- Domain APIs
backend/domain_api.py - Admissions
backend/admissions_api.py - Admissions Transitions
backend/admissions_service.py - Administration
backend/administration_api.py - Governance
backend/governance_api.py - Persona Portals
backend/portal_api.py - Integrations
backend/integrations_api.py
Role Workspaces
- Workspace Shell
frontend/src/App.tsx - API Client
frontend/src/api.ts - Admissions Workspace
frontend/src/modules/Admissions.tsx - Finance Workspace
frontend/src/modules/Finance.tsx - Student Portal UI
frontend/src/personas/StudentViews.tsx - Workflow Views
frontend/src/views/PrincipalWorkflowViews.tsx - Workspace Components
frontend/src/modules/kit.tsx - Action Dialogs
frontend/src/ui/dialogs.ts
Shared Platform
- Academic & Campus Records
backend/domain_models.py - Database
backend/database.py - Shared Runtime
backend/core.py
Other components
- Institution User
Connections 29
- Institution User → API Service: signs in
README.md - API Service → Authority Engine: authorizes actions
README.md - Authority Engine → Authority Matrices: uses policies
backend/authority.py - Authority Engine → Identity Models: evaluates authority
README.md - API Service → Domain APIs: routes requests
backend/main.py - API Service → Admissions: routes requests
backend/main.py - API Service → Administration: routes requests
backend/main.py - API Service → Governance: routes requests
backend/main.py - API Service → Persona Portals: routes requests
backend/main.py - API Service → Integrations: routes requests
backend/main.py - Admissions → Admissions Transitions: transitions applications
- Admissions Transitions → Authority Engine: checks capability
backend/admissions_service.py - Domain APIs → Authority Engine: gates mutations
README.md - Shared Runtime → Database: opens sessions
backend/core.py - Shared Runtime → Authority Engine: decodes tokens
backend/core.py - Shared Runtime → Identity Models: writes audit records
backend/core.py - Database → Academic & Campus Records: creates schema
backend/database.py - Database → Identity Models: creates schema
backend/database.py - Workspace Shell → API Client: loads workspace
frontend/src/App.tsx - Workspace Shell → Admissions Workspace: renders module
frontend/src/App.tsx - Workspace Shell → Workflow Views: renders approvals
frontend/src/App.tsx - Admissions Workspace → API Client: requests admissions
frontend/src/modules/Admissions.tsx - Finance Workspace → API Client: requests finance
frontend/src/modules/Finance.tsx - Student Portal UI → API Client: loads persona data
frontend/src/personas/StudentViews.tsx - API Client → API Service: calls API
README.md - Workspace Shell → Workspace Components: uses components
frontend/src/App.tsx - Admissions Workspace → Workspace Components: uses components
frontend/src/modules/Admissions.tsx - Finance Workspace → Workspace Components: uses components
frontend/src/modules/Finance.tsx - Admissions Workspace → Action Dialogs: uses dialogs
frontend/src/modules/Admissions.tsx