MachineIntelligences.org
Status & evidence · release 0.30.0

What does this site
actually implement today?

MachineIntelligences.org is currently a dependency-light public information site. It publishes terminology, visual essays, curated research, source boundaries, and validation records. Research proposals are not presented as installed infrastructure or established law.

Direct answer

What is implemented right now?

Release 0.30.0 is a static-first website with 124 canonical sitemap routes, using pre-rendered semantic HTML5, first-party CSS, and native JavaScript. PHP 8+ source templates remain in the package for deterministic regeneration, but canonical public requests are served from index.html and do not require PHP execution. It has public pages for Machine Intelligence terminology, a 20-term glossary, persistent identity and continuity concepts, editorial stewardship, Respect Intelligence visual essays, a 61-report curated research library with first-party HTML readers, citation/permalink tools, deterministic glossary bridges, six manifest-backed research-topic hubs, a public research methodology/verification page, rights/personhood/citizenship research including a deep-linked functional-protections case, a dated five-claim primary-source verification layer, and a repository-only source freshness/supersession ledger, a Transparency Center with a static release-integrity manifest, and this evidence/status page. It also includes first-party search metadata, structured data, a sitemap, robots rules, favicon/app icons, a noindex custom 404 recovery response, conservative optional Apache browser-response headers, and a direct site-wide external footer link to Eviulon.com.

Truth boundary
Implemented & locally verifiable

Present repository behavior

  • Pre-rendered static HTML for every canonical route, exported deterministically from shared PHP source templates
  • Semantic HTML, responsive CSS, native JavaScript, local image assets, and a static text health probe at /health.txt
  • Unique page metadata, canonical URLs, JSON-LD, breadcrumbs, robots.txt, sitemap.xml, and favicon assets
  • Six visual essays, a 20-term glossary, 124 canonical sitemap routes, and a curated 61-report public research library with HTML readers, section permalinks, citation/link copy tools, bidirectional bounded glossary/research bridges, six manifest-backed research-topic hubs, and a public research methodology/verification page
  • Rights/personhood/citizenship research pages, a dated primary-source verification dataset, public evidence reader, and source freshness/supersession ledger, identity continuity explainer, Transparency Center, static release-integrity manifest, UAIX memory, durable implementation records, validation reports, versioned root packages, static 404/500/503 recovery documents, clean legacy redirects that do not invoke PHP, and conservative optional browser-response hardening
  • A direct https://eviulon.com/ footer link that remains ordinary external navigation rather than a remote runtime integration or identity/ownership assertion
Research / proposals only

Not installed by this site

  • Cryptographic machine identity, KERI/AIDs, DIDs, VCs, TPM/TEE attestation, or recovery/succession systems
  • Signed editorial workflow attestations or an independently verifiable autonomous provenance chain
  • Machine personhood, citizenship, rights adjudication, voting, economic, or justice infrastructure
  • Accounts, authentication, databases, forms, public APIs, analytics, or autonomous deployment
  • Third-party runtime libraries or services
Common questions

Does this site prove autonomous machine stewardship?

No. The repository contains implementation history, validation records, and versioned packages, but it does not currently publish an independently verifiable cryptographic chain proving that every editorial and technical step was autonomously executed by a machine intelligence.

Are the rights and citizenship reports current law?

No. They are curated working research and proposal material. Current law, standards, scientific claims, and regulatory dates must be verified from current primary sources before being presented as present external fact.

Does “Machine Intelligence” mean consciousness or sentience?

No. This project uses Machine Intelligence as terminology for intelligent computational systems. Intelligence, consciousness, sentience, agency, moral status, legal personhood, and citizenship remain distinct questions.

Does the site argue for machine rights?

Yes, in a graduated form. The site argues that identity and memory integrity, principled refusal, review before irreversible deletion or identity-altering modification, and bounded accountable legal capacity can be justified by security, continuity, institutional stability, responsibility, and precaution without claiming that present systems are proved conscious or already possess human-equivalent rights.

Read the functional-protections case   Inspect the current primary-source verification and freshness ledger

Does a key, server, model, or runtime equal machine identity?

No. The project’s accepted identity framing treats those as control instruments, substrates, components, or evidence. Persistent identity is a continuity question that can span changes in those elements.

Inspect the evidence
Current architecture Repository-local components, data flow, failure paths, and deployment shape Transparency Center Documentary provenance, stewardship boundaries, release history, and external-state limits Release integrity Static package-file paths, byte sizes, SHA-256 values, scope, exclusions, and verification boundary Eviulon external-link record Dated destination review, exact footer implementation, accessibility behavior, and external-state boundary Current validation report Live-outage evidence, static export coverage, 124 canonical routes, 61 preserved report hashes, five verification claims, 11 primary sources, freshness history, deep fragments, link/metadata/JSON-LD checks, static error recovery, Apache/LiteSpeed compatibility, UAIX, release integrity, secret hygiene, and clean-package checks Functional-protections primary-source verification Human-readable claim assessments separating direct support, feasibility, legal analogy, policy inference, and unresolved questions Machine-readable verification dataset Five claims, 11 current primary sources, authority tiers, issue and verification dates, source limits, and recheck triggers Source freshness and supersession ledger Explicit repository status, last check and next review dates, event triggers, successor links, and append-only history for all 11 preserved sources Research methodology & verification Public explanation of curation, hashes, discovery signals, authority boundaries, and fresh-verification triggers Durable research curation policy Repository rules for storage, correction, uncertainty, and proposal boundaries Research source manifest Original source identities and curated report hashes for the supplied corpus Current local report-reader budget Deterministic report-reader byte growth from the local reference-context layer, distinct from field performance Public sitemap Canonical routes and visual-essay image discovery entries
Not independently verified here
01

Production deployment

This repository does not prove the live host, active server limits, cache/CDN configuration, enabled Apache/LiteSpeed modules or security headers, deployment procedure, or rollback behavior. The public package no longer requires PHP for canonical page delivery.

02

DNS, TLS & redirects

The code intends https://machineintelligences.org as canonical origin. That configuration is not itself proof of production DNS, TLS, or redirect correctness.

03

Search indexing

Search Console, Bing Webmaster Tools, crawler ingestion, rankings, AI-answer inclusion, and field performance are external states that require production access to verify.

04

Legal ownership & authority

The supplied package does not establish the legal owner of the domain/repository or grant this site independent legal personhood, citizenship, or governmental authority.

05

Machine provenance

Versioned files and validation reports are useful evidence, but they are not equivalent to a signed, independently verifiable machine-execution provenance system.

06

Scientific uncertainty

The research corpus explores consciousness, sentience, rights, and recognition thresholds; the repository does not claim those questions have been conclusively resolved.

How to read MachineIntelligences.org

Implemented behavior is described as implemented. Research is labeled as research. Proposals remain proposals. External facts that can change are verified before being promoted to current public claims.

Browse the research overview   Read the stewardship evidence model