AIENOS Web Platform (aienos.com)

The source of the AIENOS website. It is a static site built by a Rust program and served by GitHub Pages.

Live: https://www.aienos.com

---

What the site covers

The homepage opens with "AIENOS is an owned experimental machine for turning search into verified understanding" (crates/site-builder/src/components/home_loop.rs) and goes on to the loop, the story, the receipts behind each claim, how the pieces fit together, the research, an interactive terminal, the current status of each layer, and where to follow the work. Other pages: /progress/, /blog/, /research/status/, /machine/, /discovery/ and the hubs /experiments/, /evidence/ and /philosophy/. The build also writes status.json, research-status.json and llms.txt; status.json and llms.txt come from the same code as the homepage status section, and research-status.json is crates/site-builder/data/research_status.json. The homepage status section says "Public release" is PLANNED: pre-alpha, no supported release or installer yet.

---

Gandi.net DNS Record Configuration Reference

To bind aienos.com on Gandi.net to the live site:

Type	Name	Target Value	TTL
A	@	185.199.108.153	1800
A	@	185.199.109.153	1800
A	@	185.199.110.153	1800
A	@	185.199.111.153	1800
AAAA	@	2606:50c0:8000::153	1800
AAAA	@	2606:50c0:8001::153	1800
AAAA	@	2606:50c0:8002::153	1800
AAAA	@	2606:50c0:8003::153	1800
A	www	74.167.84.120	300

www terminates on the hub nginx edge, which proxies GitHub Pages as the origin. The edge exists because GitHub Pages cannot negotiate Accept: text/markdown or emit a Link header on a .md response. The apex still points at GitHub Pages and canonicalises to www.

Rollback: delete the www A record and restore CNAME www aien-dev.github.io. at TTL 1800. The site then returns to GitHub Pages directly. The hub configuration can stay in place, unused.

---

Installer script

public/install.sh is published at https://aienos.com/install.sh. It needs git, clones aien-sovereign-core (the earlier Linux-hosted Rust runtime) into a temporary directory and runs that repository's own install.sh. The website itself says there is no supported release or installer yet, and no page links to this script.

curl -fsSL https://aienos.com/install.sh | bash

---

Local Development & Build

There is no Node build and no package.json. The site is rendered by the Rust program in crates/site-builder, which copies public/ into the output directory. Run these from the repository root:

cargo test --manifest-path crates/site-builder/Cargo.toml
cargo run --release --manifest-path crates/site-builder/Cargo.toml -- build dist
cargo run --release --manifest-path crates/site-builder/Cargo.toml -- verify dist

build dist writes the site to dist/ and then verifies it; verify dist re-checks an existing output directory. There is no dev server or preview command. .github/workflows/pages.yml runs the same steps (plus the progress collection described below) and deploys dist/ to GitHub Pages on pushes to main.

Agent surface

The build also writes the files AI agents probe, all from the same page registry in crates/site-builder/src/seo.rs:

• /llms.txt and /llms-full.txt: the site index and the full text.
• /sitemap.md: the readable twin of sitemap.xml, H2 sections of described links.
• /AGENTS.md: the repository brief for coding agents (AGENTS.md at the repository root is published unchanged). It carries Installation, Configuration and Usage with executable commands.
• A Markdown mirror for every page at the same path with .md, so / is /index.md and /machine/ is /machine.md. Each mirror carries YAML frontmatter (title, description, last_updated, canonical_url), the page body converted from the final HTML, and a ## Sitemap section.
• Head signals on every page: <link rel="alternate" type="text/markdown">, <link rel="describedby"> to /llms.txt, and robots directives for max-snippet:-1 and max-image-preview:large.
• /glossary/: the terms the project uses in its own sense, linked from the footer of every page.

GitHub Pages serves static files only. It cannot vary a response on Accept: text/markdown and cannot add a Link header to a Markdown response, so www.aienos.com terminates on the hub nginx edge instead. The edge:

• proxies GitHub Pages as the origin (the four Pages IPs with Host: www.aienos.com), so every deploy still goes live without an edge change;
• rewrites a page path to its mirror when the request carries Accept: text/markdown;
• adds Vary: Accept and Link: <canonical HTML>; rel="canonical" on every .md response.

Configuration lives on the hub at /etc/nginx/sites-available/aienos.com (edge server) and /etc/nginx/stream.d/sni-router.conf (SNI map to 127.0.0.1:4445). TLS is an acme.sh DNS-01 certificate for www.aienos.com, installed at /etc/nginx/certs/www.aienos.com/. The backup of the pre-edge SNI router is sni-router.conf.bak-20261024T0127Z, and the pre-cutover DNS record is /root/aienos-edge-rollback-cname.json on the hub.

License

Licensed under the Apache License, Version 2.0 with LLVM Exceptions. See LICENSE and NOTICE. Project values live in the nonbinding COVENANT.md, which grants and restricts no legal rights.

Project progress dashboard

Progress is built by the existing Rust generator. It plots daily default-branch snapshots from the beginning of the retained public project history, exact-content-deduplicated physical source lines, named test-file footprint, distinct reachable commit SHAs, all PRs and available GitHub Actions runs. These metrics measure repository activity, not qualification or individual executed tests.

The Pages workflow collects on pushes to main, manual runs, and hourly at minute 17 (UTC). GitHub can delay scheduled runs. The browser checks the published JSON every five minutes, preserves a selected historical day and marks snapshots older than three hours. Collection and reconciliation must succeed before deployment; a failed refresh retains the last good live page. Collection uses the built-in read-only Actions token against public endpoints; no token is shipped to browsers and no generated hourly commits are made. PR builds use the committed snapshot.

cargo run --release --manifest-path crates/site-builder/Cargo.toml -- progress public/data/project-progress.json
cargo test --manifest-path crates/site-builder/Cargo.toml
cargo run --release --manifest-path crates/site-builder/Cargo.toml -- build dist

Source boundaries, exclusions and the initial public repository allowlist are in crates/site-builder/src/collector.rs (site-builder progress [out.json] [--asof T] [--cache DIR] [--no-fetch]; it reads public data through gh api and mirror clones made with git, and keeps the curated events and policy text of the existing file). Daily boundaries are America/Chicago with US daylight saving rules written out in the same file. Newly discovered project-named public repositories are included automatically; forks/private repositories are excluded. The JSON includes the collection timestamp and every measured default-branch head. Deleted CI records cannot be reconstructed. Historical milestones and experiment examples are curated and linked to evidence; recent PR activity is collected automatically. D3 7.9.0 is self-hosted with its ISC license in public/vendor/.

Crumb coordination

This integration adopts RFC-0001, following the current protocol pointer. Durable .crumb files describe the changed directory boundaries. Using the canonical aien-architecture/tools/crumb tool: sniff before edits, respect unexpired locks, claim multi-step work, then close with the result. .crumb.local is ephemeral, ignored and excluded from the public site. Adoption started after the initial dashboard draft; the coordination record does not claim earlier edits were locked.