# Innovation Gardens

# Codex Template: iLRN2026 Frame Development &amp; Operations

## 0. Build Governance Rules 

> Every asset must either:
> 
> - help users understand where they are
> - help users understand where to go
> - help users understand why this space matters
> 
> If it does none of these, it should be removed.

- Navigation must be resolvable within 10 seconds of entry
- No critical function depends on a single modality (e.g., color-only signage)
- All Frames must connect back to iLRN\_Central in ≤ 2 steps

## 1. Frame Overview

**Frame Name:**  
**Associated Program Area(s):**  
(e.g., Main Stage, Knowledge Tree – NES, Student Center, Guided Virtual Adventures)

**Primary Purpose:**

> One–two sentences describing *why this Frame exists* in the conference ecosystem.

- Codex Page URL
- Last Updated
- Linked Frames

## **Secondary Functions:**

**Target Audiences:**  
(e.g., presenters, attendees, students, volunteers, leadership)

**Operational Mode:**

- ☐ Online-only (June 14–15)
- ☐ Hybrid (Online + Athens)
- ☐ Face-to-face support only (Athens)

---

## 2. Ownership &amp; Stewardship

**Frame Owner (Accountable):**  
(Name, role)

**Co-Steward(s):**  
(Name, role)

**Decision Authority:**

> Who resolves design, scheduling, or access questions.

**Escalation Path:**

> If something breaks or a decision stalls, where does it go?

---

## 3. Design &amp; Experience Intent

**Experience Goal:**

> What should participants *feel and understand* when leaving this Frame?

**Design Constraints:**  
(e.g., capacity limits, spatial layout, Frame VR affordances)

**Key Interaction Patterns:**

- Arrival / Orientation
- Primary activity
- Exit / Transition

**Athens Reuse or Extension (if applicable):**

> How this Frame translates to, supports, or complements the face-to-face event.

> **Opinion:** Explicitly documenting intent here prevents Frames from drifting into “generic meeting rooms.”

---

## 4. Wayfinding &amp; Navigation

**Entry Points:**  
(e.g., Hub link, schedule click-through, guided tour)

**Internal Wayfinding Elements:**

- Signage
- Visual landmarks
- Teleport points

**Exit Paths:**  
(e.g., return to Hub, next session Frame)

**Wayfinding Owner:**  
(Name)

---

## 5. Accessibility &amp; Inclusion Checklist

**Accessibility Lead:**  
(Name)

**Baseline Commitments:**

- ☐ Clear signage and readable contrast
- ☐ Audio clarity / redundancy
- ☐ Spatial simplicity (no unnecessary navigation complexity)
- ☐ Alternative participation pathway documented

**Known Constraints or Risks:**

> Be explicit—this supports transparency, not perfection signaling.

**Athens Considerations:**  
(e.g., language support, physical accessibility alignment)

---

## 6. Volunteer &amp; Support Roles

### Required Roles

<div class="TyagGW_tableContainer" id="bkmrk-role-name-backup-not"><div class="group TyagGW_tableWrapper flex w-fit flex-col-reverse" tabindex="-1"><table class="w-fit min-w-(--thread-content-width)" data-end="3120" data-start="2954"><thead data-end="2986" data-start="2954"><tr data-end="2986" data-start="2954"><th data-col-size="sm" data-end="2961" data-start="2954">Role</th><th data-col-size="sm" data-end="2968" data-start="2961">Name</th><th data-col-size="sm" data-end="2977" data-start="2968">Backup</th><th data-col-size="sm" data-end="2986" data-start="2977">Notes</th></tr></thead><tbody data-end="3120" data-start="3009"><tr data-end="3038" data-start="3009"><td data-col-size="sm" data-end="3031" data-start="3009">Greeter / Wayfinder</td><td data-col-size="sm" data-end="3033" data-start="3031"> </td><td data-col-size="sm" data-end="3035" data-start="3033"> </td><td data-col-size="sm" data-end="3038" data-start="3035"> </td></tr><tr data-end="3071" data-start="3039"><td data-col-size="sm" data-end="3064" data-start="3039">Presentation Moderator</td><td data-col-size="sm" data-end="3066" data-start="3064"> </td><td data-col-size="sm" data-end="3068" data-start="3066"> </td><td data-col-size="sm" data-end="3071" data-start="3068"> </td></tr><tr data-end="3094" data-start="3072"><td data-col-size="sm" data-end="3087" data-start="3072">Tech Support</td><td data-col-size="sm" data-end="3089" data-start="3087"> </td><td data-col-size="sm" data-end="3091" data-start="3089"> </td><td data-col-size="sm" data-end="3094" data-start="3091"> </td></tr><tr data-end="3120" data-start="3095"><td data-col-size="sm" data-end="3113" data-start="3095">Volunteer Float</td><td data-col-size="sm" data-end="3115" data-start="3113"> </td><td data-col-size="sm" data-end="3117" data-start="3115"> </td><td data-col-size="sm" data-end="3120" data-start="3117"> </td></tr></tbody></table>

</div></div>**Training Required:**

- ☐ Yes (link to Codex page)
- ☐ No

**Shift Coverage Notes:**  
(e.g., handoffs across time zones)

---

## 7. Presentation &amp; Session Operations

**Presentation Format(s):**

- ☐ Live
- ☐ Pre-recorded
- ☐ Mixed

**Moderator Responsibilities:**

- Speaker readiness check
- Timekeeping
- Q&amp;A facilitation
- Transition to next session

**Speaker Support Assets:**  
(e.g., slide upload location, backup links)

---

## 8. Technical Configuration

**Frame URL:**  
**Capacity:**  
**Backup Space (if any):**

**Known Failure Modes:**  
(e.g., audio lag, late arrivals, capacity overflow)

**Contingency Plan:**

> Where people go if this Frame fails.

---

## 9. 48-Hour Online Conference Integration

**Primary Active Windows:**  
(e.g., Day 1 Morning UTC, Day 2 Late UTC)

**Linked Events:**  
(Reference to Events Timeline IDs)

**Quiet / Reset Periods:**

> Explicitly note when nothing should be scheduled.

---

## 10. Post-Conference Use

**Intended Afterlife:**

- ☐ Archive
- ☐ Reusable community space
- ☐ Athens-only support
- ☐ Decommission

**Documentation Owner:**

> Who ensures lessons learned are captured.