Nepal Dev VerseGitHub

ADR-0039 — nepal-dev.com owns the site, and @puncoz approves for it

The site's owner is nepal-dev.com. The maker still maintains it and approves its ADRs as @puncoz, and the footer's credit stays.

  • Status: Approved
  • Date: 2026-11-03
  • Deciders: @puncoz
  • Approved by: @puncoz
  • Approved on: 2026-11-03
  • Supersedes: ADR-0036 decision 12 (in part: who is named as the owner in the working documents)
  • Superseded by: —
  • Design documents: none; this changes who is named, not how the site works

Context

ADR-0036 made the site part of nepal-dev.com, and decision 12 kept the maker as the owner in the working documents. On 2026-11-03 the owner said that the owner is nepal-dev.com, and chose to keep approving decisions personally. The working documents use "the owner" throughout for whoever reviews and approves, so that role needs a person even though an organisation owns the site. An ADR's Deciders and Approved by take a GitHub username (ADR-0020).

Decision

  1. The site's owner is nepal-dev.com. AGENTS.md, PROJECT_AGENTS.md, PRODUCT.md and README.md say so.
  2. The maker still maintains the site and acts for the owner. In the working documents, "the owner" reviews, approves and decides through puncoz. Deciders and Approved by stay [@puncoz](https://github.com/puncoz) (ADR-0020).
  3. Nothing else moves. The footer's credit and its link (ADR-0036 decision 9), existing ADRs and the ADR gate stay as they are.

Options considered

OptionProsConsVerdict
nepal-dev.com owns; @puncoz approvesTrue to the owner's words; the gate keeps a named person"The owner" now means someone acting for an organisationChosen (owner)
nepal-dev.com also approves, through its GitHub accountOne name for bothAn organisation account in the ADR chips, unchecked; a change to who passes the gateRejected (owner)
Change the README onlySmallest changeThe working documents contradict the ownerRejected (owner)

Consequences

Positive

  • The documents agree with the site, which already names nepal-dev.com as its community and publisher.

Negative / accepted trade-offs

  • A later change of who approves needs its own ADR.

Content invariants

None touched.

Security considerations

None. This touches no data, endpoint or secret. Authority over private or public decisions stays with the same person (ADR-0004, ADR-0005), and puncoz is already public as a GitHub username (ADR-0020).

Implementation notes

No app flow (ADR-0008): nothing a reader sees changes.

  • AGENTS.md §1 and §2, PROJECT_AGENTS.md, PRODUCT.md, README.md (decisions 1 and 2).
  • "Superseded by" in ADR-0036.
  • Tests (ADR-0007): each working document names nepal-dev.com as the owner, and none still names the maker as owner and maintainer.
  • bun run test, bun run types:check and bunx next build pass, and the lint failure is reported while it stands.

Docs to update on implementation

  • content/docs/maintain/security/data-classification.mdx: who puncoz approves for
  • content/docs/maintain/adr/index.mdx: this ADR's row and the next free number

ADR-0038 — Earlier names leave the pages, and the GitHub link follows the move

Approved ADRs are reworded once so the site's earlier names leave every page, and the site's GitHub link moves to the repository's new home.

Architecture

How the site is put together: its content sources, build steps, routes and integrations.

On this page

3 min read
  1. Context
  2. Decision
  3. Options considered
  4. Consequences
  5. Content invariants
  6. Security considerations
  7. Implementation notes
  8. Docs to update on implementation