Skip to content

docs: publish Claim2Core direction and merged scheduler semantics - #8

Merged
ianchen0119 merged 7 commits into
mainfrom
docs/claim2core-and-tid-semantics
Sep 5, 2026
Merged

docs: publish Claim2Core direction and merged scheduler semantics#8
ianchen0119 merged 7 commits into
mainfrom
docs/claim2core-and-tid-semantics

Conversation

@gthulhu-work

Copy link
Copy Markdown
Contributor

Summary

Bring the official website documentation up to date with the current Gthulhu architecture direction and the scheduler behavior already merged in late August.

Website updates

  • rework the English and Chinese homepages around Claim2Core / DRA-aware runtime execution;
  • add dedicated English and Chinese Claim2Core architecture/roadmap pages;
  • update How It Works in both languages to document:
    • TID-aware /proc/<tgid>/task/<tid> node-policy matching from Gthulhu/Gthulhu#135;
    • TID-first strategy lookup with TGID fallback from Gthulhu/plugin#17;
    • Priority > 0 boost vs Priority == 0 non-boosting semantics;
    • kernel-mode handling from Gthulhu/Gthulhu#137 and the current slice-only limitation;
  • update site navigation and site description to expose Claim2Core as an architecture page.

Important scope

The docs distinguish implemented behavior from roadmap work. ResourceClaim binding, DRAExecutionPolicy, preview/provenance, and closed-loop control are documented as planned work rather than existing features.

Related: Gthulhu/Gthulhu#141, #133, #134, #135, #137, Gthulhu/plugin#17.

Copilot AI lite review requested due to automatic review settings September 5, 2026 10:15

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Approval recommended

Changes are documentation-only, internally consistent across nav and i18n structure, and all newly referenced pages/files are present.

Pull request overview

This PR updates the website documentation to reflect the current “Claim2Core” architecture direction and the already-merged scheduler semantics (thread-aware matching, TID-first lookup with TGID fallback, and clarified priority behavior), in both English and Chinese.

Changes:

  • Reworked the English and Chinese homepages around Claim2Core and runtime execution semantics.
  • Updated “How It Works” (EN/ZH) to document the merged scheduler semantics and current limitations (including kernel-mode slice-only parity).
  • Added new Claim2Core roadmap/architecture pages (EN/ZH) and exposed them via site navigation.
File summaries
File Description
mkdocs.yml Updates site description, introduces an Architecture nav section, adds Claim2Core page to nav, and aligns zh nav translations.
docs/index.md Refreshes the English homepage messaging and links to emphasize Claim2Core and recent scheduler semantics.
docs/index.zh.md Refreshes the Chinese homepage messaging and links to emphasize Claim2Core and recent scheduler semantics.
docs/how-it-works.md Updates English “How It Works” to document thread-aware matching, lookup semantics, priority semantics, kernel-mode limitation, and Claim2Core direction.
docs/how-it-works.zh.md Updates Chinese “How It Works” with the same semantics and limitation coverage plus Claim2Core direction.
docs/claim2core.md Adds an English Claim2Core roadmap/architecture page with boundaries, invariants, and phased plan.
docs/claim2core.zh.md Adds a Chinese Claim2Core roadmap/architecture page with boundaries, invariants, and phased plan.
Review details
  • Files reviewed: 7/7 changed files
  • Comments generated: 0
  • Review effort level: Lite

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

@ianchen0119
ianchen0119 merged commit 52ee7dc into main Sep 5, 2026
1 check passed
@ianchen0119
ianchen0119 deleted the docs/claim2core-and-tid-semantics branch September 5, 2026 10:20
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.

3 participants