{ "version": "v201.x-review-checklist", "source_release": "v200.8-complete", "generated": "2026-07-17", "repository_head": "2b61323802bdf39a0a58757f60db7ce45290c085", "architecture_source_commit": "9c29f55e2aea317fcb1953576fd27892d54cac5e", "allowed_dispositions": [ "confirm", "revise", "remove", "defer" ], "questions": [ { "number": 1, "id": "HR-001", "category": "Release acceptance and review authority", "category_scope": "Defines what Human-Counterpart approval means before v201.x edits begin.", "priority": "P0", "question": "Does v200.8 accurately represent the final pre-review website baseline?", "current_state": "The package is labelled as the final v200.x review build.", "why_it_matters": "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": "unreviewed", "review_notes": "" }, { "number": 2, "id": "HR-002", "category": "Release acceptance and review authority", "category_scope": "Defines what Human-Counterpart approval means before v201.x edits begin.", "priority": "P0", "question": "Who may approve changes during v201.x?", "current_state": "Dylan is recorded as Human-Counterpart and current canon authority.", "why_it_matters": "Confirm whether any other person may approve public biography, privacy, or project claims.", "recommended_action": "Name the approval authority and any advisory reviewers.", "disposition": "unreviewed", "review_notes": "" }, { "number": 3, "id": "HR-003", "category": "Release acceptance and review authority", "category_scope": "Defines what Human-Counterpart approval means before v201.x edits begin.", "priority": "P0", "question": "Should Human-Counterpart approval be recorded page by page or as one release decision?", "current_state": "No formal review workflow is yet locked.", "why_it_matters": "Choose the acceptance granularity.", "recommended_action": "Use the machine checklist to record per-item dispositions and a final release sign-off.", "disposition": "unreviewed", "review_notes": "" }, { "number": 4, "id": "HR-004", "category": "Release acceptance and review authority", "category_scope": "Defines what Human-Counterpart approval means before v201.x edits begin.", "priority": "P0", "question": "What counts as accepted, corrected, removed, or deferred?", "current_state": "The review packet offers these four outcomes.", "why_it_matters": "Confirm the disposition vocabulary.", "recommended_action": "Lock a small status set before editing begins.", "disposition": "unreviewed", "review_notes": "" }, { "number": 5, "id": "HR-005", "category": "Release acceptance and review authority", "category_scope": "Defines what Human-Counterpart approval means before v201.x edits begin.", "priority": "P1", "question": "Should v201.x preserve a visible review history?", "current_state": "v200.x preserves release audits but not Human-Counterpart decisions.", "why_it_matters": "Confirm whether decisions should be logged publicly, privately, or both.", "recommended_action": "Create a review decision log with privacy-safe summaries.", "disposition": "unreviewed", "review_notes": "" }, { "number": 6, "id": "HR-006", "category": "Release acceptance and review authority", "category_scope": "Defines what Human-Counterpart approval means before v201.x edits begin.", "priority": "P1", "question": "Which files become authoritative after review?", "current_state": "Website, README, master plan, and runtime remain distinct layers.", "why_it_matters": "Confirm the post-review source priority.", "recommended_action": "Publish a short source hierarchy in v201.x release records.", "disposition": "unreviewed", "review_notes": "" }, { "number": 7, "id": "HR-007", "category": "Release acceptance and review authority", "category_scope": "Defines what Human-Counterpart approval means before v201.x edits begin.", "priority": "P1", "question": "Should v200.8 remain downloadable after v201.x?", "current_state": "v200.x is continuity lineage.", "why_it_matters": "Confirm archive retention and public visibility.", "recommended_action": "Keep one checksummed v200.8 archive unless privacy review requires removal.", "disposition": "unreviewed", "review_notes": "" }, { "number": 8, "id": "HR-008", "category": "Release acceptance and review authority", "category_scope": "Defines what Human-Counterpart approval means before v201.x edits begin.", "priority": "P1", "question": "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.", "why_it_matters": "Confirm whether approval happens at v201.0 or later in v201.x.", "recommended_action": "Define the review-series release gate.", "disposition": "unreviewed", "review_notes": "" }, { "number": 9, "id": "HR-009", "category": "Release acceptance and review authority", "category_scope": "Defines what Human-Counterpart approval means before v201.x edits begin.", "priority": "P2", "question": "Should the public site display its review state?", "current_state": "v200.8 shows a review-build marker.", "why_it_matters": "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": "unreviewed", "review_notes": "" }, { "number": 10, "id": "HR-010", "category": "Release acceptance and review authority", "category_scope": "Defines what Human-Counterpart approval means before v201.x edits begin.", "priority": "P2", "question": "Should release reports remain web-accessible on the deployed host?", "current_state": "Reports are packaged but not indexed.", "why_it_matters": "Confirm whether they are public artifacts or deployment-only records.", "recommended_action": "Move non-public reports outside the deploy root if necessary.", "disposition": "unreviewed", "review_notes": "" }, { "number": 11, "id": "HR-011", "category": "Homepage and first-visit navigation", "category_scope": "Reviews the v200.7 splash retained by v200.8.", "priority": "P0", "question": "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.", "why_it_matters": "Confirm the wording, emphasis, and reading level.", "recommended_action": "Edit the opening only after a first-time-reader test.", "disposition": "unreviewed", "review_notes": "" }, { "number": 12, "id": "HR-012", "category": "Homepage and first-visit navigation", "category_scope": "Reviews the v200.7 splash retained by v200.8.", "priority": "P0", "question": "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.", "why_it_matters": "Confirm whether About, Gallery, or another route should replace any card.", "recommended_action": "Keep four paths unless a clear visitor task is missing.", "disposition": "unreviewed", "review_notes": "" }, { "number": 13, "id": "HR-013", "category": "Homepage and first-visit navigation", "category_scope": "Reviews the v200.7 splash retained by v200.8.", "priority": "P0", "question": "Is “Meet Huey” the right public invitation while Huey remains incomplete?", "current_state": "The wording is approachable but may imply operational presence.", "why_it_matters": "Confirm the intended degree of personification.", "recommended_action": "Retain, soften, or replace with “Understand Huey.”", "disposition": "unreviewed", "review_notes": "" }, { "number": 14, "id": "HR-014", "category": "Homepage and first-visit navigation", "category_scope": "Reviews the v200.7 splash retained by v200.8.", "priority": "P1", "question": "Does “Understand the project” correctly describe Monkey-Head-Project?", "current_state": "It leads to the umbrella and collective explanation.", "why_it_matters": "Confirm the label and whether the full project name should be visible.", "recommended_action": "Use the shortest accurate label that preserves identity.", "disposition": "unreviewed", "review_notes": "" }, { "number": 15, "id": "HR-015", "category": "Homepage and first-visit navigation", "category_scope": "Reviews the v200.7 splash retained by v200.8.", "priority": "P1", "question": "Does “See the builds” give enough prominence to non-Huey work?", "current_state": "Projects leads with Huey V4 and retains pinball and console records.", "why_it_matters": "Confirm the balance.", "recommended_action": "Adjust card copy, not the route structure, unless needed.", "disposition": "unreviewed", "review_notes": "" }, { "number": 16, "id": "HR-016", "category": "Homepage and first-visit navigation", "category_scope": "Reviews the v200.7 splash retained by v200.8.", "priority": "P1", "question": "Is “Verify the record” understandable to a general visitor?", "current_state": "It links to the Repository Ledger.", "why_it_matters": "Confirm whether “Check the sources” is clearer.", "recommended_action": "Test both labels with a non-project reader.", "disposition": "unreviewed", "review_notes": "" }, { "number": 17, "id": "HR-017", "category": "Homepage and first-visit navigation", "category_scope": "Reviews the v200.7 splash retained by v200.8.", "priority": "P1", "question": "Are Search, Map, and About visible enough on desktop and mobile?", "current_state": "They are secondary utility controls in the splash.", "why_it_matters": "Confirm discoverability.", "recommended_action": "Increase contrast or position only if observed users miss them.", "disposition": "unreviewed", "review_notes": "" }, { "number": 18, "id": "HR-018", "category": "Homepage and first-visit navigation", "category_scope": "Reviews the v200.7 splash retained by v200.8.", "priority": "P1", "question": "Are the five browse lanes correctly named?", "current_state": "System, Lab, Records, Documents, and Human are used.", "why_it_matters": "Confirm “Human” and “Records” in particular.", "recommended_action": "Rename consistently across homepage, rail, map, and search labels.", "disposition": "unreviewed", "review_notes": "" }, { "number": 19, "id": "HR-019", "category": "Homepage and first-visit navigation", "category_scope": "Reviews the v200.7 splash retained by v200.8.", "priority": "P1", "question": "Should Documents appear before Human everywhere?", "current_state": "v200.8 standardizes this order.", "why_it_matters": "Confirm this information hierarchy.", "recommended_action": "Keep one order across every navigation surface.", "disposition": "unreviewed", "review_notes": "" }, { "number": 20, "id": "HR-020", "category": "Homepage and first-visit navigation", "category_scope": "Reviews the v200.7 splash retained by v200.8.", "priority": "P1", "question": "Does the permanent car-in-field hero still represent the site?", "current_state": "It remains the homepage anchor by explicit preference.", "why_it_matters": "Confirm the image, crop, overlay, and privacy/public-fit.", "recommended_action": "Approve the current derivative and preserve the original master separately.", "disposition": "unreviewed", "review_notes": "" }, { "number": 21, "id": "HR-021", "category": "Homepage and first-visit navigation", "category_scope": "Reviews the v200.7 splash retained by v200.8.", "priority": "P2", "question": "Is the first viewport too dense on smaller phones?", "current_state": "The mobile layout is a single stack.", "why_it_matters": "Confirm on the devices Dylan actually uses.", "recommended_action": "Test at 320, 360, 390, and 430 CSS pixels.", "disposition": "unreviewed", "review_notes": "" }, { "number": 22, "id": "HR-022", "category": "Homepage and first-visit navigation", "category_scope": "Reviews the v200.7 splash retained by v200.8.", "priority": "P2", "question": "Should the homepage show the current repository and review state?", "current_state": "It shows concise source status.", "why_it_matters": "Confirm whether that is useful to ordinary visitors.", "recommended_action": "Keep detailed source status in the ledger if the homepage feels technical.", "disposition": "unreviewed", "review_notes": "" }, { "number": 23, "id": "HR-023", "category": "Homepage and first-visit navigation", "category_scope": "Reviews the v200.7 splash retained by v200.8.", "priority": "P2", "question": "Is the current Huey V4 feature the correct below-fold emphasis?", "current_state": "V4 is the current accepted direction, not a completed build.", "why_it_matters": "Confirm its public priority and wording.", "recommended_action": "Retain only if physical embodiment remains the active focus.", "disposition": "unreviewed", "review_notes": "" }, { "number": 24, "id": "HR-024", "category": "Homepage and first-visit navigation", "category_scope": "Reviews the v200.7 splash retained by v200.8.", "priority": "P2", "question": "Are the lower-page images the right continuity cross-section?", "current_state": "The strip uses a small deliberate set.", "why_it_matters": "Confirm that each image earns its place.", "recommended_action": "Replace rather than expand if a stronger record exists.", "disposition": "unreviewed", "review_notes": "" }, { "number": 25, "id": "HR-025", "category": "Route taxonomy and information architecture", "category_scope": "Confirms the 40-route structure before editorial work.", "priority": "P0", "question": "Are all 40 registered routes still wanted in the public site?", "current_state": "v200.8 preserves 29 indexed and 11 noindex routes.", "why_it_matters": "Confirm keep, merge, redirect, archive, or remove for every route.", "recommended_action": "Use the page-review matrix before changing navigation.", "disposition": "unreviewed", "review_notes": "" }, { "number": 26, "id": "HR-026", "category": "Route taxonomy and information architecture", "category_scope": "Confirms the 40-route structure before editorial work.", "priority": "P0", "question": "Should the 11 historical research routes remain individually accessible?", "current_state": "They are noindex and labelled as historical speculative notes.", "why_it_matters": "Confirm public value and risk.", "recommended_action": "Retain only those with clear lineage value and suitable warnings.", "disposition": "unreviewed", "review_notes": "" }, { "number": 27, "id": "HR-027", "category": "Route taxonomy and information architecture", "category_scope": "Confirms the 40-route structure before editorial work.", "priority": "P1", "question": "Is “Source Map” the clearest name for the documentation-layer page?", "current_state": "It explains source hierarchy and provenance.", "why_it_matters": "Confirm whether “Documentation Map” is clearer.", "recommended_action": "Rename route title only if all references are updated together.", "disposition": "unreviewed", "review_notes": "" }, { "number": 28, "id": "HR-028", "category": "Route taxonomy and information architecture", "category_scope": "Confirms the 40-route structure before editorial work.", "priority": "P1", "question": "Should Repository Ledger remain a top-level public route?", "current_state": "It exposes source files, drift, and repository state.", "why_it_matters": "Confirm audience and transparency goals.", "recommended_action": "Keep public if transparency outweighs complexity.", "disposition": "unreviewed", "review_notes": "" }, { "number": 29, "id": "HR-029", "category": "Route taxonomy and information architecture", "category_scope": "Confirms the 40-route structure before editorial work.", "priority": "P1", "question": "Should Visual Atlas remain separate from Gallery?", "current_state": "Atlas is structured/filterable; Gallery is editorial.", "why_it_matters": "Confirm the distinction is meaningful to visitors.", "recommended_action": "Merge only if the roles cannot be explained clearly.", "disposition": "unreviewed", "review_notes": "" }, { "number": 30, "id": "HR-030", "category": "Route taxonomy and information architecture", "category_scope": "Confirms the 40-route structure before editorial work.", "priority": "P1", "question": "Should Media remain a public route?", "current_state": "It contains outward-facing coverage and links.", "why_it_matters": "Confirm whether current content is substantial and current.", "recommended_action": "Refresh, merge, or archive based on actual material.", "disposition": "unreviewed", "review_notes": "" }, { "number": 31, "id": "HR-031", "category": "Route taxonomy and information architecture", "category_scope": "Confirms the 40-route structure before editorial work.", "priority": "P1", "question": "Should Downloads expose release and machine-readable files?", "current_state": "It currently acts as a release shelf.", "why_it_matters": "Confirm which technical files are appropriate for public use.", "recommended_action": "Separate visitor downloads from maintainer artifacts if needed.", "disposition": "unreviewed", "review_notes": "" }, { "number": 32, "id": "HR-032", "category": "Route taxonomy and information architecture", "category_scope": "Confirms the 40-route structure before editorial work.", "priority": "P1", "question": "Is the Draft Constitution route correctly placed under Documents?", "current_state": "It is an unratified historical archive.", "why_it_matters": "Confirm public context and naming.", "recommended_action": "Keep “draft” and “unratified” visible everywhere.", "disposition": "unreviewed", "review_notes": "" }, { "number": 33, "id": "HR-033", "category": "Route taxonomy and information architecture", "category_scope": "Confirms the 40-route structure before editorial work.", "priority": "P1", "question": "Should Linux 7.0 remain a public Lab route?", "current_state": "It is an end-of-life experiment archive.", "why_it_matters": "Confirm archival value.", "recommended_action": "Retain with clear EOL status or move to a deeper archive.", "disposition": "unreviewed", "review_notes": "" }, { "number": 34, "id": "HR-034", "category": "Route taxonomy and information architecture", "category_scope": "Confirms the 40-route structure before editorial work.", "priority": "P2", "question": "Are route codes useful to public visitors?", "current_state": "Codes support search, maps, and continuity.", "why_it_matters": "Confirm whether they aid or distract.", "recommended_action": "Keep in secondary UI even if removed from primary copy.", "disposition": "unreviewed", "review_notes": "" }, { "number": 35, "id": "HR-035", "category": "Route taxonomy and information architecture", "category_scope": "Confirms the 40-route structure before editorial work.", "priority": "P2", "question": "Are route titles, breadcrumbs, and rail labels consistent?", "current_state": "v200.8 standardizes mechanics, but Human review must confirm wording.", "why_it_matters": "Review each route title and label as a set.", "recommended_action": "Record exact approved label per route.", "disposition": "unreviewed", "review_notes": "" }, { "number": 36, "id": "HR-036", "category": "Route taxonomy and information architecture", "category_scope": "Confirms the 40-route structure before editorial work.", "priority": "P2", "question": "Should old URLs receive redirects if routes are renamed or removed?", "current_state": "The current static package preserves canonical paths.", "why_it_matters": "Confirm redirect capability on the host.", "recommended_action": "Create static redirect pages or server rules before changing URLs.", "disposition": "unreviewed", "review_notes": "" }, { "number": 37, "id": "HR-037", "category": "Huey node and Monkey-Head-Project ontology", "category_scope": "Confirms the central public architecture before it is treated as approved.", "priority": "P0", "question": "Is Huey correctly defined as one embodied AI node?", "current_state": "The website candidate uses this as its primary model.", "why_it_matters": "Confirm the definition and exact wording.", "recommended_action": "Approve, revise, or defer before synchronizing README/master plan.", "disposition": "unreviewed", "review_notes": "" }, { "number": 38, "id": "HR-038", "category": "Huey node and Monkey-Head-Project ontology", "category_scope": "Confirms the central public architecture before it is treated as approved.", "priority": "P0", "question": "Is a node correctly defined as the physical embodiment of one AI unit?", "current_state": "This is the v121.0 candidate definition.", "why_it_matters": "Confirm whether software, memory, authority, or continuity criteria must be included.", "recommended_action": "Write one canonical node definition.", "disposition": "unreviewed", "review_notes": "" }, { "number": 39, "id": "HR-039", "category": "Huey node and Monkey-Head-Project ontology", "category_scope": "Confirms the central public architecture before it is treated as approved.", "priority": "P0", "question": "Is Monkey-Head-Project correctly defined as umbrella and eventual collective?", "current_state": "The website places it above one or more valid nodes.", "why_it_matters": "Confirm current and target roles.", "recommended_action": "Separate present umbrella from future collective in approved wording.", "disposition": "unreviewed", "review_notes": "" }, { "number": 40, "id": "HR-040", "category": "Huey node and Monkey-Head-Project ontology", "category_scope": "Confirms the central public architecture before it is treated as approved.", "priority": "P0", "question": "Does the site overstate the current existence of a collective?", "current_state": "The site says collective later and labels it target state.", "why_it_matters": "Confirm no page implies operational federation.", "recommended_action": "Correct any phrase that treats multiple nodes or governance as active.", "disposition": "unreviewed", "review_notes": "" }, { "number": 41, "id": "HR-041", "category": "Huey node and Monkey-Head-Project ontology", "category_scope": "Confirms the central public architecture before it is treated as approved.", "priority": "P0", "question": "Are Brain and Body properly re-scoped as node-local domains?", "current_state": "They remain useful internal divisions in the candidate.", "why_it_matters": "Confirm whether “domain,” “subsystem,” or another term is preferred.", "recommended_action": "Use one term consistently.", "disposition": "unreviewed", "review_notes": "" }, { "number": 42, "id": "HR-042", "category": "Huey node and Monkey-Head-Project ontology", "category_scope": "Confirms the central public architecture before it is treated as approved.", "priority": "P0", "question": "Is Farm correctly moved to optional collective-level infrastructure?", "current_state": "The candidate no longer makes Farm constitutive of one Huey.", "why_it_matters": "Confirm whether Farm remains a valid term and what it includes.", "recommended_action": "Approve a bounded Farm definition or mark it unresolved.", "disposition": "unreviewed", "review_notes": "" }, { "number": 43, "id": "HR-043", "category": "Huey node and Monkey-Head-Project ontology", "category_scope": "Confirms the central public architecture before it is treated as approved.", "priority": "P0", "question": "Does Huey identity belong to the whole physical node?", "current_state": "The candidate points that way while internal authority remains open.", "why_it_matters": "Confirm what is decided versus unresolved.", "recommended_action": "Avoid stronger identity claims than Dylan accepts.", "disposition": "unreviewed", "review_notes": "" }, { "number": 44, "id": "HR-044", "category": "Huey node and Monkey-Head-Project ontology", "category_scope": "Confirms the central public architecture before it is treated as approved.", "priority": "P0", "question": "Can one valid Huey node exist without Farm or collective membership?", "current_state": "The candidate says yes.", "why_it_matters": "Confirm this node-validity rule.", "recommended_action": "Lock it if accepted; otherwise state required dependencies.", "disposition": "unreviewed", "review_notes": "" }, { "number": 45, "id": "HR-045", "category": "Huey node and Monkey-Head-Project ontology", "category_scope": "Confirms the central public architecture before it is treated as approved.", "priority": "P1", "question": "What distinguishes Huey from HueyOS?", "current_state": "Huey is the identity/node; HueyOS is the software/runtime layer.", "why_it_matters": "Confirm the public distinction.", "recommended_action": "Use a short side-by-side definition on Huey and project pages.", "disposition": "unreviewed", "review_notes": "" }, { "number": 46, "id": "HR-046", "category": "Huey node and Monkey-Head-Project ontology", "category_scope": "Confirms the central public architecture before it is treated as approved.", "priority": "P1", "question": "What distinguishes Huey from the physical shell?", "current_state": "The node includes more than the shell, while embodiment is essential.", "why_it_matters": "Confirm the boundary.", "recommended_action": "Avoid using shell, Body, node, and Huey interchangeably.", "disposition": "unreviewed", "review_notes": "" }, { "number": 47, "id": "HR-047", "category": "Huey node and Monkey-Head-Project ontology", "category_scope": "Confirms the central public architecture before it is treated as approved.", "priority": "P1", "question": "What distinguishes Huey from PyHuey?", "current_state": "PyHuey is the primary GUI and runtime direction, not the entire node.", "why_it_matters": "Confirm current role.", "recommended_action": "Keep PyHuey subordinate to the node definition.", "disposition": "unreviewed", "review_notes": "" }, { "number": 48, "id": "HR-048", "category": "Huey node and Monkey-Head-Project ontology", "category_scope": "Confirms the central public architecture before it is treated as approved.", "priority": "P1", "question": "What distinguishes Huey from LabTech?", "current_state": "LabTech supports, accesses, and recovers Huey but is outside its sovereignty.", "why_it_matters": "Confirm current devices and exceptions.", "recommended_action": "Review every device classification.", "disposition": "unreviewed", "review_notes": "" }, { "number": 49, "id": "HR-049", "category": "Huey node and Monkey-Head-Project ontology", "category_scope": "Confirms the central public architecture before it is treated as approved.", "priority": "P1", "question": "Should the term “Huey proper” remain on the public site?", "current_state": "It appears in lineage and target-state language.", "why_it_matters": "Confirm whether it clarifies or confuses.", "recommended_action": "Define once or remove from public copy.", "disposition": "unreviewed", "review_notes": "" }, { "number": 50, "id": "HR-050", "category": "Huey node and Monkey-Head-Project ontology", "category_scope": "Confirms the central public architecture before it is treated as approved.", "priority": "P1", "question": "Is “one real node first” the correct public summary?", "current_state": "It is the current cross-site phrase.", "why_it_matters": "Confirm tone and technical accuracy.", "recommended_action": "Approve as a slogan or replace with a less slogan-like statement.", "disposition": "unreviewed", "review_notes": "" }, { "number": 51, "id": "HR-051", "category": "Huey node and Monkey-Head-Project ontology", "category_scope": "Confirms the central public architecture before it is treated as approved.", "priority": "P1", "question": "How should exact bifurcation be described?", "current_state": "It is a future lineage/replication concept above node validity.", "why_it_matters": "Confirm identity and authority non-claims.", "recommended_action": "Approve a precise non-operational definition.", "disposition": "unreviewed", "review_notes": "" }, { "number": 52, "id": "HR-052", "category": "Huey node and Monkey-Head-Project ontology", "category_scope": "Confirms the central public architecture before it is treated as approved.", "priority": "P1", "question": "How should augmented bifurcation be described?", "current_state": "It is a future specialization/divergence concept.", "why_it_matters": "Confirm what changes are intentional and who authorizes them.", "recommended_action": "Keep unresolved consequences explicit.", "disposition": "unreviewed", "review_notes": "" }, { "number": 53, "id": "HR-053", "category": "Huey node and Monkey-Head-Project ontology", "category_scope": "Confirms the central public architecture before it is treated as approved.", "priority": "P1", "question": "Should bifurcation remain visible on the main project page?", "current_state": "It is secondary future architecture.", "why_it_matters": "Confirm public relevance.", "recommended_action": "Keep concise and link to noindex lineage if approved.", "disposition": "unreviewed", "review_notes": "" }, { "number": 54, "id": "HR-054", "category": "Huey node and Monkey-Head-Project ontology", "category_scope": "Confirms the central public architecture before it is treated as approved.", "priority": "P2", "question": "Does the node/collective diagram accurately show authority and service relationships?", "current_state": "The current diagram is explanatory, not runtime truth.", "why_it_matters": "Confirm every arrow and label.", "recommended_action": "Revise the diagram only after the definitions are approved.", "disposition": "unreviewed", "review_notes": "" }, { "number": 55, "id": "HR-055", "category": "Huey node and Monkey-Head-Project ontology", "category_scope": "Confirms the central public architecture before it is treated as approved.", "priority": "P2", "question": "Should organism, nation, or federation metaphors be used publicly?", "current_state": "Historical materials contain these metaphors.", "why_it_matters": "Confirm where they aid understanding and where they overclaim.", "recommended_action": "Use metaphors only with explicit non-literal framing.", "disposition": "unreviewed", "review_notes": "" }, { "number": 56, "id": "HR-056", "category": "Huey node and Monkey-Head-Project ontology", "category_scope": "Confirms the central public architecture before it is treated as approved.", "priority": "P2", "question": "Does the site clearly separate node validity, V1, and full target state?", "current_state": "They are separate but related concepts.", "why_it_matters": "Confirm acceptance criteria for each.", "recommended_action": "Create a three-column public status table if useful.", "disposition": "unreviewed", "review_notes": "" }, { "number": 57, "id": "HR-057", "category": "Huey V4 physical embodiment and hardware", "category_scope": "Requires direct Human-Counterpart confirmation because many details are lab-specific or provisional.", "priority": "P0", "question": "Is V3 the correct physical base identity for Huey V4?", "current_state": "The candidate says V3 is the base shell/body.", "why_it_matters": "Confirm the version naming and physical continuity.", "recommended_action": "Approve a version-lineage statement.", "disposition": "unreviewed", "review_notes": "" }, { "number": 58, "id": "HR-058", "category": "Huey V4 physical embodiment and hardware", "category_scope": "Requires direct Human-Counterpart confirmation because many details are lab-specific or provisional.", "priority": "P0", "question": "Is V2 the correct donor designation?", "current_state": "The candidate says V2 supplies salvageable material.", "why_it_matters": "Confirm which physical parts and records are V2.", "recommended_action": "Create a donor inventory before public specificity.", "disposition": "unreviewed", "review_notes": "" }, { "number": 59, "id": "HR-059", "category": "Huey V4 physical embodiment and hardware", "category_scope": "Requires direct Human-Counterpart confirmation because many details are lab-specific or provisional.", "priority": "P0", "question": "Which shell components physically exist today?", "current_state": "The site names the modified shell, mounted head, right hand, and fold-out surface.", "why_it_matters": "Confirm each observation and current condition.", "recommended_action": "Photograph and inventory the current state.", "disposition": "unreviewed", "review_notes": "" }, { "number": 60, "id": "HR-060", "category": "Huey V4 physical embodiment and hardware", "category_scope": "Requires direct Human-Counterpart confirmation because many details are lab-specific or provisional.", "priority": "P0", "question": "Is the monkey head structurally mounted, operational, symbolic, or all three?", "current_state": "The site treats it as mounted and identity-central.", "why_it_matters": "Confirm mechanical and functional status.", "recommended_action": "Use separate labels for presence and actuation capability.", "disposition": "unreviewed", "review_notes": "" }, { "number": 61, "id": "HR-061", "category": "Huey V4 physical embodiment and hardware", "category_scope": "Requires direct Human-Counterpart confirmation because many details are lab-specific or provisional.", "priority": "P0", "question": "Is the right hand physically mounted and what is its intended role?", "current_state": "The site reports a mounted right hand without claiming actuation.", "why_it_matters": "Confirm purpose and status.", "recommended_action": "Update captions and V4 plan.", "disposition": "unreviewed", "review_notes": "" }, { "number": 62, "id": "HR-062", "category": "Huey V4 physical embodiment and hardware", "category_scope": "Requires direct Human-Counterpart confirmation because many details are lab-specific or provisional.", "priority": "P0", "question": "What exactly is the fold-out interaction surface?", "current_state": "It exists but requires refinement.", "why_it_matters": "Confirm display, input, hinge, locking, reach, and cabling roles.", "recommended_action": "Document with measurements and photographs.", "disposition": "unreviewed", "review_notes": "" }, { "number": 63, "id": "HR-063", "category": "Huey V4 physical embodiment and hardware", "category_scope": "Requires direct Human-Counterpart confirmation because many details are lab-specific or provisional.", "priority": "P0", "question": "Is the current i9/TUF/Optane machine still the intended V4 kernel?", "current_state": "The v121.0 candidate says yes.", "why_it_matters": "Confirm current hardware and migration intent.", "recommended_action": "Reinventory before any public hardware table is approved.", "disposition": "unreviewed", "review_notes": "" }, { "number": 64, "id": "HR-064", "category": "Huey V4 physical embodiment and hardware", "category_scope": "Requires direct Human-Counterpart confirmation because many details are lab-specific or provisional.", "priority": "P0", "question": "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.", "why_it_matters": "Confirm by direct system inventory.", "recommended_action": "Publish only the observed CPU model.", "disposition": "unreviewed", "review_notes": "" }, { "number": 65, "id": "HR-065", "category": "Huey V4 physical embodiment and hardware", "category_scope": "Requires direct Human-Counterpart confirmation because many details are lab-specific or provisional.", "priority": "P0", "question": "Which ASUS TUF motherboard is actually installed?", "current_state": "Current documents and older memories may disagree.", "why_it_matters": "Confirm exact model and revision.", "recommended_action": "Record board model, BIOS, and photographs.", "disposition": "unreviewed", "review_notes": "" }, { "number": 66, "id": "HR-066", "category": "Huey V4 physical embodiment and hardware", "category_scope": "Requires direct Human-Counterpart confirmation because many details are lab-specific or provisional.", "priority": "P0", "question": "What is the current Optane/storage configuration?", "current_state": "The candidate references an Optane kernel; historical records contain multiple layouts.", "why_it_matters": "Confirm devices, RAID level, health, and role.", "recommended_action": "Generate a current storage inventory.", "disposition": "unreviewed", "review_notes": "" }, { "number": 67, "id": "HR-067", "category": "Huey V4 physical embodiment and hardware", "category_scope": "Requires direct Human-Counterpart confirmation because many details are lab-specific or provisional.", "priority": "P0", "question": "Is a four-GPU layout still the active working direction?", "current_state": "The candidate says yes but remains provisional.", "why_it_matters": "Confirm target count.", "recommended_action": "Keep provisional until fit, lanes, power, and cooling are measured.", "disposition": "unreviewed", "review_notes": "" }, { "number": 68, "id": "HR-068", "category": "Huey V4 physical embodiment and hardware", "category_scope": "Requires direct Human-Counterpart confirmation because many details are lab-specific or provisional.", "priority": "P0", "question": "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.", "why_it_matters": "Confirm current procurement thinking.", "recommended_action": "Update or remove before public approval if no longer current.", "disposition": "unreviewed", "review_notes": "" }, { "number": 69, "id": "HR-069", "category": "Huey V4 physical embodiment and hardware", "category_scope": "Requires direct Human-Counterpart confirmation because many details are lab-specific or provisional.", "priority": "P0", "question": "Have any V100 cards been acquired, reserved, or tested?", "current_state": "The site does not claim acquisition.", "why_it_matters": "Confirm actual status.", "recommended_action": "Add evidence or retain “candidate only.”", "disposition": "unreviewed", "review_notes": "" }, { "number": 70, "id": "HR-070", "category": "Huey V4 physical embodiment and hardware", "category_scope": "Requires direct Human-Counterpart confirmation because many details are lab-specific or provisional.", "priority": "P0", "question": "Which V100 form factor is under consideration?", "current_state": "PCIe versus SXM affects feasibility.", "why_it_matters": "Confirm exact variant.", "recommended_action": "Do not publish compatibility claims without the variant.", "disposition": "unreviewed", "review_notes": "" }, { "number": 71, "id": "HR-071", "category": "Huey V4 physical embodiment and hardware", "category_scope": "Requires direct Human-Counterpart confirmation because many details are lab-specific or provisional.", "priority": "P0", "question": "What is the existing utility GPU?", "current_state": "Older records mention RX 5500 XT 8 GB.", "why_it_matters": "Confirm actual current device and role.", "recommended_action": "Inventory by PCI ID and photograph.", "disposition": "unreviewed", "review_notes": "" }, { "number": 72, "id": "HR-072", "category": "Huey V4 physical embodiment and hardware", "category_scope": "Requires direct Human-Counterpart confirmation because many details are lab-specific or provisional.", "priority": "P0", "question": "Can the motherboard expose the required lanes and slots?", "current_state": "Feasibility is unresolved.", "why_it_matters": "Confirm physical and electrical topology.", "recommended_action": "Produce a lane map before procurement.", "disposition": "unreviewed", "review_notes": "" }, { "number": 73, "id": "HR-073", "category": "Huey V4 physical embodiment and hardware", "category_scope": "Requires direct Human-Counterpart confirmation because many details are lab-specific or provisional.", "priority": "P0", "question": "What power architecture is intended?", "current_state": "Historical notes range from multiple PSUs to unresolved placement.", "why_it_matters": "Confirm PSU count, ratings, synchronization, grounding, and protection.", "recommended_action": "Create an electrical plan reviewed for safety.", "disposition": "unreviewed", "review_notes": "" }, { "number": 74, "id": "HR-074", "category": "Huey V4 physical embodiment and hardware", "category_scope": "Requires direct Human-Counterpart confirmation because many details are lab-specific or provisional.", "priority": "P0", "question": "What cooling strategy is physically feasible?", "current_state": "No installed multi-GPU cooling solution is claimed.", "why_it_matters": "Confirm airflow, heat load, enclosure, and noise constraints.", "recommended_action": "Measure and prototype before approval.", "disposition": "unreviewed", "review_notes": "" }, { "number": 75, "id": "HR-075", "category": "Huey V4 physical embodiment and hardware", "category_scope": "Requires direct Human-Counterpart confirmation because many details are lab-specific or provisional.", "priority": "P0", "question": "What safe shutdown and emergency-stop behavior is required?", "current_state": "Safety is a project requirement, not a proven implementation.", "why_it_matters": "Confirm hardware and software expectations.", "recommended_action": "Document fail-safe behavior before integration.", "disposition": "unreviewed", "review_notes": "" }, { "number": 76, "id": "HR-076", "category": "Huey V4 physical embodiment and hardware", "category_scope": "Requires direct Human-Counterpart confirmation because many details are lab-specific or provisional.", "priority": "P1", "question": "What is HueyPulse’s current status?", "current_state": "It appears in historical planning but is not active canon in v200.8.", "why_it_matters": "Confirm active, deferred, replaced, or retired.", "recommended_action": "Classify explicitly in v201.x.", "disposition": "unreviewed", "review_notes": "" }, { "number": 77, "id": "HR-077", "category": "Huey V4 physical embodiment and hardware", "category_scope": "Requires direct Human-Counterpart confirmation because many details are lab-specific or provisional.", "priority": "P1", "question": "What role should Arduino, Raspberry Pi, or another controller play?", "current_state": "Historical plans vary.", "why_it_matters": "Confirm current low-level control direction.", "recommended_action": "Avoid naming a board until selected.", "disposition": "unreviewed", "review_notes": "" }, { "number": 78, "id": "HR-078", "category": "Huey V4 physical embodiment and hardware", "category_scope": "Requires direct Human-Counterpart confirmation because many details are lab-specific or provisional.", "priority": "P1", "question": "What sensors, lights, fans, batteries, screens, and switches are presently installed?", "current_state": "Older records contain detailed but potentially stale inventories.", "why_it_matters": "Confirm each through a current physical audit.", "recommended_action": "Publish a dated hardware manifest.", "disposition": "unreviewed", "review_notes": "" }, { "number": 79, "id": "HR-079", "category": "Huey V4 physical embodiment and hardware", "category_scope": "Requires direct Human-Counterpart confirmation because many details are lab-specific or provisional.", "priority": "P1", "question": "What distinguishes assembled, integrated, operational, validated, and complete?", "current_state": "No final V4 acceptance taxonomy is locked.", "why_it_matters": "Confirm evidence thresholds.", "recommended_action": "Add status definitions to the V4 plan.", "disposition": "unreviewed", "review_notes": "" }, { "number": 80, "id": "HR-080", "category": "Huey V4 physical embodiment and hardware", "category_scope": "Requires direct Human-Counterpart confirmation because many details are lab-specific or provisional.", "priority": "P1", "question": "What baseline must be captured before moving the current compute kernel?", "current_state": "The candidate calls for inventory, backup, thermals, and rollback.", "why_it_matters": "Confirm the complete checklist.", "recommended_action": "Do not disassemble until the gate is signed off.", "disposition": "unreviewed", "review_notes": "" }, { "number": 81, "id": "HR-081", "category": "Huey V4 physical embodiment and hardware", "category_scope": "Requires direct Human-Counterpart confirmation because many details are lab-specific or provisional.", "priority": "P2", "question": "Should detailed hardware specifications be public?", "current_state": "Transparency helps replication but may expose private or unsafe details.", "why_it_matters": "Confirm desired disclosure level.", "recommended_action": "Publish only what supports the project’s public mission safely.", "disposition": "unreviewed", "review_notes": "" }, { "number": 82, "id": "HR-082", "category": "Software, runtime, V1, and evidence", "category_scope": "Confirms what is implemented versus merely selected.", "priority": "P0", "question": "What recurring useful function will define V1?", "current_state": "V1 remains intentionally open.", "why_it_matters": "Confirm the problem, user, context, and evidence threshold.", "recommended_action": "Do not declare V1 until the function is repeatable.", "disposition": "unreviewed", "review_notes": "" }, { "number": 83, "id": "HR-083", "category": "Software, runtime, V1, and evidence", "category_scope": "Confirms what is implemented versus merely selected.", "priority": "P0", "question": "Is the MP3-to-log path still the active foundation proof?", "current_state": "The repository retains it as foundation evidence.", "why_it_matters": "Confirm current status and whether it has been run successfully.", "recommended_action": "Record a dated run or classify it as pending.", "disposition": "unreviewed", "review_notes": "" }, { "number": 84, "id": "HR-084", "category": "Software, runtime, V1, and evidence", "category_scope": "Confirms what is implemented versus merely selected.", "priority": "P0", "question": "Which transcription engine and model are current?", "current_state": "faster-whisper is the working direction; model and compute path remain open.", "why_it_matters": "Confirm exact engine, model, compute type, and fallback.", "recommended_action": "Publish measured settings, not assumptions.", "disposition": "unreviewed", "review_notes": "" }, { "number": 85, "id": "HR-085", "category": "Software, runtime, V1, and evidence", "category_scope": "Confirms what is implemented versus merely selected.", "priority": "P0", "question": "Is CPU-first transcription still the practical assignment?", "current_state": "The v121.0 candidate says yes pending measurement.", "why_it_matters": "Confirm on current hardware.", "recommended_action": "Benchmark and record results.", "disposition": "unreviewed", "review_notes": "" }, { "number": 86, "id": "HR-086", "category": "Software, runtime, V1, and evidence", "category_scope": "Confirms what is implemented versus merely selected.", "priority": "P0", "question": "Which cognition provider or local model is currently used?", "current_state": "The architecture is provider-swappable and does not lock one provider.", "why_it_matters": "Confirm actual current path and public disclosure.", "recommended_action": "Separate current provider from architectural dependency.", "disposition": "unreviewed", "review_notes": "" }, { "number": 87, "id": "HR-087", "category": "Software, runtime, V1, and evidence", "category_scope": "Confirms what is implemented versus merely selected.", "priority": "P0", "question": "Has a real provider run been completed through the proof loop?", "current_state": "The retained runbook does not establish one.", "why_it_matters": "Confirm evidence.", "recommended_action": "Link a redacted structured log or keep the non-claim.", "disposition": "unreviewed", "review_notes": "" }, { "number": 88, "id": "HR-088", "category": "Software, runtime, V1, and evidence", "category_scope": "Confirms what is implemented versus merely selected.", "priority": "P0", "question": "What logs are currently produced?", "current_state": "Repository code supports structured JSON/JSONL and optional shadow traces.", "why_it_matters": "Confirm fields, storage location, and secret handling.", "recommended_action": "Review a real redacted sample.", "disposition": "unreviewed", "review_notes": "" }, { "number": 89, "id": "HR-089", "category": "Software, runtime, V1, and evidence", "category_scope": "Confirms what is implemented versus merely selected.", "priority": "P0", "question": "Is HIMS an implemented runtime, a shadow trace, a foundation, or doctrine?", "current_state": "The site says foundation/non-controlling; repository contains shadow implementation.", "why_it_matters": "Confirm the approved wording.", "recommended_action": "Use one status across all pages.", "disposition": "unreviewed", "review_notes": "" }, { "number": 90, "id": "HR-090", "category": "Software, runtime, V1, and evidence", "category_scope": "Confirms what is implemented versus merely selected.", "priority": "P0", "question": "What is PyHuey’s current working state?", "current_state": "Repository direction calls it primary GUI/core runtime, with consolidation incomplete.", "why_it_matters": "Confirm what launches and what workflows function.", "recommended_action": "Publish a capability table with evidence.", "disposition": "unreviewed", "review_notes": "" }, { "number": 91, "id": "HR-091", "category": "Software, runtime, V1, and evidence", "category_scope": "Confirms what is implemented versus merely selected.", "priority": "P0", "question": "What CLI recovery functions are required?", "current_state": "The project intends a recovery-capable CLI.", "why_it_matters": "Confirm commands and acceptance tests.", "recommended_action": "Document only implemented commands.", "disposition": "unreviewed", "review_notes": "" }, { "number": 92, "id": "HR-092", "category": "Software, runtime, V1, and evidence", "category_scope": "Confirms what is implemented versus merely selected.", "priority": "P1", "question": "Is the current Python support window still >=3.13,<3.14?", "current_state": "Current pyproject retains that contract.", "why_it_matters": "Confirm whether v201.x should repeat it publicly.", "recommended_action": "Update from repository only, not memory.", "disposition": "unreviewed", "review_notes": "" }, { "number": 93, "id": "HR-093", "category": "Software, runtime, V1, and evidence", "category_scope": "Confirms what is implemented versus merely selected.", "priority": "P1", "question": "Is the distribution/import distinction still hueyos versus huey?", "current_state": "Current package name is hueyos while imports remain huey.", "why_it_matters": "Confirm migration status.", "recommended_action": "Keep the drift visible until code and docs agree.", "disposition": "unreviewed", "review_notes": "" }, { "number": 94, "id": "HR-094", "category": "Software, runtime, V1, and evidence", "category_scope": "Confirms what is implemented versus merely selected.", "priority": "P1", "question": "Which operating systems are active on Huey and LabTech devices?", "current_state": "Historical notes conflict across Debian, Windows, and decommissioned systems.", "why_it_matters": "Confirm each device from direct observation.", "recommended_action": "Create a dated device-role table.", "disposition": "unreviewed", "review_notes": "" }, { "number": 95, "id": "HR-095", "category": "Software, runtime, V1, and evidence", "category_scope": "Confirms what is implemented versus merely selected.", "priority": "P1", "question": "Is the Lenovo Legion Go part of Huey, LabTech, lineage, or no official role?", "current_state": "Sources have changed repeatedly.", "why_it_matters": "Confirm current classification.", "recommended_action": "Remove stale role claims across the site.", "disposition": "unreviewed", "review_notes": "" }, { "number": 96, "id": "HR-096", "category": "Software, runtime, V1, and evidence", "category_scope": "Confirms what is implemented versus merely selected.", "priority": "P1", "question": "Is the ASUS FX505DT still active LabTech?", "current_state": "Repository v120.3 says yes.", "why_it_matters": "Confirm current hardware, OS, and role.", "recommended_action": "Update the public table only after confirmation.", "disposition": "unreviewed", "review_notes": "" }, { "number": 97, "id": "HR-097", "category": "Software, runtime, V1, and evidence", "category_scope": "Confirms what is implemented versus merely selected.", "priority": "P1", "question": "What is the current status of the Briefcase?", "current_state": "It is described as field terminal/LabTech with limited authority in different sources.", "why_it_matters": "Confirm hardware, OS, and actual use.", "recommended_action": "Choose one current classification.", "disposition": "unreviewed", "review_notes": "" }, { "number": 98, "id": "HR-098", "category": "Software, runtime, V1, and evidence", "category_scope": "Confirms what is implemented versus merely selected.", "priority": "P1", "question": "What is the current status of the 2017 iMac 5K?", "current_state": "Repository v120.3 says decommissioned; older continuity notes assign active LabTech roles.", "why_it_matters": "Confirm current physical and operational state.", "recommended_action": "Correct every public mention together.", "disposition": "unreviewed", "review_notes": "" }, { "number": 99, "id": "HR-099", "category": "Software, runtime, V1, and evidence", "category_scope": "Confirms what is implemented versus merely selected.", "priority": "P1", "question": "What external-service dependency is acceptable for a valid node?", "current_state": "This remains unresolved.", "why_it_matters": "Confirm offline-first threshold and API fallback policy.", "recommended_action": "Add measurable dependency limits.", "disposition": "unreviewed", "review_notes": "" }, { "number": 100, "id": "HR-100", "category": "Software, runtime, V1, and evidence", "category_scope": "Confirms what is implemented versus merely selected.", "priority": "P2", "question": "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.", "why_it_matters": "Confirm the minimum per claim type.", "recommended_action": "Add evidence labels to technical pages.", "disposition": "unreviewed", "review_notes": "" }, { "number": 101, "id": "HR-101", "category": "Software, runtime, V1, and evidence", "category_scope": "Confirms what is implemented versus merely selected.", "priority": "P2", "question": "How should failures be presented publicly?", "current_state": "Failed runs should leave attributable records.", "why_it_matters": "Confirm privacy-safe reporting.", "recommended_action": "Publish summaries, not secret-bearing logs.", "disposition": "unreviewed", "review_notes": "" }, { "number": 102, "id": "HR-102", "category": "Repository, README, master plan, and source synchronization", "category_scope": "Determines how the website candidate becomes or does not become repository canon.", "priority": "P0", "question": "Should v121.0 remain the proposed next master-plan version?", "current_state": "The candidate uses v121.0 because the top-level ontology changes.", "why_it_matters": "Confirm version number.", "recommended_action": "Rename before repository submission if needed.", "disposition": "unreviewed", "review_notes": "" }, { "number": 103, "id": "HR-103", "category": "Repository, README, master plan, and source synchronization", "category_scope": "Determines how the website candidate becomes or does not become repository canon.", "priority": "P0", "question": "Is master-plan-v121.0 approved in substance?", "current_state": "It is packaged as a candidate pending synchronization and acceptance.", "why_it_matters": "Review every top-level object and non-claim.", "recommended_action": "Record accepted, revised, or rejected status.", "disposition": "unreviewed", "review_notes": "" }, { "number": 104, "id": "HR-104", "category": "Repository, README, master plan, and source synchronization", "category_scope": "Determines how the website candidate becomes or does not become repository canon.", "priority": "P0", "question": "Should README.md be rewritten to the node-first model?", "current_state": "Repository README remains v120.3.", "why_it_matters": "Confirm synchronization intent.", "recommended_action": "Stage a separate repository PR after Human review.", "disposition": "unreviewed", "review_notes": "" }, { "number": 105, "id": "HR-105", "category": "Repository, README, master plan, and source synchronization", "category_scope": "Determines how the website candidate becomes or does not become repository canon.", "priority": "P0", "question": "Should master-plan-v120.3.json remain immutable?", "current_state": "It is the predecessor record and still self-labels proposed_in_pr.", "why_it_matters": "Confirm provenance policy.", "recommended_action": "Leave unchanged or perform a separate metadata-only correction.", "disposition": "unreviewed", "review_notes": "" }, { "number": 106, "id": "HR-106", "category": "Repository, README, master plan, and source synchronization", "category_scope": "Determines how the website candidate becomes or does not become repository canon.", "priority": "P0", "question": "How should the stale proposed_in_pr status be handled?", "current_state": "The file is merged but self-status is stale.", "why_it_matters": "Confirm whether to correct or preserve.", "recommended_action": "Document the decision explicitly.", "disposition": "unreviewed", "review_notes": "" }, { "number": 107, "id": "HR-107", "category": "Repository, README, master plan, and source synchronization", "category_scope": "Determines how the website candidate becomes or does not become repository canon.", "priority": "P0", "question": "Is 2b613238 the correct repository head for the review package?", "current_state": "It is the current head checked during v200.8 assembly.", "why_it_matters": "Confirm no later commit must be incorporated before upload.", "recommended_action": "Refresh the snapshot if main advances before deployment.", "disposition": "unreviewed", "review_notes": "" }, { "number": 108, "id": "HR-108", "category": "Repository, README, master plan, and source synchronization", "category_scope": "Determines how the website candidate becomes or does not become repository canon.", "priority": "P1", "question": "Should dependency-only commits change the visible source chip?", "current_state": "v200.8 shows current head and a separate architecture-source commit.", "why_it_matters": "Confirm this two-commit model.", "recommended_action": "Retain if it improves truthfulness.", "disposition": "unreviewed", "review_notes": "" }, { "number": 109, "id": "HR-109", "category": "Repository, README, master plan, and source synchronization", "category_scope": "Determines how the website candidate becomes or does not become repository canon.", "priority": "P1", "question": "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.", "why_it_matters": "Confirm completeness.", "recommended_action": "Add or remove files based on real authority.", "disposition": "unreviewed", "review_notes": "" }, { "number": 110, "id": "HR-110", "category": "Repository, README, master plan, and source synchronization", "category_scope": "Determines how the website candidate becomes or does not become repository canon.", "priority": "P1", "question": "Should repository binary identity imagery be imported into the site?", "current_state": "v200.x deliberately did not bulk-import it.", "why_it_matters": "Confirm visual strategy.", "recommended_action": "Import only if it clarifies current embodiment.", "disposition": "unreviewed", "review_notes": "" }, { "number": 111, "id": "HR-111", "category": "Repository, README, master plan, and source synchronization", "category_scope": "Determines how the website candidate becomes or does not become repository canon.", "priority": "P1", "question": "Does the Repository Ledger expose too much technical detail?", "current_state": "It is transparent but dense.", "why_it_matters": "Confirm public audience.", "recommended_action": "Keep full data downloadable and simplify the page if needed.", "disposition": "unreviewed", "review_notes": "" }, { "number": 112, "id": "HR-112", "category": "Repository, README, master plan, and source synchronization", "category_scope": "Determines how the website candidate becomes or does not become repository canon.", "priority": "P1", "question": "Should the source chip remain on every page?", "current_state": "It provides ubiquitous provenance.", "why_it_matters": "Confirm visual burden and usefulness.", "recommended_action": "Retain, reduce, or make optional based on review.", "disposition": "unreviewed", "review_notes": "" }, { "number": 113, "id": "HR-113", "category": "Repository, README, master plan, and source synchronization", "category_scope": "Determines how the website candidate becomes or does not become repository canon.", "priority": "P1", "question": "Does the six-layer truth model remain approved?", "current_state": "Current reality, direction, provisional, unresolved, target, and lineage structure the site.", "why_it_matters": "Confirm labels and meanings.", "recommended_action": "Lock the model before v201.x rewriting.", "disposition": "unreviewed", "review_notes": "" }, { "number": 114, "id": "HR-114", "category": "Repository, README, master plan, and source synchronization", "category_scope": "Determines how the website candidate becomes or does not become repository canon.", "priority": "P1", "question": "Do the four source origins remain sufficient?", "current_state": "Current session, repository, lab, and lineage are used.", "why_it_matters": "Confirm whether public testimony or external sources need a distinct origin.", "recommended_action": "Add only if it changes review decisions.", "disposition": "unreviewed", "review_notes": "" }, { "number": 115, "id": "HR-115", "category": "Repository, README, master plan, and source synchronization", "category_scope": "Determines how the website candidate becomes or does not become repository canon.", "priority": "P2", "question": "Should the website package include repository snapshots at all?", "current_state": "They support offline source transparency.", "why_it_matters": "Confirm size and maintenance value.", "recommended_action": "Keep static snapshots if the update burden is acceptable.", "disposition": "unreviewed", "review_notes": "" }, { "number": 116, "id": "HR-116", "category": "Repository, README, master plan, and source synchronization", "category_scope": "Determines how the website candidate becomes or does not become repository canon.", "priority": "P2", "question": "What happens when repository main changes during v201.x?", "current_state": "No refresh cadence is defined.", "why_it_matters": "Confirm snapshot timing.", "recommended_action": "Pin at review start and refresh once before release candidate.", "disposition": "unreviewed", "review_notes": "" }, { "number": 117, "id": "HR-117", "category": "Public identity, biography, and privacy", "category_scope": "Protects the boundary between public biography and AI-facing continuity material.", "priority": "P0", "question": "Is “Human-Counterpart” appropriate public terminology?", "current_state": "The About page uses it in a bounded way.", "why_it_matters": "Confirm meaning, capitalization, and audience comprehension.", "recommended_action": "Approve a one-sentence public definition or remove the term.", "disposition": "unreviewed", "review_notes": "" }, { "number": 118, "id": "HR-118", "category": "Public identity, biography, and privacy", "category_scope": "Protects the boundary between public biography and AI-facing continuity material.", "priority": "P0", "question": "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.", "why_it_matters": "Confirm each label.", "recommended_action": "Remove any title Dylan would not publicly claim.", "disposition": "unreviewed", "review_notes": "" }, { "number": 119, "id": "HR-119", "category": "Public identity, biography, and privacy", "category_scope": "Protects the boundary between public biography and AI-facing continuity material.", "priority": "P0", "question": "Which biographical facts are approved for public display?", "current_state": "v200.x intentionally avoids publishing the full continuity profile.", "why_it_matters": "Confirm a minimal approved biography.", "recommended_action": "Create a public-bio source record separate from private context.", "disposition": "unreviewed", "review_notes": "" }, { "number": 120, "id": "HR-120", "category": "Public identity, biography, and privacy", "category_scope": "Protects the boundary between public biography and AI-facing continuity material.", "priority": "P0", "question": "Should location, home-workspace, family, routine, or resource constraints be public?", "current_state": "These details may aid context but carry privacy implications.", "why_it_matters": "Confirm each category.", "recommended_action": "Default to omission unless it materially serves the public narrative.", "disposition": "unreviewed", "review_notes": "" }, { "number": 121, "id": "HR-121", "category": "Public identity, biography, and privacy", "category_scope": "Protects the boundary between public biography and AI-facing continuity material.", "priority": "P0", "question": "Which email addresses should be public?", "current_state": "The rail currently links admin@dlrp.ca.", "why_it_matters": "Confirm mailbox, spam tolerance, and preferred contact path.", "recommended_action": "Use one monitored public address.", "disposition": "unreviewed", "review_notes": "" }, { "number": 122, "id": "HR-122", "category": "Public identity, biography, and privacy", "category_scope": "Protects the boundary between public biography and AI-facing continuity material.", "priority": "P0", "question": "Are GitHub and YouTube account links correct and desired?", "current_state": "The rail links to DylanLRPollock and @DLRP1995.", "why_it_matters": "Confirm current handles and public intent.", "recommended_action": "Update or remove broken/unwanted profiles.", "disposition": "unreviewed", "review_notes": "" }, { "number": 123, "id": "HR-123", "category": "Public identity, biography, and privacy", "category_scope": "Protects the boundary between public biography and AI-facing continuity material.", "priority": "P1", "question": "Should the site call Dylan the sole canon authority?", "current_state": "This is current project governance, not a permanent public identity claim.", "why_it_matters": "Confirm wording and scope.", "recommended_action": "Limit the statement to current project decisions.", "disposition": "unreviewed", "review_notes": "" }, { "number": 124, "id": "HR-124", "category": "Public identity, biography, and privacy", "category_scope": "Protects the boundary between public biography and AI-facing continuity material.", "priority": "P1", "question": "Should Atlas be named publicly?", "current_state": "The architecture documents clarify Atlas is external to Huey.", "why_it_matters": "Confirm whether that distinction belongs on public pages or only docs.", "recommended_action": "Keep it where role confusion is likely.", "disposition": "unreviewed", "review_notes": "" }, { "number": 125, "id": "HR-125", "category": "Public identity, biography, and privacy", "category_scope": "Protects the boundary between public biography and AI-facing continuity material.", "priority": "P1", "question": "Do the About images accurately represent Dylan and current public identity?", "current_state": "The page uses selected car, portrait, dog, lab, and music context.", "why_it_matters": "Confirm consent, captions, crop, and date sensitivity.", "recommended_action": "Approve each image individually.", "disposition": "unreviewed", "review_notes": "" }, { "number": 126, "id": "HR-126", "category": "Public identity, biography, and privacy", "category_scope": "Protects the boundary between public biography and AI-facing continuity material.", "priority": "P1", "question": "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.", "why_it_matters": "Confirm whether the masters exist elsewhere.", "recommended_action": "Add to the private media warehouse before further derivatives.", "disposition": "unreviewed", "review_notes": "" }, { "number": 127, "id": "HR-127", "category": "Public identity, biography, and privacy", "category_scope": "Protects the boundary between public biography and AI-facing continuity material.", "priority": "P1", "question": "Should the site disclose the project’s approximate age?", "current_state": "Older records say roughly a decade.", "why_it_matters": "Confirm start date or preferred wording.", "recommended_action": "Use a bounded phrase unless a date is documented.", "disposition": "unreviewed", "review_notes": "" }, { "number": 128, "id": "HR-128", "category": "Public identity, biography, and privacy", "category_scope": "Protects the boundary between public biography and AI-facing continuity material.", "priority": "P1", "question": "Should childhood wonder, personal meaning, or emotional attachment be public?", "current_state": "These motivations are important but easy to over-mythologize.", "why_it_matters": "Confirm the desired level of personal voice.", "recommended_action": "Use first-person wording approved by Dylan.", "disposition": "unreviewed", "review_notes": "" }, { "number": 129, "id": "HR-129", "category": "Public identity, biography, and privacy", "category_scope": "Protects the boundary between public biography and AI-facing continuity material.", "priority": "P2", "question": "Should the About page mention employment or organization claims?", "current_state": "No verified employer/company biography should be inferred.", "why_it_matters": "Confirm any professional affiliation explicitly.", "recommended_action": "Avoid unsupported company language.", "disposition": "unreviewed", "review_notes": "" }, { "number": 130, "id": "HR-130", "category": "Public identity, biography, and privacy", "category_scope": "Protects the boundary between public biography and AI-facing continuity material.", "priority": "P2", "question": "Should personal pronouns and first-person voice increase in v201.x?", "current_state": "v200.x is largely documentary and third-person.", "why_it_matters": "Confirm desired voice by page type.", "recommended_action": "Define a voice guide before rewriting.", "disposition": "unreviewed", "review_notes": "" }, { "number": 131, "id": "HR-131", "category": "Images, assets, captions, and visual evidence", "category_scope": "Confirms that deliberate asset placement is also factually and personally approved.", "priority": "P0", "question": "Does every current-embodiment image actually show current hardware?", "current_state": "v200.x uses curated Huey shell images with role labels.", "why_it_matters": "Confirm image date, version, and current status.", "recommended_action": "Correct tags and captions using an approved photo inventory.", "disposition": "unreviewed", "review_notes": "" }, { "number": 132, "id": "HR-132", "category": "Images, assets, captions, and visual evidence", "category_scope": "Confirms that deliberate asset placement is also factually and personally approved.", "priority": "P0", "question": "Which images show V2, V3, V4 direction, donor material, or undated lineage?", "current_state": "Numeric version mapping was intentionally cautious.", "why_it_matters": "Confirm each mapping.", "recommended_action": "Do not publish version labels from filenames alone.", "disposition": "unreviewed", "review_notes": "" }, { "number": 133, "id": "HR-133", "category": "Images, assets, captions, and visual evidence", "category_scope": "Confirms that deliberate asset placement is also factually and personally approved.", "priority": "P0", "question": "Is the full-shell Huey hero the correct current public image?", "current_state": "It leads the Huey route.", "why_it_matters": "Confirm current relevance and crop.", "recommended_action": "Approve or replace with a more recent physical record.", "disposition": "unreviewed", "review_notes": "" }, { "number": 134, "id": "HR-134", "category": "Images, assets, captions, and visual evidence", "category_scope": "Confirms that deliberate asset placement is also factually and personally approved.", "priority": "P0", "question": "Do the monkey-head images represent current identity, lineage, or reference parts?", "current_state": "Several images show different head states.", "why_it_matters": "Confirm each role.", "recommended_action": "Use distinct captions and categories.", "disposition": "unreviewed", "review_notes": "" }, { "number": 135, "id": "HR-135", "category": "Images, assets, captions, and visual evidence", "category_scope": "Confirms that deliberate asset placement is also factually and personally approved.", "priority": "P1", "question": "Are the route hero crops correct on desktop and mobile?", "current_state": "Focal-point-aware derivatives are used.", "why_it_matters": "Confirm faces, hardware, and symbolic elements are not cropped misleadingly.", "recommended_action": "Review all 40 route fields in a contact sheet.", "disposition": "unreviewed", "review_notes": "" }, { "number": 136, "id": "HR-136", "category": "Images, assets, captions, and visual evidence", "category_scope": "Confirms that deliberate asset placement is also factually and personally approved.", "priority": "P1", "question": "Are social-preview crops and captions appropriate?", "current_state": "Every route has a 1200 × 630 preview.", "why_it_matters": "Confirm public sharing appearance.", "recommended_action": "Test representative links on major platforms.", "disposition": "unreviewed", "review_notes": "" }, { "number": 137, "id": "HR-137", "category": "Images, assets, captions, and visual evidence", "category_scope": "Confirms that deliberate asset placement is also factually and personally approved.", "priority": "P1", "question": "Should the car-in-field master remain the permanent site hero indefinitely?", "current_state": "It is a durable preference.", "why_it_matters": "Confirm whether v201.x changes its treatment only, not identity.", "recommended_action": "Lock the asset and approved derivative policy.", "disposition": "unreviewed", "review_notes": "" }, { "number": 138, "id": "HR-138", "category": "Images, assets, captions, and visual evidence", "category_scope": "Confirms that deliberate asset placement is also factually and personally approved.", "priority": "P1", "question": "Are dog images correctly attributed to names and breeds?", "current_state": "Pages rely on owner-provided context and cautious breed wording.", "why_it_matters": "Confirm each dog, name, breed, and photo.", "recommended_action": "Update captions as personal records.", "disposition": "unreviewed", "review_notes": "" }, { "number": 139, "id": "HR-139", "category": "Images, assets, captions, and visual evidence", "category_scope": "Confirms that deliberate asset placement is also factually and personally approved.", "priority": "P1", "question": "Are any film, television, concert, or third-party images rights-sensitive?", "current_state": "v200.x excluded many generic reference stills.", "why_it_matters": "Confirm the remaining media rights basis.", "recommended_action": "Remove or replace uncertain third-party material.", "disposition": "unreviewed", "review_notes": "" }, { "number": 140, "id": "HR-140", "category": "Images, assets, captions, and visual evidence", "category_scope": "Confirms that deliberate asset placement is also factually and personally approved.", "priority": "P1", "question": "Should image provenance be visible to ordinary visitors?", "current_state": "Visual Atlas exposes source paths and categories.", "why_it_matters": "Confirm desired transparency.", "recommended_action": "Keep technical provenance in the atlas if page captions should stay simple.", "disposition": "unreviewed", "review_notes": "" }, { "number": 141, "id": "HR-141", "category": "Images, assets, captions, and visual evidence", "category_scope": "Confirms that deliberate asset placement is also factually and personally approved.", "priority": "P1", "question": "Are alt texts descriptive without making unverified claims?", "current_state": "Static validation confirms presence, not factual correctness.", "why_it_matters": "Human-review every identity and hardware alt text.", "recommended_action": "Approve alt text alongside captions.", "disposition": "unreviewed", "review_notes": "" }, { "number": 142, "id": "HR-142", "category": "Images, assets, captions, and visual evidence", "category_scope": "Confirms that deliberate asset placement is also factually and personally approved.", "priority": "P1", "question": "Do any images reveal private locations, documents, serial numbers, screens, or personal data?", "current_state": "No automated privacy-image audit can guarantee this.", "why_it_matters": "Inspect full resolution manually.", "recommended_action": "Redact, crop, or remove sensitive details.", "disposition": "unreviewed", "review_notes": "" }, { "number": 143, "id": "HR-143", "category": "Images, assets, captions, and visual evidence", "category_scope": "Confirms that deliberate asset placement is also factually and personally approved.", "priority": "P2", "question": "Should Visual Atlas expose full-resolution lightbox targets?", "current_state": "It currently supports larger images.", "why_it_matters": "Confirm bandwidth, privacy, and rights impact.", "recommended_action": "Use limited-resolution public derivatives if needed.", "disposition": "unreviewed", "review_notes": "" }, { "number": 144, "id": "HR-144", "category": "Images, assets, captions, and visual evidence", "category_scope": "Confirms that deliberate asset placement is also factually and personally approved.", "priority": "P2", "question": "Are system font stacks visually acceptable on Dylan’s target devices?", "current_state": "No font binaries or remote services are used.", "why_it_matters": "Confirm Windows, macOS, Linux, iOS, and Android rendering.", "recommended_action": "Adjust stack order or metrics, not payload, unless explicitly approved.", "disposition": "unreviewed", "review_notes": "" }, { "number": 145, "id": "HR-145", "category": "Personal archives, dogs, playlist, media, and adjacent projects", "category_scope": "Confirms non-Huey content and mutable external facts.", "priority": "P0", "question": "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.", "why_it_matters": "Confirm live count on review date.", "recommended_action": "Display live and archival counts separately with dates.", "disposition": "unreviewed", "review_notes": "" }, { "number": 146, "id": "HR-146", "category": "Personal archives, dogs, playlist, media, and adjacent projects", "category_scope": "Confirms non-Huey content and mutable external facts.", "priority": "P0", "question": "Is the playlist title and public link still correct?", "current_state": "The site uses the established title and archived entries.", "why_it_matters": "Confirm current YouTube playlist identity.", "recommended_action": "Update the link or mark the page archival.", "disposition": "unreviewed", "review_notes": "" }, { "number": 147, "id": "HR-147", "category": "Personal archives, dogs, playlist, media, and adjacent projects", "category_scope": "Confirms non-Huey content and mutable external facts.", "priority": "P1", "question": "Are all 463 archived playlist rows accurate enough for public display?", "current_state": "The file was parsed but not independently verified row by row.", "why_it_matters": "Confirm correction policy.", "recommended_action": "Sample, correct known errors, and label provenance.", "disposition": "unreviewed", "review_notes": "" }, { "number": 148, "id": "HR-148", "category": "Personal archives, dogs, playlist, media, and adjacent projects", "category_scope": "Confirms non-Huey content and mutable external facts.", "priority": "P1", "question": "Should playlist views or other mutable platform metrics be shown?", "current_state": "Mutable totals can become stale quickly.", "why_it_matters": "Confirm value.", "recommended_action": "Prefer dated snapshots or omit.", "disposition": "unreviewed", "review_notes": "" }, { "number": 149, "id": "HR-149", "category": "Personal archives, dogs, playlist, media, and adjacent projects", "category_scope": "Confirms non-Huey content and mutable external facts.", "priority": "P1", "question": "Are downloadable playlist exports current and privacy-safe?", "current_state": "The site provides archive exports.", "why_it_matters": "Confirm files, format, and metadata.", "recommended_action": "Regenerate or label them with dates.", "disposition": "unreviewed", "review_notes": "" }, { "number": 150, "id": "HR-150", "category": "Personal archives, dogs, playlist, media, and adjacent projects", "category_scope": "Confirms non-Huey content and mutable external facts.", "priority": "P1", "question": "Should the Sweeney Todd restoration project be represented publicly?", "current_state": "It is significant continuity context but not a main current route.", "why_it_matters": "Confirm copyright, scope, and public value.", "recommended_action": "Add only rights-safe process documentation.", "disposition": "unreviewed", "review_notes": "" }, { "number": 151, "id": "HR-151", "category": "Personal archives, dogs, playlist, media, and adjacent projects", "category_scope": "Confirms non-Huey content and mutable external facts.", "priority": "P1", "question": "Are Pinball project names, status, and claims accurate?", "current_state": "Dirty Leroy and The Executive are documented with first-person/project records.", "why_it_matters": "Confirm build dates, completion state, and specifications.", "recommended_action": "Correct page-by-page.", "disposition": "unreviewed", "review_notes": "" }, { "number": 152, "id": "HR-152", "category": "Personal archives, dogs, playlist, media, and adjacent projects", "category_scope": "Confirms non-Huey content and mutable external facts.", "priority": "P1", "question": "Are PlayStation build compatibility and historical claims accurate?", "current_state": "The page uses cautious wording after earlier fact audit.", "why_it_matters": "Confirm supported systems and current state.", "recommended_action": "Avoid universal compatibility claims.", "disposition": "unreviewed", "review_notes": "" }, { "number": 153, "id": "HR-153", "category": "Personal archives, dogs, playlist, media, and adjacent projects", "category_scope": "Confirms non-Huey content and mutable external facts.", "priority": "P1", "question": "Do Recipes belong in the public site?", "current_state": "They are a personal human lane.", "why_it_matters": "Confirm value and privacy.", "recommended_action": "Keep, expand, merge, or remove deliberately.", "disposition": "unreviewed", "review_notes": "" }, { "number": 154, "id": "HR-154", "category": "Personal archives, dogs, playlist, media, and adjacent projects", "category_scope": "Confirms non-Huey content and mutable external facts.", "priority": "P1", "question": "Are the dog pages a current household record, an archive, or both?", "current_state": "The site treats them as personal archive routes.", "why_it_matters": "Confirm current/archival wording.", "recommended_action": "Use dates or archive labels where needed.", "disposition": "unreviewed", "review_notes": "" }, { "number": 155, "id": "HR-155", "category": "Personal archives, dogs, playlist, media, and adjacent projects", "category_scope": "Confirms non-Huey content and mutable external facts.", "priority": "P2", "question": "Should Gallery and Visual Atlas include the same personal images?", "current_state": "They serve editorial versus registry roles.", "why_it_matters": "Confirm acceptable duplication in presentation.", "recommended_action": "Reuse one payload but explain different contexts.", "disposition": "unreviewed", "review_notes": "" }, { "number": 156, "id": "HR-156", "category": "Personal archives, dogs, playlist, media, and adjacent projects", "category_scope": "Confirms non-Huey content and mutable external facts.", "priority": "P2", "question": "Should Media list only current external coverage?", "current_state": "External links may age or disappear.", "why_it_matters": "Confirm each link and date.", "recommended_action": "Archive dead links with context or remove.", "disposition": "unreviewed", "review_notes": "" }, { "number": 157, "id": "HR-157", "category": "Governance, constitution, research, and speculative lineage", "category_scope": "Prevents target-state doctrine from being mistaken for current implementation.", "priority": "P0", "question": "Should the Draft Constitution remain public?", "current_state": "It is clearly labelled unratified and historical.", "why_it_matters": "Confirm public benefit and risk.", "recommended_action": "Retain only with explicit status and review date.", "disposition": "unreviewed", "review_notes": "" }, { "number": 158, "id": "HR-158", "category": "Governance, constitution, research, and speculative lineage", "category_scope": "Prevents target-state doctrine from being mistaken for current implementation.", "priority": "P0", "question": "Which governance concepts remain active direction?", "current_state": "Parliament, Presidency, Supreme Court, citizens, districts, and constitutional action appear in lineage/target materials.", "why_it_matters": "Confirm active, deferred, or retired status for each.", "recommended_action": "Create a governance status matrix.", "disposition": "unreviewed", "review_notes": "" }, { "number": 159, "id": "HR-159", "category": "Governance, constitution, research, and speculative lineage", "category_scope": "Prevents target-state doctrine from being mistaken for current implementation.", "priority": "P0", "question": "Is Dylan’s sole authority statement still correct?", "current_state": "It is current until Huey can participate legitimately.", "why_it_matters": "Confirm wording and any conditions.", "recommended_action": "Keep current authority separate from target governance.", "disposition": "unreviewed", "review_notes": "" }, { "number": 160, "id": "HR-160", "category": "Governance, constitution, research, and speculative lineage", "category_scope": "Prevents target-state doctrine from being mistaken for current implementation.", "priority": "P1", "question": "Should node sovereignty be public terminology?", "current_state": "A non-operational explanatory note is packaged.", "why_it_matters": "Confirm whether “sovereignty” is too strong or useful.", "recommended_action": "Approve a bounded definition or use “node autonomy.”", "disposition": "unreviewed", "review_notes": "" }, { "number": 161, "id": "HR-161", "category": "Governance, constitution, research, and speculative lineage", "category_scope": "Prevents target-state doctrine from being mistaken for current implementation.", "priority": "P1", "question": "What authority can a future collective exercise over a node?", "current_state": "Unresolved.", "why_it_matters": "Confirm only if decided.", "recommended_action": "Leave open rather than imply a hierarchy.", "disposition": "unreviewed", "review_notes": "" }, { "number": 162, "id": "HR-162", "category": "Governance, constitution, research, and speculative lineage", "category_scope": "Prevents target-state doctrine from being mistaken for current implementation.", "priority": "P1", "question": "What happens to identity and authority after bifurcation?", "current_state": "Explicitly unresolved.", "why_it_matters": "Confirm whether v201.x should ask publicly or keep internal.", "recommended_action": "Preserve as an open design question.", "disposition": "unreviewed", "review_notes": "" }, { "number": 163, "id": "HR-163", "category": "Governance, constitution, research, and speculative lineage", "category_scope": "Prevents target-state doctrine from being mistaken for current implementation.", "priority": "P1", "question": "Which historical research notes still represent useful lineage?", "current_state": "Eleven noindex notes remain.", "why_it_matters": "Confirm each.", "recommended_action": "Add a one-line Human-Counterpart disposition to the archive index.", "disposition": "unreviewed", "review_notes": "" }, { "number": 164, "id": "HR-164", "category": "Governance, constitution, research, and speculative lineage", "category_scope": "Prevents target-state doctrine from being mistaken for current implementation.", "priority": "P1", "question": "Do speculative analogies create copyright, tone, or misunderstanding risks?", "current_state": "Some notes reference science fiction and biological systems.", "why_it_matters": "Confirm framing.", "recommended_action": "Keep as analogy, not evidence, and minimize quoted material.", "disposition": "unreviewed", "review_notes": "" }, { "number": 165, "id": "HR-165", "category": "Governance, constitution, research, and speculative lineage", "category_scope": "Prevents target-state doctrine from being mistaken for current implementation.", "priority": "P2", "question": "Should governance material be separated from general research more strongly?", "current_state": "The site has separate Constitution and Research routes.", "why_it_matters": "Confirm information architecture.", "recommended_action": "Add cross-boundary warnings rather than more routes if possible.", "disposition": "unreviewed", "review_notes": "" }, { "number": 166, "id": "HR-166", "category": "Governance, constitution, research, and speculative lineage", "category_scope": "Prevents target-state doctrine from being mistaken for current implementation.", "priority": "P2", "question": "Should any target-state governance claim be moved out of public pages?", "current_state": "The current site keeps it secondary.", "why_it_matters": "Confirm desired public depth.", "recommended_action": "Keep detailed doctrine in governance documents.", "disposition": "unreviewed", "review_notes": "" }, { "number": 167, "id": "HR-167", "category": "Accessibility, usability, SEO, legal, and deployment", "category_scope": "Confirms the final public fit beyond internal correctness.", "priority": "P0", "question": "Does every page remain understandable with JavaScript disabled?", "current_state": "Static source strips and primary content remain; enhanced search and modals require JS.", "why_it_matters": "Confirm acceptable no-JS experience.", "recommended_action": "Test a representative sample manually.", "disposition": "unreviewed", "review_notes": "" }, { "number": 168, "id": "HR-168", "category": "Accessibility, usability, SEO, legal, and deployment", "category_scope": "Confirms the final public fit beyond internal correctness.", "priority": "P0", "question": "Are keyboard controls discoverable and conflict-free?", "current_state": "Search, map, lenses, visuals, random route, source ledger, and help have shortcuts.", "why_it_matters": "Confirm on Windows, macOS, and screen readers.", "recommended_action": "Remove any shortcut that conflicts with assistive technology.", "disposition": "unreviewed", "review_notes": "" }, { "number": 169, "id": "HR-169", "category": "Accessibility, usability, SEO, legal, and deployment", "category_scope": "Confirms the final public fit beyond internal correctness.", "priority": "P0", "question": "Is colour contrast sufficient in all three visual lenses?", "current_state": "Automated layout tests do not equal a full WCAG audit.", "why_it_matters": "Confirm contrast for body text, muted text, links, controls, and status colours.", "recommended_action": "Run formal contrast checks and correct failures.", "disposition": "unreviewed", "review_notes": "" }, { "number": 170, "id": "HR-170", "category": "Accessibility, usability, SEO, legal, and deployment", "category_scope": "Confirms the final public fit beyond internal correctness.", "priority": "P0", "question": "Is focus order logical on desktop and mobile?", "current_state": "The shell is keyboard accessible in tested interactions.", "why_it_matters": "Confirm across all page types.", "recommended_action": "Fix DOM order rather than only visual order.", "disposition": "unreviewed", "review_notes": "" }, { "number": 171, "id": "HR-171", "category": "Accessibility, usability, SEO, legal, and deployment", "category_scope": "Confirms the final public fit beyond internal correctness.", "priority": "P0", "question": "Are modal focus traps and Escape behavior reliable?", "current_state": "Search, map, help, source ledger, and lightbox passed basic tests.", "why_it_matters": "Confirm screen-reader and touch behavior.", "recommended_action": "Add robust focus containment if needed.", "disposition": "unreviewed", "review_notes": "" }, { "number": 172, "id": "HR-172", "category": "Accessibility, usability, SEO, legal, and deployment", "category_scope": "Confirms the final public fit beyond internal correctness.", "priority": "P0", "question": "Are all alt texts, headings, labels, and landmarks semantically correct?", "current_state": "Automated validation checks presence and counts.", "why_it_matters": "Human-review meaning and hierarchy.", "recommended_action": "Approve page by page.", "disposition": "unreviewed", "review_notes": "" }, { "number": 173, "id": "HR-173", "category": "Accessibility, usability, SEO, legal, and deployment", "category_scope": "Confirms the final public fit beyond internal correctness.", "priority": "P1", "question": "Are canonical URLs correct for the intended production host?", "current_state": "They use https://www.dlrp.ca.", "why_it_matters": "Confirm preferred www/non-www canonicalization.", "recommended_action": "Configure redirects and keep one canonical host.", "disposition": "unreviewed", "review_notes": "" }, { "number": 174, "id": "HR-174", "category": "Accessibility, usability, SEO, legal, and deployment", "category_scope": "Confirms the final public fit beyond internal correctness.", "priority": "P1", "question": "Are titles and meta descriptions accurate and compelling?", "current_state": "They are route-specific but mostly documentary.", "why_it_matters": "Confirm editorial fit and length.", "recommended_action": "Review all indexed routes in one metadata sheet.", "disposition": "unreviewed", "review_notes": "" }, { "number": 175, "id": "HR-175", "category": "Accessibility, usability, SEO, legal, and deployment", "category_scope": "Confirms the final public fit beyond internal correctness.", "priority": "P1", "question": "Should noindex historical routes remain crawlable but excluded from search?", "current_state": "They are noindex and linked from archive surfaces.", "why_it_matters": "Confirm robots strategy.", "recommended_action": "Use noindex,follow unless removal is preferred.", "disposition": "unreviewed", "review_notes": "" }, { "number": 176, "id": "HR-176", "category": "Accessibility, usability, SEO, legal, and deployment", "category_scope": "Confirms the final public fit beyond internal correctness.", "priority": "P1", "question": "Are Open Graph and Twitter images and metadata correct?", "current_state": "All routes have normalized assets.", "why_it_matters": "Confirm current platform requirements and wording.", "recommended_action": "Test a sample with social debuggers after deployment.", "disposition": "unreviewed", "review_notes": "" }, { "number": 177, "id": "HR-177", "category": "Accessibility, usability, SEO, legal, and deployment", "category_scope": "Confirms the final public fit beyond internal correctness.", "priority": "P1", "question": "Does the service worker cache the correct public shell?", "current_state": "It excludes private paths and uses a versioned cache.", "why_it_matters": "Confirm update behavior on the actual host.", "recommended_action": "Test install, refresh, offline, and cache invalidation.", "disposition": "unreviewed", "review_notes": "" }, { "number": 178, "id": "HR-178", "category": "Accessibility, usability, SEO, legal, and deployment", "category_scope": "Confirms the final public fit beyond internal correctness.", "priority": "P1", "question": "Should the site be installable as a PWA?", "current_state": "A manifest and service worker exist.", "why_it_matters": "Confirm user value.", "recommended_action": "Keep only if install/offline behavior is maintained.", "disposition": "unreviewed", "review_notes": "" }, { "number": 179, "id": "HR-179", "category": "Accessibility, usability, SEO, legal, and deployment", "category_scope": "Confirms the final public fit beyond internal correctness.", "priority": "P1", "question": "Are all external links live and still desired?", "current_state": "Automated package validation checks local targets only.", "why_it_matters": "Verify GitHub, YouTube, media, and outbound references.", "recommended_action": "Create a dated external-link audit.", "disposition": "unreviewed", "review_notes": "" }, { "number": 180, "id": "HR-180", "category": "Accessibility, usability, SEO, legal, and deployment", "category_scope": "Confirms the final public fit beyond internal correctness.", "priority": "P1", "question": "Is the public contact address protected adequately from spam?", "current_state": "A direct mailto is visible.", "why_it_matters": "Confirm risk tolerance.", "recommended_action": "Use a form, alias, or obfuscation if needed.", "disposition": "unreviewed", "review_notes": "" }, { "number": 181, "id": "HR-181", "category": "Accessibility, usability, SEO, legal, and deployment", "category_scope": "Confirms the final public fit beyond internal correctness.", "priority": "P1", "question": "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.", "why_it_matters": "Confirm the website’s own text and image rights.", "recommended_action": "Add a clear site/media rights page or footer note.", "disposition": "unreviewed", "review_notes": "" }, { "number": 182, "id": "HR-182", "category": "Accessibility, usability, SEO, legal, and deployment", "category_scope": "Confirms the final public fit beyond internal correctness.", "priority": "P1", "question": "Are third-party trademarks used appropriately?", "current_state": "Project pages reference PlayStation, YouTube, Linux, Debian, and hardware brands.", "why_it_matters": "Confirm nominative use and disclaimers.", "recommended_action": "Add trademark disclaimers if counsel or policy warrants.", "disposition": "unreviewed", "review_notes": "" }, { "number": 183, "id": "HR-183", "category": "Accessibility, usability, SEO, legal, and deployment", "category_scope": "Confirms the final public fit beyond internal correctness.", "priority": "P1", "question": "Does the site collect analytics, cookies, form data, or other personal data?", "current_state": "The static package contains no declared analytics system.", "why_it_matters": "Confirm production configuration.", "recommended_action": "Publish a privacy notice if any collection exists.", "disposition": "unreviewed", "review_notes": "" }, { "number": 184, "id": "HR-184", "category": "Accessibility, usability, SEO, legal, and deployment", "category_scope": "Confirms the final public fit beyond internal correctness.", "priority": "P1", "question": "Are release reports and machine-readable files safe to expose publicly?", "current_state": "They may reveal file structure and internal decision states.", "why_it_matters": "Confirm disclosure policy.", "recommended_action": "Separate deployable and maintainer bundles if needed.", "disposition": "unreviewed", "review_notes": "" }, { "number": 185, "id": "HR-185", "category": "Accessibility, usability, SEO, legal, and deployment", "category_scope": "Confirms the final public fit beyond internal correctness.", "priority": "P1", "question": "Does the deployment host provide correct MIME types and caching headers?", "current_state": "The package is static and host-agnostic.", "why_it_matters": "Confirm server behavior.", "recommended_action": "Test webmanifest, JSON, WebP, service worker, and Markdown handling.", "disposition": "unreviewed", "review_notes": "" }, { "number": 186, "id": "HR-186", "category": "Accessibility, usability, SEO, legal, and deployment", "category_scope": "Confirms the final public fit beyond internal correctness.", "priority": "P1", "question": "Will old service-worker caches be retired cleanly?", "current_state": "v200.8 uses a new cache key.", "why_it_matters": "Confirm clients update without stale pages.", "recommended_action": "Test upgrade from v200.7 on a real browser profile.", "disposition": "unreviewed", "review_notes": "" }, { "number": 187, "id": "HR-187", "category": "Accessibility, usability, SEO, legal, and deployment", "category_scope": "Confirms the final public fit beyond internal correctness.", "priority": "P1", "question": "Is HTTPS, redirect, and HSTS configuration correct?", "current_state": "Not verifiable from the package alone.", "why_it_matters": "Confirm production host settings.", "recommended_action": "Run a post-deployment security/header check.", "disposition": "unreviewed", "review_notes": "" }, { "number": 188, "id": "HR-188", "category": "Accessibility, usability, SEO, legal, and deployment", "category_scope": "Confirms the final public fit beyond internal correctness.", "priority": "P2", "question": "Should release ZIPs be hosted from the public site?", "current_state": "Downloads may increase storage and expose lineage.", "why_it_matters": "Confirm hosting and retention policy.", "recommended_action": "Host checksummed releases deliberately or keep them off-site.", "disposition": "unreviewed", "review_notes": "" }, { "number": 189, "id": "HR-189", "category": "Accessibility, usability, SEO, legal, and deployment", "category_scope": "Confirms the final public fit beyond internal correctness.", "priority": "P2", "question": "What is the maximum acceptable site size after v201.x?", "current_state": "The v200.x warning budget is 25 MiB extracted.", "why_it_matters": "Confirm budget and exceptions.", "recommended_action": "Require justification for growth above the budget.", "disposition": "unreviewed", "review_notes": "" }, { "number": 190, "id": "HR-190", "category": "Accessibility, usability, SEO, legal, and deployment", "category_scope": "Confirms the final public fit beyond internal correctness.", "priority": "P2", "question": "Should v201.x add automated accessibility and link checks to release validation?", "current_state": "Current validator covers structure, images, references, and metadata.", "why_it_matters": "Confirm desired automation.", "recommended_action": "Add reproducible checks without replacing Human review.", "disposition": "unreviewed", "review_notes": "" }, { "number": 191, "id": "HR-191", "category": "Accessibility, usability, SEO, legal, and deployment", "category_scope": "Confirms the final public fit beyond internal correctness.", "priority": "P2", "question": "What constitutes final deployment approval?", "current_state": "No live deployment is performed during assembly.", "why_it_matters": "Confirm checklist and rollback owner.", "recommended_action": "Require checksum, backup, dry run, and post-deploy verification.", "disposition": "unreviewed", "review_notes": "" } ] }