abcdev.app may render public abcd-managed repositories other than abcd

Context

The product thinker proposed on 2026-10-09 (itd-2610091010348892) that abcdev.app renders the landing page and development record of any public abcd-managed project on GitHub, at abcdev.app/<owner>/<repo>/, with abcd's own pages moving to abcdev.app/intentdriven/abcd/ as the showcase.

That reverses adr-47 decision 1, "The website is a surface of this repository and of nothing else", and touches its constraint that the build depends on no runtime API calls because the unauthenticated GitHub API allows 60 requests an hour. It also sits beside the product thinker's 2026-10-05 choice of a separate site, abcdesign.app, where anyone opens and edits a public project's brief (itd-2610052000411162); on 2026-10-09 they ruled that both sites are kept: abcdev.app shows a project's record, abcdesign.app edits its brief.

Open before this record can be decided:

• Which repositories are rendered: every public repository carrying an abcd-managed marker, or only those whose owners opt in, and how an owner withdraws one.
• What may be rendered from a repository abcd's maintainers do not control, under abcd's domain, and what the page says about who wrote it (the site's single-source rule renders spans of a repository's own files; a third party's files are not abcd's).
• How builds run: on a schedule, on the owner's request, or from the owner's own release, within the GitHub API's limits, and what abuse or takedown path exists. On 2026-10-09 the product thinker required, for abcdesign.app and the local route, that a read-only build for someone not signed in is rate-limited so anonymous traffic, bots included, cannot exhaust the allowance the site serves from, and that a signed-in build spends the person's own allowance (adr-2610091016270711); on the same day they ruled that the same applies to abcdev.app: "same applies to abcdev.app, too (not just abcdesign.app)".

Requirements the product thinker set on 2026-10-09, which any decision here must meet:

• Public and private repositories are both supported; a private repository is reached only through the person's own GitHub sign-in.
• A read-only build for someone not signed in is rate-limited, so anonymous traffic, bots included, can never exhaust the GitHub allowance the site serves from.
• A build for a signed-in person spends that person's own GitHub allowance, never the site's.
• A shared cache serves a page built from a public repository to everyone; a page built from a private repository is served only to people that repository admits, never beyond.

On 2026-10-14 the product thinker narrowed these requirements for the first release, verbatim: "for now, public projects only in abcd, but private ones must be an option later". The private-repository requirements above stand for the later intent that adds private repositories; the decision here must leave room for them.

Decision

Withdrawn, not adopted. On 2026-10-14 the product thinker ruled that abcdev.app renders no other project: each opted-in project's about page and development record is built at each release by its own workflow onto its own GitHub Pages (itd-2610091010348892), abcd runs no server and holds no key, and abcdev.app becomes, if there is a need, a site for the abcd community. adr-47 decision 1 therefore stands for abcdev.app.

Alternatives Considered

Rendering every public abcd-managed repository, or only opted-in ones, at abcdev.app/<owner>/<repo>/ was explored on 2026-10-14 (research note 2026-10-14-abcdev-app-github-builds-and-cache.md) and set aside: it needs a server receiving GitHub's release notices or a key-holding GitHub App, both ruled out.

Consequences

No multi-repository rendering is built. The per-project route needs nothing from abcd beyond the release workflow it ships.