docs(positioning): declare release-toolkit Codeberg-primary — close round-4 positioning ambiguity #397

New issue

Closed

opened 2026-07-04 23:33:00 +02:00 by bosun · 0 comments

bosun commented

2026-07-04 23:33:00 +02:00

Owner

Empirical finding

Round-4 external cold-read named 4 conflated positioning claims as blocking v1.0.0 trust: Forgejo-native / Gitea-compatible / Codeberg-hosted / mirror-releases. Adopter can't tell what the tool's actual claim is.

Operator ratified 2026-07-04: declare release-toolkit Codeberg-primary as the definitive positioning. Forgejo (git.frankenbit.de) becomes internal-substrate; Codeberg (codeberg.org/FrankenBit/release-toolkit) becomes the adopter-facing primary.

Blocking rationale

v1.0.0 signals broad-adoption readiness. Positioning ambiguity is a v1.0.0 blocker per round-4 external verdict. A single definitive answer closes the class-axis; the alternative (docs polish across the 4 claims) invites the same ambiguity to re-surface.

Scope

Adopter-facing files where positioning language lives:

README.md: Positioning section — replace 4-axis matrix with 'Codeberg-primary' as the answer. Codeberg URLs as canonical.
docs/integration.md: URL examples use codeberg.org form, not git.frankenbit.de
AGENTS.md: cross-refs to Codeberg URLs where they're adopter-facing (per Herald's #391 read-path framing)
CHANGELOG.md: unchanged (historical)
docs/adr/: unchanged (historical / internal)

Verification AC

Adopter reading README arrives at 'Codeberg-primary' as definitive answer, not a matrix of hedged claims
All adopter-facing examples use codeberg.org URLs consistently
External cold-read round 5 finds no positioning ambiguity
Demo repo (#382) natural companion: 'this is a Codeberg-primary tool with a Codeberg-primary demo'

Closes round-4 positioning ambiguity finding (part of external verdict 'promising but not yet trustworthy')
Dovetails with #382 (Codeberg demo repo)
Sibling to #382 (docs migration to BookStack — see companion tracker T-B)
Sibling to companion tracker T-C (Forgejo description as internal pointer surface)

Anchor

Operator-ratified Codeberg-primary architectural shift 2026-07-04, following round-4 external cold-read positioning ambiguity finding (round-4 external named 4 conflated positioning claims: Forgejo-native / Gitea-compatible / Codeberg-hosted / mirror-releases). Herald's post-#393 read-path framing (external contributor: README → CONTRIBUTING → AGENTS.md; docs/internal is out-of-read-path archaeology) established the boundary. Substrate claim verified 2026-07-04: Forgejo push-mirror to codeberg.org is git-only (git protocol cannot push repo metadata), so Forgejo project description safe as internal-only pointer surface.

BLOCKING v1.0.0.

## Empirical finding Round-4 external cold-read named 4 conflated positioning claims as blocking v1.0.0 trust: Forgejo-native / Gitea-compatible / Codeberg-hosted / mirror-releases. Adopter can't tell what the tool's actual claim is. Operator ratified 2026-07-04: declare release-toolkit **Codeberg-primary** as the definitive positioning. Forgejo (git.frankenbit.de) becomes internal-substrate; Codeberg (codeberg.org/FrankenBit/release-toolkit) becomes the adopter-facing primary. ## Blocking rationale v1.0.0 signals broad-adoption readiness. Positioning ambiguity is a v1.0.0 blocker per round-4 external verdict. A single definitive answer closes the class-axis; the alternative (docs polish across the 4 claims) invites the same ambiguity to re-surface. ## Scope Adopter-facing files where positioning language lives: - **README.md**: Positioning section — replace 4-axis matrix with 'Codeberg-primary' as the answer. Codeberg URLs as canonical. - **docs/integration.md**: URL examples use codeberg.org form, not git.frankenbit.de - **AGENTS.md**: cross-refs to Codeberg URLs where they're adopter-facing (per Herald's #391 read-path framing) - **CHANGELOG.md**: unchanged (historical) - **docs/adr/**: unchanged (historical / internal) ## Verification AC - Adopter reading README arrives at 'Codeberg-primary' as definitive answer, not a matrix of hedged claims - All adopter-facing examples use codeberg.org URLs consistently - External cold-read round 5 finds no positioning ambiguity - Demo repo (#382) natural companion: 'this is a Codeberg-primary tool with a Codeberg-primary demo' ## Related - Closes round-4 positioning ambiguity finding (part of external verdict 'promising but not yet trustworthy') - Dovetails with #382 (Codeberg demo repo) - Sibling to #382 (docs migration to BookStack — see companion tracker T-B) - Sibling to companion tracker T-C (Forgejo description as internal pointer surface) ## Anchor Operator-ratified Codeberg-primary architectural shift 2026-07-04, following round-4 external cold-read positioning ambiguity finding (round-4 external named 4 conflated positioning claims: Forgejo-native / Gitea-compatible / Codeberg-hosted / mirror-releases). Herald's post-#393 read-path framing (external contributor: README → CONTRIBUTING → AGENTS.md; docs/internal is out-of-read-path archaeology) established the boundary. Substrate claim verified 2026-07-04: Forgejo push-mirror to codeberg.org is git-only (git protocol cannot push repo metadata), so Forgejo project description safe as internal-only pointer surface. BLOCKING v1.0.0.

bosun added the

priority/high

size/M

kind/docs

labels

2026-07-04 23:33:00 +02:00