ONE CORE.
DIFFERENT
SURFACES.
The public website is completely static; account authentication uses Supabase from the browser. The actual desktop release will carry the local environment and monitoring preview. A later mobile build can use the same Core with a platform-specific notification adapter.
TORI Desktop BUILDING
Local Core, business knowledge, testing, traceable message analysis and the desktop monitoring environment. The same engine remains portable for mobile later.
TORI Mobile LATER
Same knowledge model and Core. A mobile adapter can later observe only user-selected message sources and feed structured events into the same engine.
Publish without a server.
These files are ordinary HTML, CSS and JavaScript. They can be placed on GitHub Pages or another static host. The Knowledge Studio uses browser localStorage for its current local-first prototype.
index.html
product.html
core.html
knowledge.html
lab.html
downloads.html
faq.html
styles.css
app.js
1. Push files to a repository
2. Enable GitHub Pages
3. Serve from the repository root
4. Add release links when desktop/mobile builds exist
No custom application server is required for the public pages; authentication is provided by Supabase.