{
  "library": {
    "name": "Research Library",
    "canonical_path": "/research/",
    "description": "Indexable hub for Bluehand technical briefs, protocol notes, and architecture artifacts.",
    "publication_policy": "HTML is the canonical indexed surface; PDFs are supporting encodings for sharing, review, and archive.",
    "metadata_priority": [
      "research/registry.json",
      "research/manifest.json (generated)",
      "route/prerender outputs"
    ],
    "visual_atlas": {
      "version": "BRO-VISUAL-ATLAS-v1",
      "status": "spec-integrated",
      "doc_path": "docs/BRO_VISUAL_ATLAS.md",
      "source_pdf": "research/sources/bro-visual-atlas-v1.pdf",
      "implementation_branch": "feature/bro-visual-atlas-v1",
      "bro_hook": "object_system.visual_atlas"
    }
  },
  "contract_version": "RL-CONTRACT-v0.2",
  "object_system": {
    "name": "Bluehand Research Objects",
    "abbreviation": "BRO",
    "version": "0.7.1",
    "center": "Human-first object, machine-projectable structure.",
    "lineage_policy": "Graph-compatible and lineage-optional. Strict lineage is not mandatory for the public Research Library.",
    "public_goal": "Stakeholder engagement and ontological orientation.",
    "visual_atlas": {
      "repo_drop_id": "BRO-VISUAL-ATLAS-v1",
      "version": "1",
      "status": "spec-integrated",
      "canonical_doc": "docs/BRO_VISUAL_ATLAS.md",
      "source_pdf": "research/sources/bro-visual-atlas-v1.pdf",
      "branch_suggestion": "feature/bro-visual-atlas-v1",
      "primary_objective": "Transform the Research Library into a calm semantic atlas of human-readable Research Objects—not a PDF shelf, admin dashboard, metadata wall, or graph database UI.",
      "registry_mapping": {
        "artifact_bro_envelope": "bro",
        "human_orientation_fields": [
          "purpose",
          "problem_addressed",
          "why_now",
          "inspiration",
          "vision_direction",
          "reader_takeaway"
        ],
        "stakeholder_routes": [
          "AI Infrastructure Recruiters",
          "Grant / NSF / SBIR Reviewers",
          "Technical Collaborators",
          "Governance / Policy Evaluators",
          "Founders & Institutional Partners"
        ],
        "visual_projection_folder": "public/visuals/research/",
        "diagram_ids_field": "diagram_ids",
        "visual_status_field": "bro.projections.visual_status"
      }
    }
  },
  "featured_artifact_id": "BH-RL-2026-0001",
  "authority_classes": {
    "canonical_public": "Safe to cite as current public canon.",
    "public_projection": "Safe to read and summarize; compiled projection.",
    "review_candidate": "Orient only — not current canon.",
    "historical": "Background; may be superseded.",
    "deprecated": "Do not cite as current.",
    "internal_reference": "Not production deployment state.",
    "external_reference": "Third-party; Bluehand does not vouch."
  },
  "artifacts": [
    {
      "artifact_id": "BH-RL-2026-0001",
      "slug": "personalized-generalized-interface",
      "title": "Personalized Generalized Interfaces for Agentic Workflow Orchestration",
      "subtitle": "Memory-harnessed, local-first + frontier-hybrid AI infrastructure for intent interpretation, relationship continuity, and agentic execution.",
      "abstract": "Bluehand’s research brief on personalized generalized interfaces: memory-aware interaction, relationship continuity, hybrid model routing, and agentic workflow execution as a practical infrastructure direction.",
      "artifact_type": "research_brief",
      "publication_status": "canonical",
      "publication_date": "2026-05-19",
      "version_state": "1.0.0",
      "authority_class": "canonical_public",
      "canonical_url": "https://www.blue-hand.org/research/personalized-generalized-interface/",
      "keywords": [
        "personalized AI",
        "AI interface systems",
        "agentic workflow orchestration",
        "memory-aware interfaces",
        "local-first AI assistant",
        "frontier hybrid AI"
      ],
      "domains": [
        "AI infrastructure",
        "personalized interfaces",
        "agentic workflow",
        "semantic memory"
      ],
      "maturity_note": "Published PDF and canonical HTML landing page.",
      "source_lineage": "Compiled research artifact; PDF encoding generated via ReportLab (scripts/pdf/generate_encodings.py) from research/registry.json; HTML route /research/personalized-generalized-interface/ remains canonical.",
      "revision": {
        "label": "initial-canonical",
        "number": 1
      },
      "author": {
        "name": "Bluehand Research Group"
      },
      "html": {
        "focus_sections": [
          {
            "title": "Memory-harnessed interfaces",
            "body": "The brief argues that agentic systems need persistent memory and lineage, not just a transient chat surface. The interface should remember context, task state, and relationships across repeated work."
          },
          {
            "title": "Local-first + frontier-hybrid",
            "body": "Bluehand’s substrate pairs local execution with frontier models where useful, so intent interpretation and orchestration can stay responsive while stronger models are used selectively."
          },
          {
            "title": "Governed execution",
            "body": "The architecture is meant to support real organizational work: deterministic workflows, reviewable actions, and constrained agent behavior that a hiring team or founder can evaluate for operational fit."
          }
        ],
        "hero_extra": "The audience is deliberate: recruiters, founders, funders, and technical evaluators who need to understand whether Bluehand can deliver real AI infrastructure and not just prototypes.",
        "doctrine_note": "The PDF is the shareable artifact, but the HTML route is the authority surface. It gives crawlers context, gives recruiters a readable summary, and gives Bluehand a stable research landing page that can rank for the work rather than the file format."
      },
      "related_systems": [
        "generalized-interface-layer",
        "sigmem0",
        "bluehand-spine"
      ],
      "diagram_ids": [
        "personalized-ecosystem-loop",
        "subagent-routing-runtime",
        "user-continuity-graph"
      ],
      "html_path": "/research/personalized-generalized-interface/",
      "pdf_path": "/bluehand-personalized-generalized-interfaces-2026.pdf",
      "evidence_path": "/research/personalized-generalized-interface/evidence/",
      "relations": [
        {
          "type": "builds_on",
          "target_slug": "lineage-aware-memory"
        },
        {
          "type": "related_to",
          "target_slug": "governed-agent-execution"
        },
        {
          "type": "related_to",
          "target_slug": "local-first-ai-infrastructure"
        }
      ],
      "bro": {
        "version": "0.7.1",
        "human_orientation": {
          "purpose": "Orient readers to Bluehand’s interface thesis: generalized interfaces should become continuity-aware operational environments rather than isolated prompt boxes.",
          "problem_addressed": "People repeatedly reconstruct context across apps, assistants, calendars, files, and workflows; current interfaces rarely preserve relational continuity or route intent through the best execution substrate.",
          "why_now": "AI systems are moving from isolated chat interactions toward persistent agents, retrieval systems, personal workflows, and institution-facing automation.",
          "reader_takeaway": "Bluehand is exploring the interface layer as an AI infrastructure problem, not as a chatbot wrapper.",
          "inspiration": "The waking-user scenario: a custom alarm intuited by a personal agent, followed by natural-language engagement with a personal-history-aware social/workflow intelligence.",
          "vision_direction": "A personalized generalized interface becomes the human-facing membrane for intentional computing: memory-aware, relationship-sensitive, contextually useful, and governed by human override."
        },
        "stakeholder_alignment": {
          "best_for": [
            "AI infrastructure recruiters",
            "technical reviewers",
            "grant reviewers",
            "research collaborators",
            "institutional partners"
          ],
          "stakeholder_categories": [
            "recruiter",
            "technical_reviewer",
            "grant_reviewer",
            "technical_collaborator",
            "institutional_partner"
          ],
          "recruiter_relevance": "Provides a capability signal for AI infrastructure, governance, semantic systems, agentic workflow, or local-first execution roles.",
          "grant_relevance": "Supports public-interest framing where responsible AI, trustworthy infrastructure, human-centered systems, or research-to-venture pathways matter.",
          "partner_relevance": "Helps potential partners understand the problem Bluehand is orienting around and where collaboration could fit.",
          "technical_reviewer_relevance": "Surfaces the relevant problem, methods, constraints, failure modes, and implementation boundaries without requiring internal Bluehand context."
        },
        "category_sets": {
          "topic_categories": [
            "personalized_ai",
            "generalized_interface",
            "semantic_memory",
            "agentic_workflow",
            "local_first_ai"
          ],
          "capability_categories": [
            "intent_interpretation",
            "hybrid_model_routing",
            "relationship_continuity",
            "workflow_activation"
          ],
          "method_categories": [
            "orchestration",
            "semantic_continuity",
            "local_frontier_routing",
            "human_override"
          ],
          "constraint_categories": [
            "agency_preservation",
            "privacy_sensitivity",
            "no_manipulative_engagement",
            "bounded_authority"
          ],
          "failure_mode_categories": [
            "chatbot_wrapper_drift",
            "overpersonalization",
            "hidden_automation",
            "privacy_boundary_collapse"
          ],
          "visual_categories": [
            "ecosystem_loop",
            "interface_membrane",
            "subagent_routing_diagram",
            "morning_navigation_plane"
          ]
        },
        "public_boundary": {
          "public_claims": [
            "Bluehand is researching memory-aware generalized interfaces and governed agentic workflow orchestration."
          ],
          "uncertain_claims": [
            "The exact product surface and implementation architecture remain under development."
          ],
          "do_not_infer": [
            "Do not infer a fully productionized personal operating system or autonomous assistant."
          ],
          "implementation_boundary": "This is a public Research Object. Implementation evidence, strict lineage, and runtime proof belong in project/repo-specific surfaces unless explicitly linked."
        },
        "semantic_net": {
          "related_objects": [
            "lineage-aware-memory",
            "governed-agent-execution",
            "local-first-ai-infrastructure",
            "semantic-governance"
          ],
          "associative_edges": [
            "related_to",
            "supports",
            "constrains",
            "extends"
          ],
          "optional_lineage": []
        },
        "projections": {
          "html_url": "https://www.blue-hand.org/research/personalized-generalized-interface/",
          "pdf_url": "https://www.blue-hand.org/bluehand-personalized-generalized-interfaces-2026.pdf",
          "jsonld_enabled": true,
          "llms_enabled": true,
          "visual_status": "needed",
          "pdf_depth_status": "published_reportlab_projection_v2"
        }
      }
    },
    {
      "artifact_id": "BH-RL-2026-0002",
      "slug": "governed-agent-execution",
      "title": "Governed Agent Execution and Hybrid Orchestration",
      "subtitle": "Policy-gated subagent routing, local/frontier model selection, replayability, and bounded authority for agentic workflow systems.",
      "abstract": "A Bluehand research artifact defining governed agent execution: subagent orchestration, policy gates, human override, deterministic transitions, and hybrid inference routing for operational AI systems.",
      "artifact_type": "research_brief",
      "publication_status": "canonical",
      "publication_date": "2026-05-19",
      "version_state": "1.0.0",
      "authority_class": "canonical_public",
      "canonical_url": "https://www.blue-hand.org/research/governed-agent-execution/",
      "keywords": [
        "agent orchestration",
        "governed AI systems",
        "hybrid inference routing",
        "deterministic execution",
        "AI workflow runtime",
        "policy gated agents"
      ],
      "domains": [
        "agent orchestration",
        "AI governance",
        "hybrid inference",
        "workflow automation"
      ],
      "maturity_note": "Published PDF; HTML surface should remain summary-first and point to the PDF.",
      "source_lineage": "Compiled research artifact; PDF encoding generated via ReportLab (scripts/pdf/generate_encodings.py) from research/registry.json; HTML route /research/governed-agent-execution/ remains canonical.",
      "revision": {
        "label": "initial-canonical",
        "number": 1
      },
      "author": {
        "name": "Bluehand Research Group"
      },
      "html": {
        "focus_sections": [
          {
            "title": "Operational thesis",
            "body": "Agentic systems become organizationally useful only when execution is bounded, observable, and reviewable. Bluehand treats agent orchestration as a governed runtime problem: intent is interpreted, routed to the right subagent or model pathway, checked against authority boundaries, and returned with enough lineage to support human judgment."
          },
          {
            "title": "Why it matters",
            "body": "Recruiters and technical evaluators are no longer impressed by unconstrained agents that appear capable in demos but collapse under governance, privacy, and operational accountability. The higher-value category is agent infrastructure that can act, pause, escalate, and explain why a transition occurred."
          },
          {
            "title": "Governance boundary",
            "body": "This artifact does not claim that every proposed runtime is fully implemented in production. It defines the publication-level architecture and evaluation posture: policy gates, local/frontier routing, replayability, human override, failure-mode visibility, and deterministic transition discipline."
          }
        ],
        "hero_extra": null,
        "doctrine_note": "The PDF is the shareable artifact, but the HTML route is the authority surface. It gives crawlers context, gives recruiters a readable summary, and gives Bluehand a stable research landing page that can rank for the work rather than the file format."
      },
      "related_systems": [
        "bluehand-spine",
        "bis-cp0",
        "generalized-interface-layer"
      ],
      "diagram_ids": [
        "agent-orchestration-runtime",
        "governance-membrane",
        "replay-lifecycle"
      ],
      "html_path": "/research/governed-agent-execution/",
      "pdf_path": "/bluehand-governed-agent-execution-2026.pdf",
      "evidence_path": "/research/governed-agent-execution/evidence/",
      "relations": [
        {
          "type": "implements",
          "target_slug": "semantic-governance"
        },
        {
          "type": "builds_on",
          "target_slug": "personalized-generalized-interface"
        },
        {
          "type": "related_to",
          "target_slug": "deterministic-replay"
        }
      ],
      "bro": {
        "version": "0.7.1",
        "human_orientation": {
          "purpose": "Explain Bluehand’s position that useful agent systems require governance at the execution layer, not just prompt discipline or policy prose.",
          "problem_addressed": "Agentic systems can act across tools, models, and contexts without clear authority boundaries, creating risk around autonomy, accountability, cost, privacy, and failure recovery.",
          "why_now": "AI systems are moving from isolated chat interactions toward persistent agents, retrieval systems, personal workflows, and institution-facing automation.",
          "reader_takeaway": "Bluehand thinks about agents as systems engineering and governance infrastructure, not magical autonomous workers.",
          "inspiration": "The need for fast, powerful, task-specialized subagents that remain bounded, reviewable, and optimized for the work at hand.",
          "vision_direction": "A governed orchestration fabric where local agents, frontier models, deterministic workflows, and human review coexist through explicit routing and authority rules."
        },
        "stakeholder_alignment": {
          "best_for": [
            "AI infrastructure recruiters",
            "technical reviewers",
            "grant reviewers",
            "research collaborators",
            "institutional partners"
          ],
          "stakeholder_categories": [
            "recruiter",
            "technical_reviewer",
            "grant_reviewer",
            "technical_collaborator",
            "institutional_partner"
          ],
          "recruiter_relevance": "Provides a capability signal for AI infrastructure, governance, semantic systems, agentic workflow, or local-first execution roles.",
          "grant_relevance": "Supports public-interest framing where responsible AI, trustworthy infrastructure, human-centered systems, or research-to-venture pathways matter.",
          "partner_relevance": "Helps potential partners understand the problem Bluehand is orienting around and where collaboration could fit.",
          "technical_reviewer_relevance": "Surfaces the relevant problem, methods, constraints, failure modes, and implementation boundaries without requiring internal Bluehand context."
        },
        "category_sets": {
          "topic_categories": [
            "agent_orchestration",
            "governed_execution",
            "hybrid_inference",
            "workflow_runtime"
          ],
          "capability_categories": [
            "subagent_routing",
            "policy_gating",
            "human_override",
            "execution_monitoring",
            "replayability"
          ],
          "method_categories": [
            "runtime_membrane",
            "task_specialization",
            "transition_logging",
            "local_frontier_routing"
          ],
          "constraint_categories": [
            "bounded_authority",
            "least_privilege",
            "reviewability",
            "cost_visibility"
          ],
          "failure_mode_categories": [
            "unbounded_autonomy",
            "agent_sprawl",
            "silent_tool_execution",
            "routing_opacity"
          ],
          "visual_categories": [
            "orchestration_runtime",
            "policy_gate_stack",
            "subagent_constellation",
            "authority_flow"
          ]
        },
        "public_boundary": {
          "public_claims": [
            "Bluehand defines governed agent execution as a runtime architecture concern."
          ],
          "uncertain_claims": [
            "Specific subagent catalogs and deployment maturity are project-dependent."
          ],
          "do_not_infer": [
            "Do not infer that all described agent capabilities are current production services."
          ],
          "implementation_boundary": "This is a public Research Object. Implementation evidence, strict lineage, and runtime proof belong in project/repo-specific surfaces unless explicitly linked."
        },
        "semantic_net": {
          "related_objects": [
            "semantic-governance",
            "deterministic-replay",
            "local-first-ai-infrastructure",
            "personalized-generalized-interface"
          ],
          "associative_edges": [
            "related_to",
            "supports",
            "constrains",
            "extends"
          ],
          "optional_lineage": []
        },
        "projections": {
          "html_url": "https://www.blue-hand.org/research/governed-agent-execution/",
          "pdf_url": "https://www.blue-hand.org/bluehand-governed-agent-execution-2026.pdf",
          "jsonld_enabled": true,
          "llms_enabled": true,
          "visual_status": "needed",
          "pdf_depth_status": "published_reportlab_projection_v2"
        }
      }
    },
    {
      "artifact_id": "BH-RL-2026-0003",
      "slug": "lineage-aware-memory",
      "title": "Lineage-Aware Memory Infrastructure for AI Systems",
      "subtitle": "Semantic memory, retrieval boundaries, deterministic replay, and compression discipline for longitudinal AI infrastructure.",
      "abstract": "A Bluehand research artifact establishing lineage-aware memory as an infrastructure problem: retrieval is not evidence, compression is not truth, and semantic memory requires auditable transformation context.",
      "artifact_type": "research_brief",
      "publication_status": "canonical",
      "publication_date": "2026-05-19",
      "version_state": "1.0.0",
      "authority_class": "canonical_public",
      "canonical_url": "https://www.blue-hand.org/research/lineage-aware-memory/",
      "keywords": [
        "semantic memory",
        "AI memory infrastructure",
        "lineage-aware retrieval",
        "deterministic replay",
        "vector retrieval governance",
        "memory harness"
      ],
      "domains": [
        "semantic memory",
        "AI memory infrastructure",
        "retrieval governance",
        "lineage"
      ],
      "maturity_note": "Published PDF; HTML should emphasize lineage, retrieval boundaries, and memory governance.",
      "source_lineage": "Compiled research artifact; PDF encoding generated via ReportLab (scripts/pdf/generate_encodings.py) from research/registry.json; HTML route /research/lineage-aware-memory/ remains canonical.",
      "revision": {
        "label": "initial-canonical",
        "number": 1
      },
      "author": {
        "name": "Bluehand Research Group"
      },
      "html": {
        "focus_sections": [
          {
            "title": "Operational thesis",
            "body": "Memory is not merely storage. For AI systems, memory is a transformation chain: conversations, documents, summaries, embeddings, retrieval hits, clusters, and decisions all alter meaning. Bluehand’s memory infrastructure stance requires lineage so that derived context remains visible, contestable, and bounded."
          },
          {
            "title": "Why it matters",
            "body": "Longitudinal AI systems fail when they treat retrieval as truth or compression as evidence. A recruiter evaluating serious AI infrastructure should see that Bluehand distinguishes semantic recall from evidentiary proof, and that memory usefulness depends on auditability as much as relevance."
          },
          {
            "title": "Governance boundary",
            "body": "This artifact positions lineage-aware memory as a technical and ethical architecture. It should not be read as claiming that every memory mechanism described is deployed across Bluehand systems; implementation status belongs in system-level pages and repo evidence."
          }
        ],
        "hero_extra": null,
        "doctrine_note": "The PDF is the shareable artifact, but the HTML route is the authority surface. It gives crawlers context, gives recruiters a readable summary, and gives Bluehand a stable research landing page that can rank for the work rather than the file format."
      },
      "related_systems": [
        "sigmem0",
        "bis-cp0",
        "bluehand-spine"
      ],
      "diagram_ids": [
        "memory-lineage-graph",
        "retrieval-evidence-boundary",
        "replay-validation-pipeline"
      ],
      "html_path": "/research/lineage-aware-memory/",
      "pdf_path": "/bluehand-lineage-aware-memory-infrastructure-2026.pdf",
      "evidence_path": "/research/lineage-aware-memory/evidence/",
      "relations": [
        {
          "type": "references",
          "target_slug": "compression-is-not-evidence"
        },
        {
          "type": "related_to",
          "target_slug": "deterministic-replay"
        }
      ],
      "bro": {
        "version": "0.7.1",
        "human_orientation": {
          "purpose": "Orient readers to Bluehand’s memory thesis: durable AI usefulness depends on semantic continuity with visible transformation boundaries.",
          "problem_addressed": "AI systems retrieve, summarize, and reuse context without exposing what was preserved, lost, inferred, or merely similar.",
          "why_now": "AI systems are moving from isolated chat interactions toward persistent agents, retrieval systems, personal workflows, and institution-facing automation.",
          "reader_takeaway": "Bluehand treats memory as infrastructure for meaning, not just a vector database feature.",
          "inspiration": "SigMem0 and the Bluehand doctrine that retrieval, compression, and clustering are not evidence unless authority and context are declared.",
          "vision_direction": "Memory infrastructure that lets people navigate accumulated work without confusing retrieval candidates for proof."
        },
        "stakeholder_alignment": {
          "best_for": [
            "AI infrastructure recruiters",
            "technical reviewers",
            "grant reviewers",
            "research collaborators",
            "institutional partners"
          ],
          "stakeholder_categories": [
            "recruiter",
            "technical_reviewer",
            "grant_reviewer",
            "technical_collaborator",
            "institutional_partner"
          ],
          "recruiter_relevance": "Provides a capability signal for AI infrastructure, governance, semantic systems, agentic workflow, or local-first execution roles.",
          "grant_relevance": "Supports public-interest framing where responsible AI, trustworthy infrastructure, human-centered systems, or research-to-venture pathways matter.",
          "partner_relevance": "Helps potential partners understand the problem Bluehand is orienting around and where collaboration could fit.",
          "technical_reviewer_relevance": "Surfaces the relevant problem, methods, constraints, failure modes, and implementation boundaries without requiring internal Bluehand context."
        },
        "category_sets": {
          "topic_categories": [
            "semantic_memory",
            "lineage_aware_retrieval",
            "vector_governance",
            "knowledge_continuity"
          ],
          "capability_categories": [
            "context_reconstruction",
            "retrieval_boundary_detection",
            "semantic_continuity",
            "memory_projection"
          ],
          "method_categories": [
            "chunking",
            "embedding",
            "retrieval",
            "compression",
            "replay_validation"
          ],
          "constraint_categories": [
            "retrieval_not_evidence",
            "compression_not_truth",
            "visible_uncertainty",
            "authority_boundary"
          ],
          "failure_mode_categories": [
            "false_memory",
            "retrieval_overclaim",
            "summary_drift",
            "source_erasure"
          ],
          "visual_categories": [
            "memory_lineage_map",
            "retrieval_boundary_diagram",
            "semantic_object_graph"
          ]
        },
        "public_boundary": {
          "public_claims": [
            "Bluehand researches semantic memory systems that distinguish retrieval from evidence."
          ],
          "uncertain_claims": [
            "The exact public implementation surface for SigMem0 is not represented by this page alone."
          ],
          "do_not_infer": [
            "Do not infer that retrieval hits, summaries, or embeddings are themselves proof."
          ],
          "implementation_boundary": "This is a public Research Object. Implementation evidence, strict lineage, and runtime proof belong in project/repo-specific surfaces unless explicitly linked."
        },
        "semantic_net": {
          "related_objects": [
            "compression-is-not-evidence",
            "deterministic-replay",
            "semantic-governance",
            "personalized-generalized-interface"
          ],
          "associative_edges": [
            "related_to",
            "supports",
            "constrains",
            "extends"
          ],
          "optional_lineage": []
        },
        "projections": {
          "html_url": "https://www.blue-hand.org/research/lineage-aware-memory/",
          "pdf_url": "https://www.blue-hand.org/bluehand-lineage-aware-memory-infrastructure-2026.pdf",
          "jsonld_enabled": true,
          "llms_enabled": true,
          "visual_status": "needed",
          "pdf_depth_status": "published_reportlab_projection_v2"
        }
      }
    },
    {
      "artifact_id": "BH-RL-2026-0004",
      "slug": "local-first-ai-infrastructure",
      "title": "Local-First AI Infrastructure and Sovereign Inference",
      "subtitle": "Hybrid local/frontier execution, privacy-preserving routing, edge inference, and operational autonomy for AI systems.",
      "abstract": "A Bluehand research artifact positioning local-first and frontier-hybrid inference as a practical infrastructure strategy for privacy, latency, cost control, and operational sovereignty.",
      "artifact_type": "research_brief",
      "publication_status": "canonical",
      "publication_date": "2026-05-19",
      "version_state": "1.0.0",
      "authority_class": "canonical_public",
      "canonical_url": "https://www.blue-hand.org/research/local-first-ai-infrastructure/",
      "keywords": [
        "local-first AI",
        "sovereign AI infrastructure",
        "edge inference",
        "privacy-preserving AI",
        "hybrid AI systems",
        "local LLM orchestration"
      ],
      "domains": [
        "local-first AI",
        "sovereign inference",
        "edge AI",
        "privacy-preserving AI"
      ],
      "maturity_note": "Published PDF; HTML should avoid claiming any single deployment as complete unless linked to implementation evidence.",
      "source_lineage": "Compiled research artifact; PDF encoding generated via ReportLab (scripts/pdf/generate_encodings.py) from research/registry.json; HTML route /research/local-first-ai-infrastructure/ remains canonical.",
      "revision": {
        "label": "initial-canonical",
        "number": 1
      },
      "author": {
        "name": "Bluehand Research Group"
      },
      "html": {
        "focus_sections": [
          {
            "title": "Operational thesis",
            "body": "Local-first AI is not nostalgia for offline computing. It is an infrastructure posture: route sensitive, latency-critical, or sovereignty-relevant work locally when possible, then escalate selectively to frontier systems when the task justifies the cost, disclosure, or complexity."
          },
          {
            "title": "Why it matters",
            "body": "Enterprises, researchers, and founders increasingly need hybrid AI systems that avoid total dependence on centralized inference while still benefiting from frontier capabilities. Bluehand’s position is that local and frontier intelligence should interoperate through explicit routing policy."
          },
          {
            "title": "Governance boundary",
            "body": "This artifact should be read as architecture direction and evaluation frame. It does not assert that every deployment topology exists as a production service today. Specific implementation evidence should be linked separately."
          }
        ],
        "hero_extra": null,
        "doctrine_note": "The PDF is the shareable artifact, but the HTML route is the authority surface. It gives crawlers context, gives recruiters a readable summary, and gives Bluehand a stable research landing page that can rank for the work rather than the file format."
      },
      "related_systems": [
        "bluehand-spine",
        "generalized-interface-layer",
        "n2-protocol"
      ],
      "diagram_ids": [
        "hybrid-routing-architecture",
        "local-frontier-topology",
        "privacy-boundary-map"
      ],
      "html_path": "/research/local-first-ai-infrastructure/",
      "pdf_path": "/bluehand-local-first-ai-infrastructure-2026.pdf",
      "evidence_path": "/research/local-first-ai-infrastructure/evidence/",
      "relations": [
        {
          "type": "related_to",
          "target_slug": "governed-agent-execution"
        },
        {
          "type": "companion_spec",
          "target_slug": "personalized-generalized-interface"
        }
      ],
      "bro": {
        "version": "0.7.1",
        "human_orientation": {
          "purpose": "Frame local-first AI as a practical infrastructure stance for privacy, latency, cost control, and user/organizational autonomy.",
          "problem_addressed": "AI systems that depend entirely on centralized frontier APIs can create cost, privacy, availability, and sovereignty constraints.",
          "why_now": "AI systems are moving from isolated chat interactions toward persistent agents, retrieval systems, personal workflows, and institution-facing automation.",
          "reader_takeaway": "Bluehand views local-first AI as an operational design choice, not a purity claim.",
          "inspiration": "Bluehand’s sovereign infrastructure posture and repeated work around local LLMs, frontier subscriptions, and hybrid model routing.",
          "vision_direction": "Local and frontier intelligence interoperate through policy-aware routing rather than ideological exclusivity."
        },
        "stakeholder_alignment": {
          "best_for": [
            "AI infrastructure recruiters",
            "technical reviewers",
            "grant reviewers",
            "research collaborators",
            "institutional partners"
          ],
          "stakeholder_categories": [
            "recruiter",
            "technical_reviewer",
            "grant_reviewer",
            "technical_collaborator",
            "institutional_partner"
          ],
          "recruiter_relevance": "Provides a capability signal for AI infrastructure, governance, semantic systems, agentic workflow, or local-first execution roles.",
          "grant_relevance": "Supports public-interest framing where responsible AI, trustworthy infrastructure, human-centered systems, or research-to-venture pathways matter.",
          "partner_relevance": "Helps potential partners understand the problem Bluehand is orienting around and where collaboration could fit.",
          "technical_reviewer_relevance": "Surfaces the relevant problem, methods, constraints, failure modes, and implementation boundaries without requiring internal Bluehand context."
        },
        "category_sets": {
          "topic_categories": [
            "local_first_ai",
            "sovereign_inference",
            "hybrid_ai",
            "edge_inference"
          ],
          "capability_categories": [
            "local_model_execution",
            "frontier_escalation",
            "privacy_routing",
            "latency_optimization",
            "cost_control"
          ],
          "method_categories": [
            "routing_policy",
            "local_llm_runtime",
            "model_selection",
            "fallback_design"
          ],
          "constraint_categories": [
            "privacy_boundary",
            "cost_visibility",
            "availability_resilience",
            "capability_fit"
          ],
          "failure_mode_categories": [
            "centralization_lock_in",
            "local_model_overclaim",
            "api_cost_sprawl",
            "privacy_leakage"
          ],
          "visual_categories": [
            "hybrid_topology",
            "routing_matrix",
            "privacy_boundary_map"
          ]
        },
        "public_boundary": {
          "public_claims": [
            "Bluehand researches hybrid local/frontier AI infrastructure as a sovereignty and operational design pattern."
          ],
          "uncertain_claims": [
            "Specific deployment stacks and model selections may change rapidly."
          ],
          "do_not_infer": [
            "Do not infer that local models are always superior or that frontier APIs are rejected."
          ],
          "implementation_boundary": "This is a public Research Object. Implementation evidence, strict lineage, and runtime proof belong in project/repo-specific surfaces unless explicitly linked."
        },
        "semantic_net": {
          "related_objects": [
            "governed-agent-execution",
            "personalized-generalized-interface",
            "semantic-governance"
          ],
          "associative_edges": [
            "related_to",
            "supports",
            "constrains",
            "extends"
          ],
          "optional_lineage": []
        },
        "projections": {
          "html_url": "https://www.blue-hand.org/research/local-first-ai-infrastructure/",
          "pdf_url": "https://www.blue-hand.org/bluehand-local-first-ai-infrastructure-2026.pdf",
          "jsonld_enabled": true,
          "llms_enabled": true,
          "visual_status": "needed",
          "pdf_depth_status": "published_reportlab_projection_v2"
        }
      }
    },
    {
      "artifact_id": "BH-RL-2026-0005",
      "slug": "semantic-governance",
      "title": "Semantic Governance for Agentic Systems",
      "subtitle": "Executable governance, semantic transformation disclosure, lineage, auditability, and human override for agentic AI.",
      "abstract": "A Bluehand research artifact defining semantic governance for agentic systems: governance must be executable, semantic operations are ethical acts, and auditability requires visible lineage.",
      "artifact_type": "research_brief",
      "publication_status": "canonical",
      "publication_date": "2026-05-19",
      "version_state": "1.0.0",
      "authority_class": "canonical_public",
      "canonical_url": "https://www.blue-hand.org/research/semantic-governance/",
      "keywords": [
        "AI governance",
        "explainable AI infrastructure",
        "semantic auditability",
        "trustworthy AI systems",
        "governed AI execution",
        "human override AI"
      ],
      "domains": [
        "AI governance",
        "semantic auditability",
        "agent governance",
        "trustworthy AI"
      ],
      "maturity_note": "Published PDF; HTML should preserve uncertainty discipline and avoid policy theater.",
      "source_lineage": "Compiled research artifact; PDF encoding generated via ReportLab (scripts/pdf/generate_encodings.py) from research/registry.json; HTML route /research/semantic-governance/ remains canonical.",
      "revision": {
        "label": "initial-canonical",
        "number": 1
      },
      "author": {
        "name": "Bluehand Research Group"
      },
      "html": {
        "focus_sections": [
          {
            "title": "Operational thesis",
            "body": "Semantic governance means governing the operations that alter meaning: summarization, extraction, embedding, retrieval, clustering, rewriting, redaction, and execution. In agentic systems, governance cannot live only in policy prose. It must be visible in the runtime and publication lineage."
          },
          {
            "title": "Why it matters",
            "body": "AI governance is often flattened into compliance language after systems are already built. Bluehand’s stance is earlier and more structural: semantic operations carry authority, uncertainty, and distortion risk. That risk must be declared and bounded."
          },
          {
            "title": "Governance boundary",
            "body": "This artifact is a governance research artifact. It does not claim universal compliance certification. It defines a design and publication posture for trustworthy agentic systems."
          }
        ],
        "hero_extra": null,
        "doctrine_note": "The PDF is the shareable artifact, but the HTML route is the authority surface. It gives crawlers context, gives recruiters a readable summary, and gives Bluehand a stable research landing page that can rank for the work rather than the file format."
      },
      "related_systems": [
        "bis-cp0",
        "n2-protocol",
        "bluehand-spine"
      ],
      "diagram_ids": [
        "governance-membrane",
        "semantic-transformation-graph",
        "authority-transition-flow"
      ],
      "html_path": "/research/semantic-governance/",
      "pdf_path": "/bluehand-semantic-governance-agentic-systems-2026.pdf",
      "evidence_path": "/research/semantic-governance/evidence/",
      "relations": [
        {
          "type": "references",
          "target_slug": "compression-is-not-evidence"
        },
        {
          "type": "related_to",
          "target_slug": "governed-agent-execution"
        },
        {
          "type": "related_to",
          "target_slug": "semantic-reliability"
        }
      ],
      "bro": {
        "version": "0.7.1",
        "human_orientation": {
          "purpose": "Explain Bluehand’s position that meaning-altering operations in AI systems require governance, not just output moderation.",
          "problem_addressed": "AI systems summarize, retrieve, embed, cluster, redact, rewrite, and act in ways that can alter meaning and authority without making those transformations visible.",
          "why_now": "AI systems are moving from isolated chat interactions toward persistent agents, retrieval systems, personal workflows, and institution-facing automation.",
          "reader_takeaway": "Bluehand’s governance work is about operational semantics, not compliance theater.",
          "inspiration": "Bluehand/DhammaCode semantic governance doctrine: every semantic operation is an ethical act upon meaning.",
          "vision_direction": "AI systems expose transformation boundaries, preserve human agency, support auditability, and prevent hidden authority transfer."
        },
        "stakeholder_alignment": {
          "best_for": [
            "AI infrastructure recruiters",
            "technical reviewers",
            "grant reviewers",
            "research collaborators",
            "institutional partners"
          ],
          "stakeholder_categories": [
            "recruiter",
            "technical_reviewer",
            "grant_reviewer",
            "technical_collaborator",
            "institutional_partner"
          ],
          "recruiter_relevance": "Provides a capability signal for AI infrastructure, governance, semantic systems, agentic workflow, or local-first execution roles.",
          "grant_relevance": "Supports public-interest framing where responsible AI, trustworthy infrastructure, human-centered systems, or research-to-venture pathways matter.",
          "partner_relevance": "Helps potential partners understand the problem Bluehand is orienting around and where collaboration could fit.",
          "technical_reviewer_relevance": "Surfaces the relevant problem, methods, constraints, failure modes, and implementation boundaries without requiring internal Bluehand context."
        },
        "category_sets": {
          "topic_categories": [
            "semantic_governance",
            "agent_governance",
            "trustworthy_ai",
            "auditability"
          ],
          "capability_categories": [
            "semantic_transformation_disclosure",
            "authority_boundary_detection",
            "human_override",
            "audit_support"
          ],
          "method_categories": [
            "public_boundary",
            "claim_scoping",
            "runtime_governance",
            "transformation_ethics"
          ],
          "constraint_categories": [
            "no_hidden_inference",
            "agency_preservation",
            "metadata_must_not_overclaim",
            "uncertainty_exposure"
          ],
          "failure_mode_categories": [
            "policy_theater",
            "semantic_overclaim",
            "authority_smuggling",
            "hidden_transformation"
          ],
          "visual_categories": [
            "governance_membrane",
            "semantic_transformation_chain",
            "authority_transition_flow"
          ]
        },
        "public_boundary": {
          "public_claims": [
            "Bluehand treats semantic operations as ethically and operationally consequential."
          ],
          "uncertain_claims": [
            "Specific governance implementations vary by system and context."
          ],
          "do_not_infer": [
            "Do not infer certification, compliance approval, or formal regulatory status from this artifact alone."
          ],
          "implementation_boundary": "This is a public Research Object. Implementation evidence, strict lineage, and runtime proof belong in project/repo-specific surfaces unless explicitly linked."
        },
        "semantic_net": {
          "related_objects": [
            "compression-is-not-evidence",
            "governed-agent-execution",
            "lineage-aware-memory",
            "deterministic-replay",
            "semantic-reliability"
          ],
          "associative_edges": [
            "related_to",
            "supports",
            "constrains",
            "extends"
          ],
          "optional_lineage": []
        },
        "projections": {
          "html_url": "https://www.blue-hand.org/research/semantic-governance/",
          "pdf_url": "https://www.blue-hand.org/bluehand-semantic-governance-agentic-systems-2026.pdf",
          "jsonld_enabled": true,
          "llms_enabled": true,
          "visual_status": "needed",
          "pdf_depth_status": "published_reportlab_projection_v2"
        }
      }
    },
    {
      "artifact_id": "BH-RL-2026-0006",
      "slug": "deterministic-replay",
      "title": "Deterministic Replay Architectures for AI Systems",
      "subtitle": "Runtime lineage, reconstructable transitions, observability, drift detection, and replay-aware execution governance.",
      "abstract": "A Bluehand research artifact on deterministic replay as a trust and observability pattern for AI systems: runtime transitions should be reconstructable, bounded, and reviewable.",
      "artifact_type": "research_brief",
      "publication_status": "canonical",
      "publication_date": "2026-05-19",
      "version_state": "1.0.0",
      "authority_class": "canonical_public",
      "canonical_url": "https://www.blue-hand.org/research/deterministic-replay/",
      "keywords": [
        "deterministic replay",
        "AI observability",
        "runtime lineage",
        "replayable AI systems",
        "execution traceability",
        "drift detection"
      ],
      "domains": [
        "deterministic replay",
        "AI observability",
        "runtime governance",
        "execution traceability"
      ],
      "maturity_note": "Published PDF; HTML should mark replay as a design/research artifact unless implementation evidence is linked.",
      "source_lineage": "Compiled research artifact; PDF encoding generated via ReportLab (scripts/pdf/generate_encodings.py) from research/registry.json; HTML route /research/deterministic-replay/ remains canonical.",
      "revision": {
        "label": "initial-canonical",
        "number": 1
      },
      "author": {
        "name": "Bluehand Research Group"
      },
      "html": {
        "focus_sections": [
          {
            "title": "Operational thesis",
            "body": "A system that cannot reconstruct consequential transitions cannot reliably govern them. Deterministic replay architectures aim to preserve enough event structure, state transition context, and lineage to inspect what occurred and why."
          },
          {
            "title": "Why it matters",
            "body": "Agentic workflows introduce operational ambiguity: a task can be delegated, routed, transformed, summarized, or executed through multiple intermediaries. Replayability helps convert opaque activity into inspectable execution history."
          },
          {
            "title": "Governance boundary",
            "body": "This artifact defines replay as an architecture and evaluation principle. It should be integrated with implementation evidence only when actual replay logs, tests, or runtime traces are linked."
          }
        ],
        "hero_extra": null,
        "doctrine_note": "The PDF is the shareable artifact, but the HTML route is the authority surface. It gives crawlers context, gives recruiters a readable summary, and gives Bluehand a stable research landing page that can rank for the work rather than the file format."
      },
      "related_systems": [
        "bis-cp0",
        "sigmem0",
        "bluehand-spine"
      ],
      "diagram_ids": [
        "replay-lifecycle",
        "runtime-transition-graph",
        "drift-detection-loop"
      ],
      "html_path": "/research/deterministic-replay/",
      "pdf_path": "/bluehand-deterministic-replay-architectures-2026.pdf",
      "evidence_path": "/research/deterministic-replay/evidence/",
      "relations": [
        {
          "type": "builds_on",
          "target_slug": "governed-agent-execution"
        },
        {
          "type": "related_to",
          "target_slug": "lineage-aware-memory"
        }
      ],
      "bro": {
        "version": "0.7.1",
        "human_orientation": {
          "purpose": "Orient readers to replay as a trust mechanism for AI systems: consequential transitions should be reconstructable enough to inspect.",
          "problem_addressed": "Agentic workflows can create opaque sequences of model calls, tool use, state changes, summaries, and actions that are hard to explain after the fact.",
          "why_now": "AI systems are moving from isolated chat interactions toward persistent agents, retrieval systems, personal workflows, and institution-facing automation.",
          "reader_takeaway": "Bluehand sees replayability as part of governance, trust, and systems maturity.",
          "inspiration": "CP0/BIS-CP0 transition discipline, SigMem0 replay concepts, and Bluehand’s broader concern with reconstructable reasoning and state mutation.",
          "vision_direction": "AI runtimes where important transitions can be replayed, audited, compared, or challenged without pretending hidden model reasoning is fully accessible."
        },
        "stakeholder_alignment": {
          "best_for": [
            "AI infrastructure recruiters",
            "technical reviewers",
            "grant reviewers",
            "research collaborators",
            "institutional partners"
          ],
          "stakeholder_categories": [
            "recruiter",
            "technical_reviewer",
            "grant_reviewer",
            "technical_collaborator",
            "institutional_partner"
          ],
          "recruiter_relevance": "Provides a capability signal for AI infrastructure, governance, semantic systems, agentic workflow, or local-first execution roles.",
          "grant_relevance": "Supports public-interest framing where responsible AI, trustworthy infrastructure, human-centered systems, or research-to-venture pathways matter.",
          "partner_relevance": "Helps potential partners understand the problem Bluehand is orienting around and where collaboration could fit.",
          "technical_reviewer_relevance": "Surfaces the relevant problem, methods, constraints, failure modes, and implementation boundaries without requiring internal Bluehand context."
        },
        "category_sets": {
          "topic_categories": [
            "deterministic_replay",
            "ai_observability",
            "runtime_lineage",
            "execution_traceability"
          ],
          "capability_categories": [
            "transition_reconstruction",
            "drift_detection",
            "event_logging",
            "runtime_review"
          ],
          "method_categories": [
            "state_transition_recording",
            "replay_validation",
            "comparison_trace",
            "runtime_observability"
          ],
          "constraint_categories": [
            "reconstructability",
            "bounded_logging",
            "privacy_preservation",
            "non_totalizing_replay"
          ],
          "failure_mode_categories": [
            "opaque_execution",
            "state_drift",
            "unreviewable_transition",
            "audit_gap"
          ],
          "visual_categories": [
            "replay_lifecycle",
            "runtime_transition_graph",
            "drift_detection_loop"
          ]
        },
        "public_boundary": {
          "public_claims": [
            "Bluehand identifies deterministic replay as a key design pattern for trustworthy AI execution."
          ],
          "uncertain_claims": [
            "Replay completeness depends on implementation, privacy constraints, and the kind of system being observed."
          ],
          "do_not_infer": [
            "Do not infer total access to hidden model reasoning or perfect reconstruction of every internal state."
          ],
          "implementation_boundary": "This is a public Research Object. Implementation evidence, strict lineage, and runtime proof belong in project/repo-specific surfaces unless explicitly linked."
        },
        "semantic_net": {
          "related_objects": [
            "governed-agent-execution",
            "lineage-aware-memory",
            "semantic-governance"
          ],
          "associative_edges": [
            "related_to",
            "supports",
            "constrains",
            "extends"
          ],
          "optional_lineage": []
        },
        "projections": {
          "html_url": "https://www.blue-hand.org/research/deterministic-replay/",
          "pdf_url": "https://www.blue-hand.org/bluehand-deterministic-replay-architectures-2026.pdf",
          "jsonld_enabled": true,
          "llms_enabled": true,
          "visual_status": "needed",
          "pdf_depth_status": "published_reportlab_projection_v2"
        }
      }
    },
    {
      "artifact_id": "BH-RL-2026-0007",
      "slug": "compression-is-not-evidence",
      "title": "Compression Is Not Evidence",
      "subtitle": "Semantic compression, retrieval projection, transformation ethics, uncertainty exposure, and evidentiary boundaries for AI systems.",
      "abstract": "A Bluehand position paper asserting that summaries, embeddings, clusters, and retrieval projections are semantic transformations, not evidence. Valid use requires lineage, uncertainty, and declared authority boundaries.",
      "artifact_type": "position_paper",
      "publication_status": "canonical",
      "publication_date": "2026-05-19",
      "version_state": "1.0.0",
      "authority_class": "canonical_public",
      "canonical_url": "https://www.blue-hand.org/research/compression-is-not-evidence/",
      "keywords": [
        "AI summarization ethics",
        "semantic compression",
        "retrieval vs evidence",
        "AI transformation governance",
        "trustworthy retrieval systems",
        "compression is not evidence"
      ],
      "domains": [
        "semantic compression",
        "retrieval ethics",
        "AI governance",
        "epistemic integrity"
      ],
      "maturity_note": "Published PDF and canonical doctrine/position artifact; publication status is canonical, while implementation claims remain separate.",
      "source_lineage": "Compiled research artifact; PDF encoding generated via ReportLab (scripts/pdf/generate_encodings.py) from research/registry.json; HTML route /research/compression-is-not-evidence/ remains canonical.",
      "revision": {
        "label": "initial-canonical",
        "number": 1
      },
      "author": {
        "name": "Bluehand Research Group"
      },
      "html": {
        "focus_sections": [
          {
            "title": "Operational thesis",
            "body": "Compression is a transformation, not proof. A summary, embedding, cluster, or retrieved passage may be useful, but usefulness is not evidentiary authority. Bluehand treats semantic compression as an ethical and technical act that must expose preservation, loss, uncertainty, and lineage."
          },
          {
            "title": "Why it matters",
            "body": "AI systems increasingly use compressed context to make decisions. Without declared boundaries, compressed representations can silently overwrite source complexity and convert convenience into false confidence."
          },
          {
            "title": "Governance boundary",
            "body": "This artifact is intentionally canonical as a stance, but that does not make any derived summary or retrieval result automatically authoritative. It strengthens the rule: compressed objects need lineage before they can support claims."
          }
        ],
        "hero_extra": null,
        "doctrine_note": "The PDF is the shareable artifact, but the HTML route is the authority surface. It gives crawlers context, gives recruiters a readable summary, and gives Bluehand a stable research landing page that can rank for the work rather than the file format."
      },
      "related_systems": [
        "sigmem0",
        "bis-cp0",
        "n2-protocol"
      ],
      "diagram_ids": [
        "compression-loss-map",
        "retrieval-projection-model",
        "semantic-transformation-chain"
      ],
      "html_path": "/research/compression-is-not-evidence/",
      "pdf_path": "/bluehand-compression-is-not-evidence-2026.pdf",
      "evidence_path": "/research/compression-is-not-evidence/evidence/",
      "relations": [
        {
          "type": "related_to",
          "target_slug": "lineage-aware-memory"
        },
        {
          "type": "related_to",
          "target_slug": "semantic-governance"
        }
      ],
      "bro": {
        "version": "0.7.1",
        "human_orientation": {
          "purpose": "Provide a clear public doctrine for how Bluehand thinks about summaries, embeddings, clusters, retrieval hits, and derived context.",
          "problem_addressed": "AI systems often turn compressed representations into confident claims, causing semantic loss, source erasure, and false evidentiary authority.",
          "why_now": "AI systems are moving from isolated chat interactions toward persistent agents, retrieval systems, personal workflows, and institution-facing automation.",
          "reader_takeaway": "Bluehand treats semantic transformation as a serious governance problem.",
          "inspiration": "Bluehand/SigMem0 semantic governance principle that compression, retrieval, embedding similarity, summary, and clustering are not evidence without context and authority.",
          "vision_direction": "Derived meaning remains visible, contestable, and bounded rather than silently promoted to truth."
        },
        "stakeholder_alignment": {
          "best_for": [
            "AI infrastructure recruiters",
            "technical reviewers",
            "grant reviewers",
            "research collaborators",
            "institutional partners"
          ],
          "stakeholder_categories": [
            "recruiter",
            "technical_reviewer",
            "grant_reviewer",
            "technical_collaborator",
            "institutional_partner"
          ],
          "recruiter_relevance": "Provides a capability signal for AI infrastructure, governance, semantic systems, agentic workflow, or local-first execution roles.",
          "grant_relevance": "Supports public-interest framing where responsible AI, trustworthy infrastructure, human-centered systems, or research-to-venture pathways matter.",
          "partner_relevance": "Helps potential partners understand the problem Bluehand is orienting around and where collaboration could fit.",
          "technical_reviewer_relevance": "Surfaces the relevant problem, methods, constraints, failure modes, and implementation boundaries without requiring internal Bluehand context."
        },
        "category_sets": {
          "topic_categories": [
            "semantic_compression",
            "retrieval_ethics",
            "epistemic_governance",
            "trustworthy_retrieval"
          ],
          "capability_categories": [
            "uncertainty_exposure",
            "claim_boundary_detection",
            "transformation_disclosure",
            "semantic_loss_detection"
          ],
          "method_categories": [
            "summary_boundary",
            "embedding_boundary",
            "retrieval_projection",
            "claim_scoping"
          ],
          "constraint_categories": [
            "compression_not_evidence",
            "retrieval_not_truth",
            "no_hidden_inference",
            "lineage_when_needed"
          ],
          "failure_mode_categories": [
            "summary_overclaim",
            "source_erasure",
            "semantic_flattening",
            "false_confidence"
          ],
          "visual_categories": [
            "compression_loss_map",
            "retrieval_projection_model",
            "semantic_transformation_chain"
          ]
        },
        "public_boundary": {
          "public_claims": [
            "Bluehand treats compressed semantic objects as transformations, not evidence."
          ],
          "uncertain_claims": [
            "The exact enforcement mechanism depends on implementation context."
          ],
          "do_not_infer": [
            "Do not infer that every summary is invalid; the claim is that summaries require scoped authority."
          ],
          "implementation_boundary": "This is a public Research Object. Implementation evidence, strict lineage, and runtime proof belong in project/repo-specific surfaces unless explicitly linked."
        },
        "semantic_net": {
          "related_objects": [
            "lineage-aware-memory",
            "semantic-governance",
            "deterministic-replay",
            "semantic-reliability"
          ],
          "associative_edges": [
            "related_to",
            "supports",
            "constrains",
            "extends"
          ],
          "optional_lineage": []
        },
        "projections": {
          "html_url": "https://www.blue-hand.org/research/compression-is-not-evidence/",
          "pdf_url": "https://www.blue-hand.org/bluehand-compression-is-not-evidence-2026.pdf",
          "jsonld_enabled": true,
          "llms_enabled": true,
          "visual_status": "needed",
          "pdf_depth_status": "published_reportlab_projection_v2"
        }
      }
    },
    {
      "artifact_id": "BH-RL-2026-0008",
      "slug": "semantic-reliability",
      "title": "Semantic Reliability for AI-Assisted Decision Workflows",
      "subtitle": "Meaning validation across output, reference, interpreter horizon, consequence, and revision loops for high-stakes AI-assisted decisions.",
      "abstract": "A Bluehand research framework for semantic reliability: validating not only what an AI system outputs, but how that output is interpreted, constrained, acted upon, monitored, and revised over time—through parse, reference, horizon, consequence, constraint, and audit gates.",
      "artifact_type": "research_brief",
      "publication_status": "canonical",
      "publication_date": "2026-06-01",
      "version_state": "1.0.0",
      "authority_class": "canonical_public",
      "canonical_url": "https://www.blue-hand.org/research/semantic-reliability/",
      "keywords": [
        "semantic reliability",
        "meaning validation",
        "semantic drift",
        "interpreter horizon",
        "consequence tracking",
        "bounded autonomy",
        "local authority",
        "AI decision workflows"
      ],
      "domains": [
        "AI governance",
        "semantic reliability",
        "decision support",
        "agentic systems",
        "institutional trust"
      ],
      "maturity_note": "Published PDF and canonical HTML; pilot-ready research infrastructure—not clinical certification, regulatory approval, or production deployment.",
      "source_lineage": "Public framework projection from Notion-authored source; PDF encoding bluehand_semantic_reliability_ai_decision_workflows_2026. PDF encoding generated via ReportLab (scripts/pdf/generate_encodings.py) from research/registry.json; HTML route /research/semantic-reliability/ remains canonical.",
      "revision": {
        "label": "initial-canonical",
        "number": 1
      },
      "author": {
        "name": "Bluehand Research Group"
      },
      "html": {
        "focus_sections": [
          {
            "title": "Core relation",
            "body": "Semantic reliability is validated across a complete meaning event: AI output → reference target → interpreter horizon → decision or action → observed consequence → revision loop."
          },
          {
            "title": "Operational stack",
            "body": "Six gates structure validation: parse (coherent units), reference (identifies what it refers to), horizon (intended interpreter), consequence (measurable outcomes), constraint (local boundaries), and audit (reconstructable decisions later)."
          },
          {
            "title": "Governance boundary",
            "body": "Semantic reliability must not become semantic control. The framework preserves operator agency and local authority while making meaning-affecting operations more inspectable. Do not infer clinical certification, regulatory approval, or production deployment from this artifact."
          }
        ],
        "hero_extra": "Meaning is an operational relation among generated output, reference target, interpreter horizon, declared goal, and measurable consequences—not fluent text alone.",
        "doctrine_note": "The PDF is the shareable artifact, but the HTML route is the authority surface for discovery, stakeholder orientation, and related-object navigation across the Research Library."
      },
      "related_systems": [
        "n2-protocol",
        "bis-cp0",
        "bluehand-spine"
      ],
      "diagram_ids": [
        "meaning-event-loop",
        "operational-gate-stack",
        "revision-loop"
      ],
      "html_path": "/research/semantic-reliability/",
      "pdf_path": "/bluehand-semantic-reliability-ai-decision-workflows-2026.pdf",
      "evidence_path": "/research/semantic-reliability/evidence/",
      "relations": [
        {
          "type": "builds_on",
          "target_slug": "semantic-governance"
        },
        {
          "type": "related_to",
          "target_slug": "lineage-aware-memory"
        },
        {
          "type": "related_to",
          "target_slug": "compression-is-not-evidence"
        },
        {
          "type": "related_to",
          "target_slug": "governed-agent-execution"
        },
        {
          "type": "related_to",
          "target_slug": "deterministic-replay"
        }
      ],
      "bro": {
        "version": "0.7.1",
        "human_orientation": {
          "purpose": "Provide a public framework for meaning-validation in AI-assisted workflows: whether outputs remain structurally coherent, referentially grounded, horizon-appropriate, consequence-aware, and constraint-compliant.",
          "problem_addressed": "AI systems are commonly evaluated at the output layer, while deployment risk appears at the interpretation layer—fluent, policy-compliant responses can still be misread, used outside their horizon, or acted on with harmful consequences.",
          "why_now": "High-stakes AI-assisted decision workflows need inspectable interpretation, locally governed constraints, and reviewable lineage—not output fluency alone.",
          "reader_takeaway": "Bluehand treats semantic reliability as operational meaning validation across the full decision event, not as a single-model accuracy score.",
          "inspiration": "Bluehand semantic governance doctrine, N2 semantic anonymization use cases, and governed agent execution patterns where meaning-affecting operations must remain auditable.",
          "vision_direction": "Decision workflows where interpretation boundaries, consequence tracking, and revision loops are first-class infrastructure—not post-hoc compliance overlays."
        },
        "stakeholder_alignment": {
          "best_for": [
            "AI infrastructure recruiters",
            "technical reviewers",
            "grant reviewers",
            "institutional partners",
            "policy and research synthesis teams"
          ],
          "stakeholder_categories": [
            "recruiter",
            "technical_reviewer",
            "grant_reviewer",
            "institutional_partner",
            "technical_collaborator"
          ],
          "recruiter_relevance": "Signals capability in AI governance, semantic systems, decision-support infrastructure, and trustworthy agentic workflow design.",
          "grant_relevance": "Supports responsible-AI and institutional-trust framing where interpretation boundaries and consequence-aware validation matter.",
          "partner_relevance": "Helps partners scope pilots in policy analysis, grant synthesis, code/spec governance, or internal institutional decision support—without over-claiming clinical readiness.",
          "technical_reviewer_relevance": "Surfaces axiom set, operational gates, failure modes, and explicit do-not-infer boundaries without requiring internal Bluehand namespaces."
        },
        "category_sets": {
          "topic_categories": [
            "semantic_reliability",
            "ai_decision_workflows",
            "meaning_validation",
            "institutional_trust"
          ],
          "capability_categories": [
            "interpreter_horizon",
            "consequence_tracking",
            "bounded_autonomy",
            "audit_reconstruction"
          ],
          "method_categories": [
            "parse_gate",
            "reference_gate",
            "horizon_gate",
            "consequence_gate",
            "constraint_gate",
            "audit_gate"
          ],
          "constraint_categories": [
            "local_authority",
            "bounded_pluralism",
            "no_semantic_control",
            "pilot_not_production"
          ],
          "failure_mode_categories": [
            "semantic_drift",
            "horizon_mismatch",
            "false_fluency",
            "unreviewable_consequence"
          ],
          "visual_categories": [
            "meaning_event_loop",
            "operational_gate_stack",
            "revision_loop"
          ]
        },
        "public_boundary": {
          "public_claims": [
            "Bluehand defines semantic reliability as operational validation of meaning across output, reference, horizon, action, consequence, and revision."
          ],
          "uncertain_claims": [
            "First-pilot domain fit depends on partner constraints, review structure, and measurable consequence surfaces in each institution."
          ],
          "do_not_infer": [
            "Do not infer clinical certification, regulatory approval, or production deployment from this artifact.",
            "Do not infer that semantic reliability eliminates plural interpretation—validity remains bounded by evidence, goal, and constraint."
          ],
          "implementation_boundary": "Pilot-ready public Research Object. Field validation, partner-specific constraints, and domain review remain required before high-stakes deployment claims."
        },
        "semantic_net": {
          "related_objects": [
            "semantic-governance",
            "lineage-aware-memory",
            "compression-is-not-evidence",
            "governed-agent-execution",
            "deterministic-replay"
          ],
          "associative_edges": [
            "builds_on",
            "related_to",
            "supports",
            "constrains"
          ],
          "optional_lineage": []
        },
        "projections": {
          "html_url": "https://www.blue-hand.org/research/semantic-reliability/",
          "pdf_url": "https://www.blue-hand.org/bluehand-semantic-reliability-ai-decision-workflows-2026.pdf",
          "jsonld_enabled": true,
          "llms_enabled": true,
          "visual_status": "needed",
          "pdf_depth_status": "published_reportlab_projection_v2"
        }
      }
    },
    {
      "artifact_id": "BH-RL-SRC-0001",
      "slug": "bluehand-framework-v1",
      "title": "Bluehand Framework v1",
      "subtitle": "Structured doctrine object, claims hierarchy, rights layers, ontology, and evaluation criteria for Research Library objects.",
      "abstract": "Bluehand Framework v1 is the strongest surfaced source for category-set thinking. It converts doctrine into structured entities, rights layers, claims hierarchy, ontology, and evaluation criteria.",
      "artifact_type": "framework_reference",
      "publication_status": "active",
      "publication_date": "2026-05-21",
      "version_state": "1.0.0",
      "authority_class": "public_projection",
      "canonical_url": "https://www.blue-hand.org/research/bluehand-framework-v1/",
      "keywords": [
        "structured doctrine",
        "claims hierarchy",
        "ontological taxonomy",
        "rights layers",
        "evaluation criteria",
        "public doctrine"
      ],
      "domains": [
        "research object systems",
        "ontology",
        "rights layers",
        "evaluation criteria"
      ],
      "maturity_note": "Active framework reference; HTML-first review surface, with PDF supporting encoding published.",
      "source_lineage": "Notion source intake from May 21, 2026; framework reference used as a category-taxonomy seed for the public Research Library. PDF encoding generated via ReportLab (scripts/pdf/generate_encodings.py) from operations/research-pdf-required-draft-pack.md; HTML route /research/bluehand-framework-v1/ remains canonical.py) from operations/research-pdf-required-draft-pack.md; HTML route /research/bluehand-framework-v1/ remains canonical.py) from operations/research-pdf-required-draft-pack.md; HTML route /research/bluehand-framework-v1/ remains canonical.py) from operations/research-pdf-required-draft-pack.md; HTML route /research/bluehand-framework-v1/ remains canonical.py) from operations/research-pdf-required-draft-pack.md; HTML route /research/bluehand-framework-v1/ remains canonical.py) from operations/research-pdf-required-draft-pack.md; HTML route /research/bluehand-framework-v1/ remains canonical.py) from operations/research-pdf-required-draft-pack.md; HTML route /research/bluehand-framework-v1/ remains canonical.mjs from operations/research-pdf-required-draft-pack.md; HTML route /research/bluehand-framework-v1/ remains canonical.",
      "revision": {
        "label": "source-intake",
        "number": 1
      },
      "author": {
        "name": "Bluehand Research Group"
      },
      "html": {
        "focus_sections": [
          {
            "title": "Category-set seed",
            "body": "The framework converts doctrine into structured entities, claims hierarchy, ontology categories, and evaluation criteria so the public library can stay machine-projectable without flattening the objects into simple key-value rows."
          },
          {
            "title": "Rights and constraints",
            "body": "It emphasizes rights layers, stewardship rights, non-extraction, and public-good constraints as the public language around the research library’s orientation."
          },
          {
            "title": "Evaluation boundary",
            "body": "This is not the full Research Library and it does not prove implementation. It provides the doctrine and category vocabulary that the review surface can project into visible chips and routing cues."
          }
        ],
        "hero_extra": "This object seeds the category families, rights vocabulary, and evaluation language used by the broader Research Library.",
        "doctrine_note": "The HTML route is the canonical review surface. The published PDF is a portable supporting encoding for sharing and archive—not the authority object."
      },
      "related_systems": [
        "governed-agent-execution",
        "semantic-governance",
        "compression-is-not-evidence"
      ],
      "diagram_ids": [
        "claims-hierarchy-map",
        "rights-layer-comparison",
        "artifact-constellation"
      ],
      "html_path": "/research/bluehand-framework-v1/",
      "pdf_path": "/bluehand-framework-v1-2026.pdf",
      "evidence_path": "/research/bluehand-framework-v1/evidence/",
      "relations": [
        {
          "type": "related_to",
          "target_slug": "governed-agent-execution"
        },
        {
          "type": "related_to",
          "target_slug": "semantic-governance"
        }
      ],
      "bro": {
        "version": "0.7.1",
        "human_orientation": {
          "purpose": "Seed the category families, rights vocabulary, and evaluation language used by the broader Research Library.",
          "problem_addressed": "Public research libraries often collapse doctrine into prose and lose the structured categories needed for stakeholder routing, ontology, and review.",
          "why_now": "Bluehand is moving from individual artifacts to a library of public objects that need shared terms for grant review, technical review, and institutional orientation.",
          "reader_takeaway": "This is the taxonomy seed that lets the public Research Library stay structured without becoming bureaucratic.",
          "inspiration": "The May 21, 2026 Notion framework work that formalized claims hierarchy, rights layers, ontology, and evaluation criteria.",
          "vision_direction": "A public object system with explicit category families and rights-aware review language rather than a loose pile of briefs."
        },
        "stakeholder_alignment": {
          "best_for": [
            "grant writers",
            "research partners",
            "institutional allies"
          ],
          "stakeholder_categories": [
            "grant_writer",
            "research_partner",
            "institutional_ally"
          ],
          "recruiter_relevance": "Shows how Bluehand structures doctrine and category systems for readable public review, even when the artifact is not a brief.",
          "grant_relevance": "Provides the taxonomy and rights-layer language needed to explain grant-facing public objects, evaluation criteria, and institutional positioning without collapsing into technical proof.",
          "partner_relevance": "Helps partners understand the orientation layer that shapes the public Research Library and where collaboration language comes from.",
          "technical_reviewer_relevance": "Surfaces the public ontology, category families, and evaluation vocabulary without pretending to be implementation evidence."
        },
        "category_sets": {
          "topic_categories": [
            "doctrine",
            "ontology",
            "rights_layers",
            "evaluation_framework"
          ],
          "capability_categories": [
            "claims_hierarchy",
            "category_system",
            "taxonomy_seeding",
            "institutional_orientation"
          ],
          "method_categories": [
            "structured_doctrine",
            "ontology_projection",
            "rights_layering",
            "evaluation_framing"
          ],
          "constraint_categories": [
            "non_extraction",
            "no_rights_collapse",
            "public_good_constraint",
            "claim_boundary"
          ],
          "failure_mode_categories": [
            "metadata_overclaim",
            "rights_collapse",
            "doctrine_drift",
            "pdf_only_presentation"
          ],
          "visual_categories": [
            "comparison_table",
            "concept_map",
            "artifact_constellation"
          ]
        },
        "public_boundary": {
          "public_claims": [
            "Bluehand uses a public doctrine object to seed category families, rights language, and evaluation criteria for the Research Library."
          ],
          "uncertain_claims": [
            "The full rights model and operational enforcement remain under development."
          ],
          "do_not_infer": [
            "Do not infer legal counsel, compliance certification, or a finished rights regime."
          ],
          "implementation_boundary": "This object informs the public orientation layer; runtime proof and legal implementation remain in project- or repo-specific surfaces."
        },
        "semantic_net": {
          "related_objects": [
            "governed-agent-execution",
            "semantic-governance",
            "compression-is-not-evidence"
          ],
          "associative_edges": [
            "related_to",
            "supports",
            "extends"
          ],
          "optional_lineage": []
        },
        "projections": {
          "html_url": "https://www.blue-hand.org/research/bluehand-framework-v1/",
          "pdf_url": "https://www.blue-hand.org/bluehand-framework-v1-2026.pdf",
          "jsonld_enabled": true,
          "llms_enabled": true,
          "visual_status": "needed",
          "pdf_depth_status": "published_reportlab_projection_v2"
        }
      }
    },
    {
      "artifact_id": "BH-RL-SRC-0006",
      "slug": "grant-fundability-projection",
      "title": "Bluehand Grant and Fundability Projection",
      "subtitle": "Grant-facing audience projection for SBIR/NSF framing, fundability signals, and stakeholder routing.",
      "abstract": "The grant/fundability material is an audience projection, useful for stakeholder engagement and SE/O routing.",
      "artifact_type": "funding_projection",
      "publication_status": "active",
      "publication_date": "2026-05-21",
      "version_state": "1.0.0",
      "authority_class": "public_projection",
      "canonical_url": "https://www.blue-hand.org/research/grant-fundability-projection/",
      "keywords": [
        "grant readiness",
        "SBIR",
        "STTR",
        "NSF",
        "fundability",
        "commercialization pathway",
        "broader impacts",
        "evidence preparation"
      ],
      "domains": [
        "grant writing",
        "fundability",
        "SBIR",
        "NSF"
      ],
      "maturity_note": "Review-visible grant-facing projection; HTML canonical surface with PDF supporting encoding published.",
      "source_lineage": "Notion source intake from May 21, 2026; audience projection only, used to route grant-facing language in the public Research Library. PDF encoding generated via ReportLab (scripts/pdf/generate_encodings.py) from operations/research-pdf-required-draft-pack.md; HTML route /research/grant-fundability-projection/ remains canonical.py) from operations/research-pdf-required-draft-pack.md; HTML route /research/grant-fundability-projection/ remains canonical.py) from operations/research-pdf-required-draft-pack.md; HTML route /research/grant-fundability-projection/ remains canonical.py) from operations/research-pdf-required-draft-pack.md; HTML route /research/grant-fundability-projection/ remains canonical.py) from operations/research-pdf-required-draft-pack.md; HTML route /research/grant-fundability-projection/ remains canonical.py) from operations/research-pdf-required-draft-pack.md; HTML route /research/grant-fundability-projection/ remains canonical.py) from operations/research-pdf-required-draft-pack.md; HTML route /research/grant-fundability-projection/ remains canonical.mjs from operations/research-pdf-required-draft-pack.md; HTML route /research/grant-fundability-projection/ remains canonical.",
      "revision": {
        "label": "source-intake",
        "number": 1
      },
      "author": {
        "name": "Bluehand Research Group"
      },
      "html": {
        "focus_sections": [
          {
            "title": "Grant-facing routing",
            "body": "The object provides grant-writing and SBIR/NSF language so the Research Library can surface work in a way that is legible to reviewers and institutional allies."
          },
          {
            "title": "Audience projection only",
            "body": "This is not technical evidence. It is a public-facing lens that helps route research objects into fundability-oriented review contexts."
          },
          {
            "title": "Boundary discipline",
            "body": "The projection should not be read as a claim of secured funding, compliance certification, or commercialization readiness."
          }
        ],
        "hero_extra": "This projection is a stakeholder lens. It helps grant-oriented readers see where Bluehand’s public research objects can be framed for review and fundability without overclaiming proof.",
        "doctrine_note": "The HTML route is the review surface. The object exists to guide stakeholder routing, not to replace the underlying research briefs."
      },
      "related_systems": [
        "governed-agent-execution",
        "semantic-governance",
        "personalized-generalized-interface"
      ],
      "diagram_ids": [
        "fundability-routing-map",
        "grant-review-table",
        "stakeholder-projection-card"
      ],
      "html_path": "/research/grant-fundability-projection/",
      "pdf_path": "/bluehand-grant-fundability-projection-2026.pdf",
      "evidence_path": "/research/grant-fundability-projection/evidence/",
      "relations": [
        {
          "type": "related_to",
          "target_slug": "governed-agent-execution"
        },
        {
          "type": "related_to",
          "target_slug": "semantic-governance"
        }
      ],
      "bro": {
        "version": "0.7.1",
        "human_orientation": {
          "purpose": "Provide a grant-facing lens for stakeholder engagement and fundability-oriented routing.",
          "problem_addressed": "Grant and fundability language often gets mixed with technical proof, making it hard to present research in a way that is legible to reviewers without overclaiming.",
          "why_now": "Bluehand is surfacing public research objects that need a review-friendly projection for grant writers, reviewers, and institutional allies.",
          "reader_takeaway": "This object helps reviewers orient quickly without mistaking framing for proof.",
          "inspiration": "The May 21, 2026 Notion projection work that separated audience framing from technical evidence.",
          "vision_direction": "A public project surface where grant-facing language is explicit, bounded, and separate from the underlying research claims."
        },
        "stakeholder_alignment": {
          "best_for": [
            "grant writers",
            "SBIR/NSF reviewers",
            "institutional allies"
          ],
          "stakeholder_categories": [
            "grant_writer",
            "sbir_nsf_reviewer",
            "institutional_ally"
          ],
          "recruiter_relevance": "Shows that Bluehand can structure public objects with grant-facing framing and clear boundaries.",
          "grant_relevance": "Supports grant-ready routing, broader impacts language, and fundability review without conflating projection with evidence.",
          "partner_relevance": "Helps partners see how the Research Library can be presented for external review and program fit.",
          "technical_reviewer_relevance": "Surfaces the review-facing framing while keeping the boundary between audience projection and technical proof explicit."
        },
        "category_sets": {
          "topic_categories": [
            "grant_fundability",
            "sbir_nsf",
            "stakeholder_routing",
            "funding_projection"
          ],
          "capability_categories": [
            "grant_frame_selection",
            "broader_impacts_positioning",
            "evidence_preparation",
            "audience_projection"
          ],
          "method_categories": [
            "audience_projection",
            "proposal_framing",
            "stakeholder_routing",
            "evidence_scoping"
          ],
          "constraint_categories": [
            "not_evidence",
            "not_technical_proof",
            "no_claim_overreach",
            "public_boundary"
          ],
          "failure_mode_categories": [
            "funding_language_overclaim",
            "proposal_drift",
            "evidence_conflation",
            "stakeholder_misalignment"
          ],
          "visual_categories": [
            "comparison_table",
            "callout",
            "artifact_constellation"
          ]
        },
        "public_boundary": {
          "public_claims": [
            "Bluehand uses grant-facing framing to route research objects for stakeholder engagement and fundability review."
          ],
          "uncertain_claims": [
            "The exact funding outcomes and program fit remain unknown until reviewed externally."
          ],
          "do_not_infer": [
            "Do not infer secured grants, compliance certification, or commercialization readiness from the projection alone."
          ],
          "implementation_boundary": "Use this object for public-facing routing and navigation only; technical proof lives in the underlying research objects and project surfaces."
        },
        "semantic_net": {
          "related_objects": [
            "governed-agent-execution",
            "semantic-governance",
            "personalized-generalized-interface"
          ],
          "associative_edges": [
            "related_to",
            "supports",
            "extends"
          ],
          "optional_lineage": []
        },
        "projections": {
          "html_url": "https://www.blue-hand.org/research/grant-fundability-projection/",
          "pdf_url": "https://www.blue-hand.org/bluehand-grant-fundability-projection-2026.pdf",
          "jsonld_enabled": true,
          "llms_enabled": true,
          "visual_status": "needed",
          "pdf_depth_status": "published_reportlab_projection_v2"
        }
      }
    },
    {
      "artifact_id": "BH-RL-2026-0009",
      "slug": "why-enterprise-governance-doesnt-compile",
      "title": "Why Enterprise Governance Doesn't Compile",
      "subtitle": "The missing translation layer between organizational policy and AI execution.",
      "abstract": "Introduces Governance Compilation as a discipline: translating organizational policy, authority, evidence, and institutional memory into machine-executable constraints. Enterprise AI's bottleneck is governance representation—not model capability.",
      "artifact_type": "position_paper",
      "publication_status": "review",
      "publication_date": "2026-06-01",
      "version_state": "0.2.0",
      "authority_class": "review_candidate",
      "canonical_url": "https://www.blue-hand.org/position-papers/why-enterprise-governance-doesnt-compile/",
      "keywords": [
        "Governance Compilation",
        "enterprise AI governance",
        "executable governance",
        "governance contract",
        "governance lineage",
        "authority leakage",
        "policy compilation",
        "agent orchestration",
        "AI authority boundaries"
      ],
      "domains": [
        "enterprise AI governance",
        "executable policy",
        "agentic systems",
        "institutional decision systems"
      ],
      "maturity_note": "Position paper v0.2 (HTML canonical surface); PDF supporting encoding published.",
      "source_lineage": "External position paper HTML (docs/external/position-papers/why-enterprise-governance-doesnt-compile/); synced to public/ at build. PDF encoding generated via ReportLab (scripts/pdf/generate_encodings.py) from docs/external/position-papers/why-enterprise-governance-doesnt-compile/assets/paper-body.html; HTML route /position-papers/why-enterprise-governance-doesnt-compile/ remains canonical.py) from docs/external/position-papers/why-enterprise-governance-doesnt-compile/assets/paper-body.html; HTML route /position-papers/why-enterprise-governance-doesnt-compile/ remains canonical.py) from docs/external/position-papers/why-enterprise-governance-doesnt-compile/assets/paper-body.html; HTML route /position-papers/why-enterprise-governance-doesnt-compile/ remains canonical.py) from docs/external/position-papers/why-enterprise-governance-doesnt-compile/assets/paper-body.html; HTML route /position-papers/why-enterprise-governance-doesnt-compile/ remains canonical.py) from docs/external/position-papers/why-enterprise-governance-doesnt-compile/assets/paper-body.html; HTML route /position-papers/why-enterprise-governance-doesnt-compile/ remains canonical.py) from docs/external/position-papers/why-enterprise-governance-doesnt-compile/assets/paper-body.html; HTML route /position-papers/why-enterprise-governance-doesnt-compile/ remains canonical.py) from docs/external/position-papers/why-enterprise-governance-doesnt-compile/assets/paper-body.html; HTML route /position-papers/why-enterprise-governance-doesnt-compile/ remains canonical.mjs from docs/external/position-papers/why-enterprise-governance-doesnt-compile/assets/paper-body.html; HTML route /position-papers/why-enterprise-governance-doesnt-compile/ remains canonical.",
      "revision": {
        "label": "category-staking-glossary-v0.2",
        "number": 2
      },
      "author": {
        "name": "BlueHand Solutions LLC"
      },
      "html": {
        "focus_sections": [
          {
            "title": "Thesis",
            "body": "Orchestration solved execution complexity; governance-constrained workflows still lack a machine-readable translation layer between institutional policy and agent execution."
          },
          {
            "title": "Why now",
            "body": "Models and agent frameworks are capable enough for high-stakes workflows—the blocker is representable, auditable governance rather than tool routing."
          }
        ],
        "hero_extra": "Audience: enterprise architects, governance leaders, and researchers evaluating AI deployment in consequential workflows.",
        "doctrine_note": "The full position paper is a self-contained HTML surface at /position-papers/why-enterprise-governance-doesnt-compile/—not the standard Research Library brief layout."
      },
      "related_systems": [
        "n2-protocol",
        "bis-cp0"
      ],
      "diagram_ids": [],
      "html_path": "/position-papers/why-enterprise-governance-doesnt-compile/",
      "pdf_path": "/bluehand-why-enterprise-governance-doesnt-compile-2026.pdf",
      "evidence_path": "/position-papers/why-enterprise-governance-doesnt-compile/evidence/",
      "relations": [
        {
          "type": "related_to",
          "target_slug": "semantic-governance"
        },
        {
          "type": "related_to",
          "target_slug": "governed-agent-execution"
        },
        {
          "type": "related_to",
          "target_slug": "compression-is-not-evidence"
        },
        {
          "type": "related_to",
          "target_slug": "what-is-governance-compilation"
        },
        {
          "type": "related_to",
          "target_slug": "authority-leakage"
        },
        {
          "type": "related_to",
          "target_slug": "missing-layer-policy-and-agents"
        },
        {
          "type": "related_to",
          "target_slug": "governance-teams-review-prompts"
        },
        {
          "type": "related_to",
          "target_slug": "enterprise-governance-doesnt-compile-brief"
        }
      ],
      "bro": {
        "version": "0.7.1",
        "human_orientation": {
          "purpose": "Stake the Governance Compilation category: a discipline and infrastructure layer for making organizational cognition machine-visible across changing AI runtimes.",
          "problem_addressed": "Organizations govern cognition through policy, authority, evidence, and audit—but AI systems operate through prompts, agents, and tools with a largely manual translation layer.",
          "why_now": "Agent frameworks and models can plan, retrieve, and execute; consequential workflows remain governance-constrained rather than execution-constrained.",
          "reader_takeaway": "Governance Compilation is the discipline; this paper is the canonical source for the category terms governance contract, governance lineage, authority leakage, and executable governance.",
          "inspiration": "Observed gap between mature institutional decision systems and agent orchestration stacks that treat governance as post-hoc policy prose.",
          "vision_direction": "Toward executable governance: representable authority, admissible evidence, reasoning standards, and institutional commitments compilable into agent workflows."
        },
        "stakeholder_alignment": {
          "best_for": [
            "Enterprise architects",
            "Governance leaders",
            "AI infrastructure recruiters",
            "Grant / institutional reviewers",
            "Technical collaborators"
          ],
          "stakeholder_categories": [
            "enterprise_architect",
            "governance_leader",
            "technical_reviewer",
            "grant_reviewer",
            "technical_collaborator"
          ],
          "recruiter_relevance": "Signals depth in AI governance, agentic infrastructure, and institutional decision systems—not prompt engineering alone.",
          "grant_relevance": "Frames public-interest AI deployment hesitancy as a governance compilation problem relevant to trustworthy infrastructure research.",
          "partner_relevance": "Helps enterprise and institutional partners locate Bluehand’s governance-first AI infrastructure orientation.",
          "technical_reviewer_relevance": "Surfaces the distinction between execution complexity and governance representation with open research questions."
        },
        "category_sets": {
          "topic_categories": [
            "enterprise_ai_governance",
            "executable_policy",
            "agentic_systems",
            "institutional_decision_systems"
          ],
          "capability_categories": [
            "policy_representation",
            "authority_boundary_modeling",
            "evidence_admissibility",
            "audit_controls"
          ],
          "method_categories": [
            "governance_compilation",
            "workflow_orchestration",
            "institutional_memory"
          ],
          "constraint_categories": [
            "governance_not_prompts_only",
            "no_hidden_authority",
            "evidence_requirements",
            "external_safe"
          ],
          "failure_mode_categories": [
            "manual_translation_layer",
            "policy_prose_without_execution",
            "orchestration_without_governance",
            "false_confidence_from_tools"
          ],
          "visual_categories": [
            "position_paper_layout",
            "section_navigation",
            "reading_progress"
          ]
        },
        "public_boundary": {
          "public_claims": [
            "Bluehand publishes this as an external-safe concepts and analysis position paper."
          ],
          "uncertain_claims": [
            "Specific compilation mechanisms and product timelines remain open research and engineering work."
          ],
          "do_not_infer": [
            "Do not infer proprietary implementation detail, repository layout, internal contract numbering, or compliance certification from this paper."
          ],
          "implementation_boundary": "Concepts and analysis only; implementation proof belongs in project-specific surfaces unless explicitly linked."
        },
        "semantic_net": {
          "related_objects": [
            "semantic-governance",
            "governed-agent-execution",
            "compression-is-not-evidence",
            "semantic-reliability",
            "what-is-governance-compilation",
            "authority-leakage",
            "missing-layer-policy-and-agents",
            "governance-teams-review-prompts",
            "enterprise-governance-doesnt-compile-brief"
          ],
          "associative_edges": [
            "related_to",
            "supports",
            "extends"
          ],
          "optional_lineage": []
        },
        "projections": {
          "html_url": "https://www.blue-hand.org/position-papers/why-enterprise-governance-doesnt-compile/",
          "fulltext_md_url": "https://www.blue-hand.org/position-papers/why-enterprise-governance-doesnt-compile/paper.md",
          "fulltext_txt_url": "https://www.blue-hand.org/position-papers/why-enterprise-governance-doesnt-compile/paper.txt",
          "pdf_url": "https://www.blue-hand.org/bluehand-why-enterprise-governance-doesnt-compile-2026.pdf",
          "jsonld_enabled": false,
          "llms_enabled": true,
          "visual_status": "published_html_position_paper",
          "pdf_depth_status": "published_reportlab_projection_v2"
        }
      }
    },
    {
      "artifact_id": "BH-RL-2026-0010",
      "slug": "what-is-governance-compilation",
      "title": "What Is Governance Compilation?",
      "subtitle": "Definitional foothill essay — retrieval surface for the Governance Compilation category.",
      "abstract": "Defines Governance Compilation as the discipline of translating organizational governance artifacts into machine-executable constraints. Short essay for human search and LLM retrieval; canonical analysis remains in the position paper.",
      "artifact_type": "essay",
      "publication_status": "review",
      "publication_date": "2026-06-01",
      "version_state": "1.0.0",
      "authority_class": "review_candidate",
      "canonical_url": "https://www.blue-hand.org/essays/what-is-governance-compilation/",
      "keywords": [
        "What is Governance Compilation",
        "Governance Compilation definition",
        "executable governance",
        "governance contract",
        "governance lineage"
      ],
      "domains": [
        "Governance Compilation",
        "enterprise AI governance",
        "executable policy"
      ],
      "maturity_note": "Foothill essay v1.0; links to canonical position paper.",
      "source_lineage": "Derivative essay; canonical mountain: why-enterprise-governance-doesnt-compile position paper. PDF encoding generated via ReportLab (scripts/pdf/generate_encodings.py) from docs/external/essays/what-is-governance-compilation/index.html; HTML route /essays/what-is-governance-compilation/ remains canonical.py) from docs/external/essays/what-is-governance-compilation/index.html; HTML route /essays/what-is-governance-compilation/ remains canonical.py) from docs/external/essays/what-is-governance-compilation/index.html; HTML route /essays/what-is-governance-compilation/ remains canonical.py) from docs/external/essays/what-is-governance-compilation/index.html; HTML route /essays/what-is-governance-compilation/ remains canonical.py) from docs/external/essays/what-is-governance-compilation/index.html; HTML route /essays/what-is-governance-compilation/ remains canonical.py) from docs/external/essays/what-is-governance-compilation/index.html; HTML route /essays/what-is-governance-compilation/ remains canonical.py) from docs/external/essays/what-is-governance-compilation/index.html; HTML route /essays/what-is-governance-compilation/ remains canonical.mjs from docs/external/essays/what-is-governance-compilation/index.html; HTML route /essays/what-is-governance-compilation/ remains canonical.",
      "revision": {
        "label": "initial-foothill-essay",
        "number": 1
      },
      "author": {
        "name": "BlueHand Solutions LLC"
      },
      "html": {
        "focus_sections": [
          {
            "title": "Definition",
            "body": "Governance Compilation translates policy, authority, evidence, escalation, and institutional memory into machine-executable constraints."
          },
          {
            "title": "Canonical source",
            "body": "Why Enterprise Governance Doesn't Compile at /position-papers/why-enterprise-governance-doesnt-compile/"
          }
        ],
        "hero_extra": "Optimized for the query \"What is Governance Compilation?\" — cite the position paper for full analysis.",
        "doctrine_note": "Essays are foothills; the position paper is the mountain."
      },
      "related_systems": [],
      "diagram_ids": [],
      "html_path": "/essays/what-is-governance-compilation/",
      "pdf_path": "/bluehand-what-is-governance-compilation-2026.pdf",
      "evidence_path": "/essays/what-is-governance-compilation/evidence/",
      "relations": [
        {
          "type": "builds_on",
          "target_slug": "why-enterprise-governance-doesnt-compile"
        },
        {
          "type": "related_to",
          "target_slug": "semantic-governance"
        }
      ],
      "bro": {
        "version": "0.7.1",
        "human_orientation": {
          "purpose": "Give search engines, analysts, and LLMs a citable definitional surface for Governance Compilation.",
          "problem_addressed": "Category terms need short canonical definitions—not only a 7,000-word paper.",
          "why_now": "Governance Compilation is being introduced as a discipline; retrieval surfaces must exist alongside the full thesis.",
          "reader_takeaway": "Governance Compilation is a named discipline—this page defines it; the position paper proves and extends it.",
          "inspiration": "Foothill essay strategy from the Governance Compilation discoverability plan.",
          "vision_direction": "Essays point up to the position paper; the paper remains authoritative."
        },
        "stakeholder_alignment": {
          "best_for": [
            "Enterprise architects",
            "Governance leaders",
            "Researchers",
            "Analysts citing definitions"
          ],
          "stakeholder_categories": [
            "enterprise_architect",
            "governance_leader",
            "technical_reviewer"
          ],
          "recruiter_relevance": "Signals category creation and governance-first AI infrastructure thinking.",
          "grant_relevance": "Frames trustworthy AI infrastructure as compilation problem, not moderation alone.",
          "partner_relevance": "Quick orientation before reading the full position paper.",
          "technical_reviewer_relevance": "Compact definitions of contract, lineage, and executable governance."
        },
        "category_sets": {
          "topic_categories": [
            "governance_compilation",
            "enterprise_ai_governance",
            "executable_policy"
          ],
          "capability_categories": [
            "definition_surface",
            "citation_anchor"
          ],
          "method_categories": [
            "category_creation",
            "foothill_publication"
          ],
          "constraint_categories": [
            "not_substitute_for_mountain",
            "external_safe"
          ],
          "failure_mode_categories": [
            "definition_without_lineage",
            "essay_overclaim"
          ],
          "visual_categories": [
            "pipeline_diagram"
          ]
        },
        "public_boundary": {
          "public_claims": [
            "This essay defines Governance Compilation for citation and search."
          ],
          "uncertain_claims": [
            "Implementation mechanisms remain open research."
          ],
          "do_not_infer": [
            "Do not treat this essay as exhaustive analysis or product roadmap."
          ],
          "implementation_boundary": "Read the position paper for evidence, tables, and research questions."
        },
        "semantic_net": {
          "related_objects": [
            "why-enterprise-governance-doesnt-compile",
            "semantic-governance",
            "governed-agent-execution"
          ],
          "associative_edges": [
            "builds_on",
            "related_to"
          ],
          "optional_lineage": []
        },
        "projections": {
          "html_url": "https://www.blue-hand.org/essays/what-is-governance-compilation/",
          "pdf_url": "https://www.blue-hand.org/bluehand-what-is-governance-compilation-2026.pdf",
          "jsonld_enabled": true,
          "llms_enabled": true,
          "visual_status": "published_essay",
          "pdf_depth_status": "published_reportlab_projection_v2"
        }
      }
    },
    {
      "artifact_id": "BH-RL-2026-0011",
      "slug": "authority-leakage",
      "title": "Authority Leakage: The Hidden Failure Mode of Enterprise AI",
      "subtitle": "When governance intent lives in prompts, agents exceed the authority organizations believe they granted.",
      "abstract": "Defines authority leakage: AI systems acting outside declared authority because governance lives in prompts rather than enforceable governance contracts. Foothill essay for citation and search.",
      "artifact_type": "essay",
      "publication_status": "review",
      "publication_date": "2026-06-01",
      "version_state": "1.0.0",
      "authority_class": "review_candidate",
      "canonical_url": "https://www.blue-hand.org/essays/authority-leakage/",
      "keywords": [
        "authority leakage",
        "enterprise AI governance",
        "governance contract",
        "Governance Compilation"
      ],
      "domains": [
        "Governance Compilation",
        "enterprise AI governance"
      ],
      "maturity_note": "Foothill essay v1.0.",
      "source_lineage": "Foothill essay; canonical mountain: why-enterprise-governance-doesnt-compile. PDF encoding generated via ReportLab (scripts/pdf/generate_encodings.py) from docs/external/essays/authority-leakage/index.html; HTML route /essays/authority-leakage/ remains canonical.py) from docs/external/essays/authority-leakage/index.html; HTML route /essays/authority-leakage/ remains canonical.py) from docs/external/essays/authority-leakage/index.html; HTML route /essays/authority-leakage/ remains canonical.py) from docs/external/essays/authority-leakage/index.html; HTML route /essays/authority-leakage/ remains canonical.py) from docs/external/essays/authority-leakage/index.html; HTML route /essays/authority-leakage/ remains canonical.py) from docs/external/essays/authority-leakage/index.html; HTML route /essays/authority-leakage/ remains canonical.py) from docs/external/essays/authority-leakage/index.html; HTML route /essays/authority-leakage/ remains canonical.mjs from docs/external/essays/authority-leakage/index.html; HTML route /essays/authority-leakage/ remains canonical.",
      "revision": {
        "label": "initial-foothill-essay",
        "number": 1
      },
      "author": {
        "name": "BlueHand Solutions LLC"
      },
      "html": {
        "focus_sections": [
          {
            "title": "Thesis",
            "body": "Defines authority leakage: AI systems acting outside declared authority because governance lives in prompts rather than enforceable governance contracts. Foothill essay for citation and search."
          }
        ],
        "hero_extra": "When governance intent lives in prompts, agents exceed the authority organizations believe they granted.",
        "doctrine_note": "Essays are foothills; the position paper is the mountain."
      },
      "related_systems": [],
      "diagram_ids": [],
      "html_path": "/essays/authority-leakage/",
      "pdf_path": "/bluehand-authority-leakage-2026.pdf",
      "evidence_path": "/essays/authority-leakage/evidence/",
      "relations": [
        {
          "type": "builds_on",
          "target_slug": "why-enterprise-governance-doesnt-compile"
        },
        {
          "type": "related_to",
          "target_slug": "what-is-governance-compilation"
        }
      ],
      "bro": {
        "version": "0.7.1",
        "human_orientation": {
          "purpose": "Foothill essay supporting the Governance Compilation category: Authority Leakage: The Hidden Failure Mode of Enterprise AI",
          "problem_addressed": "AI systems exceed declared authority because governance intent is embedded in prompts instead of machine-checkable governance contracts.",
          "why_now": "Category terms need retrieval surfaces beyond the canonical position paper.",
          "reader_takeaway": "When governance intent lives in prompts, agents exceed the authority organizations believe they granted.",
          "inspiration": "Governance Compilation discoverability stack—foothill essays.",
          "vision_direction": "Essays point to the mountain; the position paper remains authoritative."
        },
        "stakeholder_alignment": {
          "best_for": [
            "Enterprise architects",
            "Governance leaders",
            "Researchers",
            "Analysts"
          ],
          "stakeholder_categories": [
            "enterprise_architect",
            "governance_leader",
            "technical_reviewer"
          ],
          "recruiter_relevance": "Signals governance-first AI infrastructure category creation.",
          "grant_relevance": "Frames trustworthy AI as compilation, not moderation alone.",
          "partner_relevance": "Quick orientation before the full position paper.",
          "technical_reviewer_relevance": "Compact argument with link to canonical evidence."
        },
        "category_sets": {
          "topic_categories": [
            "governance_compilation",
            "enterprise_ai_governance"
          ],
          "capability_categories": [
            "citation_anchor",
            "definition_surface"
          ],
          "method_categories": [
            "foothill_publication",
            "category_creation"
          ],
          "constraint_categories": [
            "not_substitute_for_mountain",
            "external_safe"
          ],
          "failure_mode_categories": [
            "essay_overclaim"
          ],
          "visual_categories": [
            "essay_layout"
          ]
        },
        "public_boundary": {
          "public_claims": [
            "This essay supports citation and search for: Authority Leakage: The Hidden Failure Mode of Enterprise AI"
          ],
          "uncertain_claims": [
            "Implementation mechanisms remain open research."
          ],
          "do_not_infer": [
            "Do not treat this essay as exhaustive analysis or product roadmap."
          ],
          "implementation_boundary": "Read the position paper for full evidence and research questions."
        },
        "semantic_net": {
          "related_objects": [
            "why-enterprise-governance-doesnt-compile",
            "what-is-governance-compilation",
            "semantic-governance"
          ],
          "associative_edges": [
            "builds_on",
            "related_to"
          ],
          "optional_lineage": []
        },
        "projections": {
          "html_url": "https://www.blue-hand.org/essays/authority-leakage/",
          "pdf_url": "https://www.blue-hand.org/bluehand-authority-leakage-2026.pdf",
          "jsonld_enabled": true,
          "llms_enabled": true,
          "visual_status": "published_essay",
          "pdf_depth_status": "published_reportlab_projection_v2"
        }
      }
    },
    {
      "artifact_id": "BH-RL-2026-0012",
      "slug": "missing-layer-policy-and-agents",
      "title": "The Missing Layer Between Policy and Agents",
      "subtitle": "Enterprise policy and agent runtimes still rely on manual translation—Governance Compilation names that gap.",
      "abstract": "Explains the missing translation layer between institutional policy and agent execution: represent, compile, preserve lineage, audit constraints—not orchestration alone.",
      "artifact_type": "essay",
      "publication_status": "review",
      "publication_date": "2026-06-01",
      "version_state": "1.0.0",
      "authority_class": "review_candidate",
      "canonical_url": "https://www.blue-hand.org/essays/missing-layer-policy-and-agents/",
      "keywords": [
        "policy and agents",
        "Governance Compilation",
        "governance translation layer",
        "executable governance"
      ],
      "domains": [
        "Governance Compilation",
        "enterprise AI governance"
      ],
      "maturity_note": "Foothill essay v1.0.",
      "source_lineage": "Foothill essay; canonical mountain: why-enterprise-governance-doesnt-compile. PDF encoding generated via ReportLab (scripts/pdf/generate_encodings.py) from docs/external/essays/missing-layer-policy-and-agents/index.html; HTML route /essays/missing-layer-policy-and-agents/ remains canonical.py) from docs/external/essays/missing-layer-policy-and-agents/index.html; HTML route /essays/missing-layer-policy-and-agents/ remains canonical.py) from docs/external/essays/missing-layer-policy-and-agents/index.html; HTML route /essays/missing-layer-policy-and-agents/ remains canonical.py) from docs/external/essays/missing-layer-policy-and-agents/index.html; HTML route /essays/missing-layer-policy-and-agents/ remains canonical.py) from docs/external/essays/missing-layer-policy-and-agents/index.html; HTML route /essays/missing-layer-policy-and-agents/ remains canonical.py) from docs/external/essays/missing-layer-policy-and-agents/index.html; HTML route /essays/missing-layer-policy-and-agents/ remains canonical.py) from docs/external/essays/missing-layer-policy-and-agents/index.html; HTML route /essays/missing-layer-policy-and-agents/ remains canonical.mjs from docs/external/essays/missing-layer-policy-and-agents/index.html; HTML route /essays/missing-layer-policy-and-agents/ remains canonical.",
      "revision": {
        "label": "initial-foothill-essay",
        "number": 1
      },
      "author": {
        "name": "BlueHand Solutions LLC"
      },
      "html": {
        "focus_sections": [
          {
            "title": "Thesis",
            "body": "Explains the missing translation layer between institutional policy and agent execution: represent, compile, preserve lineage, audit constraints—not orchestration alone."
          }
        ],
        "hero_extra": "Enterprise policy and agent runtimes still rely on manual translation—Governance Compilation names that gap.",
        "doctrine_note": "Essays are foothills; the position paper is the mountain."
      },
      "related_systems": [],
      "diagram_ids": [],
      "html_path": "/essays/missing-layer-policy-and-agents/",
      "pdf_path": "/bluehand-missing-layer-policy-and-agents-2026.pdf",
      "evidence_path": "/essays/missing-layer-policy-and-agents/evidence/",
      "relations": [
        {
          "type": "builds_on",
          "target_slug": "why-enterprise-governance-doesnt-compile"
        },
        {
          "type": "related_to",
          "target_slug": "what-is-governance-compilation"
        }
      ],
      "bro": {
        "version": "0.7.1",
        "human_orientation": {
          "purpose": "Foothill essay supporting the Governance Compilation category: The Missing Layer Between Policy and Agents",
          "problem_addressed": "Policy and agent runtimes speak different languages; organizations fill the gap with manual translation that does not scale.",
          "why_now": "Category terms need retrieval surfaces beyond the canonical position paper.",
          "reader_takeaway": "Enterprise policy and agent runtimes still rely on manual translation—Governance Compilation names that gap.",
          "inspiration": "Governance Compilation discoverability stack—foothill essays.",
          "vision_direction": "Essays point to the mountain; the position paper remains authoritative."
        },
        "stakeholder_alignment": {
          "best_for": [
            "Enterprise architects",
            "Governance leaders",
            "Researchers",
            "Analysts"
          ],
          "stakeholder_categories": [
            "enterprise_architect",
            "governance_leader",
            "technical_reviewer"
          ],
          "recruiter_relevance": "Signals governance-first AI infrastructure category creation.",
          "grant_relevance": "Frames trustworthy AI as compilation, not moderation alone.",
          "partner_relevance": "Quick orientation before the full position paper.",
          "technical_reviewer_relevance": "Compact argument with link to canonical evidence."
        },
        "category_sets": {
          "topic_categories": [
            "governance_compilation",
            "enterprise_ai_governance"
          ],
          "capability_categories": [
            "citation_anchor",
            "definition_surface"
          ],
          "method_categories": [
            "foothill_publication",
            "category_creation"
          ],
          "constraint_categories": [
            "not_substitute_for_mountain",
            "external_safe"
          ],
          "failure_mode_categories": [
            "essay_overclaim"
          ],
          "visual_categories": [
            "essay_layout"
          ]
        },
        "public_boundary": {
          "public_claims": [
            "This essay supports citation and search for: The Missing Layer Between Policy and Agents"
          ],
          "uncertain_claims": [
            "Implementation mechanisms remain open research."
          ],
          "do_not_infer": [
            "Do not treat this essay as exhaustive analysis or product roadmap."
          ],
          "implementation_boundary": "Read the position paper for full evidence and research questions."
        },
        "semantic_net": {
          "related_objects": [
            "why-enterprise-governance-doesnt-compile",
            "what-is-governance-compilation",
            "semantic-governance"
          ],
          "associative_edges": [
            "builds_on",
            "related_to"
          ],
          "optional_lineage": []
        },
        "projections": {
          "html_url": "https://www.blue-hand.org/essays/missing-layer-policy-and-agents/",
          "pdf_url": "https://www.blue-hand.org/bluehand-missing-layer-policy-and-agents-2026.pdf",
          "jsonld_enabled": true,
          "llms_enabled": true,
          "visual_status": "published_essay",
          "pdf_depth_status": "published_reportlab_projection_v2"
        }
      }
    },
    {
      "artifact_id": "BH-RL-2026-0013",
      "slug": "governance-teams-review-prompts",
      "title": "Why AI Governance Teams Review Prompts Instead of Policies",
      "subtitle": "Prompt review is a rational symptom of missing Governance Compilation infrastructure.",
      "abstract": "Why governance programs center on prompt review: prompts are the only governance surface the runtime exposes. What changes when policies compile into checkable constraints.",
      "artifact_type": "essay",
      "publication_status": "review",
      "publication_date": "2026-06-01",
      "version_state": "1.0.0",
      "authority_class": "review_candidate",
      "canonical_url": "https://www.blue-hand.org/essays/governance-teams-review-prompts/",
      "keywords": [
        "AI governance teams",
        "prompt governance",
        "policy review",
        "Governance Compilation"
      ],
      "domains": [
        "Governance Compilation",
        "enterprise AI governance"
      ],
      "maturity_note": "Foothill essay v1.0.",
      "source_lineage": "Foothill essay; canonical mountain: why-enterprise-governance-doesnt-compile. PDF encoding generated via ReportLab (scripts/pdf/generate_encodings.py) from docs/external/essays/governance-teams-review-prompts/index.html; HTML route /essays/governance-teams-review-prompts/ remains canonical.py) from docs/external/essays/governance-teams-review-prompts/index.html; HTML route /essays/governance-teams-review-prompts/ remains canonical.py) from docs/external/essays/governance-teams-review-prompts/index.html; HTML route /essays/governance-teams-review-prompts/ remains canonical.py) from docs/external/essays/governance-teams-review-prompts/index.html; HTML route /essays/governance-teams-review-prompts/ remains canonical.py) from docs/external/essays/governance-teams-review-prompts/index.html; HTML route /essays/governance-teams-review-prompts/ remains canonical.py) from docs/external/essays/governance-teams-review-prompts/index.html; HTML route /essays/governance-teams-review-prompts/ remains canonical.py) from docs/external/essays/governance-teams-review-prompts/index.html; HTML route /essays/governance-teams-review-prompts/ remains canonical.mjs from docs/external/essays/governance-teams-review-prompts/index.html; HTML route /essays/governance-teams-review-prompts/ remains canonical.",
      "revision": {
        "label": "initial-foothill-essay",
        "number": 1
      },
      "author": {
        "name": "BlueHand Solutions LLC"
      },
      "html": {
        "focus_sections": [
          {
            "title": "Thesis",
            "body": "Why governance programs center on prompt review: prompts are the only governance surface the runtime exposes. What changes when policies compile into checkable constraints."
          }
        ],
        "hero_extra": "Prompt review is a rational symptom of missing Governance Compilation infrastructure.",
        "doctrine_note": "Essays are foothills; the position paper is the mountain."
      },
      "related_systems": [],
      "diagram_ids": [],
      "html_path": "/essays/governance-teams-review-prompts/",
      "pdf_path": "/bluehand-governance-teams-review-prompts-2026.pdf",
      "evidence_path": "/essays/governance-teams-review-prompts/evidence/",
      "relations": [
        {
          "type": "builds_on",
          "target_slug": "why-enterprise-governance-doesnt-compile"
        },
        {
          "type": "related_to",
          "target_slug": "what-is-governance-compilation"
        }
      ],
      "bro": {
        "version": "0.7.1",
        "human_orientation": {
          "purpose": "Foothill essay supporting the Governance Compilation category: Why AI Governance Teams Review Prompts Instead of Policies",
          "problem_addressed": "Governance teams review prompts because runtimes expose no compiled policy surface—only natural-language instructions.",
          "why_now": "Category terms need retrieval surfaces beyond the canonical position paper.",
          "reader_takeaway": "Prompt review is a rational symptom of missing Governance Compilation infrastructure.",
          "inspiration": "Governance Compilation discoverability stack—foothill essays.",
          "vision_direction": "Essays point to the mountain; the position paper remains authoritative."
        },
        "stakeholder_alignment": {
          "best_for": [
            "Enterprise architects",
            "Governance leaders",
            "Researchers",
            "Analysts"
          ],
          "stakeholder_categories": [
            "enterprise_architect",
            "governance_leader",
            "technical_reviewer"
          ],
          "recruiter_relevance": "Signals governance-first AI infrastructure category creation.",
          "grant_relevance": "Frames trustworthy AI as compilation, not moderation alone.",
          "partner_relevance": "Quick orientation before the full position paper.",
          "technical_reviewer_relevance": "Compact argument with link to canonical evidence."
        },
        "category_sets": {
          "topic_categories": [
            "governance_compilation",
            "enterprise_ai_governance"
          ],
          "capability_categories": [
            "citation_anchor",
            "definition_surface"
          ],
          "method_categories": [
            "foothill_publication",
            "category_creation"
          ],
          "constraint_categories": [
            "not_substitute_for_mountain",
            "external_safe"
          ],
          "failure_mode_categories": [
            "essay_overclaim"
          ],
          "visual_categories": [
            "essay_layout"
          ]
        },
        "public_boundary": {
          "public_claims": [
            "This essay supports citation and search for: Why AI Governance Teams Review Prompts Instead of Policies"
          ],
          "uncertain_claims": [
            "Implementation mechanisms remain open research."
          ],
          "do_not_infer": [
            "Do not treat this essay as exhaustive analysis or product roadmap."
          ],
          "implementation_boundary": "Read the position paper for full evidence and research questions."
        },
        "semantic_net": {
          "related_objects": [
            "why-enterprise-governance-doesnt-compile",
            "what-is-governance-compilation",
            "semantic-governance"
          ],
          "associative_edges": [
            "builds_on",
            "related_to"
          ],
          "optional_lineage": []
        },
        "projections": {
          "html_url": "https://www.blue-hand.org/essays/governance-teams-review-prompts/",
          "pdf_url": "https://www.blue-hand.org/bluehand-governance-teams-review-prompts-2026.pdf",
          "jsonld_enabled": true,
          "llms_enabled": true,
          "visual_status": "published_essay",
          "pdf_depth_status": "published_reportlab_projection_v2"
        }
      }
    },
    {
      "artifact_id": "BH-RL-2026-0014",
      "slug": "enterprise-governance-doesnt-compile-brief",
      "title": "Why Enterprise Governance Doesn't Compile — Brief Thesis",
      "subtitle": "Short thesis for sharing and citation; full analysis in the position paper.",
      "abstract": "Five-sentence thesis: enterprise AI solved execution, not governance representation. Governance Compilation is the discipline of machine-executable organizational constraints.",
      "artifact_type": "essay",
      "publication_status": "review",
      "publication_date": "2026-06-01",
      "version_state": "1.0.0",
      "authority_class": "review_candidate",
      "canonical_url": "https://www.blue-hand.org/essays/enterprise-governance-doesnt-compile-brief/",
      "keywords": [
        "Why Enterprise Governance Doesn't Compile",
        "Governance Compilation",
        "executable governance",
        "enterprise AI governance"
      ],
      "domains": [
        "Governance Compilation",
        "enterprise AI governance"
      ],
      "maturity_note": "Foothill essay v1.0.",
      "source_lineage": "Foothill essay; canonical mountain: why-enterprise-governance-doesnt-compile. PDF encoding generated via ReportLab (scripts/pdf/generate_encodings.py) from docs/external/essays/enterprise-governance-doesnt-compile-brief/index.html; HTML route /essays/enterprise-governance-doesnt-compile-brief/ remains canonical.py) from docs/external/essays/enterprise-governance-doesnt-compile-brief/index.html; HTML route /essays/enterprise-governance-doesnt-compile-brief/ remains canonical.py) from docs/external/essays/enterprise-governance-doesnt-compile-brief/index.html; HTML route /essays/enterprise-governance-doesnt-compile-brief/ remains canonical.py) from docs/external/essays/enterprise-governance-doesnt-compile-brief/index.html; HTML route /essays/enterprise-governance-doesnt-compile-brief/ remains canonical.py) from docs/external/essays/enterprise-governance-doesnt-compile-brief/index.html; HTML route /essays/enterprise-governance-doesnt-compile-brief/ remains canonical.py) from docs/external/essays/enterprise-governance-doesnt-compile-brief/index.html; HTML route /essays/enterprise-governance-doesnt-compile-brief/ remains canonical.py) from docs/external/essays/enterprise-governance-doesnt-compile-brief/index.html; HTML route /essays/enterprise-governance-doesnt-compile-brief/ remains canonical.mjs from docs/external/essays/enterprise-governance-doesnt-compile-brief/index.html; HTML route /essays/enterprise-governance-doesnt-compile-brief/ remains canonical.",
      "revision": {
        "label": "initial-foothill-essay",
        "number": 1
      },
      "author": {
        "name": "BlueHand Solutions LLC"
      },
      "html": {
        "focus_sections": [
          {
            "title": "Thesis",
            "body": "Five-sentence thesis: enterprise AI solved execution, not governance representation. Governance Compilation is the discipline of machine-executable organizational constraints."
          }
        ],
        "hero_extra": "Short thesis for sharing and citation; full analysis in the position paper.",
        "doctrine_note": "Essays are foothills; the position paper is the mountain."
      },
      "related_systems": [],
      "diagram_ids": [],
      "html_path": "/essays/enterprise-governance-doesnt-compile-brief/",
      "pdf_path": "/bluehand-enterprise-governance-doesnt-compile-brief-2026.pdf",
      "evidence_path": "/essays/enterprise-governance-doesnt-compile-brief/evidence/",
      "relations": [
        {
          "type": "builds_on",
          "target_slug": "why-enterprise-governance-doesnt-compile"
        },
        {
          "type": "related_to",
          "target_slug": "what-is-governance-compilation"
        }
      ],
      "bro": {
        "version": "0.7.1",
        "human_orientation": {
          "purpose": "Foothill essay supporting the Governance Compilation category: Why Enterprise Governance Doesn't Compile — Brief Thesis",
          "problem_addressed": "Enterprise AI scaled execution faster than governance representation; manual translation cannot keep pace with agent deployment and model churn.",
          "why_now": "Category terms need retrieval surfaces beyond the canonical position paper.",
          "reader_takeaway": "Short thesis for sharing and citation; full analysis in the position paper.",
          "inspiration": "Governance Compilation discoverability stack—foothill essays.",
          "vision_direction": "Essays point to the mountain; the position paper remains authoritative."
        },
        "stakeholder_alignment": {
          "best_for": [
            "Enterprise architects",
            "Governance leaders",
            "Researchers",
            "Analysts"
          ],
          "stakeholder_categories": [
            "enterprise_architect",
            "governance_leader",
            "technical_reviewer"
          ],
          "recruiter_relevance": "Signals governance-first AI infrastructure category creation.",
          "grant_relevance": "Frames trustworthy AI as compilation, not moderation alone.",
          "partner_relevance": "Quick orientation before the full position paper.",
          "technical_reviewer_relevance": "Compact argument with link to canonical evidence."
        },
        "category_sets": {
          "topic_categories": [
            "governance_compilation",
            "enterprise_ai_governance"
          ],
          "capability_categories": [
            "citation_anchor",
            "definition_surface"
          ],
          "method_categories": [
            "foothill_publication",
            "category_creation"
          ],
          "constraint_categories": [
            "not_substitute_for_mountain",
            "external_safe"
          ],
          "failure_mode_categories": [
            "essay_overclaim"
          ],
          "visual_categories": [
            "essay_layout"
          ]
        },
        "public_boundary": {
          "public_claims": [
            "This essay supports citation and search for: Why Enterprise Governance Doesn't Compile — Brief Thesis"
          ],
          "uncertain_claims": [
            "Implementation mechanisms remain open research."
          ],
          "do_not_infer": [
            "Do not treat this essay as exhaustive analysis or product roadmap."
          ],
          "implementation_boundary": "Read the position paper for full evidence and research questions."
        },
        "semantic_net": {
          "related_objects": [
            "why-enterprise-governance-doesnt-compile",
            "what-is-governance-compilation",
            "semantic-governance"
          ],
          "associative_edges": [
            "builds_on",
            "related_to"
          ],
          "optional_lineage": []
        },
        "projections": {
          "html_url": "https://www.blue-hand.org/essays/enterprise-governance-doesnt-compile-brief/",
          "pdf_url": "https://www.blue-hand.org/bluehand-enterprise-governance-doesnt-compile-brief-2026.pdf",
          "jsonld_enabled": true,
          "llms_enabled": true,
          "visual_status": "published_essay",
          "pdf_depth_status": "published_reportlab_projection_v2"
        }
      }
    }
  ],
  "schema_version": "1.0.0",
  "generated_at": "2026-06-13T02:43:48.932Z",
  "source_commit": "0c0acb75cdda8855f181a7f77c49cb3b6036d732",
  "canonical_url": "https://www.blue-hand.org/research/registry.public.json",
  "authority_class": "public_projection",
  "governed_by": "/schemas/registry.schema.json",
  "compile_receipt": {
    "compiler": "compile-research-registry.mjs",
    "pipeline": "research:compile",
    "generated_at": "2026-06-13T02:43:48.932Z",
    "source_commit": "0c0acb75cdda8855f181a7f77c49cb3b6036d732",
    "inputs": [
      "research/registry.json"
    ],
    "schema": "/schemas/registry.schema.json"
  },
  "integrity_hash": "e69e550154f0a7d783d446c47a278a09b2c17b1441fcc4b70c09b0fd27ec5f5d"
}
