Ashlight Systems is the independent software studio of Shane Tyas. The work spans browser-native research tools, deterministic simulation, procedural world systems, multiplayer runtime engineering and the connected science-fiction project Ashlight Frontier.
Public builds are labelled by maturity. Some are usable tools; others are research branches or game-development laboratories. The common thread is explicit state, inspectable runtime behaviour and reproducible handoffs.
A browser-native research environment for multi-source search, custom repository traversal, domain topology, TOC/sitemap discovery, query reduction, evidence collection and portable session export. v31.1 adds a single transport authority and first-class persistent custom repositories.
A science-fiction runtime being built from bounded, auditable systems: deterministic world receipts, asteroid simulation, modular drone loadouts, cargo and threat systems, responsive HUDs, shared-session multiplayer and presentation reconstructed locally from authority state.
The portfolio is intentionally interconnected. Research, authoring, world generation, runtime diagnostics and game systems are developed as reusable authorities rather than isolated demos.
Procedural asteroid bodies, family/material recipes, sector distribution, sensor mapping, fracture diagnostics and bounded performance testing for Frontier space encounters.
Deterministic planetary addressing and biome authority with exportable descent manifests, connecting generated world truth to downstream Frontier encounters.
Receives world-generation manifests, inspects grid and encounter data, and formalises the handoff between upstream world authority and mission execution.
Peer-to-peer shared sessions with stable pilot identity, host-owned world mutations, action-parity reconstruction, browser diagnostics and canonical shared playfield work.
Internet radio player with audio-reactive visualisation, Signal Theatre and the .ashviz contribution format for portable visual-scene plugins.
An extensible visualisation format used by Stream for audio-reactive scenes with explicit attribution and portable plugin envelopes.
Infinite-canvas entity modelling, structured definitions, system log and runtime-oriented architecture experiments for agent-addressable system design.
Component language, registry, FSM and plugin/runtime experiments that established many of the contract and diagnostics patterns used across later Ashlight systems.
Stateful traversal-worker architecture and domain strategy reference developed alongside Focus for configurable, inspectable crawl behaviour.
Persistent task and idea organisation built around structured state, project hydration and AI-native working patterns.
An in-universe launcher and software shell for presenting Ashlight tools through a common device language and controlled application entry.
Turret-defense and encounter experiments for the planetary branch of Frontier, including UFO pressure, upgrades and ground-facing combat presentation.
Top-down vehicle command and territory-control experiments for broader planetary encounter grammar.
Power-routing puzzle system used to explore agent-addressable game state, explicit JSON contracts and reusable encounter logic.
Ashlight development favours small authorities that can be inspected, tested, replaced and handed off. The aim is not to make everything complicated; it is to keep complexity from becoming accidental.
Seeds, manifests, session receipts and exported state make important handoffs reproducible instead of implicit.
Simulation truth, network ownership and presentation are separated so each layer can evolve without redefining the others.
Diagnostics, system logs and explicit lifecycle states are treated as product infrastructure, not emergency add-ons.
Many builds ship as directly inspectable web applications, keeping experiments portable and deployment friction low.
The site now links to canonical deployment names such as focus.html. Internal build IDs remain versioned. This keeps the public route stable while development builds continue to advance.
ASHLIGHT RELAY v2.1 · ashlight_relay.php
Public HTTP/HTTPS retrieval only; private/local targets and non-standard ports are blocked.
Ashlight Systems is operated by Shane Tyas in New South Wales, Australia. The work draws on web development, IT support, multimedia, training and ongoing systems/game development. AI tools are used as coding and research collaborators, with major design decisions, architecture and product direction retained and documented by the human developer.
The public site is both a portfolio and a development record: mature tools sit beside experimental branches so the engineering lineage remains visible rather than being rewritten as a polished origin story after the fact.
This section is a practical website notice, not legal advice. Formal commercial licences, privacy terms or contributor agreements should be issued separately when a project reaches that stage.
Unless a build states otherwise, original site text, software, visual design and project material are © Shane Tyas / Ashlight Systems. All rights reserved. Third-party libraries, APIs, datasets, fonts, media and contributed material remain subject to their own licences and terms. Registering a business name is separate from trade mark rights.
Many public builds are prototypes, laboratories or development snapshots. They are provided for demonstration and evaluation and may change, fail, lose local state or contain incomplete features. Do not rely on them for safety-critical, financial, medical or production operations.
This portfolio page does not intentionally run analytics or advertising trackers. Individual Ashlight applications may contact external APIs, peer-to-peer services or user-selected websites. Those services can receive ordinary network metadata such as IP address and request headers. Their own privacy policies and terms apply. Future account features will require a dedicated privacy policy before deployment.
AI systems including OpenAI and Anthropic models have assisted with implementation, review, research and some creative experiments. Human direction, system ownership and final deployment decisions remain with Shane Tyas. Where a contribution needs specific attribution, the project aims to preserve it in source comments, metadata or accompanying documentation.
Support is optional and does not purchase a licence, ownership interest or product entitlement.