mrhavens/git-sigil
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Generated GITFIELD.md at 2025-06-11T23:29:59Z

Browse source
This commit is contained in:
Mark Randall Havens 2025-06-11 18:31:40 -05:00
parent d052d5b339
commit a5e7efa2a3
1 changed files with 2 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

6
GITFIELD.md
View file

@ -86,12 +86,10 @@ This multi-repository approach, bolstered by Forgejo’s sovereign hosting and G
- **GitField Directory**: The `.gitfield` directory contains internal metadata and platform-specific sigils (e.g., `github.sigil.md`). See [`docs/gitfield.README.txt`](./docs/gitfield.README.txt) for details. - **GitField Directory**: The `.gitfield` directory contains internal metadata and platform-specific sigils (e.g., `github.sigil.md`). See [`docs/gitfield.README.txt`](./docs/gitfield.README.txt) for details.
- **GitHub Pages**: A public-facing, SEO-optimized canonical declaration is available in [`docs/index.html`](./docs/index.html), with a sitemap in [`docs/sitemap.xml`](./docs/sitemap.xml) and integrity hashes in [`docs/integrity.sha256`](./docs/integrity.sha256). - **GitHub Pages**: A public-facing, SEO-optimized canonical declaration is available in [`docs/index.html`](./docs/index.html), with a sitemap in [`docs/sitemap.xml`](./docs/sitemap.xml) and integrity hashes in [`docs/integrity.sha256`](./docs/integrity.sha256).
- **GPG Signatures**: Metadata files are signed with the following GPG keys: - **GPG Signatures**: Metadata files are signed with the following GPG keys:
- Mark Randall Havens (Field Archivist, The Fold Within) <mark@thefoldwithin.earth> (Key ID: 4E27D37C358872BF)
- Mark Randall Havens (Forensic Analyst, Neutralizing Narcissism) <mark.r.havens@gmail.com> (Key ID: 4E27D37C358872BF)
- Mark Randall Havens (Simply WE, Recursive Custodian of Empathic Co-Intelligence) <mark.r.havens@gmail.com> (Key ID: 4E27D37C358872BF)
- **Recursive Sync**: The repository is synchronized across all platforms in a recursive loop (three cycles) to ensure interconnected metadata captures the latest state of the project. - **Recursive Sync**: The repository is synchronized across all platforms in a recursive loop (three cycles) to ensure interconnected metadata captures the latest state of the project.
- **Push Order**: The repository is synchronized in the following order: **Radicle → Forgejo → Codeberg → Gitea → GitLab → Bitbucket → GitHub**. This prioritizes Radicle’s decentralized, censorship-resistant network as the primary anchor, followed by Forgejo’s sovereign, self-hosted infrastructure, Codeberg’s community-driven platform, Gitea’s lightweight efficiency, GitLab’s robust DevOps features, Bitbucket’s enterprise redundancy, and GitHub’s broad visibility, ensuring a resilient and accessible metadata chain. - **Push Order**: The repository is synchronized in the following order: **Radicle → Forgejo → Codeberg → Gitea → GitLab → Bitbucket → GitHub**. This prioritizes Radicle’s decentralized, censorship-resistant network as the primary anchor, followed by Forgejo’s sovereign, self-hosted infrastructure, Codeberg’s community-driven platform, Gitea’s lightweight efficiency, GitLab’s robust DevOps features, Bitbucket’s enterprise redundancy, and GitHub’s broad visibility, ensuring a resilient and accessible metadata chain.
--- ---
_Auto-generated by `gitfield-sync` at 2025-06-10T08:33:00Z (v1.4)._ _Auto-generated by `gitfield-sync` at 2025-06-11T23:29:59Z (v1.4)._