Skip to content

docs(hub): five goal-based entry points ahead of the package pipeline - #96

Merged
firejune merged 1 commit into
mainfrom
naru/89-goal-based-entry-points
Oct 27, 2026
Merged

firejune merged 1 commit into
mainfrom
naru/89-goal-based-entry-points

Conversation

@firejune

Copy link
Copy Markdown
Contributor

Closes #89. One file: content/docs/index.md.

A five-row chooser (start from a painting and layers · play an existing compiled rig · apply a pose sequence · add interactive head/gaze controls · inspect, correct and review an agent's result) with what to have ready, minimum packages, output and one next step; the package map and existing anchors stay. Explicit lines: input generation precedes CPU-only processing; compiled playback skips both; structural checks do not judge appearance; the adapter example's slider fixture does not establish the new depth producer's playback.

Check Result
targeted / full 21 pass / 68 pass (642 assertions)
build / verify 13 pages + 8 redirects / 0 (HTML + Markdown/LLM, anchors)
planted-anchor control red → green
browser 1440 / 390 px 5 rows, 8 route clicks each, no overflow

@codex review

🤖 Generated with Claude Code

The docs hub explained the packages in pipeline order, so a visitor who only
wanted to play an existing compiled rig had to read about image generation
and rig authoring first. The hub now opens with a five-row chooser — start
from a painting and layers; play an existing compiled rig; apply a pose
sequence; add interactive head/gaze controls; inspect, correct and review an
agent's result — each naming what to have ready, the minimum packages, what
comes out and one authoritative next step, then keeps the package map and
every existing anchor.

Stated explicitly: painting and layer generation happen before CPU-only
rig-c processing; compiled-model playback skips both; structural checks do
not judge how a rig looks, a person still inspects; the adapter example's
public slider fixture does not establish playback of the newly released
depth producer. The interactive row points at the capabilities page.

Measured: targeted 21 pass / 240 assertions; full 68 pass / 642; build 13
pages + 8 redirects; verify 0 over 13 HTML + 13 Markdown/LLM routes; the
planted-anchor control red then green; browser at 1440 and 390 px: five rows,
eight local route clicks each, old anchors reachable, no body overflow.

Rejected: JavaScript or style additions; forcing authoring through playback
or inspection; any new depth-combination claim; #91's example delivery.

Closes #89

Co-Authored-By: Naru <342599188+fj-naru[bot]@users.noreply.github.com>
Co-Authored-By: Roa <342598975+fj-roa[bot]@users.noreply.github.com>
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 27, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-27T03:48:36.831798Z ed37a77 Manual request
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Swish!

Reviewed commit: ed37a778ad

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@firejune
firejune merged commit 51cbfb7 into main Oct 27, 2026
3 checks passed
@firejune
firejune deleted the naru/89-goal-based-entry-points branch October 27, 2026 04:11
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.

docs(navigation): add goal-based entry points alongside the package pipeline

1 participant