QAEDA.NET · MAIN PUBLICATIONNetwork →

RELATED, NOT COLLAPSED

QAEDA Network.

QAEDA can publish across more than one hostname without pretending those hostnames are one undifferentiated site. Cross-links are explicit; canonical, indexing, and policy boundaries stay legible.

01

One relationship.

AL.QAEDA.NET is presented by this site as a related QAEDA subdomain for additional project material.

02

Separate surfaces.

Each hostname is treated as owning its own URLs, canonicals, crawler policy, sitemap decisions, and page-level disclosures.

03

No invented meaning.

This site does not assert an expansion for the AL label. If that subdomain defines one, its own published material is the source of truth.

MAIN HOST01

QAEDA.NET

Quietly Against Every Damn Authority.

The main publication: cognitive liberty, civil liberties, accountable institutions, decentralization, research synthesis, Field Notes, and explicitly nonviolent dissent.

RELATED SUBDOMAIN02

AL.QAEDA.NET

Additional QAEDA material, separately published.

AL.QAEDA.NET is linked as a related destination outside this site’s canonical page tree. QAEDA.net does not silently treat pages on that hostname as local pages.

BOUNDARY CONTRACT

Cross-domain clarity beats invisible coupling.

Canonical boundary. The QAEDA.net sitemap lists QAEDA.net URLs only. The related subdomain is treated as a separate indexing surface rather than being smuggled into this host’s canonical tree.

Privacy boundary. A cross-link does not, by itself, imply shared cookies, login state, analytics, storage, or privacy terms. Readers should evaluate the disclosures published by the destination they are visiting.

Editorial boundary. A relationship between hostnames does not erase page-level provenance. Claims should be attributed to the page or source that actually publishes them.

Machine boundary. The same relationship is published in network.json so agents do not have to infer the topology from domain names alone.

THE RULE

Make relationships inspectable.

A network should tell readers what is connected, what is separate, and where authority for a claim actually lives.

View network.json