Skip to content

docs(planning): the generator's backlog carries its own specs - #167

Merged
sksizer merged 1 commit into
mainfrom
port-dev-ontogen-specs
Sep 21, 2026
Merged

sksizer merged 1 commit into
mainfrom
port-dev-ontogen-specs

Conversation

@sksizer

@sksizer sksizer commented Sep 21, 2026

Copy link
Copy Markdown
Owner

Eight task specs authored in the consuming dev monorepo — written against ontogen's own source, citing its files — move into docs/planning/tasks/. The generator's backlog now carries the reasoning behind changes that were only ever recorded on the consumer side.

Six are already in review here and now have a spec behind them:

Task PR
API surfaces with their own store accessor #156
Pagination declared per module folded into #156
Pagination pushdown into the store #159, #166
Enum variants, labels and the id type #160
Admin layer: registry path, pickers, packaging #157 (merged), #158
Docs stage: data-model reference and JSON Schema #161

Two have no implementation yet and land as backlog:

  • Bytes, timestamp, date and JSON columns, defaults, and declared indexes — the field-type vocabulary a realistic domain model needs.
  • Explicit route shapes, or loud failure — route shape is inferred from name prefixes and arity, and a wrong name reshapes routes silently. Also covers the alphabetical TS type-pool ordering that makes every small API change a large generated diff.

A ninth consumer item, per-variant HTTP error status, is not ported: the E0003 epic already covers it.

What changed in the porting

  • Paths are repo-relative; the /Users/.../rust-ontogen/ clone references are gone.
  • The consumer's situation reads as motivation, not scope.
  • Consumer-side acceptance criteria — pin bumps, git diff --exit-code drift gates, "fallback if the upstream PR stalls" — stay in the monorepo, where they are actionable.
  • Cross-references are relative links between the ported files instead of the monorepo's wikilinks.

Docs only; no code touched.

Eight specs authored in the consuming dev monorepo against ontogen's
source — six of them already in review here as #156, #158, #159, #160,
#161 and #166 — move into docs/planning/tasks/ so the reasoning behind
each change lives with the generator rather than with one consumer.

Rewritten upstream-native: repo-relative paths, the consumer's situation
as motivation rather than scope, and the consumer-side acceptance
criteria (pin bumps, drift gates, fallback plans) left behind in the
monorepo where they belong.

Two carry no implementation yet: the schema field-type vocabulary
(bytes, timestamp, date, JSON, defaults, declared indexes) and explicit
route shapes. The consumer's ninth item, per-variant HTTP error status,
is already covered by the E0003 epic and is not duplicated here.
@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Sep 21, 2026 •

Copy link
Copy Markdown

Deploying ontogen with  Cloudflare Pages  Cloudflare Pages

Latest commit: 34d748e
Status: ✅  Deploy successful!
Preview URL: https://2d7cb60d.ontogen.pages.dev
Branch Preview URL: https://port-dev-ontogen-specs.ontogen.pages.dev

View logs

@sksizer
sksizer merged commit 71fa574 into main Sep 21, 2026
2 checks passed
@sksizer
sksizer deleted the port-dev-ontogen-specs branch September 21, 2026 04:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant