# Integration & Systems

The **iLRN Codex** is the hub that connects our people, projects, and platforms. It is not a standalone archive—it is the **central nervous system** of iLRN’s technology ecosystem. This page explains how the Codex integrates with other systems, ensuring that updates are captured once, delegated effectively, and consistently communicated across the network.

---

## Why Integration Matters

- **Efficiency**: Updates are logged once in Codex, then flow into other systems.
- **Clarity**: The Codex is the authoritative source, while other platforms deliver and engage.
- **Scalability**: As iLRN grows, integrations reduce manual duplication and lighten the load for leadership and volunteers.

---

## Core Systems Connected to the Codex

- **BookStack (Codex Platform)**
    
    
    - The **single source of truth** for roles, workflows, and records.
    - Linked directly to all other platforms.
- **Google Suite (iLRN Email, Docs, Drive, Calendar)**
    
    
    - iLRN email accounts anchor identity and access.
    - Google Docs/Sheets/Slides remain essential for **real-time collaboration**.
    - Google Drive houses shared working files.
    - **Migration Note**: We are transitioning core documentation from Google Docs into Codex for permanence, while continuing to link to Google Docs for drafts, collaborative editing, and living spreadsheets.
- **Tally.so (Forms & Intake)**
    
    
    - Used for nominations, submissions, and updates.
    - Linked from Codex pages so every request begins with proper capture.
- **iLRN Discord Servers (Main & Current Conference)**
    
    
    - Main server: our year-round **community hub**, member discussions, and volunteer coordination.
    - Conference server: event-specific space for **synchronous planning, attendee support, and community engagement**.
    - Codex anchors official procedures while Discord channels enable real-time dialogue.
- **Frame VR (Virtual Campus)**
    
    
    - Hosts events, exhibits, and community activities.
    - Codex pages link to Frames, showing where activities take place and who stewards them.
- **Invision Community (Forums & Discussions)**
    
    
    - Long-form conversations, debates, and archives of community knowledge.
    - Codex provides the “map”; Invision provides the “room.”
- **Social Media (LinkedIn, X, Facebook, Instagram)**
    
    
    - External voice of iLRN.
    - Campaign plans, hashtags, and calendars are housed in Codex; social channels are the broadcast layer.
- **CVent (Event Management)**
    
    
    - Registration, scheduling, and program curation.
    - Codex ensures alignment across Special Tracks, sessions, and speakers.
- **Knowledge Repositories (e.g., Zotero, Evidence Libraries)**
    
    
    - Codex catalogs what exists, who manages it, and how to access it.
    - External repositories hold the content; Codex ensures visibility and connection.
- **Technology BookStack Shelf**
    
    
    - The dedicated Shelf for documenting integrations, technical instructions, and platform-specific workflows.
    - Serves as the **reference library** for maintaining iLRN’s digital stack.

---

## How the Systems Work Together

1. **Capture in Codex**
    
    
    - Requests and updates are logged here first.
2. **Trigger Workflow**
    
    
    - Linked forms (Tally), Discord channel tags, or task assignments push actions outward.
3. **Collaborate in Google Suite**
    
    
    - Drafts, spreadsheets, and live notes are developed in Google Docs/Sheets.
    - Once finalized, documents are migrated or summarized into Codex for permanence.
4. **Synchronize with Platforms**
    
    
    - Stewards update CVent, Frame VR, social media, or Invision based on Codex records.
5. **Confirm Back in Codex**
    
    
    - Completion is recorded here, ensuring accountability and consistency.

---

## Integration Principles

- **Codex as Authority**: All systems point back to Codex for definitive information.
- **Codex as Workflow Trigger**: Entries initiate actions in other systems, not ad hoc leadership emails.
- **Codex as Accountability**: Responsibilities, ownership, and confirmation live here.
- **Codex + Google Suite Partnership**: Codex holds *records*, Google Suite enables *collaboration*.

---

## Systems Cadence

- **Weekly**: Stewards check Codex for new tasks tied to their platform.
- **Monthly**: Technology leads review integration points and links for accuracy.
- **Annually**: Systems are reviewed for fitness, with updates captured in the **Technology Shelf** for clarity and training.

---

## Design Principle

The Codex is our **map and signal system**: it captures inputs (requests), triggers workflows (tasks), and confirms outputs (results). Google Suite, Discord, Frame VR, CVent, Invision, and social media are the hands and voices of the network; the Codex keeps them coordinated and accountable.