Architectus Decisions

Forge Selection Rationale

Why Three Forges?

Principle Reasoning

Vendor Independence

No single forge controls availability of all repositories

CI/CD Redundancy

GitHub Actions is primary, GitLab CI is backup — if one fails, the other deploys

Self-Hosted Backup

Gitea on local infrastructure provides a complete offline copy

Zero-Trust Distribution

Public forges (GitHub, GitLab) for collaboration; private forge (Gitea) for sovereignty

GitHub as Primary

  • Cloudflare Pages has native GitHub integration

  • repository_dispatch enables spoke-to-hub triggering

  • Largest community visibility for public content

GitLab as Backup

  • Independent CI pipeline via wrangler direct deploy

  • Separate token management (no shared credential chain)

  • Can be promoted to primary if GitHub has extended outages

Gitea as Archive

  • Runs on gitea-01.inside.domusdigitalis.dev inside the management network

  • Full mirror of all repositories

  • No external dependency — works during internet outages

  • Serves as disaster recovery source

Design Decisions

Antora Hub-Spoke Model

Decision: Use Antora multi-repo aggregation rather than a monorepo.

Rationale:

  • Each domain (technology, humanities, exploration) evolves independently

  • Contributors can clone only the repos they need

  • CI/CD triggers only rebuild when relevant content changes

  • Maps cleanly to organizational boundaries

Domain Taxonomy

Decision: Three top-level domains (Technology, Humanities, Exploration).

Rationale:

  • Technology covers the professional engineering body of knowledge

  • Humanities covers the liberal arts and classical education track

  • Exploration covers applied field sciences (radio, navigation)

  • Each domain can scale independently without polluting others

Public vs. Private Content

Decision: architectus.dev is fully public; domusdigitalis.dev is private.

Rationale:

  • architectus content is sanitized of internal infrastructure details

  • No IP addresses, hostnames, or credential references

  • Suitable for portfolio, community sharing, and professional visibility

  • domus-* repos contain operational specifics (IPs, VLANs, credentials paths)