# DLRP.ca v201.x Human-Counterpart Review Questions

**Prepared from:** `v200.8-complete`  
**Repository head at handoff:** `2b61323802bdf39a0a58757f60db7ce45290c085`  
**Architecture-source commit:** `9c29f55e2aea317fcb1953576fd27892d54cac5e`  
**Status:** Unreviewed Human-Counterpart checklist  

This document is a review instrument, not public canon. Each item should receive one disposition: **confirm**, **revise**, **remove**, or **defer**. A confirmed answer becomes eligible for v201.x implementation only after the affected documentation layer is identified.

Priority key: **P0** blocks trustworthy approval, **P1** should be decided during v201.x, and **P2** is a polish or policy decision that may be deferred deliberately.

**Total questions:** 191

## Release acceptance and review authority

Defines what Human-Counterpart approval means before v201.x edits begin.

1. **[P0] Does v200.8 accurately represent the final pre-review website baseline?**
   - **Current state:** The package is labelled as the final v200.x review build.
   - **What must be confirmed:** Confirm that no missing v200.x structural pass should occur first.
   - **Recommended action:** Accept v200.8 as the frozen review baseline or list blocking corrections.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

2. **[P0] Who may approve changes during v201.x?**
   - **Current state:** Dylan is recorded as Human-Counterpart and current canon authority.
   - **What must be confirmed:** Confirm whether any other person may approve public biography, privacy, or project claims.
   - **Recommended action:** Name the approval authority and any advisory reviewers.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

3. **[P0] Should Human-Counterpart approval be recorded page by page or as one release decision?**
   - **Current state:** No formal review workflow is yet locked.
   - **What must be confirmed:** Choose the acceptance granularity.
   - **Recommended action:** Use the machine checklist to record per-item dispositions and a final release sign-off.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

4. **[P0] What counts as accepted, corrected, removed, or deferred?**
   - **Current state:** The review packet offers these four outcomes.
   - **What must be confirmed:** Confirm the disposition vocabulary.
   - **Recommended action:** Lock a small status set before editing begins.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

5. **[P1] Should v201.x preserve a visible review history?**
   - **Current state:** v200.x preserves release audits but not Human-Counterpart decisions.
   - **What must be confirmed:** Confirm whether decisions should be logged publicly, privately, or both.
   - **Recommended action:** Create a review decision log with privacy-safe summaries.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

6. **[P1] Which files become authoritative after review?**
   - **Current state:** Website, README, master plan, and runtime remain distinct layers.
   - **What must be confirmed:** Confirm the post-review source priority.
   - **Recommended action:** Publish a short source hierarchy in v201.x release records.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

7. **[P1] Should v200.8 remain downloadable after v201.x?**
   - **Current state:** v200.x is continuity lineage.
   - **What must be confirmed:** Confirm archive retention and public visibility.
   - **Recommended action:** Keep one checksummed v200.8 archive unless privacy review requires removal.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

8. **[P1] Is v201.0 the first approved public release or only the first review pass?**
   - **Current state:** The next series is described as a Human-Counterpart review.
   - **What must be confirmed:** Confirm whether approval happens at v201.0 or later in v201.x.
   - **Recommended action:** Define the review-series release gate.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

9. **[P2] Should the public site display its review state?**
   - **Current state:** v200.8 shows a review-build marker.
   - **What must be confirmed:** Confirm whether v201.x should display approved, in-review, or draft status.
   - **Recommended action:** Use one consistent public review badge or remove it after approval.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

10. **[P2] Should release reports remain web-accessible on the deployed host?**
   - **Current state:** Reports are packaged but not indexed.
   - **What must be confirmed:** Confirm whether they are public artifacts or deployment-only records.
   - **Recommended action:** Move non-public reports outside the deploy root if necessary.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

## Homepage and first-visit navigation

Reviews the v200.7 splash retained by v200.8.

11. **[P0] Does the homepage explain DLRP.ca clearly to a first-time visitor?**
   - **Current state:** It calls the site a public workbench for Huey, the project, builds, records, and sources.
   - **What must be confirmed:** Confirm the wording, emphasis, and reading level.
   - **Recommended action:** Edit the opening only after a first-time-reader test.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

12. **[P0] Are the four first-screen paths the correct priorities?**
   - **Current state:** Meet Huey, understand the project, see the builds, and verify the record are primary.
   - **What must be confirmed:** Confirm whether About, Gallery, or another route should replace any card.
   - **Recommended action:** Keep four paths unless a clear visitor task is missing.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

13. **[P0] Is “Meet Huey” the right public invitation while Huey remains incomplete?**
   - **Current state:** The wording is approachable but may imply operational presence.
   - **What must be confirmed:** Confirm the intended degree of personification.
   - **Recommended action:** Retain, soften, or replace with “Understand Huey.”
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

14. **[P1] Does “Understand the project” correctly describe Monkey-Head-Project?**
   - **Current state:** It leads to the umbrella and collective explanation.
   - **What must be confirmed:** Confirm the label and whether the full project name should be visible.
   - **Recommended action:** Use the shortest accurate label that preserves identity.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

15. **[P1] Does “See the builds” give enough prominence to non-Huey work?**
   - **Current state:** Projects leads with Huey V4 and retains pinball and console records.
   - **What must be confirmed:** Confirm the balance.
   - **Recommended action:** Adjust card copy, not the route structure, unless needed.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

16. **[P1] Is “Verify the record” understandable to a general visitor?**
   - **Current state:** It links to the Repository Ledger.
   - **What must be confirmed:** Confirm whether “Check the sources” is clearer.
   - **Recommended action:** Test both labels with a non-project reader.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

17. **[P1] Are Search, Map, and About visible enough on desktop and mobile?**
   - **Current state:** They are secondary utility controls in the splash.
   - **What must be confirmed:** Confirm discoverability.
   - **Recommended action:** Increase contrast or position only if observed users miss them.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

18. **[P1] Are the five browse lanes correctly named?**
   - **Current state:** System, Lab, Records, Documents, and Human are used.
   - **What must be confirmed:** Confirm “Human” and “Records” in particular.
   - **Recommended action:** Rename consistently across homepage, rail, map, and search labels.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

19. **[P1] Should Documents appear before Human everywhere?**
   - **Current state:** v200.8 standardizes this order.
   - **What must be confirmed:** Confirm this information hierarchy.
   - **Recommended action:** Keep one order across every navigation surface.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

20. **[P1] Does the permanent car-in-field hero still represent the site?**
   - **Current state:** It remains the homepage anchor by explicit preference.
   - **What must be confirmed:** Confirm the image, crop, overlay, and privacy/public-fit.
   - **Recommended action:** Approve the current derivative and preserve the original master separately.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

21. **[P2] Is the first viewport too dense on smaller phones?**
   - **Current state:** The mobile layout is a single stack.
   - **What must be confirmed:** Confirm on the devices Dylan actually uses.
   - **Recommended action:** Test at 320, 360, 390, and 430 CSS pixels.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

22. **[P2] Should the homepage show the current repository and review state?**
   - **Current state:** It shows concise source status.
   - **What must be confirmed:** Confirm whether that is useful to ordinary visitors.
   - **Recommended action:** Keep detailed source status in the ledger if the homepage feels technical.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

23. **[P2] Is the current Huey V4 feature the correct below-fold emphasis?**
   - **Current state:** V4 is the current accepted direction, not a completed build.
   - **What must be confirmed:** Confirm its public priority and wording.
   - **Recommended action:** Retain only if physical embodiment remains the active focus.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

24. **[P2] Are the lower-page images the right continuity cross-section?**
   - **Current state:** The strip uses a small deliberate set.
   - **What must be confirmed:** Confirm that each image earns its place.
   - **Recommended action:** Replace rather than expand if a stronger record exists.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

## Route taxonomy and information architecture

Confirms the 40-route structure before editorial work.

25. **[P0] Are all 40 registered routes still wanted in the public site?**
   - **Current state:** v200.8 preserves 29 indexed and 11 noindex routes.
   - **What must be confirmed:** Confirm keep, merge, redirect, archive, or remove for every route.
   - **Recommended action:** Use the page-review matrix before changing navigation.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

26. **[P0] Should the 11 historical research routes remain individually accessible?**
   - **Current state:** They are noindex and labelled as historical speculative notes.
   - **What must be confirmed:** Confirm public value and risk.
   - **Recommended action:** Retain only those with clear lineage value and suitable warnings.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

27. **[P1] Is “Source Map” the clearest name for the documentation-layer page?**
   - **Current state:** It explains source hierarchy and provenance.
   - **What must be confirmed:** Confirm whether “Documentation Map” is clearer.
   - **Recommended action:** Rename route title only if all references are updated together.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

28. **[P1] Should Repository Ledger remain a top-level public route?**
   - **Current state:** It exposes source files, drift, and repository state.
   - **What must be confirmed:** Confirm audience and transparency goals.
   - **Recommended action:** Keep public if transparency outweighs complexity.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

29. **[P1] Should Visual Atlas remain separate from Gallery?**
   - **Current state:** Atlas is structured/filterable; Gallery is editorial.
   - **What must be confirmed:** Confirm the distinction is meaningful to visitors.
   - **Recommended action:** Merge only if the roles cannot be explained clearly.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

30. **[P1] Should Media remain a public route?**
   - **Current state:** It contains outward-facing coverage and links.
   - **What must be confirmed:** Confirm whether current content is substantial and current.
   - **Recommended action:** Refresh, merge, or archive based on actual material.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

31. **[P1] Should Downloads expose release and machine-readable files?**
   - **Current state:** It currently acts as a release shelf.
   - **What must be confirmed:** Confirm which technical files are appropriate for public use.
   - **Recommended action:** Separate visitor downloads from maintainer artifacts if needed.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

32. **[P1] Is the Draft Constitution route correctly placed under Documents?**
   - **Current state:** It is an unratified historical archive.
   - **What must be confirmed:** Confirm public context and naming.
   - **Recommended action:** Keep “draft” and “unratified” visible everywhere.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

33. **[P1] Should Linux 7.0 remain a public Lab route?**
   - **Current state:** It is an end-of-life experiment archive.
   - **What must be confirmed:** Confirm archival value.
   - **Recommended action:** Retain with clear EOL status or move to a deeper archive.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

34. **[P2] Are route codes useful to public visitors?**
   - **Current state:** Codes support search, maps, and continuity.
   - **What must be confirmed:** Confirm whether they aid or distract.
   - **Recommended action:** Keep in secondary UI even if removed from primary copy.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

35. **[P2] Are route titles, breadcrumbs, and rail labels consistent?**
   - **Current state:** v200.8 standardizes mechanics, but Human review must confirm wording.
   - **What must be confirmed:** Review each route title and label as a set.
   - **Recommended action:** Record exact approved label per route.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

36. **[P2] Should old URLs receive redirects if routes are renamed or removed?**
   - **Current state:** The current static package preserves canonical paths.
   - **What must be confirmed:** Confirm redirect capability on the host.
   - **Recommended action:** Create static redirect pages or server rules before changing URLs.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

## Huey node and Monkey-Head-Project ontology

Confirms the central public architecture before it is treated as approved.

37. **[P0] Is Huey correctly defined as one embodied AI node?**
   - **Current state:** The website candidate uses this as its primary model.
   - **What must be confirmed:** Confirm the definition and exact wording.
   - **Recommended action:** Approve, revise, or defer before synchronizing README/master plan.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

38. **[P0] Is a node correctly defined as the physical embodiment of one AI unit?**
   - **Current state:** This is the v121.0 candidate definition.
   - **What must be confirmed:** Confirm whether software, memory, authority, or continuity criteria must be included.
   - **Recommended action:** Write one canonical node definition.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

39. **[P0] Is Monkey-Head-Project correctly defined as umbrella and eventual collective?**
   - **Current state:** The website places it above one or more valid nodes.
   - **What must be confirmed:** Confirm current and target roles.
   - **Recommended action:** Separate present umbrella from future collective in approved wording.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

40. **[P0] Does the site overstate the current existence of a collective?**
   - **Current state:** The site says collective later and labels it target state.
   - **What must be confirmed:** Confirm no page implies operational federation.
   - **Recommended action:** Correct any phrase that treats multiple nodes or governance as active.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

41. **[P0] Are Brain and Body properly re-scoped as node-local domains?**
   - **Current state:** They remain useful internal divisions in the candidate.
   - **What must be confirmed:** Confirm whether “domain,” “subsystem,” or another term is preferred.
   - **Recommended action:** Use one term consistently.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

42. **[P0] Is Farm correctly moved to optional collective-level infrastructure?**
   - **Current state:** The candidate no longer makes Farm constitutive of one Huey.
   - **What must be confirmed:** Confirm whether Farm remains a valid term and what it includes.
   - **Recommended action:** Approve a bounded Farm definition or mark it unresolved.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

43. **[P0] Does Huey identity belong to the whole physical node?**
   - **Current state:** The candidate points that way while internal authority remains open.
   - **What must be confirmed:** Confirm what is decided versus unresolved.
   - **Recommended action:** Avoid stronger identity claims than Dylan accepts.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

44. **[P0] Can one valid Huey node exist without Farm or collective membership?**
   - **Current state:** The candidate says yes.
   - **What must be confirmed:** Confirm this node-validity rule.
   - **Recommended action:** Lock it if accepted; otherwise state required dependencies.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

45. **[P1] What distinguishes Huey from HueyOS?**
   - **Current state:** Huey is the identity/node; HueyOS is the software/runtime layer.
   - **What must be confirmed:** Confirm the public distinction.
   - **Recommended action:** Use a short side-by-side definition on Huey and project pages.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

46. **[P1] What distinguishes Huey from the physical shell?**
   - **Current state:** The node includes more than the shell, while embodiment is essential.
   - **What must be confirmed:** Confirm the boundary.
   - **Recommended action:** Avoid using shell, Body, node, and Huey interchangeably.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

47. **[P1] What distinguishes Huey from PyHuey?**
   - **Current state:** PyHuey is the primary GUI and runtime direction, not the entire node.
   - **What must be confirmed:** Confirm current role.
   - **Recommended action:** Keep PyHuey subordinate to the node definition.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

48. **[P1] What distinguishes Huey from LabTech?**
   - **Current state:** LabTech supports, accesses, and recovers Huey but is outside its sovereignty.
   - **What must be confirmed:** Confirm current devices and exceptions.
   - **Recommended action:** Review every device classification.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

49. **[P1] Should the term “Huey proper” remain on the public site?**
   - **Current state:** It appears in lineage and target-state language.
   - **What must be confirmed:** Confirm whether it clarifies or confuses.
   - **Recommended action:** Define once or remove from public copy.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

50. **[P1] Is “one real node first” the correct public summary?**
   - **Current state:** It is the current cross-site phrase.
   - **What must be confirmed:** Confirm tone and technical accuracy.
   - **Recommended action:** Approve as a slogan or replace with a less slogan-like statement.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

51. **[P1] How should exact bifurcation be described?**
   - **Current state:** It is a future lineage/replication concept above node validity.
   - **What must be confirmed:** Confirm identity and authority non-claims.
   - **Recommended action:** Approve a precise non-operational definition.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

52. **[P1] How should augmented bifurcation be described?**
   - **Current state:** It is a future specialization/divergence concept.
   - **What must be confirmed:** Confirm what changes are intentional and who authorizes them.
   - **Recommended action:** Keep unresolved consequences explicit.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

53. **[P1] Should bifurcation remain visible on the main project page?**
   - **Current state:** It is secondary future architecture.
   - **What must be confirmed:** Confirm public relevance.
   - **Recommended action:** Keep concise and link to noindex lineage if approved.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

54. **[P2] Does the node/collective diagram accurately show authority and service relationships?**
   - **Current state:** The current diagram is explanatory, not runtime truth.
   - **What must be confirmed:** Confirm every arrow and label.
   - **Recommended action:** Revise the diagram only after the definitions are approved.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

55. **[P2] Should organism, nation, or federation metaphors be used publicly?**
   - **Current state:** Historical materials contain these metaphors.
   - **What must be confirmed:** Confirm where they aid understanding and where they overclaim.
   - **Recommended action:** Use metaphors only with explicit non-literal framing.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

56. **[P2] Does the site clearly separate node validity, V1, and full target state?**
   - **Current state:** They are separate but related concepts.
   - **What must be confirmed:** Confirm acceptance criteria for each.
   - **Recommended action:** Create a three-column public status table if useful.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

## Huey V4 physical embodiment and hardware

Requires direct Human-Counterpart confirmation because many details are lab-specific or provisional.

57. **[P0] Is V3 the correct physical base identity for Huey V4?**
   - **Current state:** The candidate says V3 is the base shell/body.
   - **What must be confirmed:** Confirm the version naming and physical continuity.
   - **Recommended action:** Approve a version-lineage statement.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

58. **[P0] Is V2 the correct donor designation?**
   - **Current state:** The candidate says V2 supplies salvageable material.
   - **What must be confirmed:** Confirm which physical parts and records are V2.
   - **Recommended action:** Create a donor inventory before public specificity.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

59. **[P0] Which shell components physically exist today?**
   - **Current state:** The site names the modified shell, mounted head, right hand, and fold-out surface.
   - **What must be confirmed:** Confirm each observation and current condition.
   - **Recommended action:** Photograph and inventory the current state.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

60. **[P0] Is the monkey head structurally mounted, operational, symbolic, or all three?**
   - **Current state:** The site treats it as mounted and identity-central.
   - **What must be confirmed:** Confirm mechanical and functional status.
   - **Recommended action:** Use separate labels for presence and actuation capability.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

61. **[P0] Is the right hand physically mounted and what is its intended role?**
   - **Current state:** The site reports a mounted right hand without claiming actuation.
   - **What must be confirmed:** Confirm purpose and status.
   - **Recommended action:** Update captions and V4 plan.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

62. **[P0] What exactly is the fold-out interaction surface?**
   - **Current state:** It exists but requires refinement.
   - **What must be confirmed:** Confirm display, input, hinge, locking, reach, and cabling roles.
   - **Recommended action:** Document with measurements and photographs.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

63. **[P0] Is the current i9/TUF/Optane machine still the intended V4 kernel?**
   - **Current state:** The v121.0 candidate says yes.
   - **What must be confirmed:** Confirm current hardware and migration intent.
   - **Recommended action:** Reinventory before any public hardware table is approved.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

64. **[P0] Which Intel CPU is actually installed in the current kernel?**
   - **Current state:** Repository v120.3 says i9-12900K; older notes mention i9-14900K and other systems.
   - **What must be confirmed:** Confirm by direct system inventory.
   - **Recommended action:** Publish only the observed CPU model.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

65. **[P0] Which ASUS TUF motherboard is actually installed?**
   - **Current state:** Current documents and older memories may disagree.
   - **What must be confirmed:** Confirm exact model and revision.
   - **Recommended action:** Record board model, BIOS, and photographs.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

66. **[P0] What is the current Optane/storage configuration?**
   - **Current state:** The candidate references an Optane kernel; historical records contain multiple layouts.
   - **What must be confirmed:** Confirm devices, RAID level, health, and role.
   - **Recommended action:** Generate a current storage inventory.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

67. **[P0] Is a four-GPU layout still the active working direction?**
   - **Current state:** The candidate says yes but remains provisional.
   - **What must be confirmed:** Confirm target count.
   - **Recommended action:** Keep provisional until fit, lanes, power, and cooling are measured.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

68. **[P0] Is 3 × Tesla V100 32 GB plus one utility GPU still the strongest candidate?**
   - **Current state:** This is the website candidate, not an installed fact.
   - **What must be confirmed:** Confirm current procurement thinking.
   - **Recommended action:** Update or remove before public approval if no longer current.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

69. **[P0] Have any V100 cards been acquired, reserved, or tested?**
   - **Current state:** The site does not claim acquisition.
   - **What must be confirmed:** Confirm actual status.
   - **Recommended action:** Add evidence or retain “candidate only.”
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

70. **[P0] Which V100 form factor is under consideration?**
   - **Current state:** PCIe versus SXM affects feasibility.
   - **What must be confirmed:** Confirm exact variant.
   - **Recommended action:** Do not publish compatibility claims without the variant.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

71. **[P0] What is the existing utility GPU?**
   - **Current state:** Older records mention RX 5500 XT 8 GB.
   - **What must be confirmed:** Confirm actual current device and role.
   - **Recommended action:** Inventory by PCI ID and photograph.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

72. **[P0] Can the motherboard expose the required lanes and slots?**
   - **Current state:** Feasibility is unresolved.
   - **What must be confirmed:** Confirm physical and electrical topology.
   - **Recommended action:** Produce a lane map before procurement.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

73. **[P0] What power architecture is intended?**
   - **Current state:** Historical notes range from multiple PSUs to unresolved placement.
   - **What must be confirmed:** Confirm PSU count, ratings, synchronization, grounding, and protection.
   - **Recommended action:** Create an electrical plan reviewed for safety.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

74. **[P0] What cooling strategy is physically feasible?**
   - **Current state:** No installed multi-GPU cooling solution is claimed.
   - **What must be confirmed:** Confirm airflow, heat load, enclosure, and noise constraints.
   - **Recommended action:** Measure and prototype before approval.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

75. **[P0] What safe shutdown and emergency-stop behavior is required?**
   - **Current state:** Safety is a project requirement, not a proven implementation.
   - **What must be confirmed:** Confirm hardware and software expectations.
   - **Recommended action:** Document fail-safe behavior before integration.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

76. **[P1] What is HueyPulse’s current status?**
   - **Current state:** It appears in historical planning but is not active canon in v200.8.
   - **What must be confirmed:** Confirm active, deferred, replaced, or retired.
   - **Recommended action:** Classify explicitly in v201.x.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

77. **[P1] What role should Arduino, Raspberry Pi, or another controller play?**
   - **Current state:** Historical plans vary.
   - **What must be confirmed:** Confirm current low-level control direction.
   - **Recommended action:** Avoid naming a board until selected.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

78. **[P1] What sensors, lights, fans, batteries, screens, and switches are presently installed?**
   - **Current state:** Older records contain detailed but potentially stale inventories.
   - **What must be confirmed:** Confirm each through a current physical audit.
   - **Recommended action:** Publish a dated hardware manifest.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

79. **[P1] What distinguishes assembled, integrated, operational, validated, and complete?**
   - **Current state:** No final V4 acceptance taxonomy is locked.
   - **What must be confirmed:** Confirm evidence thresholds.
   - **Recommended action:** Add status definitions to the V4 plan.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

80. **[P1] What baseline must be captured before moving the current compute kernel?**
   - **Current state:** The candidate calls for inventory, backup, thermals, and rollback.
   - **What must be confirmed:** Confirm the complete checklist.
   - **Recommended action:** Do not disassemble until the gate is signed off.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

81. **[P2] Should detailed hardware specifications be public?**
   - **Current state:** Transparency helps replication but may expose private or unsafe details.
   - **What must be confirmed:** Confirm desired disclosure level.
   - **Recommended action:** Publish only what supports the project’s public mission safely.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

## Software, runtime, V1, and evidence

Confirms what is implemented versus merely selected.

82. **[P0] What recurring useful function will define V1?**
   - **Current state:** V1 remains intentionally open.
   - **What must be confirmed:** Confirm the problem, user, context, and evidence threshold.
   - **Recommended action:** Do not declare V1 until the function is repeatable.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

83. **[P0] Is the MP3-to-log path still the active foundation proof?**
   - **Current state:** The repository retains it as foundation evidence.
   - **What must be confirmed:** Confirm current status and whether it has been run successfully.
   - **Recommended action:** Record a dated run or classify it as pending.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

84. **[P0] Which transcription engine and model are current?**
   - **Current state:** faster-whisper is the working direction; model and compute path remain open.
   - **What must be confirmed:** Confirm exact engine, model, compute type, and fallback.
   - **Recommended action:** Publish measured settings, not assumptions.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

85. **[P0] Is CPU-first transcription still the practical assignment?**
   - **Current state:** The v121.0 candidate says yes pending measurement.
   - **What must be confirmed:** Confirm on current hardware.
   - **Recommended action:** Benchmark and record results.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

86. **[P0] Which cognition provider or local model is currently used?**
   - **Current state:** The architecture is provider-swappable and does not lock one provider.
   - **What must be confirmed:** Confirm actual current path and public disclosure.
   - **Recommended action:** Separate current provider from architectural dependency.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

87. **[P0] Has a real provider run been completed through the proof loop?**
   - **Current state:** The retained runbook does not establish one.
   - **What must be confirmed:** Confirm evidence.
   - **Recommended action:** Link a redacted structured log or keep the non-claim.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

88. **[P0] What logs are currently produced?**
   - **Current state:** Repository code supports structured JSON/JSONL and optional shadow traces.
   - **What must be confirmed:** Confirm fields, storage location, and secret handling.
   - **Recommended action:** Review a real redacted sample.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

89. **[P0] Is HIMS an implemented runtime, a shadow trace, a foundation, or doctrine?**
   - **Current state:** The site says foundation/non-controlling; repository contains shadow implementation.
   - **What must be confirmed:** Confirm the approved wording.
   - **Recommended action:** Use one status across all pages.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

90. **[P0] What is PyHuey’s current working state?**
   - **Current state:** Repository direction calls it primary GUI/core runtime, with consolidation incomplete.
   - **What must be confirmed:** Confirm what launches and what workflows function.
   - **Recommended action:** Publish a capability table with evidence.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

91. **[P0] What CLI recovery functions are required?**
   - **Current state:** The project intends a recovery-capable CLI.
   - **What must be confirmed:** Confirm commands and acceptance tests.
   - **Recommended action:** Document only implemented commands.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

92. **[P1] Is the current Python support window still >=3.13,<3.14?**
   - **Current state:** Current pyproject retains that contract.
   - **What must be confirmed:** Confirm whether v201.x should repeat it publicly.
   - **Recommended action:** Update from repository only, not memory.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

93. **[P1] Is the distribution/import distinction still hueyos versus huey?**
   - **Current state:** Current package name is hueyos while imports remain huey.
   - **What must be confirmed:** Confirm migration status.
   - **Recommended action:** Keep the drift visible until code and docs agree.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

94. **[P1] Which operating systems are active on Huey and LabTech devices?**
   - **Current state:** Historical notes conflict across Debian, Windows, and decommissioned systems.
   - **What must be confirmed:** Confirm each device from direct observation.
   - **Recommended action:** Create a dated device-role table.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

95. **[P1] Is the Lenovo Legion Go part of Huey, LabTech, lineage, or no official role?**
   - **Current state:** Sources have changed repeatedly.
   - **What must be confirmed:** Confirm current classification.
   - **Recommended action:** Remove stale role claims across the site.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

96. **[P1] Is the ASUS FX505DT still active LabTech?**
   - **Current state:** Repository v120.3 says yes.
   - **What must be confirmed:** Confirm current hardware, OS, and role.
   - **Recommended action:** Update the public table only after confirmation.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

97. **[P1] What is the current status of the Briefcase?**
   - **Current state:** It is described as field terminal/LabTech with limited authority in different sources.
   - **What must be confirmed:** Confirm hardware, OS, and actual use.
   - **Recommended action:** Choose one current classification.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

98. **[P1] What is the current status of the 2017 iMac 5K?**
   - **Current state:** Repository v120.3 says decommissioned; older continuity notes assign active LabTech roles.
   - **What must be confirmed:** Confirm current physical and operational state.
   - **Recommended action:** Correct every public mention together.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

99. **[P1] What external-service dependency is acceptable for a valid node?**
   - **Current state:** This remains unresolved.
   - **What must be confirmed:** Confirm offline-first threshold and API fallback policy.
   - **Recommended action:** Add measurable dependency limits.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

100. **[P2] What tests are required before a software claim appears publicly?**
   - **Current state:** Unit, mocked integration, fixture fidelity, live E2E, and failure-path testing are the current baseline.
   - **What must be confirmed:** Confirm the minimum per claim type.
   - **Recommended action:** Add evidence labels to technical pages.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

101. **[P2] How should failures be presented publicly?**
   - **Current state:** Failed runs should leave attributable records.
   - **What must be confirmed:** Confirm privacy-safe reporting.
   - **Recommended action:** Publish summaries, not secret-bearing logs.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

## Repository, README, master plan, and source synchronization

Determines how the website candidate becomes or does not become repository canon.

102. **[P0] Should v121.0 remain the proposed next master-plan version?**
   - **Current state:** The candidate uses v121.0 because the top-level ontology changes.
   - **What must be confirmed:** Confirm version number.
   - **Recommended action:** Rename before repository submission if needed.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

103. **[P0] Is master-plan-v121.0 approved in substance?**
   - **Current state:** It is packaged as a candidate pending synchronization and acceptance.
   - **What must be confirmed:** Review every top-level object and non-claim.
   - **Recommended action:** Record accepted, revised, or rejected status.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

104. **[P0] Should README.md be rewritten to the node-first model?**
   - **Current state:** Repository README remains v120.3.
   - **What must be confirmed:** Confirm synchronization intent.
   - **Recommended action:** Stage a separate repository PR after Human review.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

105. **[P0] Should master-plan-v120.3.json remain immutable?**
   - **Current state:** It is the predecessor record and still self-labels proposed_in_pr.
   - **What must be confirmed:** Confirm provenance policy.
   - **Recommended action:** Leave unchanged or perform a separate metadata-only correction.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

106. **[P0] How should the stale proposed_in_pr status be handled?**
   - **Current state:** The file is merged but self-status is stale.
   - **What must be confirmed:** Confirm whether to correct or preserve.
   - **Recommended action:** Document the decision explicitly.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

107. **[P0] Is 2b613238 the correct repository head for the review package?**
   - **Current state:** It is the current head checked during v200.8 assembly.
   - **What must be confirmed:** Confirm no later commit must be incorporated before upload.
   - **Recommended action:** Refresh the snapshot if main advances before deployment.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

108. **[P1] Should dependency-only commits change the visible source chip?**
   - **Current state:** v200.8 shows current head and a separate architecture-source commit.
   - **What must be confirmed:** Confirm this two-commit model.
   - **Recommended action:** Retain if it improves truthfulness.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

109. **[P1] Are all repository source-file roles correct?**
   - **Current state:** The ledger records README, master plan, decision record, pyproject, proof loop, runtime, HIMS, PyHuey bridge, runbook, and tests.
   - **What must be confirmed:** Confirm completeness.
   - **Recommended action:** Add or remove files based on real authority.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

110. **[P1] Should repository binary identity imagery be imported into the site?**
   - **Current state:** v200.x deliberately did not bulk-import it.
   - **What must be confirmed:** Confirm visual strategy.
   - **Recommended action:** Import only if it clarifies current embodiment.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

111. **[P1] Does the Repository Ledger expose too much technical detail?**
   - **Current state:** It is transparent but dense.
   - **What must be confirmed:** Confirm public audience.
   - **Recommended action:** Keep full data downloadable and simplify the page if needed.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

112. **[P1] Should the source chip remain on every page?**
   - **Current state:** It provides ubiquitous provenance.
   - **What must be confirmed:** Confirm visual burden and usefulness.
   - **Recommended action:** Retain, reduce, or make optional based on review.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

113. **[P1] Does the six-layer truth model remain approved?**
   - **Current state:** Current reality, direction, provisional, unresolved, target, and lineage structure the site.
   - **What must be confirmed:** Confirm labels and meanings.
   - **Recommended action:** Lock the model before v201.x rewriting.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

114. **[P1] Do the four source origins remain sufficient?**
   - **Current state:** Current session, repository, lab, and lineage are used.
   - **What must be confirmed:** Confirm whether public testimony or external sources need a distinct origin.
   - **Recommended action:** Add only if it changes review decisions.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

115. **[P2] Should the website package include repository snapshots at all?**
   - **Current state:** They support offline source transparency.
   - **What must be confirmed:** Confirm size and maintenance value.
   - **Recommended action:** Keep static snapshots if the update burden is acceptable.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

116. **[P2] What happens when repository main changes during v201.x?**
   - **Current state:** No refresh cadence is defined.
   - **What must be confirmed:** Confirm snapshot timing.
   - **Recommended action:** Pin at review start and refresh once before release candidate.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

## Public identity, biography, and privacy

Protects the boundary between public biography and AI-facing continuity material.

117. **[P0] Is “Human-Counterpart” appropriate public terminology?**
   - **Current state:** The About page uses it in a bounded way.
   - **What must be confirmed:** Confirm meaning, capitalization, and audience comprehension.
   - **Recommended action:** Approve a one-sentence public definition or remove the term.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

118. **[P0] Which public role labels should appear beside Dylan’s name?**
   - **Current state:** Lab Assistant, inventor, scientist, builder, documentarian, restorer, and systems designer appear in current context.
   - **What must be confirmed:** Confirm each label.
   - **Recommended action:** Remove any title Dylan would not publicly claim.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

119. **[P0] Which biographical facts are approved for public display?**
   - **Current state:** v200.x intentionally avoids publishing the full continuity profile.
   - **What must be confirmed:** Confirm a minimal approved biography.
   - **Recommended action:** Create a public-bio source record separate from private context.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

120. **[P0] Should location, home-workspace, family, routine, or resource constraints be public?**
   - **Current state:** These details may aid context but carry privacy implications.
   - **What must be confirmed:** Confirm each category.
   - **Recommended action:** Default to omission unless it materially serves the public narrative.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

121. **[P0] Which email addresses should be public?**
   - **Current state:** The rail currently links admin@dlrp.ca.
   - **What must be confirmed:** Confirm mailbox, spam tolerance, and preferred contact path.
   - **Recommended action:** Use one monitored public address.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

122. **[P0] Are GitHub and YouTube account links correct and desired?**
   - **Current state:** The rail links to DylanLRPollock and @DLRP1995.
   - **What must be confirmed:** Confirm current handles and public intent.
   - **Recommended action:** Update or remove broken/unwanted profiles.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

123. **[P1] Should the site call Dylan the sole canon authority?**
   - **Current state:** This is current project governance, not a permanent public identity claim.
   - **What must be confirmed:** Confirm wording and scope.
   - **Recommended action:** Limit the statement to current project decisions.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

124. **[P1] Should Atlas be named publicly?**
   - **Current state:** The architecture documents clarify Atlas is external to Huey.
   - **What must be confirmed:** Confirm whether that distinction belongs on public pages or only docs.
   - **Recommended action:** Keep it where role confusion is likely.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

125. **[P1] Do the About images accurately represent Dylan and current public identity?**
   - **Current state:** The page uses selected car, portrait, dog, lab, and music context.
   - **What must be confirmed:** Confirm consent, captions, crop, and date sensitivity.
   - **Recommended action:** Approve each image individually.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

126. **[P1] Are hero.JPEG and profile.JPEG available and properly preserved?**
   - **Current state:** Earlier continuity notes request full-quality preservation, but exact filenames were not found in supplied archives.
   - **What must be confirmed:** Confirm whether the masters exist elsewhere.
   - **Recommended action:** Add to the private media warehouse before further derivatives.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

127. **[P1] Should the site disclose the project’s approximate age?**
   - **Current state:** Older records say roughly a decade.
   - **What must be confirmed:** Confirm start date or preferred wording.
   - **Recommended action:** Use a bounded phrase unless a date is documented.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

128. **[P1] Should childhood wonder, personal meaning, or emotional attachment be public?**
   - **Current state:** These motivations are important but easy to over-mythologize.
   - **What must be confirmed:** Confirm the desired level of personal voice.
   - **Recommended action:** Use first-person wording approved by Dylan.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

129. **[P2] Should the About page mention employment or organization claims?**
   - **Current state:** No verified employer/company biography should be inferred.
   - **What must be confirmed:** Confirm any professional affiliation explicitly.
   - **Recommended action:** Avoid unsupported company language.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

130. **[P2] Should personal pronouns and first-person voice increase in v201.x?**
   - **Current state:** v200.x is largely documentary and third-person.
   - **What must be confirmed:** Confirm desired voice by page type.
   - **Recommended action:** Define a voice guide before rewriting.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

## Images, assets, captions, and visual evidence

Confirms that deliberate asset placement is also factually and personally approved.

131. **[P0] Does every current-embodiment image actually show current hardware?**
   - **Current state:** v200.x uses curated Huey shell images with role labels.
   - **What must be confirmed:** Confirm image date, version, and current status.
   - **Recommended action:** Correct tags and captions using an approved photo inventory.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

132. **[P0] Which images show V2, V3, V4 direction, donor material, or undated lineage?**
   - **Current state:** Numeric version mapping was intentionally cautious.
   - **What must be confirmed:** Confirm each mapping.
   - **Recommended action:** Do not publish version labels from filenames alone.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

133. **[P0] Is the full-shell Huey hero the correct current public image?**
   - **Current state:** It leads the Huey route.
   - **What must be confirmed:** Confirm current relevance and crop.
   - **Recommended action:** Approve or replace with a more recent physical record.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

134. **[P0] Do the monkey-head images represent current identity, lineage, or reference parts?**
   - **Current state:** Several images show different head states.
   - **What must be confirmed:** Confirm each role.
   - **Recommended action:** Use distinct captions and categories.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

135. **[P1] Are the route hero crops correct on desktop and mobile?**
   - **Current state:** Focal-point-aware derivatives are used.
   - **What must be confirmed:** Confirm faces, hardware, and symbolic elements are not cropped misleadingly.
   - **Recommended action:** Review all 40 route fields in a contact sheet.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

136. **[P1] Are social-preview crops and captions appropriate?**
   - **Current state:** Every route has a 1200 × 630 preview.
   - **What must be confirmed:** Confirm public sharing appearance.
   - **Recommended action:** Test representative links on major platforms.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

137. **[P1] Should the car-in-field master remain the permanent site hero indefinitely?**
   - **Current state:** It is a durable preference.
   - **What must be confirmed:** Confirm whether v201.x changes its treatment only, not identity.
   - **Recommended action:** Lock the asset and approved derivative policy.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

138. **[P1] Are dog images correctly attributed to names and breeds?**
   - **Current state:** Pages rely on owner-provided context and cautious breed wording.
   - **What must be confirmed:** Confirm each dog, name, breed, and photo.
   - **Recommended action:** Update captions as personal records.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

139. **[P1] Are any film, television, concert, or third-party images rights-sensitive?**
   - **Current state:** v200.x excluded many generic reference stills.
   - **What must be confirmed:** Confirm the remaining media rights basis.
   - **Recommended action:** Remove or replace uncertain third-party material.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

140. **[P1] Should image provenance be visible to ordinary visitors?**
   - **Current state:** Visual Atlas exposes source paths and categories.
   - **What must be confirmed:** Confirm desired transparency.
   - **Recommended action:** Keep technical provenance in the atlas if page captions should stay simple.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

141. **[P1] Are alt texts descriptive without making unverified claims?**
   - **Current state:** Static validation confirms presence, not factual correctness.
   - **What must be confirmed:** Human-review every identity and hardware alt text.
   - **Recommended action:** Approve alt text alongside captions.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

142. **[P1] Do any images reveal private locations, documents, serial numbers, screens, or personal data?**
   - **Current state:** No automated privacy-image audit can guarantee this.
   - **What must be confirmed:** Inspect full resolution manually.
   - **Recommended action:** Redact, crop, or remove sensitive details.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

143. **[P2] Should Visual Atlas expose full-resolution lightbox targets?**
   - **Current state:** It currently supports larger images.
   - **What must be confirmed:** Confirm bandwidth, privacy, and rights impact.
   - **Recommended action:** Use limited-resolution public derivatives if needed.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

144. **[P2] Are system font stacks visually acceptable on Dylan’s target devices?**
   - **Current state:** No font binaries or remote services are used.
   - **What must be confirmed:** Confirm Windows, macOS, Linux, iOS, and Android rendering.
   - **Recommended action:** Adjust stack order or metrics, not payload, unless explicitly approved.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

## Personal archives, dogs, playlist, media, and adjacent projects

Confirms non-Huey content and mutable external facts.

145. **[P0] What is the current live count for the Demons Enter My Body playlist?**
   - **Current state:** The packaged archival dataset contains 463 rows; older live counts differ.
   - **What must be confirmed:** Confirm live count on review date.
   - **Recommended action:** Display live and archival counts separately with dates.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

146. **[P0] Is the playlist title and public link still correct?**
   - **Current state:** The site uses the established title and archived entries.
   - **What must be confirmed:** Confirm current YouTube playlist identity.
   - **Recommended action:** Update the link or mark the page archival.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

147. **[P1] Are all 463 archived playlist rows accurate enough for public display?**
   - **Current state:** The file was parsed but not independently verified row by row.
   - **What must be confirmed:** Confirm correction policy.
   - **Recommended action:** Sample, correct known errors, and label provenance.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

148. **[P1] Should playlist views or other mutable platform metrics be shown?**
   - **Current state:** Mutable totals can become stale quickly.
   - **What must be confirmed:** Confirm value.
   - **Recommended action:** Prefer dated snapshots or omit.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

149. **[P1] Are downloadable playlist exports current and privacy-safe?**
   - **Current state:** The site provides archive exports.
   - **What must be confirmed:** Confirm files, format, and metadata.
   - **Recommended action:** Regenerate or label them with dates.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

150. **[P1] Should the Sweeney Todd restoration project be represented publicly?**
   - **Current state:** It is significant continuity context but not a main current route.
   - **What must be confirmed:** Confirm copyright, scope, and public value.
   - **Recommended action:** Add only rights-safe process documentation.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

151. **[P1] Are Pinball project names, status, and claims accurate?**
   - **Current state:** Dirty Leroy and The Executive are documented with first-person/project records.
   - **What must be confirmed:** Confirm build dates, completion state, and specifications.
   - **Recommended action:** Correct page-by-page.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

152. **[P1] Are PlayStation build compatibility and historical claims accurate?**
   - **Current state:** The page uses cautious wording after earlier fact audit.
   - **What must be confirmed:** Confirm supported systems and current state.
   - **Recommended action:** Avoid universal compatibility claims.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

153. **[P1] Do Recipes belong in the public site?**
   - **Current state:** They are a personal human lane.
   - **What must be confirmed:** Confirm value and privacy.
   - **Recommended action:** Keep, expand, merge, or remove deliberately.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

154. **[P1] Are the dog pages a current household record, an archive, or both?**
   - **Current state:** The site treats them as personal archive routes.
   - **What must be confirmed:** Confirm current/archival wording.
   - **Recommended action:** Use dates or archive labels where needed.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

155. **[P2] Should Gallery and Visual Atlas include the same personal images?**
   - **Current state:** They serve editorial versus registry roles.
   - **What must be confirmed:** Confirm acceptable duplication in presentation.
   - **Recommended action:** Reuse one payload but explain different contexts.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

156. **[P2] Should Media list only current external coverage?**
   - **Current state:** External links may age or disappear.
   - **What must be confirmed:** Confirm each link and date.
   - **Recommended action:** Archive dead links with context or remove.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

## Governance, constitution, research, and speculative lineage

Prevents target-state doctrine from being mistaken for current implementation.

157. **[P0] Should the Draft Constitution remain public?**
   - **Current state:** It is clearly labelled unratified and historical.
   - **What must be confirmed:** Confirm public benefit and risk.
   - **Recommended action:** Retain only with explicit status and review date.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

158. **[P0] Which governance concepts remain active direction?**
   - **Current state:** Parliament, Presidency, Supreme Court, citizens, districts, and constitutional action appear in lineage/target materials.
   - **What must be confirmed:** Confirm active, deferred, or retired status for each.
   - **Recommended action:** Create a governance status matrix.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

159. **[P0] Is Dylan’s sole authority statement still correct?**
   - **Current state:** It is current until Huey can participate legitimately.
   - **What must be confirmed:** Confirm wording and any conditions.
   - **Recommended action:** Keep current authority separate from target governance.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

160. **[P1] Should node sovereignty be public terminology?**
   - **Current state:** A non-operational explanatory note is packaged.
   - **What must be confirmed:** Confirm whether “sovereignty” is too strong or useful.
   - **Recommended action:** Approve a bounded definition or use “node autonomy.”
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

161. **[P1] What authority can a future collective exercise over a node?**
   - **Current state:** Unresolved.
   - **What must be confirmed:** Confirm only if decided.
   - **Recommended action:** Leave open rather than imply a hierarchy.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

162. **[P1] What happens to identity and authority after bifurcation?**
   - **Current state:** Explicitly unresolved.
   - **What must be confirmed:** Confirm whether v201.x should ask publicly or keep internal.
   - **Recommended action:** Preserve as an open design question.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

163. **[P1] Which historical research notes still represent useful lineage?**
   - **Current state:** Eleven noindex notes remain.
   - **What must be confirmed:** Confirm each.
   - **Recommended action:** Add a one-line Human-Counterpart disposition to the archive index.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

164. **[P1] Do speculative analogies create copyright, tone, or misunderstanding risks?**
   - **Current state:** Some notes reference science fiction and biological systems.
   - **What must be confirmed:** Confirm framing.
   - **Recommended action:** Keep as analogy, not evidence, and minimize quoted material.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

165. **[P2] Should governance material be separated from general research more strongly?**
   - **Current state:** The site has separate Constitution and Research routes.
   - **What must be confirmed:** Confirm information architecture.
   - **Recommended action:** Add cross-boundary warnings rather than more routes if possible.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

166. **[P2] Should any target-state governance claim be moved out of public pages?**
   - **Current state:** The current site keeps it secondary.
   - **What must be confirmed:** Confirm desired public depth.
   - **Recommended action:** Keep detailed doctrine in governance documents.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

## Accessibility, usability, SEO, legal, and deployment

Confirms the final public fit beyond internal correctness.

167. **[P0] Does every page remain understandable with JavaScript disabled?**
   - **Current state:** Static source strips and primary content remain; enhanced search and modals require JS.
   - **What must be confirmed:** Confirm acceptable no-JS experience.
   - **Recommended action:** Test a representative sample manually.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

168. **[P0] Are keyboard controls discoverable and conflict-free?**
   - **Current state:** Search, map, lenses, visuals, random route, source ledger, and help have shortcuts.
   - **What must be confirmed:** Confirm on Windows, macOS, and screen readers.
   - **Recommended action:** Remove any shortcut that conflicts with assistive technology.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

169. **[P0] Is colour contrast sufficient in all three visual lenses?**
   - **Current state:** Automated layout tests do not equal a full WCAG audit.
   - **What must be confirmed:** Confirm contrast for body text, muted text, links, controls, and status colours.
   - **Recommended action:** Run formal contrast checks and correct failures.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

170. **[P0] Is focus order logical on desktop and mobile?**
   - **Current state:** The shell is keyboard accessible in tested interactions.
   - **What must be confirmed:** Confirm across all page types.
   - **Recommended action:** Fix DOM order rather than only visual order.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

171. **[P0] Are modal focus traps and Escape behavior reliable?**
   - **Current state:** Search, map, help, source ledger, and lightbox passed basic tests.
   - **What must be confirmed:** Confirm screen-reader and touch behavior.
   - **Recommended action:** Add robust focus containment if needed.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

172. **[P0] Are all alt texts, headings, labels, and landmarks semantically correct?**
   - **Current state:** Automated validation checks presence and counts.
   - **What must be confirmed:** Human-review meaning and hierarchy.
   - **Recommended action:** Approve page by page.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

173. **[P1] Are canonical URLs correct for the intended production host?**
   - **Current state:** They use https://www.dlrp.ca.
   - **What must be confirmed:** Confirm preferred www/non-www canonicalization.
   - **Recommended action:** Configure redirects and keep one canonical host.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

174. **[P1] Are titles and meta descriptions accurate and compelling?**
   - **Current state:** They are route-specific but mostly documentary.
   - **What must be confirmed:** Confirm editorial fit and length.
   - **Recommended action:** Review all indexed routes in one metadata sheet.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

175. **[P1] Should noindex historical routes remain crawlable but excluded from search?**
   - **Current state:** They are noindex and linked from archive surfaces.
   - **What must be confirmed:** Confirm robots strategy.
   - **Recommended action:** Use noindex,follow unless removal is preferred.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

176. **[P1] Are Open Graph and Twitter images and metadata correct?**
   - **Current state:** All routes have normalized assets.
   - **What must be confirmed:** Confirm current platform requirements and wording.
   - **Recommended action:** Test a sample with social debuggers after deployment.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

177. **[P1] Does the service worker cache the correct public shell?**
   - **Current state:** It excludes private paths and uses a versioned cache.
   - **What must be confirmed:** Confirm update behavior on the actual host.
   - **Recommended action:** Test install, refresh, offline, and cache invalidation.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

178. **[P1] Should the site be installable as a PWA?**
   - **Current state:** A manifest and service worker exist.
   - **What must be confirmed:** Confirm user value.
   - **Recommended action:** Keep only if install/offline behavior is maintained.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

179. **[P1] Are all external links live and still desired?**
   - **Current state:** Automated package validation checks local targets only.
   - **What must be confirmed:** Verify GitHub, YouTube, media, and outbound references.
   - **Recommended action:** Create a dated external-link audit.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

180. **[P1] Is the public contact address protected adequately from spam?**
   - **Current state:** A direct mailto is visible.
   - **What must be confirmed:** Confirm risk tolerance.
   - **Recommended action:** Use a form, alias, or obfuscation if needed.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

181. **[P1] Are license statements correct for code, documentation, and media?**
   - **Current state:** Repository says GPL-3.0-only for code and CC-BY-SA-4.0 for docs/media unless noted.
   - **What must be confirmed:** Confirm the website’s own text and image rights.
   - **Recommended action:** Add a clear site/media rights page or footer note.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

182. **[P1] Are third-party trademarks used appropriately?**
   - **Current state:** Project pages reference PlayStation, YouTube, Linux, Debian, and hardware brands.
   - **What must be confirmed:** Confirm nominative use and disclaimers.
   - **Recommended action:** Add trademark disclaimers if counsel or policy warrants.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

183. **[P1] Does the site collect analytics, cookies, form data, or other personal data?**
   - **Current state:** The static package contains no declared analytics system.
   - **What must be confirmed:** Confirm production configuration.
   - **Recommended action:** Publish a privacy notice if any collection exists.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

184. **[P1] Are release reports and machine-readable files safe to expose publicly?**
   - **Current state:** They may reveal file structure and internal decision states.
   - **What must be confirmed:** Confirm disclosure policy.
   - **Recommended action:** Separate deployable and maintainer bundles if needed.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

185. **[P1] Does the deployment host provide correct MIME types and caching headers?**
   - **Current state:** The package is static and host-agnostic.
   - **What must be confirmed:** Confirm server behavior.
   - **Recommended action:** Test webmanifest, JSON, WebP, service worker, and Markdown handling.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

186. **[P1] Will old service-worker caches be retired cleanly?**
   - **Current state:** v200.8 uses a new cache key.
   - **What must be confirmed:** Confirm clients update without stale pages.
   - **Recommended action:** Test upgrade from v200.7 on a real browser profile.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

187. **[P1] Is HTTPS, redirect, and HSTS configuration correct?**
   - **Current state:** Not verifiable from the package alone.
   - **What must be confirmed:** Confirm production host settings.
   - **Recommended action:** Run a post-deployment security/header check.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

188. **[P2] Should release ZIPs be hosted from the public site?**
   - **Current state:** Downloads may increase storage and expose lineage.
   - **What must be confirmed:** Confirm hosting and retention policy.
   - **Recommended action:** Host checksummed releases deliberately or keep them off-site.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

189. **[P2] What is the maximum acceptable site size after v201.x?**
   - **Current state:** The v200.x warning budget is 25 MiB extracted.
   - **What must be confirmed:** Confirm budget and exceptions.
   - **Recommended action:** Require justification for growth above the budget.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

190. **[P2] Should v201.x add automated accessibility and link checks to release validation?**
   - **Current state:** Current validator covers structure, images, references, and metadata.
   - **What must be confirmed:** Confirm desired automation.
   - **Recommended action:** Add reproducible checks without replacing Human review.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**

191. **[P2] What constitutes final deployment approval?**
   - **Current state:** No live deployment is performed during assembly.
   - **What must be confirmed:** Confirm checklist and rollback owner.
   - **Recommended action:** Require checksum, backup, dry run, and post-deploy verification.
   - **Disposition:** [ ] Confirm  [ ] Revise  [ ] Remove  [ ] Defer
   - **Human-Counterpart notes:**