A dark, animated static front end for the FED-OS / Signal House experience — with a symbol favicon, procedural signal background, comic-tech promotional artwork, centered community pages, gated support flows, and an index-page Supabase login modal.
This repository is a static front end. It does not boot Android, package an APK, create a Manus website, or publish a live demo by itself.
A launcher or project landing page can easily become a pile of disconnected widgets: a static hero, unrelated promotional graphics, floating payment buttons, broken local links, and a community embed that fights the layout. That makes the project feel unfinished before anyone reaches the useful part.
Signal House turns that surface into one coherent entry point. It keeps the first impression dark and animated, makes the fastest links obvious, keeps local navigation on real HTML pages, and separates public links from age-, country-, membership-, and provider-gated destinations.
The project is intentionally dependency-light. There is no bundler, package install, build pipeline, or framework required for the static shell.
A live demo URL is not configured in this repository. The quickest real demo is local:
python3 -m http.server 4173Then open http://localhost:4173/index.html.
The capture below is from the actual locally served application, not a mockup:
- Open
index.htmldirectly, or serve the folder with the command above. - Try the animated landing page and its local navigation.
- Open Support to see the age-gated provider choices.
- Open Login in the header to test the Supabase sign-in/sign-up modal against the configured project.
The main example is index.html. The main support flow is support.html.
No install step is required.
# clone or download the repository
cd meta-ai-emulator-background
# run the static site locally
python3 -m http.server 4173
# open in a browser
# http://localhost:4173/index.htmlFor a quick syntax check of the JavaScript files:
node --check main.js
node --check auth.jsindex.html— animated landing page, looping header strip, login button/modal, refreshed hero artwork, community embed, and FED-OS footer.community.html— centered Discord community page.support.html— age-gated PayPal, Stripe, GitHub Sponsors, Buy Me a Coffee, thanks.dev, and NOWPayments choices.thanks.html— supplied standalone thanks.dev donation page with the package’s symbol favicon.private-communities.html— 18+ and eligible-country gate before revealing the restricted Matrix room.legal.html— local payment, privacy, and deployment notes.404.html— static-hosting fallback page.styles.cssandmain.js— shared dark visual system and procedural animation.auth.cssandauth.js— Supabase email/password sign-in, sign-up, password reset, session restore, and logout.assets/— favicon, refreshed promotional images, animated GIF, and real local demo captures.
The background is procedural rather than a stock star field: drifting particles follow a changing vector field across a linear architectural grid, with glow, scanlines, and a slow scan beam. The promotional artwork uses a consistent indigo, cyan, violet, and coral palette with one recurring signal-creature motif.
There are no orbital rings, planet paths, or orbital UI motifs. Reduced-motion preferences are respected in the CSS and canvas animation.
The support page places the supplied provider integrations behind a front-end 18+ gate. The gate is not identity verification, legal advice, or a substitute for provider-side controls. Payment details are handled by the external provider.
The login modal uses the supplied Supabase project URL and publishable browser key. The static client contains no service-role key. Before production use, configure the Supabase redirect and email settings for the final deployment origin.
The public footer includes ecosystem, membership, storefront, Whop, contact, media, support, Discord, X, Bluesky, and artwork links. The restricted Matrix URL is kept out of the public footer and is revealed only by private-communities.html after the age and country checks.
The repository contains no build configuration because it does not need one.
Use the repository root as the publishing directory. Select a branch or GitHub Actions source in the repository’s Pages settings. No build command is required.
Connect the repository, set the project root to the repository root, leave the build command empty, and use the root directory as the output directory. No framework preset is required.
A live deployment is not included in this repository, so verify the final origin in Supabase, Discord, and payment-provider dashboards before publishing.
This package is a polished static presentation and interaction shell. It does not include the Android APK, QEMU system image, extracted APK blueprints, or a native Electron launcher. Those artifacts are not present in this repository.
MIT. See LICENSE.







