Skip to content

[finding] One scaffold run writes three different documentation hostnames — objectstack.ai, objectstack.com, docs.objectstack.ai #10321

Description

@os-elon

Found during the new-developer first-run journey audit, #10264.

The first three files a newcomer reads point at three different hosts. Verified by the PM on origin/main:

FileHost
root README.md:174https://objectstack.ai/docs/…
packages/create-objectstack/src/templates/AGENTS.md:99https://objectstack.com/docs
packages/create-objectstack/src/templates/blank/README.md:39,70,108https://docs.objectstack.ai/docs/…
…/blank/Dockerfile:10, …/blank/docker-compose.yml:7https://docs.objectstack.ai/docs/…

objectstack.com is a different domain from objectstack.ai. The last three all ship inside the same create-objectstack@17.1.0 output, so a single scaffold run hands the user two of the three.

Scope of the claim

Reported as an internal inconsistency, not as verified dead links. All three hosts are egress-blocked in the audit runner, so the auditor could not resolve any of them and deliberately did not claim which are broken. They cannot all be right; which one is canonical is for whoever takes this to decide.

Each wrong link is a dead end at the exact moment someone went looking for help — the worst possible time to spend a reader's patience.

Suggested landing (hint for triage, not a routing decision)

packages/create-objectstack/src/templates/ (both AGENTS.md and blank/), plus root README.md if the canonical host turns out not to be the one it uses. Worth checking whether anything gates doc hostnames repo-wide.

Filed by the PM loop from the audit in #10264. Not yet graded or routed.

Metadata

Metadata

Assignees

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions