# Part II. About the iLRN Futures Guild Codex

## 2.1 The Fundamental Two-Section Page Structure

Every page in the Immersive Futures Guild Codex — with only rare exception — is organized into two sections. This is the defining architectural principle of this Guild’s Codex, distinguishing it from general-purpose Codex or the other two Guilds’ deployments and from static knowledge repositories.

<div align="left" dir="ltr" id="bkmrk-section-name-content"><table><colgroup><col width="80"></col><col width="160"></col><col width="200"></col><col width="184"></col></colgroup><thead><tr><th scope="col">Section

</th><th scope="col">Name

</th><th scope="col">Content

</th><th scope="col">Status

</th></tr></thead><tbody><tr><td>Part I

</td><td>Foresight Snapshot

</td><td>Time-stamped Circle of Scholars workshop synthesis; core claims; dimensions; tensions; Ways of Knowing links; architecture connections

</td><td>FIXED — Time-stamped; revised only by formal versioning

</td></tr><tr><td>Part II

</td><td>Community Evidence &amp; Dialogue Track

</td><td>Community contributions organized by category; tension response spaces; evidence registers; Tally.so form integration; synthesis notes

</td><td>LIVING — H2 cycle; rolling contributions; synthesis reviews at 3 points

</td></tr></tbody></table>

</div>## 2.2 Four-Layer Content Architecture

Within the two-section structure, Guild Codex pages are organized into four possible content layers. All four layers follow the same Part I / Part II architecture; they differ in the type of foresight content they carry. Layer 1 – Atomic Foresight Objects shall all be applied at a base level evenly across all category pages; Layer 2 – Narrative Assemblages (Scenarios) are dependent on author assignments within the Guild; Layer 3 is moderated by the Scientific Quality Assurance &amp; Publications team guidelines and volunteers able to administer the respective volume of community response to respected Immersive Futures content areas; and Layer 4 is interconnected with the operational and community stewardship of iLRN, thus is dependent on and controlled by the Executive and iLRN Leadership Teams.

<div align="left" dir="ltr" id="bkmrk-layer-1-%E2%80%94-atomic-for"><table><colgroup><col width="624"></col></colgroup><tbody><tr><td>Layer 1 — Atomic Foresight Objects (Cards)

</td></tr><tr><td>Societal Challenge Cards (SC) — broad social conditions shaping immersive learning futures

</td></tr><tr><td>Future Technology Possibility Cards (FT) — technologies plausible within a 10–20 year horizon

</td></tr><tr><td>Historical Technology Shift Cards (HT) — transitions that have occurred and shaped the present

</td></tr><tr><td>Educational Transformation Cards (ET) — structural shifts in educational organization and delivery

</td></tr></tbody></table>

</div><div align="left" dir="ltr" id="bkmrk-layer-2-%E2%80%94-narrative-"><table><colgroup><col width="624"></col></colgroup><tbody><tr><td>Layer 2 — Narrative Assemblages (Scenarios)

</td></tr><tr><td>Scenario Pages assemble multiple cards into coherent future world-pictures.

</td></tr><tr><td>They are analytical tools for structured futures thinking — not predictions.

</td></tr><tr><td>Scenarios carry their own Part I (Circle of Scholars narrative synthesis) and Part II (community scenario testing).

</td></tr></tbody></table>

</div><div align="left" dir="ltr" id="bkmrk-layer-3-%E2%80%94-research-c"><table><colgroup><col width="624"></col></colgroup><tbody><tr><td>Layer 3 — Research Coordination Infrastructure (Strands)

</td></tr><tr><td>Research Strand Pages are long-term coordination nodes organizing open questions, methodologies, and ethical considerations.

</td></tr><tr><td>They connect Guild foresight work to the iLRN Knowledge Tree evidence base.

</td></tr><tr><td>Strand Part I documents Circle of Scholars research agenda synthesis; Strand Part II collects field-wide community input.

</td></tr></tbody></table>

</div><div align="left" dir="ltr" id="bkmrk-layer-4-%E2%80%94-operationa"><table><colgroup><col width="624"></col></colgroup><tbody><tr><td>Layer 4 — Operational &amp; Community Knowledge

</td></tr><tr><td>Papers, Projects, Exemplars, Design Patterns, Communities of Practice, Toolkits, Methods, Events

</td></tr><tr><td>These pages document specific outputs and communities connected to the Guild's foresight work.

</td></tr><tr><td>Layer 4 pages follow a simplified version of the two-section structure.

</td></tr></tbody></table>

</div>## 2.3 The Annual Foresight Calendar

The Guild Codex operates on a structured annual calendar that governs when cards are produced, when evidence tracks open, and when syntheses are reviewed. All Guild Codex activities are anchored to this calendar.

<div align="left" dir="ltr" id="bkmrk-period-phase-activit"><table><colgroup><col width="107"></col><col width="147"></col><col width="371"></col></colgroup><thead><tr><th scope="col">Period

</th><th scope="col">Phase

</th><th scope="col">Activities

</th></tr></thead><tbody><tr><td>January

</td><td>Circle of Scholars Workshop

</td><td>Annual workshop(s): produce new cards; version existing Part I content based on prior year evidence track; assign new Tally.so forms

</td></tr><tr><td>Feb–May

</td><td>Part I Completion &amp; Review

</td><td>Workshop outputs refined and published; cross-links established; Tally.so forms built and linked; Part II scaffolding prepared

</td></tr><tr><td>June 30

</td><td>Part I Deadline

</td><td>All Part I content for the cycle finalized and published; Tally.so forms activated; Part II sections opened to public view

</td></tr><tr><td>July 1

</td><td>Part II Opens

</td><td>Community evidence tracks open; contribution forms activated; editorial review of submissions begins

</td></tr><tr><td>September

</td><td>Midpoint Synthesis

</td><td>First synthesis of received contributions; synthesis notes added to Part II; iLRN Conference integration if applicable

</td></tr><tr><td>November

</td><td>Late Synthesis

</td><td>Second synthesis pass; emerging tensions identified; versioning recommendations drafted if warranted

</td></tr><tr><td>December 31

</td><td>Part II Closes

</td><td>Contribution forms deactivated (forms archived); final synthesis notes completed; handoff memo prepared for January Circle

</td></tr><tr><td>January (next)

</td><td>Annual Handoff

</td><td>Circle of Scholars reviews prior year evidence; decides on Part I versioning; opens new cycle; new Tally.so forms assigned

</td></tr></tbody></table>

</div>## 2.4 The Tally.so Form Architecture

Every Guild Codex page is paired with a unique Tally.so form that serves as the primary submission mechanism for Part II contributions. These forms are structural infrastructure — they are not optional feedback channels, and they persist for the full H2 cycle before being archived and replaced for the next cycle.

### 2.4.1 Form URL Convention

All Guild Codex contribution forms follow a standardized URL pattern:

<div align="left" dir="ltr" id="bkmrk-tally.so-url-convent"><table><colgroup><col width="624"></col></colgroup><tbody><tr><td>Tally.so URL Convention

</td></tr><tr><td>Base: https://tally.so/r/ilrn-if-\[card-code\]-\[year\]

</td></tr><tr><td>  
</td></tr><tr><td>Card code components:

</td></tr><tr><td> \[type-prefix\]-\[shortname\]-\[year\]

</td></tr><tr><td> Type prefixes: sc (Societal Challenge) | ft (Future Technology) | ht (Historical Shift) | et (Educational Transformation)

</td></tr><tr><td> Scenario prefix: scn | Research Strand prefix: str

</td></tr><tr><td>  
</td></tr><tr><td>Examples:

</td></tr><tr><td> SC: Care, Culture &amp; Community → https://tally.so/r/ilrn-if-sc-ccc-2026

</td></tr><tr><td> FT: Agentic AI → https://tally.so/r/ilrn-if-ft-agentai-2026

</td></tr><tr><td> SCENARIO: Extractive Surveillance → https://tally.so/r/ilrn-if-scn-extractive-2026

</td></tr><tr><td> STRAND: Embodied Cognition &amp; Learning → https://tally.so/r/ilrn-if-str-embodied-2026

</td></tr></tbody></table>

</div>### 2.4.2 Standard Form Fields

All Guild Codex Tally.so forms share a standard field structure. Card-specific forms may add supplementary fields but must not remove standard fields.

<div align="left" dir="ltr" id="bkmrk-field-type-required%3F"><table><colgroup><col width="187"></col><col width="107"></col><col width="91"></col><col width="240"></col></colgroup><thead><tr><th scope="col">Field

</th><th scope="col">Type

</th><th scope="col">Required?

</th><th scope="col">Notes

</th></tr></thead><tbody><tr><td>Contributor Name

</td><td>Short text

</td><td>Required

</td><td>Full name; displayed in Part II register unless anonymity requested

</td></tr><tr><td>Affiliation / Institution

</td><td>Short text

</td><td>Required

</td><td>Used for provenance; displayed in register

</td></tr><tr><td>Country / Region

</td><td>Dropdown

</td><td>Required

</td><td>For geographic diversity tracking

</td></tr><tr><td>Contribution Category

</td><td>Single select

</td><td>Required

</td><td>Case Example | Methodological Challenge | Cultural/Community Perspective | Proposed Evidence Criterion | General Response

</td></tr><tr><td>Tension Addressed (if applicable)

</td><td>Single select

</td><td>Optional

</td><td>From the named tensions in Part I; 'None / General' option included

</td></tr><tr><td>Ways of Knowing Mode

</td><td>Single select

</td><td>Required

</td><td>Tree (evidence) | Garden (practice) | Lantern (futures)

</td></tr><tr><td>Contribution Text

</td><td>Long text

</td><td>Required

</td><td>Main body of the submission; 50–600 words recommended

</td></tr><tr><td>Supporting Reference(s)

</td><td>Long text

</td><td>Optional

</td><td>APA citation with DOI if available

</td></tr><tr><td>Permission to Publish

</td><td>Yes/No

</td><td>Required

</td><td>Consent to include in Part II register; 'Yes anonymously' option included

</td></tr><tr><td>Anonymity Requested?

</td><td>Yes/No

</td><td>Required

</td><td>If yes, affiliation is displayed but name is replaced with \[Contributor\]

</td></tr></tbody></table>

</div>### 2.4.3 Form Management Protocol

- Forms are built and activated by the Codex Administrator no later than June 15 of each cycle year.
- Form URLs are embedded in both the card's Part II section and the card's metadata table.
- Submissions are reviewed weekly by the assigned Category Steward; eligible submissions appear in Part II within 10 business days.
- At each synthesis review point (September, November), the Tally.so response export is archived to the Guild Codex operations folder.
- At December 31, forms are deactivated and marked as archived. The URL is retained in the card's revision log for reference.
- New cycle forms receive a new year suffix (e.g., -2027) and are linked from the card's updated Part II section.