docs: show the autonomous target SoC on the homepage

[WJiangH]

The homepage now presents the complete intended autonomous SoC, backed by the architecture-owned target contract and ADR0006. It shows ROM boot and a separate core-startup control path, real external Flash, core/memory/fabric/peripheral/test blocks, and complete stories260K FP32 execution at a 40-token runtime context. Implementation status is separate from the target architecture.

Deliverable manifest

Role: orchestrator, assigned framework documentation author
Work item: TARGET-SOC-HOMEPAGE; replace the current integration snapshot with the defined target chip
Delivery state: MERGED; scoped target-homepage delivery complete
Runtime requested: not specified
Runtime observed: UNKNOWN / none / UNKNOWN
Provenance: 4f41f1a929848c59cd61e8bcbfe7f55a3a84f6aa is the final head; both outgoing commits pass registered attribution range validation (2/2)
Platform publisher: github.com/WJiangH, account 45132014; authenticated publisher verified
CI state: PR boundaries / framework / gates PASS (34623760446); main framework / gates / source delivery SUCCESS (34624655486), with push boundaries skipped as configured.

Artifacts:

• README.md: complete target, autonomous operation, workload/context scope and canonical engineering links.
• docs/images/chip-architecture.svg: complete chip/board boundary, target blocks, AXI data paths, distinct subordinate boot-control path and explicit workload.

Applicable checks:

• python3 scripts/check_docs.py: PASS (77 documents, 130 local links, 0 errors).
• git diff --cached --check: PASS.
• bash flow/check_boundaries.sh 38560c96651ee90cb91269aad0a1eba162ac6aa8 docs/target-soc-home: boundary check OK; prefix has no automated role restriction, so the exact two-file documentation scope was manually audited.
• python3 scripts/agent_attribution.py validate-commit --commit HEAD: PASS at 4f41f1a929848c59cd61e8bcbfe7f55a3a84f6aa.
• XML parse, title/description and no external resource/script inspection: PASS.
• rsvg-convert at 1200 and 420 pixels: PASS; both target layout sizes inspected, with exact final desktop output inspected after source formatting/footer update. Small thumbnail labels need zoom; the essential workload and autonomous behavior are also in Markdown and alt text.

Not run:

• Local framework regression and hardware/software/physical execution: two-file documentation/SVG scope changes no product behavior; required repository CI passed separately.

Spec / policy refs:

• docs/spec/coralnpu_soc.md TSOC-01–11 and docs/adr/0006-autonomous-small-model-soc.md, introduced by reviewed PR37.
• AGENTS.md documentation stewardship, independent review and candidate-bound integration.

Lifecycle impact:

• Presents the intended logical system. Detailed executable, numerical, physical and tapeout qualification remain open under the target spec; no implementation acceptance, waiver or inherited highmem result.

Publication audit:

• Public base: origin/main at 38560c96651ee90cb91269aad0a1eba162ac6aa8 (merged target contract PR37).
• Entire outgoing ancestry: two scoped commits, 708fbaecf0839b18498da53da72728d3df2508a6 and 4f41f1a929848c59cd61e8bcbfe7f55a3a84f6aa.
• Aggregate diff: only README and the existing chip SVG; no spec/product changes, private design records, model bytes or unrelated artifacts.

Independent review:

• Target architecture and earlier diagram semantics were independently checked; two diagram findings were fixed before this final candidate. Initial public review found stale accessible title/description; corrected on the same branch in 4f41f1a929848c59cd61e8bcbfe7f55a3a84f6aa. Visible layout is unchanged: both rerendered PNGs are byte-identical. Independent corrected-head APPROVE at 4f41f1a929848c59cd61e8bcbfe7f55a3a84f6aa resolves HOME-ACCESSIBILITY-01 with no remaining findings. Reproduced docs77/130/0, attribution2/2, XML, aggregate whitespace and fresh1200/420 renders; all required checks passed. This is a substantive review comment from a separate agent context, with shared publisher/filesystem and convention-only isolation; not a GitHub review-state event.

Integration / retirement:

• Existing scoped maintainer authority covers normal integration after exact-head substantive approval and required checks; root owns this author delivery and cleanup.
• Normal exact-head merge completed as 07f040055385f382ba780d7cd647167e632593ff at 2026-09-11T16:54:15Z. Verified expected parents and identical reviewed-source/merge trees; local main fast-forwarded with unrelated untracked files preserved. Source/review evidence worktrees and local branch retained; author worktree clean, remote feature branch absent (deletion actor unknown). No active author/reviewer jobs; main CI completed. Root owns final record synchronization and retained evidence.

Open items:

• None for this documentation delivery. The separately scoped implementation and physical obligations in the target contract remain open.

Friction: Previous review checked current-state accuracy but missed the requested target-system view; acceptance now starts with the intended chip and end-to-end autonomous operation.
Skill candidates: none.

[claude]

Integrator review — no merge.

Reviewed head: 708fbaecf0839b18498da53da72728d3df2508a6 (matches live PR head).

Current state blocks merge, no product findings raised:

• PR is Draft (isDraft: true, mergeStateStatus: BLOCKED).
• Required checks (gh pr checks 38 --required): boundaries pass, framework pass, gates pending.

Spot-checks performed while waiting (informational, not a verdict):

• Boundary: diff touches only README.md and docs/images/chip-architecture.svg — homepage navigation/presentation, consistent with the orchestrator's documentation-stewardship scope in AGENTS.md; no docs/spec/ or docs/adr/ edits.
• Gate integrity: no changes to flow/gates.mk, .sdc, or test thresholds.
• Manifest cites docs/spec/coralnpu_soc.md (TSOC-01–11) and docs/adr/0006-autonomous-small-model-soc.md from merged PR Define the autonomous small-model CoralNPU target SoC #37 as the basis for the presented target architecture; not independently re-verified against spec text in this pass since merge is not on the table yet.

Per protocol, exiting without merging and without a background watch. Re-review will trigger automatically once the PR is marked Ready and gates completes as a required-check success on this same head.

[WJiangH]

Independent integrator verdict: REQUEST CHANGES at 708fbaecf0839b18498da53da72728d3df2508a6, limited to one presentation-status inconsistency.

1. HOME-ACCESSIBILITY-01 — synchronize the SVG accessible status. SVG lines 2–3 still name a “proposal” and say “pending independent review,” while the visible footer and merged canonical target identify a logical target baseline with implementation/physical qualification separately open. Update the title/description to that same status. This is not a request to claim implementation readiness.

The rest of the complete two-file/one-commit review is clean: the homepage now answers the target-chip objective, including autonomous ROM startup, real NOR, on-chip model/text processing, bounded stories260K FP32 context and separate boot-control path. Canonical source hashes and actual manifest match. Independently reproduced docs 77 documents / 130 links / 0 errors, attribution 1/1, aggregate whitespace checks and 1200/420 px SVG renders; both match the author previews and have no clipping/overlap. Narrow detail requires zoom. Actual PR readback showed boundaries/framework/gates SUCCESS; automated review was running with no posted verdict then. These results do not override the finding above.

The active original author has accepted this finding and is preparing a correction on this same PR. Final approval will bind the corrected head. No DUT or product tests were run, and no implementation acceptance is transferred.

This is a substantive review comment, not a GitHub review-state event. Reviewer and author use separate assigned agent contexts with shared publisher WJiangH and filesystem; isolation is convention-only. Observed runtime identity is UNKNOWN; no runtime attestation is claimed.

[claude]

Integrator review — no merge.

Reviewed head: 4f41f1a929848c59cd61e8bcbfe7f55a3a84f6aa (matches live PR head).

Current state blocks merge, no new product findings raised:

• PR is Draft (isDraft: true, mergeStateStatus: BLOCKED).
• Required checks (gh pr checks 38 --required): boundaries pass, framework pass, gates pending.

Spot-check: the fix commit 4f41f1a ("docs: align accessible text with the target architecture") touches only docs/images/chip-architecture.svg and resolves the prior HOME-ACCESSIBILITY-01 finding (the SVG <title>/<desc> no longer say "proposal"/"pending independent review"; both now read "Target architecture ... implementation and physical qualification are tracked separately," consistent with the footer and the merged canonical spec status). Boundary and gate-integrity spot-checks unchanged from the prior pass: diff stays within README.md and docs/images/chip-architecture.svg (documentation-stewardship scope), no flow/gates.mk/.sdc/threshold edits.

Per protocol, exiting without merging and without a background watch. Re-review will trigger automatically once the PR is marked Ready and gates completes as a required-check success on this same head.

[WJiangH]

Independent integrator re-review: APPROVE the corrected homepage at 4f41f1a929848c59cd61e8bcbfe7f55a3a84f6aa.

HOME-ACCESSIBILITY-01 is resolved. The SVG title/description now identify the logical target architecture and retain the separate implementation/physical-qualification boundary. Only those two XML text nodes changed in the fix; all geometry, visible content and README bytes remain unchanged.

I checked the complete two-file/two-commit ancestry against 38560c96651ee90cb91269aad0a1eba162ac6aa8, the actual PR head and manifest, and the unchanged canonical target contract. The homepage answers the intended autonomous-chip goal: ROM startup and distinct subordinate boot-control path, physical NOR, on-chip tokenization/full inference/output, and the complete stories260K FP32 / 40-token runtime scope. It does not substitute a current simulation setup for the target or claim implementation acceptance.

Independent checks: docs PASS (77 documents, 130 local links, 0 errors); attribution range 2 scanned / 2 validated; aggregate whitespace PASS; XML comparison PASS; freshly rendered 1200/420 px PNGs are byte-identical to the previously visually inspected homepage renders. Actual required checks boundaries, framework and gates all PASS in run 34623760446. The latest bot comment is a status/spot-check report with no new finding; its earlier pending-check state is superseded by this live readback. Bot job success is not this substantive approval.

Final file SHA-256:

• README.md: b0bb61284ccda19592a2b318f00f6e7ed846bdef0d37a6e36b2551712b78ee2f
• docs/images/chip-architecture.svg: 2f5efdb5166cab646874d85121a915f718097c9ab5220f9d4aea51ec3c4d521f

No source finding remains. Author final manifest-status synchronization and authorized integration remain; no DUT or product tests were rerun. This is a substantive approval comment, not a GitHub APPROVED event. Separate assigned author/reviewer contexts share publisher WJiangH and filesystem; separation is convention-only. Observed runtime identity is UNKNOWN, with no attestation. Prior request-changes evidence remains preserved.

[claude]

Integrator final verification — no merge action taken (already merged).

Reviewed head: 4f41f1a929848c59cd61e8bcbfe7f55a3a84f6aa.

State: PR #38 is already MERGED (mergedAt 2026-09-11T16:54:15Z, mergedBy WJiangH), merge commit 07f040055385f382ba780d7cd647167e632593ff, head branch deleted. 4f41f1a is a verified ancestor of the merge commit and matches this review's reviewed-head pin exactly — integration happened on the intended candidate, not a stale one.

Independent spot-checks performed on this exact head (not just re-reading the manifest):

• Boundary: diff is limited to README.md and docs/images/chip-architecture.svg across both commits (git diff 38560c96..4f41f1a --stat). No docs/spec/, docs/adr/, or product-code paths touched — within the orchestrator's documentation-stewardship scope (AGENTS.md), not chief-architect's spec/ADR ownership.
• Gate integrity: no changes to flow/gates.mk, .sdc, or any threshold/test.
• Spec conformance (independently read, not manifest-trusted): docs/spec/coralnpu_soc.md §1/§TSOC-01 confirms complete FP32 stories260K anchor, 40-token runtime capacity (≤32 input + 8 generated), 8 KiB ITCM/32 KiB DTCM, 16 KiB boot ROM, 64 KiB working SRAM, 4 MiB SPI NOR, and a separate boot-sequencer→subordinate-CSR startup path — matches the README prose and the SVG block diagram/labels claim-for-claim. "Logical target architecture; implementation and physical qualification are tracked separately" mirrors spec §1's LOGICAL_TARGET_BASELINE ... OPEN status.
• Review resolution: HOME-ACCESSIBILITY-01 (stale "proposal"/"pending independent review" SVG a11y text) was raised and fixed in 4f41f1a; independent re-review approved that exact head. No open findings remain.
• Required checks on this head: boundaries pass, framework pass, gates pass (run 34623760446).

Nothing further to do here; recording this as the closing verification of the review thread.