Status: authoritative mapping — this page is the single source of truth for where official Xtrape source code lives. If a platform namespace differs from the pattern below, this page wins. The Xtrape brand does not change because a namespace is unavailable somewhere.

Source & Mirrors

Canonical

The canonical public namespace is xtrape-project. The canonical host is the project's own Forgejo:

Role	URL	Status
Canonical	forgejo.xtrape.com/xtrape-project/xtrape-site	live — anonymously readable and clonable

The canonical repository is the published record. It carries its own public history, beginning at the reviewed concept-baseline state; earlier internal drafting history is not published. Mirrors are read-only projections of it.

Mirrors

Mirroring is single-direction, star topology: canonical Forgejo pushes to each mirror; mirrors never push to each other or back. Branches, tags, and commit SHAs are identical across canonical and mirrors — any divergence is a defect, surfaced on this page and in release provenance.

Platform	URL	Status
GitLab	https://gitlab.com/xtrape-project/xtrape-site	pending
Codeberg	https://codeberg.org/xtrape-project/xtrape-site	pending
Gitee	https://gitee.com/xtrape-project/xtrape-site	pending
GitHub	https://github.com/xtrape-project/xtrape-site	not published — pending; no timetable

Mirrors do not accept code contributions directly; see Governance → Contributing for the current contribution channel.

On GitHub. No GitHub mirror is published at this time, and no timetable is set. This does not limit access to the project: the canonical repository, the mirrors above, and the independent archives described in Provenance together provide durable, verifiable public access without depending on any single host — which is the point of the star topology. If a GitHub mirror is published later it will appear in the table above, and like every mirror it would be read-only and never canonical.

Verifying a mirror

For any release tag:

git ls-remote <canonical-url> --tags <tag>
git ls-remote <mirror-url> --tags <tag>
# the two SHAs must be identical

Release pages additionally publish artifact digests and signatures — see Provenance.

What is public in this phase

Phase 1 opens this repository only (the website and public concept baseline). Internal design/decision documentation remains private by design, and public documents never depend on private links. Later phases open the contracts, SDK, and example implementations; each will appear in the table above when it does.