https://www-staging.alwaldend.com/docs/infra/repos/ Recent content in Repositories on Alwaldend Hugo en https://www-staging.alwaldend.com/docs/infra/repos/openspec/spec/ Mon, 01 Jan 0001 00:00:00 +0000 https://www-staging.alwaldend.com/docs/infra/repos/openspec/spec/ <h1 id="repository-catalog-specification">repository-catalog Specification<a class="td-heading-self-link" href="#repository-catalog-specification" aria-label="Heading self-link"></a></h1><h2 id="purpose">Purpose<a class="td-heading-self-link" href="#purpose" aria-label="Heading self-link"></a></h2><p>Define shared organization, repository identity, naming, and named access configuration for the GitHub, GitLab, and Forgejo infrastructure consumers.</p> <h2 id="requirements">Requirements<a class="td-heading-self-link" href="#requirements" aria-label="Heading self-link"></a></h2><h3 id="requirement-authoritative-organization-and-repository-inventory">Requirement: Authoritative organization and repository inventory<a class="td-heading-self-link" href="#requirement-authoritative-organization-and-repository-inventory" aria-label="Heading self-link"></a></h3><p>The repository catalog SHALL store shared defaults and schema version at its root, one configuration file per organization, and one configuration file per repository beneath its organization. Those records SHALL own the configured organizations, repositories, named administrators, and named developers. Each forge consumer SHALL use that catalog for its selected repositories and named roles, preserving forge-specific settings without maintaining another copy of the inventory. Authentication and service-specific grants SHALL remain with their existing owners.</p>