Official site wave-2: architecture overview + doctrine highlights pages (EN + zh)

[loning]

Parent: official-site umbrella issue (#2). Wave-1 (#3) is verified live: https://chronoaiproject.github.io/fkst-website/ (EN) and /zh/ (中文), deployed by the autonomous pipeline end-to-end.

Scope (tight)

Add the wave-2 content pages to the existing static site (same conventions as wave-1: pure static, no build framework, no JS, English-primary with zh mirrors, shared site/style.css, EN/中文 header cross-links):

1. site/architecture.html + site/zh/architecture.html — architecture overview:
   • the three-tier company model (Company / Department / Person) and the event flow source → fanout → route → spawn → RAISED;
   • reliable delivery (redb-backed, at-least-once-until-ack, lease+fencing, DLQ) and the "content never rides the payload; consumers re-fetch via source_ref" constitution;
   • the three-repo ecosystem and composition model (flat vs composed packages; engine unions N package roots into one graph).
2. site/doctrine.html + site/zh/doctrine.html — doctrine highlights (selected, not exhaustive):
   • marker-as-fact with version-CAS over an eventually-consistent GitHub;
   • gates are codex-judgment pipelines, not per-event human labels; the only write-posture switch is a host env fact;
   • no backward-compat modes: the system has exactly one current shape; patterns must serve a proven present problem (YAGNI).
3. Navigation: add links to the two new pages from the homepage (both languages); each page links back home.
4. Content basis: derive from the repos' public README/CLAUDE docs conceptually; do NOT paste long doc bodies verbatim — short, readable sections.

Must keep (DELETE NOTHING ELSE)

• Do not touch packages/, scripts/, ci.yml, or pages.yml behavior (pages.yml already publishes the whole site/ directory).
• Keep wave-1 pages working; only additive nav edits to index.html / zh/index.html.
• English canonical; zh mirrors.

Acceptance

• scripts/run.sh test + scripts/run.sh check stay green.
• After merge to dev, the pages workflow is green and both new pages render at /architecture.html and /doctrine.html (plus /zh/ mirrors), cross-linked with the homepage in both languages.

⟦AI:FKST⟧

[loning]

github-devloop intake decision: enable

Reason:
Additive static-site implementation request with tests/checks; no credentials, production operation, destructive action, or human approval required.

[loning]

github-devloop thinking: consensus started

[loning]

github-devloop decision: approve
三方裁决: minimal=approve structural=approve delete=approve

minimal:
Scope is additive and tightly bounded to four static content pages plus homepage nav, with explicit constraints against touching package, script, or workflow behavior; acceptance is concrete enough via existing test/check commands and Pages render paths.

structural:
The proposal preserves clean boundaries: it is additive static-site content only, keeps package/script/CI behavior untouched, uses existing site conventions and bilingual mirrors, treats source documents as conceptual inputs rather than copied contracts, and reinforces reliable data-flow doctrine around source_ref payloads without changing engine or package contracts.

delete:
Additive static content is justified here: two focused documentation pages and homepage nav links improve the official site without touching package, script, CI, or publish behavior; the scope is narrow, no new framework or JS is introduced, and the acceptance checks constrain the change enough for the delete-biased angle to approve.

⟦AI:FKST⟧

[loning]

github-devloop implementation started

Worktree: /tmp/website-sv-rt.luo98t/worktrees/devloop-ChronoAIProject-fkst-website-8-2322936737
Branch: devloop/issue/ChronoAIProject/fkst-website/8/ready-consensus-github-devloop-issue-ChronoAIProject-fkst-website-8-2026-06-10T07-30-11Z-2322936737
Head: 8741d0c
Base branch: integration
Base head: 84125cb

[loning]

github-devloop PR opened: #9