Skip to content

docs: compose WorldState and GeoTask public portal - #32

Open
stpku wants to merge 9 commits into
mainfrom
feat/worldstate-geotask-public-portal-v0.1
Open

stpku wants to merge 9 commits into
mainfrom
feat/worldstate-geotask-public-portal-v0.1

Conversation

@stpku

@stpku stpku commented Aug 27, 2026

Copy link
Copy Markdown
Owner

Goal

Reframe the GeoTask GitHub Pages root as a shared public entry for WorldState + GeoTask without merging repository or semantic ownership.

Public story

Reality → WorldState → GeoTask → Agent

  • WorldState: what is true, unknown, conflicted, valid, stale, or changed about the world.
  • GeoTask: what the current task needs to know, whether context is applicable/resolution-adequate/sufficient, and how to minimize context cost.

Changes

  • make the first-screen story primarily Chinese and reduce generic Chinese/English mixing;
  • retain canonical API/object names where they carry engineering meaning;
  • add explicit WorldState and GeoTask foundation cards and independence boundaries;
  • add independent consumer proofs for Warehouse Robot Picking and WorldState cold-chain state;
  • keep GT01–GT42 routes as a historical archive rather than moving the whole series into WorldState;
  • add three recommended historical learning paths;
  • add a visible ★ GitHub navigation CTA and ★ Star GeoTask closing CTA without displaying a potentially misleading star count;
  • preserve the current Task Context Engine invariants, all 42 case routes, SEO metadata, and static/no-network portal behavior;
  • add a focused regression test freezing the combined-portal boundary.

Non-goals

  • no repository merge;
  • no WorldState code change;
  • no GT route migration;
  • no production/runtime semantic change;
  • no merge or Pages publication in this PR step.

Review focus

  1. Does one public story improve first-time comprehension without making WorldState look like a GeoTask submodule?
  2. Is the Chinese surface natural enough while preserving canonical technical names?
  3. Does the historical-case treatment correctly preserve provenance without carrying legacy positioning into the hero narrative?
  4. Is the Star CTA visible but not intrusive?

@stpku
stpku marked this pull request as ready for review August 27, 2026 10:19
@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.

stpku commented Aug 27, 2026

Copy link
Copy Markdown
Owner Author

Final visual / Fresh Eyes gate

Verdict: PASS_WITH_MOBILE_STAR_ATTENTION

Validated on exact candidate 5a28ce9b07ae47a8189a9172724281228e058a67 after full CI success.

  • Desktop first-screen comprehension: PASS — the page explains Reality → WorldState → GeoTask → Agent without merging semantic ownership.
  • Chinese/English narrative parity: PASS.
  • WorldState truth boundary: PASS — state is evidence/validity/unknown/conflict aware rather than presented as an unconditional truth oracle.
  • GeoTask Task Context identity: PASS.
  • GT01–GT42 historical treatment: PASS — curated learning paths first, full generated catalog preserved and collapsed.
  • P1 Reference Agent compatibility entry: PASS.
  • Desktop GitHub Star CTA: PASS.
  • Mobile hierarchy / one-column flow: PASS.
  • Attention: at max-width:760px, .links{display:none} also hides the header ★ GitHub CTA. The closing-page Star CTA remains available, but the requested top-right Star affordance is not visible on mobile.

No further portal content changes are included in this review. Do not merge/publish solely on this comment; mobile Star visibility should be treated as the only remaining visual polish decision.

This branch has not been deployed

No deployments
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