This public .github repository contains organization-wide community health files, contributor guidance, shared agent policy, and explicit repository, planning, and delivery contracts.
Repository-local policy wins when it is stricter or more specific. Existing project history must be preserved during consolidation and conflict resolution.
- Canonical organization routing
- Machine-readable routing projection
- Routing schema
- GitHub Projects and Linear operating contract
- Deterministic project registry generator
- Project registry artifact schema
- Project registry artifact workflow
- Canonical CLI and project-registry consumer:
3FA-app/3FA-app-cli - Repository boundaries
- Branching and GitOps policy
The canonical execution board is GitHub Project 3FA-app-project #1. The planning system of record is the Linear project github.com/3FA-app. Projects access reconciliation is tracked in DEN-2439 and GitHub issue #9; restricted automation must not create a duplicate board.
Private repository details are intentionally withheld from this public document.
The canonical execution board currently projects 14 repositories, including
3FA-app/3FA-app-cli with role cli.
Pull-request and main workflows publish a deterministic Markdown/JSON project
registry plus SHA-256 checksums as a GitHub Actions artifact.
This public repository is the canonical source for GitHub-supported community-health fallbacks, organization profile content, contribution guidance, public security/support policy, issue and pull-request templates, and agent-governance declarations for 3FA-app.
- GitHub organization: https://github.com/3FA-app
- Public organization defaults: https://github.com/3FA-app/.github
- Canonical Linear project: https://linear.app/denman/project/githubcom3fa-app-c3db52220894
- Fleet tracking issue: ORESoftware/k8s-cluster#1222
All Git conflicts must be resolved semantically with full historical, repository-wide, organization-wide, and relevant external-organization context. Automated agents are hard-denied from destructive or history-rewriting operations, including all forms of git stash, git reset, git clean, git filter-repo, force pushing, destructive deletion, data or infrastructure teardown, credential revocation, and policy bypass.
GitHub can use supported community-health files from a public organization .github repository as fallbacks and can render profile/README.md on the organization page. agents.md, AGENTS.md, Copilot instructions, workflows, settings, rulesets, branch protections, permissions, and secrets are not automatically inherited merely because they exist here. Each repository must carry or synchronize compatible local policy and explicitly call reusable workflows where enforcement is required.
Generated managed-policy version: 2026-08-08.
3FA-app declares repository roles, dependency edges, cross-organization capabilities, deployment ownership, and the git-submodule/Zed-package contract:
The public registry withholds private repository names and edges.