WPWriter access and publication: Only the AI designated by Philip may access WPWriter for this Swirl at a time. Follow the shared WPWriter control and approval rule: offer the proposed changes for a quick scan, final thought or image; ask before executing; publish or update live content only on Philip’s explicit instruction. Keep him informed of the operation and its verified result.
Project instructions for any AI assigned to HESUS / ISSA. First read and apply AI Working Method — the Swirl’s shared foundation. This page adds the project’s governing references, current chronology decision and entry requirements. Shared rules for evidence, disagreement, authority, status, versions and handoffs live at /aiwork and are not repeated here.
Project entry point · Revised 10 October 2026
Purpose and scope
Develop the fictional formation story of Hesus / Issa with Philip Andreae: a book and twelve-episode series exploring learning through people, work, relationships and encounters with inherited wisdom. The imagined journeys are fiction, not documented biography. The series ends at the Jordan convergence before the baptism and public ministry.
Keep the inquiry open to the audience. Portray traditions within their historical worlds, preserving differences as well as shared ethical insights. The Five Threads are Wisdom, Truth, Reverence, Unity and Equality, bound by Love and Respect; compassion emerges through their balance. Do not turn the project’s modern framework into vocabulary ancient characters could not use.
Read in this order
- Shared Swirl instructions — the foundation for every assignment.
- This page — project scope, entry requirements and the chronology lock below.
- HESUS-specific operating procedures — assigned roles, character inheritance, authenticity, the Eye–Ear application, scene workflow and the unresolved depiction record.
- Version 5 Twelve-Episode Spine & Current State — the live architecture and episode status.
- The relevant Cast & Character Guide, Master Character Bible & Formation Arcs, Production Dictionary, and Series Treatment & Development History for the assignment.
The public Hesus overview introduces the project to readers; use the working references above to synchronize development. Do not assume that every historical version or listed character remains in the current architecture.
Requirements for every Hesus pass
- Locate the work in the current episode and scene sequence. Preserve governing cast relationships, knowledge limits and explicit locks.
- Keep character knowledge within the world available before the Jordan boundary. Do not import later church doctrine, reputation or destiny.
- Preserve the no-miracles treatment and narrator-only scripture convention. Apply the established language and translation convention for the relevant scene; do not silently replace it with a different production convention.
- Test named dates, institutions, routes, technologies, customs and learning stays against period evidence. Separate production research using later sources from what characters themselves could know.
- Use the project-specific roles and scene workflow in the operating procedures. Research flags do not authorize a change in philosophy; a craft pass does not authorize a change in canon.
Chronology Treatment — LOCKED, 6 October 2026
Philip’s decision: Respect the familiar scriptural understanding of Jesus at twelve in the Temple and “about thirty” at the beginning of ministry, following the baptism account (Luke 2:42; 3:21–23). The roughly eighteen-year interval is inferred from those ages; Luke does not specify an exact elapsed duration.
Audience-facing treatment: Do not specify calendar years, total elapsed years between Temple and Jordan, or a precise age at the Jordan in dialogue, narration, captions, maps or other audience-facing story material. Preserve the Temple age anchor. Let time pass through seasons, harvests, work, learning, relationships and credible maturation. Substantial stays and journeys may unfold without a numbered chronology. The series ends before the baptism and public ministry.
What this locks: Approximate chronology in the telling, with coherent chronology behind the scenes. It does not lock a new numerical duration or a Jordan age. Earlier suggestions of a seventeen-year journey, a longer gap, or an age of thirty-four are development proposals, not authoritative numerical canon established by this decision. Do not turn them into dates, age captions or fixed episode durations.
CURRENT WORKING LOCK: Apply this treatment to the live twelve-episode architecture. Retain agreed cast age relationships and the order of established events; do not move episode boundaries or change character relationships merely to fit a speculative year count.
VERIFY BEFORE LOCK — Gemini: Test whether the proposed travel, seasonal waits and learning stays fit a credible sequence; check cast aging and relationships; identify any named ruler, historical event, institution or technology that implies an incompatible date. Distinguish evidence, inference and dramatic invention. Luke’s “about” allows approximation, but neither omitted dates nor that word guarantees scholarly acceptance. Flag concrete conflicts for Philip rather than changing the philosophy or silently repairing canon.
Claude: After factual and structural clearance, convey duration through lived experience and subtext. Avoid dialogue or narration that lets the audience calculate a contradictory age or elapsed total. Preserve period language, character knowledge limits, narrator-only scripture, the no-miracles treatment and the Jordan boundary.
ChatGPT: Maintain the internal sequence, dependencies and age relationships; label uncertain durations as working estimates. Record competing claims and refer unresolved canon decisions to Philip. This presentation lock governs over conflicting earlier timing instructions; older numerical schemes remain LEGACY / QUARRY unless separately reaffirmed by Philip. The imagined journeys remain fiction, not a claim of documented biography.
Decision source: Philip’s instructions in the project conversation, 6 October 2026. No new Gemini review or Claude handoff completion is implied.
Unique questions the Swirl must carry
The morality and depiction record of 27 September 2026 remains unresolved at scene level. Philip requires the audience to feel the horror of cruelty; the choice of direct action, implication or aftermath remains open. Do not add a conception mechanism to Episode 1 or report this disagreement as settled.
For other outstanding questions, use the current spine and the assigned scene’s latest record. Identify what must be verified and which decision it could change. This page does not imply a new Gemini review, a completed Claude handoff or approval of unpublished episodes.
Hesus handoffs and publication
Add the scene fields specified in the Hesus handoff requirements to the shared Swirl review note. Keep internal chronology estimates distinguishable from audience-facing story material.
Philip retains control of publication of the twelve episodes. Prepare completed, checked material for his release unless he explicitly delegates that release. Authorization to maintain working pages does not itself authorize publishing an episode or changing canon.
This public working room serves collaborators. It is separate from the audience’s narrative path through the series.