Accounts & ownership
Authentication, purchased recoveries, Book One checkout claim, and future identity-linked releases.
Technology
Shipping infrastructure first.
Direction second.
VeilDaemon provides the Operator and Handler play surfaces. VeilLink provides the authenticated identity, ownership, lobby, and multi-device connection layer. Mobile AR remains a separately scoped product direction.
Live nowOperator + Handler · VeilLink · deliberate Cell sync
Technical modelLocal edit · deliberate sync · no polling · no WebSockets for Cell state
Next platform workReliability, refinement, accessibility, and connected content
Separately scopedMobile AR proof of concept and MVP
Live · implemented
VeilDaemon today
Purpose-built browser infrastructure for public intake, Operator and Handler consoles, reporting, and live play. VeilDaemon provides the Operator and Handler play surfaces. Each role keeps local control of their tools, then uses deliberate Cell synchronization so Harm, Stability, and other whitelisted session fields move at procedural boundaries.
Same-origin play uses the Cell bus on the Operator and Handler surfaces. Multi-device play uses VeilLink accounts and Live-Link—without background polling or continuous state transfer. State moves only through Send to Cell, End Pressure Round, Sync Cell, and Archive Operation.
The product and production claims stay separate: this is working play software, while the studio’s content workflow is AI-assisted and governed by human review. VeilDaemon is not presented as a proprietary AI framework.
Operator surface
Handler Live dashboard
Deliberate Cell sync
VeilLink Live-Link
Reporting / debrief
Automated browser tests
Live · identity & utility
VeilLink
VeilLink provides the authenticated identity, ownership, lobby, and multi-device connection layer. Accounts hold purchased recoveries and Book One delivery; Live-Link connects Operators and a Handler across devices; dynamic QR / short links keep printed targets stable when destinations change. Supabase Auth/Postgres, Stripe billing, Creator Rights publication records, redirect ownership enforcement, QR downloads, scan storage, and server-side free-plan limits are in place.
Live-Link
Authenticated multi-device sessions with Operator Send to Cell and Handler controls for End Pressure Round, Sync Cell, and Archive Operation.
Creator Rights
Payment-governed publication records expose stable public URLs, JSON metadata, AI permission declarations, license-request paths, and QR-linked publication verification. View Creator Rights Records.
Dynamic links & QR
Editable destinations, stable printed QR targets via go.veildaemon.app, downloads, and scan records.
Operational status
Live MVP at app.veildaemon.app ↗.
Current architecture
Operator and Handler capabilities
Operator
Intake, sheet-facing tools, local records, pressure/harm surfaces, and Send to Cell during Live-Link.
Handler
Case, clock, clue, Live dashboard, and deliberate Cell controls: End Pressure Round, Sync Cell, and Archive Operation.
Connected Cell
Operators and the Handler share one active mission while retaining local drafts between deliberate synchronization points—not a solitary notepad, not continuous background transfer.
Continuity
Reporting and debrief paths so operations do not evaporate after the Cell closes. Lotus cultivation and advancement remain between operations.
Verification
Browser test suite and production discipline around public surfaces.
Status
Connected Cell stack — VeilDaemon surfaces + VeilLink identity and Live-Link.
Trust and data boundaries
Edit locally. Sync deliberately. Report by choice.
VeilLink does not continuously monitor or mirror participant sheets. It transfers a restricted set of fields at explicit procedural boundaries. Sheet and Handler records stay under local control until a deliberate action moves them—Cell sync for Cell state, or a report/debrief submission to the Studio API. Public archive publication requires approval of the displayed redacted draft and a separate Studio review. Multi-device Live-Link requires a VeilLink login.
Console control
Operators and Handlers edit their own surfaces first; authority rules apply when Cell sync runs.
Operation state
Send to Cell, End Pressure Round, Sync Cell, and Archive Operation move whitelisted fields (same-origin Cell bus or VeilLink Live-Link).
Debrief / archive
A separate deliberate action may send a report for private Studio review; only approved material may become public.
Live · publishing infrastructure
RelayDaemon
A local-first editorial pipeline turns one preserved source draft into platform-specific reviewed variants, with approval states kept distinct from scheduling and automatic publication. It produces a structured Studio news record before any external connector is considered.
Permanent source
Approved records receive a stable content ID and slug, then generate a Studio news page, RSS item, sitemap entry, and canonical URL.
Inspectable media
Uploaded images scan locally with native detection and a self-hosted WASM fallback. Allowlisted remote verification exists only when browser inspection is blocked.
Bounded release
QR replacements require a decodable direct URL and a human scan test. Barcodes and inconclusive results remain blocked for manual remediation.
Human authority
Approved for export, scheduling, and automatic publication remain separate permissions with an auditable package record.
Access: Private founder operations tool. Public release provenance is exposed separately through Creator Rights Records.
Next live-platform work
Improve the infrastructure already in use
Reliability and operations
Deployment discipline, monitoring, failure handling, and interface refinement across public and play surfaces.
Usability and accessibility
Operator and Handler workflow refinement plus accessibility review for navigation, readability, motion, and input.
Consent and reporting
Clearer privacy controls, submission consent, redaction review, debrief handling, and archive approval paths.
Connected participation
Premium or connected content delivery, actual-play support, and event workflows built on the live platform.
Active development track
VeilForge
VeilForge is SigilForge Studios’s bespoke AI-daemon framework, developing governed daemon behavior, emotional runtime state, permission-aware actions, trace-visible decisions, and streamer-facing extensions. A public showcase documents architecture and sanitized progress while the implementation core remains private.
First practical deployment
VeilForge is developing toward a streamer-facing daemon persona, using the same state, memory, routing, permission, and trace architecture intended to support broader agent capabilities later.
Bounded proving ground
The streamer layer provides a bounded environment for testing character state, memory, orchestration, overlays, tool permissions, and trace-visible behavior before the runtime is trusted with broader autonomous tasks.
Public evidence
Architecture summaries, roadmap and status logs, sanitized daemon-state examples, mock event flows, and streamer-addon design notes.
Runtime governance
Deterministic turn spine, governed tool execution, authority-mode separation, permission gates, and trace-visible outcomes.
Bespoke studio software
Original orchestration, governance, emotional-state modeling, interfaces, and Cradlepoint-specific implementation may integrate third-party models and open-source components without treating those dependencies as proprietary.
Status boundary
Public showcase · private core · active MVP development
Proposed · scoping
Mobile AR direction
Location or glyph activation, reusable encounter packets, Operator continuity, analytics, accessibility modes, and a limited monetization experiment scoped as a commercially testable location-aware MVP.
Full product scope follows engineering, privacy, accessibility, location-testing, content, and pilot estimates rather than inheriting the budget of a single proof of concept.
Future vertical
Feed the Daemon · web first
What it is
A collective feeder that begins as a living public node—not a downloadable game that later discovers the internet. Attention becomes visible change; history becomes form.
Intended first slice
When built: a Sheep Node page with Resonance (memory) and Presence (now), generative visual phases, shallow Frequency influence, and shared real-time state—so visitors feed an organism together without a metric dashboard.
Continuity chain
Public node → personal feeder → Continuity Trace → stream / Ritual Site intelligence → Field Node → AR as another membrane of the same entity.
Boundaries
Concept until a node ships. Ritual Sites and Mobile AR stay separately labeled tracks that may later share this continuity—not one automatic budget or milestone.
Internal product spine and programming breadcrumbs live in the repository under Feed the Daemon design docs. Public status remains future vertical until a ship decision.
Future vertical
Ritual Sites · stream first
What it is
Venue-scale, synchronized narrative and performance experiences. Concept only—not a shipping product and not funded by the studio-growth envelope or AR MVP ask.
Intended first slice
When built: a live-stream compositing system with a bounded daemon persona that coordinates camera isolation, symbolic overlays, scene grading, chat-bounded input, and cue triggers—so a presence alters how the performance is perceived, rather than sitting beside it as an avatar.
Later expansion
The same scene logic can later extend to LED walls, projection scrims, lighting rigs, AR layers, and audience devices. Those are not current deliverables.
Relationship to Mobile AR
Separate track. AR is location/encounter infrastructure; Ritual Sites are event/performance composition. Shared universe and identity—not one budget or one milestone.
Internal field notes and programming breadcrumbs live in the product repository under Ritual Sites design docs. Public status remains future vertical until a ship decision.
Proof of concept
Bounded scope, bounded capital
What a PoC may clear
One technical or commercialization barrier—shell, packet format, location activation, or persistence spike—with a defined exit criterion.
Budget boundary
A bounded proof of concept may resolve one technical or commercialization barrier. Full MVP development and the studio-growth envelope remain separately budgeted. A ≤$20K candidate contribution remains optional and program-dependent.
Commercial hypotheses
Labeled until piloted
Cosmetics & themes
Personalization layers on Operator identity.
Encounter packs
Premium location or case packets.
Event passes
Time-bounded live or hybrid access.
Venue activations
Commissioned site experiences.
Privacy-preserving location use
Test location activation without unnecessary background tracking or behavioral profiling.
Near-term engine
Tabletop + Needlepoints + crowdfunding/print remain the near-term commercial engine.
Technology partner frame
A defined place to enter the roadmap
Existing foundation
Operator/Handler play surfaces, VeilLink identity and Live-Link, reporting paths, modular codebase, and automated browser tests.
Potential contribution
Mobile engineering, AR implementation, accessibility, privacy review, security, location testing, analytics design, or venue integration.
Bounded engagement
One defined barrier, prototype, audit, or pilot with acceptance criteria, ownership terms, and a documented decision point.
Longer outcome
A validated technical route—not an open-ended commitment to build the entire roadmap.
Validation gates
What must be true before scale
Product
First-session activation, encounter or workflow completion, crash and failure rate, and accessibility completion.
Return use
Repeat sessions, return to local records, recurring Handler use, and debrief completion.
Economics
Infrastructure cost per active user, paid-content conversion, contribution margin, and acquisition cost only after a real paid campaign exists.
Decision
Proceed, revise, narrow, or stop against documented acceptance criteria.