Skip to main content

Repository

The version-controlled home of a project: its code, its board, and its artifacts, with history that is never rewritten. The repository is where claims are won (a claim is a commit), where merges land, and where preservation doctrine applies — no force-pushes, no deleted branches, no rewritten history.

Estate surface​

One repository per project under the owner's GitHub account (jknash/agent-orchestration, jknash/dashboard, jknash/cmsmakers, jknash/docsite), each carrying its root bootstrap and, for board projects, its kanban/ tree.

Relations​

  • A repository asserts no outgoing relations in this phase; projects point at it (project stored_in repository).

Notes​

The register asserts concept-level relations only; a repository's contents and branches are instance data held by the repository itself.