14ft × 9ft foil at 45° for 8ft × 8ft visible image
10-12K lumen projector in concealed pit
Classic theatrical illusion with proven reliability
Best for: Museum installations with controlled lighting and dedicated space
Both technologies support the same magical particle-based Oracle experience, with LED rotor arrays offering advantages in brightness, flexibility, and modern aesthetic appeal.
LED lattice and gray “off” state visible at 6–8 ft viewing distance
Works as hidden emitter inside a PG bay; weak as the hero surface
Best for: Backup technology or bright ambient environments
C. Scrim / Gauze Projection (Hologauze, Holonet)
Big scale, cheap, fast rig — rapid deployment option
Looks foggy without hard light control — blacks go milky
Softer edges than PG — less crisp image quality
Best for: Temporary installations or budget-constrained projects
D. Boxed “Holo” Cabinets (Proto/Portl Style)
Turnkey, self-contained — minimal site preparation
Reads like fancy TV in a box up close; shallow depth illusion
Good satellite piece, not the main Oracle — secondary installations
Best for: Touring demos or quick deployment while main build happens
E. Holographic LED Rotor Arrays (Small Scale)
Novel, some operational noise, lower pixel density at scale — limited for large faces
Safety considerations, challenging for crisp 8 ft face — better for entry displays
Best for: Entry attraction displays or smaller supplementary installations
F. True Light-Field / Multi-View (Looking Glass 65, SolidLight)
Real parallax, tiny viewing cone — limited audience
Seven-figure cost and content headaches — not practical for public installation
Not viable for 8 ft public head today — technology not mature enough
Best for: Research demonstrations only
Implementation Strategy
”Enterability” Considerations
We could put visitors inside the bay with a second foil, but reflections stack and contrast dies. Better approach: keep the vitrine sealed, let viewers approach the front edge, never see the pit.
Our Recommendation
Keep the projection PG pit as the hero. Use transparent LED only as a hidden emitter if projector logistics collapse. If we want a lighter second install elsewhere, a Proto-style cabinet or transparent LED frame can echo the main piece without the pit.
The “Vitrine” Aesthetic
Regardless of display technology, we want a cube/vitrine presence without killing contrast:
Front face: Clear or AR-coated glass/acrylic
Sides/back: Matte black or smoked panels to kill reflections
Interior illusion: Dim faux room/cube behind the head—barely visible geometry to sell depth without fighting the foil
Platform build-up: 24 in OR 24–36 in recess option
Latency budget: <700 ms end-to-end
Cleaning: anti-static microfiber, no ammonia, quick-swap foil frame
Pipeline: Throw path: projector → ground screen → foil → viewer. Mic → STT/LLM/TTS → visemes/emotion JSON → render on black → projector → foil. Hue/DMX pulses bounce off walls/ceiling, never the foil.
Pepper’s Ghost (Screen Reflection) — Backup
Use a 55–98″ OLED at 45° if you can’t get throw depth. Faster install, shallower cavity. You fight: bezels, lower brightness, “not quite black” blacks. Good for PoC or tight spaces.
Holographic LED Rotor Arrays — Entry Attraction Display
Strategic placement of holographic LED rotor arrays at venue entrances creates an ethereal preview of the Oracle experience. These synchronized LED rotor systems create full-motion 3D visuals that appear to hover in space, drawing visitors toward the main installation.
Implementation: Glass-enclosed holographic LED rotor units display a looping 15-20 second sequence: “The Oracle is speaking inside” with subtle particle effects that echo the main experience. The floating text and abstract visuals create intrigue without revealing the full Oracle interaction.
Technical Integration: Pre-rendered content optimized for holographic display, with potential for real-time status updates showing when the Oracle is actively engaged with visitors.
Teaser Content Demo
Particle Typography Demo — “ORACLE ENTITY” forming from motes then shattering. Created with procedural animation and graded to match the project palette (teal/magenta/amber). This effect could run silently at entry points or with spatial chimes.
Construction Ask (put this in the architect brief)
Reserve a projection bay: 6 ft deep × width of foil, full blackout
Provide power & ventilation for 1–2 projectors (≈1.0–1.5 kW each) and a workstation
Mounting points for a tensioned 45° foil frame (or beamsplitter glass, if permanent)
Lighting zones: independent dimming near the vitrine; DMX/Hue-ready circuits
Cable paths (SDI/DP, Cat6 for NDI) and service access (front and rear)
B) Detailed Technical Playbook — Pepper’s Ghost (and Adjacent) Path
1. Define objectives and scale
Decide: home PoC, temporary pilot, or museum‑grade install. That choice sets foil type, projector class, rigging method, budget, and compliance burden.
Write the target image size in feet/meters first. Everything propagates from that (throw distance, lumen count, frame size).
2. Pick the reflective medium
Hologauze (Holotronica/Gerriets): woven, silver‑coated mesh. Nearly invisible unlit. Low gain (~0.15). Needs high‑lumen projection. Widths to ~7.4 m.
Choose on: portability, life expectancy, and image quality. Foil for prototypes, glass for permanent.
3. Geometry & footprint
Foil/glass at 45° to the floor. Projector image reflects toward viewers.
For a ~10 ft vitrine, reserve ≥6 ft of depth behind/below the foil for projector + black box.
Viewer stand‑off: ≥6–8 ft to block sightlines past the foil edge. Center the head at ~5 ft eye height.
Use tensioned frames or truss; quick‑release framing saves you during maintenance.
Line the cavity with black velvet/DarkMat to kill stray light.
4. Projector selection & placement
Target ≥50 ft‑L on screen for museum lighting; back‑solve lumens after film gain losses. 10–12 k lm laser projectors are typical for a 6 × 10 ft image in dim conditions. 5 k lm is fine for PoC in a dark room.
Prefer short‑throw (≈0.8:1) with ±50–60 % vertical, ±20–23 % horizontal lens shift. UST saves space but usually lacks shift and brightness.
Two blended projectors = brightness + redundancy (optional mid/high tiers).
Pick 24/7‑rated, filter‑free laser units to cut maintenance.
5. Media pipeline (real‑time or near‑real‑time)
Server: TouchDesigner, Notch, Resolume, or Unreal/Unity direct.
Ingress: NDI / NDI HX3 for IP video; Spout for GPU texture pass‑through on Windows.
Egress: SDI or DisplayPort to projector. Avoid long HDMI runs.
Latency budget: aim <50 ms screen delay for interactive cues. Keep audio‑video offset within ±20 ms.
Fallback: if LLM or TTS lags, cut to a “thinking swirl” loop.
6. Lighting design
Keep ambient ≤50 lux at the foil plane. Black drapes, hoods, or baffles. Block sunlight.
DMX or Hue fixtures can still pulse, but keep beams off the foil surface. Bounce from ceiling/walls behind viewers.
Narrow‑beam spots can light physical props inside the vitrine without washing the image.
7. Maintenance & risk
Film is fragile: gloves, rigid tubes, mild soap (ammonia‑free), microfiber only. Inspect for wrinkles, re‑tension as needed.
Projectors: clean filters (if any) on schedule; monitor hours to avoid surprise downtime.
Control HVAC. Drafts ripple foil, humidity fogs glass. Use desiccant packs in the cavity.
Historical Representation: Community advisory panels and transparent AI limitations
Privacy Protection: Anonymous interaction logging with data protection protocols
Cultural Sensitivity: Respectful portrayal verified by descendant communities where possible
Sustainability Framework
Technical Longevity
Modular Architecture: Independent component upgrades without system overhaul
Multi-Vendor Strategy: Reduced lock-in risk with alternative provider relationships
Open-Source Foundation: Community-maintainable components and documentation
Content Evolution
Regular Updates: Quarterly content reviews and historical accuracy improvements
Expansion Pathway: Systematic addition of new Indiana historical figures
Educational Integration: University partnerships for ongoing research and development
Financial Sustainability
Maintenance Endowment: Dedicated funding for long-term operation and upgrades
Scalable Deployment: Multi-site installation model for shared costs
Sponsor Engagement: Corporate partnerships for ongoing support and enhancements
Implementation Timeline
Phase 1 (Months 1-4): Foundation
Technology stack selection and initial development
Vonnegut persona development and testing
Prototype hardware assembly and software integration
Initial stakeholder demonstrations
Phase 2 (Months 5-8): Enhancement
Real-time optimization and performance tuning
Multi-persona architecture development
Pilot installation preparation and site selection
Community feedback integration
Phase 3 (Months 9-12): Deployment
Full kiosk development and testing
Pilot site installation and public launch
Performance monitoring and system refinement
Additional persona development
Phase 4 (Months 13-18): Full Development
3D display research and prototype development
Premium installation planning and partnerships
Complete character library finalization
Long-term sustainability planning implementation
This approach ensures each development phase builds value while maintaining clear paths for growth, providing funders with confidence in both immediate deliverables and long-term vision.
Scalability & Future Projects
Bloomington Oracle as Flagship Installation
The Bloomington Oracle will serve as a permanent installation with a strong educational focus, establishing the technical and content standards for the Oracle Entity system. This flagship installation will:
Demonstrate the full capabilities of holographic LED rotor arrays or Pepper’s Ghost technology
Serve as a living laboratory for ongoing improvements and new persona development
Provide educational programming for students, researchers, and the public
Create a replicable model for other communities interested in preserving local history
Expansion to Other Cities
The Oracle Entity system has been designed from the ground up for scalability and reproduction:
Technical Scalability
Modular software architecture allows easy deployment across different hardware configurations
Cloud-based AI models can be accessed from any installation location
Standardized hardware packages reduce setup complexity and costs
Remote monitoring and updates enable centralized maintenance support
Content Development Process
Developing a new Oracle for another city requires:
6-12 months for research, persona development, and local customization
Partnerships with local historians and cultural institutions
Community input sessions to identify key historical figures
Content verification with academic partners and descendant communities
Implementation Models
Cities interested in their own Oracle can choose from:
Full Installation: Complete system with all technical capabilities
Touring Version: Portable setup using holographic LED rotor arrays
Educational Package: Simplified version for schools and libraries
Virtual Access: Web-based interaction for remote communities
Start Early Conversations
Institutions interested in developing their own Oracle Entity should begin conversations early in the process:
Initial Consultation: 1-2 months to assess local needs and resources
Partnership Development: 2-3 months to establish institutional agreements
Funding Strategy: 3-6 months for grant writing and fundraising
Technical Planning: 2-3 months for site assessment and infrastructure planning
Network Effects
As more cities implement Oracle Entities, the network will provide:
Shared learning from operational experiences
Cost efficiencies through bulk hardware purchasing
Content collaboration for cross-regional historical connections
Technical support community for troubleshooting and improvements