Generated GITFIELD.md at 2025-06-06 01:30:02

This commit is contained in:
Mark Randall Havens 2025-06-06 01:31:45 -05:00
parent a96a6672b5
commit a56abf8cd2

View file

@ -11,9 +11,22 @@ The `git-sigil` project employs a multi-repository strategy across four distinct
The following platforms host the `git-sigil` repository, each chosen for its unique strengths and contributions to the project's goals.
### 1. Radicle
- **URL**: [https://app.radicle.xyz/nodes/ash.radicle.garden/rad:z45QC21eWL1F43VSbnV9AZbCZrHQJ](https://app.radicle.xyz/nodes/ash.radicle.garden/rad:z45QC21eWL1F43VSbnV9AZbCZrHQJ)
- **RID**: rad:z3FEj7rF8gZw9eFksCuiN43qjzrex
- **Peer ID**: z6Mkw5s3ppo26C7y7tGK5MD8n2GqTHS582PPpeX5Xqbu2Mpz
- **Purpose**: Radicle is a decentralized, peer-to-peer git platform that ensures sovereignty and censorship resistance. It hosts the repository in a distributed network, independent of centralized servers.
- **Value**: Protects against deplatforming by eliminating reliance on centralized infrastructure, ensuring the project remains accessible in a decentralized ecosystem.
- **Access Details**: To view project details, run:
```bash
rad inspect rad:z3FEj7rF8gZw9eFksCuiN43qjzrex
```
To view the file structure, run:
```bash
rad ls rad:z3FEj7rF8gZw9eFksCuiN43qjzrex
```
Alternatively, use Git to list files at the current HEAD:
```bash
git ls-tree -r --name-only HEAD
```
### 2. GitLab
- **URL**: [https://gitlab.com/mrhavens/git-sigil](https://gitlab.com/mrhavens/git-sigil)
@ -48,10 +61,10 @@ This multi-repository approach reflects a commitment to preserving the integrity
## 📜 Metadata and Logs
- **Metadata Files**: Each platform generates a metadata snapshot in the `.gitfield` directory (e.g., `github.sigil.md`, `gitlab.sigil.md`, etc.), capturing commit details, environment information, and hardware fingerprints.
- **Push Log**: The `.gitfield/pushed.log` file records the date, time, and URL of every push operation across all platforms, providing a transparent audit trail.
- **Push Log**: The `.gitfield/pushed.log` file records the date, time, and RID/URL of every push operation across all platforms, providing a transparent audit trail.
- **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 → GitLab → Bitbucket → GitHub**. This prioritizes Radicles decentralized, censorship-resistant network as the primary anchor, followed by GitLabs robust DevOps features, Bitbuckets enterprise redundancy, and GitHubs broad visibility, ensuring a resilient and accessible metadata chain.
---
_Auto-generated by `gitfield-sync` at 2025-06-05 02:36:33 (v1.0)._
_Auto-generated by `gitfield-sync` at 2025-06-06 01:30:02 (v1.0)._