# Overview of the iLRN Codex A guide to the Codex as the association’s single source of record, explaining its structure, navigation, governance, and future development. # Introduction & Orientation # Welcome to the iLRN Codex! The **iLRN Codex** is our shared knowledge base and delegation hub. It is not only a record of what we do but also the engine that drives how we work together. Every role, project, and initiative within iLRN should live here first. The Codex is where we align our efforts, distribute responsibilities, and hold ourselves accountable to one another. --- ## Ethos: A Living Network of Shared Responsibility iLRN thrives when the work is not carried by a few but shared across our network. The Codex reflects our ethos of **collective stewardship**: - Service to the community is embodied here, not in one person’s inbox. - Transparency and trust grow when decisions, updates, and responsibilities are visible to all. - Authority is not centralized; it is distributed, with the Codex as our common source of truth. --- ## Structure: How the Codex Organizes Our Work - **Books & Chapters**: Each major initiative (e.g., Conference, Special Tracks, Virtual Campus, Partnerships) has its own book. Within books, chapters break down tasks, resources, and role-specific information. - **Roles & Responsibilities**: Every Chair, Coordinator, or Volunteer Steward has a clearly defined lane documented here. If you’re unsure of your duties, start with your Codex page. - **Processes & Templates**: Standardized forms, checklists, and workflows live here to reduce duplication and ensure consistency. --- ## Cadence: The Rhythm of Updates The Codex works best when it’s kept alive with steady contributions. We commit to: - **Immediate Capture**: New requests, decisions, or updates are logged here as the first step. Let us aspire to create core documentation and culture such that we can (almost) live by the maxim, "*If it isn’t in the Codex, it isn’t real.* - *Of course, dynamic change, innovation, and the sheer complexity & scope of our work will make this more an ideal than a hard principle. Let's try!* - **Weekly Stewardship**: Each designated Content Steward checks updates, assigns tasks, and closes loops at least once a week. - **Monthly Sync**: Core leadership reviews Codex entries together to ensure alignment, spot gaps, and celebrate progress. --- ## Working Plan: Codex as Delegation Hub The Codex anchors three key functions that make iLRN scalable: 1. **Codex as Authority** - This is our single source of truth. - Every new member, role, or change—like adding a Program Committee member—must be logged here first. 2. **Codex as Workflow Trigger** - Codex entries launch tasks. - Linked forms (Tally), volunteer tags, or checklists turn updates into action by the right person—*without bottlenecking at leadership.* 3. **Codex as Accountability** - Publicly, we maintain our service ethos: responsive, welcoming, and professional. - Internally, the Codex shows who is responsible, what’s in progress, and when it’s complete. --- ## Our Commitment The Codex is how we **shift from “leaders doing everything” to “a network that does everything together.”** It’s where ideas become coordinated action and where we keep ourselves honest about progress. By using the Codex as our delegation hub, we not only lighten the load—we strengthen the network itself. --- # Codex Orientation Welcome to the **iLRN Codex Orientation**. This page is your guide for understanding how to navigate, contribute, and thrive within our shared knowledge base and delegation hub. The Codex is not just a library of documents—it’s the **operating system of iLRN**. It connects people, projects, and processes, ensuring that our global network works together with clarity and purpose. --- ## Why the Codex Matters - **Shared Understanding**: Everyone, from Special Track Chairs to Content Writers, works from the same playbook. - **Delegation Hub**: Tasks and updates live here first, triggering actions across our network. - **Collective Memory**: By recording our knowledge, we prevent burnout, duplication, and confusion. - **Transparency & Trust**: Members can see who is responsible for what and how decisions are being carried out. --- ## Your First Steps 1. **Read Your Role Page** - Start with the section that matches your role (Chair, Steward, Volunteer, Partner). - If you don’t see your role, contact your Coordinator or add a draft page. 2. **Log Your First Update** - If you have a responsibility (e.g., adding a Program Committee member), record it here as the first step. - Remember: *If it isn’t in the Codex, it isn’t real.* 3. **Use the Templates** - Access checklists, forms, and sample workflows provided for your area. - Templates are designed to save time and keep consistency across the network. --- ## How We Work in the Codex - **Capture → Assign → Confirm** - Every request is captured in Codex. - The task is assigned to the correct steward or chair. - Completion is confirmed in the Codex and communicated outward. - **Weekly Stewardship** - Each week, stewards check their pages, close loops, and update progress. - **Monthly Sync** - Leadership reviews Codex entries, resolves gaps, and aligns global initiatives. --- ## Expectations for Everyone - **Keep It Current**: Outdated pages weaken the network. Update as soon as changes occur. - **Be Clear & Concise**: Write so others can step in and understand your work without explanation. - **Respect the Hub**: Treat Codex entries as official records, not rough notes. - **Collaborate in Public**: Use Codex pages, not private emails, for shared tasks. --- ## Orientation Checklist ✔ Read your role page ✔ Make your first entry or update ✔ Explore templates for your area ✔ Bookmark the Codex and check it weekly --- By following these practices, you help transform iLRN from a network *carried by a few* into a network *powered by all*. The Codex is how we scale, sustain, and succeed together. # 🧩 How the Codex Supports iLRN Leaders The iLRN Codex is designed to lighten the load of leadership. It transforms administrative and coordination tasks from being a scattered burden into a shared, structured system. Whether you’re a General Chair, Program Chair, Local Host, or leading a special role, the Codex provides scaffolding to help you operate efficiently while keeping our collective memory intact. --- ## 1. Meeting Management (Agendas, Notes, Follow-up) **The Problem:** Meetings drift, agendas vanish, action items don’t get tracked. **Codex Solution:** - Pre-built **Agenda Templates** with slots for purpose, discussion points, and action items. - Pages for **Meeting Notes**, where action items can be tagged to responsible chairs. - A **Meeting Archive** book, so commitments don’t get lost. - Automated **reminder prompts**: “After this meeting, add your summary + actions here.” 👉 Meetings shift from ephemeral conversations to a **single source of record**. --- ## 2. Keeping Teams Informed **The Problem:** Updates get lost across email, Discord, and Zoom chat. **Codex Solution:** - A **Weekly Updates page** with short, bulleted “pulse notes.” - Links to key changes: deadlines, new templates, workflows. - Clear **last updated** stamps for transparency. 👉 Instead of chasing people across channels, you point them to one canonical page. --- ## 3. Templates, Forms, and Contracts **The Problem:** Re-inventing the wheel for contracts, registration forms, or procedures. **Codex Solution:** - Store all **templates in one Codex chapter**. - Version control ensures clarity on “latest” documents. - Fill-in-the-blank placeholders save time customizing. 👉 No more hunting through inboxes — everything is codified and accessible. --- ## 4. Central Repository (Docs, Discord, Website) **The Problem:** Knowledge sprawls across Drive, Discord, Slack, and inboxes. **Codex Solution:** - Codex serves as the **front door** to all systems. - Drive folders, Discord channels, registration links all indexed in one page. - Each tool tagged with a “How to Use + Owner” note. 👉 You become the person who can always answer: *“Where is that?”* --- ## 5. Registration Oversight **The Problem:** Registration and payments are siloed and confusing. **Codex Solution:** - A **Registration Oversight Dashboard** with: - Role ownership (Registration Chair, Treasurer, Admin). - Deadlines. - Data checklists (payments confirmed, author info matched). - Linked forms/templates for resolving discrepancies. 👉 Problems are visible early, not after the fact. --- ## 6. Volunteer Coordination **The Problem:** Volunteer recruitment and management is ad hoc. **Codex Solution:** - **Volunteer Roster template** (name, role, contact, shift, notes). - **Volunteer Onboarding page** with scripts, expectations, FAQs. - Volunteer recognition section to log contributions. 👉 Codex doubles as both a **recruiting tool** and a **recognition ledger**. --- ## 7. Ceremonies & Newsletters **The Problem:** Opening/closing ceremonies and newsletters often feel last-minute. **Codex Solution:** - **Ceremonies Playbook** with placeholders for: welcome remarks, acknowledgments, slide decks, running order. - **Newsletter template** with drop-in sections for announcements, deadlines, and spotlights. 👉 Instead of scrambling, you adapt and reuse structured content. --- ## 8. Awards & Achievements **The Problem:** Awards nominations, reviews, and announcements risk being fragmented — and achievements fade quickly after the event. **Codex Solution:** - **Awards Dashboard**: a single page for timelines, nomination forms, and criteria. - **Nomination Tracker**: centralized spreadsheet or database linked in Codex (who nominated, status, outcomes). - **Reviewer Toolkit**: scoring rubrics, review forms, and guidance stored in one place. - **Ceremonies Integration**: Award slides, winner bios, and scripts saved in the Ceremonies Playbook. - **Post-Conference Archive**: Past awardees logged in a Codex “Hall of Recognition,” creating continuity across years. 👉 Awards shift from a one-off highlight to a **codified legacy of excellence** within iLRN. --- ## 🚀 The Shift The Codex helps iLRN leaders shift from: - **Reactive → Proactive** (reminders and templates built in). - **Scattered → Centralized** (all indexed in one hub). - **Personal Burden → Shared Memory** (volunteers and co-chairs add to the record). - **Ephemeral Highlights → Lasting Legacy** (Awards archived, achievements celebrated year after year). --- ## 🪴 MVP Codex Setup for Leaders To “level up” quickly, leaders only need to seed these **minimum pages**: 1. **Leadership Dashboard** (landing page linking to everything below). 2. **Meeting Hub** (agenda template + notes archive). 3. **Templates Vault** (contracts, forms, checklists). 4. **Registration Oversight Page** (owners, deadlines, workflows). 5. **Volunteer Roster** (contact list + roles). 6. **Ceremonies Playbook** (outline + placeholders). 7. **Awards Dashboard** (criteria, tracker, archive of past winners). Once these exist, the Codex begins doing the remembering, nudging, and organizing — so leaders can focus on **vision, collaboration, recognition, and impact.** # Structure & Navigation The **iLRN Codex** is designed to be simple, intuitive, and scalable. Its structure mirrors how we operate as a global network: people and projects organized into clear containers, with fast paths from context to action. --- ## The Building Blocks - **Book Shelves (Collections of Books)** Top-level containers that group related **Books**. Use Shelves to reflect major domains (e.g., *Conference Operations*, *Virtual Campus & Events*, *Partnerships & Development*, *Knowledge Repository*). If you’re unsure where something belongs, start by choosing the right Shelf. - **Books (Domains of Work)** Each Book covers a focused area (e.g., *Conference 2026*, *Volunteer Management*, *Social Media & Comms*). Think of Books as operational handbooks for a domain. - **Chapters (Functional Areas)** Subsections inside a Book that cluster related processes, roles, or work streams (e.g., within *Conference 2026*: *Special Tracks*, *Keynotes*, *Registration & Fees*). - **Pages (Single Source of Truth)** The atomic unit where decisions, responsibilities, templates, and updates live. Pages are the authoritative record—*if it isn’t in the Codex, it isn’t real.* - **Templates, Forms & Checklists (Action Assets)** Embedded or linked Tally forms, Google Docs, and checklists that turn information into action (e.g., *Program Committee Update Form*, *Speaker Intake Checklist*). - **Tags & Cross-Links (Connectivity Tissue)** Tags connect related work across Shelves; cross-links stitch Pages together so people can jump from context to execution. --- ## How to Navigate 1. **Start at the Shelf** Pick the Shelf that matches your domain (e.g., *Conference Operations*). This reduces misfiling and speeds discovery. 2. **Open the Relevant Book** Within the Shelf, choose the Book for your responsibility (e.g., *Conference 2026*). 3. **Drill into the Chapter** Find the functional area (e.g., *Special Tracks*). Chapters keep role-specific materials together. 4. **Work from the Page** Use the Page as the single source of truth. Capture updates, assign stewards, and launch tasks from here. > **Fast path:** When in doubt, use search—then add a cross-link so the next person won’t have to search. --- ## Core Shelves (Quick Map) - **Overview & Governance** *Books:* Welcome to the Codex, Codex Orientation, Structure & Navigation, Governance & Roles - **Conference Operations** *Books:* Conference 2026, Registration & Fees, Publications & Proceedings, Keynotes & Featured Speakers - **Virtual Campus & Events** *Books:* Frame VR Campus, Webinars & iLEAD Workshops, Community Debates (Thirsty Scholar) - **Partnerships & Development** *Books:* Sponsors & Partners, Grants & Fundraising, Strategic Alliances - **Knowledge Repository** *Books:* iLRN Repository (Evidence & Exemplars), Methods & Measures, Platforms, Devices & Accessibility (Adjust shelf names to your exact taxonomy as the Codex matures.) --- ## Cross-Linking for Clarity - Link **role pages ↔ process pages** (e.g., *ST Chair Role* ↔ *Special Track Update Workflow*). - Link **context pages ↔ action assets** (e.g., *Program Committee Updates* ↔ *Tally: Add PC Member*). - Add **“See also”** sections at the bottom of Pages to surface adjacent workflows. --- ## Best Practices - **Capture First:** New requests land in the correct Page immediately (no private docs as the source). - **Breadcrumbs Matter:** Use the navigation trail (Shelf → Book → Chapter → Page) to keep orientation. - **Name Things Well:** Page titles should start with the noun of record (e.g., *Program Committee — Special Track 6*). - **One Page = One Promise:** Each Page should answer, “Who owns this, what happens next, and how do we know it’s done?” --- ## Design Principle The Codex prioritizes **findability → actionability → accountability**. Shelves get you to the right neighborhood, Books to the right house, Chapters to the right room, and Pages to the exact workbench—complete with the tools to act and the logbook to prove it. # Community & Governance The **Immersive Learning Research Network (iLRN)** is more than a professional association—it is a living community of practice. Our strength comes from how we share responsibility, distribute authority, and act in alignment with our mission. The Codex is the system that makes this governance visible and actionable. --- ## Our Community Ethos iLRN thrives on **collaboration, inclusivity, and service**. - **Collaboration**: Every member, from new volunteer to senior scholar, contributes to the health of the network. - **Inclusivity**: Leadership roles, committees, and working groups are open to diverse voices across disciplines, geographies, and career stages. - **Service**: Decisions are guided by what best advances immersive learning worldwide—not individual agendas. --- ## Governance Framework The Codex documents how leadership, volunteers, and members coordinate. At its core: - **Board of Directors** Provides strategic direction, oversight, and alignment with iLRN’s mission. - **Executive Leadership** The CEO and officers steward vision, partnerships, and organizational health. - **Circle of Scholars** iLRN's primary Advisory Board, ensures scientific quality and scholarly rigor across initiatives; advises on innovation, scholarship, & community development. - **Program & Track Chairs** Lead the intellectual and creative dimensions of our conferences and initiatives. - **Volunteer Stewards & Coordinators** Execute on operational needs—social media, content, community engagement, technical platforms. - **Membership at Large** Engages in projects, events, and initiatives, contributing to the network’s vitality. Each of these groups is represented in the Codex with clear roles, responsibilities, and reporting lines. --- ## Governance in Action: Codex as Hub - **Codex as Authority** Governance decisions are logged here first. If it’s not in the Codex, it isn’t official. - **Codex as Workflow Trigger** Role descriptions, committee decisions, and community nominations here launch real actions across iLRN. - **Codex as Accountability** The Codex shows who is responsible, what has been decided, and how progress is tracked. Transparency is the foundation of trust. --- ## Community Pathways into Governance - **Step Into Roles**: Members can join committees, volunteer as stewards, or apply for leadership roles—all documented in the Codex. - **Voice & Vote**: Mechanisms for feedback, proposals, and votes (when required) are captured here for clarity. - **Visibility**: Leaders and volunteers are recognized on Codex pages, ensuring that contributions are visible and valued. --- ## Cadence of Governance - **Weekly**: Stewards check and update their Codex responsibilities. - **Monthly**: Leadership syncs around Codex entries, identifying gaps and aligning direction. - **Annually**: Governance reviews ensure structures and practices remain fit for purpose as iLRN evolves. --- ## Principle iLRN’s governance is not about control—it is about **distributed stewardship**. The Codex ensures that decisions, roles, and responsibilities are transparent, enabling our global community to act as one network rather than a set of disconnected parts. # 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. # Future(s) Development The **iLRN Codex** is not static—it is a living system that will continue to evolve with our community and with the changing landscape of immersive learning. This page sets out how we think about the future(s) of the Codex, and how every member of iLRN can contribute to its ongoing development. --- ## Ethos: Designing for Many Futures At iLRN, we believe in **plural futures**. Just as immersive learning spans multiple disciplines and contexts, so too must our Codex remain flexible and adaptive. We are designing not only for today’s needs but also for the possibilities of tomorrow: - **Scalability**: Ready to support a growing global membership and expanding initiatives. - **Resilience**: Built to withstand leadership transitions and evolving technologies. - **Adaptability**: Open to new tools, workflows, and community practices as they emerge. --- ## Development Pathways 1. **Content Evolution** - Ongoing migration of documents from Google Suite into Codex for permanence. - Expanding templates, workflows, and playbooks for new roles and projects. - Refining role descriptions and governance pages as responsibilities evolve. 2. **Integration Growth** - Deeper connections between Codex and tools like CVent, Discord, Frame VR, and social media. - Automations that reduce repetitive work (e.g., syncing Tally form inputs to Codex pages). - A living **Technology Shelf** to track, document, and train on all integrations. 3. **Community Stewardship** - Rotation of Content Stewards to prevent burnout and broaden ownership. - Training new volunteers to use Codex as their first stop for guidance and accountability. - Encouraging members to propose improvements directly in Codex. 4. **Strategic Expansion** - Using Codex to support development of a public Immersive Learning knowledge base, regional geographic Chapters, Indigenous-led initiatives, and partner projects. - Aligning Codex development with iLRN’s global strategy and conference cycle. - Preparing Codex to serve as an **archive of record** for iLRN history and legacy. --- ## Your Role in Future(s) Development - **Contribute**: Add updates, templates, and clarifications to your role’s pages. - **Propose**: Suggest new Books, Chapters, or workflows that could strengthen iLRN. - **Experiment**: Pilot new ways of linking Codex to other platforms or practices. - **Reflect**: Use Codex not only as a task tool but as a mirror for how our community is growing. - **Redesign**: Help us make the Codex usable and complete—improving navigation, filling gaps, and ensuring it serves as a true working hub for our global community. --- ## Development Cadence - **Quarterly**: Review Codex structure for gaps or redundancies. - **Annually**: Update integration maps and governance workflows. - **Multi-Year**: Align Codex growth with iLRN’s strategic themes (e.g., *Knowledge Tree, Innovation Garden, Immersive Futures*). --- ## Principle The Codex embodies iLRN’s belief that **the future is co-created**. By treating this system as both a delegation hub and a futures tool, we ensure that iLRN remains not only administratively strong but also visionary in its capacity to support immersive learning worldwide. # Codex FAQ This page answers common questions about the iLRN Codex, helping members understand its purpose, how to use it, and how to contribute effectively. --- ## 🌱 For New Members **1. What is the iLRN Codex?** The Codex is iLRN’s single source of record—a knowledge base that organizes, preserves, and connects resources, initiatives, and communities across the network. **2. Who can access the Codex?** Members with an @immersivelrn.org account can access internal resources, while selected pages are publicly viewable to showcase iLRN’s work to the broader community. **3. How is the Codex organized?** The Codex uses **Shelves → Books → Chapters → Pages** to structure knowledge. Each book focuses on a major domain, and chapters/pages provide detailed information and processes. **4. What makes the Codex different from other platforms like Discord or Zoom?** Unlike chat or meeting platforms, the Codex provides structured, persistent, and searchable knowledge—turning ephemeral discussions into lasting organizational memory. --- ## 🛠 For Active Contributors **5. What kinds of content belong in the Codex?** Content that serves as a single source of truth: role descriptions, procedures, project records, standards, frameworks, event guides, and knowledge artifacts that need to be preserved. **6. Can I contribute to the Codex?** Yes. Members are encouraged to contribute by drafting pages, refining entries, and updating resources in collaboration with editors and leadership teams. **7. How do I make sure my contributions are accurate?** Contributors should reference official documents, follow existing templates, and coordinate with editors or governance stewards before publishing. **8. How does the Codex connect with other iLRN platforms?** It links with the Frame VR Campus, Invision Community forums, the Repository of Immersive Experiences, and iLRN’s publication archives to provide a unified knowledge ecosystem. --- ## 🎯 For Leaders & Organizers **9. Who maintains the Codex?** The Codex is maintained by volunteer editors, the Scientific Quality Assurance Officer, and designated community stewards who ensure content accuracy and consistency. **10. Is the Codex permanent?** Yes. The Codex is designed as a long-term archival and living knowledge base, ensuring iLRN’s history, standards, and practices remain accessible and future-ready. **11. How can I suggest improvements or changes to the Codex?** Members can directly comment on Codex books, chapters, and pages - please be specific and professional in all Codex Comments - please use feedback forms (linked where applicable), contribute directly in editing roles, or bring suggestions to the Codex governance team for review and integration. We are grateful for your thoughtful and generous contributions! **12. How does the Codex support iLRN strategy?** By capturing initiatives, events, people, and standards, the Codex ensures continuity and transparency across leadership cycles and prepares the network for future growth.