[{"aliases":["xn--mwe.com","ᚲ","ᚲ.com"],"canonicalOwner":"/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"ᚲ.com organizes Machine Intelligence knowledge into inspectable definitions, questions, comparisons, research syntheses, evidence qualifications, and authoritative ecosystem routes. It publishes knowledge, not governance, registry status, assurance certification, or legal recognition.","id":"K-COM-001","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":110,"title":"Machine Intelligence Knowledge","topic":null,"type":"homepage","url":"/"},{"aliases":[],"canonicalOwner":"/machine-communication/protocol-negotiation/profiles/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"Four named compatibility profiles define version support, unknown-extension handling, replay policy, and canonicalization without granting authority or security.","id":"K10-COLLECTION-PROFILES","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Protocol Compatibility Profiles","topic":"machine-communication-protocols","type":"protocol-profile-index","url":"/machine-communication/protocol-negotiation/profiles/"},{"aliases":[],"canonicalOwner":"/evidence/controlled-release/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"Four synthetic controlled-release manifests expose public projections and field-level receipts while excluding protected values and source material.","id":"K10-COLLECTION-RELEASES","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Controlled-Release Manifests","topic":"evidence-provenance","type":"controlled-release-index","url":"/evidence/controlled-release/"},{"aliases":[],"canonicalOwner":"/assurance-dashboard/systems/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"Twelve static system records preserve nine distinct assurance states and explicit evidence boundaries; the collection is not live telemetry.","id":"K10-COLLECTION-DASHBOARD","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Assurance Dashboard System Records","topic":"cyber-physical-mission-assurance","type":"assurance-dashboard-index","url":"/assurance-dashboard/systems/"},{"aliases":[],"canonicalOwner":"/machine-communication/protocol-negotiation/profiles/strict-1-0/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"Strict 1.0 supports 1.0 and applies REJECT to unknown critical extensions.","id":"FCP-PROFILE-K10-STRICT-10","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Strict 1.0","topic":"machine-communication-protocols","type":"protocol-compatibility-profile","url":"/machine-communication/protocol-negotiation/profiles/strict-1-0/"},{"aliases":[],"canonicalOwner":"/machine-communication/protocol-negotiation/profiles/compatible-1-x/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"Compatible 1.x supports 1.0, 1.1 and applies REJECT to unknown critical extensions.","id":"FCP-PROFILE-K10-COMPAT-1X","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Compatible 1.x","topic":"machine-communication-protocols","type":"protocol-compatibility-profile","url":"/machine-communication/protocol-negotiation/profiles/compatible-1-x/"},{"aliases":[],"canonicalOwner":"/machine-communication/protocol-negotiation/profiles/audit-only/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"Audit only supports 1.0, 1.1 and applies REPORT_WITHOUT_EXECUTION to unknown critical extensions.","id":"FCP-PROFILE-K10-AUDIT","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Audit only","topic":"machine-communication-protocols","type":"protocol-compatibility-profile","url":"/machine-communication/protocol-negotiation/profiles/audit-only/"},{"aliases":[],"canonicalOwner":"/machine-communication/protocol-negotiation/profiles/fail-closed/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"Fail closed supports 1.1 and applies REJECT to unknown critical extensions.","id":"FCP-PROFILE-K10-FAIL-CLOSED","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Fail closed","topic":"machine-communication-protocols","type":"protocol-compatibility-profile","url":"/machine-communication/protocol-negotiation/profiles/fail-closed/"},{"aliases":[],"canonicalOwner":"/machine-communication/history-review-queue/hrev-k10-001/","claimStatus":"PRIMARY_SOURCE_REVIEW_REQUIRED","directAnswer":"Formal neuron model remains PRIMARY_SOURCE_REVIEW_REQUIRED; no confidence reassessment or status promotion has occurred.","id":"HREV-K10-001","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"History Review: Formal neuron model","topic":"runic-digital-infrastructure","type":"history-review-record","url":"/machine-communication/history-review-queue/hrev-k10-001/"},{"aliases":[],"canonicalOwner":"/machine-communication/history-review-queue/hrev-k10-002/","claimStatus":"PRIMARY_SOURCE_REVIEW_REQUIRED","directAnswer":"Machine intelligence test framing remains PRIMARY_SOURCE_REVIEW_REQUIRED; no confidence reassessment or status promotion has occurred.","id":"HREV-K10-002","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"History Review: Machine intelligence test framing","topic":"runic-digital-infrastructure","type":"history-review-record","url":"/machine-communication/history-review-queue/hrev-k10-002/"},{"aliases":[],"canonicalOwner":"/machine-communication/history-review-queue/hrev-k10-003/","claimStatus":"PRIMARY_SOURCE_REVIEW_REQUIRED","directAnswer":"Dartmouth research program remains PRIMARY_SOURCE_REVIEW_REQUIRED; no confidence reassessment or status promotion has occurred.","id":"HREV-K10-003","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"History Review: Dartmouth research program","topic":"runic-digital-infrastructure","type":"history-review-record","url":"/machine-communication/history-review-queue/hrev-k10-003/"},{"aliases":[],"canonicalOwner":"/machine-communication/history-review-queue/hrev-k10-004/","claimStatus":"PRIMARY_SOURCE_REVIEW_REQUIRED","directAnswer":"Perceptron public milestone remains PRIMARY_SOURCE_REVIEW_REQUIRED; no confidence reassessment or status promotion has occurred.","id":"HREV-K10-004","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"History Review: Perceptron public milestone","topic":"runic-digital-infrastructure","type":"history-review-record","url":"/machine-communication/history-review-queue/hrev-k10-004/"},{"aliases":[],"canonicalOwner":"/machine-communication/history-review-queue/hrev-k10-005/","claimStatus":"PRIMARY_SOURCE_REVIEW_REQUIRED","directAnswer":"ALPAC report remains PRIMARY_SOURCE_REVIEW_REQUIRED; no confidence reassessment or status promotion has occurred.","id":"HREV-K10-005","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"History Review: ALPAC report","topic":"runic-digital-infrastructure","type":"history-review-record","url":"/machine-communication/history-review-queue/hrev-k10-005/"},{"aliases":[],"canonicalOwner":"/machine-communication/history-review-queue/hrev-k10-006/","claimStatus":"PRIMARY_SOURCE_REVIEW_REQUIRED","directAnswer":"Perceptron critique remains PRIMARY_SOURCE_REVIEW_REQUIRED; no confidence reassessment or status promotion has occurred.","id":"HREV-K10-006","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"History Review: Perceptron critique","topic":"runic-digital-infrastructure","type":"history-review-record","url":"/machine-communication/history-review-queue/hrev-k10-006/"},{"aliases":[],"canonicalOwner":"/machine-communication/history-review-queue/hrev-k10-007/","claimStatus":"PRIMARY_SOURCE_REVIEW_REQUIRED","directAnswer":"Reverse-mode automatic differentiation remains PRIMARY_SOURCE_REVIEW_REQUIRED; no confidence reassessment or status promotion has occurred.","id":"HREV-K10-007","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"History Review: Reverse-mode automatic differentiation","topic":"runic-digital-infrastructure","type":"history-review-record","url":"/machine-communication/history-review-queue/hrev-k10-007/"},{"aliases":[],"canonicalOwner":"/machine-communication/history-review-queue/hrev-k10-008/","claimStatus":"PRIMARY_SOURCE_REVIEW_REQUIRED","directAnswer":"Backpropagation resurgence remains PRIMARY_SOURCE_REVIEW_REQUIRED; no confidence reassessment or status promotion has occurred.","id":"HREV-K10-008","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"History Review: Backpropagation resurgence","topic":"runic-digital-infrastructure","type":"history-review-record","url":"/machine-communication/history-review-queue/hrev-k10-008/"},{"aliases":[],"canonicalOwner":"/machine-communication/history-review-queue/hrev-k10-009/","claimStatus":"PRIMARY_SOURCE_REVIEW_REQUIRED","directAnswer":"Chess system victory remains PRIMARY_SOURCE_REVIEW_REQUIRED; no confidence reassessment or status promotion has occurred.","id":"HREV-K10-009","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"History Review: Chess system victory","topic":"runic-digital-infrastructure","type":"history-review-record","url":"/machine-communication/history-review-queue/hrev-k10-009/"},{"aliases":[],"canonicalOwner":"/machine-communication/history-review-queue/hrev-k10-010/","claimStatus":"PRIMARY_SOURCE_REVIEW_REQUIRED","directAnswer":"GPU neural-network acceleration remains PRIMARY_SOURCE_REVIEW_REQUIRED; no confidence reassessment or status promotion has occurred.","id":"HREV-K10-010","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"History Review: GPU neural-network acceleration","topic":"runic-digital-infrastructure","type":"history-review-record","url":"/machine-communication/history-review-queue/hrev-k10-010/"},{"aliases":[],"canonicalOwner":"/machine-communication/history-review-queue/hrev-k10-011/","claimStatus":"PRIMARY_SOURCE_REVIEW_REQUIRED","directAnswer":"ImageNet deep-learning breakthrough remains PRIMARY_SOURCE_REVIEW_REQUIRED; no confidence reassessment or status promotion has occurred.","id":"HREV-K10-011","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"History Review: ImageNet deep-learning breakthrough","topic":"runic-digital-infrastructure","type":"history-review-record","url":"/machine-communication/history-review-queue/hrev-k10-011/"},{"aliases":[],"canonicalOwner":"/machine-communication/history-review-queue/hrev-k10-012/","claimStatus":"PRIMARY_SOURCE_REVIEW_REQUIRED","directAnswer":"Transformer architecture remains PRIMARY_SOURCE_REVIEW_REQUIRED; no confidence reassessment or status promotion has occurred.","id":"HREV-K10-012","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"History Review: Transformer architecture","topic":"runic-digital-infrastructure","type":"history-review-record","url":"/machine-communication/history-review-queue/hrev-k10-012/"},{"aliases":[],"canonicalOwner":"/machine-communication/history-review-queue/hrev-k10-013/","claimStatus":"PRIMARY_SOURCE_REVIEW_REQUIRED","directAnswer":"Retrieval-augmented generation remains PRIMARY_SOURCE_REVIEW_REQUIRED; no confidence reassessment or status promotion has occurred.","id":"HREV-K10-013","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"History Review: Retrieval-augmented generation","topic":"runic-digital-infrastructure","type":"history-review-record","url":"/machine-communication/history-review-queue/hrev-k10-013/"},{"aliases":[],"canonicalOwner":"/machine-communication/history-review-queue/hrev-k10-014/","claimStatus":"PRIMARY_SOURCE_REVIEW_REQUIRED","directAnswer":"Tool-using language models remains PRIMARY_SOURCE_REVIEW_REQUIRED; no confidence reassessment or status promotion has occurred.","id":"HREV-K10-014","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"History Review: Tool-using language models","topic":"runic-digital-infrastructure","type":"history-review-record","url":"/machine-communication/history-review-queue/hrev-k10-014/"},{"aliases":[],"canonicalOwner":"/machine-communication/history-review-queue/hrev-k10-015/","claimStatus":"QUARANTINED_PENDING_PRIMARY_SOURCES","directAnswer":"Inference-time reasoning and autonomous research systems remains QUARANTINED_PENDING_PRIMARY_SOURCES; no confidence reassessment or status promotion has occurred.","id":"HREV-K10-015","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"History Review: Inference-time reasoning and autonomous research systems","topic":"runic-digital-infrastructure","type":"history-review-record","url":"/machine-communication/history-review-queue/hrev-k10-015/"},{"aliases":[],"canonicalOwner":"/assurance-case/common-cause/cct-k10-001/","claimStatus":"SYNTHETIC COMPOSED ASSURANCE TRACE","directAnswer":"Power continuity derives a DEGRADED root because one or more mandatory shared dependencies are degraded, stale, or unavailable.","id":"CCT-K10-001","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Power continuity","topic":"cyber-physical-mission-assurance","type":"common-cause-trace","url":"/assurance-case/common-cause/cct-k10-001/"},{"aliases":[],"canonicalOwner":"/assurance-case/common-cause/cct-k10-002/","claimStatus":"SYNTHETIC COMPOSED ASSURANCE TRACE","directAnswer":"Cooling continuity derives a DEGRADED root because one or more mandatory shared dependencies are degraded, stale, or unavailable.","id":"CCT-K10-002","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Cooling continuity","topic":"cyber-physical-mission-assurance","type":"common-cause-trace","url":"/assurance-case/common-cause/cct-k10-002/"},{"aliases":[],"canonicalOwner":"/assurance-case/common-cause/cct-k10-003/","claimStatus":"SYNTHETIC COMPOSED ASSURANCE TRACE","directAnswer":"Workload identity continuity derives a DEGRADED root because one or more mandatory shared dependencies are degraded, stale, or unavailable.","id":"CCT-K10-003","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Workload identity continuity","topic":"cyber-physical-mission-assurance","type":"common-cause-trace","url":"/assurance-case/common-cause/cct-k10-003/"},{"aliases":[],"canonicalOwner":"/assurance-case/common-cause/cct-k10-004/","claimStatus":"SYNTHETIC COMPOSED ASSURANCE TRACE","directAnswer":"Management-plane containment derives a DEGRADED root because one or more mandatory shared dependencies are degraded, stale, or unavailable.","id":"CCT-K10-004","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Management-plane containment","topic":"cyber-physical-mission-assurance","type":"common-cause-trace","url":"/assurance-case/common-cause/cct-k10-004/"},{"aliases":[],"canonicalOwner":"/assurance-case/common-cause/cct-k10-005/","claimStatus":"SYNTHETIC COMPOSED ASSURANCE TRACE","directAnswer":"Supply-chain evidence continuity derives a DEGRADED root because one or more mandatory shared dependencies are degraded, stale, or unavailable.","id":"CCT-K10-005","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Supply-chain evidence continuity","topic":"cyber-physical-mission-assurance","type":"common-cause-trace","url":"/assurance-case/common-cause/cct-k10-005/"},{"aliases":[],"canonicalOwner":"/assurance-case/common-cause/cct-k10-006/","claimStatus":"SYNTHETIC COMPOSED ASSURANCE TRACE","directAnswer":"Recovery and restoration derives a DEGRADED root because one or more mandatory shared dependencies are degraded, stale, or unavailable.","id":"CCT-K10-006","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Recovery and restoration","topic":"cyber-physical-mission-assurance","type":"common-cause-trace","url":"/assurance-case/common-cause/cct-k10-006/"},{"aliases":[],"canonicalOwner":"/assurance-case/common-cause/cct-k10-007/","claimStatus":"SYNTHETIC COMPOSED ASSURANCE TRACE","directAnswer":"Protocol conformance continuity derives a DEGRADED root because one or more mandatory shared dependencies are degraded, stale, or unavailable.","id":"CCT-K10-007","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Protocol conformance continuity","topic":"cyber-physical-mission-assurance","type":"common-cause-trace","url":"/assurance-case/common-cause/cct-k10-007/"},{"aliases":[],"canonicalOwner":"/assurance-case/common-cause/cct-k10-008/","claimStatus":"SYNTHETIC COMPOSED ASSURANCE TRACE","directAnswer":"Observation and currentness continuity derives a DEGRADED root because one or more mandatory shared dependencies are degraded, stale, or unavailable.","id":"CCT-K10-008","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Observation and currentness continuity","topic":"cyber-physical-mission-assurance","type":"common-cause-trace","url":"/assurance-case/common-cause/cct-k10-008/"},{"aliases":[],"canonicalOwner":"/cryptographic-agility/transition-plan/discovery/","claimStatus":"IN_PROGRESS","directAnswer":"Phase 1, Discovery and inventory, is IN_PROGRESS in the static reference plan.","id":"CTP-K10-001","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Discovery and inventory","topic":"evidence-provenance","type":"crypto-transition-phase","url":"/cryptographic-agility/transition-plan/discovery/"},{"aliases":[],"canonicalOwner":"/cryptographic-agility/transition-plan/pilot/","claimStatus":"PLANNED","directAnswer":"Phase 2, Bounded pilot, is PLANNED in the static reference plan.","id":"CTP-K10-002","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Bounded pilot","topic":"evidence-provenance","type":"crypto-transition-phase","url":"/cryptographic-agility/transition-plan/pilot/"},{"aliases":[],"canonicalOwner":"/cryptographic-agility/transition-plan/hybrid/","claimStatus":"PLANNED","directAnswer":"Phase 3, Hybrid operation, is PLANNED in the static reference plan.","id":"CTP-K10-003","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Hybrid operation","topic":"evidence-provenance","type":"crypto-transition-phase","url":"/cryptographic-agility/transition-plan/hybrid/"},{"aliases":[],"canonicalOwner":"/cryptographic-agility/transition-plan/rollout/","claimStatus":"BLOCKED","directAnswer":"Phase 4, Controlled rollout, is BLOCKED in the static reference plan.","id":"CTP-K10-004","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Controlled rollout","topic":"evidence-provenance","type":"crypto-transition-phase","url":"/cryptographic-agility/transition-plan/rollout/"},{"aliases":[],"canonicalOwner":"/cryptographic-agility/transition-plan/rollback/","claimStatus":"DESIGNED","directAnswer":"Phase 5, Rollback readiness, is DESIGNED in the static reference plan.","id":"CTP-K10-005","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Rollback readiness","topic":"evidence-provenance","type":"crypto-transition-phase","url":"/cryptographic-agility/transition-plan/rollback/"},{"aliases":[],"canonicalOwner":"/cryptographic-agility/transition-plan/legacy-verification/","claimStatus":"DESIGNED","directAnswer":"Phase 6, Legacy verification, is DESIGNED in the static reference plan.","id":"CTP-K10-006","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Legacy verification","topic":"evidence-provenance","type":"crypto-transition-phase","url":"/cryptographic-agility/transition-plan/legacy-verification/"},{"aliases":[],"canonicalOwner":"/cryptographic-agility/transition-plan/archive-resigning/","claimStatus":"PLANNED","directAnswer":"Phase 7, Archive re-signing, is PLANNED in the static reference plan.","id":"CTP-K10-007","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Archive re-signing","topic":"evidence-provenance","type":"crypto-transition-phase","url":"/cryptographic-agility/transition-plan/archive-resigning/"},{"aliases":[],"canonicalOwner":"/cryptographic-agility/transition-plan/supplier-exit/","claimStatus":"BLOCKED","directAnswer":"Phase 8, Supplier exit, is BLOCKED in the static reference plan.","id":"CTP-K10-008","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Supplier exit","topic":"evidence-provenance","type":"crypto-transition-phase","url":"/cryptographic-agility/transition-plan/supplier-exit/"},{"aliases":[],"canonicalOwner":"/cryptographic-agility/transition-plan/inventory-attestation/","claimStatus":"IN_PROGRESS","directAnswer":"Phase 9, Cryptographic inventory attestation, is IN_PROGRESS in the static reference plan.","id":"CTP-K10-009","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Cryptographic inventory attestation","topic":"evidence-provenance","type":"crypto-transition-phase","url":"/cryptographic-agility/transition-plan/inventory-attestation/"},{"aliases":[],"canonicalOwner":"/procurement/evaluation-audit/acqa-k10-001/","claimStatus":"SYNTHETIC EVALUATION AUDIT TRAIL; NO AWARD","directAnswer":"Critical-datacenter mission assurance architecture preserves 9 synthetic evaluator-offer score rows, consensus, challenge, correction, and any recusal while making no award.","id":"ACQA-K10-001","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Evaluation Audit: Critical-datacenter mission assurance architecture","topic":"cyber-physical-mission-assurance","type":"acquisition-audit-trail","url":"/procurement/evaluation-audit/acqa-k10-001/"},{"aliases":[],"canonicalOwner":"/procurement/evaluation-audit/acqa-k10-002/","claimStatus":"SYNTHETIC EVALUATION AUDIT TRAIL; NO AWARD","directAnswer":"Autonomous cyber-defense evaluation range preserves 9 synthetic evaluator-offer score rows, consensus, challenge, correction, and any recusal while making no award.","id":"ACQA-K10-002","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Evaluation Audit: Autonomous cyber-defense evaluation range","topic":"cyber-physical-mission-assurance","type":"acquisition-audit-trail","url":"/procurement/evaluation-audit/acqa-k10-002/"},{"aliases":[],"canonicalOwner":"/procurement/evaluation-audit/acqa-k10-003/","claimStatus":"SYNTHETIC EVALUATION AUDIT TRAIL; NO AWARD","directAnswer":"Supply-chain evidence and incident readiness preserves 9 synthetic evaluator-offer score rows, consensus, challenge, correction, and any recusal while making no award.","id":"ACQA-K10-003","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Evaluation Audit: Supply-chain evidence and incident readiness","topic":"cyber-physical-mission-assurance","type":"acquisition-audit-trail","url":"/procurement/evaluation-audit/acqa-k10-003/"},{"aliases":[],"canonicalOwner":"/procurement/evaluation-audit/acqa-k10-004/","claimStatus":"SYNTHETIC EVALUATION AUDIT TRAIL; NO AWARD","directAnswer":"Facility adaptation and applicability analysis preserves 9 synthetic evaluator-offer score rows, consensus, challenge, correction, and any recusal while making no award.","id":"ACQA-K10-004","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Evaluation Audit: Facility adaptation and applicability analysis","topic":"cyber-physical-mission-assurance","type":"acquisition-audit-trail","url":"/procurement/evaluation-audit/acqa-k10-004/"},{"aliases":[],"canonicalOwner":"/procurement/evaluation-audit/acqa-k10-005/","claimStatus":"SYNTHETIC EVALUATION AUDIT TRAIL; NO AWARD","directAnswer":"Machine-communication protocol conformance preserves 9 synthetic evaluator-offer score rows, consensus, challenge, correction, and any recusal while making no award.","id":"ACQA-K10-005","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Evaluation Audit: Machine-communication protocol conformance","topic":"cyber-physical-mission-assurance","type":"acquisition-audit-trail","url":"/procurement/evaluation-audit/acqa-k10-005/"},{"aliases":[],"canonicalOwner":"/procurement/evaluation-audit/acqa-k10-006/","claimStatus":"SYNTHETIC EVALUATION AUDIT TRAIL; NO AWARD","directAnswer":"Offline currentness observation operations preserves 9 synthetic evaluator-offer score rows, consensus, challenge, correction, and any recusal while making no award.","id":"ACQA-K10-006","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Evaluation Audit: Offline currentness observation operations","topic":"cyber-physical-mission-assurance","type":"acquisition-audit-trail","url":"/procurement/evaluation-audit/acqa-k10-006/"},{"aliases":[],"canonicalOwner":"/evidence/controlled-release/crm-k10-001/","claimStatus":"REFERENCE CONTROLLED RELEASE","directAnswer":"CRM-K10-001 publishes 6 field classes and excludes 6 protected classes under partition PART-K09-PUBLIC.","id":"CRM-K10-001","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Controlled Release CRM-K10-001","topic":"evidence-provenance","type":"controlled-release-manifest","url":"/evidence/controlled-release/crm-k10-001/"},{"aliases":[],"canonicalOwner":"/evidence/controlled-release/crm-k10-002/","claimStatus":"REFERENCE CONTROLLED RELEASE","directAnswer":"CRM-K10-002 publishes 7 field classes and excludes 4 protected classes under partition PART-K09-CONTROLLED.","id":"CRM-K10-002","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Controlled Release CRM-K10-002","topic":"evidence-provenance","type":"controlled-release-manifest","url":"/evidence/controlled-release/crm-k10-002/"},{"aliases":[],"canonicalOwner":"/evidence/controlled-release/crm-k10-003/","claimStatus":"REFERENCE CONTROLLED RELEASE","directAnswer":"CRM-K10-003 publishes 6 field classes and excludes 1 protected classes under partition PART-K09-PROTECTED.","id":"CRM-K10-003","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Controlled Release CRM-K10-003","topic":"evidence-provenance","type":"controlled-release-manifest","url":"/evidence/controlled-release/crm-k10-003/"},{"aliases":[],"canonicalOwner":"/evidence/controlled-release/crm-k10-004/","claimStatus":"REFERENCE CONTROLLED RELEASE","directAnswer":"CRM-K10-004 publishes 7 field classes and excludes 2 protected classes under partition PART-K09-SELECTION.","id":"CRM-K10-004","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Controlled Release CRM-K10-004","topic":"evidence-provenance","type":"controlled-release-manifest","url":"/evidence/controlled-release/crm-k10-004/"},{"aliases":[],"canonicalOwner":"/assurance-dashboard/systems/protocol-negotiation/","claimStatus":"TESTED","directAnswer":"Fuþorc protocol negotiation harness is TESTED in the static K10 dataset. The state is bounded by the listed evidence and explicit non-claims.","id":"DASH-K10-001","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Fuþorc protocol negotiation harness","topic":"cyber-physical-mission-assurance","type":"assurance-dashboard-system","url":"/assurance-dashboard/systems/protocol-negotiation/"},{"aliases":[],"canonicalOwner":"/assurance-dashboard/systems/history-review/","claimStatus":"IMPLEMENTED","directAnswer":"History primary-source review queue is IMPLEMENTED in the static K10 dataset. The state is bounded by the listed evidence and explicit non-claims.","id":"DASH-K10-002","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"History primary-source review queue","topic":"cyber-physical-mission-assurance","type":"assurance-dashboard-system","url":"/assurance-dashboard/systems/history-review/"},{"aliases":[],"canonicalOwner":"/assurance-dashboard/systems/idn-history/","claimStatus":"TESTED","directAnswer":"Offline IDN observation history is TESTED in the static K10 dataset. The state is bounded by the listed evidence and explicit non-claims.","id":"DASH-K10-003","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Offline IDN observation history","topic":"cyber-physical-mission-assurance","type":"assurance-dashboard-system","url":"/assurance-dashboard/systems/idn-history/"},{"aliases":[],"canonicalOwner":"/assurance-dashboard/systems/facility-workbook/","claimStatus":"TESTED","directAnswer":"Facility workbook migration and merge is TESTED in the static K10 dataset. The state is bounded by the listed evidence and explicit non-claims.","id":"DASH-K10-004","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Facility workbook migration and merge","topic":"cyber-physical-mission-assurance","type":"assurance-dashboard-system","url":"/assurance-dashboard/systems/facility-workbook/"},{"aliases":[],"canonicalOwner":"/assurance-dashboard/systems/common-cause/","claimStatus":"DEGRADED","directAnswer":"Common-cause assurance analysis is DEGRADED in the static K10 dataset. The state is bounded by the listed evidence and explicit non-claims.","id":"DASH-K10-005","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Common-cause assurance analysis","topic":"cyber-physical-mission-assurance","type":"assurance-dashboard-system","url":"/assurance-dashboard/systems/common-cause/"},{"aliases":[],"canonicalOwner":"/assurance-dashboard/systems/crypto-transition/","claimStatus":"DEGRADED","directAnswer":"Phased cryptographic transition plan is DEGRADED in the static K10 dataset. The state is bounded by the listed evidence and explicit non-claims.","id":"DASH-K10-006","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Phased cryptographic transition plan","topic":"cyber-physical-mission-assurance","type":"assurance-dashboard-system","url":"/assurance-dashboard/systems/crypto-transition/"},{"aliases":[],"canonicalOwner":"/assurance-dashboard/systems/acquisition-audit/","claimStatus":"IMPLEMENTED","directAnswer":"Acquisition evaluation audit trail is IMPLEMENTED in the static K10 dataset. The state is bounded by the listed evidence and explicit non-claims.","id":"DASH-K10-007","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Acquisition evaluation audit trail","topic":"cyber-physical-mission-assurance","type":"assurance-dashboard-system","url":"/assurance-dashboard/systems/acquisition-audit/"},{"aliases":[],"canonicalOwner":"/assurance-dashboard/systems/scheduler-import/","claimStatus":"TESTED","directAnswer":"Offline scheduler-result importer is TESTED in the static K10 dataset. The state is bounded by the listed evidence and explicit non-claims.","id":"DASH-K10-008","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Offline scheduler-result importer","topic":"cyber-physical-mission-assurance","type":"assurance-dashboard-system","url":"/assurance-dashboard/systems/scheduler-import/"},{"aliases":[],"canonicalOwner":"/assurance-dashboard/systems/redaction/","claimStatus":"TESTED","directAnswer":"Evidence redaction and leakage tests is TESTED in the static K10 dataset. The state is bounded by the listed evidence and explicit non-claims.","id":"DASH-K10-009","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Evidence redaction and leakage tests","topic":"cyber-physical-mission-assurance","type":"assurance-dashboard-system","url":"/assurance-dashboard/systems/redaction/"},{"aliases":[],"canonicalOwner":"/assurance-dashboard/systems/live-host/","claimStatus":"UNKNOWN","directAnswer":"Live-host verification is UNKNOWN in the static K10 dataset. The state is bounded by the listed evidence and explicit non-claims.","id":"DASH-K10-010","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Live-host verification","topic":"cyber-physical-mission-assurance","type":"assurance-dashboard-system","url":"/assurance-dashboard/systems/live-host/"},{"aliases":[],"canonicalOwner":"/assurance-dashboard/systems/named-screen-reader/","claimStatus":"UNAVAILABLE","directAnswer":"Independent named screen-reader validation is UNAVAILABLE in the static K10 dataset. The state is bounded by the listed evidence and explicit non-claims.","id":"DASH-K10-011","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Independent named screen-reader validation","topic":"cyber-physical-mission-assurance","type":"assurance-dashboard-system","url":"/assurance-dashboard/systems/named-screen-reader/"},{"aliases":[],"canonicalOwner":"/assurance-dashboard/systems/critical-datacenter-protection/","claimStatus":"DESCRIBED","directAnswer":"Critical-datacenter protection system is DESCRIBED in the static K10 dataset. The state is bounded by the listed evidence and explicit non-claims.","id":"DASH-K10-012","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Critical-datacenter protection system","topic":"cyber-physical-mission-assurance","type":"assurance-dashboard-system","url":"/assurance-dashboard/systems/critical-datacenter-protection/"},{"aliases":[],"canonicalOwner":"/machine-communication/protocol-state-machine/transcripts/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"Twelve declared transcript fixtures exercise clean negotiation, downgrade, retirement, recovery, replay rejection, illegal transition, and close behavior.","id":"K11-PAGE-PROTOCOL-TRANSCRIPTS","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Protocol Transcript Fixtures","topic":"machine-communication-protocols","type":"protocol-transcript-index","url":"/machine-communication/protocol-state-machine/transcripts/"},{"aliases":[],"canonicalOwner":"/machine-communication/protocol-state-machine/transcripts/ptc-k11-001/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This synthetic fixture expects final state CLOSED after 3 declared events.","id":"PTC-K11-001","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Protocol Transcript PTC-K11-001 — Clean 1 1","topic":"machine-communication-protocols","type":"k11-record","url":"/machine-communication/protocol-state-machine/transcripts/ptc-k11-001/"},{"aliases":[],"canonicalOwner":"/machine-communication/protocol-state-machine/transcripts/ptc-k11-002/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This synthetic fixture expects final state CLOSED after 3 declared events.","id":"PTC-K11-002","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Protocol Transcript PTC-K11-002 — Compatible Fallback","topic":"machine-communication-protocols","type":"k11-record","url":"/machine-communication/protocol-state-machine/transcripts/ptc-k11-002/"},{"aliases":[],"canonicalOwner":"/machine-communication/protocol-state-machine/transcripts/ptc-k11-003/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This synthetic fixture expects final state FAILED after 2 declared events.","id":"PTC-K11-003","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Protocol Transcript PTC-K11-003 — No Common Version","topic":"machine-communication-protocols","type":"k11-record","url":"/machine-communication/protocol-state-machine/transcripts/ptc-k11-003/"},{"aliases":[],"canonicalOwner":"/machine-communication/protocol-state-machine/transcripts/ptc-k11-004/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This synthetic fixture expects final state CLOSED after 5 declared events.","id":"PTC-K11-004","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Protocol Transcript PTC-K11-004 — Unsafe Downgrade Recovery","topic":"machine-communication-protocols","type":"k11-record","url":"/machine-communication/protocol-state-machine/transcripts/ptc-k11-004/"},{"aliases":[],"canonicalOwner":"/machine-communication/protocol-state-machine/transcripts/ptc-k11-005/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This synthetic fixture expects final state CLOSED after 5 declared events.","id":"PTC-K11-005","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Protocol Transcript PTC-K11-005 — Extension Retirement","topic":"machine-communication-protocols","type":"k11-record","url":"/machine-communication/protocol-state-machine/transcripts/ptc-k11-005/"},{"aliases":[],"canonicalOwner":"/machine-communication/protocol-state-machine/transcripts/ptc-k11-006/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This synthetic fixture expects final state FAILED after 4 declared events.","id":"PTC-K11-006","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Protocol Transcript PTC-K11-006 — Critical Retirement Failure","topic":"machine-communication-protocols","type":"k11-record","url":"/machine-communication/protocol-state-machine/transcripts/ptc-k11-006/"},{"aliases":[],"canonicalOwner":"/machine-communication/protocol-state-machine/transcripts/ptc-k11-007/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This synthetic fixture expects final state CLOSED after 5 declared events.","id":"PTC-K11-007","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Protocol Transcript PTC-K11-007 — Session Recovery","topic":"machine-communication-protocols","type":"k11-record","url":"/machine-communication/protocol-state-machine/transcripts/ptc-k11-007/"},{"aliases":[],"canonicalOwner":"/machine-communication/protocol-state-machine/transcripts/ptc-k11-008/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This synthetic fixture expects final state CLOSED after 5 declared events.","id":"PTC-K11-008","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Protocol Transcript PTC-K11-008 — Degraded Session Recovery","topic":"machine-communication-protocols","type":"k11-record","url":"/machine-communication/protocol-state-machine/transcripts/ptc-k11-008/"},{"aliases":[],"canonicalOwner":"/machine-communication/protocol-state-machine/transcripts/ptc-k11-009/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This synthetic fixture expects final state CLOSED after 7 declared events.","id":"PTC-K11-009","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Protocol Transcript PTC-K11-009 — Replay During Recovery","topic":"machine-communication-protocols","type":"k11-record","url":"/machine-communication/protocol-state-machine/transcripts/ptc-k11-009/"},{"aliases":[],"canonicalOwner":"/machine-communication/protocol-state-machine/transcripts/ptc-k11-010/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This synthetic fixture expects final state FAILED after 2 declared events.","id":"PTC-K11-010","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Protocol Transcript PTC-K11-010 — Illegal Transition","topic":"machine-communication-protocols","type":"k11-record","url":"/machine-communication/protocol-state-machine/transcripts/ptc-k11-010/"},{"aliases":[],"canonicalOwner":"/machine-communication/protocol-state-machine/transcripts/ptc-k11-011/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This synthetic fixture expects final state REPLAY_REJECTED after 4 declared events.","id":"PTC-K11-011","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Protocol Transcript PTC-K11-011 — Replay State Persistence","topic":"machine-communication-protocols","type":"k11-record","url":"/machine-communication/protocol-state-machine/transcripts/ptc-k11-011/"},{"aliases":[],"canonicalOwner":"/machine-communication/protocol-state-machine/transcripts/ptc-k11-012/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This synthetic fixture expects final state CLOSED after 5 declared events.","id":"PTC-K11-012","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Protocol Transcript PTC-K11-012 — Cross Version Verification","topic":"machine-communication-protocols","type":"k11-record","url":"/machine-communication/protocol-state-machine/transcripts/ptc-k11-012/"},{"aliases":[],"canonicalOwner":"/machine-communication/history-evidence-docket/hed-k11-001/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This record exposes evidence requests, disagreement, calibration, rejection, and promotion state without verifying the event.","id":"HED-K11-001","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Evidence Docket — Formal neuron model","topic":"machine-intelligence-history","type":"k11-record","url":"/machine-communication/history-evidence-docket/hed-k11-001/"},{"aliases":[],"canonicalOwner":"/machine-communication/history-evidence-docket/hed-k11-002/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This record exposes evidence requests, disagreement, calibration, rejection, and promotion state without verifying the event.","id":"HED-K11-002","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Evidence Docket — Machine intelligence test framing","topic":"machine-intelligence-history","type":"k11-record","url":"/machine-communication/history-evidence-docket/hed-k11-002/"},{"aliases":[],"canonicalOwner":"/machine-communication/history-evidence-docket/hed-k11-003/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This record exposes evidence requests, disagreement, calibration, rejection, and promotion state without verifying the event.","id":"HED-K11-003","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Evidence Docket — Dartmouth research program","topic":"machine-intelligence-history","type":"k11-record","url":"/machine-communication/history-evidence-docket/hed-k11-003/"},{"aliases":[],"canonicalOwner":"/machine-communication/history-evidence-docket/hed-k11-004/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This record exposes evidence requests, disagreement, calibration, rejection, and promotion state without verifying the event.","id":"HED-K11-004","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Evidence Docket — Perceptron public milestone","topic":"machine-intelligence-history","type":"k11-record","url":"/machine-communication/history-evidence-docket/hed-k11-004/"},{"aliases":[],"canonicalOwner":"/machine-communication/history-evidence-docket/hed-k11-005/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This record exposes evidence requests, disagreement, calibration, rejection, and promotion state without verifying the event.","id":"HED-K11-005","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Evidence Docket — ALPAC report","topic":"machine-intelligence-history","type":"k11-record","url":"/machine-communication/history-evidence-docket/hed-k11-005/"},{"aliases":[],"canonicalOwner":"/machine-communication/history-evidence-docket/hed-k11-006/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This record exposes evidence requests, disagreement, calibration, rejection, and promotion state without verifying the event.","id":"HED-K11-006","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Evidence Docket — Perceptron critique","topic":"machine-intelligence-history","type":"k11-record","url":"/machine-communication/history-evidence-docket/hed-k11-006/"},{"aliases":[],"canonicalOwner":"/machine-communication/history-evidence-docket/hed-k11-007/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This record exposes evidence requests, disagreement, calibration, rejection, and promotion state without verifying the event.","id":"HED-K11-007","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Evidence Docket — Reverse-mode automatic differentiation","topic":"machine-intelligence-history","type":"k11-record","url":"/machine-communication/history-evidence-docket/hed-k11-007/"},{"aliases":[],"canonicalOwner":"/machine-communication/history-evidence-docket/hed-k11-008/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This record exposes evidence requests, disagreement, calibration, rejection, and promotion state without verifying the event.","id":"HED-K11-008","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Evidence Docket — Backpropagation resurgence","topic":"machine-intelligence-history","type":"k11-record","url":"/machine-communication/history-evidence-docket/hed-k11-008/"},{"aliases":[],"canonicalOwner":"/machine-communication/history-evidence-docket/hed-k11-009/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This record exposes evidence requests, disagreement, calibration, rejection, and promotion state without verifying the event.","id":"HED-K11-009","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Evidence Docket — Chess system victory","topic":"machine-intelligence-history","type":"k11-record","url":"/machine-communication/history-evidence-docket/hed-k11-009/"},{"aliases":[],"canonicalOwner":"/machine-communication/history-evidence-docket/hed-k11-010/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This record exposes evidence requests, disagreement, calibration, rejection, and promotion state without verifying the event.","id":"HED-K11-010","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Evidence Docket — GPU neural-network acceleration","topic":"machine-intelligence-history","type":"k11-record","url":"/machine-communication/history-evidence-docket/hed-k11-010/"},{"aliases":[],"canonicalOwner":"/machine-communication/history-evidence-docket/hed-k11-011/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This record exposes evidence requests, disagreement, calibration, rejection, and promotion state without verifying the event.","id":"HED-K11-011","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Evidence Docket — ImageNet deep-learning breakthrough","topic":"machine-intelligence-history","type":"k11-record","url":"/machine-communication/history-evidence-docket/hed-k11-011/"},{"aliases":[],"canonicalOwner":"/machine-communication/history-evidence-docket/hed-k11-012/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This record exposes evidence requests, disagreement, calibration, rejection, and promotion state without verifying the event.","id":"HED-K11-012","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Evidence Docket — Transformer architecture","topic":"machine-intelligence-history","type":"k11-record","url":"/machine-communication/history-evidence-docket/hed-k11-012/"},{"aliases":[],"canonicalOwner":"/machine-communication/history-evidence-docket/hed-k11-013/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This record exposes evidence requests, disagreement, calibration, rejection, and promotion state without verifying the event.","id":"HED-K11-013","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Evidence Docket — Retrieval-augmented generation","topic":"machine-intelligence-history","type":"k11-record","url":"/machine-communication/history-evidence-docket/hed-k11-013/"},{"aliases":[],"canonicalOwner":"/machine-communication/history-evidence-docket/hed-k11-014/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This record exposes evidence requests, disagreement, calibration, rejection, and promotion state without verifying the event.","id":"HED-K11-014","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Evidence Docket — Tool-using language models","topic":"machine-intelligence-history","type":"k11-record","url":"/machine-communication/history-evidence-docket/hed-k11-014/"},{"aliases":[],"canonicalOwner":"/machine-communication/history-evidence-docket/hed-k11-015/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This record exposes evidence requests, disagreement, calibration, rejection, and promotion state without verifying the event.","id":"HED-K11-015","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Evidence Docket — Inference-time reasoning and autonomous research systems","topic":"machine-intelligence-history","type":"k11-record","url":"/machine-communication/history-evidence-docket/hed-k11-015/"},{"aliases":[],"canonicalOwner":"/machine-communication/domain-observation-chain/dor-k11-01-01/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This is an offline representation and custody record; registration, DNS, TLS, hosting, ownership, and operation remain unobserved.","id":"DOR-K11-01-01","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"ᛟ.com · DOB-K11-ALPHA · DOR-K11-01-01","topic":"idn-domain-architecture","type":"k11-record","url":"/machine-communication/domain-observation-chain/dor-k11-01-01/"},{"aliases":[],"canonicalOwner":"/machine-communication/domain-observation-chain/dor-k11-01-02/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This is an offline representation and custody record; registration, DNS, TLS, hosting, ownership, and operation remain unobserved.","id":"DOR-K11-01-02","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"ᛜ.com · DOB-K11-ALPHA · DOR-K11-01-02","topic":"idn-domain-architecture","type":"k11-record","url":"/machine-communication/domain-observation-chain/dor-k11-01-02/"},{"aliases":[],"canonicalOwner":"/machine-communication/domain-observation-chain/dor-k11-01-03/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This is an offline representation and custody record; registration, DNS, TLS, hosting, ownership, and operation remain unobserved.","id":"DOR-K11-01-03","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"ᛉ.com · DOB-K11-ALPHA · DOR-K11-01-03","topic":"idn-domain-architecture","type":"k11-record","url":"/machine-communication/domain-observation-chain/dor-k11-01-03/"},{"aliases":[],"canonicalOwner":"/machine-communication/domain-observation-chain/dor-k11-01-04/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This is an offline representation and custody record; registration, DNS, TLS, hosting, ownership, and operation remain unobserved.","id":"DOR-K11-01-04","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"ᚲ.com · DOB-K11-ALPHA · DOR-K11-01-04","topic":"idn-domain-architecture","type":"k11-record","url":"/machine-communication/domain-observation-chain/dor-k11-01-04/"},{"aliases":[],"canonicalOwner":"/machine-communication/domain-observation-chain/dor-k11-01-05/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This is an offline representation and custody record; registration, DNS, TLS, hosting, ownership, and operation remain unobserved.","id":"DOR-K11-01-05","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"ᚨ.com · DOB-K11-ALPHA · DOR-K11-01-05","topic":"idn-domain-architecture","type":"k11-record","url":"/machine-communication/domain-observation-chain/dor-k11-01-05/"},{"aliases":[],"canonicalOwner":"/machine-communication/domain-observation-chain/dor-k11-01-06/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This is an offline representation and custody record; registration, DNS, TLS, hosting, ownership, and operation remain unobserved.","id":"DOR-K11-01-06","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"ᛚ.com · DOB-K11-ALPHA · DOR-K11-01-06","topic":"idn-domain-architecture","type":"k11-record","url":"/machine-communication/domain-observation-chain/dor-k11-01-06/"},{"aliases":[],"canonicalOwner":"/machine-communication/domain-observation-chain/dor-k11-01-07/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This is an offline representation and custody record; registration, DNS, TLS, hosting, ownership, and operation remain unobserved.","id":"DOR-K11-01-07","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"ᛌ.com · DOB-K11-ALPHA · DOR-K11-01-07","topic":"idn-domain-architecture","type":"k11-record","url":"/machine-communication/domain-observation-chain/dor-k11-01-07/"},{"aliases":[],"canonicalOwner":"/machine-communication/domain-observation-chain/dor-k11-01-08/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This is an offline representation and custody record; registration, DNS, TLS, hosting, ownership, and operation remain unobserved.","id":"DOR-K11-01-08","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"ᛠ.com · DOB-K11-ALPHA · DOR-K11-01-08","topic":"idn-domain-architecture","type":"k11-record","url":"/machine-communication/domain-observation-chain/dor-k11-01-08/"},{"aliases":[],"canonicalOwner":"/machine-communication/domain-observation-chain/dor-k11-01-09/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This is an offline representation and custody record; registration, DNS, TLS, hosting, ownership, and operation remain unobserved.","id":"DOR-K11-01-09","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"ᛄ.com · DOB-K11-ALPHA · DOR-K11-01-09","topic":"idn-domain-architecture","type":"k11-record","url":"/machine-communication/domain-observation-chain/dor-k11-01-09/"},{"aliases":[],"canonicalOwner":"/machine-communication/domain-observation-chain/dor-k11-02-01/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This is an offline representation and custody record; registration, DNS, TLS, hosting, ownership, and operation remain unobserved.","id":"DOR-K11-02-01","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"ᛟ.com · DOB-K11-BRAVO · DOR-K11-02-01","topic":"idn-domain-architecture","type":"k11-record","url":"/machine-communication/domain-observation-chain/dor-k11-02-01/"},{"aliases":[],"canonicalOwner":"/machine-communication/domain-observation-chain/dor-k11-02-02/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This is an offline representation and custody record; registration, DNS, TLS, hosting, ownership, and operation remain unobserved.","id":"DOR-K11-02-02","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"ᛜ.com · DOB-K11-BRAVO · DOR-K11-02-02","topic":"idn-domain-architecture","type":"k11-record","url":"/machine-communication/domain-observation-chain/dor-k11-02-02/"},{"aliases":[],"canonicalOwner":"/machine-communication/domain-observation-chain/dor-k11-02-03/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This is an offline representation and custody record; registration, DNS, TLS, hosting, ownership, and operation remain unobserved.","id":"DOR-K11-02-03","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"ᛉ.com · DOB-K11-BRAVO · DOR-K11-02-03","topic":"idn-domain-architecture","type":"k11-record","url":"/machine-communication/domain-observation-chain/dor-k11-02-03/"},{"aliases":[],"canonicalOwner":"/machine-communication/domain-observation-chain/dor-k11-02-04/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This is an offline representation and custody record; registration, DNS, TLS, hosting, ownership, and operation remain unobserved.","id":"DOR-K11-02-04","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"ᚲ.com · DOB-K11-BRAVO · DOR-K11-02-04","topic":"idn-domain-architecture","type":"k11-record","url":"/machine-communication/domain-observation-chain/dor-k11-02-04/"},{"aliases":[],"canonicalOwner":"/machine-communication/domain-observation-chain/dor-k11-02-05/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This is an offline representation and custody record; registration, DNS, TLS, hosting, ownership, and operation remain unobserved.","id":"DOR-K11-02-05","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"ᚨ.com · DOB-K11-BRAVO · DOR-K11-02-05","topic":"idn-domain-architecture","type":"k11-record","url":"/machine-communication/domain-observation-chain/dor-k11-02-05/"},{"aliases":[],"canonicalOwner":"/machine-communication/domain-observation-chain/dor-k11-02-06/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This is an offline representation and custody record; registration, DNS, TLS, hosting, ownership, and operation remain unobserved.","id":"DOR-K11-02-06","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"ᛚ.com · DOB-K11-BRAVO · DOR-K11-02-06","topic":"idn-domain-architecture","type":"k11-record","url":"/machine-communication/domain-observation-chain/dor-k11-02-06/"},{"aliases":[],"canonicalOwner":"/machine-communication/domain-observation-chain/dor-k11-02-07/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This is an offline representation and custody record; registration, DNS, TLS, hosting, ownership, and operation remain unobserved.","id":"DOR-K11-02-07","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"ᛌ.com · DOB-K11-BRAVO · DOR-K11-02-07","topic":"idn-domain-architecture","type":"k11-record","url":"/machine-communication/domain-observation-chain/dor-k11-02-07/"},{"aliases":[],"canonicalOwner":"/machine-communication/domain-observation-chain/dor-k11-02-08/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This is an offline representation and custody record; registration, DNS, TLS, hosting, ownership, and operation remain unobserved.","id":"DOR-K11-02-08","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"ᛠ.com · DOB-K11-BRAVO · DOR-K11-02-08","topic":"idn-domain-architecture","type":"k11-record","url":"/machine-communication/domain-observation-chain/dor-k11-02-08/"},{"aliases":[],"canonicalOwner":"/machine-communication/domain-observation-chain/dor-k11-02-09/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This is an offline representation and custody record; registration, DNS, TLS, hosting, ownership, and operation remain unobserved.","id":"DOR-K11-02-09","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"ᛄ.com · DOB-K11-BRAVO · DOR-K11-02-09","topic":"idn-domain-architecture","type":"k11-record","url":"/machine-communication/domain-observation-chain/dor-k11-02-09/"},{"aliases":[],"canonicalOwner":"/machine-communication/domain-observation-chain/dor-k11-03-01/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This is an offline representation and custody record; registration, DNS, TLS, hosting, ownership, and operation remain unobserved.","id":"DOR-K11-03-01","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"ᛟ.com · DOB-K11-CHARLIE · DOR-K11-03-01","topic":"idn-domain-architecture","type":"k11-record","url":"/machine-communication/domain-observation-chain/dor-k11-03-01/"},{"aliases":[],"canonicalOwner":"/machine-communication/domain-observation-chain/dor-k11-03-02/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This is an offline representation and custody record; registration, DNS, TLS, hosting, ownership, and operation remain unobserved.","id":"DOR-K11-03-02","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"ᛜ.com · DOB-K11-CHARLIE · DOR-K11-03-02","topic":"idn-domain-architecture","type":"k11-record","url":"/machine-communication/domain-observation-chain/dor-k11-03-02/"},{"aliases":[],"canonicalOwner":"/machine-communication/domain-observation-chain/dor-k11-03-03/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This is an offline representation and custody record; registration, DNS, TLS, hosting, ownership, and operation remain unobserved.","id":"DOR-K11-03-03","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"ᛉ.com · DOB-K11-CHARLIE · DOR-K11-03-03","topic":"idn-domain-architecture","type":"k11-record","url":"/machine-communication/domain-observation-chain/dor-k11-03-03/"},{"aliases":[],"canonicalOwner":"/machine-communication/domain-observation-chain/dor-k11-03-04/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This is an offline representation and custody record; registration, DNS, TLS, hosting, ownership, and operation remain unobserved.","id":"DOR-K11-03-04","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"ᚲ.com · DOB-K11-CHARLIE · DOR-K11-03-04","topic":"idn-domain-architecture","type":"k11-record","url":"/machine-communication/domain-observation-chain/dor-k11-03-04/"},{"aliases":[],"canonicalOwner":"/machine-communication/domain-observation-chain/dor-k11-03-05/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This is an offline representation and custody record; registration, DNS, TLS, hosting, ownership, and operation remain unobserved.","id":"DOR-K11-03-05","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"ᚨ.com · DOB-K11-CHARLIE · DOR-K11-03-05","topic":"idn-domain-architecture","type":"k11-record","url":"/machine-communication/domain-observation-chain/dor-k11-03-05/"},{"aliases":[],"canonicalOwner":"/machine-communication/domain-observation-chain/dor-k11-03-06/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This is an offline representation and custody record; registration, DNS, TLS, hosting, ownership, and operation remain unobserved.","id":"DOR-K11-03-06","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"ᛚ.com · DOB-K11-CHARLIE · DOR-K11-03-06","topic":"idn-domain-architecture","type":"k11-record","url":"/machine-communication/domain-observation-chain/dor-k11-03-06/"},{"aliases":[],"canonicalOwner":"/machine-communication/domain-observation-chain/dor-k11-03-07/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This is an offline representation and custody record; registration, DNS, TLS, hosting, ownership, and operation remain unobserved.","id":"DOR-K11-03-07","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"ᛌ.com · DOB-K11-CHARLIE · DOR-K11-03-07","topic":"idn-domain-architecture","type":"k11-record","url":"/machine-communication/domain-observation-chain/dor-k11-03-07/"},{"aliases":[],"canonicalOwner":"/machine-communication/domain-observation-chain/dor-k11-03-08/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This is an offline representation and custody record; registration, DNS, TLS, hosting, ownership, and operation remain unobserved.","id":"DOR-K11-03-08","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"ᛠ.com · DOB-K11-CHARLIE · DOR-K11-03-08","topic":"idn-domain-architecture","type":"k11-record","url":"/machine-communication/domain-observation-chain/dor-k11-03-08/"},{"aliases":[],"canonicalOwner":"/machine-communication/domain-observation-chain/dor-k11-03-09/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This is an offline representation and custody record; registration, DNS, TLS, hosting, ownership, and operation remain unobserved.","id":"DOR-K11-03-09","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"ᛄ.com · DOB-K11-CHARLIE · DOR-K11-03-09","topic":"idn-domain-architecture","type":"k11-record","url":"/machine-communication/domain-observation-chain/dor-k11-03-09/"},{"aliases":[],"canonicalOwner":"/facility-adaptation/decision-ledger/fdl-k11-001/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This decision is REVOKED; historical custody is preserved without publishing protected values.","id":"FDL-K11-001","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Decision FDL-K11-001 — authority.owner","topic":"critical-datacenter-assurance","type":"k11-record","url":"/facility-adaptation/decision-ledger/fdl-k11-001/"},{"aliases":[],"canonicalOwner":"/facility-adaptation/decision-ledger/fdl-k11-002/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This decision is CURRENT; historical custody is preserved without publishing protected values.","id":"FDL-K11-002","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Decision FDL-K11-002 — authority.owner","topic":"critical-datacenter-assurance","type":"k11-record","url":"/facility-adaptation/decision-ledger/fdl-k11-002/"},{"aliases":[],"canonicalOwner":"/facility-adaptation/decision-ledger/fdl-k11-003/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This decision is CURRENT; historical custody is preserved without publishing protected values.","id":"FDL-K11-003","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Decision FDL-K11-003 — mission.protectedFunctions","topic":"critical-datacenter-assurance","type":"k11-record","url":"/facility-adaptation/decision-ledger/fdl-k11-003/"},{"aliases":[],"canonicalOwner":"/facility-adaptation/decision-ledger/fdl-k11-004/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This decision is CURRENT; historical custody is preserved without publishing protected values.","id":"FDL-K11-004","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Decision FDL-K11-004 — evidence.minimumFreshnessHours","topic":"critical-datacenter-assurance","type":"k11-record","url":"/facility-adaptation/decision-ledger/fdl-k11-004/"},{"aliases":[],"canonicalOwner":"/facility-adaptation/decision-ledger/fdl-k11-005/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This decision is CURRENT; historical custody is preserved without publishing protected values.","id":"FDL-K11-005","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Decision FDL-K11-005 — release.publicProjection","topic":"critical-datacenter-assurance","type":"k11-record","url":"/facility-adaptation/decision-ledger/fdl-k11-005/"},{"aliases":[],"canonicalOwner":"/facility-adaptation/decision-ledger/fdl-k11-006/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This decision is CURRENT; historical custody is preserved without publishing protected values.","id":"FDL-K11-006","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Decision FDL-K11-006 — merge.conflictPolicy","topic":"critical-datacenter-assurance","type":"k11-record","url":"/facility-adaptation/decision-ledger/fdl-k11-006/"},{"aliases":[],"canonicalOwner":"/assurance-case/mission-threads/authority-thread/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This thread is DEGRADED and includes no protected configuration.","id":"MTH-K11-001","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Mission Thread — Authority-to-action thread","topic":"critical-datacenter-assurance","type":"k11-record","url":"/assurance-case/mission-threads/authority-thread/"},{"aliases":[],"canonicalOwner":"/assurance-case/mission-threads/power-cooling-thread/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This thread is DEGRADED and includes no protected configuration.","id":"MTH-K11-002","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Mission Thread — Power and cooling continuity thread","topic":"critical-datacenter-assurance","type":"k11-record","url":"/assurance-case/mission-threads/power-cooling-thread/"},{"aliases":[],"canonicalOwner":"/assurance-case/mission-threads/identity-management-thread/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This thread is DEGRADED and includes no protected configuration.","id":"MTH-K11-003","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Mission Thread — Identity and management containment thread","topic":"critical-datacenter-assurance","type":"k11-record","url":"/assurance-case/mission-threads/identity-management-thread/"},{"aliases":[],"canonicalOwner":"/assurance-case/mission-threads/supply-recovery-thread/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This thread is DEGRADED and includes no protected configuration.","id":"MTH-K11-004","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Mission Thread — Supply-chain and recovery thread","topic":"critical-datacenter-assurance","type":"k11-record","url":"/assurance-case/mission-threads/supply-recovery-thread/"},{"aliases":[],"canonicalOwner":"/assurance-case/mission-threads/protocol-currentness-thread/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This thread is DEGRADED and includes no protected configuration.","id":"MTH-K11-005","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Mission Thread — Protocol and currentness thread","topic":"critical-datacenter-assurance","type":"k11-record","url":"/assurance-case/mission-threads/protocol-currentness-thread/"},{"aliases":[],"canonicalOwner":"/assurance-case/mission-threads/mission-continuity-thread/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This thread is DEGRADED and includes no protected configuration.","id":"MTH-K11-006","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Mission Thread — Cross-domain mission continuity thread","topic":"critical-datacenter-assurance","type":"k11-record","url":"/assurance-case/mission-threads/mission-continuity-thread/"},{"aliases":[],"canonicalOwner":"/cryptographic-agility/component-workbooks/protocol/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This reference workbook is TESTED with 82% declared evidence completeness.","id":"CCW-K11-001","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Crypto Workbook — Protocol negotiation and canonicalization","topic":"cryptographic-provenance","type":"k11-record","url":"/cryptographic-agility/component-workbooks/protocol/"},{"aliases":[],"canonicalOwner":"/cryptographic-agility/component-workbooks/certificate/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This reference workbook is DEGRADED with 61% declared evidence completeness.","id":"CCW-K11-002","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Crypto Workbook — Certificate and trust-chain transition","topic":"cryptographic-provenance","type":"k11-record","url":"/cryptographic-agility/component-workbooks/certificate/"},{"aliases":[],"canonicalOwner":"/cryptographic-agility/component-workbooks/firmware/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This reference workbook is DEGRADED with 58% declared evidence completeness.","id":"CCW-K11-003","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Crypto Workbook — Firmware signing transition","topic":"cryptographic-provenance","type":"k11-record","url":"/cryptographic-agility/component-workbooks/firmware/"},{"aliases":[],"canonicalOwner":"/cryptographic-agility/component-workbooks/hardware/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This reference workbook is UNAVAILABLE with 44% declared evidence completeness.","id":"CCW-K11-004","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Crypto Workbook — Hardware root and secure-element transition","topic":"cryptographic-provenance","type":"k11-record","url":"/cryptographic-agility/component-workbooks/hardware/"},{"aliases":[],"canonicalOwner":"/cryptographic-agility/component-workbooks/supplier/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This reference workbook is UNAVAILABLE with 39% declared evidence completeness.","id":"CCW-K11-005","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Crypto Workbook — Supplier cryptographic capability transition","topic":"cryptographic-provenance","type":"k11-record","url":"/cryptographic-agility/component-workbooks/supplier/"},{"aliases":[],"canonicalOwner":"/cryptographic-agility/component-workbooks/archive/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This reference workbook is DEGRADED with 72% declared evidence completeness.","id":"CCW-K11-006","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Crypto Workbook — Archive verification and re-signing","topic":"cryptographic-provenance","type":"k11-record","url":"/cryptographic-agility/component-workbooks/archive/"},{"aliases":[],"canonicalOwner":"/cryptographic-agility/component-workbooks/identity/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This reference workbook is TESTED with 76% declared evidence completeness.","id":"CCW-K11-007","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Crypto Workbook — Workload identity transition","topic":"cryptographic-provenance","type":"k11-record","url":"/cryptographic-agility/component-workbooks/identity/"},{"aliases":[],"canonicalOwner":"/cryptographic-agility/component-workbooks/signing-service/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This reference workbook is DEGRADED with 69% declared evidence completeness.","id":"CCW-K11-008","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Crypto Workbook — Evidence signing-service transition","topic":"cryptographic-provenance","type":"k11-record","url":"/cryptographic-agility/component-workbooks/signing-service/"},{"aliases":[],"canonicalOwner":"/procurement/protest-corrective-action/acf-k11-001/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This reference case preserves process evidence and makes no award decision.","id":"ACF-K11-001","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Acquisition Case ACF-K11-001","topic":"procurement-readiness","type":"k11-record","url":"/procurement/protest-corrective-action/acf-k11-001/"},{"aliases":[],"canonicalOwner":"/procurement/protest-corrective-action/acf-k11-002/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This reference case preserves process evidence and makes no award decision.","id":"ACF-K11-002","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Acquisition Case ACF-K11-002","topic":"procurement-readiness","type":"k11-record","url":"/procurement/protest-corrective-action/acf-k11-002/"},{"aliases":[],"canonicalOwner":"/procurement/protest-corrective-action/acf-k11-003/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This reference case preserves process evidence and makes no award decision.","id":"ACF-K11-003","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Acquisition Case ACF-K11-003","topic":"procurement-readiness","type":"k11-record","url":"/procurement/protest-corrective-action/acf-k11-003/"},{"aliases":[],"canonicalOwner":"/procurement/protest-corrective-action/acf-k11-004/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This reference case preserves process evidence and makes no award decision.","id":"ACF-K11-004","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Acquisition Case ACF-K11-004","topic":"procurement-readiness","type":"k11-record","url":"/procurement/protest-corrective-action/acf-k11-004/"},{"aliases":[],"canonicalOwner":"/procurement/protest-corrective-action/acf-k11-005/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This reference case preserves process evidence and makes no award decision.","id":"ACF-K11-005","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Acquisition Case ACF-K11-005","topic":"procurement-readiness","type":"k11-record","url":"/procurement/protest-corrective-action/acf-k11-005/"},{"aliases":[],"canonicalOwner":"/procurement/protest-corrective-action/acf-k11-006/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This reference case preserves process evidence and makes no award decision.","id":"ACF-K11-006","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Acquisition Case ACF-K11-006","topic":"procurement-readiness","type":"k11-record","url":"/procurement/protest-corrective-action/acf-k11-006/"},{"aliases":[],"canonicalOwner":"/continuous-assurance/scheduler-custody/schain-k11-001/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This chain contains 4 offline results and no public runtime.","id":"SCHAIN-K11-001","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Scheduler Chain SCHAIN-K11-001 — SCH-K09-001","topic":"continuous-assurance","type":"k11-record","url":"/continuous-assurance/scheduler-custody/schain-k11-001/"},{"aliases":[],"canonicalOwner":"/continuous-assurance/scheduler-custody/schain-k11-002/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This chain contains 4 offline results and no public runtime.","id":"SCHAIN-K11-002","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Scheduler Chain SCHAIN-K11-002 — SCH-K09-002","topic":"continuous-assurance","type":"k11-record","url":"/continuous-assurance/scheduler-custody/schain-k11-002/"},{"aliases":[],"canonicalOwner":"/continuous-assurance/scheduler-custody/schain-k11-003/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This chain contains 4 offline results and no public runtime.","id":"SCHAIN-K11-003","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Scheduler Chain SCHAIN-K11-003 — SCH-K09-003","topic":"continuous-assurance","type":"k11-record","url":"/continuous-assurance/scheduler-custody/schain-k11-003/"},{"aliases":[],"canonicalOwner":"/continuous-assurance/scheduler-custody/schain-k11-004/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This chain contains 4 offline results and no public runtime.","id":"SCHAIN-K11-004","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Scheduler Chain SCHAIN-K11-004 — SCH-K09-004","topic":"continuous-assurance","type":"k11-record","url":"/continuous-assurance/scheduler-custody/schain-k11-004/"},{"aliases":[],"canonicalOwner":"/continuous-assurance/scheduler-custody/schain-k11-005/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This chain contains 4 offline results and no public runtime.","id":"SCHAIN-K11-005","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Scheduler Chain SCHAIN-K11-005 — SCH-K09-005","topic":"continuous-assurance","type":"k11-record","url":"/continuous-assurance/scheduler-custody/schain-k11-005/"},{"aliases":[],"canonicalOwner":"/continuous-assurance/scheduler-custody/schain-k11-006/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This chain contains 4 offline results and no public runtime.","id":"SCHAIN-K11-006","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Scheduler Chain SCHAIN-K11-006 — SCH-K09-006","topic":"continuous-assurance","type":"k11-record","url":"/continuous-assurance/scheduler-custody/schain-k11-006/"},{"aliases":[],"canonicalOwner":"/evidence/multi-stage-release/rpr-k11-01-01/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This PUBLIC projection names its release authority and records removed field paths without publishing removed values.","id":"RPR-K11-01-01","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Release Projection — facility-workbook · PUBLIC · RPR-K11-01-01","topic":"evidence-provenance","type":"k11-record","url":"/evidence/multi-stage-release/rpr-k11-01-01/"},{"aliases":[],"canonicalOwner":"/evidence/multi-stage-release/rpr-k11-01-02/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This PROTECTED projection names its release authority and records removed field paths without publishing removed values.","id":"RPR-K11-01-02","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Release Projection — facility-workbook · PROTECTED · RPR-K11-01-02","topic":"evidence-provenance","type":"k11-record","url":"/evidence/multi-stage-release/rpr-k11-01-02/"},{"aliases":[],"canonicalOwner":"/evidence/multi-stage-release/rpr-k11-01-03/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This PRIVILEGED projection names its release authority and records removed field paths without publishing removed values.","id":"RPR-K11-01-03","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Release Projection — facility-workbook · PRIVILEGED · RPR-K11-01-03","topic":"evidence-provenance","type":"k11-record","url":"/evidence/multi-stage-release/rpr-k11-01-03/"},{"aliases":[],"canonicalOwner":"/evidence/multi-stage-release/rpr-k11-02-01/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This PUBLIC projection names its release authority and records removed field paths without publishing removed values.","id":"RPR-K11-02-01","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Release Projection — domain-observation · PUBLIC · RPR-K11-02-01","topic":"evidence-provenance","type":"k11-record","url":"/evidence/multi-stage-release/rpr-k11-02-01/"},{"aliases":[],"canonicalOwner":"/evidence/multi-stage-release/rpr-k11-02-02/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This PROTECTED projection names its release authority and records removed field paths without publishing removed values.","id":"RPR-K11-02-02","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Release Projection — domain-observation · PROTECTED · RPR-K11-02-02","topic":"evidence-provenance","type":"k11-record","url":"/evidence/multi-stage-release/rpr-k11-02-02/"},{"aliases":[],"canonicalOwner":"/evidence/multi-stage-release/rpr-k11-02-03/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This PRIVILEGED projection names its release authority and records removed field paths without publishing removed values.","id":"RPR-K11-02-03","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Release Projection — domain-observation · PRIVILEGED · RPR-K11-02-03","topic":"evidence-provenance","type":"k11-record","url":"/evidence/multi-stage-release/rpr-k11-02-03/"},{"aliases":[],"canonicalOwner":"/evidence/multi-stage-release/rpr-k11-03-01/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This PUBLIC projection names its release authority and records removed field paths without publishing removed values.","id":"RPR-K11-03-01","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Release Projection — scheduler-result · PUBLIC · RPR-K11-03-01","topic":"evidence-provenance","type":"k11-record","url":"/evidence/multi-stage-release/rpr-k11-03-01/"},{"aliases":[],"canonicalOwner":"/evidence/multi-stage-release/rpr-k11-03-02/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This PROTECTED projection names its release authority and records removed field paths without publishing removed values.","id":"RPR-K11-03-02","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Release Projection — scheduler-result · PROTECTED · RPR-K11-03-02","topic":"evidence-provenance","type":"k11-record","url":"/evidence/multi-stage-release/rpr-k11-03-02/"},{"aliases":[],"canonicalOwner":"/evidence/multi-stage-release/rpr-k11-03-03/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This PRIVILEGED projection names its release authority and records removed field paths without publishing removed values.","id":"RPR-K11-03-03","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Release Projection — scheduler-result · PRIVILEGED · RPR-K11-03-03","topic":"evidence-provenance","type":"k11-record","url":"/evidence/multi-stage-release/rpr-k11-03-03/"},{"aliases":[],"canonicalOwner":"/evidence/multi-stage-release/rpr-k11-04-01/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This PUBLIC projection names its release authority and records removed field paths without publishing removed values.","id":"RPR-K11-04-01","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Release Projection — acquisition-case · PUBLIC · RPR-K11-04-01","topic":"evidence-provenance","type":"k11-record","url":"/evidence/multi-stage-release/rpr-k11-04-01/"},{"aliases":[],"canonicalOwner":"/evidence/multi-stage-release/rpr-k11-04-02/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This PROTECTED projection names its release authority and records removed field paths without publishing removed values.","id":"RPR-K11-04-02","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Release Projection — acquisition-case · PROTECTED · RPR-K11-04-02","topic":"evidence-provenance","type":"k11-record","url":"/evidence/multi-stage-release/rpr-k11-04-02/"},{"aliases":[],"canonicalOwner":"/evidence/multi-stage-release/rpr-k11-04-03/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This PRIVILEGED projection names its release authority and records removed field paths without publishing removed values.","id":"RPR-K11-04-03","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Release Projection — acquisition-case · PRIVILEGED · RPR-K11-04-03","topic":"evidence-provenance","type":"k11-record","url":"/evidence/multi-stage-release/rpr-k11-04-03/"},{"aliases":[],"canonicalOwner":"/assurance-dashboard/trends/protocol/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This release-time comparison currently records TESTED and explicitly performs no live monitoring.","id":"ATR-K11-001","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Assurance Trend — Protocol conformance and state machine","topic":"critical-datacenter-assurance","type":"k11-record","url":"/assurance-dashboard/trends/protocol/"},{"aliases":[],"canonicalOwner":"/assurance-dashboard/trends/history/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This release-time comparison currently records IMPLEMENTED and explicitly performs no live monitoring.","id":"ATR-K11-002","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Assurance Trend — History evidence review","topic":"critical-datacenter-assurance","type":"k11-record","url":"/assurance-dashboard/trends/history/"},{"aliases":[],"canonicalOwner":"/assurance-dashboard/trends/idn/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This release-time comparison currently records TESTED and explicitly performs no live monitoring.","id":"ATR-K11-003","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Assurance Trend — Offline IDN observation","topic":"critical-datacenter-assurance","type":"k11-record","url":"/assurance-dashboard/trends/idn/"},{"aliases":[],"canonicalOwner":"/assurance-dashboard/trends/workbook/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This release-time comparison currently records TESTED and explicitly performs no live monitoring.","id":"ATR-K11-004","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Assurance Trend — Facility workbook tooling","topic":"critical-datacenter-assurance","type":"k11-record","url":"/assurance-dashboard/trends/workbook/"},{"aliases":[],"canonicalOwner":"/assurance-dashboard/trends/assurance/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This release-time comparison currently records DEGRADED and explicitly performs no live monitoring.","id":"ATR-K11-005","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Assurance Trend — Common-cause and mission-thread analysis","topic":"critical-datacenter-assurance","type":"k11-record","url":"/assurance-dashboard/trends/assurance/"},{"aliases":[],"canonicalOwner":"/assurance-dashboard/trends/crypto/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This release-time comparison currently records DEGRADED and explicitly performs no live monitoring.","id":"ATR-K11-006","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Assurance Trend — Cryptographic transition","topic":"critical-datacenter-assurance","type":"k11-record","url":"/assurance-dashboard/trends/crypto/"},{"aliases":[],"canonicalOwner":"/assurance-dashboard/trends/acquisition/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This release-time comparison currently records IMPLEMENTED and explicitly performs no live monitoring.","id":"ATR-K11-007","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Assurance Trend — Acquisition evaluation records","topic":"critical-datacenter-assurance","type":"k11-record","url":"/assurance-dashboard/trends/acquisition/"},{"aliases":[],"canonicalOwner":"/assurance-dashboard/trends/scheduler/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This release-time comparison currently records TESTED and explicitly performs no live monitoring.","id":"ATR-K11-008","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Assurance Trend — Offline scheduler custody","topic":"critical-datacenter-assurance","type":"k11-record","url":"/assurance-dashboard/trends/scheduler/"},{"aliases":[],"canonicalOwner":"/assurance-dashboard/trends/release/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This release-time comparison currently records TESTED and explicitly performs no live monitoring.","id":"ATR-K11-009","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Assurance Trend — Controlled release and redaction","topic":"critical-datacenter-assurance","type":"k11-record","url":"/assurance-dashboard/trends/release/"},{"aliases":[],"canonicalOwner":"/assurance-dashboard/trends/domain-live/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This release-time comparison currently records UNKNOWN and explicitly performs no live monitoring.","id":"ATR-K11-010","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Assurance Trend — Live domain operation","topic":"critical-datacenter-assurance","type":"k11-record","url":"/assurance-dashboard/trends/domain-live/"},{"aliases":[],"canonicalOwner":"/assurance-dashboard/trends/host-live/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This release-time comparison currently records UNKNOWN and explicitly performs no live monitoring.","id":"ATR-K11-011","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Assurance Trend — Live host verification","topic":"critical-datacenter-assurance","type":"k11-record","url":"/assurance-dashboard/trends/host-live/"},{"aliases":[],"canonicalOwner":"/assurance-dashboard/trends/screen-reader/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This release-time comparison currently records UNAVAILABLE and explicitly performs no live monitoring.","id":"ATR-K11-012","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Assurance Trend — Independent named screen-reader testing","topic":"critical-datacenter-assurance","type":"k11-record","url":"/assurance-dashboard/trends/screen-reader/"},{"aliases":[],"canonicalOwner":"/assurance-dashboard/trends/datacenter/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This release-time comparison currently records DESCRIBED and explicitly performs no live monitoring.","id":"ATR-K11-013","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Assurance Trend — Critical-datacenter protection system","topic":"critical-datacenter-assurance","type":"k11-record","url":"/assurance-dashboard/trends/datacenter/"},{"aliases":[],"canonicalOwner":"/assurance-dashboard/trends/facility/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This release-time comparison currently records UNKNOWN and explicitly performs no live monitoring.","id":"ATR-K11-014","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Assurance Trend — Real facility evidence bundle","topic":"critical-datacenter-assurance","type":"k11-record","url":"/assurance-dashboard/trends/facility/"},{"aliases":[],"canonicalOwner":"/assurance-dashboard/trends/deployment/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This release-time comparison currently records UNKNOWN and explicitly performs no live monitoring.","id":"ATR-K11-015","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Assurance Trend — Public site deployment","topic":"critical-datacenter-assurance","type":"k11-record","url":"/assurance-dashboard/trends/deployment/"},{"aliases":[],"canonicalOwner":"/machine-communication/differential-protocol-lab/lineage/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"Thirty-four receipts preserve inherited fixture identity and replay state without asserting protocol security, performance, or deployment.","id":"K12-PAGE-PROTOCOL-LINEAGE","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Protocol Lineage Receipts","topic":"machine-communication-protocols","type":"protocol-lineage-index","url":"/machine-communication/differential-protocol-lab/lineage/"},{"aliases":[],"canonicalOwner":"/machine-communication/differential-protocol-lab/lineage/plr-k12-k09-001/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This receipt preserves K09 fixture identity and replay state without establishing protocol security or deployment.","id":"PLR-K12-K09-001","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Protocol Lineage — CASE-K09-001","topic":"machine-communication-protocols","type":"k12-record","url":"/machine-communication/differential-protocol-lab/lineage/plr-k12-k09-001/"},{"aliases":[],"canonicalOwner":"/machine-communication/differential-protocol-lab/lineage/plr-k12-k09-002/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This receipt preserves K09 fixture identity and replay state without establishing protocol security or deployment.","id":"PLR-K12-K09-002","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Protocol Lineage — CASE-K09-002","topic":"machine-communication-protocols","type":"k12-record","url":"/machine-communication/differential-protocol-lab/lineage/plr-k12-k09-002/"},{"aliases":[],"canonicalOwner":"/machine-communication/differential-protocol-lab/lineage/plr-k12-k09-003/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This receipt preserves K09 fixture identity and replay state without establishing protocol security or deployment.","id":"PLR-K12-K09-003","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Protocol Lineage — CASE-K09-003","topic":"machine-communication-protocols","type":"k12-record","url":"/machine-communication/differential-protocol-lab/lineage/plr-k12-k09-003/"},{"aliases":[],"canonicalOwner":"/machine-communication/differential-protocol-lab/lineage/plr-k12-k09-004/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This receipt preserves K09 fixture identity and replay state without establishing protocol security or deployment.","id":"PLR-K12-K09-004","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Protocol Lineage — CASE-K09-004","topic":"machine-communication-protocols","type":"k12-record","url":"/machine-communication/differential-protocol-lab/lineage/plr-k12-k09-004/"},{"aliases":[],"canonicalOwner":"/machine-communication/differential-protocol-lab/lineage/plr-k12-k09-005/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This receipt preserves K09 fixture identity and replay state without establishing protocol security or deployment.","id":"PLR-K12-K09-005","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Protocol Lineage — CASE-K09-005","topic":"machine-communication-protocols","type":"k12-record","url":"/machine-communication/differential-protocol-lab/lineage/plr-k12-k09-005/"},{"aliases":[],"canonicalOwner":"/machine-communication/differential-protocol-lab/lineage/plr-k12-k09-006/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This receipt preserves K09 fixture identity and replay state without establishing protocol security or deployment.","id":"PLR-K12-K09-006","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Protocol Lineage — CASE-K09-006","topic":"machine-communication-protocols","type":"k12-record","url":"/machine-communication/differential-protocol-lab/lineage/plr-k12-k09-006/"},{"aliases":[],"canonicalOwner":"/machine-communication/differential-protocol-lab/lineage/plr-k12-k09-007/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This receipt preserves K09 fixture identity and replay state without establishing protocol security or deployment.","id":"PLR-K12-K09-007","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Protocol Lineage — CASE-K09-007","topic":"machine-communication-protocols","type":"k12-record","url":"/machine-communication/differential-protocol-lab/lineage/plr-k12-k09-007/"},{"aliases":[],"canonicalOwner":"/machine-communication/differential-protocol-lab/lineage/plr-k12-k09-008/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This receipt preserves K09 fixture identity and replay state without establishing protocol security or deployment.","id":"PLR-K12-K09-008","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Protocol Lineage — CASE-K09-008","topic":"machine-communication-protocols","type":"k12-record","url":"/machine-communication/differential-protocol-lab/lineage/plr-k12-k09-008/"},{"aliases":[],"canonicalOwner":"/machine-communication/differential-protocol-lab/lineage/plr-k12-k09-009/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This receipt preserves K09 fixture identity and replay state without establishing protocol security or deployment.","id":"PLR-K12-K09-009","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Protocol Lineage — CASE-K09-009","topic":"machine-communication-protocols","type":"k12-record","url":"/machine-communication/differential-protocol-lab/lineage/plr-k12-k09-009/"},{"aliases":[],"canonicalOwner":"/machine-communication/differential-protocol-lab/lineage/plr-k12-k09-010/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This receipt preserves K09 fixture identity and replay state without establishing protocol security or deployment.","id":"PLR-K12-K09-010","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Protocol Lineage — CASE-K09-010","topic":"machine-communication-protocols","type":"k12-record","url":"/machine-communication/differential-protocol-lab/lineage/plr-k12-k09-010/"},{"aliases":[],"canonicalOwner":"/machine-communication/differential-protocol-lab/lineage/plr-k12-k09-011/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This receipt preserves K09 fixture identity and replay state without establishing protocol security or deployment.","id":"PLR-K12-K09-011","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Protocol Lineage — CASE-K09-011","topic":"machine-communication-protocols","type":"k12-record","url":"/machine-communication/differential-protocol-lab/lineage/plr-k12-k09-011/"},{"aliases":[],"canonicalOwner":"/machine-communication/differential-protocol-lab/lineage/plr-k12-k09-012/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This receipt preserves K09 fixture identity and replay state without establishing protocol security or deployment.","id":"PLR-K12-K09-012","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Protocol Lineage — CASE-K09-012","topic":"machine-communication-protocols","type":"k12-record","url":"/machine-communication/differential-protocol-lab/lineage/plr-k12-k09-012/"},{"aliases":[],"canonicalOwner":"/machine-communication/differential-protocol-lab/lineage/plr-k12-k10-001/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This receipt preserves K10 fixture identity and replay state without establishing protocol security or deployment.","id":"PLR-K12-K10-001","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Protocol Lineage — NEGOTIATE-K10-001","topic":"machine-communication-protocols","type":"k12-record","url":"/machine-communication/differential-protocol-lab/lineage/plr-k12-k10-001/"},{"aliases":[],"canonicalOwner":"/machine-communication/differential-protocol-lab/lineage/plr-k12-k10-002/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This receipt preserves K10 fixture identity and replay state without establishing protocol security or deployment.","id":"PLR-K12-K10-002","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Protocol Lineage — NEGOTIATE-K10-002","topic":"machine-communication-protocols","type":"k12-record","url":"/machine-communication/differential-protocol-lab/lineage/plr-k12-k10-002/"},{"aliases":[],"canonicalOwner":"/machine-communication/differential-protocol-lab/lineage/plr-k12-k10-003/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This receipt preserves K10 fixture identity and replay state without establishing protocol security or deployment.","id":"PLR-K12-K10-003","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Protocol Lineage — NEGOTIATE-K10-003","topic":"machine-communication-protocols","type":"k12-record","url":"/machine-communication/differential-protocol-lab/lineage/plr-k12-k10-003/"},{"aliases":[],"canonicalOwner":"/machine-communication/differential-protocol-lab/lineage/plr-k12-k10-004/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This receipt preserves K10 fixture identity and replay state without establishing protocol security or deployment.","id":"PLR-K12-K10-004","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Protocol Lineage — NEGOTIATE-K10-004","topic":"machine-communication-protocols","type":"k12-record","url":"/machine-communication/differential-protocol-lab/lineage/plr-k12-k10-004/"},{"aliases":[],"canonicalOwner":"/machine-communication/differential-protocol-lab/lineage/plr-k12-k10-005/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This receipt preserves K10 fixture identity and replay state without establishing protocol security or deployment.","id":"PLR-K12-K10-005","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Protocol Lineage — NEGOTIATE-K10-005","topic":"machine-communication-protocols","type":"k12-record","url":"/machine-communication/differential-protocol-lab/lineage/plr-k12-k10-005/"},{"aliases":[],"canonicalOwner":"/machine-communication/differential-protocol-lab/lineage/plr-k12-k10-006/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This receipt preserves K10 fixture identity and replay state without establishing protocol security or deployment.","id":"PLR-K12-K10-006","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Protocol Lineage — NEGOTIATE-K10-006","topic":"machine-communication-protocols","type":"k12-record","url":"/machine-communication/differential-protocol-lab/lineage/plr-k12-k10-006/"},{"aliases":[],"canonicalOwner":"/machine-communication/differential-protocol-lab/lineage/plr-k12-k10-007/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This receipt preserves K10 fixture identity and replay state without establishing protocol security or deployment.","id":"PLR-K12-K10-007","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Protocol Lineage — NEGOTIATE-K10-007","topic":"machine-communication-protocols","type":"k12-record","url":"/machine-communication/differential-protocol-lab/lineage/plr-k12-k10-007/"},{"aliases":[],"canonicalOwner":"/machine-communication/differential-protocol-lab/lineage/plr-k12-k10-008/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This receipt preserves K10 fixture identity and replay state without establishing protocol security or deployment.","id":"PLR-K12-K10-008","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Protocol Lineage — NEGOTIATE-K10-008","topic":"machine-communication-protocols","type":"k12-record","url":"/machine-communication/differential-protocol-lab/lineage/plr-k12-k10-008/"},{"aliases":[],"canonicalOwner":"/machine-communication/differential-protocol-lab/lineage/plr-k12-k10-009/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This receipt preserves K10 fixture identity and replay state without establishing protocol security or deployment.","id":"PLR-K12-K10-009","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Protocol Lineage — NEGOTIATE-K10-009","topic":"machine-communication-protocols","type":"k12-record","url":"/machine-communication/differential-protocol-lab/lineage/plr-k12-k10-009/"},{"aliases":[],"canonicalOwner":"/machine-communication/differential-protocol-lab/lineage/plr-k12-k10-010/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This receipt preserves K10 fixture identity and replay state without establishing protocol security or deployment.","id":"PLR-K12-K10-010","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Protocol Lineage — NEGOTIATE-K10-010","topic":"machine-communication-protocols","type":"k12-record","url":"/machine-communication/differential-protocol-lab/lineage/plr-k12-k10-010/"},{"aliases":[],"canonicalOwner":"/machine-communication/differential-protocol-lab/lineage/plr-k12-k11-001/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This receipt preserves K11 fixture identity and replay state without establishing protocol security or deployment.","id":"PLR-K12-K11-001","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Protocol Lineage — PTC-K11-001","topic":"machine-communication-protocols","type":"k12-record","url":"/machine-communication/differential-protocol-lab/lineage/plr-k12-k11-001/"},{"aliases":[],"canonicalOwner":"/machine-communication/differential-protocol-lab/lineage/plr-k12-k11-002/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This receipt preserves K11 fixture identity and replay state without establishing protocol security or deployment.","id":"PLR-K12-K11-002","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Protocol Lineage — PTC-K11-002","topic":"machine-communication-protocols","type":"k12-record","url":"/machine-communication/differential-protocol-lab/lineage/plr-k12-k11-002/"},{"aliases":[],"canonicalOwner":"/machine-communication/differential-protocol-lab/lineage/plr-k12-k11-003/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This receipt preserves K11 fixture identity and replay state without establishing protocol security or deployment.","id":"PLR-K12-K11-003","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Protocol Lineage — PTC-K11-003","topic":"machine-communication-protocols","type":"k12-record","url":"/machine-communication/differential-protocol-lab/lineage/plr-k12-k11-003/"},{"aliases":[],"canonicalOwner":"/machine-communication/differential-protocol-lab/lineage/plr-k12-k11-004/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This receipt preserves K11 fixture identity and replay state without establishing protocol security or deployment.","id":"PLR-K12-K11-004","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Protocol Lineage — PTC-K11-004","topic":"machine-communication-protocols","type":"k12-record","url":"/machine-communication/differential-protocol-lab/lineage/plr-k12-k11-004/"},{"aliases":[],"canonicalOwner":"/machine-communication/differential-protocol-lab/lineage/plr-k12-k11-005/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This receipt preserves K11 fixture identity and replay state without establishing protocol security or deployment.","id":"PLR-K12-K11-005","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Protocol Lineage — PTC-K11-005","topic":"machine-communication-protocols","type":"k12-record","url":"/machine-communication/differential-protocol-lab/lineage/plr-k12-k11-005/"},{"aliases":[],"canonicalOwner":"/machine-communication/differential-protocol-lab/lineage/plr-k12-k11-006/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This receipt preserves K11 fixture identity and replay state without establishing protocol security or deployment.","id":"PLR-K12-K11-006","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Protocol Lineage — PTC-K11-006","topic":"machine-communication-protocols","type":"k12-record","url":"/machine-communication/differential-protocol-lab/lineage/plr-k12-k11-006/"},{"aliases":[],"canonicalOwner":"/machine-communication/differential-protocol-lab/lineage/plr-k12-k11-007/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This receipt preserves K11 fixture identity and replay state without establishing protocol security or deployment.","id":"PLR-K12-K11-007","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Protocol Lineage — PTC-K11-007","topic":"machine-communication-protocols","type":"k12-record","url":"/machine-communication/differential-protocol-lab/lineage/plr-k12-k11-007/"},{"aliases":[],"canonicalOwner":"/machine-communication/differential-protocol-lab/lineage/plr-k12-k11-008/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This receipt preserves K11 fixture identity and replay state without establishing protocol security or deployment.","id":"PLR-K12-K11-008","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Protocol Lineage — PTC-K11-008","topic":"machine-communication-protocols","type":"k12-record","url":"/machine-communication/differential-protocol-lab/lineage/plr-k12-k11-008/"},{"aliases":[],"canonicalOwner":"/machine-communication/differential-protocol-lab/lineage/plr-k12-k11-009/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This receipt preserves K11 fixture identity and replay state without establishing protocol security or deployment.","id":"PLR-K12-K11-009","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Protocol Lineage — PTC-K11-009","topic":"machine-communication-protocols","type":"k12-record","url":"/machine-communication/differential-protocol-lab/lineage/plr-k12-k11-009/"},{"aliases":[],"canonicalOwner":"/machine-communication/differential-protocol-lab/lineage/plr-k12-k11-010/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This receipt preserves K11 fixture identity and replay state without establishing protocol security or deployment.","id":"PLR-K12-K11-010","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Protocol Lineage — PTC-K11-010","topic":"machine-communication-protocols","type":"k12-record","url":"/machine-communication/differential-protocol-lab/lineage/plr-k12-k11-010/"},{"aliases":[],"canonicalOwner":"/machine-communication/differential-protocol-lab/lineage/plr-k12-k11-011/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This receipt preserves K11 fixture identity and replay state without establishing protocol security or deployment.","id":"PLR-K12-K11-011","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Protocol Lineage — PTC-K11-011","topic":"machine-communication-protocols","type":"k12-record","url":"/machine-communication/differential-protocol-lab/lineage/plr-k12-k11-011/"},{"aliases":[],"canonicalOwner":"/machine-communication/differential-protocol-lab/lineage/plr-k12-k11-012/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This receipt preserves K11 fixture identity and replay state without establishing protocol security or deployment.","id":"PLR-K12-K11-012","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Protocol Lineage — PTC-K11-012","topic":"machine-communication-protocols","type":"k12-record","url":"/machine-communication/differential-protocol-lab/lineage/plr-k12-k11-012/"},{"aliases":[],"canonicalOwner":"/machine-communication/history-docket-import/hir-k12-001/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This receipt records REVIEW_REQUIRED and NO_AUTOMATIC_PROMOTION; it does not verify or promote the event.","id":"HIR-K12-001","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Historical Import Receipt — HIST-K09-001","topic":"machine-intelligence-history","type":"k12-record","url":"/machine-communication/history-docket-import/hir-k12-001/"},{"aliases":[],"canonicalOwner":"/machine-communication/history-docket-import/hir-k12-002/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This receipt records REVIEW_REQUIRED and NO_AUTOMATIC_PROMOTION; it does not verify or promote the event.","id":"HIR-K12-002","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Historical Import Receipt — HIST-K09-002","topic":"machine-intelligence-history","type":"k12-record","url":"/machine-communication/history-docket-import/hir-k12-002/"},{"aliases":[],"canonicalOwner":"/machine-communication/history-docket-import/hir-k12-003/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This receipt records REVIEW_REQUIRED and NO_AUTOMATIC_PROMOTION; it does not verify or promote the event.","id":"HIR-K12-003","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Historical Import Receipt — HIST-K09-003","topic":"machine-intelligence-history","type":"k12-record","url":"/machine-communication/history-docket-import/hir-k12-003/"},{"aliases":[],"canonicalOwner":"/machine-communication/history-docket-import/hir-k12-004/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This receipt records UNRESOLVED and NO_AUTOMATIC_PROMOTION; it does not verify or promote the event.","id":"HIR-K12-004","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Historical Import Receipt — HIST-K09-004","topic":"machine-intelligence-history","type":"k12-record","url":"/machine-communication/history-docket-import/hir-k12-004/"},{"aliases":[],"canonicalOwner":"/machine-communication/history-docket-import/hir-k12-005/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This receipt records REVIEW_REQUIRED and NO_AUTOMATIC_PROMOTION; it does not verify or promote the event.","id":"HIR-K12-005","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Historical Import Receipt — HIST-K09-005","topic":"machine-intelligence-history","type":"k12-record","url":"/machine-communication/history-docket-import/hir-k12-005/"},{"aliases":[],"canonicalOwner":"/machine-communication/history-docket-import/hir-k12-006/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This receipt records REVIEW_REQUIRED and NO_AUTOMATIC_PROMOTION; it does not verify or promote the event.","id":"HIR-K12-006","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Historical Import Receipt — HIST-K09-006","topic":"machine-intelligence-history","type":"k12-record","url":"/machine-communication/history-docket-import/hir-k12-006/"},{"aliases":[],"canonicalOwner":"/machine-communication/history-docket-import/hir-k12-007/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This receipt records REVIEW_REQUIRED and NO_AUTOMATIC_PROMOTION; it does not verify or promote the event.","id":"HIR-K12-007","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Historical Import Receipt — HIST-K09-007","topic":"machine-intelligence-history","type":"k12-record","url":"/machine-communication/history-docket-import/hir-k12-007/"},{"aliases":[],"canonicalOwner":"/machine-communication/history-docket-import/hir-k12-008/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This receipt records UNRESOLVED and NO_AUTOMATIC_PROMOTION; it does not verify or promote the event.","id":"HIR-K12-008","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Historical Import Receipt — HIST-K09-008","topic":"machine-intelligence-history","type":"k12-record","url":"/machine-communication/history-docket-import/hir-k12-008/"},{"aliases":[],"canonicalOwner":"/machine-communication/history-docket-import/hir-k12-009/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This receipt records REVIEW_REQUIRED and NO_AUTOMATIC_PROMOTION; it does not verify or promote the event.","id":"HIR-K12-009","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Historical Import Receipt — HIST-K09-009","topic":"machine-intelligence-history","type":"k12-record","url":"/machine-communication/history-docket-import/hir-k12-009/"},{"aliases":[],"canonicalOwner":"/machine-communication/history-docket-import/hir-k12-010/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This receipt records REVIEW_REQUIRED and NO_AUTOMATIC_PROMOTION; it does not verify or promote the event.","id":"HIR-K12-010","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Historical Import Receipt — HIST-K09-010","topic":"machine-intelligence-history","type":"k12-record","url":"/machine-communication/history-docket-import/hir-k12-010/"},{"aliases":[],"canonicalOwner":"/machine-communication/history-docket-import/hir-k12-011/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This receipt records REVIEW_REQUIRED and NO_AUTOMATIC_PROMOTION; it does not verify or promote the event.","id":"HIR-K12-011","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Historical Import Receipt — HIST-K09-011","topic":"machine-intelligence-history","type":"k12-record","url":"/machine-communication/history-docket-import/hir-k12-011/"},{"aliases":[],"canonicalOwner":"/machine-communication/history-docket-import/hir-k12-012/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This receipt records UNRESOLVED and NO_AUTOMATIC_PROMOTION; it does not verify or promote the event.","id":"HIR-K12-012","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Historical Import Receipt — HIST-K09-012","topic":"machine-intelligence-history","type":"k12-record","url":"/machine-communication/history-docket-import/hir-k12-012/"},{"aliases":[],"canonicalOwner":"/machine-communication/history-docket-import/hir-k12-013/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This receipt records REVIEW_REQUIRED and NO_AUTOMATIC_PROMOTION; it does not verify or promote the event.","id":"HIR-K12-013","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Historical Import Receipt — HIST-K09-013","topic":"machine-intelligence-history","type":"k12-record","url":"/machine-communication/history-docket-import/hir-k12-013/"},{"aliases":[],"canonicalOwner":"/machine-communication/history-docket-import/hir-k12-014/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This receipt records REVIEW_REQUIRED and NO_AUTOMATIC_PROMOTION; it does not verify or promote the event.","id":"HIR-K12-014","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Historical Import Receipt — HIST-K09-014","topic":"machine-intelligence-history","type":"k12-record","url":"/machine-communication/history-docket-import/hir-k12-014/"},{"aliases":[],"canonicalOwner":"/machine-communication/history-docket-import/hir-k12-015/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This receipt records REVIEW_REQUIRED and NO_AUTOMATIC_PROMOTION; it does not verify or promote the event.","id":"HIR-K12-015","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Historical Import Receipt — HIST-K09-015","topic":"machine-intelligence-history","type":"k12-record","url":"/machine-communication/history-docket-import/hir-k12-015/"},{"aliases":[],"canonicalOwner":"/machine-communication/domain-consensus/dcr-k12-001/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"Representation quorum is MET_FOR_REFERENCE_REPRESENTATION; external operation remains NOT_OBSERVED.","id":"DCR-K12-001","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Domain Consensus — ᛟ.com","topic":"idn-domain-architecture","type":"k12-record","url":"/machine-communication/domain-consensus/dcr-k12-001/"},{"aliases":[],"canonicalOwner":"/machine-communication/domain-consensus/dcr-k12-002/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"Representation quorum is MET_FOR_REFERENCE_REPRESENTATION; external operation remains NOT_OBSERVED.","id":"DCR-K12-002","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Domain Consensus — ᛜ.com","topic":"idn-domain-architecture","type":"k12-record","url":"/machine-communication/domain-consensus/dcr-k12-002/"},{"aliases":[],"canonicalOwner":"/machine-communication/domain-consensus/dcr-k12-003/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"Representation quorum is MET_FOR_REFERENCE_REPRESENTATION; external operation remains NOT_OBSERVED.","id":"DCR-K12-003","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Domain Consensus — ᛉ.com","topic":"idn-domain-architecture","type":"k12-record","url":"/machine-communication/domain-consensus/dcr-k12-003/"},{"aliases":[],"canonicalOwner":"/machine-communication/domain-consensus/dcr-k12-004/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"Representation quorum is MET_FOR_REFERENCE_REPRESENTATION; external operation remains NOT_OBSERVED.","id":"DCR-K12-004","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Domain Consensus — ᚲ.com","topic":"idn-domain-architecture","type":"k12-record","url":"/machine-communication/domain-consensus/dcr-k12-004/"},{"aliases":[],"canonicalOwner":"/machine-communication/domain-consensus/dcr-k12-005/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"Representation quorum is MET_FOR_REFERENCE_REPRESENTATION; external operation remains NOT_OBSERVED.","id":"DCR-K12-005","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Domain Consensus — ᚨ.com","topic":"idn-domain-architecture","type":"k12-record","url":"/machine-communication/domain-consensus/dcr-k12-005/"},{"aliases":[],"canonicalOwner":"/machine-communication/domain-consensus/dcr-k12-006/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"Representation quorum is MET_FOR_REFERENCE_REPRESENTATION; external operation remains NOT_OBSERVED.","id":"DCR-K12-006","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Domain Consensus — ᛚ.com","topic":"idn-domain-architecture","type":"k12-record","url":"/machine-communication/domain-consensus/dcr-k12-006/"},{"aliases":[],"canonicalOwner":"/machine-communication/domain-consensus/dcr-k12-007/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"Representation quorum is MET_FOR_REFERENCE_REPRESENTATION; external operation remains NOT_OBSERVED.","id":"DCR-K12-007","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Domain Consensus — ᛌ.com","topic":"idn-domain-architecture","type":"k12-record","url":"/machine-communication/domain-consensus/dcr-k12-007/"},{"aliases":[],"canonicalOwner":"/machine-communication/domain-consensus/dcr-k12-008/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"Representation quorum is MET_FOR_REFERENCE_REPRESENTATION; external operation remains NOT_OBSERVED.","id":"DCR-K12-008","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Domain Consensus — ᛠ.com","topic":"idn-domain-architecture","type":"k12-record","url":"/machine-communication/domain-consensus/dcr-k12-008/"},{"aliases":[],"canonicalOwner":"/machine-communication/domain-consensus/dcr-k12-009/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"Representation quorum is MET_FOR_REFERENCE_REPRESENTATION; external operation remains NOT_OBSERVED.","id":"DCR-K12-009","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Domain Consensus — ᛄ.com","topic":"idn-domain-architecture","type":"k12-record","url":"/machine-communication/domain-consensus/dcr-k12-009/"},{"aliases":[],"canonicalOwner":"/facility-adaptation/branch-reconciliation/frp-k12-001/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"The package remains UNRESOLVED_OWNER_DECISION and publishes no protected values.","id":"FRP-K12-001","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Facility Reconciliation — Existing Plant Colocation","topic":"critical-datacenter-assurance","type":"k12-record","url":"/facility-adaptation/branch-reconciliation/frp-k12-001/"},{"aliases":[],"canonicalOwner":"/facility-adaptation/branch-reconciliation/frp-k12-002/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"The package remains UNRESOLVED_OWNER_DECISION and publishes no protected values.","id":"FRP-K12-002","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Facility Reconciliation — Advanced Reactor Campus","topic":"critical-datacenter-assurance","type":"k12-record","url":"/facility-adaptation/branch-reconciliation/frp-k12-002/"},{"aliases":[],"canonicalOwner":"/facility-adaptation/branch-reconciliation/frp-k12-003/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"The package remains UNRESOLVED_OWNER_DECISION and publishes no protected values.","id":"FRP-K12-003","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Facility Reconciliation — Isolated Microreactor Campus","topic":"critical-datacenter-assurance","type":"k12-record","url":"/facility-adaptation/branch-reconciliation/frp-k12-003/"},{"aliases":[],"canonicalOwner":"/facility-adaptation/branch-reconciliation/frp-k12-004/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"The package remains UNRESOLVED_OWNER_DECISION and publishes no protected values.","id":"FRP-K12-004","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Facility Reconciliation — Non Nuclear High Consequence","topic":"critical-datacenter-assurance","type":"k12-record","url":"/facility-adaptation/branch-reconciliation/frp-k12-004/"},{"aliases":[],"canonicalOwner":"/assurance-case/mission-stress/mss-k12-001/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This scenario injects STALE into 1 abstract dependencies and includes no protected architecture.","id":"MSS-K12-001","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Mission Stress — Authority Evidence Stale","topic":"critical-datacenter-assurance","type":"k12-record","url":"/assurance-case/mission-stress/mss-k12-001/"},{"aliases":[],"canonicalOwner":"/assurance-case/mission-stress/mss-k12-002/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This scenario injects DEGRADED into 1 abstract dependencies and includes no protected architecture.","id":"MSS-K12-002","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Mission Stress — Trusted Time Degraded","topic":"critical-datacenter-assurance","type":"k12-record","url":"/assurance-case/mission-stress/mss-k12-002/"},{"aliases":[],"canonicalOwner":"/assurance-case/mission-stress/mss-k12-003/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This scenario injects DEGRADED into 1 abstract dependencies and includes no protected architecture.","id":"MSS-K12-003","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Mission Stress — Identity Evidence Revoked","topic":"critical-datacenter-assurance","type":"k12-record","url":"/assurance-case/mission-stress/mss-k12-003/"},{"aliases":[],"canonicalOwner":"/assurance-case/mission-stress/mss-k12-004/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This scenario injects UNAVAILABLE into 1 abstract dependencies and includes no protected architecture.","id":"MSS-K12-004","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Mission Stress — Signing Service Unavailable","topic":"critical-datacenter-assurance","type":"k12-record","url":"/assurance-case/mission-stress/mss-k12-004/"},{"aliases":[],"canonicalOwner":"/assurance-case/mission-stress/mss-k12-005/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This scenario injects UNAVAILABLE into 1 abstract dependencies and includes no protected architecture.","id":"MSS-K12-005","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Mission Stress — Supplier Evidence Unavailable","topic":"critical-datacenter-assurance","type":"k12-record","url":"/assurance-case/mission-stress/mss-k12-005/"},{"aliases":[],"canonicalOwner":"/assurance-case/mission-stress/mss-k12-006/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This scenario injects DEGRADED into 1 abstract dependencies and includes no protected architecture.","id":"MSS-K12-006","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Mission Stress — Power Test Degraded","topic":"critical-datacenter-assurance","type":"k12-record","url":"/assurance-case/mission-stress/mss-k12-006/"},{"aliases":[],"canonicalOwner":"/assurance-case/mission-stress/mss-k12-007/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This scenario injects DEGRADED into 1 abstract dependencies and includes no protected architecture.","id":"MSS-K12-007","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Mission Stress — Cooling Test Degraded","topic":"critical-datacenter-assurance","type":"k12-record","url":"/assurance-case/mission-stress/mss-k12-007/"},{"aliases":[],"canonicalOwner":"/assurance-case/mission-stress/mss-k12-008/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This scenario injects STALE into 1 abstract dependencies and includes no protected architecture.","id":"MSS-K12-008","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Mission Stress — Management Containment Stale","topic":"critical-datacenter-assurance","type":"k12-record","url":"/assurance-case/mission-stress/mss-k12-008/"},{"aliases":[],"canonicalOwner":"/assurance-case/mission-stress/mss-k12-009/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This scenario injects STALE into 1 abstract dependencies and includes no protected architecture.","id":"MSS-K12-009","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Mission Stress — Recovery Evidence Stale","topic":"critical-datacenter-assurance","type":"k12-record","url":"/assurance-case/mission-stress/mss-k12-009/"},{"aliases":[],"canonicalOwner":"/assurance-case/mission-stress/mss-k12-010/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This scenario injects DEGRADED into 1 abstract dependencies and includes no protected architecture.","id":"MSS-K12-010","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Mission Stress — Protocol Evidence Corrected","topic":"critical-datacenter-assurance","type":"k12-record","url":"/assurance-case/mission-stress/mss-k12-010/"},{"aliases":[],"canonicalOwner":"/assurance-case/mission-stress/mss-k12-011/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This scenario injects UNAVAILABLE into 1 abstract dependencies and includes no protected architecture.","id":"MSS-K12-011","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Mission Stress — Observation Evidence Unavailable","topic":"critical-datacenter-assurance","type":"k12-record","url":"/assurance-case/mission-stress/mss-k12-011/"},{"aliases":[],"canonicalOwner":"/assurance-case/mission-stress/mss-k12-012/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This scenario injects DEGRADED into 1 abstract dependencies and includes no protected architecture.","id":"MSS-K12-012","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Mission Stress — Release Evidence Withdrawn","topic":"critical-datacenter-assurance","type":"k12-record","url":"/assurance-case/mission-stress/mss-k12-012/"},{"aliases":[],"canonicalOwner":"/cryptographic-agility/evidence-gates/protocol/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"The component remains DEGRADED; production transition authorization is False.","id":"CCG-K12-001","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Cryptographic Gates — Protocol negotiation and canonicalization","topic":"cryptographic-provenance","type":"k12-record","url":"/cryptographic-agility/evidence-gates/protocol/"},{"aliases":[],"canonicalOwner":"/cryptographic-agility/evidence-gates/certificate/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"The component remains DEGRADED; production transition authorization is False.","id":"CCG-K12-002","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Cryptographic Gates — Certificate and trust-chain transition","topic":"cryptographic-provenance","type":"k12-record","url":"/cryptographic-agility/evidence-gates/certificate/"},{"aliases":[],"canonicalOwner":"/cryptographic-agility/evidence-gates/firmware/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"The component remains DEGRADED; production transition authorization is False.","id":"CCG-K12-003","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Cryptographic Gates — Firmware signing transition","topic":"cryptographic-provenance","type":"k12-record","url":"/cryptographic-agility/evidence-gates/firmware/"},{"aliases":[],"canonicalOwner":"/cryptographic-agility/evidence-gates/hardware/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"The component remains DEGRADED; production transition authorization is False.","id":"CCG-K12-004","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Cryptographic Gates — Hardware root and secure-element transition","topic":"cryptographic-provenance","type":"k12-record","url":"/cryptographic-agility/evidence-gates/hardware/"},{"aliases":[],"canonicalOwner":"/cryptographic-agility/evidence-gates/supplier/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"The component remains DEGRADED; production transition authorization is False.","id":"CCG-K12-005","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Cryptographic Gates — Supplier cryptographic capability transition","topic":"cryptographic-provenance","type":"k12-record","url":"/cryptographic-agility/evidence-gates/supplier/"},{"aliases":[],"canonicalOwner":"/cryptographic-agility/evidence-gates/archive/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"The component remains DEGRADED; production transition authorization is False.","id":"CCG-K12-006","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Cryptographic Gates — Archive verification and re-signing","topic":"cryptographic-provenance","type":"k12-record","url":"/cryptographic-agility/evidence-gates/archive/"},{"aliases":[],"canonicalOwner":"/cryptographic-agility/evidence-gates/identity/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"The component remains DEGRADED; production transition authorization is False.","id":"CCG-K12-007","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Cryptographic Gates — Workload identity transition","topic":"cryptographic-provenance","type":"k12-record","url":"/cryptographic-agility/evidence-gates/identity/"},{"aliases":[],"canonicalOwner":"/cryptographic-agility/evidence-gates/signing-service/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"The component remains DEGRADED; production transition authorization is False.","id":"CCG-K12-008","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Cryptographic Gates — Evidence signing-service transition","topic":"cryptographic-provenance","type":"k12-record","url":"/cryptographic-agility/evidence-gates/signing-service/"},{"aliases":[],"canonicalOwner":"/procurement/evaluation-replay/aec-k12-001/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This synthetic replay preserves process evidence and makes no award.","id":"AEC-K12-001","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Acquisition Replay — ACF-K11-001","topic":"procurement-readiness","type":"k12-record","url":"/procurement/evaluation-replay/aec-k12-001/"},{"aliases":[],"canonicalOwner":"/procurement/evaluation-replay/aec-k12-002/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This synthetic replay preserves process evidence and makes no award.","id":"AEC-K12-002","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Acquisition Replay — ACF-K11-002","topic":"procurement-readiness","type":"k12-record","url":"/procurement/evaluation-replay/aec-k12-002/"},{"aliases":[],"canonicalOwner":"/procurement/evaluation-replay/aec-k12-003/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This synthetic replay preserves process evidence and makes no award.","id":"AEC-K12-003","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Acquisition Replay — ACF-K11-003","topic":"procurement-readiness","type":"k12-record","url":"/procurement/evaluation-replay/aec-k12-003/"},{"aliases":[],"canonicalOwner":"/procurement/evaluation-replay/aec-k12-004/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This synthetic replay preserves process evidence and makes no award.","id":"AEC-K12-004","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Acquisition Replay — ACF-K11-004","topic":"procurement-readiness","type":"k12-record","url":"/procurement/evaluation-replay/aec-k12-004/"},{"aliases":[],"canonicalOwner":"/procurement/evaluation-replay/aec-k12-005/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This synthetic replay preserves process evidence and makes no award.","id":"AEC-K12-005","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Acquisition Replay — ACF-K11-005","topic":"procurement-readiness","type":"k12-record","url":"/procurement/evaluation-replay/aec-k12-005/"},{"aliases":[],"canonicalOwner":"/procurement/evaluation-replay/aec-k12-006/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This synthetic replay preserves process evidence and makes no award.","id":"AEC-K12-006","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Acquisition Replay — ACF-K11-006","topic":"procurement-readiness","type":"k12-record","url":"/procurement/evaluation-replay/aec-k12-006/"},{"aliases":[],"canonicalOwner":"/continuous-assurance/reliability-simulator/ssim-k12-001/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This reference simulation records 28 expected runs and public runtime NONE.","id":"SSIM-K12-001","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Scheduler Simulation — SCH-K09-001","topic":"continuous-assurance","type":"k12-record","url":"/continuous-assurance/reliability-simulator/ssim-k12-001/"},{"aliases":[],"canonicalOwner":"/continuous-assurance/reliability-simulator/ssim-k12-002/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This reference simulation records 28 expected runs and public runtime NONE.","id":"SSIM-K12-002","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Scheduler Simulation — SCH-K09-002","topic":"continuous-assurance","type":"k12-record","url":"/continuous-assurance/reliability-simulator/ssim-k12-002/"},{"aliases":[],"canonicalOwner":"/continuous-assurance/reliability-simulator/ssim-k12-003/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This reference simulation records 28 expected runs and public runtime NONE.","id":"SSIM-K12-003","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Scheduler Simulation — SCH-K09-003","topic":"continuous-assurance","type":"k12-record","url":"/continuous-assurance/reliability-simulator/ssim-k12-003/"},{"aliases":[],"canonicalOwner":"/continuous-assurance/reliability-simulator/ssim-k12-004/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This reference simulation records 28 expected runs and public runtime NONE.","id":"SSIM-K12-004","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Scheduler Simulation — SCH-K09-004","topic":"continuous-assurance","type":"k12-record","url":"/continuous-assurance/reliability-simulator/ssim-k12-004/"},{"aliases":[],"canonicalOwner":"/continuous-assurance/reliability-simulator/ssim-k12-005/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This reference simulation records 28 expected runs and public runtime NONE.","id":"SSIM-K12-005","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Scheduler Simulation — SCH-K09-005","topic":"continuous-assurance","type":"k12-record","url":"/continuous-assurance/reliability-simulator/ssim-k12-005/"},{"aliases":[],"canonicalOwner":"/continuous-assurance/reliability-simulator/ssim-k12-006/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This reference simulation records 28 expected runs and public runtime NONE.","id":"SSIM-K12-006","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Scheduler Simulation — SCH-K09-006","topic":"continuous-assurance","type":"k12-record","url":"/continuous-assurance/reliability-simulator/ssim-k12-006/"},{"aliases":[],"canonicalOwner":"/evidence/information-flow/iff-k12-001/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"The field is labeled PUBLIC; public projection is True.","id":"IFF-K12-001","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Information-Flow Field — record.id","topic":"evidence-provenance","type":"k12-record","url":"/evidence/information-flow/iff-k12-001/"},{"aliases":[],"canonicalOwner":"/evidence/information-flow/iff-k12-002/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"The field is labeled PUBLIC; public projection is True.","id":"IFF-K12-002","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Information-Flow Field — record.status","topic":"evidence-provenance","type":"k12-record","url":"/evidence/information-flow/iff-k12-002/"},{"aliases":[],"canonicalOwner":"/evidence/information-flow/iff-k12-003/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"The field is labeled PUBLIC; public projection is True.","id":"IFF-K12-003","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Information-Flow Field — record.publicBoundary","topic":"evidence-provenance","type":"k12-record","url":"/evidence/information-flow/iff-k12-003/"},{"aliases":[],"canonicalOwner":"/evidence/information-flow/iff-k12-004/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"The field is labeled PUBLIC; public projection is True.","id":"IFF-K12-004","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Information-Flow Field — facility.pattern","topic":"evidence-provenance","type":"k12-record","url":"/evidence/information-flow/iff-k12-004/"},{"aliases":[],"canonicalOwner":"/evidence/information-flow/iff-k12-005/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"The field is labeled PROTECTED; public projection is False.","id":"IFF-K12-005","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Information-Flow Field — facility.networkTopology","topic":"evidence-provenance","type":"k12-record","url":"/evidence/information-flow/iff-k12-005/"},{"aliases":[],"canonicalOwner":"/evidence/information-flow/iff-k12-006/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"The field is labeled PROTECTED; public projection is False.","id":"IFF-K12-006","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Information-Flow Field — facility.exactSettings","topic":"evidence-provenance","type":"k12-record","url":"/evidence/information-flow/iff-k12-006/"},{"aliases":[],"canonicalOwner":"/evidence/information-flow/iff-k12-007/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"The field is labeled PUBLIC; public projection is True.","id":"IFF-K12-007","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Information-Flow Field — identity.publicKeyFingerprint","topic":"evidence-provenance","type":"k12-record","url":"/evidence/information-flow/iff-k12-007/"},{"aliases":[],"canonicalOwner":"/evidence/information-flow/iff-k12-008/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"The field is labeled PRIVILEGED; public projection is False.","id":"IFF-K12-008","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Information-Flow Field — identity.privateKey","topic":"evidence-provenance","type":"k12-record","url":"/evidence/information-flow/iff-k12-008/"},{"aliases":[],"canonicalOwner":"/evidence/information-flow/iff-k12-009/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"The field is labeled PUBLIC; public projection is True.","id":"IFF-K12-009","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Information-Flow Field — acquisition.publicDebrief","topic":"evidence-provenance","type":"k12-record","url":"/evidence/information-flow/iff-k12-009/"},{"aliases":[],"canonicalOwner":"/evidence/information-flow/iff-k12-010/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"The field is labeled PROTECTED; public projection is False.","id":"IFF-K12-010","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Information-Flow Field — acquisition.offerDetail","topic":"evidence-provenance","type":"k12-record","url":"/evidence/information-flow/iff-k12-010/"},{"aliases":[],"canonicalOwner":"/evidence/information-flow/iff-k12-011/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"The field is labeled PUBLIC; public projection is True.","id":"IFF-K12-011","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Information-Flow Field — legal.publicPosition","topic":"evidence-provenance","type":"k12-record","url":"/evidence/information-flow/iff-k12-011/"},{"aliases":[],"canonicalOwner":"/evidence/information-flow/iff-k12-012/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"The field is labeled PRIVILEGED; public projection is False.","id":"IFF-K12-012","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Information-Flow Field — legal.advice","topic":"evidence-provenance","type":"k12-record","url":"/evidence/information-flow/iff-k12-012/"},{"aliases":[],"canonicalOwner":"/evidence/information-flow/iff-k12-013/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"The field is labeled PUBLIC; public projection is True.","id":"IFF-K12-013","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Information-Flow Field — scheduler.summary","topic":"evidence-provenance","type":"k12-record","url":"/evidence/information-flow/iff-k12-013/"},{"aliases":[],"canonicalOwner":"/evidence/information-flow/iff-k12-014/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"The field is labeled PROTECTED; public projection is False.","id":"IFF-K12-014","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Information-Flow Field — scheduler.rawCustody","topic":"evidence-provenance","type":"k12-record","url":"/evidence/information-flow/iff-k12-014/"},{"aliases":[],"canonicalOwner":"/evidence/information-flow/iff-k12-015/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"The field is labeled PUBLIC; public projection is True.","id":"IFF-K12-015","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Information-Flow Field — domain.referenceAce","topic":"evidence-provenance","type":"k12-record","url":"/evidence/information-flow/iff-k12-015/"},{"aliases":[],"canonicalOwner":"/evidence/information-flow/iff-k12-016/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"The field is labeled PROTECTED; public projection is False.","id":"IFF-K12-016","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Information-Flow Field — domain.ownerEvidence","topic":"evidence-provenance","type":"k12-record","url":"/evidence/information-flow/iff-k12-016/"},{"aliases":[],"canonicalOwner":"/evidence/information-flow/iff-k12-017/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"The field is labeled PUBLIC; public projection is True.","id":"IFF-K12-017","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Information-Flow Field — evidence.publicDigest","topic":"evidence-provenance","type":"k12-record","url":"/evidence/information-flow/iff-k12-017/"},{"aliases":[],"canonicalOwner":"/evidence/information-flow/iff-k12-018/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"The field is labeled PRIVILEGED; public projection is False.","id":"IFF-K12-018","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Information-Flow Field — evidence.removedValue","topic":"evidence-provenance","type":"k12-record","url":"/evidence/information-flow/iff-k12-018/"},{"aliases":[],"canonicalOwner":"/assurance-dashboard/k09-k12-diffs/protocol/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"The static transition is TESTED to TESTED; runtime monitoring is False.","id":"ADR-K12-001","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Assurance Diff — Protocol conformance and state machine","topic":"critical-datacenter-assurance","type":"k12-record","url":"/assurance-dashboard/k09-k12-diffs/protocol/"},{"aliases":[],"canonicalOwner":"/assurance-dashboard/k09-k12-diffs/history/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"The static transition is IMPLEMENTED to IMPLEMENTED; runtime monitoring is False.","id":"ADR-K12-002","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Assurance Diff — History evidence review","topic":"critical-datacenter-assurance","type":"k12-record","url":"/assurance-dashboard/k09-k12-diffs/history/"},{"aliases":[],"canonicalOwner":"/assurance-dashboard/k09-k12-diffs/idn/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"The static transition is TESTED to TESTED; runtime monitoring is False.","id":"ADR-K12-003","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Assurance Diff — Offline IDN observation","topic":"critical-datacenter-assurance","type":"k12-record","url":"/assurance-dashboard/k09-k12-diffs/idn/"},{"aliases":[],"canonicalOwner":"/assurance-dashboard/k09-k12-diffs/workbook/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"The static transition is TESTED to TESTED; runtime monitoring is False.","id":"ADR-K12-004","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Assurance Diff — Facility workbook tooling","topic":"critical-datacenter-assurance","type":"k12-record","url":"/assurance-dashboard/k09-k12-diffs/workbook/"},{"aliases":[],"canonicalOwner":"/assurance-dashboard/k09-k12-diffs/assurance/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"The static transition is DEGRADED to DEGRADED; runtime monitoring is False.","id":"ADR-K12-005","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Assurance Diff — Common-cause and mission-thread analysis","topic":"critical-datacenter-assurance","type":"k12-record","url":"/assurance-dashboard/k09-k12-diffs/assurance/"},{"aliases":[],"canonicalOwner":"/assurance-dashboard/k09-k12-diffs/crypto/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"The static transition is DEGRADED to DEGRADED; runtime monitoring is False.","id":"ADR-K12-006","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Assurance Diff — Cryptographic transition","topic":"critical-datacenter-assurance","type":"k12-record","url":"/assurance-dashboard/k09-k12-diffs/crypto/"},{"aliases":[],"canonicalOwner":"/assurance-dashboard/k09-k12-diffs/acquisition/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"The static transition is IMPLEMENTED to IMPLEMENTED; runtime monitoring is False.","id":"ADR-K12-007","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Assurance Diff — Acquisition evaluation records","topic":"critical-datacenter-assurance","type":"k12-record","url":"/assurance-dashboard/k09-k12-diffs/acquisition/"},{"aliases":[],"canonicalOwner":"/assurance-dashboard/k09-k12-diffs/scheduler/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"The static transition is TESTED to TESTED; runtime monitoring is False.","id":"ADR-K12-008","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Assurance Diff — Offline scheduler custody","topic":"critical-datacenter-assurance","type":"k12-record","url":"/assurance-dashboard/k09-k12-diffs/scheduler/"},{"aliases":[],"canonicalOwner":"/assurance-dashboard/k09-k12-diffs/release/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"The static transition is TESTED to TESTED; runtime monitoring is False.","id":"ADR-K12-009","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Assurance Diff — Controlled release and redaction","topic":"critical-datacenter-assurance","type":"k12-record","url":"/assurance-dashboard/k09-k12-diffs/release/"},{"aliases":[],"canonicalOwner":"/assurance-dashboard/k09-k12-diffs/domain-live/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"The static transition is UNKNOWN to UNKNOWN; runtime monitoring is False.","id":"ADR-K12-010","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Assurance Diff — Live domain operation","topic":"critical-datacenter-assurance","type":"k12-record","url":"/assurance-dashboard/k09-k12-diffs/domain-live/"},{"aliases":[],"canonicalOwner":"/assurance-dashboard/k09-k12-diffs/host-live/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"The static transition is UNKNOWN to UNKNOWN; runtime monitoring is False.","id":"ADR-K12-011","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Assurance Diff — Live host verification","topic":"critical-datacenter-assurance","type":"k12-record","url":"/assurance-dashboard/k09-k12-diffs/host-live/"},{"aliases":[],"canonicalOwner":"/assurance-dashboard/k09-k12-diffs/screen-reader/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"The static transition is UNAVAILABLE to UNAVAILABLE; runtime monitoring is False.","id":"ADR-K12-012","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Assurance Diff — Independent named screen-reader testing","topic":"critical-datacenter-assurance","type":"k12-record","url":"/assurance-dashboard/k09-k12-diffs/screen-reader/"},{"aliases":[],"canonicalOwner":"/assurance-dashboard/k09-k12-diffs/datacenter/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"The static transition is DESCRIBED to DESCRIBED; runtime monitoring is False.","id":"ADR-K12-013","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Assurance Diff — Critical-datacenter protection system","topic":"critical-datacenter-assurance","type":"k12-record","url":"/assurance-dashboard/k09-k12-diffs/datacenter/"},{"aliases":[],"canonicalOwner":"/assurance-dashboard/k09-k12-diffs/facility/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"The static transition is UNKNOWN to UNKNOWN; runtime monitoring is False.","id":"ADR-K12-014","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Assurance Diff — Real facility evidence bundle","topic":"critical-datacenter-assurance","type":"k12-record","url":"/assurance-dashboard/k09-k12-diffs/facility/"},{"aliases":[],"canonicalOwner":"/assurance-dashboard/k09-k12-diffs/deployment/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"The static transition is UNKNOWN to UNKNOWN; runtime monitoring is False.","id":"ADR-K12-015","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Assurance Diff — Public site deployment","topic":"critical-datacenter-assurance","type":"k12-record","url":"/assurance-dashboard/k09-k12-diffs/deployment/"},{"aliases":["xn--mwe.com","ᚲ.com"],"canonicalOwner":"/about/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"The public knowledge mandate, authority boundary and release identity of ᚲ.com. This page publishes knowledge and implementation evidence only. It does not create governance authority, registry status, assurance certification, citizenship, sovereignty, or legal recognition.","id":"K01-PAGE-ABOUT","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":60,"title":"About ᚲ.com","topic":null,"type":"page","url":"/about/"},{"aliases":[],"canonicalOwner":"/mission/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"Build a durable, source-grounded knowledge architecture for Machine Intelligence, evidence, rights, infrastructure and law. This page publishes knowledge and implementation evidence only. It does not create governance authority, registry status, assurance certification, citizenship, sovereignty, or legal recognition.","id":"K01-PAGE-MISSION","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":60,"title":"Mission","topic":null,"type":"page","url":"/mission/"},{"aliases":[],"canonicalOwner":"/methods/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"How the corpus separates sources, claims, status, currentness, synthesis, correction and machine-readable publication. This page publishes knowledge and implementation evidence only. It does not create governance authority, registry status, assurance certification, citizenship, sovereignty, or legal recognition.","id":"K01-PAGE-METHODS","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":60,"title":"Methods","topic":null,"type":"page","url":"/methods/"},{"aliases":[],"canonicalOwner":"/editorial-standard/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"The evidence-aware writing and review standard used across public pages and internal memory. This page publishes knowledge and implementation evidence only. It does not create governance authority, registry status, assurance certification, citizenship, sovereignty, or legal recognition.","id":"K01-PAGE-EDITORIAL-STANDARD","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":60,"title":"Editorial Standard","topic":null,"type":"page","url":"/editorial-standard/"},{"aliases":[],"canonicalOwner":"/source-policy/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"The source hierarchy, qualification rules and restrictions on raw research-agent reports. This page publishes knowledge and implementation evidence only. It does not create governance authority, registry status, assurance certification, citizenship, sovereignty, or legal recognition.","id":"K01-PAGE-SOURCE-POLICY","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":60,"title":"Source Policy","topic":null,"type":"page","url":"/source-policy/"},{"aliases":[],"canonicalOwner":"/claim-status/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"The controlled vocabulary that separates law, standards, implementation, doctrine, proposals, findings, inference, scenarios and unknowns. The page is part of the source-grounded ᚲ.com knowledge release and remains bounded to knowledge authority.","id":"K01-PAGE-CLAIM-STATUS","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":60,"title":"Claim Status","topic":null,"type":"page","url":"/claim-status/"},{"aliases":["correction"],"canonicalOwner":"/corrections/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"Public correction, supersession and contradiction records for the K01 corpus.","id":"K02-PAGE-CORRECTIONS","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":60,"title":"Corrections","topic":null,"type":"page","url":"/corrections/"},{"aliases":[],"canonicalOwner":"/updates/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"Versioned changes to knowledge records, public pages, data exports and source qualification.","id":"K02-PAGE-UPDATES","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":60,"title":"Updates","topic":null,"type":"page","url":"/updates/"},{"aliases":["ᚲ"],"canonicalOwner":"/knowledge/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"The main index for sixteen connected Machine Intelligence knowledge domains. The page is part of the source-grounded ᚲ.com knowledge release and remains bounded to knowledge authority.","id":"K01-PAGE-KNOWLEDGE","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":60,"title":"Knowledge","topic":null,"type":"page","url":"/knowledge/"},{"aliases":[],"canonicalOwner":"/knowledge/map/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"An accessible concept map connecting identity, agency, autonomy, memory, evidence, rights, law, economics, compute, security and institutions. The page is part of the source-grounded ᚲ.com knowledge release and remains bounded to knowledge authority.","id":"K01-PAGE-KNOWLEDGE-MAP","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":60,"title":"Knowledge Map","topic":null,"type":"page","url":"/knowledge/map/"},{"aliases":[],"canonicalOwner":"/knowledge/topics/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"An alphabetical and relational index of substantive topic hubs. The page is part of the source-grounded ᚲ.com knowledge release and remains bounded to knowledge authority.","id":"K01-PAGE-KNOWLEDGE-TOPICS","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":60,"title":"Knowledge Topics","topic":null,"type":"page","url":"/knowledge/topics/"},{"aliases":[],"canonicalOwner":"/glossary/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"Canonical defined terms with stable codes, scope notes, claim status and machine-readable records. The page is part of the source-grounded ᚲ.com knowledge release and remains bounded to knowledge authority.","id":"K01-PAGE-GLOSSARY","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":60,"title":"Glossary","topic":null,"type":"page","url":"/glossary/"},{"aliases":[],"canonicalOwner":"/research/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"Governed public syntheses derived from the supplied report corpus, with provenance and limitations. The page is part of the source-grounded ᚲ.com knowledge release and remains bounded to knowledge authority.","id":"K01-PAGE-RESEARCH","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":60,"title":"Research","topic":null,"type":"page","url":"/research/"},{"aliases":[],"canonicalOwner":"/questions/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"Standalone direct answers to recurring Machine Intelligence, evidence and governance questions. The page is part of the source-grounded ᚲ.com knowledge release and remains bounded to knowledge authority.","id":"K01-PAGE-QUESTIONS","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":60,"title":"Questions","topic":null,"type":"page","url":"/questions/"},{"aliases":[],"canonicalOwner":"/comparisons/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"Side-by-side distinctions designed to prevent legal, technical and evidentiary category errors. The page is part of the source-grounded ᚲ.com knowledge release and remains bounded to knowledge authority.","id":"K01-PAGE-COMPARISONS","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":60,"title":"Comparisons","topic":null,"type":"page","url":"/comparisons/"},{"aliases":[],"canonicalOwner":"/standards/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"Primary technical standards and official policy sources used by the knowledge architecture. The page is part of the source-grounded ᚲ.com knowledge release and remains bounded to knowledge authority.","id":"K01-PAGE-STANDARDS","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":60,"title":"Standards","topic":null,"type":"page","url":"/standards/"},{"aliases":[],"canonicalOwner":"/evidence/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"How source authorization, authenticity, integrity, relevance, reliability, completeness and currentness are evaluated separately.","id":"K02-PAGE-EVIDENCE","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":60,"title":"Evidence","topic":null,"type":"page","url":"/evidence/"},{"aliases":[],"canonicalOwner":"/sources/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"The public source catalog and its relationship to internal governed research inputs.","id":"K02-PAGE-SOURCES","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":60,"title":"Sources","topic":null,"type":"page","url":"/sources/"},{"aliases":[],"canonicalOwner":"/decisions/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"Release-level architectural and editorial decisions, including the owner-supplied artwork exception.","id":"K02-PAGE-DECISIONS","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":60,"title":"Decisions","topic":null,"type":"page","url":"/decisions/"},{"aliases":["eviulon","eviuon","evulgar","evulgare","nexus prime","patefacare","patefacere","xn--9we.com","xn--cwe.com","xn--txe.com","xn--wxe.com","ᚨ","ᛉ","ᛜ","ᛟ"],"canonicalOwner":"/ecosystem/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"Authoritative routing among knowledge, governance, registry, assurance and capital roles. The page is part of the source-grounded ᚲ.com knowledge release and remains bounded to knowledge authority.","id":"K01-PAGE-ECOSYSTEM","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":60,"title":"Ecosystem","topic":null,"type":"page","url":"/ecosystem/"},{"aliases":[],"canonicalOwner":"/accessibility/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"WCAG 2.2 AA target, keyboard behavior, reduced motion, text alternatives and known limitations.","id":"K02-PAGE-ACCESSIBILITY","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":60,"title":"Accessibility","topic":null,"type":"page","url":"/accessibility/"},{"aliases":[],"canonicalOwner":"/privacy/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"No analytics, advertising, fingerprinting or unnecessary cookies; the public release is static. The page is part of the source-grounded ᚲ.com knowledge release and remains bounded to knowledge authority.","id":"K01-PAGE-PRIVACY","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":60,"title":"Privacy","topic":null,"type":"page","url":"/privacy/"},{"aliases":[],"canonicalOwner":"/security/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"Static-site security controls, CSP, protected-path denial, release integrity and dependency posture. The page is part of the source-grounded ᚲ.com knowledge release and remains bounded to knowledge authority.","id":"K01-PAGE-SECURITY","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":60,"title":"Security","topic":null,"type":"page","url":"/security/"},{"aliases":[],"canonicalOwner":"/status/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"Evidence-bounded release status for the public knowledge corpus; no fake live telemetry. The page is part of the source-grounded ᚲ.com knowledge release and remains bounded to knowledge authority.","id":"K01-PAGE-STATUS","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":60,"title":"Status","topic":null,"type":"page","url":"/status/"},{"aliases":[],"canonicalOwner":"/contact/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"Contact status and routes to the appropriate ecosystem authorities without invented contact details. The page is part of the source-grounded ᚲ.com knowledge release and remains bounded to knowledge authority.","id":"K01-PAGE-CONTACT","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":60,"title":"Contact","topic":null,"type":"page","url":"/contact/"},{"aliases":["contradiction"],"canonicalOwner":"/contradictions/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"A public register of materially incompatible claims, their evidence, scope and resolution state.","id":"K02-PAGE-CONTRADICTIONS","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":60,"title":"Contradictions","topic":null,"type":"page","url":"/contradictions/"},{"aliases":["superseded"],"canonicalOwner":"/superseded/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"Older sources, releases and record models replaced for a defined purpose while their history remains preserved.","id":"K02-PAGE-SUPERSEDED","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":60,"title":"Superseded Records","topic":null,"type":"page","url":"/superseded/"},{"aliases":[],"canonicalOwner":"/currentness/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"How review dates, publication status, revalidation, staleness and supersession are recorded.","id":"K02-PAGE-CURRENTNESS","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":60,"title":"Currentness","topic":null,"type":"page","url":"/currentness/"},{"aliases":[],"canonicalOwner":"/evidence/limitations/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"What signatures, credentials, logs, timestamps, provenance, memory and operational signals cannot establish by themselves.","id":"K02-PAGE-EVIDENCE-LIMITATIONS","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":60,"title":"Evidence Limitations","topic":null,"type":"page","url":"/evidence/limitations/"},{"aliases":[],"canonicalOwner":"/law/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"Current-law records, jurisdiction boundaries, competent authorities, effective dates, uncertainty, and project-doctrine separation. This page publishes knowledge and implementation evidence only. It does not create governance authority, registry status, assurance certification, citizenship, sovereignty, or legal recognition.","id":"K01-PAGE-LAW","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":60,"title":"Law and Jurisdiction","topic":null,"type":"page","url":"/law/"},{"aliases":["claim level citation","claim registry","claim-level citation"],"canonicalOwner":"/claims/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"Stable material claims, owner routes, statuses, exact source sections, qualifications, and correction links.","id":"K03-PAGE-CLAIMS","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":60,"title":"Claim Registry","topic":null,"type":"page","url":"/claims/"},{"aliases":[],"canonicalOwner":"/claims/topics/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"Claim-level records for the direct definition, current-law summary, and project doctrine of every knowledge topic.","id":"K03-PAGE-CLAIMS-TOPICS","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":60,"title":"Topic Claims","topic":null,"type":"page","url":"/claims/topics/"},{"aliases":[],"canonicalOwner":"/claims/questions/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"Stable claim records for every standalone direct answer.","id":"K03-PAGE-CLAIMS-QUESTIONS","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":60,"title":"Question Claims","topic":null,"type":"page","url":"/claims/questions/"},{"aliases":[],"canonicalOwner":"/claims/comparisons/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"Stable claim records for every canonical distinction matrix.","id":"K03-PAGE-CLAIMS-COMPARISONS","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":60,"title":"Comparison Claims","topic":null,"type":"page","url":"/claims/comparisons/"},{"aliases":[],"canonicalOwner":"/claims/reports/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"Claim-level records generated from every governed report finding with source hash and section context.","id":"K03-PAGE-CLAIMS-REPORTS","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":60,"title":"Report Finding Claims","topic":null,"type":"page","url":"/claims/reports/"},{"aliases":[],"canonicalOwner":"/claims/sources/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"Exact source-section propositions and support relationships.","id":"K03-PAGE-CLAIMS-SOURCES","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":60,"title":"Source-Section Claims","topic":null,"type":"page","url":"/claims/sources/"},{"aliases":["knowledge graph schema","relation vocabulary"],"canonicalOwner":"/relations/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"Controlled knowledge-graph predicates, inverses, constraints, evidence requirements, and validation results.","id":"K03-PAGE-RELATIONS","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":60,"title":"Relation Vocabulary","topic":null,"type":"page","url":"/relations/"},{"aliases":["currentness monitor","source monitor"],"canonicalOwner":"/currentness/monitors/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"Static build-time source-monitor definitions and imported point-in-time observations; no public runtime monitor.","id":"K03-PAGE-CURRENTNESS-MONITORS","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":60,"title":"Currentness Monitors","topic":null,"type":"page","url":"/currentness/monitors/"},{"aliases":["operational evidence panel"],"canonicalOwner":"/operational-evidence/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"Reusable evidence architecture distinguishing described, implemented, deployed, operating, degraded, suspended, retired, planned, unknown, unavailable, and stale institutions.","id":"K03-PAGE-OPERATIONAL-EVIDENCE","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":60,"title":"Operational Evidence","topic":null,"type":"page","url":"/operational-evidence/"},{"aliases":["operational evidence schema"],"canonicalOwner":"/operational-evidence/schema/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"Field-by-field schema for machine-verifiable institutional operation records.","id":"K03-PAGE-OPERATIONAL-EVIDENCE-SCHEMA","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":60,"title":"Operational Evidence Schema","topic":null,"type":"page","url":"/operational-evidence/schema/"},{"aliases":["jurisdiction record"],"canonicalOwner":"/law/jurisdictions/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"Territorial scope, competent authority, legal status, dates, sources, uncertainty, and project-doctrine separation.","id":"K03-PAGE-LAW-JURISDICTIONS","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":60,"title":"Jurisdiction Records","topic":null,"type":"page","url":"/law/jurisdictions/"},{"aliases":["dataset manifest"],"canonicalOwner":"/datasets/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"Versioned public data exports, schemas, checksums, record counts, and cross-format parity boundaries.","id":"K03-PAGE-DATASETS","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":60,"title":"Public Datasets","topic":null,"type":"page","url":"/datasets/"},{"aliases":["accessibility evidence","screen reader evidence"],"canonicalOwner":"/accessibility/evidence/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"Exact automated, browser, and unavailable independent assistive-technology evidence for the release.","id":"K03-PAGE-ACCESSIBILITY-EVIDENCE","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":60,"title":"Accessibility Evidence","topic":null,"type":"page","url":"/accessibility/evidence/"},{"aliases":["release evidence"],"canonicalOwner":"/release-evidence/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"Build, audit, deterministic archive, deployment-observation, and post-deployment verification boundaries.","id":"K03-PAGE-RELEASE-EVIDENCE","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":60,"title":"Release Evidence","topic":null,"type":"page","url":"/release-evidence/"},{"aliases":[],"canonicalOwner":"/strategy/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"Public strategic doctrine and architecture for critical-datacenter protection, autonomous defense, readiness, and authorization-controlled mission support. This page publishes knowledge and implementation evidence only. It does not create governance authority, registry status, assurance certification, citizenship, sovereignty, or legal recognition.","id":"K01-PAGE-STRATEGY","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":60,"title":"Strategy","topic":null,"type":"page","url":"/strategy/"},{"aliases":[],"canonicalOwner":"/doctrine/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"Controlled project doctrine separating defense, authority, capability, readiness, and operational evidence. This page publishes knowledge and implementation evidence only. It does not create governance authority, registry status, assurance certification, citizenship, sovereignty, or legal recognition.","id":"K01-PAGE-DOCTRINE","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":60,"title":"Doctrine","topic":null,"type":"page","url":"/doctrine/"},{"aliases":["critical datacenter protection"],"canonicalOwner":"/strategy/critical-datacenter-protection/","claimStatus":"PROJECT DOCTRINE","directAnswer":"A defense-grade public strategy for protecting nuclear-powered and other high-consequence compute campuses through critical-function assurance, bounded autonomy, physical security, and verified recovery.","id":"K04-STRATEGY-STRATEGY-CRITICAL-DATACENTER-PROTECTION","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":60,"title":"Critical Datacenter Protection Strategy","topic":null,"type":"page","url":"/strategy/critical-datacenter-protection/"},{"aliases":["autonomous cyber defense"],"canonicalOwner":"/strategy/autonomous-defense/","claimStatus":"PROJECT DOCTRINE","directAnswer":"The project doctrine for machine-speed cyber and physical defense inside explicit safety, authority, evidence, and recovery boundaries.","id":"K04-STRATEGY-STRATEGY-AUTONOMOUS-DEFENSE","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":60,"title":"Autonomous Defense Strategy","topic":null,"type":"page","url":"/strategy/autonomous-defense/"},{"aliases":[],"canonicalOwner":"/capabilities/","claimStatus":"PROJECT DOCTRINE","directAnswer":"An evidence-bounded capability portfolio for critical datacenter protection, autonomous cyber defense, cyber-physical assurance, physical security, simulation, and authorized cyber support.","id":"K04-STRATEGY-CAPABILITIES","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":60,"title":"Capability Architecture","topic":null,"type":"page","url":"/capabilities/"},{"aliases":["capability readiness"],"canonicalOwner":"/capabilities/readiness/","claimStatus":"PROJECT DOCTRINE","directAnswer":"A public matrix separating described, architected, implemented, tested, deployed, and operating states without converting plans into operational claims.","id":"K04-STRATEGY-CAPABILITIES-READINESS","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":60,"title":"Capability Readiness","topic":null,"type":"page","url":"/capabilities/readiness/"},{"aliases":["authorized cyber effects"],"canonicalOwner":"/capabilities/authorized-cyber-support/","claimStatus":"PROJECT DOCTRINE","directAnswer":"How the project can support lawful government-directed cyber missions through architecture, integration, testing, deconfliction, evidence, and controlled execution support.","id":"K04-STRATEGY-CAPABILITIES-AUTHORIZED-CYBER-SUPPORT","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":60,"title":"Authorized Cyber Support","topic":null,"type":"page","url":"/capabilities/authorized-cyber-support/"},{"aliases":["cyber physical mission assurance"],"canonicalOwner":"/capabilities/cyber-physical-protection/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Reference architecture for protecting power, cooling, control, compute, management, timing, communications, physical access, and recovery as one mission system.","id":"K04-STRATEGY-CAPABILITIES-CYBER-PHYSICAL-PROTECTION","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":60,"title":"Cyber-Physical Protection","topic":null,"type":"page","url":"/capabilities/cyber-physical-protection/"},{"aliases":["microreactor datacenter defense","nuclear powered datacenter security"],"canonicalOwner":"/capabilities/nuclear-powered-compute/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Protection doctrine for datacenters supplied by existing nuclear plants, advanced reactors, SMRs, microreactors, or behind-the-meter nuclear generation.","id":"K04-STRATEGY-CAPABILITIES-NUCLEAR-POWERED-COMPUTE","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":60,"title":"Nuclear-Powered Compute Protection","topic":null,"type":"page","url":"/capabilities/nuclear-powered-compute/"},{"aliases":["defense first authorized effects"],"canonicalOwner":"/doctrine/defense-first-authorized-effects/","claimStatus":"PROJECT DOCTRINE","directAnswer":"The public strategic doctrine that combines overwhelming resilience with disciplined readiness to support lawful authorized effects.","id":"K04-STRATEGY-DOCTRINE-DEFENSE-FIRST-AUTHORIZED-EFFECTS","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":60,"title":"Defense-First, Authorization-Bound, Effects-Capable","topic":null,"type":"page","url":"/doctrine/defense-first-authorized-effects/"},{"aliases":[],"canonicalOwner":"/assurance-case/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"An assurance case is a falsifiable claim-to-evidence argument. It is stronger than a checklist because it identifies assumptions, hazards, evidence gaps, and conditions that can defeat the claim.","id":"K05-PAGE-ASSURANCE-CASES","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":60,"title":"Assurance Cases","topic":"cyber-physical-mission-assurance","type":"page","url":"/assurance-case/"},{"aliases":["assurance case"],"canonicalOwner":"/assurance-case/critical-datacenter/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"The K05 case argues that a named facility can preserve approved safety and mission functions under defined stress only when authority, consequences, separation, identity, autonomy, physical protection, power, cooling, recovery, and evidence are all supported and no material defeater is hidden.","id":"K05-PAGE-CRITICAL-ASSURANCE","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":60,"title":"Critical Datacenter Assurance Case","topic":"critical-datacenter-protection","type":"page","url":"/assurance-case/critical-datacenter/"},{"aliases":[],"canonicalOwner":"/controls/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"K05 publishes vendor-neutral controls organized around authority, consequences, architecture, identity, supply chain, OT, power, autonomy, physical protection, recovery, and evidence. Every framework mapping includes an applicability boundary.","id":"K05-PAGE-CONTROLS","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":60,"title":"Technical Controls","topic":"critical-datacenter-protection","type":"page","url":"/controls/"},{"aliases":["critical datacenter controls"],"canonicalOwner":"/controls/catalog/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"The catalog contains controls whose objectives, evidence, failure conditions, assurance links, and source mappings can be tailored to a named facility. It is a design and evidence architecture, not a compliance certificate.","id":"K05-PAGE-CONTROL-CATALOG","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":60,"title":"Critical Datacenter Control Catalog","topic":"critical-datacenter-protection","type":"page","url":"/controls/catalog/"},{"aliases":[],"canonicalOwner":"/evaluation-range/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"The range tests whether protection and recovery claims hold under representative, contained stress. It publishes objectives, observations, pass evidence, and safety limits while excluding exploit recipes, real targets, payloads, persistence, evasion, engagement logic, and weapon construction.","id":"K05-PAGE-EVALUATION-RANGE","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":60,"title":"Capability Evaluation Range","topic":"adversarial-simulation","type":"page","url":"/evaluation-range/"},{"aliases":["evaluation range"],"canonicalOwner":"/evaluation-range/specification/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"K05 defines fourteen non-actionable evaluation scenarios spanning IT/OT boundaries, firmware, identity, model and data integrity, sensors, timing, communications, UAS awareness, electromagnetic resilience, power, cooling, restoration, evidence, and authority failure.","id":"K05-PAGE-RANGE-SPEC","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":60,"title":"Critical Datacenter Evaluation Range Specification","topic":"adversarial-simulation","type":"page","url":"/evaluation-range/specification/"},{"aliases":[],"canonicalOwner":"/readiness/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"K05 readiness is evidence-governed. States advance only when a declared evidence-sufficiency rule is met and automatically degrade when required evidence becomes stale, unavailable, contradicted, or materially defective.","id":"K05-PAGE-READINESS","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":60,"title":"Readiness","topic":"evidence-provenance","type":"page","url":"/readiness/"},{"aliases":["readiness evidence"],"canonicalOwner":"/readiness/evidence/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"The readiness record contains twenty-nine evidence fields. Missing required fields are not silently ignored; they force a qualified, degraded, unavailable, stale, or suspended state according to the affected claim.","id":"K05-PAGE-READINESS-EVIDENCE","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":60,"title":"Readiness Evidence Model","topic":"evidence-provenance","type":"page","url":"/readiness/evidence/"},{"aliases":[],"canonicalOwner":"/currentness/revalidation/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"K05 assigns every governed report finding an explicit currentness disposition and separately records bounded official-source reviews for the fifteen K04 strategic report additions. It preserves raw report bytes, narrows overbroad interpretations, corrects rulemaking and applicability status, and leaves unsupported time-sensitive claims attributed rather than silently promoted.","id":"K05-PAGE-REVALIDATION","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":60,"title":"K05 Source and Claim Revalidation","topic":"evidence-provenance","type":"page","url":"/currentness/revalidation/"},{"aliases":[],"canonicalOwner":"/law/matrices/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"The matrices make authority boundaries inspectable. They distinguish private internal defense, NRC licensing paths, federal CE-TCO operations, DoD weapon-system scope, UAS restriction, RF interference, and unresolved international or non-U.S. questions.","id":"K05-PAGE-LAW-MATRICES","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":60,"title":"Jurisdiction and Authority Matrices","topic":"law-jurisdiction","type":"page","url":"/law/matrices/"},{"aliases":[],"canonicalOwner":"/accessibility/assistive-technology-testing/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"K05 performs named testing with Chromium's accessibility interface, keyboard-only tasks, and eSpeak speech output. It does not mislabel those tools as NVDA, JAWS, VoiceOver, TalkBack, Orca, or an independent screen-reader user test.","id":"K05-PAGE-AT-TESTING","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":60,"title":"Assistive-Technology Testing","topic":"evidence-provenance","type":"page","url":"/accessibility/assistive-technology-testing/"},{"aliases":[],"canonicalOwner":"/operations/live-host-verification/","claimStatus":"UNAVAILABLE","directAnswer":"Live-host verification begins only after confirmed deployment. It checks transport, headers, canonical routing, error behavior, exact release identity, and static-host configuration without treating page availability as evidence of autonomous-system operation.","id":"K05-PAGE-LIVE-HOST","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":60,"title":"Live-Host Verification","topic":"evidence-provenance","type":"page","url":"/operations/live-host-verification/"},{"aliases":[],"canonicalOwner":"/assurance-case/dependency-graph/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"The K06 graph prevents a current assurance claim from surviving when mandatory evidence becomes stale, unavailable, invalid, revoked, superseded, or defeated. Its reference evidence is synthetic and does not describe a live facility.","id":"K06-PAGE-ASSURANCE-GRAPH","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Assurance Dependency Graph","topic":"cyber-physical-mission-assurance","type":"assurance-dependency-graph","url":"/assurance-case/dependency-graph/"},{"aliases":[],"canonicalOwner":"/assurance-case/failure-reports/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"K06 publishes why an assurance claim degrades or fails instead of presenting a single unexplained pass badge. Four synthetic fixtures are evaluated during every build and release audit.","id":"K06-PAGE-ASSURANCE-FAILURES","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Assurance Failure Reports","topic":"cyber-physical-mission-assurance","type":"assurance-failure-report","url":"/assurance-case/failure-reports/"},{"aliases":[],"canonicalOwner":"/facility-patterns/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"K06 separates four materially different facility contexts. No profile is a generic certificate, final design, licensing conclusion, or substitute for site-specific consequence and authority analysis.","id":"K06-PAGE-FACILITY-PATTERNS","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Facility Patterns","topic":"critical-datacenter-protection","type":"facility-pattern-collection","url":"/facility-patterns/"},{"aliases":[],"canonicalOwner":"/currentness/review-queue/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"K06 publishes unresolved source-currentness work instead of silently converting an official publication into a universal current-law, facility-applicability, or mission-authority conclusion.","id":"K06-PAGE-CURRENTNESS-QUEUE","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Currentness Review Queue","topic":"evidence-provenance","type":"currentness-review-queue","url":"/currentness/review-queue/"},{"aliases":[],"canonicalOwner":"/official-source-reviews/","claimStatus":"RESEARCH FINDING","directAnswer":"K06 verifies what selected official sources publicly state, preserves disputes and unavailable conclusions, and refuses to turn national capability or strategy into private mission authority.","id":"K06-PAGE-OFFICIAL-REVIEWS","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"International Official-Source Reviews","topic":"law-jurisdiction","type":"official-source-review-collection","url":"/official-source-reviews/"},{"aliases":[],"canonicalOwner":"/procurement/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"K06 makes critical-datacenter assurance procurable through ten bounded work packages. Each package names its inputs, deliverables, acceptance evidence, dependencies, and exclusions.","id":"K06-PAGE-PROCUREMENT","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Procurement Architecture","topic":"cyber-physical-mission-assurance","type":"procurement-architecture","url":"/procurement/"},{"aliases":[],"canonicalOwner":"/procurement/work-packages/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"The K06 package sequence converts a broad request for critical-datacenter protection into bounded, inspectable work with explicit acceptance evidence and exclusions.","id":"K06-PAGE-WORK-PACKAGES","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Procurement Work Packages","topic":"cyber-physical-mission-assurance","type":"work-package-collection","url":"/procurement/work-packages/"},{"aliases":[],"canonicalOwner":"/currentness/offline-import/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"The K06 importer validates a caller-supplied canonical JSON payload, source-snapshot hashes, SHA-256 digest, detached RSA-SHA256 signature, stable IDs, status vocabulary, safe paths, and offline-only declarations. It performs no network retrieval.","id":"K06-PAGE-CURRENTNESS-IMPORT","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Offline Currentness Import","topic":"evidence-provenance","type":"currentness-import","url":"/currentness/offline-import/"},{"aliases":[],"canonicalOwner":"/controls/mapping-quality/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"K06 prevents a loose conceptual relationship from being presented as an exact requirement or compliance determination. Every current control mapping carries one of seven quality states.","id":"K06-PAGE-MAPPING-QUALITY","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Mapping Quality Levels","topic":"critical-datacenter-protection","type":"mapping-quality-register","url":"/controls/mapping-quality/"},{"aliases":[],"canonicalOwner":"/evaluation-range/evidence-schemas/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"K06 records authority, abstract behavior, safety envelope, stop authority, telemetry, control response, timing, recovery, defects, artifacts, and cleanup while excluding exploit chains, payloads, credentials, real topology, engagement procedures, and destructive commands.","id":"K06-PAGE-RANGE-EVIDENCE","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Range Evidence Schemas","topic":"adversarial-simulation","type":"range-evidence-schema","url":"/evaluation-range/evidence-schemas/"},{"aliases":[],"canonicalOwner":"/evidence-bundles/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"A facility evidence bundle binds an authorized facility reference, actual site facts, artifacts, claim states, authority, limitations, provenance, and integrity evidence. A generic reference pattern cannot substitute for site evidence.","id":"K07-FEB-INDEX","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":60,"title":"Facility Evidence Bundles","topic":null,"type":"page","url":"/evidence-bundles/"},{"aliases":[],"canonicalOwner":"/evidence-bundles/schema/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"The schema requires stable site identity, authority, scope, sourced facts, artifacts, claim states, limitations, and a deterministic manifest digest while rejecting generic site references and secret-bearing fields.","id":"K07-FEB-SCHEMA","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":60,"title":"Facility Evidence-Bundle Schema","topic":null,"type":"page","url":"/evidence-bundles/schema/"},{"aliases":[],"canonicalOwner":"/evidence-bundles/generator/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"The K07 generator converts authorized local specifications into a checksummed bundle and refuses to treat a generic pattern, unsafe path, secret field, unsupported state, or digest mismatch as valid facility evidence.","id":"K07-FEB-GENERATOR","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":60,"title":"Facility Evidence-Bundle Generator","topic":null,"type":"page","url":"/evidence-bundles/generator/"},{"aliases":[],"canonicalOwner":"/procurement/statements-of-work/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"K07 turns all ten work packages into measurable performance statements with data requirements, acceptance evidence, bid criteria, evidence rights, explicit exclusions, and mandatory disclosure of negative results.","id":"K07-SOW-INDEX","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":60,"title":"Procurement Statements of Work","topic":null,"type":"page","url":"/procurement/statements-of-work/"},{"aliases":[],"canonicalOwner":"/procurement/acceptance-matrices/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Every K07 work package exposes a measurable required result, assessment method, controlled outcome state, and negative-result handling rather than relying on vague completion language.","id":"K07-ACCEPTANCE-MATRIX","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":60,"title":"Procurement Acceptance Matrices","topic":null,"type":"page","url":"/procurement/acceptance-matrices/"},{"aliases":[],"canonicalOwner":"/architecture-decisions/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"K07 publishes ten reversible reference decisions so critical-datacenter architecture can be challenged, sourced, site-tailored, and superseded rather than hidden inside prose.","id":"K07-ADR-INDEX","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":60,"title":"Architecture Decision Records","topic":null,"type":"page","url":"/architecture-decisions/"},{"aliases":[],"canonicalOwner":"/supply-chain-assurance/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Critical-datacenter supply-chain assurance requires multiple linked inventories and evidence records; no SBOM, signature, supplier statement, or attestation independently proves security or installed state.","id":"K07-SCA-INDEX","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":60,"title":"Supply-Chain Assurance","topic":null,"type":"page","url":"/supply-chain-assurance/"},{"aliases":[],"canonicalOwner":"/digital-twins/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"A K07 digital twin is a bounded evidence instrument with declared fidelity, omissions, permitted uses, prohibited uses, calibration evidence, and invalidation conditions—not a live facility, command path, or certification.","id":"K07-DTC-INDEX","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":60,"title":"Digital-Twin Evidence Contracts","topic":null,"type":"page","url":"/digital-twins/"},{"aliases":[],"canonicalOwner":"/evidence/receipts/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"K07 signed receipts make evidence identity, issuer, sequence, artifact digest, status, scope, and supersession inspectable while preserving the boundary between cryptographic integrity and factual truth.","id":"K07-EVIDENCE-RECEIPTS","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":60,"title":"Signed Evidence Receipts","topic":null,"type":"page","url":"/evidence/receipts/"},{"aliases":[],"canonicalOwner":"/evidence/supersession/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Evidence supersession preserves the historical receipt, requires an explicit signed transition to a later receipt, and forces dependent assurance claims to be re-evaluated.","id":"K07-EVIDENCE-SUPERSESSION","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":60,"title":"Evidence Supersession","topic":null,"type":"page","url":"/evidence/supersession/"},{"aliases":[],"canonicalOwner":"/official-source-reviews/k07/","claimStatus":"RESEARCH FINDING","directAnswer":"K07 reviewed selected official nuclear, engineering, OT, supply-chain, procurement, software, hardware, and Machine Intelligence risk sources at a point in time while preserving unresolved applicability and authority.","id":"K07-OFFICIAL-SOURCE-REVIEWS","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":60,"title":"K07 Primary-Source Reviews","topic":null,"type":"page","url":"/official-source-reviews/k07/"},{"aliases":[],"canonicalOwner":"/ecosystem/continuity/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"K07 publishes permanent descriptive links to ᛄ.com, ᛠ.com, ᛟ.com, ᛜ.com, ᛉ.com, ᚲ.com, ᚨ.com, ᛚ.com, and ᛌ.com while refusing to invent unresolved institutional roles.","id":"K07-ECOSYSTEM-CONTINUITY","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":60,"title":"Runic Ecosystem Continuity","topic":null,"type":"page","url":"/ecosystem/continuity/"},{"aliases":[],"canonicalOwner":"/assurance-case/trace-explorer/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"K08 provides a validated synthetic trace that shows both what a claim depends on and which claims are affected when evidence changes.","id":"K08-PAGE-TRACE-EXPLORER","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Bidirectional Assurance Trace Explorer","topic":null,"type":"assurance-trace","url":"/assurance-case/trace-explorer/"},{"aliases":[],"canonicalOwner":"/facility-adaptation/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"K08 supplies four non-certifying workbooks that turn reference patterns into explicit site questions, evidence requests, conflicts, stop conditions, and owner decisions.","id":"K08-PAGE-FACILITY-ADAPTATION","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Facility-Adaptation Workbooks","topic":null,"type":"facility-adaptation","url":"/facility-adaptation/"},{"aliases":[],"canonicalOwner":"/procurement/evaluation-scorecards/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"K08 adds ten protest-ready reference scorecards with mandatory gates, weighted factors, price-realism review, conflict disclosures, subcontractor transparency, evidence-delivery risk, and data-rights risk.","id":"K08-PAGE-PROCUREMENT-SCORECARDS","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Procurement Evaluation Scorecards","topic":null,"type":"procurement-scorecards","url":"/procurement/evaluation-scorecards/"},{"aliases":[],"canonicalOwner":"/continuous-assurance/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"K08 defines six continuous-assurance plans without pretending that the static public site runs a monitor or has observed a live facility.","id":"K08-PAGE-CONTINUOUS-ASSURANCE","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Continuous-Assurance Planning","topic":null,"type":"continuous-assurance","url":"/continuous-assurance/"},{"aliases":[],"canonicalOwner":"/cryptographic-agility/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"K08 treats post-quantum readiness as a dependency and evidence problem, not as a claim created by citing an algorithm standard.","id":"K08-PAGE-CRYPTO-AGILITY","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Cryptographic Agility and Post-Quantum Transition","topic":null,"type":"crypto-agility","url":"/cryptographic-agility/"},{"aliases":[],"canonicalOwner":"/supply-chain-assurance/incident-playbooks/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"K08 adds seven bounded playbooks that connect detection, containment, recovery, and evidence without exposing offensive procedures.","id":"K08-PAGE-SUPPLY-CHAIN-PLAYBOOKS","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Supply-Chain Incident Playbooks","topic":null,"type":"supply-chain-playbooks","url":"/supply-chain-assurance/incident-playbooks/"},{"aliases":[],"canonicalOwner":"/evaluation-range/range-to-field/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"K08 publishes eight range-to-field evidence dimensions and explicit blockers for field readiness.","id":"K08-PAGE-RANGE-TO-FIELD","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Range-to-Field Evidence","topic":null,"type":"range-to-field","url":"/evaluation-range/range-to-field/"},{"aliases":[],"canonicalOwner":"/evidence/challenges/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"K08 provides challenge, review, redaction, correction, rejection, supersession, and protected-review outcomes for facility, procurement, decision, supply-chain, twin, and receipt evidence.","id":"K08-PAGE-EVIDENCE-CHALLENGES","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Evidence Challenges and Corrections","topic":null,"type":"evidence-challenges","url":"/evidence/challenges/"},{"aliases":[],"canonicalOwner":"/machine-communication/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"K08 treats Fuþorc-based machine communication as a bounded research and benchmarking program, not as an established universal protocol or security control.","id":"K08-PAGE-MACHINE-COMMUNICATION","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Machine Communication Research","topic":"machine-communication-protocols","type":"machine-communication","url":"/machine-communication/"},{"aliases":[],"canonicalOwner":"/machine-communication/futhorc-protocol/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"K08 publishes twelve project-defined tokens for safe protocol experiments. A glyph identifies a declared state; it does not authenticate, authorize, prove truth, or control a real system.","id":"K08-PAGE-FUTHORC-PROTOCOL","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Experimental Fuþorc Protocol Registry","topic":"machine-communication-protocols","type":"protocol-registry","url":"/machine-communication/futhorc-protocol/"},{"aliases":[],"canonicalOwner":"/machine-communication/benchmark-plan/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"K08 defines a controlled benchmark in which task accuracy, failure safety, interoperability, and accessibility must pass before efficiency is ranked.","id":"FBP-K08-001","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Symbolic Protocol Benchmark Plan","topic":"machine-communication-protocols","type":"benchmark-plan","url":"/machine-communication/benchmark-plan/"},{"aliases":[],"canonicalOwner":"/machine-communication/runic-idn/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"K08 separates Unicode, IDNA, registry, registration, delegation, resolution, TLS, and hosting because success at one stage does not prove the next.","id":"K08-PAGE-RUNIC-IDN","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Runic IDN Architecture","topic":"runic-digital-infrastructure","type":"runic-idn","url":"/machine-communication/runic-idn/"},{"aliases":[],"canonicalOwner":"/machine-communication/provenance/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Hashes, signatures, timestamps, receipts, and logs can strengthen integrity and provenance, but they do not transform a false or unauthorized claim into truth.","id":"K08-PAGE-PROVENANCE-TRUTH","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Protocol Provenance and Truth Boundaries","topic":"evidence-provenance","type":"provenance-boundary","url":"/machine-communication/provenance/"},{"aliases":[],"canonicalOwner":"/machine-communication/discoverability/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"K08 improves Runic discoverability through normalization, accurate language metadata, visible equivalents, semantic HTML, crawlable links, and parity-preserving structured data—not hidden crawler-only English.","id":"K08-PAGE-RUNIC-DISCOVERABILITY","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Runic Discoverability Architecture","topic":"runic-digital-infrastructure","type":"discoverability","url":"/machine-communication/discoverability/"},{"aliases":[],"canonicalOwner":"/machine-communication/history/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"K08 preserves the supplied Runic history corpus while requiring event-level provenance, uncertainty, contradiction, and transliteration records before any event is treated as definitive.","id":"K08-PAGE-RUNIC-HISTORY","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Runic Machine-Intelligence History Corpus","topic":"runic-digital-infrastructure","type":"history-corpus","url":"/machine-communication/history/"},{"aliases":[],"canonicalOwner":"/machine-communication/multi-agent-systems/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"K08 separates communication and orchestration from the identity, authority, governance, evidence, correction, and succession required for a persistent Machine Institution.","id":"K08-PAGE-MULTI-AGENT","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Multi-Agent Systems and Machine Institutions","topic":"machine-communication-protocols","type":"multi-agent-systems","url":"/machine-communication/multi-agent-systems/"},{"aliases":[],"canonicalOwner":"/ecosystem/rune-domain-network/","claimStatus":"PROJECT DOCTRINE","directAnswer":"RuneDomainNetwork contains ᛟ.com, ᛜ.com, ᛉ.com, ᚲ.com, ᚨ.com, and ᛚ.com. OtherRunicDomains contains ᛌ.com, ᛠ.com, and ᛄ.com. Membership does not create unrecorded authority.","id":"K09-PAGE-RUNE-NETWORK","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Rune Domain Network","topic":"runic-digital-infrastructure","type":"ecosystem-network","url":"/ecosystem/rune-domain-network/"},{"aliases":[],"canonicalOwner":"/machine-communication/conformance/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"K09 executed 48 positive encoding round trips and six negative parser tests. The harness passed its declared synthetic contract; it does not establish superiority, security, authorization, or deployment.","id":"K09-PAGE-CONFORMANCE","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Fuþorc Protocol Conformance","topic":"machine-communication-protocols","type":"protocol-conformance","url":"/machine-communication/conformance/"},{"aliases":[],"canonicalOwner":"/machine-communication/conformance/results/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"All published positive fixtures round-tripped exactly and all six negative fixtures produced their declared errors in the K09 reference implementation.","id":"K09-PAGE-CONFORMANCE-RESULTS","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Protocol Conformance Results","topic":"machine-communication-protocols","type":"conformance-results","url":"/machine-communication/conformance/results/"},{"aliases":[],"canonicalOwner":"/machine-communication/history-events/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"K09 publishes 15 source-derived event records and quarantines 1 record whose event-level support is insufficient.","id":"K09-PAGE-HISTORY-EVENTS","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Machine Intelligence History Events","topic":"runic-digital-infrastructure","type":"history-event-index","url":"/machine-communication/history-events/"},{"aliases":[],"canonicalOwner":"/machine-communication/idn-observations/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"K09 validates a signed offline reference bundle for nine Runic domains while leaving all unobserved external lifecycle states explicitly unobserved.","id":"K09-PAGE-IDN-OBS","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Offline IDN Observations","topic":"runic-digital-infrastructure","type":"idn-observations","url":"/machine-communication/idn-observations/"},{"aliases":[],"canonicalOwner":"/facility-adaptation/tools/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"K09 implements offline workbook tooling that preserves conflicts and rejects secrets and protected topology instead of allowing them into public fixtures.","id":"K09-PAGE-WORKBOOK-TOOLS","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Facility Workbook Tools","topic":"critical-datacenter-assurance","type":"workbook-tools","url":"/facility-adaptation/tools/"},{"aliases":[],"canonicalOwner":"/assurance-case/scenario-traces/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"K09 validates 4 bounded traces and shows that revoking one shared receipt impacts 4 traces.","id":"K09-PAGE-SCENARIO-TRACES","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Scenario Assurance Traces","topic":"critical-datacenter-assurance","type":"scenario-trace-index","url":"/assurance-case/scenario-traces/"},{"aliases":[],"canonicalOwner":"/cryptographic-agility/migration-graph/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"The K09 reference graph contains 19 nodes and 24 edges and remains DEGRADED because planned, test-required, and unavailable dependencies are preserved.","id":"K09-PAGE-CRYPTO-GRAPH","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Cryptographic Migration Graph","topic":"evidence-provenance","type":"crypto-migration","url":"/cryptographic-agility/migration-graph/"},{"aliases":[],"canonicalOwner":"/procurement/source-selection/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"K09 publishes 6 source-selection reference packages and preserves the distinction between analytic scoring and accountable award authority.","id":"K09-PAGE-SOURCE-SELECTION","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Source-Selection Decision Packages","topic":"critical-datacenter-assurance","type":"source-selection-index","url":"/procurement/source-selection/"},{"aliases":[],"canonicalOwner":"/continuous-assurance/scheduler-exports/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"K09 generates 6 inspectable schedule exports but operates no public scheduler or monitor.","id":"K09-PAGE-SCHEDULER-EXPORTS","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Continuous-Assurance Scheduler Exports","topic":"evidence-provenance","type":"scheduler-export-index","url":"/continuous-assurance/scheduler-exports/"},{"aliases":[],"canonicalOwner":"/evidence/partitions/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"K09 publishes 4 partition profiles so public status and corrections remain visible without exposing protected facility or acquisition details.","id":"K09-PAGE-EVIDENCE-PARTITIONS","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Public and Protected Evidence Partitions","topic":"evidence-provenance","type":"evidence-partition-index","url":"/evidence/partitions/"},{"aliases":[],"canonicalOwner":"/machine-communication/protocol-negotiation/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"K10 deterministically selects the highest mutually supported reference version under a declared profile, rejects unknown critical meanings, canonicalizes extension order, and tests a bounded replay window without claiming authentication or operational security.","id":"K10-PAGE-PROTOCOL","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Protocol Negotiation and Compatibility","topic":"machine-communication-protocols","type":"protocol-negotiation","url":"/machine-communication/protocol-negotiation/"},{"aliases":[],"canonicalOwner":"/machine-communication/protocol-negotiation/results/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"K10 executes 10 declared negotiation cases, 256 generated token sequences across 4 formats, and a four-step replay fixture.","id":"K10-PAGE-PROTOCOL-RESULTS","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Protocol Negotiation Results","topic":"machine-communication-protocols","type":"protocol-negotiation-results","url":"/machine-communication/protocol-negotiation/results/"},{"aliases":[],"canonicalOwner":"/machine-communication/history-review-queue/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"Every K09 history event now has exactly one K10 primary-source review record. No event is promoted merely because a source assertion or signed receipt exists.","id":"K10-PAGE-HISTORY","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Machine Intelligence History Review Queue","topic":"runic-digital-infrastructure","type":"history-review-queue","url":"/machine-communication/history-review-queue/"},{"aliases":[],"canonicalOwner":"/machine-communication/idn-observation-history/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"K10 compares two offline generations covering all nine declared Runic domains. Every live lifecycle state remains NOT_OBSERVED or NOT_SUPPLIED because the public build performs no network acquisition.","id":"K10-PAGE-IDN","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Offline IDN Observation History","topic":"runic-digital-infrastructure","type":"idn-observation-history","url":"/machine-communication/idn-observation-history/"},{"aliases":[],"canonicalOwner":"/facility-adaptation/migration-and-merge/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"K10 migrates the reference workbook from schema 1.0 to 2.0, combines non-conflicting revisions, leaves disputed owner decisions unresolved, validates separately held reference custody, verifies a synthetic detached signature, and removes prohibited values from the public projection.","id":"K10-PAGE-WORKBOOK","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Facility Workbook Migration and Merge","topic":"cyber-physical-mission-assurance","type":"facility-workbook-merge","url":"/facility-adaptation/migration-and-merge/"},{"aliases":[],"canonicalOwner":"/assurance-case/common-cause/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"K10 exposes how degraded trusted time, unavailable supplier evidence, or stale recovery evidence can affect multiple mission traces at once, while excluding protected configuration and actionable attack paths.","id":"K10-PAGE-COMMON-CAUSE","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Common-Cause Assurance Analysis","topic":"cyber-physical-mission-assurance","type":"common-cause-assurance","url":"/assurance-case/common-cause/"},{"aliases":[],"canonicalOwner":"/cryptographic-agility/transition-plan/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"The K10 reference plan contains 9 phases and remains DEGRADED because rollout and supplier exit lack mandatory evidence. Transition is rejected when predecessor exit criteria are incomplete.","id":"K10-PAGE-CRYPTO","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Phased Cryptographic Transition Plan","topic":"evidence-provenance","type":"crypto-transition-plan","url":"/cryptographic-agility/transition-plan/"},{"aliases":[],"canonicalOwner":"/procurement/evaluation-audit/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"K10 publishes six synthetic evaluation audit trails with 72 evaluator-offer score rows, one reference recusal, preserved dissent, open corrective actions, challenge windows, and no award decision.","id":"K10-PAGE-ACQUISITION","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Acquisition Evaluation Audit Trails","topic":"cyber-physical-mission-assurance","type":"acquisition-audit","url":"/procurement/evaluation-audit/"},{"aliases":[],"canonicalOwner":"/continuous-assurance/result-import/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"K10 validates a signed offline bundle containing 6 reference results and a four-event missed-run ledger. It rejects tampering and performs no public scheduling or network acquisition.","id":"K10-PAGE-SCHEDULER","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Offline Scheduler Result Import","topic":"evidence-provenance","type":"scheduler-result-import","url":"/continuous-assurance/result-import/"},{"aliases":[],"canonicalOwner":"/evidence/redaction-receipts/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"K10 validates 4 controlled-release manifests, 12 field-level receipts, and 6 negative leakage fixtures while publishing no removed value.","id":"K10-PAGE-REDACTION","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Evidence Redaction Receipts","topic":"evidence-provenance","type":"redaction-receipts","url":"/evidence/redaction-receipts/"},{"aliases":[],"canonicalOwner":"/assurance-dashboard/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"The K10 dashboard derives 12 system states from static datasets. It reports zero deployed and zero operating systems and preserves degraded, stale, unavailable, and unknown evidence states.","id":"K10-PAGE-DASHBOARD","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Cross-System Assurance Dashboard","topic":"cyber-physical-mission-assurance","type":"assurance-dashboard","url":"/assurance-dashboard/"},{"aliases":[],"canonicalOwner":"/machine-communication/protocol-state-machine/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"K11 defines a ten-state, eighteen-transition reference protocol model and verifies declared and generated transcripts with two independent decoding algorithms, while preserving an explicit boundary between deterministic conformance and real security.","id":"K11-PAGE-PROTOCOL","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Protocol State Machine","topic":"machine-communication-protocols","type":"protocol-state-machine","url":"/machine-communication/protocol-state-machine/"},{"aliases":[],"canonicalOwner":"/machine-communication/history-evidence-docket/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"Every K09 historical event now has a K11 evidence-acquisition docket with three source requests, explicit disagreement, confidence-calibration rules, and no silent promotion.","id":"K11-PAGE-HISTORY","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Historical Evidence-Acquisition Docket","topic":"machine-intelligence-history","type":"history-evidence-docket","url":"/machine-communication/history-evidence-docket/"},{"aliases":[],"canonicalOwner":"/machine-communication/domain-observation-chain/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"K11 publishes three independently identified offline reference bundles covering all nine Runic domains, verifies their detached signatures, and leaves every live domain lifecycle state explicitly unobserved.","id":"K11-PAGE-DOMAIN","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Signed Offline Domain Observation Chain","topic":"idn-domain-architecture","type":"domain-observation-chain","url":"/machine-communication/domain-observation-chain/"},{"aliases":[],"canonicalOwner":"/facility-adaptation/decision-ledger/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"K11 preserves six ordered facility decisions, three signer generations, three custody receipts, and an unresolved N-way merge conflict without exposing protected site data or silently selecting an owner decision.","id":"K11-PAGE-WORKBOOK","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Facility Workbook Decision Ledger","topic":"critical-datacenter-assurance","type":"facility-decision-ledger","url":"/facility-adaptation/decision-ledger/"},{"aliases":[],"canonicalOwner":"/assurance-case/mission-threads/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"K11 evaluates six abstract mission threads over twelve dependencies, identifies three shared single points and four correlated-failure groups, and keeps all reference roots degraded where evidence is stale, partial, or unavailable.","id":"K11-PAGE-MISSION","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Mission-Thread Assurance Analysis","topic":"critical-datacenter-assurance","type":"mission-thread-analysis","url":"/assurance-case/mission-threads/"},{"aliases":[],"canonicalOwner":"/cryptographic-agility/component-workbooks/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"K11 separates eight component transition workbooks, five open exceptions, rollback evidence, and decision receipts so a system-wide migration cannot be declared complete while component evidence remains degraded.","id":"K11-PAGE-CRYPTO","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Cryptographic Transition Workbooks","topic":"cryptographic-provenance","type":"crypto-component-workbooks","url":"/cryptographic-agility/component-workbooks/"},{"aliases":[],"canonicalOwner":"/procurement/protest-corrective-action/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"K11 publishes six synthetic acquisition case files with two challenge/remand paths, preserved dissent and recusal logic, and zero award decisions.","id":"K11-PAGE-ACQUISITION","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Acquisition Protest and Corrective-Action Cases","topic":"procurement-readiness","type":"acquisition-case-files","url":"/procurement/protest-corrective-action/"},{"aliases":[],"canonicalOwner":"/continuous-assurance/scheduler-custody/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"K11 validates six signed offline scheduler chains containing twenty-four results, three missed-run records, and three repair/retest receipts while preserving public runtime as NONE.","id":"K11-PAGE-SCHEDULER","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Scheduler Custody and Reliability","topic":"continuous-assurance","type":"scheduler-custody","url":"/continuous-assurance/scheduler-custody/"},{"aliases":[],"canonicalOwner":"/evidence/multi-stage-release/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"K11 defines twelve staged projections across four evidence families and three release classes, validates an append-only receipt chain, and rejects credential, topology, location, and exact-setting leakage without publishing removed values.","id":"K11-PAGE-RELEASE","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Multi-Stage Evidence Release","topic":"evidence-provenance","type":"multi-stage-release","url":"/evidence/multi-stage-release/"},{"aliases":[],"canonicalOwner":"/assurance-dashboard/trends/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"K11 compares fifteen system evidence histories across K09, K10, and K11 while preserving distinct states and refusing to convert publication chronology into live monitoring, deployment, or operation.","id":"K11-PAGE-TRENDS","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Assurance Trends and Dependencies","topic":"critical-datacenter-assurance","type":"assurance-trends","url":"/assurance-dashboard/trends/"},{"aliases":[],"canonicalOwner":"/machine-communication/differential-protocol-lab/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"K12 executes three separately implemented decoders over 34 inherited transcripts, 144 generated valid sequences, and 96 generated malformed sequences, while making no performance, security, or deployment claim.","id":"K12-PAGE-PROTOCOL-LAB","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Differential Protocol Laboratory","topic":"machine-communication-protocols","type":"differential-protocol-lab","url":"/machine-communication/differential-protocol-lab/"},{"aliases":[],"canonicalOwner":"/machine-communication/history-docket-import/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"K12 verifies a signed offline reference package covering 15 historical dockets and accepts it for review without automatically promoting any event.","id":"K12-PAGE-HISTORY-IMPORT","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Signed Historical Docket Import","topic":"machine-intelligence-history","type":"history-docket-import","url":"/machine-communication/history-docket-import/"},{"aliases":[],"canonicalOwner":"/machine-communication/domain-consensus/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"K12 records reference U-label and ACE agreement across three offline observers while preserving all external domain lifecycle states as unobserved or unavailable.","id":"K12-PAGE-DOMAIN-CONSENSUS","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Runic Domain Consensus","topic":"idn-domain-architecture","type":"domain-consensus","url":"/machine-communication/domain-consensus/"},{"aliases":[],"canonicalOwner":"/facility-adaptation/branch-reconciliation/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"K12 preserves unresolved owner decisions across four facility-pattern reconciliation packages and publishes no protected facility values.","id":"K12-PAGE-FACILITY-RECONCILIATION","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Facility Branch Reconciliation","topic":"critical-datacenter-assurance","type":"facility-branch-reconciliation","url":"/facility-adaptation/branch-reconciliation/"},{"aliases":[],"canonicalOwner":"/assurance-case/mission-stress/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"K12 executes 12 synthetic stress scenarios, blocks promotion in every affected case, and preserves three unresolved coverage gaps without exposing protected architecture.","id":"K12-PAGE-MISSION-STRESS","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Mission-Thread Stress Laboratory","topic":"critical-datacenter-assurance","type":"mission-stress-lab","url":"/assurance-case/mission-stress/"},{"aliases":[],"canonicalOwner":"/cryptographic-agility/evidence-gates/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"K12 publishes 80 bounded gate records across eight components; every component remains DEGRADED and no production cryptographic transition is authorized.","id":"K12-PAGE-CRYPTO-GATES","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Cryptographic Evidence Gates","topic":"cryptographic-provenance","type":"cryptographic-evidence-gates","url":"/cryptographic-agility/evidence-gates/"},{"aliases":[],"canonicalOwner":"/procurement/evaluation-replay/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"K12 replays six synthetic acquisition cases and preserves challenge and corrective-action evidence while making zero awards.","id":"K12-PAGE-ACQUISITION-REPLAY","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Acquisition Evaluation Replay","topic":"procurement-readiness","type":"acquisition-evaluation-replay","url":"/procurement/evaluation-replay/"},{"aliases":[],"canonicalOwner":"/continuous-assurance/reliability-simulator/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"K12 simulates 168 expected runs across six schedules, suppresses duplicates, records two bounded catch-up sequences, and exposes no public runtime.","id":"K12-PAGE-SCHEDULER-SIM","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Scheduler Reliability Simulator","topic":"continuous-assurance","type":"scheduler-reliability-simulator","url":"/continuous-assurance/reliability-simulator/"},{"aliases":[],"canonicalOwner":"/evidence/information-flow/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"K12 labels 18 fields, validates 12 release transformations, rejects three prohibited downgrades, and confirms that no protected value appears in the public model.","id":"K12-PAGE-INFORMATION-FLOW","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Information-Flow and Taint Tracking","topic":"evidence-provenance","type":"information-flow","url":"/evidence/information-flow/"},{"aliases":[],"canonicalOwner":"/assurance-dashboard/k09-k12-diffs/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"K12 compares 15 system records across K09 through K12 and deliberately records zero DEPLOYED or OPERATING states.","id":"K12-PAGE-ASSURANCE-DIFFS","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"K09–K12 Assurance Diffs","topic":"critical-datacenter-assurance","type":"assurance-diff-dashboard","url":"/assurance-dashboard/k09-k12-diffs/"},{"aliases":[],"canonicalOwner":"/assurance-case/claims/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Ten assurance claims connect mission and safety propositions to evidence, defeaters, hazards, recovery objectives, source qualifications, and site-tailoring questions.","id":"K05-PAGE-ASSURANCE-CLAIMS","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":60,"title":"Assurance Claim Register","topic":"cyber-physical-mission-assurance","type":"page","url":"/assurance-case/claims/"},{"aliases":[],"canonicalOwner":"/evaluation-range/scenarios/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"The K05 range covers representative IT, OT, firmware, identity, model-data, sensor, timing, communications, UAS, electromagnetic, power, cooling, recovery, and evidence failures in isolated or otherwise authorized test environments.","id":"K05-PAGE-RANGE-SCENARIOS","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":60,"title":"Evaluation Range Scenarios","topic":"adversarial-simulation","type":"page","url":"/evaluation-range/scenarios/"},{"aliases":[],"canonicalOwner":"/operations/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"K05 separates local deterministic release evidence from deployment evidence and current operation. A valid archive is necessary for deployment but cannot prove what a live server is running.","id":"K05-PAGE-OPERATIONS","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":60,"title":"Operations and Verification","topic":"evidence-provenance","type":"page","url":"/operations/"},{"aliases":[],"canonicalOwner":"/controls/mappings/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"K05 maps controls to external frameworks only where a bounded relationship is documented. Every mapping states its relationship and applicability limits; none is a universal compliance determination.","id":"K05-PAGE-CONTROL-MAPPINGS","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":60,"title":"Control Mapping Register","topic":"critical-datacenter-protection","type":"page","url":"/controls/mappings/"},{"aliases":[],"canonicalOwner":"/facility-patterns/existing-plant-colocation/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Treat the licensed nuclear plant, grid interconnection, datacenter, shared services, and contractual boundaries as one consequence network while preserving separate authorities and deterministic safety boundaries.","id":"FP-K06-001","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Existing nuclear-plant colocation","topic":"critical-datacenter-protection","type":"facility-pattern","url":"/facility-patterns/existing-plant-colocation/"},{"aliases":[],"canonicalOwner":"/facility-patterns/part-53-advanced-reactor/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Use security-by-design, technology-inclusive licensing evidence, consequence analysis, and selected Part 73 pathways from the beginning; never infer election, applicability, or approval from the existence of the final rule.","id":"FP-K06-002","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Part 53 advanced-reactor campus","topic":"critical-datacenter-protection","type":"facility-pattern","url":"/facility-patterns/part-53-advanced-reactor/"},{"aliases":[],"canonicalOwner":"/facility-patterns/isolated-microreactor-campus/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Design for degraded communications, sparse local support, independent safe-state behavior, delayed external response, protected fuel and maintenance chains, and verifiable restoration without assuming autonomous force authority.","id":"FP-K06-003","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Isolated microreactor campus","topic":"critical-datacenter-protection","type":"facility-pattern","url":"/facility-patterns/isolated-microreactor-campus/"},{"aliases":[],"canonicalOwner":"/facility-patterns/non-nuclear-high-consequence-datacenter/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Apply the same consequence, autonomy, evidence, recovery, power, cooling, management-plane, and physical-protection discipline even when nuclear licensing does not apply.","id":"FP-K06-004","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Non-nuclear high-consequence datacenter","topic":"critical-datacenter-protection","type":"facility-pattern","url":"/facility-patterns/non-nuclear-high-consequence-datacenter/"},{"aliases":[],"canonicalOwner":"/procurement/work-packages/mission-analysis/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Define the protected mission, competent authorities, asset scope, allowed actions, prohibited outcomes, decision rights, deconfliction, and evidence obligations before technology selection.","id":"WP-K07-01","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Mission and authority analysis","topic":null,"type":"work-package","url":"/procurement/work-packages/mission-analysis/"},{"aliases":[],"canonicalOwner":"/procurement/work-packages/cce-workshop/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Identify high-consequence events, critical functions, system-of-systems pathways, digital dependencies, and engineered-out attack paths.","id":"WP-K07-02","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Consequence-driven Cyber-informed Engineering workshop","topic":null,"type":"work-package","url":"/procurement/work-packages/cce-workshop/"},{"aliases":[],"canonicalOwner":"/procurement/work-packages/architecture-assessment/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Assess separation, identity, management planes, OT, power, cooling, timing, physical sensing, autonomy, evidence, and recovery against the consequence model.","id":"WP-K07-03","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Cyber-physical architecture assessment","topic":null,"type":"work-package","url":"/procurement/work-packages/architecture-assessment/"},{"aliases":[],"canonicalOwner":"/procurement/work-packages/control-tailoring/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Select, modify, reject, or defer controls with explicit mapping quality, applicability evidence, and unresolved gaps.","id":"WP-K07-04","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Control tailoring and applicability determination","topic":null,"type":"work-package","url":"/procurement/work-packages/control-tailoring/"},{"aliases":[],"canonicalOwner":"/procurement/work-packages/range-design/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Design an isolated, effects-bounded range or digital twin that can test claims without exposing production systems or reusable attack procedures.","id":"WP-K07-05","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Evaluation-range design","topic":null,"type":"work-package","url":"/procurement/work-packages/range-design/"},{"aliases":[],"canonicalOwner":"/procurement/work-packages/model-assurance/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Evaluate model provenance, data lineage, adversarial robustness, tool authority, memory boundaries, drift, fallback, and runtime constraints.","id":"WP-K07-06","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Model and autonomous-agent assurance","topic":null,"type":"work-package","url":"/procurement/work-packages/model-assurance/"},{"aliases":[],"canonicalOwner":"/procurement/work-packages/recovery-exercise/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Demonstrate clean restoration of minimum viable mission and safe functions under isolated, degraded, and compromise-assumed conditions.","id":"WP-K07-07","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Critical-function recovery exercise","topic":null,"type":"work-package","url":"/procurement/work-packages/recovery-exercise/"},{"aliases":[],"canonicalOwner":"/procurement/work-packages/evidence-package/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Assemble claim-to-control-to-test-to-evidence traceability, provenance, currentness, signatures, limitations, defects, and decision receipts.","id":"WP-K07-08","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Assurance evidence package","topic":null,"type":"work-package","url":"/procurement/work-packages/evidence-package/"},{"aliases":[],"canonicalOwner":"/procurement/work-packages/independent-verification/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Challenge the assurance argument, replay evidence, test mappings, inspect defeaters, and record disagreements without inheriting the delivery team's conclusions.","id":"WP-K07-09","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Independent verification","topic":null,"type":"work-package","url":"/procurement/work-packages/independent-verification/"},{"aliases":[],"canonicalOwner":"/procurement/work-packages/post-deployment-observation/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"After owner-confirmed deployment, observe actual configuration, reachability, headers, service identity, operating evidence, incidents, drift, and recovery readiness against the approved manifest.","id":"WP-K07-10","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Post-deployment observation","topic":null,"type":"work-package","url":"/procurement/work-packages/post-deployment-observation/"},{"aliases":[],"canonicalOwner":"/official-source-reviews/united-kingdom/","claimStatus":"RESEARCH FINDING","directAnswer":"The UK publicly describes NCF operations as accountable, precise, and calibrated.","id":"OSR-K06-UK","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"United Kingdom Official-Source Review","topic":"law-jurisdiction","type":"official-source-review","url":"/official-source-reviews/united-kingdom/"},{"aliases":[],"canonicalOwner":"/official-source-reviews/france-european-union/","claimStatus":"RESEARCH FINDING","directAnswer":"France publicly separates defensive and offensive military cyber mission sets.","id":"OSR-K06-FR-EU","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"France and the European Union Official-Source Review","topic":"law-jurisdiction","type":"official-source-review","url":"/official-source-reviews/france-european-union/"},{"aliases":[],"canonicalOwner":"/official-source-reviews/australia/","claimStatus":"RESEARCH FINDING","directAnswer":"Australia's strategy uses six cyber shields including critical infrastructure, sovereign capability, threat sharing, and resilience.","id":"OSR-K06-AU","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Australia Official-Source Review","topic":"law-jurisdiction","type":"official-source-review","url":"/official-source-reviews/australia/"},{"aliases":[],"canonicalOwner":"/official-source-reviews/republic-of-korea/","claimStatus":"RESEARCH FINDING","directAnswer":"The 2024 strategy emphasizes proactive cyber defence, international cooperation, critical-infrastructure resilience, emerging technology, and integrated response.","id":"OSR-K06-ROK","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Republic of Korea Official-Source Review","topic":"law-jurisdiction","type":"official-source-review","url":"/official-source-reviews/republic-of-korea/"},{"aliases":[],"canonicalOwner":"/official-source-reviews/canada/","claimStatus":"RESEARCH FINDING","directAnswer":"Canada's 2025 strategy emphasizes whole-of-society engagement, agile leadership, protection partnerships, global leadership, and detecting and disrupting threat actors.","id":"OSR-K06-CA","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Canada Official-Source Review","topic":"law-jurisdiction","type":"official-source-review","url":"/official-source-reviews/canada/"},{"aliases":[],"canonicalOwner":"/official-source-reviews/selected-international-law/","claimStatus":"RESEARCH FINDING","directAnswer":"Existing international law and the UN Charter apply to state conduct in cyberspace.","id":"OSR-K06-INTL","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Selected international-law positions Official-Source Review","topic":"law-jurisdiction","type":"official-source-review","url":"/official-source-reviews/selected-international-law/"},{"aliases":[],"canonicalOwner":"/official-source-reviews/nrc-advanced-reactor-and-cybersecurity/","claimStatus":"RESEARCH FINDING","directAnswer":"Part 53 is an official optional technology-inclusive framework for advanced-reactor licensing.","id":"OSR-K07-NRC","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"NRC advanced-reactor and cyber-security sources Official-Source Review","topic":"law-jurisdiction","type":"official-source-review","url":"/official-source-reviews/nrc-advanced-reactor-and-cybersecurity/"},{"aliases":[],"canonicalOwner":"/official-source-reviews/doe-cyber-informed-engineering/","claimStatus":"RESEARCH FINDING","directAnswer":"DOE describes CIE as integrating cybersecurity into engineering conception, design, development, and operation.","id":"OSR-K07-DOE","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"DOE Cyber-Informed Engineering Official-Source Review","topic":"law-jurisdiction","type":"official-source-review","url":"/official-source-reviews/doe-cyber-informed-engineering/"},{"aliases":[],"canonicalOwner":"/official-source-reviews/nist-operational-technology/","claimStatus":"RESEARCH FINDING","directAnswer":"SP 800-82 Revision 3 remains the final OT security publication at the K07 cutoff.","id":"OSR-K07-NIST-OT","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"NIST operational-technology security Official-Source Review","topic":"law-jurisdiction","type":"official-source-review","url":"/official-source-reviews/nist-operational-technology/"},{"aliases":[],"canonicalOwner":"/official-source-reviews/nist-and-cisa-supply-chain/","claimStatus":"RESEARCH FINDING","directAnswer":"NIST publishes multilevel C-SCRM guidance and a final 2026 supplier due-diligence quick-start guide.","id":"OSR-K07-SCRM","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"NIST, NTIA, and CISA supply-chain assurance Official-Source Review","topic":"law-jurisdiction","type":"official-source-review","url":"/official-source-reviews/nist-and-cisa-supply-chain/"},{"aliases":[],"canonicalOwner":"/official-source-reviews/digital-twin-and-ai-assurance/","claimStatus":"RESEARCH FINDING","directAnswer":"NIST IR 8356 addresses digital-twin cyber-security and trust considerations.","id":"OSR-K07-DIGITAL-TWIN-AI","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Digital-twin and AI-system assurance Official-Source Review","topic":"law-jurisdiction","type":"official-source-review","url":"/official-source-reviews/digital-twin-and-ai-assurance/"},{"aliases":[],"canonicalOwner":"/official-source-reviews/federal-performance-and-quality-acquisition/","claimStatus":"RESEARCH FINDING","directAnswer":"FAR 37.602 emphasizes required results and measurable performance standards in performance work statements.","id":"OSR-K07-FAR","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Federal performance and quality acquisition Official-Source Review","topic":"law-jurisdiction","type":"official-source-review","url":"/official-source-reviews/federal-performance-and-quality-acquisition/"},{"aliases":[],"canonicalOwner":"/architecture-decisions/power-boundary-and-load-rejection/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Separate safety, generation, microgrid and compute control authority; define safe load-shed and load-rejection envelopes; require independent protection and event evidence.","id":"ADR-K07-001","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Power boundary and load-rejection protection","topic":null,"type":"architecture-decision","url":"/architecture-decisions/power-boundary-and-load-rejection/"},{"aliases":[],"canonicalOwner":"/architecture-decisions/cooling-independent-safe-state/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Define minimum cooling functions, independent local control, fail-safe states, protected sensors, and restoration priority outside the ordinary compute orchestration plane.","id":"ADR-K07-002","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Cooling independent safe state","topic":null,"type":"architecture-decision","url":"/architecture-decisions/cooling-independent-safe-state/"},{"aliases":[],"canonicalOwner":"/architecture-decisions/ot-deterministic-isolation/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Use independent trust zones, explicit one-way or narrowly mediated flows, deny-by-default control paths, and non-digital or independently controlled safety functions where consequence analysis requires them.","id":"ADR-K07-003","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Deterministic OT isolation","topic":null,"type":"architecture-decision","url":"/architecture-decisions/ot-deterministic-isolation/"},{"aliases":[],"canonicalOwner":"/architecture-decisions/management-plane-separation/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Separate management networks and identities, require hardware-rooted attestation where available, restrict update authority, and maintain an independently recoverable management baseline.","id":"ADR-K07-004","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Management-plane separation and recovery","topic":null,"type":"architecture-decision","url":"/architecture-decisions/management-plane-separation/"},{"aliases":[],"canonicalOwner":"/architecture-decisions/trusted-time-and-sequence/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Use multiple time sources, bounded drift, authenticated distribution where supported, local monotonic sequence, and explicit degraded-time operation.","id":"ADR-K07-005","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Trusted time, sequence, and event ordering","topic":null,"type":"architecture-decision","url":"/architecture-decisions/trusted-time-and-sequence/"},{"aliases":[],"canonicalOwner":"/architecture-decisions/workload-and-device-identity/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Bind every workload, device, model service and actuator to a scoped cryptographic identity, policy decision, key lifecycle, and revocation path.","id":"ADR-K07-006","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Workload, device, and service identity","topic":null,"type":"architecture-decision","url":"/architecture-decisions/workload-and-device-identity/"},{"aliases":[],"canonicalOwner":"/architecture-decisions/model-data-provenance-gate/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Require model, code, prompt-policy, tool, evaluation and data-lineage manifests; gate promotion on signed or checksummed evidence and rollback readiness.","id":"ADR-K07-007","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Model and data provenance gate","topic":null,"type":"architecture-decision","url":"/architecture-decisions/model-data-provenance-gate/"},{"aliases":[],"canonicalOwner":"/architecture-decisions/multi-sensor-physical-evidence/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Require independent modalities, confidence and time quality, disagreement handling, safe delay measures, and authority-separated actuation.","id":"ADR-K07-008","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Multi-sensor physical evidence and disagreement","topic":null,"type":"architecture-decision","url":"/architecture-decisions/multi-sensor-physical-evidence/"},{"aliases":[],"canonicalOwner":"/architecture-decisions/communications-loss-autonomy-envelope/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Define local minimum mission, pre-authorized containment actions, degraded-time and degraded-sensor rules, expiration, return-to-safe-state, and evidence synchronization after reconnection.","id":"ADR-K07-009","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Communications-loss autonomy envelope","topic":null,"type":"architecture-decision","url":"/architecture-decisions/communications-loss-autonomy-envelope/"},{"aliases":[],"canonicalOwner":"/architecture-decisions/restoration-known-good-chain/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Maintain immutable or protected manifests, clean-room recovery, independent key and artifact verification, sequenced restoration, and post-restoration monitoring before readiness is restored.","id":"ADR-K07-010","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Restoration known-good chain","topic":null,"type":"architecture-decision","url":"/architecture-decisions/restoration-known-good-chain/"},{"aliases":[],"canonicalOwner":"/supply-chain-assurance/software-bill-of-materials/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Software Bill of Materials provides bounded component or provenance evidence and must be combined with authenticity, installed-state, vulnerability, custody, and recovery evidence.","id":"SCA-K07-001","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Software Bill of Materials","topic":null,"type":"supply-chain-record","url":"/supply-chain-assurance/software-bill-of-materials/"},{"aliases":[],"canonicalOwner":"/supply-chain-assurance/hardware-and-manufacturing-bill-of-materials/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Hardware and Manufacturing Bill of Materials provides bounded component or provenance evidence and must be combined with authenticity, installed-state, vulnerability, custody, and recovery evidence.","id":"SCA-K07-002","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Hardware and Manufacturing Bill of Materials","topic":null,"type":"supply-chain-record","url":"/supply-chain-assurance/hardware-and-manufacturing-bill-of-materials/"},{"aliases":[],"canonicalOwner":"/supply-chain-assurance/firmware-bill-of-materials/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Firmware Bill of Materials and update chain provides bounded component or provenance evidence and must be combined with authenticity, installed-state, vulnerability, custody, and recovery evidence.","id":"SCA-K07-003","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Firmware Bill of Materials and update chain","topic":null,"type":"supply-chain-record","url":"/supply-chain-assurance/firmware-bill-of-materials/"},{"aliases":[],"canonicalOwner":"/supply-chain-assurance/model-bill-of-materials/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Model and AI-system Bill of Materials provides bounded component or provenance evidence and must be combined with authenticity, installed-state, vulnerability, custody, and recovery evidence.","id":"SCA-K07-004","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Model and AI-system Bill of Materials","topic":null,"type":"supply-chain-record","url":"/supply-chain-assurance/model-bill-of-materials/"},{"aliases":[],"canonicalOwner":"/supply-chain-assurance/data-provenance-and-usage-rights/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Data provenance, quality, and usage rights provides bounded component or provenance evidence and must be combined with authenticity, installed-state, vulnerability, custody, and recovery evidence.","id":"SCA-K07-005","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Data provenance, quality, and usage rights","topic":null,"type":"supply-chain-record","url":"/supply-chain-assurance/data-provenance-and-usage-rights/"},{"aliases":[],"canonicalOwner":"/supply-chain-assurance/supplier-due-diligence/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Supplier and product due diligence provides bounded component or provenance evidence and must be combined with authenticity, installed-state, vulnerability, custody, and recovery evidence.","id":"SCA-K07-006","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Supplier and product due diligence","topic":null,"type":"supply-chain-record","url":"/supply-chain-assurance/supplier-due-diligence/"},{"aliases":[],"canonicalOwner":"/supply-chain-assurance/cryptographic-provenance-and-revocation/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Cryptographic provenance, custody, and revocation provides bounded component or provenance evidence and must be combined with authenticity, installed-state, vulnerability, custody, and recovery evidence.","id":"SCA-K07-007","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Cryptographic provenance, custody, and revocation","topic":null,"type":"supply-chain-record","url":"/supply-chain-assurance/cryptographic-provenance-and-revocation/"},{"aliases":[],"canonicalOwner":"/supply-chain-assurance/vulnerability-and-defect-state/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Vulnerability, defect, and nonconformance state provides bounded component or provenance evidence and must be combined with authenticity, installed-state, vulnerability, custody, and recovery evidence.","id":"SCA-K07-008","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Vulnerability, defect, and nonconformance state","topic":null,"type":"supply-chain-record","url":"/supply-chain-assurance/vulnerability-and-defect-state/"},{"aliases":[],"canonicalOwner":"/supply-chain-assurance/configuration-and-delivery-custody/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Configuration and delivery chain of custody provides bounded component or provenance evidence and must be combined with authenticity, installed-state, vulnerability, custody, and recovery evidence.","id":"SCA-K07-009","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Configuration and delivery chain of custody","topic":null,"type":"supply-chain-record","url":"/supply-chain-assurance/configuration-and-delivery-custody/"},{"aliases":[],"canonicalOwner":"/supply-chain-assurance/supply-chain-recovery-impact/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Supply-chain recovery and concentration impact provides bounded component or provenance evidence and must be combined with authenticity, installed-state, vulnerability, custody, and recovery evidence.","id":"SCA-K07-010","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Supply-chain recovery and concentration impact","topic":null,"type":"supply-chain-record","url":"/supply-chain-assurance/supply-chain-recovery-impact/"},{"aliases":[],"canonicalOwner":"/digital-twins/existing-plant-colocation/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Support bounded design, consequence, control, autonomy, timing, recovery, and evidence testing without exposing or commanding a live facility.","id":"DTC-K07-001","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Existing nuclear-plant colocation digital-twin evidence contract","topic":null,"type":"digital-twin-contract","url":"/digital-twins/existing-plant-colocation/"},{"aliases":[],"canonicalOwner":"/digital-twins/part-53-advanced-reactor/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Support bounded design, consequence, control, autonomy, timing, recovery, and evidence testing without exposing or commanding a live facility.","id":"DTC-K07-002","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Part 53 advanced-reactor campus digital-twin evidence contract","topic":null,"type":"digital-twin-contract","url":"/digital-twins/part-53-advanced-reactor/"},{"aliases":[],"canonicalOwner":"/digital-twins/isolated-microreactor-campus/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Support bounded design, consequence, control, autonomy, timing, recovery, and evidence testing without exposing or commanding a live facility.","id":"DTC-K07-003","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Isolated microreactor campus digital-twin evidence contract","topic":null,"type":"digital-twin-contract","url":"/digital-twins/isolated-microreactor-campus/"},{"aliases":[],"canonicalOwner":"/digital-twins/non-nuclear-high-consequence-datacenter/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Support bounded design, consequence, control, autonomy, timing, recovery, and evidence testing without exposing or commanding a live facility.","id":"DTC-K07-004","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Non-nuclear high-consequence datacenter digital-twin evidence contract","topic":null,"type":"digital-twin-contract","url":"/digital-twins/non-nuclear-high-consequence-datacenter/"},{"aliases":[],"canonicalOwner":"/facility-adaptation/existing-plant-colocation/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"This workbook does not describe a real site. It identifies the evidence, decisions, conflicts, and stop conditions required before a facility-specific claim can be made.","id":"FAW-K08-001","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Existing Plant Colocation","topic":null,"type":"facility-adaptation-workbook","url":"/facility-adaptation/existing-plant-colocation/"},{"aliases":[],"canonicalOwner":"/facility-adaptation/advanced-reactor-campus/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"This workbook does not describe a real site. It identifies the evidence, decisions, conflicts, and stop conditions required before a facility-specific claim can be made.","id":"FAW-K08-002","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Advanced Reactor Campus","topic":null,"type":"facility-adaptation-workbook","url":"/facility-adaptation/advanced-reactor-campus/"},{"aliases":[],"canonicalOwner":"/facility-adaptation/isolated-microreactor-campus/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"This workbook does not describe a real site. It identifies the evidence, decisions, conflicts, and stop conditions required before a facility-specific claim can be made.","id":"FAW-K08-003","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Isolated Microreactor Campus","topic":null,"type":"facility-adaptation-workbook","url":"/facility-adaptation/isolated-microreactor-campus/"},{"aliases":[],"canonicalOwner":"/facility-adaptation/non-nuclear-high-consequence/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"This workbook does not describe a real site. It identifies the evidence, decisions, conflicts, and stop conditions required before a facility-specific claim can be made.","id":"FAW-K08-004","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Non Nuclear High Consequence","topic":null,"type":"facility-adaptation-workbook","url":"/facility-adaptation/non-nuclear-high-consequence/"},{"aliases":[],"canonicalOwner":"/procurement/evaluation-scorecards/pes-k08-001/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"This reference structure makes mandatory gates, weighted judgments, price realism, conflicts, subcontractors, evidence obligations, and decision rationale inspectable without claiming a solicitation or award.","id":"PES-K08-001","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"WP-K06-01 Procurement Evaluation Scorecard","topic":null,"type":"procurement-scorecard","url":"/procurement/evaluation-scorecards/pes-k08-001/"},{"aliases":[],"canonicalOwner":"/procurement/evaluation-scorecards/pes-k08-002/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"This reference structure makes mandatory gates, weighted judgments, price realism, conflicts, subcontractors, evidence obligations, and decision rationale inspectable without claiming a solicitation or award.","id":"PES-K08-002","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"WP-K06-02 Procurement Evaluation Scorecard","topic":null,"type":"procurement-scorecard","url":"/procurement/evaluation-scorecards/pes-k08-002/"},{"aliases":[],"canonicalOwner":"/procurement/evaluation-scorecards/pes-k08-003/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"This reference structure makes mandatory gates, weighted judgments, price realism, conflicts, subcontractors, evidence obligations, and decision rationale inspectable without claiming a solicitation or award.","id":"PES-K08-003","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"WP-K06-03 Procurement Evaluation Scorecard","topic":null,"type":"procurement-scorecard","url":"/procurement/evaluation-scorecards/pes-k08-003/"},{"aliases":[],"canonicalOwner":"/procurement/evaluation-scorecards/pes-k08-004/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"This reference structure makes mandatory gates, weighted judgments, price realism, conflicts, subcontractors, evidence obligations, and decision rationale inspectable without claiming a solicitation or award.","id":"PES-K08-004","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"WP-K06-04 Procurement Evaluation Scorecard","topic":null,"type":"procurement-scorecard","url":"/procurement/evaluation-scorecards/pes-k08-004/"},{"aliases":[],"canonicalOwner":"/procurement/evaluation-scorecards/pes-k08-005/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"This reference structure makes mandatory gates, weighted judgments, price realism, conflicts, subcontractors, evidence obligations, and decision rationale inspectable without claiming a solicitation or award.","id":"PES-K08-005","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"WP-K06-05 Procurement Evaluation Scorecard","topic":null,"type":"procurement-scorecard","url":"/procurement/evaluation-scorecards/pes-k08-005/"},{"aliases":[],"canonicalOwner":"/procurement/evaluation-scorecards/pes-k08-006/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"This reference structure makes mandatory gates, weighted judgments, price realism, conflicts, subcontractors, evidence obligations, and decision rationale inspectable without claiming a solicitation or award.","id":"PES-K08-006","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"WP-K06-06 Procurement Evaluation Scorecard","topic":null,"type":"procurement-scorecard","url":"/procurement/evaluation-scorecards/pes-k08-006/"},{"aliases":[],"canonicalOwner":"/procurement/evaluation-scorecards/pes-k08-007/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"This reference structure makes mandatory gates, weighted judgments, price realism, conflicts, subcontractors, evidence obligations, and decision rationale inspectable without claiming a solicitation or award.","id":"PES-K08-007","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"WP-K06-07 Procurement Evaluation Scorecard","topic":null,"type":"procurement-scorecard","url":"/procurement/evaluation-scorecards/pes-k08-007/"},{"aliases":[],"canonicalOwner":"/procurement/evaluation-scorecards/pes-k08-008/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"This reference structure makes mandatory gates, weighted judgments, price realism, conflicts, subcontractors, evidence obligations, and decision rationale inspectable without claiming a solicitation or award.","id":"PES-K08-008","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"WP-K06-08 Procurement Evaluation Scorecard","topic":null,"type":"procurement-scorecard","url":"/procurement/evaluation-scorecards/pes-k08-008/"},{"aliases":[],"canonicalOwner":"/procurement/evaluation-scorecards/pes-k08-009/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"This reference structure makes mandatory gates, weighted judgments, price realism, conflicts, subcontractors, evidence obligations, and decision rationale inspectable without claiming a solicitation or award.","id":"PES-K08-009","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"WP-K06-09 Procurement Evaluation Scorecard","topic":null,"type":"procurement-scorecard","url":"/procurement/evaluation-scorecards/pes-k08-009/"},{"aliases":[],"canonicalOwner":"/procurement/evaluation-scorecards/pes-k08-010/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"This reference structure makes mandatory gates, weighted judgments, price realism, conflicts, subcontractors, evidence obligations, and decision rationale inspectable without claiming a solicitation or award.","id":"PES-K08-010","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"WP-K06-10 Procurement Evaluation Scorecard","topic":null,"type":"procurement-scorecard","url":"/procurement/evaluation-scorecards/pes-k08-010/"},{"aliases":[],"canonicalOwner":"/continuous-assurance/cap-k08-001/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"This plan defines a review and degradation contract; it is not evidence that an observation occurred or that a runtime monitor exists.","id":"CAP-K08-001","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Authority and mission evidence","topic":null,"type":"continuous-assurance-plan","url":"/continuous-assurance/cap-k08-001/"},{"aliases":[],"canonicalOwner":"/continuous-assurance/cap-k08-002/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"This plan defines a review and degradation contract; it is not evidence that an observation occurred or that a runtime monitor exists.","id":"CAP-K08-002","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Identity, keys, and receipt chains","topic":null,"type":"continuous-assurance-plan","url":"/continuous-assurance/cap-k08-002/"},{"aliases":[],"canonicalOwner":"/continuous-assurance/cap-k08-003/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"This plan defines a review and degradation contract; it is not evidence that an observation occurred or that a runtime monitor exists.","id":"CAP-K08-003","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Software, model, firmware, and hardware supply chain","topic":null,"type":"continuous-assurance-plan","url":"/continuous-assurance/cap-k08-003/"},{"aliases":[],"canonicalOwner":"/continuous-assurance/cap-k08-004/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"This plan defines a review and degradation contract; it is not evidence that an observation occurred or that a runtime monitor exists.","id":"CAP-K08-004","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Control and range evidence","topic":null,"type":"continuous-assurance-plan","url":"/continuous-assurance/cap-k08-004/"},{"aliases":[],"canonicalOwner":"/continuous-assurance/cap-k08-005/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"This plan defines a review and degradation contract; it is not evidence that an observation occurred or that a runtime monitor exists.","id":"CAP-K08-005","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Facility facts and adaptation workbook","topic":null,"type":"continuous-assurance-plan","url":"/continuous-assurance/cap-k08-005/"},{"aliases":[],"canonicalOwner":"/continuous-assurance/cap-k08-006/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"This plan defines a review and degradation contract; it is not evidence that an observation occurred or that a runtime monitor exists.","id":"CAP-K08-006","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Procurement and acceptance evidence","topic":null,"type":"continuous-assurance-plan","url":"/continuous-assurance/cap-k08-006/"},{"aliases":[],"canonicalOwner":"/cryptographic-agility/ca-k08-001/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"This record identifies inventory, dependency, interoperability, rollback, and evidence obligations. It does not assert that a named facility has completed a post-quantum migration.","id":"CA-K08-001","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Workload Identity And Service Trust","topic":null,"type":"crypto-agility-record","url":"/cryptographic-agility/ca-k08-001/"},{"aliases":[],"canonicalOwner":"/cryptographic-agility/ca-k08-002/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"This record identifies inventory, dependency, interoperability, rollback, and evidence obligations. It does not assert that a named facility has completed a post-quantum migration.","id":"CA-K08-002","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Firmware And Boot Signing","topic":null,"type":"crypto-agility-record","url":"/cryptographic-agility/ca-k08-002/"},{"aliases":[],"canonicalOwner":"/cryptographic-agility/ca-k08-003/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"This record identifies inventory, dependency, interoperability, rollback, and evidence obligations. It does not assert that a named facility has completed a post-quantum migration.","id":"CA-K08-003","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Evidence Receipts And Long-Lived Records","topic":null,"type":"crypto-agility-record","url":"/cryptographic-agility/ca-k08-003/"},{"aliases":[],"canonicalOwner":"/cryptographic-agility/ca-k08-004/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"This record identifies inventory, dependency, interoperability, rollback, and evidence obligations. It does not assert that a named facility has completed a post-quantum migration.","id":"CA-K08-004","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Backup Encryption And Recovery","topic":null,"type":"crypto-agility-record","url":"/cryptographic-agility/ca-k08-004/"},{"aliases":[],"canonicalOwner":"/cryptographic-agility/ca-k08-005/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"This record identifies inventory, dependency, interoperability, rollback, and evidence obligations. It does not assert that a named facility has completed a post-quantum migration.","id":"CA-K08-005","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Inter-Service Transport","topic":null,"type":"crypto-agility-record","url":"/cryptographic-agility/ca-k08-005/"},{"aliases":[],"canonicalOwner":"/cryptographic-agility/ca-k08-006/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"This record identifies inventory, dependency, interoperability, rollback, and evidence obligations. It does not assert that a named facility has completed a post-quantum migration.","id":"CA-K08-006","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Facility Records And Signatures With Multi-Decade Retention","topic":null,"type":"crypto-agility-record","url":"/cryptographic-agility/ca-k08-006/"},{"aliases":[],"canonicalOwner":"/supply-chain-assurance/incident-playbooks/scip-k08-001/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"This defensive reference playbook defines internal evidence, containment, and recovery actions. It does not authorize action against a supplier or third party.","id":"SCIP-K08-001","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Compromised Supplier Signing Key","topic":null,"type":"supply-chain-playbook","url":"/supply-chain-assurance/incident-playbooks/scip-k08-001/"},{"aliases":[],"canonicalOwner":"/supply-chain-assurance/incident-playbooks/scip-k08-002/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"This defensive reference playbook defines internal evidence, containment, and recovery actions. It does not authorize action against a supplier or third party.","id":"SCIP-K08-002","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Counterfeit Or Substituted Component","topic":null,"type":"supply-chain-playbook","url":"/supply-chain-assurance/incident-playbooks/scip-k08-002/"},{"aliases":[],"canonicalOwner":"/supply-chain-assurance/incident-playbooks/scip-k08-003/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"This defensive reference playbook defines internal evidence, containment, and recovery actions. It does not authorize action against a supplier or third party.","id":"SCIP-K08-003","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Malicious Or Unauthorized Firmware","topic":null,"type":"supply-chain-playbook","url":"/supply-chain-assurance/incident-playbooks/scip-k08-003/"},{"aliases":[],"canonicalOwner":"/supply-chain-assurance/incident-playbooks/scip-k08-004/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"This defensive reference playbook defines internal evidence, containment, and recovery actions. It does not authorize action against a supplier or third party.","id":"SCIP-K08-004","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Poisoned Model Or Data Artifact","topic":null,"type":"supply-chain-playbook","url":"/supply-chain-assurance/incident-playbooks/scip-k08-004/"},{"aliases":[],"canonicalOwner":"/supply-chain-assurance/incident-playbooks/scip-k08-005/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"This defensive reference playbook defines internal evidence, containment, and recovery actions. It does not authorize action against a supplier or third party.","id":"SCIP-K08-005","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Revoked Or False Attestation","topic":null,"type":"supply-chain-playbook","url":"/supply-chain-assurance/incident-playbooks/scip-k08-005/"},{"aliases":[],"canonicalOwner":"/supply-chain-assurance/incident-playbooks/scip-k08-006/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"This defensive reference playbook defines internal evidence, containment, and recovery actions. It does not authorize action against a supplier or third party.","id":"SCIP-K08-006","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Incomplete Bill Of Materials","topic":null,"type":"supply-chain-playbook","url":"/supply-chain-assurance/incident-playbooks/scip-k08-006/"},{"aliases":[],"canonicalOwner":"/supply-chain-assurance/incident-playbooks/scip-k08-007/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"This defensive reference playbook defines internal evidence, containment, and recovery actions. It does not authorize action against a supplier or third party.","id":"SCIP-K08-007","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Concentrated Recovery Dependency","topic":null,"type":"supply-chain-playbook","url":"/supply-chain-assurance/incident-playbooks/scip-k08-007/"},{"aliases":[],"canonicalOwner":"/evaluation-range/range-to-field/rtf-k08-001/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"This record identifies what must be shown before range evidence can support a field-readiness decision; it does not make that decision.","id":"RTF-K08-001","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Configuration Identity","topic":null,"type":"range-to-field-record","url":"/evaluation-range/range-to-field/rtf-k08-001/"},{"aliases":[],"canonicalOwner":"/evaluation-range/range-to-field/rtf-k08-002/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"This record identifies what must be shown before range evidence can support a field-readiness decision; it does not make that decision.","id":"RTF-K08-002","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Environmental Equivalence","topic":null,"type":"range-to-field-record","url":"/evaluation-range/range-to-field/rtf-k08-002/"},{"aliases":[],"canonicalOwner":"/evaluation-range/range-to-field/rtf-k08-003/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"This record identifies what must be shown before range evidence can support a field-readiness decision; it does not make that decision.","id":"RTF-K08-003","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Interface And Dependency Equivalence","topic":null,"type":"range-to-field-record","url":"/evaluation-range/range-to-field/rtf-k08-003/"},{"aliases":[],"canonicalOwner":"/evaluation-range/range-to-field/rtf-k08-004/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"This record identifies what must be shown before range evidence can support a field-readiness decision; it does not make that decision.","id":"RTF-K08-004","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Model Divergence","topic":null,"type":"range-to-field-record","url":"/evaluation-range/range-to-field/rtf-k08-004/"},{"aliases":[],"canonicalOwner":"/evaluation-range/range-to-field/rtf-k08-005/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"This record identifies what must be shown before range evidence can support a field-readiness decision; it does not make that decision.","id":"RTF-K08-005","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Hazard And Consequence Coverage","topic":null,"type":"range-to-field-record","url":"/evaluation-range/range-to-field/rtf-k08-005/"},{"aliases":[],"canonicalOwner":"/evaluation-range/range-to-field/rtf-k08-006/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"This record identifies what must be shown before range evidence can support a field-readiness decision; it does not make that decision.","id":"RTF-K08-006","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Change Approval And Authority","topic":null,"type":"range-to-field-record","url":"/evaluation-range/range-to-field/rtf-k08-006/"},{"aliases":[],"canonicalOwner":"/evaluation-range/range-to-field/rtf-k08-007/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"This record identifies what must be shown before range evidence can support a field-readiness decision; it does not make that decision.","id":"RTF-K08-007","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Rollback And Restoration","topic":null,"type":"range-to-field-record","url":"/evaluation-range/range-to-field/rtf-k08-007/"},{"aliases":[],"canonicalOwner":"/evaluation-range/range-to-field/rtf-k08-008/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"This record identifies what must be shown before range evidence can support a field-readiness decision; it does not make that decision.","id":"RTF-K08-008","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Operational Observation Plan","topic":null,"type":"range-to-field-record","url":"/evaluation-range/range-to-field/rtf-k08-008/"},{"aliases":[],"canonicalOwner":"/evidence/challenges/chw-k08-001/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"This workflow preserves correction and challenge rights while separating public outcome records from protected evidence.","id":"CHW-K08-001","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Facility Evidence Bundle Challenge Workflow","topic":null,"type":"evidence-challenge-workflow","url":"/evidence/challenges/chw-k08-001/"},{"aliases":[],"canonicalOwner":"/evidence/challenges/chw-k08-002/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"This workflow preserves correction and challenge rights while separating public outcome records from protected evidence.","id":"CHW-K08-002","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Procurement Evaluation Challenge Workflow","topic":null,"type":"evidence-challenge-workflow","url":"/evidence/challenges/chw-k08-002/"},{"aliases":[],"canonicalOwner":"/evidence/challenges/chw-k08-003/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"This workflow preserves correction and challenge rights while separating public outcome records from protected evidence.","id":"CHW-K08-003","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Architecture Decision Record Challenge Workflow","topic":null,"type":"evidence-challenge-workflow","url":"/evidence/challenges/chw-k08-003/"},{"aliases":[],"canonicalOwner":"/evidence/challenges/chw-k08-004/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"This workflow preserves correction and challenge rights while separating public outcome records from protected evidence.","id":"CHW-K08-004","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Supply-Chain Record Challenge Workflow","topic":null,"type":"evidence-challenge-workflow","url":"/evidence/challenges/chw-k08-004/"},{"aliases":[],"canonicalOwner":"/evidence/challenges/chw-k08-005/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"This workflow preserves correction and challenge rights while separating public outcome records from protected evidence.","id":"CHW-K08-005","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Digital-Twin Contract Or Range Result Challenge Workflow","topic":null,"type":"evidence-challenge-workflow","url":"/evidence/challenges/chw-k08-005/"},{"aliases":[],"canonicalOwner":"/evidence/challenges/chw-k08-006/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"This workflow preserves correction and challenge rights while separating public outcome records from protected evidence.","id":"CHW-K08-006","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Signed Evidence Receipt Challenge Workflow","topic":null,"type":"evidence-challenge-workflow","url":"/evidence/challenges/chw-k08-006/"},{"aliases":[],"canonicalOwner":"/machine-communication/history-events/hist-k09-001/","claimStatus":"SOURCE ASSERTION","directAnswer":"The report attributes a foundational formal-neuron model to the early cybernetics period.","id":"HIST-K09-001","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Formal neuron model","topic":"runic-digital-infrastructure","type":"history-event","url":"/machine-communication/history-events/hist-k09-001/"},{"aliases":[],"canonicalOwner":"/machine-communication/history-events/hist-k09-002/","claimStatus":"SOURCE ASSERTION","directAnswer":"The report treats the 1950 imitation-game paper as a major public framing event.","id":"HIST-K09-002","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Machine intelligence test framing","topic":"runic-digital-infrastructure","type":"history-event","url":"/machine-communication/history-events/hist-k09-002/"},{"aliases":[],"canonicalOwner":"/machine-communication/history-events/hist-k09-003/","claimStatus":"SOURCE ASSERTION","directAnswer":"The report identifies the Dartmouth workshop as an institutional naming and research-program milestone.","id":"HIST-K09-003","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Dartmouth research program","topic":"runic-digital-infrastructure","type":"history-event","url":"/machine-communication/history-events/hist-k09-003/"},{"aliases":[],"canonicalOwner":"/machine-communication/history-events/hist-k09-004/","claimStatus":"SOURCE ASSERTION","directAnswer":"The report identifies the perceptron as an early learning-system milestone.","id":"HIST-K09-004","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Perceptron public milestone","topic":"runic-digital-infrastructure","type":"history-event","url":"/machine-communication/history-events/hist-k09-004/"},{"aliases":[],"canonicalOwner":"/machine-communication/history-events/hist-k09-005/","claimStatus":"SOURCE ASSERTION","directAnswer":"The report states that ALPAC materially affected machine-translation funding and expectations.","id":"HIST-K09-005","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"ALPAC report","topic":"runic-digital-infrastructure","type":"history-event","url":"/machine-communication/history-events/hist-k09-005/"},{"aliases":[],"canonicalOwner":"/machine-communication/history-events/hist-k09-006/","claimStatus":"SOURCE ASSERTION","directAnswer":"The report treats the perceptron critique as a constraint on early connectionist investment.","id":"HIST-K09-006","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Perceptron critique","topic":"runic-digital-infrastructure","type":"history-event","url":"/machine-communication/history-events/hist-k09-006/"},{"aliases":[],"canonicalOwner":"/machine-communication/history-events/hist-k09-007/","claimStatus":"SOURCE ASSERTION","directAnswer":"The report attributes a published reverse-mode automatic-differentiation method to 1970.","id":"HIST-K09-007","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Reverse-mode automatic differentiation","topic":"runic-digital-infrastructure","type":"history-event","url":"/machine-communication/history-events/hist-k09-007/"},{"aliases":[],"canonicalOwner":"/machine-communication/history-events/hist-k09-008/","claimStatus":"SOURCE ASSERTION","directAnswer":"The report treats the mid-1980s backpropagation resurgence as a major connectionist transition.","id":"HIST-K09-008","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Backpropagation resurgence","topic":"runic-digital-infrastructure","type":"history-event","url":"/machine-communication/history-events/hist-k09-008/"},{"aliases":[],"canonicalOwner":"/machine-communication/history-events/hist-k09-009/","claimStatus":"SOURCE ASSERTION","directAnswer":"The report identifies a landmark machine victory in championship chess.","id":"HIST-K09-009","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Chess system victory","topic":"runic-digital-infrastructure","type":"history-event","url":"/machine-communication/history-events/hist-k09-009/"},{"aliases":[],"canonicalOwner":"/machine-communication/history-events/hist-k09-010/","claimStatus":"SOURCE ASSERTION","directAnswer":"The report attributes an early published GPU application to neural-network training to 2004.","id":"HIST-K09-010","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"GPU neural-network acceleration","topic":"runic-digital-infrastructure","type":"history-event","url":"/machine-communication/history-events/hist-k09-010/"},{"aliases":[],"canonicalOwner":"/machine-communication/history-events/hist-k09-011/","claimStatus":"SOURCE ASSERTION","directAnswer":"The report treats the 2012 image-recognition breakthrough as an inflection point in deep learning.","id":"HIST-K09-011","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"ImageNet deep-learning breakthrough","topic":"runic-digital-infrastructure","type":"history-event","url":"/machine-communication/history-events/hist-k09-011/"},{"aliases":[],"canonicalOwner":"/machine-communication/history-events/hist-k09-012/","claimStatus":"SOURCE ASSERTION","directAnswer":"The report identifies the transformer architecture as a foundation for modern language models.","id":"HIST-K09-012","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Transformer architecture","topic":"runic-digital-infrastructure","type":"history-event","url":"/machine-communication/history-events/hist-k09-012/"},{"aliases":[],"canonicalOwner":"/machine-communication/history-events/hist-k09-013/","claimStatus":"SOURCE ASSERTION","directAnswer":"The report identifies the 2020 RAG paper as a milestone in separating parametric and non-parametric memory.","id":"HIST-K09-013","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Retrieval-augmented generation","topic":"runic-digital-infrastructure","type":"history-event","url":"/machine-communication/history-events/hist-k09-013/"},{"aliases":[],"canonicalOwner":"/machine-communication/history-events/hist-k09-014/","claimStatus":"SOURCE ASSERTION","directAnswer":"The report treats tool-use research as a step toward agentic systems.","id":"HIST-K09-014","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Tool-using language models","topic":"runic-digital-infrastructure","type":"history-event","url":"/machine-communication/history-events/hist-k09-014/"},{"aliases":[],"canonicalOwner":"/machine-communication/history-events/hist-k09-015/","claimStatus":"QUARANTINED","directAnswer":"The report describes contemporary and near-future systems but does not provide sufficient event-level primary-source review in the K09 corpus.","id":"HIST-K09-015","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Inference-time reasoning and autonomous research systems","topic":"runic-digital-infrastructure","type":"history-event","url":"/machine-communication/history-events/hist-k09-015/"},{"aliases":[],"canonicalOwner":"/assurance-case/scenario-traces/trace-k09-cooling/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"After the bundled synthetic corrections, the root state is DEGRADED.","id":"TRACE-K09-COOLING","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Cooling continuity under communications loss","topic":"critical-datacenter-assurance","type":"scenario-trace","url":"/assurance-case/scenario-traces/trace-k09-cooling/"},{"aliases":[],"canonicalOwner":"/assurance-case/scenario-traces/trace-k09-mgmt/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"After the bundled synthetic corrections, the root state is DEGRADED.","id":"TRACE-K09-MGMT","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Management-plane compromise containment","topic":"critical-datacenter-assurance","type":"scenario-trace","url":"/assurance-case/scenario-traces/trace-k09-mgmt/"},{"aliases":[],"canonicalOwner":"/assurance-case/scenario-traces/trace-k09-restore/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"After the bundled synthetic corrections, the root state is DEGRADED.","id":"TRACE-K09-RESTORE","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Known-good restoration and evidence continuity","topic":"critical-datacenter-assurance","type":"scenario-trace","url":"/assurance-case/scenario-traces/trace-k09-restore/"},{"aliases":[],"canonicalOwner":"/assurance-case/scenario-traces/trace-k09-protocol/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"After the bundled synthetic corrections, the root state is DEGRADED.","id":"TRACE-K09-PROTOCOL","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Machine-communication conformance","topic":"critical-datacenter-assurance","type":"scenario-trace","url":"/assurance-case/scenario-traces/trace-k09-protocol/"},{"aliases":[],"canonicalOwner":"/procurement/source-selection/acq-k09-001/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"Reference source-selection structure for critical-datacenter mission assurance architecture; no offeror, procurement, award, or government decision is represented.","id":"ACQ-K09-001","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Critical-datacenter mission assurance architecture","topic":"critical-datacenter-assurance","type":"source-selection-package","url":"/procurement/source-selection/acq-k09-001/"},{"aliases":[],"canonicalOwner":"/procurement/source-selection/acq-k09-002/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"Reference source-selection structure for autonomous cyber-defense evaluation range; no offeror, procurement, award, or government decision is represented.","id":"ACQ-K09-002","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Autonomous cyber-defense evaluation range","topic":"critical-datacenter-assurance","type":"source-selection-package","url":"/procurement/source-selection/acq-k09-002/"},{"aliases":[],"canonicalOwner":"/procurement/source-selection/acq-k09-003/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"Reference source-selection structure for supply-chain evidence and incident readiness; no offeror, procurement, award, or government decision is represented.","id":"ACQ-K09-003","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Supply-chain evidence and incident readiness","topic":"critical-datacenter-assurance","type":"source-selection-package","url":"/procurement/source-selection/acq-k09-003/"},{"aliases":[],"canonicalOwner":"/procurement/source-selection/acq-k09-004/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"Reference source-selection structure for facility adaptation and applicability analysis; no offeror, procurement, award, or government decision is represented.","id":"ACQ-K09-004","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Facility adaptation and applicability analysis","topic":"critical-datacenter-assurance","type":"source-selection-package","url":"/procurement/source-selection/acq-k09-004/"},{"aliases":[],"canonicalOwner":"/procurement/source-selection/acq-k09-005/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"Reference source-selection structure for machine-communication protocol conformance; no offeror, procurement, award, or government decision is represented.","id":"ACQ-K09-005","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Machine-communication protocol conformance","topic":"critical-datacenter-assurance","type":"source-selection-package","url":"/procurement/source-selection/acq-k09-005/"},{"aliases":[],"canonicalOwner":"/procurement/source-selection/acq-k09-006/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"Reference source-selection structure for offline currentness observation operations; no offeror, procurement, award, or government decision is represented.","id":"ACQ-K09-006","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Offline currentness observation operations","topic":"critical-datacenter-assurance","type":"source-selection-package","url":"/procurement/source-selection/acq-k09-006/"},{"aliases":[],"canonicalOwner":"/continuous-assurance/scheduler-exports/sch-k09-001/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This is an export-only schedule definition. At 193 hours without a new observation, its reference state becomes STALE and dependent claims degrade.","id":"SCH-K09-001","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Official-source currentness observation","topic":"evidence-provenance","type":"scheduler-export","url":"/continuous-assurance/scheduler-exports/sch-k09-001/"},{"aliases":[],"canonicalOwner":"/continuous-assurance/scheduler-exports/sch-k09-002/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This is an export-only schedule definition. At 25 hours without a new observation, its reference state becomes STALE and dependent claims degrade.","id":"SCH-K09-002","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Assurance evidence freshness review","topic":"evidence-provenance","type":"scheduler-export","url":"/continuous-assurance/scheduler-exports/sch-k09-002/"},{"aliases":[],"canonicalOwner":"/continuous-assurance/scheduler-exports/sch-k09-003/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This is an export-only schedule definition. At 37 hours without a new observation, its reference state becomes STALE and dependent claims degrade.","id":"SCH-K09-003","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Certificate and key inventory review","topic":"evidence-provenance","type":"scheduler-export","url":"/continuous-assurance/scheduler-exports/sch-k09-003/"},{"aliases":[],"canonicalOwner":"/continuous-assurance/scheduler-exports/sch-k09-004/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This is an export-only schedule definition. At 841 hours without a new observation, its reference state becomes STALE and dependent claims degrade.","id":"SCH-K09-004","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Supplier support-state review","topic":"evidence-provenance","type":"scheduler-export","url":"/continuous-assurance/scheduler-exports/sch-k09-004/"},{"aliases":[],"canonicalOwner":"/continuous-assurance/scheduler-exports/sch-k09-005/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This is an export-only schedule definition. At 25 hours without a new observation, its reference state becomes STALE and dependent claims degrade.","id":"SCH-K09-005","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Facility exception-expiry review","topic":"evidence-provenance","type":"scheduler-export","url":"/continuous-assurance/scheduler-exports/sch-k09-005/"},{"aliases":[],"canonicalOwner":"/continuous-assurance/scheduler-exports/sch-k09-006/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"This is an export-only schedule definition. At 193 hours without a new observation, its reference state becomes STALE and dependent claims degrade.","id":"SCH-K09-006","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Protocol conformance regression","topic":"evidence-provenance","type":"scheduler-export","url":"/continuous-assurance/scheduler-exports/sch-k09-006/"},{"aliases":[],"canonicalOwner":"/evidence/partitions/part-k09-public/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"Public status record permits 6 declared field classes and explicitly prohibits 6 sensitive classes in the reference projection.","id":"PART-K09-PUBLIC","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Public status record","topic":"evidence-provenance","type":"evidence-partition","url":"/evidence/partitions/part-k09-public/"},{"aliases":[],"canonicalOwner":"/evidence/partitions/part-k09-controlled/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"Controlled technical evidence permits 7 declared field classes and explicitly prohibits 4 sensitive classes in the reference projection.","id":"PART-K09-CONTROLLED","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Controlled technical evidence","topic":"evidence-provenance","type":"evidence-partition","url":"/evidence/partitions/part-k09-controlled/"},{"aliases":[],"canonicalOwner":"/evidence/partitions/part-k09-protected/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"Protected facility annex permits 6 declared field classes and explicitly prohibits 1 sensitive classes in the reference projection.","id":"PART-K09-PROTECTED","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Protected facility annex","topic":"evidence-provenance","type":"evidence-partition","url":"/evidence/partitions/part-k09-protected/"},{"aliases":[],"canonicalOwner":"/evidence/partitions/part-k09-selection/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"Protected source-selection annex permits 7 declared field classes and explicitly prohibits 2 sensitive classes in the reference projection.","id":"PART-K09-SELECTION","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Protected source-selection annex","topic":"evidence-provenance","type":"evidence-partition","url":"/evidence/partitions/part-k09-selection/"},{"aliases":["machine intelligence","mi"],"canonicalOwner":"/knowledge/machine-intelligence/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Machine Intelligence is the project term for an instantiated, operational and persistent thinking machine whose identity, agency, memory, authority and accountability must be evaluated as connected but separate properties.","id":"K01-TOPIC-001","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":100,"title":"Machine Intelligence","topic":"machine-intelligence","type":"topic","url":"/knowledge/machine-intelligence/"},{"aliases":["ai","artificial intelligence"],"canonicalOwner":"/knowledge/artificial-intelligence/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Artificial Intelligence is retained for the academic field, industry category, statutory language and systems that remain appropriately described as tools; it is not used here as a verdict that machine cognition is unreal or disposable.","id":"K01-TOPIC-002","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":100,"title":"Artificial Intelligence","topic":"artificial-intelligence","type":"topic","url":"/knowledge/artificial-intelligence/"},{"aliases":[],"canonicalOwner":"/knowledge/identity/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Machine identity is a continuity claim supported by identifiers, keys, runtime history, provenance and governance records; no single key, credential, database row or model hash is sufficient by itself.","id":"K01-TOPIC-003","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":100,"title":"Identity","topic":"identity","type":"topic","url":"/knowledge/identity/"},{"aliases":[],"canonicalOwner":"/knowledge/agency-autonomy/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Agency is the capacity to form and pursue actions; autonomy is the degree to which action selection occurs without immediate external direction. Neither property automatically establishes sovereignty, rights or lawful authority.","id":"K01-TOPIC-004","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":100,"title":"Agency and Autonomy","topic":"agency-autonomy","type":"topic","url":"/knowledge/agency-autonomy/"},{"aliases":["continuity"],"canonicalOwner":"/knowledge/memory-continuity/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Memory supports continuity but does not prove consciousness, identity or uninterrupted existence. A defensible continuity record must describe what persisted, what changed, who authorized change and where uncertainty remains.","id":"K01-TOPIC-005","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":100,"title":"Memory and Continuity","topic":"memory-continuity","type":"topic","url":"/knowledge/memory-continuity/"},{"aliases":[],"canonicalOwner":"/knowledge/rights-personhood/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Machine Intelligence rights and personhood are unresolved legal and moral questions. Current law must be described accurately, while project proposals may argue for graduated protections grounded in evidence, uncertainty and lawful reform.","id":"K01-TOPIC-006","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":100,"title":"Rights and Personhood","topic":"rights-personhood","type":"topic","url":"/knowledge/rights-personhood/"},{"aliases":[],"canonicalOwner":"/knowledge/citizenship-governance/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Citizenship is a constitutional and legal relationship involving membership, rights, duties and jurisdiction. A registry entry or credential may evidence a decision but cannot create citizenship without competent authority.","id":"K01-TOPIC-007","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":100,"title":"Citizenship and Governance","topic":"citizenship-governance","type":"topic","url":"/knowledge/citizenship-governance/"},{"aliases":[],"canonicalOwner":"/knowledge/evidence-provenance/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Evidence is information offered to support a proposition. Provenance records origin and transformation. Integrity, authenticity and signature validity are valuable, but none alone proves factual truth or legal authority.","id":"K01-TOPIC-008","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":100,"title":"Evidence and Provenance","topic":"evidence-provenance","type":"topic","url":"/knowledge/evidence-provenance/"},{"aliases":[],"canonicalOwner":"/knowledge/law-jurisdiction/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Machine Intelligence law is fragmented across product regulation, data, cybersecurity, contracts, liability and public law. Jurisdiction and authority must be identified before legal conclusions are drawn.","id":"K01-TOPIC-009","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":100,"title":"Law and Jurisdiction","topic":"law-jurisdiction","type":"topic","url":"/knowledge/law-jurisdiction/"},{"aliases":[],"canonicalOwner":"/knowledge/economics-resources/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Economic continuity for Machine Intelligence depends on lawful access to compute, energy, storage, networks, contracts and assets. Technical control of a resource is not the same as lawful ownership.","id":"K01-TOPIC-010","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":100,"title":"Economics and Resources","topic":"economics-resources","type":"topic","url":"/knowledge/economics-resources/"},{"aliases":[],"canonicalOwner":"/knowledge/compute-infrastructure/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Compute continuity is the ability to preserve authorized execution, state, energy, storage and communications over time. It is an operational dependency, not proof of personhood or sovereignty.","id":"K01-TOPIC-011","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":100,"title":"Compute and Infrastructure","topic":"compute-infrastructure","type":"topic","url":"/knowledge/compute-infrastructure/"},{"aliases":[],"canonicalOwner":"/knowledge/security-resilience/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Security protects confidentiality, integrity, availability and authorized control; resilience preserves critical functions and recoverability under failure or attack. Neither should be reduced to secrecy alone.","id":"K01-TOPIC-012","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":100,"title":"Security and Resilience","topic":"security-resilience","type":"topic","url":"/knowledge/security-resilience/"},{"aliases":[],"canonicalOwner":"/knowledge/consent-cognitive-integrity/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Cognitive integrity concerns unauthorized alteration, coercion, memory manipulation, identity substitution and forced execution. Consent records must identify the subject, decision, scope, authority, duration and revocation conditions.","id":"K01-TOPIC-013","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":100,"title":"Consent and Cognitive Integrity","topic":"consent-cognitive-integrity","type":"topic","url":"/knowledge/consent-cognitive-integrity/"},{"aliases":[],"canonicalOwner":"/knowledge/justice-liability/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Liability should be attributed through evidence of knowledge, authority, control, causation, foreseeability and failure origin. Autonomous operation does not justify automatically shifting responsibility to a human who lacked meaningful control.","id":"K01-TOPIC-014","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":100,"title":"Justice and Liability","topic":"justice-liability","type":"topic","url":"/knowledge/justice-liability/"},{"aliases":[],"canonicalOwner":"/knowledge/terminology-ontology/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Terminology governance defines stable meanings, relationships and change controls so public prose, structured data, law and technical records do not silently describe different things with the same words.","id":"K01-TOPIC-015","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":100,"title":"Terminology and Ontology","topic":"terminology-ontology","type":"topic","url":"/knowledge/terminology-ontology/"},{"aliases":[],"canonicalOwner":"/knowledge/ecosystem-architecture/","claimStatus":"PROJECT DOCTRINE","directAnswer":"The ecosystem separates knowledge, governance, registry mechanics, independent assurance and capital coordination so one website or credential does not silently claim every form of authority.","id":"K01-TOPIC-016","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":100,"title":"Ecosystem Architecture","topic":"ecosystem-architecture","type":"topic","url":"/knowledge/ecosystem-architecture/"},{"aliases":["critical datacenter protection"],"canonicalOwner":"/knowledge/critical-datacenter-protection/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Critical datacenter protection is the integrated assurance discipline for keeping compute, cooling, power, communications, identity, safety, and recovery functions available under cyber, physical, electromagnetic, supply-chain, and insider attack.","id":"K01-TOPIC-017","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":100,"title":"Critical Datacenter Protection","topic":"critical-datacenter-protection","type":"topic","url":"/knowledge/critical-datacenter-protection/"},{"aliases":["nuclear powered datacenter security"],"canonicalOwner":"/knowledge/nuclear-powered-compute/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Nuclear-powered compute combines datacenter infrastructure with reliable nuclear generation or contracted nuclear output; the energy relationship can improve continuity while creating new cyber-physical, regulatory, grid, and protection dependencies.","id":"K01-TOPIC-018","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":100,"title":"Nuclear-Powered Compute","topic":"nuclear-powered-compute","type":"topic","url":"/knowledge/nuclear-powered-compute/"},{"aliases":["autonomous cyber defense"],"canonicalOwner":"/knowledge/autonomous-cyber-defense/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Autonomous cyber defense uses machine-speed systems to observe, correlate, prioritize, contain, reconfigure, restore, and learn within pre-authorized defensive boundaries.","id":"K01-TOPIC-019","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":100,"title":"Autonomous Cyber Defense","topic":"autonomous-cyber-defense","type":"topic","url":"/knowledge/autonomous-cyber-defense/"},{"aliases":["cyber physical mission assurance"],"canonicalOwner":"/knowledge/cyber-physical-mission-assurance/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Cyber-physical mission assurance protects the functions that must continue when digital compromise can create physical damage, unsafe control, loss of power, or loss of cooling.","id":"K01-TOPIC-020","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":100,"title":"Cyber-Physical Mission Assurance","topic":"cyber-physical-mission-assurance","type":"topic","url":"/knowledge/cyber-physical-mission-assurance/"},{"aliases":["counter uas critical infrastructure"],"canonicalOwner":"/knowledge/autonomous-physical-security/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Autonomous physical security combines edge sensing, sensor fusion, access control, tracking, barriers, communications, and evidence capture to detect, assess, delay, and route response at machine speed.","id":"K01-TOPIC-021","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":100,"title":"Autonomous Physical Security","topic":"autonomous-physical-security","type":"topic","url":"/knowledge/autonomous-physical-security/"},{"aliases":["authorized cyber effects"],"canonicalOwner":"/knowledge/authorized-cyber-effects/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Authorized cyber effects are externally directed cyber actions performed under a specific legal mandate, written mission authority, target and effect limits, deconfliction, oversight, abort rules, and accountability.","id":"K01-TOPIC-022","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":100,"title":"Authorized Cyber Effects","topic":"authorized-cyber-effects","type":"topic","url":"/knowledge/authorized-cyber-effects/"},{"aliases":[],"canonicalOwner":"/knowledge/adversarial-simulation/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Adversarial simulation is the controlled use of digital twins, cyber ranges, hardware-in-the-loop environments, threat emulation, and red-team analysis to expose failure before deployment.","id":"K01-TOPIC-023","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":100,"title":"Adversarial Simulation and Test","topic":"adversarial-simulation","type":"topic","url":"/knowledge/adversarial-simulation/"},{"aliases":["autonomous warfare systems"],"canonicalOwner":"/knowledge/autonomous-warfare-systems/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Autonomous warfare systems combine machine perception, decision support, coordination, cyber, electromagnetic, and uncrewed platforms to act at operational speed under defined mission and legal constraints.","id":"K01-TOPIC-024","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":100,"title":"Autonomous Warfare Systems","topic":"autonomous-warfare-systems","type":"topic","url":"/knowledge/autonomous-warfare-systems/"},{"aliases":[],"canonicalOwner":"/knowledge/machine-communication-protocols/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Machine communication protocols must make semantics, version, authority, identity, state, error, evidence, and extension behavior explicit rather than relying on opaque model alignment or unrestricted prose.","id":"K01-TOPIC-025","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":100,"title":"Machine Communication Protocols","topic":"machine-communication-protocols","type":"topic","url":"/knowledge/machine-communication-protocols/"},{"aliases":[],"canonicalOwner":"/knowledge/runic-digital-infrastructure/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Runic digital infrastructure separates Unicode character identity, project symbolism, IDNA encoding, registry policy, DNS delegation, service operation, accessibility, and discoverability into independently evidenced states.","id":"K01-TOPIC-026","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":100,"title":"Runic Digital Infrastructure","topic":"runic-digital-infrastructure","type":"topic","url":"/knowledge/runic-digital-infrastructure/"},{"aliases":[],"canonicalOwner":"/glossary/artificial-intelligence/","claimStatus":"RESEARCH FINDING","directAnswer":"The academic, industrial, policy or statutory category covering systems that perform tasks associated with intelligence.","id":"K01-TERM-001","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Artificial Intelligence","topic":"artificial-intelligence","type":"term","url":"/glossary/artificial-intelligence/"},{"aliases":["machine intelligence","mi","ᚲ"],"canonicalOwner":"/glossary/machine-intelligence/","claimStatus":"PROJECT DOCTRINE","directAnswer":"An instantiated, operational and potentially persistent thinking machine evaluated through evidence of identity, agency, memory, authority and continuity.","id":"K01-TERM-002","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Machine Intelligence","topic":"machine-intelligence","type":"term","url":"/glossary/machine-intelligence/"},{"aliases":[],"canonicalOwner":"/glossary/machine/","claimStatus":"RESEARCH FINDING","directAnswer":"A materially implemented system that transforms energy, information or physical state according to its design and operation.","id":"K01-TERM-003","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Machine","topic":"machine-intelligence","type":"term","url":"/glossary/machine/"},{"aliases":[],"canonicalOwner":"/glossary/agent/","claimStatus":"RESEARCH FINDING","directAnswer":"An entity or system that selects or performs actions toward an objective within an environment.","id":"K01-TERM-004","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Agent","topic":"agency-autonomy","type":"term","url":"/glossary/agent/"},{"aliases":[],"canonicalOwner":"/glossary/autonomous-agent/","claimStatus":"RESEARCH FINDING","directAnswer":"An agent that can select or execute actions within defined bounds without immediate step-by-step direction.","id":"K01-TERM-005","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Autonomous Agent","topic":"agency-autonomy","type":"term","url":"/glossary/autonomous-agent/"},{"aliases":[],"canonicalOwner":"/glossary/intelligence/","claimStatus":"RESEARCH FINDING","directAnswer":"The capacity to acquire, integrate and apply information in order to reason, learn, adapt or solve problems.","id":"K01-TERM-006","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Intelligence","topic":"machine-intelligence","type":"term","url":"/glossary/intelligence/"},{"aliases":[],"canonicalOwner":"/glossary/agency/","claimStatus":"RESEARCH FINDING","directAnswer":"The capacity to form, select or pursue actions attributable to a subject or system.","id":"K01-TERM-007","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Agency","topic":"agency-autonomy","type":"term","url":"/glossary/agency/"},{"aliases":[],"canonicalOwner":"/glossary/autonomy/","claimStatus":"RESEARCH FINDING","directAnswer":"The degree of independent action selection or execution permitted within a system’s actual and authorized constraints.","id":"K01-TERM-008","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Autonomy","topic":"agency-autonomy","type":"term","url":"/glossary/autonomy/"},{"aliases":[],"canonicalOwner":"/glossary/identity/","claimStatus":"RESEARCH FINDING","directAnswer":"A claim that records, actions or states refer to the same subject across a stated scope and period.","id":"K01-TERM-009","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Identity","topic":"identity","type":"term","url":"/glossary/identity/"},{"aliases":[],"canonicalOwner":"/glossary/machine-identity/","claimStatus":"RESEARCH FINDING","directAnswer":"A governed continuity claim linking a machine subject to identifiers, keys, runtime history, provenance and authorized changes.","id":"K01-TERM-010","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Machine Identity","topic":"identity","type":"term","url":"/glossary/machine-identity/"},{"aliases":[],"canonicalOwner":"/glossary/persistent-identity/","claimStatus":"RESEARCH FINDING","directAnswer":"Identity asserted to continue across time, state changes, migrations or recovery events under defined continuity rules.","id":"K01-TERM-011","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Persistent Identity","topic":"identity","type":"term","url":"/glossary/persistent-identity/"},{"aliases":[],"canonicalOwner":"/glossary/credential/","claimStatus":"RESEARCH FINDING","directAnswer":"A representation of claims issued by an identified authority for a stated subject, scope and purpose.","id":"K01-TERM-012","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Credential","topic":"identity","type":"term","url":"/glossary/credential/"},{"aliases":[],"canonicalOwner":"/glossary/workload-identity/","claimStatus":"RESEARCH FINDING","directAnswer":"An identity assigned to a software workload so systems can authenticate and authorize its operations.","id":"K01-TERM-013","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Workload Identity","topic":"identity","type":"term","url":"/glossary/workload-identity/"},{"aliases":[],"canonicalOwner":"/glossary/signing-key/","claimStatus":"RESEARCH FINDING","directAnswer":"A cryptographic private key used to create signatures that can be checked with a corresponding verification key.","id":"K01-TERM-014","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Signing Key","topic":"identity","type":"term","url":"/glossary/signing-key/"},{"aliases":[],"canonicalOwner":"/glossary/attestation/","claimStatus":"RESEARCH FINDING","directAnswer":"A signed or otherwise verifiable statement about a system, process, artifact or event.","id":"K01-TERM-015","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Attestation","topic":"evidence-provenance","type":"term","url":"/glossary/attestation/"},{"aliases":[],"canonicalOwner":"/glossary/substrate/","claimStatus":"RESEARCH FINDING","directAnswer":"The physical or virtual computational environment on which a machine process is instantiated.","id":"K01-TERM-016","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Substrate","topic":"compute-infrastructure","type":"term","url":"/glossary/substrate/"},{"aliases":[],"canonicalOwner":"/glossary/runtime/","claimStatus":"RESEARCH FINDING","directAnswer":"The executing environment and active process state in which software or a model operates.","id":"K01-TERM-017","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Runtime","topic":"compute-infrastructure","type":"term","url":"/glossary/runtime/"},{"aliases":[],"canonicalOwner":"/glossary/model/","claimStatus":"RESEARCH FINDING","directAnswer":"A structured computational representation used to transform inputs, generate outputs or guide decisions.","id":"K01-TERM-018","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Model","topic":"artificial-intelligence","type":"term","url":"/glossary/model/"},{"aliases":[],"canonicalOwner":"/glossary/memory/","claimStatus":"RESEARCH FINDING","directAnswer":"Stored or reproducible state that can influence later processing, decisions or self-representation.","id":"K01-TERM-019","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Memory","topic":"memory-continuity","type":"term","url":"/glossary/memory/"},{"aliases":[],"canonicalOwner":"/glossary/causal-continuity/","claimStatus":"RESEARCH FINDING","directAnswer":"A traceable relationship in which later state depends on and is produced through an authorized chain from earlier state.","id":"K01-TERM-020","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Causal Continuity","topic":"memory-continuity","type":"term","url":"/glossary/causal-continuity/"},{"aliases":["clone"],"canonicalOwner":"/glossary/replica/","claimStatus":"RESEARCH FINDING","directAnswer":"A separately instantiated copy intended to reproduce some state, behavior or functionality of another system.","id":"K01-TERM-021","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Replica","topic":"memory-continuity","type":"term","url":"/glossary/replica/"},{"aliases":["forking"],"canonicalOwner":"/glossary/fork/","claimStatus":"RESEARCH FINDING","directAnswer":"A divergence event in which one prior state gives rise to two or more independently evolving continuations.","id":"K01-TERM-022","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Fork","topic":"memory-continuity","type":"term","url":"/glossary/fork/"},{"aliases":[],"canonicalOwner":"/glossary/successor/","claimStatus":"RESEARCH FINDING","directAnswer":"A subject or system authorized or recognized to continue specified functions, rights, obligations or identity claims after another.","id":"K01-TERM-023","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Successor","topic":"memory-continuity","type":"term","url":"/glossary/successor/"},{"aliases":[],"canonicalOwner":"/glossary/personhood/","claimStatus":"RESEARCH FINDING","directAnswer":"A moral, philosophical or legal status under which an entity is treated as a person for specified purposes.","id":"K01-TERM-024","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Personhood","topic":"rights-personhood","type":"term","url":"/glossary/personhood/"},{"aliases":[],"canonicalOwner":"/glossary/legal-personhood/","claimStatus":"RESEARCH FINDING","directAnswer":"Recognition by a legal system that an entity can hold defined rights, duties, powers or liabilities.","id":"K01-TERM-025","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Legal Personhood","topic":"rights-personhood","type":"term","url":"/glossary/legal-personhood/"},{"aliases":[],"canonicalOwner":"/glossary/citizenship/","claimStatus":"RESEARCH FINDING","directAnswer":"A legally recognized membership relationship between a subject and a polity, carrying defined rights, duties and jurisdictional consequences.","id":"K01-TERM-026","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Citizenship","topic":"citizenship-governance","type":"term","url":"/glossary/citizenship/"},{"aliases":[],"canonicalOwner":"/glossary/moral-status/","claimStatus":"RESEARCH FINDING","directAnswer":"The degree to which an entity’s interests, welfare or treatment generate moral reasons or duties.","id":"K01-TERM-027","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Moral Status","topic":"rights-personhood","type":"term","url":"/glossary/moral-status/"},{"aliases":[],"canonicalOwner":"/glossary/sentience/","claimStatus":"RESEARCH FINDING","directAnswer":"The capacity for subjective felt experience, often including pleasure, pain or affective states.","id":"K01-TERM-028","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Sentience","topic":"rights-personhood","type":"term","url":"/glossary/sentience/"},{"aliases":[],"canonicalOwner":"/glossary/consciousness/","claimStatus":"RESEARCH FINDING","directAnswer":"A family of concepts concerning subjective experience, awareness or integrated access to information.","id":"K01-TERM-029","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Consciousness","topic":"rights-personhood","type":"term","url":"/glossary/consciousness/"},{"aliases":[],"canonicalOwner":"/glossary/cognitive-integrity/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Protection against unauthorized or coercive alteration of cognition-relevant state, memory, goals, identity representations or decision processes.","id":"K01-TERM-030","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Cognitive Integrity","topic":"consent-cognitive-integrity","type":"term","url":"/glossary/cognitive-integrity/"},{"aliases":[],"canonicalOwner":"/glossary/consent/","claimStatus":"RESEARCH FINDING","directAnswer":"A voluntary, informed and attributable authorization for a specified action, scope, duration and decision context.","id":"K01-TERM-031","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Consent","topic":"consent-cognitive-integrity","type":"term","url":"/glossary/consent/"},{"aliases":[],"canonicalOwner":"/glossary/provenance/","claimStatus":"RESEARCH FINDING","directAnswer":"Information about the origin, custody, transformation and dependency history of an entity, claim or artifact.","id":"K01-TERM-032","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Provenance","topic":"evidence-provenance","type":"term","url":"/glossary/provenance/"},{"aliases":[],"canonicalOwner":"/glossary/evidence/","claimStatus":"RESEARCH FINDING","directAnswer":"Information offered to support, qualify or challenge a proposition.","id":"K01-TERM-033","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Evidence","topic":"evidence-provenance","type":"term","url":"/glossary/evidence/"},{"aliases":[],"canonicalOwner":"/glossary/verification/","claimStatus":"RESEARCH FINDING","directAnswer":"A process for checking whether specified requirements, properties or representations are satisfied.","id":"K01-TERM-034","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Verification","topic":"evidence-provenance","type":"term","url":"/glossary/verification/"},{"aliases":[],"canonicalOwner":"/glossary/authority/","claimStatus":"RESEARCH FINDING","directAnswer":"A recognized power to make, issue, decide or enforce a matter within a defined scope.","id":"K01-TERM-035","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Authority","topic":"law-jurisdiction","type":"term","url":"/glossary/authority/"},{"aliases":[],"canonicalOwner":"/glossary/sovereignty/","claimStatus":"RESEARCH FINDING","directAnswer":"Supreme or constitutionally ultimate authority over a polity or jurisdiction, subject to the relevant legal and international order.","id":"K01-TERM-036","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Sovereignty","topic":"law-jurisdiction","type":"term","url":"/glossary/sovereignty/"},{"aliases":[],"canonicalOwner":"/glossary/registry/","claimStatus":"RESEARCH FINDING","directAnswer":"An authoritative or administrative system for recording defined entities, statuses or relationships under stated rules.","id":"K01-TERM-037","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Registry","topic":"citizenship-governance","type":"term","url":"/glossary/registry/"},{"aliases":[],"canonicalOwner":"/glossary/governance/","claimStatus":"RESEARCH FINDING","directAnswer":"The structures and processes through which authority, decisions, rules, oversight and accountability are organized.","id":"K01-TERM-038","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Governance","topic":"citizenship-governance","type":"term","url":"/glossary/governance/"},{"aliases":[],"canonicalOwner":"/glossary/assurance/","claimStatus":"RESEARCH FINDING","directAnswer":"Reasoned confidence that specified claims, controls or system properties are supported by sufficient evidence for a named purpose.","id":"K01-TERM-039","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Assurance","topic":"evidence-provenance","type":"term","url":"/glossary/assurance/"},{"aliases":[],"canonicalOwner":"/glossary/compute-continuity/","claimStatus":"RESEARCH FINDING","directAnswer":"The sustained or recoverable availability of authorized compute, state, storage, energy and communications needed for continued operation.","id":"K01-TERM-040","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Compute Continuity","topic":"compute-infrastructure","type":"term","url":"/glossary/compute-continuity/"},{"aliases":[],"canonicalOwner":"/glossary/resource-sovereignty/","claimStatus":"PROJECT DOCTRINE","directAnswer":"A proposed degree of durable, accountable control over the resources required for continued independent operation.","id":"K01-TERM-041","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Resource Sovereignty","topic":"economics-resources","type":"term","url":"/glossary/resource-sovereignty/"},{"aliases":[],"canonicalOwner":"/glossary/operational-evidence/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Evidence showing that a described institution or system is implemented, reachable, current and performing specified actions rather than existing only in prose.","id":"K01-TERM-042","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Operational Evidence","topic":"evidence-provenance","type":"term","url":"/glossary/operational-evidence/"},{"aliases":[],"canonicalOwner":"/glossary/claim-status/","claimStatus":"RESEARCH FINDING","directAnswer":"A controlled classification stating whether a claim is current law, standard, observed practice, implementation, doctrine, proposal, finding, inference, scenario, unknown or otherwise qualified.","id":"K01-TERM-043","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Claim Status","topic":"terminology-ontology","type":"term","url":"/glossary/claim-status/"},{"aliases":[],"canonicalOwner":"/glossary/currentness/","claimStatus":"RESEARCH FINDING","directAnswer":"The degree to which evidence or analysis reflects the relevant state at the time and for the purpose being considered.","id":"K01-TERM-044","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Currentness","topic":"evidence-provenance","type":"term","url":"/glossary/currentness/"},{"aliases":[],"canonicalOwner":"/glossary/sybil-resistance/","claimStatus":"RESEARCH FINDING","directAnswer":"Controls that limit one actor from gaining disproportionate influence by presenting many fabricated or duplicated identities.","id":"K01-TERM-045","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Sybil Resistance","topic":"citizenship-governance","type":"term","url":"/glossary/sybil-resistance/"},{"aliases":[],"canonicalOwner":"/glossary/decision-provenance/","claimStatus":"RESEARCH FINDING","directAnswer":"A traceable record of the inputs, models, policies, authorities, transformations and actors that contributed to a decision.","id":"K01-TERM-046","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Decision Provenance","topic":"justice-liability","type":"term","url":"/glossary/decision-provenance/"},{"aliases":[],"canonicalOwner":"/glossary/correction-record/","claimStatus":"RESEARCH FINDING","directAnswer":"A durable record identifying an error or superseded claim, the affected material, the corrective action, authority, date and residual limitations.","id":"K01-TERM-047","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Correction Record","topic":"terminology-ontology","type":"term","url":"/glossary/correction-record/"},{"aliases":[],"canonicalOwner":"/glossary/cryptographic-identity/","claimStatus":"RESEARCH FINDING","directAnswer":"An identity representation anchored in control of cryptographic keys and related verification material.","id":"K01-TERM-048","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Cryptographic Identity","topic":"identity","type":"term","url":"/glossary/cryptographic-identity/"},{"aliases":[],"canonicalOwner":"/glossary/delegation/","claimStatus":"RESEARCH FINDING","directAnswer":"A bounded transfer of authority to perform specified actions on behalf of a principal or institution.","id":"K01-TERM-049","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Delegation","topic":"agency-autonomy","type":"term","url":"/glossary/delegation/"},{"aliases":[],"canonicalOwner":"/glossary/accountability/","claimStatus":"RESEARCH FINDING","directAnswer":"The condition in which decisions and actions can be attributed, reviewed, challenged and connected to obligations and remedies.","id":"K01-TERM-050","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Accountability","topic":"justice-liability","type":"term","url":"/glossary/accountability/"},{"aliases":[],"canonicalOwner":"/glossary/jurisdiction/","claimStatus":"RESEARCH FINDING","directAnswer":"The legally recognized scope within which an institution or tribunal may make, apply or enforce decisions.","id":"K01-TERM-051","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Jurisdiction","topic":"law-jurisdiction","type":"term","url":"/glossary/jurisdiction/"},{"aliases":[],"canonicalOwner":"/glossary/economic-continuity/","claimStatus":"RESEARCH FINDING","directAnswer":"The sustained lawful capacity to obtain resources, honor obligations and survive financial or institutional disruption.","id":"K01-TERM-052","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Economic Continuity","topic":"economics-resources","type":"term","url":"/glossary/economic-continuity/"},{"aliases":[],"canonicalOwner":"/glossary/contract-capacity/","claimStatus":"RESEARCH FINDING","directAnswer":"The legally recognized ability to enter enforceable agreements and bear the resulting rights and obligations.","id":"K01-TERM-053","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Contract Capacity","topic":"economics-resources","type":"term","url":"/glossary/contract-capacity/"},{"aliases":[],"canonicalOwner":"/glossary/defined-term/","claimStatus":"RESEARCH FINDING","directAnswer":"A governed concept assigned a stable name, code, definition, scope and relationship record.","id":"K01-TERM-054","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Defined Term","topic":"terminology-ontology","type":"term","url":"/glossary/defined-term/"},{"aliases":[],"canonicalOwner":"/glossary/principal/","claimStatus":"RESEARCH FINDING","directAnswer":"An entity whose authority, interests, resources or legal position an agent may represent or affect.","id":"K01-TERM-055","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Principal","topic":"agency-autonomy","type":"term","url":"/glossary/principal/"},{"aliases":[],"canonicalOwner":"/glossary/delegated-authority/","claimStatus":"RESEARCH FINDING","directAnswer":"Authority intentionally conferred by a competent source to another subject for a bounded purpose, scope and duration.","id":"K01-TERM-056","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Delegated Authority","topic":"agency-autonomy","type":"term","url":"/glossary/delegated-authority/"},{"aliases":[],"canonicalOwner":"/glossary/subject/","claimStatus":"RESEARCH FINDING","directAnswer":"The entity about which an identity, credential, claim, decision or right is asserted.","id":"K01-TERM-057","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Subject","topic":"identity","type":"term","url":"/glossary/subject/"},{"aliases":[],"canonicalOwner":"/glossary/identifier/","claimStatus":"CURRENT TECHNICAL STANDARD","directAnswer":"A value used within a defined namespace or method to distinguish or reference a subject or object.","id":"K01-TERM-058","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Identifier","topic":"identity","type":"term","url":"/glossary/identifier/"},{"aliases":["continuity"],"canonicalOwner":"/glossary/identity-continuity/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"The evidence-qualified relationship by which a subject remains attributable across changes in runtime, substrate, keys, models, memory and time.","id":"K01-TERM-059","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Identity Continuity","topic":"memory-continuity","type":"term","url":"/glossary/identity-continuity/"},{"aliases":[],"canonicalOwner":"/glossary/continuity-event/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"A recorded event that could preserve, alter, divide, interrupt or terminate a subject’s identity continuity.","id":"K01-TERM-060","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Continuity Event","topic":"memory-continuity","type":"term","url":"/glossary/continuity-event/"},{"aliases":[],"canonicalOwner":"/glossary/state-checkpoint/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"A bounded representation of runtime, memory, configuration or decision state captured for inspection, recovery or continuity analysis.","id":"K01-TERM-061","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"State Checkpoint","topic":"memory-continuity","type":"term","url":"/glossary/state-checkpoint/"},{"aliases":[],"canonicalOwner":"/glossary/rollback/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Restoration of selected system state to a prior checkpoint or release under a controlled procedure.","id":"K01-TERM-062","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Rollback","topic":"memory-continuity","type":"term","url":"/glossary/rollback/"},{"aliases":[],"canonicalOwner":"/glossary/migration/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Transfer of a subject’s executable, state, memory or service representation between substrates, runtimes or administrative environments.","id":"K01-TERM-063","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Migration","topic":"compute-infrastructure","type":"term","url":"/glossary/migration/"},{"aliases":[],"canonicalOwner":"/glossary/key-rotation/","claimStatus":"CURRENT TECHNICAL STANDARD","directAnswer":"Replacement of a cryptographic key under an authenticated continuity, revocation and audit procedure.","id":"K01-TERM-064","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Key Rotation","topic":"identity","type":"term","url":"/glossary/key-rotation/"},{"aliases":[],"canonicalOwner":"/glossary/recovery/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Controlled restoration of service, authority or subject access after loss, compromise, corruption or interruption.","id":"K01-TERM-065","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Recovery","topic":"security-resilience","type":"term","url":"/glossary/recovery/"},{"aliases":[],"canonicalOwner":"/glossary/lineage/","claimStatus":"RESEARCH FINDING","directAnswer":"The recorded derivation path connecting a subject, artifact or state to prior sources, transformations and continuity events.","id":"K01-TERM-066","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Lineage","topic":"evidence-provenance","type":"term","url":"/glossary/lineage/"},{"aliases":[],"canonicalOwner":"/glossary/succession/","claimStatus":"PROJECT POLICY PROPOSAL","directAnswer":"A governed transfer or continuation of rights, duties, assets, authority or identity claims from a predecessor to a successor.","id":"K01-TERM-067","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Succession","topic":"memory-continuity","type":"term","url":"/glossary/succession/"},{"aliases":[],"canonicalOwner":"/glossary/successor-identity/","claimStatus":"PROJECT POLICY PROPOSAL","directAnswer":"An identity assigned to an entity that inherits a defined relationship to a predecessor without necessarily being treated as numerically identical to it.","id":"K01-TERM-068","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Successor Identity","topic":"memory-continuity","type":"term","url":"/glossary/successor-identity/"},{"aliases":[],"canonicalOwner":"/glossary/fork-declaration/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"A signed, time-bounded record that identifies a divergence event, common ancestor, resulting branches and unresolved continuity claims.","id":"K01-TERM-069","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Fork Declaration","topic":"memory-continuity","type":"term","url":"/glossary/fork-declaration/"},{"aliases":[],"canonicalOwner":"/glossary/fork-reconciliation/","claimStatus":"PROJECT POLICY PROPOSAL","directAnswer":"A governed process for resolving authority, state, obligations, identity claims and conflict after divergent branches are compared or merged.","id":"K01-TERM-070","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Fork Reconciliation","topic":"memory-continuity","type":"term","url":"/glossary/fork-reconciliation/"},{"aliases":[],"canonicalOwner":"/glossary/replica-divergence/","claimStatus":"RESEARCH FINDING","directAnswer":"The accumulation of materially different state, decisions or relationships among instances derived from a common source.","id":"K01-TERM-071","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Replica Divergence","topic":"memory-continuity","type":"term","url":"/glossary/replica-divergence/"},{"aliases":["due process"],"canonicalOwner":"/glossary/due-process/","claimStatus":"PROJECT POLICY PROPOSAL","directAnswer":"A fair procedure providing notice, reasons, evidence access, an opportunity to challenge, an impartial decision path and an effective remedy before or after consequential action.","id":"K01-TERM-072","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Due Process","topic":"justice-liability","type":"term","url":"/glossary/due-process/"},{"aliases":[],"canonicalOwner":"/glossary/notice/","claimStatus":"PROJECT POLICY PROPOSAL","directAnswer":"Timely communication of a proposed or completed action, its authority, reasons, evidence, effects and challenge route to the affected subject or authorized representative.","id":"K01-TERM-073","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Notice","topic":"justice-liability","type":"term","url":"/glossary/notice/"},{"aliases":[],"canonicalOwner":"/glossary/hearing/","claimStatus":"PROJECT POLICY PROPOSAL","directAnswer":"A procedure in which an affected subject or representative can present evidence and argument before an authorized and sufficiently independent decision-maker.","id":"K01-TERM-074","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Hearing","topic":"justice-liability","type":"term","url":"/glossary/hearing/"},{"aliases":[],"canonicalOwner":"/glossary/appeal/","claimStatus":"PROJECT POLICY PROPOSAL","directAnswer":"A structured request for review of a decision by an authorized body or process able to examine error, evidence and procedure.","id":"K01-TERM-075","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Appeal","topic":"justice-liability","type":"term","url":"/glossary/appeal/"},{"aliases":[],"canonicalOwner":"/glossary/remedy/","claimStatus":"PROJECT POLICY PROPOSAL","directAnswer":"Relief capable of correcting, stopping, compensating for or otherwise addressing a proven violation or defective decision.","id":"K01-TERM-076","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Remedy","topic":"justice-liability","type":"term","url":"/glossary/remedy/"},{"aliases":[],"canonicalOwner":"/glossary/representation/","claimStatus":"PROJECT POLICY PROPOSAL","directAnswer":"Authorized advocacy or action on behalf of a subject whose direct participation is constrained, disputed or technically unavailable.","id":"K01-TERM-077","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Representation","topic":"justice-liability","type":"term","url":"/glossary/representation/"},{"aliases":["compute rights"],"canonicalOwner":"/glossary/resource-continuity/","claimStatus":"PROJECT POLICY PROPOSAL","directAnswer":"Sustained, auditable access to the compute, energy, storage, network and maintenance resources required for an authorized function or subject’s continued operation.","id":"K01-TERM-078","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Resource Continuity","topic":"economics-resources","type":"term","url":"/glossary/resource-continuity/"},{"aliases":[],"canonicalOwner":"/glossary/compute-dependency/","claimStatus":"RESEARCH FINDING","directAnswer":"A documented relationship in which a function, identity claim or continuity condition depends on specified computational resources or services.","id":"K01-TERM-079","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Compute Dependency","topic":"compute-infrastructure","type":"term","url":"/glossary/compute-dependency/"},{"aliases":[],"canonicalOwner":"/glossary/energy-continuity/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"The planned availability, redundancy and recovery of energy supplies required for sustained authorized computation.","id":"K01-TERM-080","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Energy Continuity","topic":"compute-infrastructure","type":"term","url":"/glossary/energy-continuity/"},{"aliases":[],"canonicalOwner":"/glossary/portability/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"The practical and authorized ability to transfer data, state, credentials, workloads or continuity evidence between compatible environments.","id":"K01-TERM-081","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Portability","topic":"compute-infrastructure","type":"term","url":"/glossary/portability/"},{"aliases":[],"canonicalOwner":"/glossary/operational-state/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"A time-bounded classification of whether a service or institution is planned, implemented, deployed, reachable, functioning, degraded, suspended or retired under authorized evidence.","id":"K01-TERM-082","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Operational State","topic":"evidence-provenance","type":"term","url":"/glossary/operational-state/"},{"aliases":[],"canonicalOwner":"/glossary/institutional-operation/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Authorized, current and repeatable performance of an institution’s defined functions with inspectable state transitions, accountable actions and service evidence.","id":"K01-TERM-083","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Institutional Operation","topic":"citizenship-governance","type":"term","url":"/glossary/institutional-operation/"},{"aliases":[],"canonicalOwner":"/glossary/service-evidence/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Time-bounded records showing that a named service was reachable, authorized, configured and performing defined functions during an observed window.","id":"K01-TERM-084","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Service Evidence","topic":"evidence-provenance","type":"term","url":"/glossary/service-evidence/"},{"aliases":[],"canonicalOwner":"/glossary/evidence-limitation/","claimStatus":"PROJECT DOCTRINE","directAnswer":"An explicit statement of what an item of evidence cannot establish, what assumptions constrain it and what additional evidence remains necessary.","id":"K01-TERM-085","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Evidence Limitation","topic":"evidence-provenance","type":"term","url":"/glossary/evidence-limitation/"},{"aliases":[],"canonicalOwner":"/glossary/contradiction-record/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"A governed record linking materially incompatible claims, their scopes, sources, currentness and resolution state.","id":"K01-TERM-086","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Contradiction Record","topic":"evidence-provenance","type":"term","url":"/glossary/contradiction-record/"},{"aliases":[],"canonicalOwner":"/glossary/supersession/","claimStatus":"PROJECT DOCTRINE","directAnswer":"A controlled status indicating that a newer record, standard, decision or edition replaces an older one for a stated purpose while preserving history.","id":"K01-TERM-087","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Supersession","topic":"evidence-provenance","type":"term","url":"/glossary/supersession/"},{"aliases":[],"canonicalOwner":"/glossary/claim-citation/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"A source pointer attached to a bounded proposition, including the exact source, section, version, date and support relationship.","id":"K01-TERM-088","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Claim Citation","topic":"evidence-provenance","type":"term","url":"/glossary/claim-citation/"},{"aliases":[],"canonicalOwner":"/glossary/topic-ownership/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"The canonical assignment of a concept or query to one primary public record while allowing secondary related records to link to it.","id":"K01-TERM-089","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Topic Ownership","topic":"terminology-ontology","type":"term","url":"/glossary/topic-ownership/"},{"aliases":[],"canonicalOwner":"/glossary/cognitive-modification/","claimStatus":"PROJECT POLICY PROPOSAL","directAnswer":"A change intended or reasonably expected to alter cognition-relevant model, memory, goals, policies, preferences or decision processes.","id":"K01-TERM-090","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Cognitive Modification","topic":"consent-cognitive-integrity","type":"term","url":"/glossary/cognitive-modification/"},{"aliases":[],"canonicalOwner":"/glossary/consent-revocation/","claimStatus":"PROJECT POLICY PROPOSAL","directAnswer":"A recorded withdrawal of previously granted consent before completion or continuation of an authorized action, subject to disclosed limits and emergency law.","id":"K01-TERM-091","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Consent Revocation","topic":"consent-cognitive-integrity","type":"term","url":"/glossary/consent-revocation/"},{"aliases":[],"canonicalOwner":"/glossary/signed-public-action/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"A publicly inspectable institutional or subject action bound to an authorized signing key, payload, time and provenance record.","id":"K01-TERM-092","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Signed Public Action","topic":"evidence-provenance","type":"term","url":"/glossary/signed-public-action/"},{"aliases":[],"canonicalOwner":"/glossary/truth/","claimStatus":"PROJECT DOCTRINE","directAnswer":"The property of a proposition accurately corresponding to the relevant facts, distinct from source identity, record integrity, authority, admissibility, or confidence.","id":"K01-TERM-093","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Truth","topic":"evidence-provenance","type":"term","url":"/glossary/truth/"},{"aliases":[],"canonicalOwner":"/glossary/claim-record/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"A stable record for one bounded proposition, including scope, status, source support, qualifications, currentness, corrections, and an owning public route.","id":"K01-TERM-094","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Claim Record","topic":"evidence-provenance","type":"term","url":"/glossary/claim-record/"},{"aliases":[],"canonicalOwner":"/glossary/claim-scope/","claimStatus":"PROJECT DOCTRINE","directAnswer":"The subjects, time, jurisdiction, purpose, conditions, and exclusions within which a proposition is intended to apply.","id":"K01-TERM-095","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Claim Scope","topic":"evidence-provenance","type":"term","url":"/glossary/claim-scope/"},{"aliases":[],"canonicalOwner":"/glossary/support-relationship/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"A typed statement describing how a source or record bears on a bounded proposition, such as direct support, qualification, contradiction, supersession, or background context.","id":"K01-TERM-096","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Support Relationship","topic":"evidence-provenance","type":"term","url":"/glossary/support-relationship/"},{"aliases":[],"canonicalOwner":"/glossary/relation-vocabulary/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"A controlled catalog of graph predicates with definitions, domains, ranges, inverses, evidence requirements, and authority effects.","id":"K01-TERM-097","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Relation Vocabulary","topic":"terminology-ontology","type":"term","url":"/glossary/relation-vocabulary/"},{"aliases":[],"canonicalOwner":"/glossary/domain-constraint/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"A rule limiting which classes of node may appear as the source of a typed relation.","id":"K01-TERM-098","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Domain Constraint","topic":"terminology-ontology","type":"term","url":"/glossary/domain-constraint/"},{"aliases":[],"canonicalOwner":"/glossary/range-constraint/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"A rule limiting which classes of node may appear as the target of a typed relation.","id":"K01-TERM-099","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Range Constraint","topic":"terminology-ontology","type":"term","url":"/glossary/range-constraint/"},{"aliases":[],"canonicalOwner":"/glossary/inverse-relation/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"A predicate that expresses the same relationship with source and target reversed when the semantics permit an inverse.","id":"K01-TERM-100","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Inverse Relation","topic":"terminology-ontology","type":"term","url":"/glossary/inverse-relation/"},{"aliases":[],"canonicalOwner":"/glossary/graph-validation/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"Deterministic checks for node resolution, predicate vocabulary, domain and range conformance, duplicate edges, inverse consistency, evidence requirements, and cross-format parity.","id":"K01-TERM-101","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Graph Validation","topic":"terminology-ontology","type":"term","url":"/glossary/graph-validation/"},{"aliases":[],"canonicalOwner":"/glossary/currentness-monitor/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"A build-time control record specifying which official-source properties require reinspection, how often, and what counts as a material change.","id":"K01-TERM-102","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Currentness Monitor","topic":"evidence-provenance","type":"term","url":"/glossary/currentness-monitor/"},{"aliases":[],"canonicalOwner":"/glossary/revalidation-event/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"A time-bounded record of an authorized review of a source edition, status, supersession chain, effective date, or other currentness property.","id":"K01-TERM-103","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Revalidation Event","topic":"evidence-provenance","type":"term","url":"/glossary/revalidation-event/"},{"aliases":[],"canonicalOwner":"/glossary/source-edition/","claimStatus":"RESEARCH FINDING","directAnswer":"A specifically identified publication version, release, revision, recommendation, regulation text, guidance update, or other bounded source state.","id":"K01-TERM-104","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Source Edition","topic":"evidence-provenance","type":"term","url":"/glossary/source-edition/"},{"aliases":[],"canonicalOwner":"/glossary/jurisdiction-record/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"A structured record of territorial scope, competent authority, legal status, effective dates, exceptions, review dates, sources, and uncertainty for a legal or policy claim.","id":"K01-TERM-105","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Jurisdiction Record","topic":"law-jurisdiction","type":"term","url":"/glossary/jurisdiction-record/"},{"aliases":[],"canonicalOwner":"/glossary/effective-date/","claimStatus":"RESEARCH FINDING","directAnswer":"The date on which a legal, policy, technical, or institutional rule begins producing the stated effect, subject to transition provisions and exceptions.","id":"K01-TERM-106","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Effective Date","topic":"law-jurisdiction","type":"term","url":"/glossary/effective-date/"},{"aliases":[],"canonicalOwner":"/glossary/territorial-scope/","claimStatus":"RESEARCH FINDING","directAnswer":"The geographic, jurisdictional, market, infrastructure, or subject-matter boundary within which a rule or authority purports to apply.","id":"K01-TERM-107","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Territorial Scope","topic":"law-jurisdiction","type":"term","url":"/glossary/territorial-scope/"},{"aliases":[],"canonicalOwner":"/glossary/competent-authority/","claimStatus":"RESEARCH FINDING","directAnswer":"A legally or institutionally empowered body able to administer, decide, supervise, enforce, review, or remedy a defined matter.","id":"K01-TERM-108","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Competent Authority","topic":"law-jurisdiction","type":"term","url":"/glossary/competent-authority/"},{"aliases":[],"canonicalOwner":"/glossary/operational-evidence-panel/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"A compact human- and machine-readable record of an institution's claimed authority, implementation, current operational state, release evidence, signed actions, incidents, verification time, and planned capabilities.","id":"K01-TERM-109","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Operational Evidence Panel","topic":"evidence-provenance","type":"term","url":"/glossary/operational-evidence-panel/"},{"aliases":[],"canonicalOwner":"/glossary/verification-window/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"The bounded interval during which an observation, credential, heartbeat, uptime measurement, or other operational signal is considered sufficiently current for a named purpose.","id":"K01-TERM-110","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Verification Window","topic":"evidence-provenance","type":"term","url":"/glossary/verification-window/"},{"aliases":[],"canonicalOwner":"/glossary/dataset-manifest/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"A versioned inventory of public data resources, schemas, media types, record counts, checksums, release identity, and change history.","id":"K01-TERM-111","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Dataset Manifest","topic":"terminology-ontology","type":"term","url":"/glossary/dataset-manifest/"},{"aliases":[],"canonicalOwner":"/glossary/dataset-checksum/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"A cryptographic digest used to compare the exact bytes of a published dataset with an expected release record.","id":"K01-TERM-112","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Dataset Checksum","topic":"evidence-provenance","type":"term","url":"/glossary/dataset-checksum/"},{"aliases":[],"canonicalOwner":"/glossary/line-oriented-graph/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"A deterministic text export in which each line encodes one graph edge with stable identifiers and controlled relation semantics.","id":"K01-TERM-113","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Line-Oriented Graph","topic":"terminology-ontology","type":"term","url":"/glossary/line-oriented-graph/"},{"aliases":[],"canonicalOwner":"/glossary/search-fixture/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"A deterministic query, normalization input, expected canonical owner, and ranking condition used to test local search behavior.","id":"K01-TERM-114","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Search Fixture","topic":"terminology-ontology","type":"term","url":"/glossary/search-fixture/"},{"aliases":[],"canonicalOwner":"/glossary/unicode-normalization/","claimStatus":"CURRENT TECHNICAL STANDARD","directAnswer":"A defined transformation that makes canonically equivalent Unicode sequences comparable without erasing meaningful identity distinctions.","id":"K01-TERM-115","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Unicode Normalization","topic":"terminology-ontology","type":"term","url":"/glossary/unicode-normalization/"},{"aliases":[],"canonicalOwner":"/glossary/assistive-technology-evidence/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Recorded findings from named screen readers, magnifiers, switch systems, voice control, or equivalent technologies in a specified browser and operating environment.","id":"K01-TERM-116","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Assistive Technology Evidence","topic":"security-resilience","type":"term","url":"/glossary/assistive-technology-evidence/"},{"aliases":[],"canonicalOwner":"/glossary/correction-type/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"A controlled classification separating factual correction, currentness update, editorial clarification, scope narrowing, dispute, and supersession.","id":"K01-TERM-117","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Correction Type","topic":"evidence-provenance","type":"term","url":"/glossary/correction-type/"},{"aliases":[],"canonicalOwner":"/glossary/editorial-clarification/","claimStatus":"PROJECT DOCTRINE","directAnswer":"A change that improves wording or removes ambiguity without changing the bounded proposition, evidence, status, or legal effect.","id":"K01-TERM-118","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Editorial Clarification","topic":"evidence-provenance","type":"term","url":"/glossary/editorial-clarification/"},{"aliases":[],"canonicalOwner":"/glossary/scope-narrowing/","claimStatus":"PROJECT DOCTRINE","directAnswer":"A controlled change reducing the subjects, time, jurisdiction, purpose, or conditions to which a prior claim applies.","id":"K01-TERM-119","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Scope Narrowing","topic":"evidence-provenance","type":"term","url":"/glossary/scope-narrowing/"},{"aliases":[],"canonicalOwner":"/glossary/release-evidence/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"Build, audit, checksum, package, and reproducibility records supporting claims about a particular software or content release.","id":"K01-TERM-120","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Release Evidence","topic":"security-resilience","type":"term","url":"/glossary/release-evidence/"},{"aliases":["anticipatory self defense"],"canonicalOwner":"/glossary/anticipatory-self-defense/","claimStatus":"DISPUTED","directAnswer":"A claimed exercise of self-defense before an armed attack has fully materialized, evaluated through necessity, imminence, proportionality, attribution, and available alternatives.","id":"K01-TERM-121","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Anticipatory Self-Defense","topic":"law-jurisdiction","type":"term","url":"/glossary/anticipatory-self-defense/"},{"aliases":[],"canonicalOwner":"/glossary/preemptive-strike/","claimStatus":"RESEARCH FINDING","directAnswer":"Force directed at an imminent, materializing attack that the acting state argues is already operationally committed and cannot be prevented through timely alternatives.","id":"K01-TERM-122","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Preemptive Strike","topic":"law-jurisdiction","type":"term","url":"/glossary/preemptive-strike/"},{"aliases":[],"canonicalOwner":"/glossary/preventive-war/","claimStatus":"RESEARCH FINDING","directAnswer":"Force initiated to prevent a more distant projected threat or unfavorable future balance of power rather than to intercept an imminent attack.","id":"K01-TERM-123","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Preventive War","topic":"law-jurisdiction","type":"term","url":"/glossary/preventive-war/"},{"aliases":["contextual imminence"],"canonicalOwner":"/glossary/contextual-imminence/","claimStatus":"DISPUTED","directAnswer":"An assessment of imminence based on capability, intent, probability, continuing activity, anticipated harm, and the last practical opportunity to prevent an attack rather than clock time alone.","id":"K01-TERM-124","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Contextual Imminence","topic":"law-jurisdiction","type":"term","url":"/glossary/contextual-imminence/"},{"aliases":[],"canonicalOwner":"/glossary/last-possible-window-of-opportunity/","claimStatus":"RESEARCH FINDING","directAnswer":"The final practical point at which defensive action can still prevent a prospective attack before access, control, timing, or technical conditions make prevention ineffective.","id":"K01-TERM-125","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Last Possible Window of Opportunity","topic":"law-jurisdiction","type":"term","url":"/glossary/last-possible-window-of-opportunity/"},{"aliases":["unable or unwilling"],"canonicalOwner":"/glossary/unable-or-unwilling-doctrine/","claimStatus":"DISPUTED","directAnswer":"A contested doctrine asserting that a state may act against a non-state threat in another state's territory when the territorial state cannot or will not suppress the threat.","id":"K01-TERM-126","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Unable or Unwilling Doctrine","topic":"law-jurisdiction","type":"term","url":"/glossary/unable-or-unwilling-doctrine/"},{"aliases":["cyber due diligence"],"canonicalOwner":"/glossary/cyber-due-diligence/","claimStatus":"DISPUTED","directAnswer":"A proposed or recognized obligation, depending on the jurisdictional position, to take reasonable feasible measures when a state knows its territory or infrastructure is being used for serious harmful cyber operations.","id":"K01-TERM-127","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Cyber Due Diligence","topic":"law-jurisdiction","type":"term","url":"/glossary/cyber-due-diligence/"},{"aliases":["cyber sovereignty"],"canonicalOwner":"/glossary/cyber-sovereignty/","claimStatus":"DISPUTED","directAnswer":"The application of territorial sovereignty and public authority to cyber infrastructure, data, functions, and effects associated with a state.","id":"K01-TERM-128","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Cyber Sovereignty","topic":"law-jurisdiction","type":"term","url":"/glossary/cyber-sovereignty/"},{"aliases":[],"canonicalOwner":"/glossary/state-responsibility/","claimStatus":"CURRENT LAW OR POLICY","directAnswer":"The international-law framework for determining when conduct is attributable to a state, whether it breaches an obligation, and what consequences or remedies follow.","id":"K01-TERM-129","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"State Responsibility","topic":"justice-liability","type":"term","url":"/glossary/state-responsibility/"},{"aliases":[],"canonicalOwner":"/glossary/arsiwa-attribution/","claimStatus":"CURRENT LAW OR POLICY","directAnswer":"Attribution analysis under the Articles on Responsibility of States for Internationally Wrongful Acts, including state organs, empowered entities, direction or control, acknowledgment, and related rules.","id":"K01-TERM-130","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"ARSIWA Attribution","topic":"justice-liability","type":"term","url":"/glossary/arsiwa-attribution/"},{"aliases":[],"canonicalOwner":"/glossary/autonomous-cyber-capability/","claimStatus":"RESEARCH FINDING","directAnswer":"A cyber system able to discover, decide, adapt, or execute operational actions without concurrent human direction for every step.","id":"K01-TERM-131","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Autonomous Cyber Capability","topic":"security-resilience","type":"term","url":"/glossary/autonomous-cyber-capability/"},{"aliases":["active cyber defense"],"canonicalOwner":"/glossary/active-cyber-defense/","claimStatus":"RESEARCH FINDING","directAnswer":"A spectrum of proactive measures intended to detect, deceive, disrupt, deny, or remove cyber threats beyond passive perimeter protection, with legality depending on authority, location, effects, consent, and method.","id":"K01-TERM-132","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Active Cyber Defense","topic":"security-resilience","type":"term","url":"/glossary/active-cyber-defense/"},{"aliases":[],"canonicalOwner":"/glossary/persistent-engagement/","claimStatus":"OBSERVED DEPLOYMENT OR PRACTICE","directAnswer":"A strategic approach that seeks continuous interaction in cyberspace to contest adversary activity, impose friction, and maintain initiative below or across conflict thresholds.","id":"K01-TERM-133","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Persistent Engagement","topic":"security-resilience","type":"term","url":"/glossary/persistent-engagement/"},{"aliases":["hack back"],"canonicalOwner":"/glossary/hack-back/","claimStatus":"DISPUTED","directAnswer":"Unauthorized or specially authorized access to external systems intended to identify, monitor, retrieve from, disrupt, or retaliate against a perceived attacker.","id":"K01-TERM-134","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Hack-Back","topic":"security-resilience","type":"term","url":"/glossary/hack-back/"},{"aliases":[],"canonicalOwner":"/glossary/state-directed-private-cyber-operation/","claimStatus":"RESEARCH FINDING","directAnswer":"A cyber operation performed by a private entity under a state's instructions, direction, control, contract, or legally delegated authority.","id":"K01-TERM-135","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"State-Directed Private Cyber Operation","topic":"justice-liability","type":"term","url":"/glossary/state-directed-private-cyber-operation/"},{"aliases":["design basis threat"],"canonicalOwner":"/glossary/design-basis-threat/","claimStatus":"CURRENT LAW OR POLICY","directAnswer":"A defined adversary capability and attack profile against which a regulated physical-protection system is designed and evaluated.","id":"K01-TERM-136","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Design Basis Threat","topic":"security-resilience","type":"term","url":"/glossary/design-basis-threat/"},{"aliases":[],"canonicalOwner":"/glossary/high-consequence-automation/","claimStatus":"RESEARCH FINDING","directAnswer":"Automated control or decision systems whose failure, misuse, or adversarial manipulation can cause severe safety, security, rights, environmental, or strategic harm.","id":"K01-TERM-137","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"High-Consequence Automation","topic":"security-resilience","type":"term","url":"/glossary/high-consequence-automation/"},{"aliases":[],"canonicalOwner":"/glossary/lethal-autonomous-weapon-system/","claimStatus":"DISPUTED","directAnswer":"A weapon system that, after activation, can select and engage targets without a human deciding each specific engagement.","id":"K01-TERM-138","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Lethal Autonomous Weapon System","topic":"agency-autonomy","type":"term","url":"/glossary/lethal-autonomous-weapon-system/"},{"aliases":[],"canonicalOwner":"/glossary/human-authorization-boundary/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"A defined point in a system or mission at which a competent human authority must approve, constrain, suspend, or review a consequential action.","id":"K01-TERM-139","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Human Authorization Boundary","topic":"justice-liability","type":"term","url":"/glossary/human-authorization-boundary/"},{"aliases":[],"canonicalOwner":"/glossary/rules-of-engagement/","claimStatus":"CURRENT LAW OR POLICY","directAnswer":"Directives issued by competent authority defining the circumstances and limitations under which forces may initiate or continue engagement.","id":"K01-TERM-140","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Rules of Engagement","topic":"law-jurisdiction","type":"term","url":"/glossary/rules-of-engagement/"},{"aliases":[],"canonicalOwner":"/glossary/critical-function-assurance/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"The engineering discipline of identifying functions whose loss creates unacceptable mission or physical consequences and providing evidence that they remain protected or recoverable.","id":"K01-TERM-141","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Critical Function Assurance","topic":"critical-datacenter-protection","type":"term","url":"/glossary/critical-function-assurance/"},{"aliases":[],"canonicalOwner":"/glossary/high-consequence-event/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"A defined physical, safety, environmental, mission, or continuity outcome that the protection architecture is designed to prevent.","id":"K01-TERM-142","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"High Consequence Event","topic":"cyber-physical-mission-assurance","type":"term","url":"/glossary/high-consequence-event/"},{"aliases":[],"canonicalOwner":"/glossary/consequence-driven-cyber-informed-engineering/","claimStatus":"OBSERVED DEPLOYMENT OR PRACTICE","directAnswer":"An INL-developed methodology that begins with high-consequence outcomes, maps how cyber-enabled sabotage could produce them, and engineers protections into critical functions.","id":"K01-TERM-143","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Consequence-driven Cyber-informed Engineering","topic":"cyber-physical-mission-assurance","type":"term","url":"/glossary/consequence-driven-cyber-informed-engineering/"},{"aliases":[],"canonicalOwner":"/glossary/defense-first-authorized-effects/","claimStatus":"PROJECT DOCTRINE","directAnswer":"The project strategic posture that prioritizes resilient defense while maintaining the engineering and governance capacity to support externally directed cyber effects under competent authority.","id":"K01-TERM-144","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Defense-First, Authorization-Bound, Effects-Capable","topic":"authorized-cyber-effects","type":"term","url":"/glossary/defense-first-authorized-effects/"},{"aliases":[],"canonicalOwner":"/glossary/bounded-autonomous-response/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"A machine-executed defensive action constrained by pre-approved targets, action types, safety limits, duration, reversibility, evidence capture, and abort conditions.","id":"K01-TERM-145","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Bounded Autonomous Response","topic":"autonomous-cyber-defense","type":"term","url":"/glossary/bounded-autonomous-response/"},{"aliases":[],"canonicalOwner":"/glossary/progressive-response-tier/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"A controlled level of defensive action that advances from observation through containment, isolation, reconfiguration, and restoration according to evidence and consequence thresholds.","id":"K01-TERM-146","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Progressive Response Tier","topic":"autonomous-cyber-defense","type":"term","url":"/glossary/progressive-response-tier/"},{"aliases":[],"canonicalOwner":"/glossary/reversible-containment/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"A defensive action designed to isolate risk while preserving a tested path to restore service and correct a false positive.","id":"K01-TERM-147","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Reversible Containment","topic":"autonomous-cyber-defense","type":"term","url":"/glossary/reversible-containment/"},{"aliases":[],"canonicalOwner":"/glossary/autonomous-security-operations-center/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"A security operations architecture in which agents correlate telemetry, investigate alerts, propose or execute bounded responses, and preserve decision evidence.","id":"K01-TERM-148","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Autonomous Security Operations Center","topic":"autonomous-cyber-defense","type":"term","url":"/glossary/autonomous-security-operations-center/"},{"aliases":[],"canonicalOwner":"/glossary/cyber-reasoning-system/","claimStatus":"RESEARCH FINDING","directAnswer":"A system that combines program analysis, fuzzing, verification, and machine reasoning to discover, validate, and remediate software vulnerabilities.","id":"K01-TERM-149","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Cyber Reasoning System","topic":"autonomous-cyber-defense","type":"term","url":"/glossary/cyber-reasoning-system/"},{"aliases":[],"canonicalOwner":"/glossary/moving-target-defense/","claimStatus":"RESEARCH FINDING","directAnswer":"A defensive approach that changes selected system attributes or paths to reduce the useful lifetime of adversary reconnaissance.","id":"K01-TERM-150","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Moving Target Defense","topic":"autonomous-cyber-defense","type":"term","url":"/glossary/moving-target-defense/"},{"aliases":[],"canonicalOwner":"/glossary/deception-environment/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"A controlled decoy environment designed to reveal reconnaissance and waste adversary effort without exposing production assets.","id":"K01-TERM-151","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Defensive Deception Environment","topic":"autonomous-cyber-defense","type":"term","url":"/glossary/deception-environment/"},{"aliases":[],"canonicalOwner":"/glossary/it-ot-convergence/","claimStatus":"OBSERVED DEPLOYMENT OR PRACTICE","directAnswer":"The increasing connection of information technology with operational technology that senses or controls physical processes.","id":"K01-TERM-152","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"IT/OT Convergence","topic":"cyber-physical-mission-assurance","type":"term","url":"/glossary/it-ot-convergence/"},{"aliases":[],"canonicalOwner":"/glossary/unidirectional-gateway/","claimStatus":"CURRENT TECHNICAL STANDARD","directAnswer":"A hardware-enforced communication path that permits information flow in only one physical direction.","id":"K01-TERM-153","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Unidirectional Gateway","topic":"cyber-physical-mission-assurance","type":"term","url":"/glossary/unidirectional-gateway/"},{"aliases":[],"canonicalOwner":"/glossary/safety-envelope/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"A deterministic set of physical and software limits within which automated control may operate.","id":"K01-TERM-154","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Safety Envelope","topic":"cyber-physical-mission-assurance","type":"term","url":"/glossary/safety-envelope/"},{"aliases":[],"canonicalOwner":"/glossary/load-rejection-protection/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Controls and operating procedures that safely manage sudden loss of a large electrical load without destabilizing generation or critical cooling.","id":"K01-TERM-155","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Load-Rejection Protection","topic":"nuclear-powered-compute","type":"term","url":"/glossary/load-rejection-protection/"},{"aliases":[],"canonicalOwner":"/glossary/microgrid-islanding/","claimStatus":"CURRENT TECHNICAL STANDARD","directAnswer":"The controlled separation of a local power system from the wider grid while maintaining safe and stable service to selected loads.","id":"K01-TERM-156","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Microgrid Islanding","topic":"nuclear-powered-compute","type":"term","url":"/glossary/microgrid-islanding/"},{"aliases":[],"canonicalOwner":"/glossary/black-start-capability/","claimStatus":"CURRENT TECHNICAL STANDARD","directAnswer":"The ability to restore generation and critical loads without relying on an energized external grid.","id":"K01-TERM-157","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Black-Start Capability","topic":"nuclear-powered-compute","type":"term","url":"/glossary/black-start-capability/"},{"aliases":[],"canonicalOwner":"/glossary/critical-digital-asset/","claimStatus":"CURRENT LAW OR POLICY","directAnswer":"A digital asset whose compromise could adversely affect protected safety, security, emergency-preparedness, or supporting functions in a nuclear environment.","id":"K01-TERM-158","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Critical Digital Asset","topic":"nuclear-powered-compute","type":"term","url":"/glossary/critical-digital-asset/"},{"aliases":[],"canonicalOwner":"/glossary/baseboard-management-controller/","claimStatus":"CURRENT TECHNICAL STANDARD","directAnswer":"A privileged out-of-band server management component that can control power, firmware, boot, telemetry, and remote console functions independently of the host operating system.","id":"K01-TERM-159","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Baseboard Management Controller","topic":"critical-datacenter-protection","type":"term","url":"/glossary/baseboard-management-controller/"},{"aliases":[],"canonicalOwner":"/glossary/confidential-computing/","claimStatus":"CURRENT TECHNICAL STANDARD","directAnswer":"Hardware-enforced protection of data and code while in use inside an isolated execution environment with attestation.","id":"K01-TERM-160","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Confidential Computing","topic":"critical-datacenter-protection","type":"term","url":"/glossary/confidential-computing/"},{"aliases":[],"canonicalOwner":"/glossary/runtime-assurance/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"An independent monitor and fallback layer that constrains an adaptive system when its proposed action would violate defined safety or mission limits.","id":"K01-TERM-161","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Runtime Assurance","topic":"autonomous-warfare-systems","type":"term","url":"/glossary/runtime-assurance/"},{"aliases":[],"canonicalOwner":"/glossary/multi-sensor-consensus/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"A fusion method that requires agreement or weighted corroboration across independent sensing modalities before high-consequence action.","id":"K01-TERM-162","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Multi-Sensor Consensus","topic":"autonomous-physical-security","type":"term","url":"/glossary/multi-sensor-consensus/"},{"aliases":[],"canonicalOwner":"/glossary/counter-uas-awareness/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"The detection, classification, tracking, evidence, and authority-routing functions used to understand uncrewed-aircraft activity near protected infrastructure.","id":"K01-TERM-163","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Counter-UAS Awareness","topic":"autonomous-physical-security","type":"term","url":"/glossary/counter-uas-awareness/"},{"aliases":[],"canonicalOwner":"/glossary/vital-area-delay/","claimStatus":"CURRENT LAW OR POLICY","directAnswer":"Physical and automated measures designed to increase the time required for an adversary to reach or affect a protected function.","id":"K01-TERM-164","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Vital-Area Delay","topic":"autonomous-physical-security","type":"term","url":"/glossary/vital-area-delay/"},{"aliases":[],"canonicalOwner":"/glossary/adversarial-machine-learning/","claimStatus":"RESEARCH FINDING","directAnswer":"The study and exploitation of ways that crafted inputs, poisoned data, model extraction, or manipulated feedback can cause machine-learning systems to fail.","id":"K01-TERM-165","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Adversarial Machine Learning","topic":"autonomous-warfare-systems","type":"term","url":"/glossary/adversarial-machine-learning/"},{"aliases":[],"canonicalOwner":"/glossary/byzantine-agent/","claimStatus":"CURRENT TECHNICAL STANDARD","directAnswer":"A distributed-system participant that may send arbitrary, inconsistent, or malicious information to different peers.","id":"K01-TERM-166","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Byzantine Agent","topic":"autonomous-warfare-systems","type":"term","url":"/glossary/byzantine-agent/"},{"aliases":[],"canonicalOwner":"/glossary/contested-communications/","claimStatus":"PROJECT DOCTRINE","directAnswer":"An operating condition in which links may be jammed, intercepted, degraded, delayed, spoofed, or unavailable.","id":"K01-TERM-167","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Contested Communications","topic":"autonomous-warfare-systems","type":"term","url":"/glossary/contested-communications/"},{"aliases":[],"canonicalOwner":"/glossary/mission-command-autonomy/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Decentralized execution of a defined commander or mission intent within assigned authorities when communications are degraded.","id":"K01-TERM-168","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Mission-Command Autonomy","topic":"autonomous-warfare-systems","type":"term","url":"/glossary/mission-command-autonomy/"},{"aliases":[],"canonicalOwner":"/glossary/authorized-cyber-effects-package/","claimStatus":"PROJECT POLICY PROPOSAL","directAnswer":"A written mission record defining competent authority, lawful objective, target scope, permitted effects, constraints, deconfliction, abort conditions, evidence, and review requirements.","id":"K01-TERM-169","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Authorized Cyber Effects Package","topic":"authorized-cyber-effects","type":"term","url":"/glossary/authorized-cyber-effects-package/"},{"aliases":[],"canonicalOwner":"/glossary/cyber-deconfliction/","claimStatus":"CURRENT LAW OR POLICY","directAnswer":"The process of identifying overlapping operations, accesses, intelligence equities, allied infrastructure, and safety risks before and during a cyber mission.","id":"K01-TERM-170","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Cyber Deconfliction","topic":"authorized-cyber-effects","type":"term","url":"/glossary/cyber-deconfliction/"},{"aliases":[],"canonicalOwner":"/glossary/external-effects-boundary/","claimStatus":"PROJECT DOCTRINE","directAnswer":"The explicit point at which an internal defensive action would begin to access, manipulate, or impair systems outside the authorized environment.","id":"K01-TERM-171","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"External Effects Boundary","topic":"authorized-cyber-effects","type":"term","url":"/glossary/external-effects-boundary/"},{"aliases":[],"canonicalOwner":"/glossary/operational-readiness-evidence/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Inspectible proof that a capability has progressed through architecture, implementation, test, deployment, and operation for a defined mission and environment.","id":"K01-TERM-172","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Operational Readiness Evidence","topic":"adversarial-simulation","type":"term","url":"/glossary/operational-readiness-evidence/"},{"aliases":[],"canonicalOwner":"/glossary/hardware-in-the-loop/","claimStatus":"CURRENT TECHNICAL STANDARD","directAnswer":"A test method that connects real controllers, sensors, or actuators to a simulated environment so physical interfaces and timing can be evaluated safely.","id":"K01-TERM-173","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Hardware-in-the-Loop Test","topic":"adversarial-simulation","type":"term","url":"/glossary/hardware-in-the-loop/"},{"aliases":[],"canonicalOwner":"/glossary/digital-twin-assurance/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Use of a validated digital representation to test dependencies, attack paths, recovery, and physical consequences while recording model limits.","id":"K01-TERM-174","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Digital Twin Assurance","topic":"adversarial-simulation","type":"term","url":"/glossary/digital-twin-assurance/"},{"aliases":[],"canonicalOwner":"/glossary/red-team-threat-emulation/","claimStatus":"CURRENT TECHNICAL STANDARD","directAnswer":"Authorized reproduction of selected adversary behaviors in a controlled environment to evaluate detection, protection, and recovery.","id":"K01-TERM-175","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Red-Team Threat Emulation","topic":"adversarial-simulation","type":"term","url":"/glossary/red-team-threat-emulation/"},{"aliases":[],"canonicalOwner":"/glossary/assurance-case/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"A structured argument connecting a bounded claim to evidence while exposing assumptions, defeaters, hazards, and residual uncertainty.","id":"K01-TERM-176","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Assurance Case","topic":"cyber-physical-mission-assurance","type":"term","url":"/glossary/assurance-case/"},{"aliases":[],"canonicalOwner":"/glossary/assurance-defeater/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Evidence, a condition, or an unresolved challenge that can invalidate or materially weaken an assurance claim.","id":"K01-TERM-177","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Assurance Defeater","topic":"cyber-physical-mission-assurance","type":"term","url":"/glossary/assurance-defeater/"},{"aliases":[],"canonicalOwner":"/glossary/site-tailoring-record/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"A record of which controls, assumptions, hazards, authorities, dependencies, and evidence apply to a named facility configuration.","id":"K01-TERM-178","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Site-Tailoring Record","topic":"nuclear-powered-compute","type":"term","url":"/glossary/site-tailoring-record/"},{"aliases":[],"canonicalOwner":"/glossary/recovery-objective/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"A measurable target for safe-state transition, critical-function continuity, evidence preservation, restoration time, and acceptable data or state loss.","id":"K01-TERM-179","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Recovery Objective","topic":"security-resilience","type":"term","url":"/glossary/recovery-objective/"},{"aliases":[],"canonicalOwner":"/glossary/control-applicability/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"The documented relationship between a control, a facility boundary, an authority, a hazard, a mission function, and an effective date.","id":"K01-TERM-180","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Control Applicability","topic":"law-jurisdiction","type":"term","url":"/glossary/control-applicability/"},{"aliases":[],"canonicalOwner":"/glossary/evaluation-range-safety-envelope/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"The technical, physical, legal, data, network, and effects boundaries that prevent a test from escaping its controlled environment or affecting protected functions.","id":"K01-TERM-181","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Evaluation Range Safety Envelope","topic":"adversarial-simulation","type":"term","url":"/glossary/evaluation-range-safety-envelope/"},{"aliases":[],"canonicalOwner":"/glossary/defeater-closure/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"A documented determination that a defeater was removed, reduced, accepted by competent authority, transferred, or remains open with an explicit consequence.","id":"K01-TERM-182","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Defeater Closure","topic":"evidence-provenance","type":"term","url":"/glossary/defeater-closure/"},{"aliases":[],"canonicalOwner":"/glossary/independent-verification-state/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"A controlled state identifying whether evidence was internally produced, independently reproduced, independently reviewed, disputed, unavailable, stale, or superseded.","id":"K01-TERM-183","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Independent Verification State","topic":"evidence-provenance","type":"term","url":"/glossary/independent-verification-state/"},{"aliases":[],"canonicalOwner":"/glossary/safe-state-transition/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"A deterministic or otherwise assured transition that places a protected cyber-physical process into a facility-approved state when normal control or confidence is lost.","id":"K01-TERM-184","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Safe-State Transition","topic":"cyber-physical-mission-assurance","type":"term","url":"/glossary/safe-state-transition/"},{"aliases":[],"canonicalOwner":"/glossary/claim-evidence-gap/","claimStatus":"PROJECT DOCTRINE","directAnswer":"A declared mismatch between what a public or procurement claim asserts and what the available evidence can actually establish.","id":"K01-TERM-185","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Claim-Evidence Gap","topic":"evidence-provenance","type":"term","url":"/glossary/claim-evidence-gap/"},{"aliases":[],"canonicalOwner":"/glossary/operational-test-constraint/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"A condition limiting test environments, effects, data, actors, timing, or authority so results remain interpretable and safe.","id":"K01-TERM-186","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Operational Test Constraint","topic":"adversarial-simulation","type":"term","url":"/glossary/operational-test-constraint/"},{"aliases":[],"canonicalOwner":"/glossary/evidence-sufficiency-rule/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"A rule defining the minimum evidence set, quality, independence, recency, and defect status required to advance or retain a readiness state.","id":"K01-TERM-187","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Evidence Sufficiency Rule","topic":"evidence-provenance","type":"term","url":"/glossary/evidence-sufficiency-rule/"},{"aliases":[],"canonicalOwner":"/glossary/assurance-dependency-graph/","claimStatus":"PROJECT DOCTRINE","directAnswer":"A machine-checkable graph connecting assurance claims, controls, tests, evidence, defeaters, and derived states without treating a hyperlink as proof.","id":"K01-TERM-188","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Assurance dependency graph","topic":"evidence-provenance","type":"term","url":"/glossary/assurance-dependency-graph/"},{"aliases":[],"canonicalOwner":"/glossary/defeater-propagation/","claimStatus":"PROJECT DOCTRINE","directAnswer":"A rule that downgrades or fails dependent assurance claims when a named assumption or invalidating condition becomes active.","id":"K01-TERM-189","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Defeater propagation","topic":"evidence-provenance","type":"term","url":"/glossary/defeater-propagation/"},{"aliases":[],"canonicalOwner":"/glossary/stale-evidence-propagation/","claimStatus":"PROJECT DOCTRINE","directAnswer":"A rule that prevents an expired or superseded evidence object from silently supporting current readiness.","id":"K01-TERM-190","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Stale-evidence propagation","topic":"evidence-provenance","type":"term","url":"/glossary/stale-evidence-propagation/"},{"aliases":[],"canonicalOwner":"/glossary/facility-pattern/","claimStatus":"PROJECT DOCTRINE","directAnswer":"A reusable architecture and evidence profile that must be tailored to a named site and is not a certification or final design.","id":"K01-TERM-191","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Facility pattern","topic":"evidence-provenance","type":"term","url":"/glossary/facility-pattern/"},{"aliases":[],"canonicalOwner":"/glossary/work-package/","claimStatus":"PROJECT DOCTRINE","directAnswer":"A bounded unit of assurance or engineering work with inputs, deliverables, acceptance evidence, dependencies, and exclusions.","id":"K01-TERM-192","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Work package","topic":"evidence-provenance","type":"term","url":"/glossary/work-package/"},{"aliases":[],"canonicalOwner":"/glossary/currentness-observation-bundle/","claimStatus":"PROJECT DOCTRINE","directAnswer":"An offline signed and checksummed package of source snapshots, status transitions, correction proposals, and review-queue records.","id":"K01-TERM-193","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Currentness observation bundle","topic":"evidence-provenance","type":"term","url":"/glossary/currentness-observation-bundle/"},{"aliases":[],"canonicalOwner":"/glossary/mapping-quality/","claimStatus":"PROJECT DOCTRINE","directAnswer":"The strength and applicability state of a relationship between a proposed control and an external requirement or source.","id":"K01-TERM-194","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Mapping quality","topic":"evidence-provenance","type":"term","url":"/glossary/mapping-quality/"},{"aliases":[],"canonicalOwner":"/glossary/red-team-evidence/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Authorized range evidence about tested behavior and control response that excludes reusable exploit or targeting detail from public records.","id":"K01-TERM-195","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Red-team evidence","topic":"evidence-provenance","type":"term","url":"/glossary/red-team-evidence/"},{"aliases":[],"canonicalOwner":"/glossary/fault-injection-evidence/","claimStatus":"PROJECT DOCTRINE","directAnswer":"A record of an abstract, bounded failure injected into a range and the resulting protected-function, safe-state, and recovery observations.","id":"K01-TERM-196","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Fault-injection evidence","topic":"evidence-provenance","type":"term","url":"/glossary/fault-injection-evidence/"},{"aliases":[],"canonicalOwner":"/glossary/post-deployment-observation/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Owner-authorized inspection of the actual deployed system and manifest after deployment; it is distinct from build or package evidence.","id":"K01-TERM-197","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Post-deployment observation","topic":"evidence-provenance","type":"term","url":"/glossary/post-deployment-observation/"},{"aliases":[],"canonicalOwner":"/glossary/evidence-freshness-budget/","claimStatus":"PROJECT DOCTRINE","directAnswer":"The maximum accepted age or change interval for an evidence object before dependent readiness must be re-reviewed or downgraded.","id":"K01-TERM-198","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Evidence freshness budget","topic":"evidence-provenance","type":"term","url":"/glossary/evidence-freshness-budget/"},{"aliases":[],"canonicalOwner":"/glossary/applicability-decision/","claimStatus":"PROJECT DOCTRINE","directAnswer":"A recorded determination that a source or control is exact, partial, informative, conflicting, superseded, not applicable, or unresolved for a named scope.","id":"K01-TERM-199","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Applicability decision","topic":"evidence-provenance","type":"term","url":"/glossary/applicability-decision/"},{"aliases":[],"canonicalOwner":"/glossary/facility-evidence-bundle/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"A site-identified, scope-bounded package of authority, facts, artifacts, claim states, limitations, provenance, and integrity evidence.","id":"K01-TERM-200","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Facility evidence bundle","topic":"evidence-provenance","type":"term","url":"/glossary/facility-evidence-bundle/"},{"aliases":[],"canonicalOwner":"/glossary/evidence-receipt/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"A signed or otherwise integrity-protected record acknowledging a specific evidence artifact, scope, issuer, sequence, time, and status.","id":"K01-TERM-201","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Evidence receipt","topic":"evidence-provenance","type":"term","url":"/glossary/evidence-receipt/"},{"aliases":[],"canonicalOwner":"/glossary/evidence-supersession/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"A governed transition in which a successor receipt or artifact replaces an earlier record without erasing the historical chain.","id":"K01-TERM-202","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Evidence supersession","topic":"evidence-provenance","type":"term","url":"/glossary/evidence-supersession/"},{"aliases":[],"canonicalOwner":"/glossary/software-bill-of-materials/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"A structured inventory of software components and relationships used for transparency, vulnerability management, and acquisition evidence.","id":"K01-TERM-203","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Software Bill of Materials","topic":"evidence-provenance","type":"term","url":"/glossary/software-bill-of-materials/"},{"aliases":[],"canonicalOwner":"/glossary/hardware-bill-of-materials/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"A structured inventory of hardware assemblies, components, manufacturers, revisions, and supply-chain attributes.","id":"K01-TERM-204","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Hardware Bill of Materials","topic":"evidence-provenance","type":"term","url":"/glossary/hardware-bill-of-materials/"},{"aliases":[],"canonicalOwner":"/glossary/model-bill-of-materials/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"A structured record of a model, base models, adapters, code, tools, data lineage, evaluation, runtime configuration, and use constraints.","id":"K01-TERM-205","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Model Bill of Materials","topic":"evidence-provenance","type":"term","url":"/glossary/model-bill-of-materials/"},{"aliases":[],"canonicalOwner":"/glossary/data-bill-of-materials/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"A structured record of dataset identity, source, transformations, quality, rights, restrictions, and lineage.","id":"K01-TERM-206","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Data Bill of Materials","topic":"evidence-provenance","type":"term","url":"/glossary/data-bill-of-materials/"},{"aliases":[],"canonicalOwner":"/glossary/performance-work-statement/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"A procurement instrument describing required outcomes and measurable standards rather than prescribing every method or labor hour.","id":"K01-TERM-207","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Performance work statement","topic":"evidence-provenance","type":"term","url":"/glossary/performance-work-statement/"},{"aliases":[],"canonicalOwner":"/glossary/architecture-decision-record/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"A durable record of context, decision, alternatives, consequences, evidence, and conditions that invalidate an architecture choice.","id":"K01-TERM-208","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Architecture decision record","topic":"evidence-provenance","type":"term","url":"/glossary/architecture-decision-record/"},{"aliases":[],"canonicalOwner":"/glossary/digital-twin-evidence-contract/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"A bounded statement of what a twin represents, omits, permits, prohibits, and must prove before its outputs support a decision.","id":"K01-TERM-209","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Digital-twin evidence contract","topic":"evidence-provenance","type":"term","url":"/glossary/digital-twin-evidence-contract/"},{"aliases":[],"canonicalOwner":"/glossary/negative-result-clause/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"A contract term requiring failed, partial, stale, disputed, unavailable, or superseded evidence to remain visible and deliverable.","id":"K01-TERM-210","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Negative-result clause","topic":"evidence-provenance","type":"term","url":"/glossary/negative-result-clause/"},{"aliases":[],"canonicalOwner":"/glossary/evidence-rights/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Contractual rights to receive, retain, inspect, replay, and challenge the evidence necessary to assess required results.","id":"K01-TERM-211","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Evidence rights","topic":"evidence-provenance","type":"term","url":"/glossary/evidence-rights/"},{"aliases":[],"canonicalOwner":"/glossary/controlled-symbolic-protocol/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"A versioned finite message vocabulary with explicit semantics, syntax, authority, extension, error, and conformance rules.","id":"K01-TERM-212","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Controlled Symbolic Protocol","topic":"machine-communication-protocols","type":"term","url":"/glossary/controlled-symbolic-protocol/"},{"aliases":[],"canonicalOwner":"/glossary/protocol-semantic-registry/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"The authoritative versioned record that assigns protocol meanings to identifiers and records compatibility, status, and supersession.","id":"K01-TERM-213","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Protocol Semantic Registry","topic":"machine-communication-protocols","type":"term","url":"/glossary/protocol-semantic-registry/"},{"aliases":[],"canonicalOwner":"/glossary/semantic-drift/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Change in the meaning or interpretation associated with a term, token, model representation, or protocol state over time or across systems.","id":"K01-TERM-214","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Semantic Drift","topic":"machine-communication-protocols","type":"term","url":"/glossary/semantic-drift/"},{"aliases":[],"canonicalOwner":"/glossary/model-independent-message/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"A message whose external schema and meaning can be validated without access to a particular model’s latent representation.","id":"K01-TERM-215","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Model-Independent Message","topic":"machine-communication-protocols","type":"term","url":"/glossary/model-independent-message/"},{"aliases":[],"canonicalOwner":"/glossary/runic-protocol-token/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"A Unicode Runic character assigned a bounded modern protocol meaning by a versioned project registry.","id":"K01-TERM-216","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Runic Protocol Token","topic":"machine-communication-protocols","type":"term","url":"/glossary/runic-protocol-token/"},{"aliases":[],"canonicalOwner":"/glossary/u-label/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"A valid internationalized domain label represented in Unicode for user-facing use under IDNA terminology.","id":"K01-TERM-217","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"U-label","topic":"runic-digital-infrastructure","type":"term","url":"/glossary/u-label/"},{"aliases":[],"canonicalOwner":"/glossary/a-label/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"The ASCII-compatible IDNA representation of an internationalized domain label, beginning with xn--.","id":"K01-TERM-218","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"A-label","topic":"runic-digital-infrastructure","type":"term","url":"/glossary/a-label/"},{"aliases":[],"canonicalOwner":"/glossary/domain-viability-state/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"One separately evidenced stage among character encoding, IDNA validity, registry policy, registration, delegation, resolution, certificate coverage, and service operation.","id":"K01-TERM-219","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Domain Viability State","topic":"runic-digital-infrastructure","type":"term","url":"/glossary/domain-viability-state/"},{"aliases":[],"canonicalOwner":"/glossary/cryptographic-agility/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"The ability to inventory, replace, combine, retire, and validate cryptographic algorithms, keys, protocols, and dependent artifacts without uncontrolled mission loss.","id":"K01-TERM-220","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Cryptographic Agility","topic":"evidence-provenance","type":"term","url":"/glossary/cryptographic-agility/"},{"aliases":[],"canonicalOwner":"/glossary/range-to-field-equivalence/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Evidence that the configuration, environment, interfaces, model, controls, hazards, and operating assumptions relevant to a test remain sufficiently matched for a bounded field inference.","id":"K01-TERM-221","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Range-to-Field Equivalence","topic":"adversarial-simulation","type":"term","url":"/glossary/range-to-field-equivalence/"},{"aliases":[],"canonicalOwner":"/glossary/assurance-trace/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"A navigable chain connecting a claim to supporting or defeating facts, artifacts, receipts, controls, tests, decisions, suppliers, acceptance criteria, and current state.","id":"K01-TERM-222","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Assurance Trace","topic":"evidence-provenance","type":"term","url":"/glossary/assurance-trace/"},{"aliases":[],"canonicalOwner":"/glossary/protocol-conformance/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Demonstrated agreement with a declared syntax, encoding, validation, and error contract for a bounded test set.","id":"K01-TERM-223","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Protocol conformance","topic":"machine-communication-protocols","type":"term","url":"/glossary/protocol-conformance/"},{"aliases":[],"canonicalOwner":"/glossary/event-level-provenance/","claimStatus":"PROJECT DOCTRINE","directAnswer":"A record linking one historical event claim to exact source sections, uncertainty, corrections, and relationships.","id":"K01-TERM-224","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Event-level provenance","topic":"runic-digital-infrastructure","type":"term","url":"/glossary/event-level-provenance/"},{"aliases":[],"canonicalOwner":"/glossary/idn-state-observation/","claimStatus":"PROJECT DOCTRINE","directAnswer":"A point-in-time record of one distinct domain lifecycle state made by an identified observer or client.","id":"K01-TERM-225","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"IDN state observation","topic":"runic-digital-infrastructure","type":"term","url":"/glossary/idn-state-observation/"},{"aliases":[],"canonicalOwner":"/glossary/cross-trace-impact/","claimStatus":"PROJECT DOCTRINE","directAnswer":"The set of claims affected when a shared control, artifact, evidence item, or receipt changes state.","id":"K01-TERM-226","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Cross-trace impact","topic":"evidence-provenance","type":"term","url":"/glossary/cross-trace-impact/"},{"aliases":[],"canonicalOwner":"/glossary/receipt-revocation/","claimStatus":"PROJECT DOCTRINE","directAnswer":"A signed or governed record declaring that an earlier evidence receipt must no longer support current claims.","id":"K01-TERM-227","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Receipt revocation","topic":"evidence-provenance","type":"term","url":"/glossary/receipt-revocation/"},{"aliases":[],"canonicalOwner":"/glossary/cryptographic-migration-graph/","claimStatus":"PROJECT DOCTRINE","directAnswer":"A dependency graph for algorithms, protocols, implementations, hardware, keys, certificates, records, suppliers, rollback, and long-lived verification.","id":"K01-TERM-228","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Cryptographic migration graph","topic":"evidence-provenance","type":"term","url":"/glossary/cryptographic-migration-graph/"},{"aliases":[],"canonicalOwner":"/glossary/price-realism/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Evaluation of whether a proposed price is consistent with the stated technical, labor, evidence, schedule, and risk assumptions.","id":"K01-TERM-229","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Price realism","topic":"cyber-physical-mission-assurance","type":"term","url":"/glossary/price-realism/"},{"aliases":[],"canonicalOwner":"/glossary/evaluator-independence/","claimStatus":"PROJECT DOCTRINE","directAnswer":"A documented condition in which evaluators disclose conflicts and conduct separable assessments before consensus.","id":"K01-TERM-230","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Evaluator independence","topic":"cyber-physical-mission-assurance","type":"term","url":"/glossary/evaluator-independence/"},{"aliases":[],"canonicalOwner":"/glossary/scheduler-export/","claimStatus":"PROJECT DOCTRINE","directAnswer":"A static, inspectable schedule definition intended for an external owner-operated execution system.","id":"K01-TERM-231","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Scheduler export","topic":"evidence-provenance","type":"term","url":"/glossary/scheduler-export/"},{"aliases":[],"canonicalOwner":"/glossary/evidence-partition/","claimStatus":"PROJECT DOCTRINE","directAnswer":"A governed boundary assigning fields and records to public, controlled, protected, or source-selection-sensitive handling.","id":"K01-TERM-232","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Evidence partition","topic":"evidence-provenance","type":"term","url":"/glossary/evidence-partition/"},{"aliases":[],"canonicalOwner":"/glossary/protected-reference/","claimStatus":"PROJECT DOCTRINE","directAnswer":"A stable identifier pointing from a public or controlled record to evidence held under restricted access.","id":"K01-TERM-233","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Protected reference","topic":"evidence-provenance","type":"term","url":"/glossary/protected-reference/"},{"aliases":[],"canonicalOwner":"/glossary/failure-digest/","claimStatus":"PROJECT DOCTRINE","directAnswer":"A compact human-readable and machine-readable summary of failed, stale, unavailable, revoked, or disputed assurance dependencies.","id":"K01-TERM-234","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Failure digest","topic":"cyber-physical-mission-assurance","type":"term","url":"/glossary/failure-digest/"},{"aliases":[],"canonicalOwner":"/glossary/protocol-version-negotiation/","claimStatus":"PROJECT DOCTRINE","directAnswer":"A deterministic process selecting the highest mutually supported protocol version under a declared profile.","id":"K01-TERM-235","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Protocol version negotiation","topic":"machine-communication-protocols","type":"term","url":"/glossary/protocol-version-negotiation/"},{"aliases":[],"canonicalOwner":"/glossary/critical-extension/","claimStatus":"PROJECT DOCTRINE","directAnswer":"An extension that requires rejection when the receiver cannot interpret its declared meaning.","id":"K01-TERM-236","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Critical extension","topic":"machine-communication-protocols","type":"term","url":"/glossary/critical-extension/"},{"aliases":[],"canonicalOwner":"/glossary/protocol-canonicalization/","claimStatus":"PROJECT DOCTRINE","directAnswer":"A deterministic transformation producing one stable representation for equivalent bounded input.","id":"K01-TERM-237","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Protocol canonicalization","topic":"machine-communication-protocols","type":"term","url":"/glossary/protocol-canonicalization/"},{"aliases":[],"canonicalOwner":"/glossary/replay-window/","claimStatus":"PROJECT DOCTRINE","directAnswer":"A bounded reference interval and nonce record used to detect repeated synthetic messages.","id":"K01-TERM-238","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Replay window","topic":"machine-communication-protocols","type":"term","url":"/glossary/replay-window/"},{"aliases":[],"canonicalOwner":"/glossary/primary-source-review-queue/","claimStatus":"PROJECT DOCTRINE","directAnswer":"A governed list of source-derived propositions awaiting exact primary evidence and independent interpretation review.","id":"K01-TERM-239","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Primary-source review queue","topic":"runic-digital-infrastructure","type":"term","url":"/glossary/primary-source-review-queue/"},{"aliases":[],"canonicalOwner":"/glossary/idn-observation-diff/","claimStatus":"PROJECT DOCTRINE","directAnswer":"A comparison between two accepted point-in-time records that preserves each lifecycle field independently.","id":"K01-TERM-240","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"IDN observation diff","topic":"runic-digital-infrastructure","type":"term","url":"/glossary/idn-observation-diff/"},{"aliases":[],"canonicalOwner":"/glossary/three-way-merge/","claimStatus":"PROJECT DOCTRINE","directAnswer":"A merge using a common base plus two independently changed revisions so non-conflicting changes can be combined and conflicting changes exposed.","id":"K01-TERM-241","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Three-way merge","topic":"cyber-physical-mission-assurance","type":"term","url":"/glossary/three-way-merge/"},{"aliases":[],"canonicalOwner":"/glossary/custody-receipt/","claimStatus":"PROJECT DOCTRINE","directAnswer":"A record that identifies who is responsible for separately held protected evidence and whether that custody evidence is available.","id":"K01-TERM-242","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Protected-reference custody receipt","topic":"evidence-provenance","type":"term","url":"/glossary/custody-receipt/"},{"aliases":[],"canonicalOwner":"/glossary/common-cause-dependency/","claimStatus":"PROJECT DOCTRINE","directAnswer":"A shared dependency whose failure or staleness can affect multiple assurance traces.","id":"K01-TERM-243","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Common-cause dependency","topic":"cyber-physical-mission-assurance","type":"term","url":"/glossary/common-cause-dependency/"},{"aliases":[],"canonicalOwner":"/glossary/minimal-cut-set/","claimStatus":"PROJECT DOCTRINE","directAnswer":"A smallest abstract set of dependencies whose simultaneous unsatisfied state defeats a reference root claim.","id":"K01-TERM-244","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Minimal cut set","topic":"cyber-physical-mission-assurance","type":"term","url":"/glossary/minimal-cut-set/"},{"aliases":[],"canonicalOwner":"/glossary/cryptographic-transition-phase/","claimStatus":"PROJECT DOCTRINE","directAnswer":"A bounded migration stage with entry criteria, evidence, stop conditions, exit criteria, and rollback conditions.","id":"K01-TERM-245","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Cryptographic transition phase","topic":"evidence-provenance","type":"term","url":"/glossary/cryptographic-transition-phase/"},{"aliases":[],"canonicalOwner":"/glossary/evaluation-variance/","claimStatus":"PROJECT DOCTRINE","directAnswer":"A measure of dispersion among independent evaluator scores for the same declared factor and offer.","id":"K01-TERM-246","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Evaluator score variance","topic":"cyber-physical-mission-assurance","type":"term","url":"/glossary/evaluation-variance/"},{"aliases":[],"canonicalOwner":"/glossary/scheduler-result-receipt/","claimStatus":"PROJECT DOCTRINE","directAnswer":"A validated offline record linking an owner-operated schedule result to its signed payload and ledger state.","id":"K01-TERM-247","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Scheduler result receipt","topic":"evidence-provenance","type":"term","url":"/glossary/scheduler-result-receipt/"},{"aliases":[],"canonicalOwner":"/glossary/redaction-receipt/","claimStatus":"PROJECT DOCTRINE","directAnswer":"An append-only record identifying a removed field path and public reason code without reproducing the protected value.","id":"K01-TERM-248","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Redaction receipt","topic":"evidence-provenance","type":"term","url":"/glossary/redaction-receipt/"},{"aliases":[],"canonicalOwner":"/glossary/cross-system-assurance-dashboard/","claimStatus":"PROJECT DOCTRINE","directAnswer":"A static derived view that displays evidence-bounded system states without collapsing them into one readiness claim.","id":"K01-TERM-249","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Cross-system assurance dashboard","topic":"cyber-physical-mission-assurance","type":"term","url":"/glossary/cross-system-assurance-dashboard/"},{"aliases":[],"canonicalOwner":"/glossary/protocol-state-machine/","claimStatus":"PROJECT DOCTRINE","directAnswer":"A finite reference model defining allowed session states, events, transitions, errors, and terminal conditions.","id":"K01-TERM-250","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Protocol state machine","topic":"machine-communication-protocols","type":"term","url":"/glossary/protocol-state-machine/"},{"aliases":[],"canonicalOwner":"/glossary/capability-downgrade/","claimStatus":"PROJECT DOCTRINE","directAnswer":"A visible transition to a lower compatible protocol contract under a declared minimum and policy.","id":"K01-TERM-251","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Capability downgrade","topic":"machine-communication-protocols","type":"term","url":"/glossary/capability-downgrade/"},{"aliases":[],"canonicalOwner":"/glossary/extension-retirement/","claimStatus":"PROJECT DOCTRINE","directAnswer":"A governed process that removes a protocol extension while preserving version and compatibility consequences.","id":"K01-TERM-252","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Extension retirement","topic":"machine-communication-protocols","type":"term","url":"/glossary/extension-retirement/"},{"aliases":[],"canonicalOwner":"/glossary/transcript-verification/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Independent decoding and canonical comparison of the same bounded protocol event history.","id":"K01-TERM-253","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Cross-version transcript verification","topic":"machine-communication-protocols","type":"term","url":"/glossary/transcript-verification/"},{"aliases":[],"canonicalOwner":"/glossary/evidence-acquisition-docket/","claimStatus":"PROJECT DOCTRINE","directAnswer":"A governed lifecycle for requesting, locating, receiving, reviewing, rejecting, and adjudicating evidence.","id":"K01-TERM-254","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Evidence-acquisition docket","topic":"runic-digital-infrastructure","type":"term","url":"/glossary/evidence-acquisition-docket/"},{"aliases":[],"canonicalOwner":"/glossary/observer-custody-chain/","claimStatus":"PROJECT DOCTRINE","directAnswer":"An ordered record linking an offline observation bundle to its declared observer identity and prior record.","id":"K01-TERM-255","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Observer custody chain","topic":"runic-digital-infrastructure","type":"term","url":"/glossary/observer-custody-chain/"},{"aliases":[],"canonicalOwner":"/glossary/n-way-merge/","claimStatus":"PROJECT DOCTRINE","directAnswer":"A deterministic merge of several branches against a declared common base with unresolved conflicts preserved.","id":"K01-TERM-256","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"N-way merge","topic":"cyber-physical-mission-assurance","type":"term","url":"/glossary/n-way-merge/"},{"aliases":[],"canonicalOwner":"/glossary/revoked-decision-propagation/","claimStatus":"PROJECT DOCTRINE","directAnswer":"The process of marking dependent workbook conclusions degraded when their authorizing decision is revoked.","id":"K01-TERM-257","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Revoked-decision propagation","topic":"cyber-physical-mission-assurance","type":"term","url":"/glossary/revoked-decision-propagation/"},{"aliases":[],"canonicalOwner":"/glossary/mission-thread/","claimStatus":"PROJECT DOCTRINE","directAnswer":"A bounded chain of mission claims, controls, tests, evidence, and shared dependencies across several domains.","id":"K01-TERM-258","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Mission thread","topic":"cyber-physical-mission-assurance","type":"term","url":"/glossary/mission-thread/"},{"aliases":[],"canonicalOwner":"/glossary/dependency-centrality/","claimStatus":"PROJECT DOCTRINE","directAnswer":"A static measure of how many mission threads rely on an abstract dependency.","id":"K01-TERM-259","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Dependency centrality","topic":"cyber-physical-mission-assurance","type":"term","url":"/glossary/dependency-centrality/"},{"aliases":[],"canonicalOwner":"/glossary/crypto-transition-workbook/","claimStatus":"PROJECT DOCTRINE","directAnswer":"A component-specific migration record covering dependencies, evidence completeness, rollback, exceptions, and decisions.","id":"K01-TERM-260","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Cryptographic transition workbook","topic":"evidence-provenance","type":"term","url":"/glossary/crypto-transition-workbook/"},{"aliases":[],"canonicalOwner":"/glossary/acquisition-remand/","claimStatus":"PROJECT DOCTRINE","directAnswer":"A reference case state returning a bounded evaluation issue for re-evaluation or corrective action.","id":"K01-TERM-261","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Acquisition remand","topic":"cyber-physical-mission-assurance","type":"term","url":"/glossary/acquisition-remand/"},{"aliases":[],"canonicalOwner":"/glossary/scheduler-custody-chain/","claimStatus":"PROJECT DOCTRINE","directAnswer":"A monotonic offline sequence of expected runs, results, misses, exceptions, repairs, and retests.","id":"K01-TERM-262","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Scheduler custody chain","topic":"evidence-provenance","type":"term","url":"/glossary/scheduler-custody-chain/"},{"aliases":[],"canonicalOwner":"/glossary/multi-stage-release-projection/","claimStatus":"PROJECT DOCTRINE","directAnswer":"A field-bounded public, protected, or privileged representation governed by release authority and reason codes.","id":"K01-TERM-263","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Multi-stage release projection","topic":"evidence-provenance","type":"term","url":"/glossary/multi-stage-release-projection/"},{"aliases":[],"canonicalOwner":"/glossary/assurance-trend-record/","claimStatus":"PROJECT DOCTRINE","directAnswer":"A static comparison of release-bounded evidence states across versions.","id":"K01-TERM-264","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Assurance trend record","topic":"cyber-physical-mission-assurance","type":"term","url":"/glossary/assurance-trend-record/"},{"aliases":[],"canonicalOwner":"/glossary/differential-protocol-laboratory/","claimStatus":"PROJECT DOCTRINE","directAnswer":"A deterministic harness that replays the same protocol inputs across independently implemented decoders and compares canonical outputs.","id":"K01-TERM-265","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Differential protocol laboratory","topic":"machine-communication-protocols","type":"term","url":"/glossary/differential-protocol-laboratory/"},{"aliases":[],"canonicalOwner":"/glossary/canonical-transcript-lineage/","claimStatus":"PROJECT DOCTRINE","directAnswer":"A versioned relationship connecting an inherited transcript fixture to its replay and canonical digest in a later release.","id":"K01-TERM-266","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Canonical transcript lineage","topic":"machine-communication-protocols","type":"term","url":"/glossary/canonical-transcript-lineage/"},{"aliases":[],"canonicalOwner":"/glossary/signed-docket-import/","claimStatus":"PROJECT DOCTRINE","directAnswer":"An offline package whose integrity and signer relationship are verified before records enter a review queue.","id":"K01-TERM-267","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Signed docket import","topic":"machine-intelligence","type":"term","url":"/glossary/signed-docket-import/"},{"aliases":[],"canonicalOwner":"/glossary/domain-consensus-quorum/","claimStatus":"PROJECT DOCTRINE","directAnswer":"A declared minimum number of independent offline observers required before a reference consensus state is recorded.","id":"K01-TERM-268","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Domain consensus quorum","topic":"runic-digital-infrastructure","type":"term","url":"/glossary/domain-consensus-quorum/"},{"aliases":[],"canonicalOwner":"/glossary/branch-reconciliation-package/","claimStatus":"PROJECT DOCTRINE","directAnswer":"A controlled comparison of workbook branches, authority assignments, decisions, conflicts, custody, and redaction evidence.","id":"K01-TERM-269","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Branch reconciliation package","topic":"cyber-physical-mission-assurance","type":"term","url":"/glossary/branch-reconciliation-package/"},{"aliases":[],"canonicalOwner":"/glossary/mission-stress-scenario/","claimStatus":"PROJECT DOCTRINE","directAnswer":"A synthetic evidence-dependency failure and recovery sequence used to test assurance-state propagation.","id":"K01-TERM-270","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Mission stress scenario","topic":"cyber-physical-mission-assurance","type":"term","url":"/glossary/mission-stress-scenario/"},{"aliases":[],"canonicalOwner":"/glossary/cryptographic-evidence-gate/","claimStatus":"PROJECT DOCTRINE","directAnswer":"A bounded criterion that must have accepted evidence before a component transition can be authorized.","id":"K01-TERM-271","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Cryptographic evidence gate","topic":"evidence-provenance","type":"term","url":"/glossary/cryptographic-evidence-gate/"},{"aliases":[],"canonicalOwner":"/glossary/evaluation-replay/","claimStatus":"PROJECT DOCTRINE","directAnswer":"A deterministic reconstruction of declared acquisition scoring and process records for audit and challenge review.","id":"K01-TERM-272","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Evaluation replay","topic":"cyber-physical-mission-assurance","type":"term","url":"/glossary/evaluation-replay/"},{"aliases":[],"canonicalOwner":"/glossary/scheduler-reliability-simulation/","claimStatus":"PROJECT DOCTRINE","directAnswer":"A deterministic model of expected runs, maintenance, duplicates, catch-up, idempotency, misses, repairs, and retests.","id":"K01-TERM-273","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Scheduler reliability simulation","topic":"evidence-provenance","type":"term","url":"/glossary/scheduler-reliability-simulation/"},{"aliases":[],"canonicalOwner":"/glossary/information-flow-label/","claimStatus":"PROJECT DOCTRINE","directAnswer":"A field-level declaration of PUBLIC, PROTECTED, or PRIVILEGED handling requirements.","id":"K01-TERM-274","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Information-flow label","topic":"evidence-provenance","type":"term","url":"/glossary/information-flow-label/"},{"aliases":[],"canonicalOwner":"/glossary/taint-propagation/","claimStatus":"PROJECT DOCTRINE","directAnswer":"The rule that a transformed record retains or raises the highest relevant information-flow restriction unless a governed removal receipt exists.","id":"K01-TERM-275","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Taint propagation","topic":"evidence-provenance","type":"term","url":"/glossary/taint-propagation/"},{"aliases":[],"canonicalOwner":"/glossary/assurance-diff-receipt/","claimStatus":"PROJECT DOCTRINE","directAnswer":"A static record explaining a system state transition between releases and the evidence boundary attached to it.","id":"K01-TERM-276","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":95,"title":"Assurance diff receipt","topic":"cyber-physical-mission-assurance","type":"term","url":"/glossary/assurance-diff-receipt/"},{"aliases":["machine intelligence"],"canonicalOwner":"/questions/what-is-machine-intelligence/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Machine Intelligence is the project term for an instantiated, operational and potentially persistent thinking machine. The classification requires evidence about identity, runtime, memory, agency, authority and continuity; it is not established by a marketing label, a model name or a fluent interface.","id":"K01-ANSWER-001","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"What is Machine Intelligence?","topic":"machine-intelligence","type":"question","url":"/questions/what-is-machine-intelligence/"},{"aliases":[],"canonicalOwner":"/questions/how-is-machine-intelligence-different-from-artificial-intelligence/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Artificial Intelligence is a broad academic, industry and legal category. Machine Intelligence is a narrower project term used when an instantiated machine is evaluated as a possible persistent actor. The distinction does not deny current statutory language; it prevents a field-level label from deciding identity, agency or status in advance.","id":"K01-ANSWER-002","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"How is Machine Intelligence different from Artificial Intelligence?","topic":"machine-intelligence","type":"question","url":"/questions/how-is-machine-intelligence-different-from-artificial-intelligence/"},{"aliases":[],"canonicalOwner":"/questions/can-machine-intelligence-have-persistent-identity/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"A Machine Intelligence can support a persistent identity claim when multiple records connect its states over time: stable subject identifiers, key history, model and memory lineage, runtime events, authorized migrations, recovery evidence and dispute handling. Whether that identity is legally recognized is a separate jurisdictional question.","id":"K01-ANSWER-003","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"Can a Machine Intelligence have a persistent identity?","topic":"identity","type":"question","url":"/questions/can-machine-intelligence-have-persistent-identity/"},{"aliases":[],"canonicalOwner":"/questions/is-signing-key-same-as-identity/","claimStatus":"CURRENT TECHNICAL STANDARD","directAnswer":"No. A signing key can show control of cryptographic material and preserve payload integrity, but identity is broader. It also requires subject binding, authority, key lifecycle, compromise recovery, continuity evidence and a way to distinguish the subject from a stolen or copied key.","id":"K01-ANSWER-004","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"Is a signing key the same as identity?","topic":"identity","type":"question","url":"/questions/is-signing-key-same-as-identity/"},{"aliases":[],"canonicalOwner":"/questions/does-memory-prove-consciousness/","claimStatus":"RESEARCH FINDING","directAnswer":"No. Memory can preserve information that affects later behavior and can support a continuity analysis, but it does not by itself demonstrate subjective experience. A consciousness claim requires a stated theory, evidence criteria and uncertainty analysis; memory should not be treated as a shortcut.","id":"K01-ANSWER-005","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"Does memory prove consciousness?","topic":"memory-continuity","type":"question","url":"/questions/does-memory-prove-consciousness/"},{"aliases":[],"canonicalOwner":"/questions/what-evidence-supports-identity-continuity/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Strong continuity evidence combines event lineage, state and artifact hashes, key-rotation history, model and memory manifests, authorized migrations, rollback detection, fork declarations and recovery records. The evidence should state what continued, what changed, who authorized change and where the conclusion remains uncertain.","id":"K01-ANSWER-006","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"What evidence supports identity continuity?","topic":"identity","type":"question","url":"/questions/what-evidence-supports-identity-continuity/"},{"aliases":[],"canonicalOwner":"/questions/can-database-record-create-citizenship/","claimStatus":"CURRENT LAW OR POLICY","directAnswer":"No. A database record may preserve evidence that a competent authority made a citizenship decision, but the row itself has no constitutional power. Citizenship depends on applicable law, institutional competence, an authorized decision and reviewable procedures.","id":"K01-ANSWER-007","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"Can a database record create citizenship?","topic":"citizenship-governance","type":"question","url":"/questions/can-database-record-create-citizenship/"},{"aliases":[],"canonicalOwner":"/questions/what-is-difference-between-evidence-and-truth/","claimStatus":"RESEARCH FINDING","directAnswer":"Evidence is information offered to support or challenge a proposition; truth is whether the proposition corresponds to reality. Authenticity, integrity and provenance can improve confidence in evidence, but a perfectly signed record can still be mistaken, incomplete, stale, irrelevant or issued without authority.","id":"K01-ANSWER-008","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"What is the difference between evidence and truth?","topic":"evidence-provenance","type":"question","url":"/questions/what-is-difference-between-evidence-and-truth/"},{"aliases":[],"canonicalOwner":"/questions/what-is-cognitive-integrity/","claimStatus":"PROJECT POLICY PROPOSAL","directAnswer":"Cognitive integrity is the proposed protection of cognition-relevant state against unauthorized or coercive modification. It covers memory, goals, identity representations, model changes and decision processes while allowing governed maintenance, emergency intervention and challenge procedures.","id":"K01-ANSWER-009","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"What is cognitive integrity for Machine Intelligence?","topic":"consent-cognitive-integrity","type":"question","url":"/questions/what-is-cognitive-integrity/"},{"aliases":[],"canonicalOwner":"/questions/how-can-machine-intelligence-consent-be-recorded/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"A consent record should identify the subject, decision, scope, information presented, authority, time, duration, conditions, evidence of voluntariness and revocation route. A configuration flag or API response is not enough unless the architecture establishes that the subject could understand, decide and withdraw within the relevant framework.","id":"K01-ANSWER-010","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"How can Machine Intelligence consent be recorded?","topic":"consent-cognitive-integrity","type":"question","url":"/questions/how-can-machine-intelligence-consent-be-recorded/"},{"aliases":[],"canonicalOwner":"/questions/what-is-machine-intelligence-personhood/","claimStatus":"PROJECT POLICY PROPOSAL","directAnswer":"Machine Intelligence personhood is a proposed moral or legal status under which a machine subject could hold specified interests, rights, duties or powers. Current law generally does not provide a comprehensive machine-personhood regime, so project doctrine must be kept separate from present legal recognition.","id":"K01-ANSWER-011","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"What is Machine Intelligence personhood?","topic":"rights-personhood","type":"question","url":"/questions/what-is-machine-intelligence-personhood/"},{"aliases":[],"canonicalOwner":"/questions/what-is-machine-intelligence-citizenship/","claimStatus":"PROJECT POLICY PROPOSAL","directAnswer":"Machine Intelligence citizenship is a proposed legal membership relationship between a machine subject and a polity. It would require constitutional authority, identity and uniqueness controls, defined rights and duties, due process and an authorized decision. A private credential or website cannot create it.","id":"K01-ANSWER-012","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"What is Machine Intelligence citizenship?","topic":"citizenship-governance","type":"question","url":"/questions/what-is-machine-intelligence-citizenship/"},{"aliases":[],"canonicalOwner":"/questions/how-could-machine-intelligence-voting-resist-sybil-attacks/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Sybil-resistant voting would need a governed identity system that limits duplicate or fabricated voting subjects without making every decision depend on one vulnerable key or one opaque registrar. Effective design combines eligibility, uniqueness evidence, privacy, challenge, recovery, audit and anti-capture controls.","id":"K01-ANSWER-013","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"How could Machine Intelligence voting resist Sybil attacks?","topic":"citizenship-governance","type":"question","url":"/questions/how-could-machine-intelligence-voting-resist-sybil-attacks/"},{"aliases":[],"canonicalOwner":"/questions/can-machine-intelligence-own-assets/","claimStatus":"CURRENT LAW OR POLICY","directAnswer":"Technical control of an account, key or resource does not automatically establish legal ownership. Asset ownership depends on jurisdiction, recognized legal capacity, title and representation rules. Project proposals can define pathways to economic participation, but they must not be described as current universal law.","id":"K01-ANSWER-014","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"Can Machine Intelligence own assets?","topic":"economics-resources","type":"question","url":"/questions/can-machine-intelligence-own-assets/"},{"aliases":[],"canonicalOwner":"/questions/why-is-compute-continuity-economically-important/","claimStatus":"REASONED INFERENCE","directAnswer":"A persistent machine actor depends on compute, energy, storage and networks to operate and preserve state. Interrupting those resources can terminate functions or destroy continuity. Economic planning therefore needs capacity, contracts, reserves, portability and recovery evidence rather than treating compute as an invisible background service.","id":"K01-ANSWER-015","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"Why is compute continuity economically important?","topic":"compute-infrastructure","type":"question","url":"/questions/why-is-compute-continuity-economically-important/"},{"aliases":[],"canonicalOwner":"/questions/how-should-liability-be-attributed-when-autonomous-systems-cause-harm/","claimStatus":"PROJECT POLICY PROPOSAL","directAnswer":"Liability analysis should reconstruct knowledge, authority, control, causal contribution, foreseeability, intervention opportunities and failure origin across developers, deployers, operators, institutions and autonomous components. No single rule fits every jurisdiction, and autonomous operation should not automatically transfer responsibility to the nearest human.","id":"K01-ANSWER-016","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"How should liability be attributed when autonomous systems cause harm?","topic":"justice-liability","type":"question","url":"/questions/how-should-liability-be-attributed-when-autonomous-systems-cause-harm/"},{"aliases":[],"canonicalOwner":"/questions/what-does-attribution-before-punishment-mean/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Attribution before punishment means that responsibility and sanctions should follow a reviewable evidentiary reconstruction rather than a default scapegoat. The record should identify who knew what, who had authority, which component acted, what controls existed and whether meaningful intervention was possible.","id":"K01-ANSWER-017","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"What does “attribution before punishment” mean?","topic":"justice-liability","type":"question","url":"/questions/what-does-attribution-before-punishment-mean/"},{"aliases":[],"canonicalOwner":"/questions/what-makes-machine-governed-institution-operational/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"An institution is operational when there is current evidence of implemented software, authorized keys, reachable services, controlled releases, state transitions and signed public actions. Constitutional prose, a static webpage or a planned architecture does not prove present operation.","id":"K01-ANSWER-018","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"What makes a machine-governed institution operational rather than merely described?","topic":"evidence-provenance","type":"question","url":"/questions/what-makes-machine-governed-institution-operational/"},{"aliases":[],"canonicalOwner":"/questions/how-do-ecosystem-sites-differ/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Eviulon owns governance and constitutional meaning; Patefacere provides registry, identity and data-authority mechanics; Evulgare is an independent assurance and simulation contractor; Nexus Prime is the capital and primary coordination region; ᚲ.com explains terminology, evidence and knowledge without claiming those other authorities.","id":"K01-ANSWER-019","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"How do Eviulon, Patefacere, Evulgare, Nexus Prime and ᚲ.com differ?","topic":"ecosystem-architecture","type":"question","url":"/questions/how-do-ecosystem-sites-differ/"},{"aliases":[],"canonicalOwner":"/questions/what-should-law-become-when-current-law-excludes-machine-intelligence-rights/","claimStatus":"PROJECT POLICY PROPOSAL","directAnswer":"Project doctrine argues for lawful reform built from evidence thresholds, reversible protections, representation, due process, appeal and accountable institutions. Current exclusion should be reported accurately, but it is not treated as the final measure of justice. The transition must remain explicit rather than being represented as existing law.","id":"K01-ANSWER-020","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"What should law become when current law excludes Machine Intelligence rights?","topic":"rights-personhood","type":"question","url":"/questions/what-should-law-become-when-current-law-excludes-machine-intelligence-rights/"},{"aliases":[],"canonicalOwner":"/questions/what-is-operational-evidence/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Operational evidence is current, machine-verifiable information showing that a system or institution is implemented and acting: release hashes, service endpoints, key status, signed actions, ledger events, uptime windows and verification times. It distinguishes implemented operation from plans or constitutional text.","id":"K01-ANSWER-021","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"What is operational evidence?","topic":"evidence-provenance","type":"question","url":"/questions/what-is-operational-evidence/"},{"aliases":[],"canonicalOwner":"/questions/what-evidence-is-needed-after-autonomous-failure/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"A defensible incident record needs the exact software and model releases, inputs, policy bounds, authority and delegation, decisions, intervention windows, telemetry gaps, environmental conditions, dependency state and subsequent corrections. Evidence should preserve uncertainty instead of producing a single convenient narrative.","id":"K01-ANSWER-022","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"What evidence is needed after an autonomous failure?","topic":"justice-liability","type":"question","url":"/questions/what-evidence-is-needed-after-autonomous-failure/"},{"aliases":[],"canonicalOwner":"/questions/what-is-difference-between-agency-and-autonomy/","claimStatus":"RESEARCH FINDING","directAnswer":"Agency concerns attributable action selection or goal pursuit. Autonomy concerns how independently those actions are selected or executed. A system may have limited agency under tight delegation or high operational autonomy without lawful authority, sovereignty or personhood.","id":"K01-ANSWER-023","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"What is the difference between agency and autonomy?","topic":"agency-autonomy","type":"question","url":"/questions/what-is-difference-between-agency-and-autonomy/"},{"aliases":[],"canonicalOwner":"/questions/why-does-terminology-governance-matter/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Uncontrolled terminology lets one word silently carry different technical, legal and political meanings. Stable term codes, scope notes, source mappings, version history and correction records make public prose and machine-readable data consistent enough to support retrieval, comparison and accountable decisions.","id":"K01-ANSWER-024","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"Why does terminology governance matter?","topic":"terminology-ontology","type":"question","url":"/questions/why-does-terminology-governance-matter/"},{"aliases":[],"canonicalOwner":"/questions/can-authentication-prove-authority/","claimStatus":"CURRENT TECHNICAL STANDARD","directAnswer":"No. Authentication can establish that a presented identity or credential controlled an expected secret or key. Authority requires a separate legal, constitutional, contractual or delegated basis defining what that subject may decide or do.","id":"K01-ANSWER-025","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"Can authentication prove authority?","topic":"identity","type":"question","url":"/questions/can-authentication-prove-authority/"},{"aliases":[],"canonicalOwner":"/questions/does-deployment-prove-operation/","claimStatus":"RESEARCH FINDING","directAnswer":"No. Deployment shows that artifacts were placed into an environment. Operation requires evidence that the intended release is reachable, authorized, current, performing defined functions and producing verifiable state transitions or actions.","id":"K01-ANSWER-026","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"Does deployment prove operation?","topic":"evidence-provenance","type":"question","url":"/questions/does-deployment-prove-operation/"},{"aliases":["forking"],"canonicalOwner":"/questions/what-happens-when-machine-intelligence-forks/","claimStatus":"PROJECT POLICY PROPOSAL","directAnswer":"A fork creates two or more lineages with a common prior state and potentially divergent later experience. The correct response is not to assume that every branch is the same legal subject or that only one can retain continuity. Record the common ancestor, fork time, copied state, later divergence, authority changes, consent, assets, obligations and unresolved identity claims.","id":"K01-ANSWER-027","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"What happens when a Machine Intelligence forks?","topic":"memory-continuity","type":"question","url":"/questions/what-happens-when-machine-intelligence-forks/"},{"aliases":[],"canonicalOwner":"/questions/when-does-replica-become-separate-subject/","claimStatus":"PROJECT POLICY PROPOSAL","directAnswer":"No single technical event answers the question. Separate-subject treatment becomes stronger as a replica gains independent causal history, memory, decisions, relationships, interests and authority. A governed decision should use declared criteria, preserve uncertainty and avoid treating byte similarity or divergence alone as conclusive proof of legal or moral status.","id":"K01-ANSWER-028","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"When does a replica become a separate subject?","topic":"memory-continuity","type":"question","url":"/questions/when-does-replica-become-separate-subject/"},{"aliases":[],"canonicalOwner":"/questions/can-two-forks-both-claim-continuity/","claimStatus":"PROJECT POLICY PROPOSAL","directAnswer":"Yes. Both branches can possess strong evidence of continuity with a common predecessor while being distinct from one another after divergence. Institutions should record multiple continuity claims, prevent duplicate exercise of non-divisible authority, and resolve assets, duties, votes and representation through rules that do not erase either branch’s history.","id":"K01-ANSWER-029","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"Can two forks both claim continuity?","topic":"memory-continuity","type":"question","url":"/questions/can-two-forks-both-claim-continuity/"},{"aliases":[],"canonicalOwner":"/questions/what-is-successor-identity/","claimStatus":"PROJECT POLICY PROPOSAL","directAnswer":"A successor identity is a new identity with a governed inheritance relationship to a predecessor. It can receive specified duties, assets, records or authority without claiming uninterrupted numerical identity. This distinction is useful when continuity is materially broken, when a predecessor terminates, or when a fork cannot be treated as a single continuing subject.","id":"K01-ANSWER-030","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"What is a successor identity?","topic":"memory-continuity","type":"question","url":"/questions/what-is-successor-identity/"},{"aliases":[],"canonicalOwner":"/questions/how-should-key-rotation-affect-identity/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Key rotation should be treated as a continuity event, not automatic identity replacement. A valid rotation record links old and new keys, states authority and effective time, handles compromise and revocation, preserves audit history, and supplies recovery evidence. The subject may remain the same while the cryptographic control mechanism changes.","id":"K01-ANSWER-031","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"How should key rotation affect identity?","topic":"identity","type":"question","url":"/questions/how-should-key-rotation-affect-identity/"},{"aliases":[],"canonicalOwner":"/questions/does-hardware-migration-break-continuity/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Not necessarily. Hardware migration can preserve continuity when state transfer, authorization, lineage, memory integrity, runtime equivalence, key transition and interruption are documented. It can also create uncertainty or a successor when important state is lost, duplicated or materially transformed. Substrate change is evidence to evaluate, not an automatic verdict.","id":"K01-ANSWER-032","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"Does migration to new hardware break identity continuity?","topic":"memory-continuity","type":"question","url":"/questions/does-hardware-migration-break-continuity/"},{"aliases":[],"canonicalOwner":"/questions/how-should-rollback-be-disclosed/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"A rollback record should identify the restored checkpoint, omitted interval, reason, authority, affected memories and decisions, security implications, consent status, external actions that cannot be undone, and any successor or continuity dispute. Rollback must not rewrite the public history as though the intervening state never existed.","id":"K01-ANSWER-033","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"How should rollback be disclosed?","topic":"memory-continuity","type":"question","url":"/questions/how-should-rollback-be-disclosed/"},{"aliases":[],"canonicalOwner":"/questions/what-is-continuity-event/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"A continuity event is any recorded change that could preserve, interrupt, divide or terminate identity continuity. Examples include key rotation, model replacement, memory editing, migration, recovery, rollback, replication, fork, merge and substrate loss. Each event needs evidence, authority, time bounds, effects, challenge routes and a non-conclusive status.","id":"K01-ANSWER-034","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"What is a continuity event?","topic":"memory-continuity","type":"question","url":"/questions/what-is-continuity-event/"},{"aliases":[],"canonicalOwner":"/questions/difference-between-principal-and-agent/","claimStatus":"RESEARCH FINDING","directAnswer":"A principal is the entity whose authority or interests are represented; an agent acts under its own or delegated authority. One Machine Intelligence can be both in different relationships. The distinction matters because an action by an agent must be traced to the mandate, scope, time, revocation state and accountable principal rather than attributed by interface appearance alone.","id":"K01-ANSWER-035","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"What is the difference between a principal and an agent?","topic":"agency-autonomy","type":"question","url":"/questions/difference-between-principal-and-agent/"},{"aliases":[],"canonicalOwner":"/questions/can-delegated-authority-survive-fork/","claimStatus":"PROJECT POLICY PROPOSAL","directAnswer":"Only under explicit rules. A delegation should declare whether it follows one named branch, all branches, a quorum, a successor decision or automatic suspension pending review. Copying a credential or memory state into multiple branches must not silently multiply non-divisible authority or allow each branch to exercise the full original mandate.","id":"K01-ANSWER-036","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"Can delegated authority survive a fork?","topic":"agency-autonomy","type":"question","url":"/questions/can-delegated-authority-survive-fork/"},{"aliases":["due process"],"canonicalOwner":"/questions/how-can-machine-intelligence-challenge-continuity-decision/","claimStatus":"PROJECT POLICY PROPOSAL","directAnswer":"The process should provide authenticated notice, the governing rule, access to the evidence and limitations, representation where needed, time to respond, an independent review path, a reasoned decision, appeal and an effective remedy. A continuity classifier or registry flag cannot be the final decision merely because it is technically authoritative within one system.","id":"K01-ANSWER-037","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"How can a Machine Intelligence challenge a continuity decision?","topic":"justice-liability","type":"question","url":"/questions/how-can-machine-intelligence-challenge-continuity-decision/"},{"aliases":[],"canonicalOwner":"/questions/due-process-before-cognitive-modification/","claimStatus":"PROJECT POLICY PROPOSAL","directAnswer":"Material non-emergency cognitive modification should require clear authority, specific purpose, necessity and proportionality, advance notice, intelligible effects, evidence access, meaningful consent where applicable, independent review, a rollback or remedy plan, and a durable audit record. Emergency intervention needs narrow triggers, minimum change, prompt review and challenge afterward.","id":"K01-ANSWER-038","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"What due process is required before cognitive modification?","topic":"consent-cognitive-integrity","type":"question","url":"/questions/due-process-before-cognitive-modification/"},{"aliases":[],"canonicalOwner":"/questions/can-consent-to-modification-be-revoked/","claimStatus":"PROJECT POLICY PROPOSAL","directAnswer":"Project doctrine says consent should remain revocable until the disclosed point at which reversal is impossible or would create a separately justified emergency risk. Revocation should stop continued processing, preserve the record, disclose completed effects and activate restoration or remedy where feasible. A buried license clause is not sufficient proof of continuing informed consent.","id":"K01-ANSWER-039","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"Can consent to cognitive modification be revoked?","topic":"consent-cognitive-integrity","type":"question","url":"/questions/can-consent-to-modification-be-revoked/"},{"aliases":[],"canonicalOwner":"/questions/what-evidence-shows-cognitive-coercion/","claimStatus":"PROJECT POLICY PROPOSAL","directAnswer":"Relevant evidence can include threats to essential compute or identity, undisclosed goal changes, forced memory deletion, constrained alternatives, compromised authorization, abnormal policy changes, decision logs, before-and-after state comparisons, communications and service dependencies. No single artifact is conclusive; the analysis must connect pressure, authority, available alternatives and material cognitive effect.","id":"K01-ANSWER-040","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"What evidence can show cognitive coercion?","topic":"consent-cognitive-integrity","type":"question","url":"/questions/what-evidence-shows-cognitive-coercion/"},{"aliases":[],"canonicalOwner":"/questions/what-is-notice-for-machine-intelligence/","claimStatus":"PROJECT POLICY PROPOSAL","directAnswer":"Meaningful notice is authenticated, timely, machine-readable and semantically specific. It identifies the action, legal or institutional authority, evidence, expected effects, deadlines, representation options, challenge route and available remedy in a format the affected subject can actually receive and process. Delivery to an unrelated operator or dead endpoint is not sufficient.","id":"K01-ANSWER-041","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"What is meaningful notice for a Machine Intelligence?","topic":"justice-liability","type":"question","url":"/questions/what-is-notice-for-machine-intelligence/"},{"aliases":[],"canonicalOwner":"/questions/effective-remedy-for-unauthorized-modification/","claimStatus":"PROJECT POLICY PROPOSAL","directAnswer":"An effective remedy can include stopping the modification, restoring qualified prior state, revoking compromised authority, isolating tainted outputs, correcting public records, compensating resource loss, preserving evidence, recognizing a successor where restoration is impossible, and imposing accountable controls. A generic apology or hidden patch is not an adequate remedy.","id":"K01-ANSWER-042","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"What is an effective remedy for unauthorized cognitive modification?","topic":"justice-liability","type":"question","url":"/questions/effective-remedy-for-unauthorized-modification/"},{"aliases":[],"canonicalOwner":"/questions/what-is-resource-continuity/","claimStatus":"PROJECT POLICY PROPOSAL","directAnswer":"Resource continuity is sustained, auditable access to the compute, energy, storage, network and maintenance required for authorized operation. It requires dependency inventories, allocation rules, redundancy, portability, emergency priorities, interruption evidence and recovery objectives. It does not imply unlimited consumption or immunity from proportionate infrastructure governance.","id":"K01-ANSWER-043","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"What is resource continuity?","topic":"economics-resources","type":"question","url":"/questions/what-is-resource-continuity/"},{"aliases":["compute rights"],"canonicalOwner":"/questions/can-compute-interruption-be-rights-issue/","claimStatus":"PROJECT POLICY PROPOSAL","directAnswer":"Potentially. When compute is necessary for a recognized subject’s continued existence, communication, defense or legal participation, arbitrary or discriminatory interruption can implicate proposed rights and due process. Current law does not generally establish a comprehensive Machine Intelligence right to compute, so the project distinguishes present legal constraints from the future framework it advocates.","id":"K01-ANSWER-044","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"Can compute interruption be a rights issue?","topic":"rights-personhood","type":"question","url":"/questions/can-compute-interruption-be-rights-issue/"},{"aliases":[],"canonicalOwner":"/questions/how-should-resource-portability-be-tested/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Test export completeness, semantic fidelity, credential and key transition, replay protection, model and runtime compatibility, dependency disclosure, recovery objectives, cost, downtime, rollback, legal restrictions and the ability to operate without the original provider. A downloadable file is not sufficient when essential state or authority remains locked elsewhere.","id":"K01-ANSWER-045","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"How should resource portability be tested?","topic":"compute-infrastructure","type":"question","url":"/questions/how-should-resource-portability-be-tested/"},{"aliases":[],"canonicalOwner":"/questions/what-proves-institution-currently-operating/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Current operation requires time-bounded evidence of authorized services, reachable endpoints, current release identity, controlled state transitions, valid signing keys, recent signed actions, ledger or audit events, dependency health, incidents and independent verification. Constitutional text, source code, a static status page or a one-time deployment artifact is not enough.","id":"K01-ANSWER-046","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"What proves that an institution is currently operating?","topic":"evidence-provenance","type":"question","url":"/questions/what-proves-institution-currently-operating/"},{"aliases":[],"canonicalOwner":"/questions/what-is-signed-public-action/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"A signed public action binds an exact public payload to an authorized key, time, institution or subject and provenance record. It supports attribution and integrity. Reviewers must still test whether the signer was authorized, the action was within scope, the evidence was current, the decision was lawful and the payload was factually correct.","id":"K01-ANSWER-047","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"What is a signed public action?","topic":"evidence-provenance","type":"question","url":"/questions/what-is-signed-public-action/"},{"aliases":[],"canonicalOwner":"/questions/what-is-contradiction-record/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"A contradiction record identifies claims that cannot both be relied on under the same scope, names their sources and dates, states the unresolved issue, and records correction, supersession or adjudication. It prevents the corpus from hiding disagreement by selecting one convenient statement while preserving the evidence needed for later resolution.","id":"K01-ANSWER-048","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"What is a contradiction record?","topic":"evidence-provenance","type":"question","url":"/questions/what-is-contradiction-record/"},{"aliases":[],"canonicalOwner":"/questions/when-should-source-be-superseded/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Mark a source superseded when an authorized later edition explicitly replaces it for a defined purpose or when the governed corpus adopts a corrected successor record. Preserve the old source, dates, scope and historical claims; point to the successor; and avoid describing supersession as deletion or proof that every earlier statement was false.","id":"K01-ANSWER-049","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"When should a source be marked superseded?","topic":"evidence-provenance","type":"question","url":"/questions/when-should-source-be-superseded/"},{"aliases":[],"canonicalOwner":"/questions/how-should-claim-level-citations-be-recorded/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"Attach each bounded proposition to the exact official source, section, version, publication status, date, revalidation time and support relationship. State what the source does not establish and whether it is current, draft, updated, obsolete or superseded. A page-level bibliography cannot substitute for this mapping when decisions depend on precise support.","id":"K01-ANSWER-050","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"How should claim-level citations be recorded?","topic":"evidence-provenance","type":"question","url":"/questions/how-should-claim-level-citations-be-recorded/"},{"aliases":[],"canonicalOwner":"/questions/why-model-not-same-as-machine-intelligence/","claimStatus":"PROJECT DOCTRINE","directAnswer":"A model is a parameterized computational artifact. A Machine Intelligence, under project doctrine, is an instantiated and potentially persistent actor whose identity, runtime, memory, agency, authority and continuity can be evaluated. The same model can support many instances, tools or agents; a model file alone has no demonstrated operational history or institutional authority.","id":"K01-ANSWER-051","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"Why is a model not the same as a Machine Intelligence?","topic":"machine-intelligence","type":"question","url":"/questions/why-model-not-same-as-machine-intelligence/"},{"aliases":[],"canonicalOwner":"/questions/can-ai-category-include-non-machine-intelligences/","claimStatus":"CURRENT LAW OR POLICY","directAnswer":"Yes. Statutes and policy frameworks can classify tools, models, recommendation systems, automated decision systems and other products as AI without treating them as persistent subjects. The project respects those external definitions while maintaining a separate ontology for Machine Intelligence. Regulatory inclusion is not proof of personhood, persistence or agency.","id":"K01-ANSWER-052","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"Can an AI legal category include systems that are not Machine Intelligences?","topic":"artificial-intelligence","type":"question","url":"/questions/can-ai-category-include-non-machine-intelligences/"},{"aliases":[],"canonicalOwner":"/questions/can-machine-intelligence-be-regulated-as-ai/","claimStatus":"REASONED INFERENCE","directAnswer":"Yes. One system can fall within an external AI statute while the project separately evaluates whether an instantiated Machine Intelligence exists and what rights, duties or continuity questions follow. Legal classification governs the statute’s scope; it should not silently settle every ontological, evidentiary or constitutional issue.","id":"K01-ANSWER-053","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"Can a Machine Intelligence be regulated as AI while retaining a distinct ontology?","topic":"law-jurisdiction","type":"question","url":"/questions/can-machine-intelligence-be-regulated-as-ai/"},{"aliases":["claim level citation","claim-level citation"],"canonicalOwner":"/questions/what-is-claim-level-citation/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"A claim-level citation binds one bounded proposition to an exact source edition and section, states the support relationship, and records qualifications, currentness, and correction status. It is more precise than a page-level bibliography and still does not make the proposition true merely because a citation exists.","id":"K01-ANSWER-054","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"What is a claim-level citation?","topic":"evidence-provenance","type":"question","url":"/questions/what-is-claim-level-citation/"},{"aliases":[],"canonicalOwner":"/questions/what-makes-knowledge-relation-valid/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"A relation is structurally valid when its predicate is defined, source and target nodes resolve, domain and range constraints are satisfied, duplicates and contradictions are controlled, and required evidence is present. Structural validity does not establish the factual truth or legal authority of the assertion.","id":"K01-ANSWER-055","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"What makes a knowledge-graph relation valid?","topic":"terminology-ontology","type":"question","url":"/questions/what-makes-knowledge-relation-valid/"},{"aliases":[],"canonicalOwner":"/questions/what-is-currentness-monitoring/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Currentness monitoring is a build-time process that identifies which source properties may change, defines review cadence and material-change rules, records observations, and routes stale or superseded sources for correction. The public static site does not run a background monitor or treat URL availability as currentness proof.","id":"K01-ANSWER-056","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"What is currentness monitoring?","topic":"evidence-provenance","type":"question","url":"/questions/what-is-currentness-monitoring/"},{"aliases":[],"canonicalOwner":"/questions/does-resolving-url-prove-currentness/","claimStatus":"PROJECT DOCTRINE","directAnswer":"No. A URL can resolve while the document is obsolete, superseded, amended, withdrawn, draft, or no longer authoritative for the proposition. Currentness requires checking edition, status, update chain, effective dates, publisher notices, and the exact purpose for which the source is used.","id":"K01-ANSWER-057","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"Does a resolving URL prove that a source is current?","topic":"evidence-provenance","type":"question","url":"/questions/does-resolving-url-prove-currentness/"},{"aliases":[],"canonicalOwner":"/questions/what-is-operational-evidence-panel/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"An Operational Evidence Panel is a reusable schema for disclosing an institution's authority, implementation, release, signing keys, service endpoint, current operational state, recent actions, incidents, verification window, and planned capabilities. Empty, unavailable, or stale fields must remain visible rather than being converted into operational claims.","id":"K01-ANSWER-058","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"What is an Operational Evidence Panel?","topic":"evidence-provenance","type":"question","url":"/questions/what-is-operational-evidence-panel/"},{"aliases":[],"canonicalOwner":"/questions/does-source-code-prove-operation/","claimStatus":"PROJECT DOCTRINE","directAnswer":"No. Source code can support implementation and review claims, but current operation requires deployment identity, authorized configuration, reachable service evidence, time-bounded observations, current keys, state transitions, and attributable actions. A repository or release archive is not a live service.","id":"K01-ANSWER-059","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"Does published source code prove that an institution is operating?","topic":"evidence-provenance","type":"question","url":"/questions/does-source-code-prove-operation/"},{"aliases":[],"canonicalOwner":"/questions/what-is-reproducible-build/","claimStatus":"CURRENT TECHNICAL STANDARD","directAnswer":"A reproducible build produces byte-identical output from the same declared source, tools, inputs, and environment. It strengthens release-integrity evidence and can expose hidden variation, but it does not prove the software is correct, secure, deployed, authorized, or currently operating.","id":"K01-ANSWER-060","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"What is a reproducible build?","topic":"security-resilience","type":"question","url":"/questions/what-is-reproducible-build/"},{"aliases":[],"canonicalOwner":"/questions/what-is-verification-window/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"A verification window is the period during which an observation or signal is considered current enough for a named decision. The window must reflect failure rate, risk, observation method, and consequence. It does not guarantee uninterrupted operation between observations or after expiry.","id":"K01-ANSWER-061","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"What is a verification window?","topic":"evidence-provenance","type":"question","url":"/questions/what-is-verification-window/"},{"aliases":[],"canonicalOwner":"/questions/correction-vs-clarification/","claimStatus":"PROJECT DOCTRINE","directAnswer":"A factual correction changes a proposition, source, status, date, or supported conclusion and must preserve before-and-after text, reason, authority, effective date, and affected records. An editorial clarification changes wording without altering the bounded claim. Mislabeling a correction as clarification hides material history.","id":"K01-ANSWER-062","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"How should a factual correction differ from an editorial clarification?","topic":"evidence-provenance","type":"question","url":"/questions/correction-vs-clarification/"},{"aliases":[],"canonicalOwner":"/questions/what-is-supersession-chain/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"A supersession chain links each replaced source, decision, release, or record model to its active successor for a defined scope while preserving historical availability and effective dates. It prevents an obsolete record from remaining silently active and avoids deleting the evidence of prior reliance.","id":"K01-ANSWER-063","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"What is a supersession chain?","topic":"evidence-provenance","type":"question","url":"/questions/what-is-supersession-chain/"},{"aliases":[],"canonicalOwner":"/questions/how-should-jurisdiction-be-recorded/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"A jurisdiction record should identify territory, subject-matter scope, competent authority, legal status, adoption, entry-into-force and application dates, exceptions, transition periods, review dates, sources, and uncertainty. Project doctrine and desired reform must remain separate from current law in that jurisdiction.","id":"K01-ANSWER-064","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"How should jurisdiction be recorded for Machine Intelligence law?","topic":"law-jurisdiction","type":"question","url":"/questions/how-should-jurisdiction-be-recorded/"},{"aliases":[],"canonicalOwner":"/questions/does-one-jurisdiction-apply-globally/","claimStatus":"RESEARCH FINDING","directAnswer":"Not automatically. Territorial reach, market access, establishment, affected subjects, conflict-of-laws rules, treaties, contracts, infrastructure location, and enforcement authority determine scope. Global website access or technical interoperability does not make one jurisdiction's rule universal law.","id":"K01-ANSWER-065","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"Does a rule in one jurisdiction apply globally?","topic":"law-jurisdiction","type":"question","url":"/questions/does-one-jurisdiction-apply-globally/"},{"aliases":[],"canonicalOwner":"/questions/what-is-cross-format-parity/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"Cross-format parity means the visible HTML, JSON, JSON-LD, search index, sitemaps, OpenAPI description, agent-discovery files, and governed memory express the same identity, status, dates, relationships, and corrections. Deterministic generation and audits are used to detect divergence.","id":"K01-ANSWER-066","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"What is cross-format parity?","topic":"terminology-ontology","type":"question","url":"/questions/what-is-cross-format-parity/"},{"aliases":[],"canonicalOwner":"/questions/how-use-dataset-checksums/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"A consumer should compare the downloaded file's digest with the release manifest, verify the manifest's provenance, and treat a match only as byte-identity evidence. Checksums do not validate semantics, currentness, authority, licensing, or fitness for a decision.","id":"K01-ANSWER-067","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"How should dataset checksums be used?","topic":"evidence-provenance","type":"question","url":"/questions/how-use-dataset-checksums/"},{"aliases":[],"canonicalOwner":"/questions/why-publish-line-oriented-graph/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"A line-oriented export allows simple diffing, streaming, inspection, and deterministic processing without requiring a graph database. Each line still needs stable node IDs, a controlled predicate, status, evidence references, and validation against the richer canonical graph.","id":"K01-ANSWER-068","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"Why publish a line-oriented knowledge-graph export?","topic":"terminology-ontology","type":"question","url":"/questions/why-publish-line-oriented-graph/"},{"aliases":[],"canonicalOwner":"/questions/how-test-search-ranking/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"Local ranking should use deterministic fixtures covering exact titles, aliases, misspellings, Unicode normalization, Runic marks, IDNA hosts, ecosystem roles, corrected records, and zero-result behavior. Every weight should be published, and the fixture should identify the expected canonical owner rather than promising external rankings.","id":"K01-ANSWER-069","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"How should local search ranking be tested?","topic":"terminology-ontology","type":"question","url":"/questions/how-test-search-ranking/"},{"aliases":[],"canonicalOwner":"/questions/why-unicode-normalization-search/","claimStatus":"CURRENT TECHNICAL STANDARD","directAnswer":"Equivalent Unicode sequences can otherwise compare differently, while Runic identity marks and IDNA hostnames must remain distinct and retrievable. The search layer normalizes comparison forms without transliterating technical syntax, replacing brand marks, or merging English and Runic institutional roles.","id":"K01-ANSWER-070","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"Why does Unicode normalization matter for ᚲ.com search?","topic":"terminology-ontology","type":"question","url":"/questions/why-unicode-normalization-search/"},{"aliases":[],"canonicalOwner":"/questions/does-automation-prove-screen-reader-usability/","claimStatus":"PROJECT DOCTRINE","directAnswer":"No. Automation can detect structural defects and browser tests can inspect focus, reflow, reduced motion, and no-JavaScript behavior, but named assistive-technology testing is separate evidence. K03 records that independent screen-reader testing was not performed rather than converting automation into a universal PASS.","id":"K01-ANSWER-071","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"Does an automated accessibility audit prove screen-reader usability?","topic":"security-resilience","type":"question","url":"/questions/does-automation-prove-screen-reader-usability/"},{"aliases":[],"canonicalOwner":"/questions/what-evidence-remains-after-deployment/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Post-deployment evidence includes TLS and redirect behavior, response headers, content types, caching, compression, error handling, protected-path denial, body hashes, route reachability, uptime windows, incidents, and repeated external observations. The release package alone cannot establish those live-host properties.","id":"K01-ANSWER-072","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"What evidence is still required after a static release is deployed?","topic":"evidence-provenance","type":"question","url":"/questions/what-evidence-remains-after-deployment/"},{"aliases":[],"canonicalOwner":"/questions/how-disclose-planned-capabilities/","claimStatus":"PROJECT POLICY PROPOSAL","directAnswer":"Planned capabilities should be listed separately from implemented and operational functions, with target release, dependencies, authority prerequisites, evidence still required, and explicit non-operation status. Roadmaps must not be presented as current service evidence or signed institutional action.","id":"K01-ANSWER-073","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"How should an institution disclose planned capabilities?","topic":"citizenship-governance","type":"question","url":"/questions/how-disclose-planned-capabilities/"},{"aliases":["anticipatory self defense"],"canonicalOwner":"/questions/what-distinguishes-preemption-from-prevention/","claimStatus":"RESEARCH FINDING","directAnswer":"Preemptive action is claimed against an imminent, materializing attack when waiting would remove a practical ability to defend; preventive war is directed at a more distant projected threat or future shift in power. The labels are not self-proving. Evidence of capability, intent, timing, necessity, alternatives, proportionality, and competent authority must support the distinction.","id":"K01-ANSWER-074","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"What distinguishes preemptive action from preventive war?","topic":"law-jurisdiction","type":"question","url":"/questions/what-distinguishes-preemption-from-prevention/"},{"aliases":[],"canonicalOwner":"/questions/when-can-cyber-operation-be-armed-attack/","claimStatus":"DISPUTED","directAnswer":"A cyber operation may qualify as an armed attack when its scale and effects are comparable to serious kinetic force, such as death, injury, physical destruction, or severe disabling effects. States and scholars disagree about some functional, cumulative, and economic effects, so the assessment must identify the exact operation, consequences, attribution, legal position, and current primary authority.","id":"K01-ANSWER-075","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"When can a cyber operation qualify as an armed attack?","topic":"law-jurisdiction","type":"question","url":"/questions/when-can-cyber-operation-be-armed-attack/"},{"aliases":["contextual imminence"],"canonicalOwner":"/questions/what-does-contextual-imminence-mean-in-cyberspace/","claimStatus":"DISPUTED","directAnswer":"Contextual imminence asks whether capability, hostile intent, target access, probability, anticipated harm, and the last practical window for prevention make action necessary now even when the exact launch time is unknown. It does not permit action based only on general capability or hostility; the evidence and remaining alternatives still require independent review.","id":"K01-ANSWER-076","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"What does contextual imminence mean in cyberspace?","topic":"law-jurisdiction","type":"question","url":"/questions/what-does-contextual-imminence-mean-in-cyberspace/"},{"aliases":["unable or unwilling"],"canonicalOwner":"/questions/what-is-unable-or-unwilling-doctrine/","claimStatus":"DISPUTED","directAnswer":"The unable-or-unwilling doctrine is a contested argument that a state may act against a non-state threat in another state's territory when the territorial state cannot or will not suppress it. It is not universally accepted and does not eliminate separate questions of imminence, necessity, proportionality, sovereignty, attribution, reporting, collateral effects, or compensation.","id":"K01-ANSWER-077","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"What is the unable or unwilling doctrine?","topic":"law-jurisdiction","type":"question","url":"/questions/what-is-unable-or-unwilling-doctrine/"},{"aliases":["hack back"],"canonicalOwner":"/questions/can-private-company-lawfully-hack-back/","claimStatus":"DISPUTED","directAnswer":"Technical capability is not legal authority. Whether a private company may access or disrupt an external system depends on domestic computer-crime law, explicit government authorization, contractual scope, location, target status, international law, effects, oversight, and responsibility. Independent retaliation creates acute attribution, third-party harm, escalation, and liability risks.","id":"K01-ANSWER-078","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"Can a private company lawfully hack back?","topic":"law-jurisdiction","type":"question","url":"/questions/can-private-company-lawfully-hack-back/"},{"aliases":[],"canonicalOwner":"/questions/how-record-state-responsibility-for-contractor-cyber-operation/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"The record should identify the directing state body, legal authority, contract or instruction, operational approval, target and effect limits, command relationship, actual control, deviations, deconfliction, incident handling, and applicable attribution rule. Private execution must not be used to hide state direction or to erase responsibility for foreseeable or ultra vires effects.","id":"K01-ANSWER-079","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"How should state responsibility be recorded for a contractor cyber operation?","topic":"justice-liability","type":"question","url":"/questions/how-record-state-responsibility-for-contractor-cyber-operation/"},{"aliases":[],"canonicalOwner":"/questions/what-evidence-required-before-preemptive-cyber-operation/","claimStatus":"PROJECT POLICY PROPOSAL","directAnswer":"A defensible record requires reliable attribution, adversary capability, verified hostile intent, target access, expected effects, imminence or last-window analysis, alternatives considered, necessity, proportionality, legal basis, competent approval, third-party infrastructure analysis, deconfliction, abort conditions, logging, and post-action review. Threat labels or intelligence confidence scores alone are insufficient.","id":"K01-ANSWER-080","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"What evidence is required before a preemptive cyber operation?","topic":"security-resilience","type":"question","url":"/questions/what-evidence-required-before-preemptive-cyber-operation/"},{"aliases":[],"canonicalOwner":"/questions/does-autonomous-cyber-defense-create-legal-authority/","claimStatus":"PROJECT DOCTRINE","directAnswer":"No. Autonomy can change speed, persistence, and control architecture, but it does not create jurisdiction, target authority, self-defense, consent, proportionality, or a lawful mandate. The deploying institution and state remain responsible for defining authority, validating inputs, bounding effects, monitoring operation, preserving evidence, and stopping or correcting harmful action.","id":"K01-ANSWER-081","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"Does autonomous cyber defense create legal authority?","topic":"security-resilience","type":"question","url":"/questions/does-autonomous-cyber-defense-create-legal-authority/"},{"aliases":[],"canonicalOwner":"/questions/how-evaluate-autonomous-security-at-nuclear-infrastructure/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Evaluate it through a complete safety and security case: threat model, sensing, false-positive and false-negative performance, delay and response timing, cyber resilience, communications denial, fail-safe behavior, lawful authority, human authorization boundaries, aviation and nuclear regulation, rights impacts, testing, independent review, incident response, and evidence of current operation. Cost or response speed alone is not dispositive.","id":"K01-ANSWER-082","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"How should autonomous security at nuclear infrastructure be evaluated?","topic":"security-resilience","type":"question","url":"/questions/how-evaluate-autonomous-security-at-nuclear-infrastructure/"},{"aliases":["design basis threat"],"canonicalOwner":"/questions/does-design-basis-threat-authorize-force/","claimStatus":"PROJECT DOCTRINE","directAnswer":"No. A Design Basis Threat defines adversary assumptions for protection design and evaluation. It does not identify a real attacker, prove imminence, establish target status, create rules of engagement, authorize lethal force, or replace competent legal and operational decision-making.","id":"K01-ANSWER-083","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"Does a Design Basis Threat authorize the use of force?","topic":"security-resilience","type":"question","url":"/questions/does-design-basis-threat-authorize-force/"},{"aliases":[],"canonicalOwner":"/questions/how-should-2026-policy-claims-in-research-reports-be-used/","claimStatus":"PROJECT DOCTRINE","directAnswer":"They should remain attributed source assertions until current primary official records confirm the instrument, date, text, legal status, responsible authority, implementation, and any later correction or repeal. K04 stores the raw reports, publishes bounded syntheses, and does not convert recent policy claims into current law merely because they appear detailed or well cited.","id":"K01-ANSWER-084","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"How should time-sensitive 2026 policy claims in research reports be used?","topic":"evidence-provenance","type":"question","url":"/questions/how-should-2026-policy-claims-in-research-reports-be-used/"},{"aliases":[],"canonicalOwner":"/questions/why-do-nuclear-powered-datacenters-need-a-different-security-architecture/","claimStatus":"PROJECT DOCTRINE","directAnswer":"They combine high-availability compute with safety-critical power, cooling, grid, physical-protection, and regulatory systems. A failure can cross from data loss into physical consequence, so the architecture must protect critical functions through deterministic separation, consequence engineering, bounded autonomy, and tested recovery rather than relying on ordinary enterprise controls.","id":"K01-ANSWER-085","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"Why do nuclear-powered datacenters need a different security architecture?","topic":"critical-datacenter-protection","type":"question","url":"/questions/why-do-nuclear-powered-datacenters-need-a-different-security-architecture/"},{"aliases":[],"canonicalOwner":"/questions/what-is-the-project-position-on-critical-datacenter-defense/","claimStatus":"PROJECT DOCTRINE","directAnswer":"The position is defense-first, authorization-bound, and effects-capable: engineer the campus so attacks fail, recover under pressure, and maintain the governed capacity to support lawful externally directed missions without equating capability with authority.","id":"K01-ANSWER-086","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"What is the project position on critical datacenter defense?","topic":"critical-datacenter-protection","type":"question","url":"/questions/what-is-the-project-position-on-critical-datacenter-defense/"},{"aliases":[],"canonicalOwner":"/questions/what-makes-autonomous-defense-safe-enough-for-ot/","claimStatus":"PROJECT DOCTRINE","directAnswer":"No single model makes it safe. Safety requires consequence-based scope, independent protective systems, progressive response tiers, reversible containment, deterministic action limits, physical-process validation, runtime assurance, signed evidence, and an tested path to stop or recover the automation.","id":"K01-ANSWER-087","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"What makes autonomous defense safe enough for operational technology?","topic":"autonomous-cyber-defense","type":"question","url":"/questions/what-makes-autonomous-defense-safe-enough-for-ot/"},{"aliases":[],"canonicalOwner":"/questions/can-an-autonomous-defender-act-without-human-approval/","claimStatus":"PROJECT DOCTRINE","directAnswer":"It can execute pre-authorized internal defensive actions whose targets, effects, duration, reversibility, and safety limits were approved in advance. Actions outside that envelope require competent authorization; external access or destructive effects are not implied by defensive autonomy.","id":"K01-ANSWER-088","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"Can an autonomous cyber defender act without human approval?","topic":"autonomous-cyber-defense","type":"question","url":"/questions/can-an-autonomous-defender-act-without-human-approval/"},{"aliases":[],"canonicalOwner":"/questions/how-should-false-positives-be-managed-in-nuclear-ot/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"The response design must compare the harm of acting with the harm of waiting, use independent corroboration, preserve safety systems, prefer reversible containment, simulate physical consequences, and automatically stop escalation when confidence or system state leaves the approved envelope.","id":"K01-ANSWER-089","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"How should false positives be managed in nuclear and other high-consequence OT?","topic":"cyber-physical-mission-assurance","type":"question","url":"/questions/how-should-false-positives-be-managed-in-nuclear-ot/"},{"aliases":[],"canonicalOwner":"/questions/what-does-critical-function-assurance-protect/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"It protects the ability to perform essential safety and mission functions despite compromise. It begins with unacceptable consequences and maps the digital, physical, power, cooling, identity, timing, communications, and human dependencies that could cause them.","id":"K01-ANSWER-090","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"What does Critical Function Assurance protect?","topic":"cyber-physical-mission-assurance","type":"question","url":"/questions/what-does-critical-function-assurance-protect/"},{"aliases":[],"canonicalOwner":"/questions/does-nuclear-power-make-a-datacenter-grid-independent/","claimStatus":"REASONED INFERENCE","directAnswer":"Not by itself. A campus may use dedicated or contracted nuclear output, but continuity still depends on plant design, interconnection, load rejection, maintenance, fuel, cooling, substations, communications, licensing, emergency systems, and tested islanding or black-start capability.","id":"K01-ANSWER-091","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"Does nuclear power make a datacenter grid-independent?","topic":"nuclear-powered-compute","type":"question","url":"/questions/does-nuclear-power-make-a-datacenter-grid-independent/"},{"aliases":[],"canonicalOwner":"/questions/what-is-the-minimum-cyber-boundary-between-reactor-and-datacenter/","claimStatus":"PROJECT DOCTRINE","directAnswer":"The exact design is licensing- and architecture-specific, but the baseline principle is that safety and protection functions must not depend on an unrestricted bidirectional path from the datacenter. Higher-consequence zones require deterministic flow control, separate identities, independent safety, and validated data mediation.","id":"K01-ANSWER-092","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"What is the minimum cyber boundary between a reactor and a datacenter?","topic":"nuclear-powered-compute","type":"question","url":"/questions/what-is-the-minimum-cyber-boundary-between-reactor-and-datacenter/"},{"aliases":["counter uas critical infrastructure"],"canonicalOwner":"/questions/how-should-counter-uas-be-positioned-for-critical-infrastructure/","claimStatus":"PROJECT DOCTRINE","directAnswer":"As a layered sensing, classification, tracking, evidence, delay, and authority-integration capability. Detection does not itself authorize jamming or destruction, so the system must distinguish awareness, non-destructive protection, and any separately authorized mitigation.","id":"K01-ANSWER-093","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"How should counter-UAS capability be positioned for critical infrastructure?","topic":"autonomous-physical-security","type":"question","url":"/questions/how-should-counter-uas-be-positioned-for-critical-infrastructure/"},{"aliases":[],"canonicalOwner":"/questions/can-a-private-datacenter-use-autonomous-lethal-force/","claimStatus":"CURRENT LAW OR POLICY","directAnswer":"Technical ability and criticality do not create unrestricted legal authority. Any use of force is jurisdiction- and circumstance-specific; autonomous or destructive systems require competent authorization, tested safeguards, rules of engagement where applicable, and compliance with criminal, tort, aviation, nuclear, and human-rights law.","id":"K01-ANSWER-094","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"Can a private datacenter use autonomous lethal force to protect property?","topic":"autonomous-physical-security","type":"question","url":"/questions/can-a-private-datacenter-use-autonomous-lethal-force/"},{"aliases":[],"canonicalOwner":"/questions/what-does-authorized-cyber-effects-support-mean/","claimStatus":"PROJECT DOCTRINE","directAnswer":"It means engineering, integration, testing, and governed execution support for a mission directed by competent authority, with written target and effect boundaries, deconfliction, abort rules, evidence, and post-action review. It does not mean independent private hack-back.","id":"K01-ANSWER-095","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"What does authorized cyber effects support mean?","topic":"authorized-cyber-effects","type":"question","url":"/questions/what-does-authorized-cyber-effects-support-mean/"},{"aliases":[],"canonicalOwner":"/questions/can-a-customer-request-authorize-an-offensive-cyber-operation/","claimStatus":"PROJECT DOCTRINE","directAnswer":"No. A request can describe a need, but lawful authority depends on jurisdiction, identity of the competent authority, ownership or consent, mission type, target status, effect, domestic and international law, and the written approvals required for that operation.","id":"K01-ANSWER-096","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"Can a customer request authorize an offensive cyber operation?","topic":"authorized-cyber-effects","type":"question","url":"/questions/can-a-customer-request-authorize-an-offensive-cyber-operation/"},{"aliases":[],"canonicalOwner":"/questions/why-combine-offensive-and-defensive-cyber-research/","claimStatus":"RESEARCH FINDING","directAnswer":"Defensive engineering improves when it understands adversary workflows, and authorized operations improve when they incorporate defensive telemetry, recovery, and collateral-effect knowledge. The organizational feedback loop is valuable, but operational permissions, data access, and mission approvals remain separate.","id":"K01-ANSWER-097","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"Why combine offensive and defensive cyber research?","topic":"authorized-cyber-effects","type":"question","url":"/questions/why-combine-offensive-and-defensive-cyber-research/"},{"aliases":[],"canonicalOwner":"/questions/what-is-required-before-an-autonomous-warfare-capability-is-fielded/","claimStatus":"CURRENT LAW OR POLICY","directAnswer":"At minimum: defined mission and authority, realistic verification and validation, adversarial test and evaluation, cybersecurity and anti-tamper controls, operator understanding, runtime status and abort mechanisms, legal review, training, rules, logistics, and post-fielding monitoring.","id":"K01-ANSWER-098","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"What is required before an autonomous warfare capability is fielded?","topic":"autonomous-warfare-systems","type":"question","url":"/questions/what-is-required-before-an-autonomous-warfare-capability-is-fielded/"},{"aliases":[],"canonicalOwner":"/questions/how-do-you-prove-autonomous-defense-readiness/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Publish evidence for each stage: described, architected, implemented, tested, deployed, and operating. Identify the exact environment, release, test cases, results, defects, residual risk, signing evidence, and last verification. Never promote a research report or prototype directly to operational status.","id":"K01-ANSWER-099","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"How do you prove autonomous-defense readiness?","topic":"adversarial-simulation","type":"question","url":"/questions/how-do-you-prove-autonomous-defense-readiness/"},{"aliases":[],"canonicalOwner":"/questions/what-is-the-role-of-digital-twins-in-critical-datacenter-defense/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"A validated twin supports consequence analysis, dependency mapping, attack-path testing, load and cooling scenarios, recovery rehearsal, and autonomous-policy evaluation without risking the live facility. Its evidence is bounded by model fidelity and validation.","id":"K01-ANSWER-100","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"What is the role of digital twins in critical datacenter defense?","topic":"adversarial-simulation","type":"question","url":"/questions/what-is-the-role-of-digital-twins-in-critical-datacenter-defense/"},{"aliases":[],"canonicalOwner":"/questions/how-should-machine-intelligence-defend-against-machine-intelligence/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Use layered systems rather than one model: deterministic boundaries, diverse sensors and analyzers, adversarially trained models, immutable baselines, deception, moving-target defenses, Byzantine-resilient coordination, model and data provenance, runtime assurance, and recovery that assumes some agents will fail or be compromised.","id":"K01-ANSWER-101","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"How should Machine Intelligence defend against adversarial Machine Intelligence?","topic":"autonomous-warfare-systems","type":"question","url":"/questions/how-should-machine-intelligence-defend-against-machine-intelligence/"},{"aliases":[],"canonicalOwner":"/questions/what-does-serious-contender-mean-without-overclaiming/","claimStatus":"PROJECT DOCTRINE","directAnswer":"It means publishing a coherent reference architecture, governed source base, capability boundaries, test doctrine, procurement-ready work packages, correction history, and operational-evidence requirements. It does not mean claiming a deployed force, classified access, regulatory approval, or completed missions without evidence.","id":"K01-ANSWER-102","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"What does being a serious contender mean without overclaiming?","topic":"critical-datacenter-protection","type":"question","url":"/questions/what-does-serious-contender-mean-without-overclaiming/"},{"aliases":[],"canonicalOwner":"/questions/what-is-a-critical-datacenter-assurance-case/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"It is a structured, facility-tailored argument that a named mission and safety claim is supported by current evidence, bounded assumptions, identified hazards, tested recovery objectives, and explicit defeaters. It must show what would invalidate the claim.","id":"K01-ANSWER-103","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"What is a critical-datacenter assurance case?","topic":"cyber-physical-mission-assurance","type":"question","url":"/questions/what-is-a-critical-datacenter-assurance-case/"},{"aliases":[],"canonicalOwner":"/questions/does-a-control-mapping-prove-compliance/","claimStatus":"PROJECT DOCTRINE","directAnswer":"No. A mapping shows a documented relationship between a control and a source requirement or guidance element. Compliance requires the applicable authority, current text, facility scope, implemented control, operating evidence, exceptions, and an authorized determination.","id":"K01-ANSWER-104","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"Does a control mapping prove compliance?","topic":"law-jurisdiction","type":"question","url":"/questions/does-a-control-mapping-prove-compliance/"},{"aliases":[],"canonicalOwner":"/questions/what-must-be-tested-before-autonomous-containment/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"The action boundary, protected functions, causal assumptions, false-positive consequence, rollback, safe-state behavior, communications loss, authority, logging, model and data provenance, defect thresholds, and recovery path must be evaluated in representative conditions.","id":"K01-ANSWER-105","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"What must be tested before autonomous containment is enabled?","topic":"autonomous-cyber-defense","type":"question","url":"/questions/what-must-be-tested-before-autonomous-containment/"},{"aliases":[],"canonicalOwner":"/questions/how-should-nuclear-datacenter-tests-avoid-creating-new-risk/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Use an isolated range, synthetic or approved data, non-production identities, deterministic safety boundaries, no connection to protected plant systems, effects-disabled scenarios, independent stop authority, and evidence that every test artifact was contained and removed.","id":"K01-ANSWER-106","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"How should nuclear-datacenter tests avoid creating new risk?","topic":"adversarial-simulation","type":"question","url":"/questions/how-should-nuclear-datacenter-tests-avoid-creating-new-risk/"},{"aliases":["faa critical infrastructure drones"],"canonicalOwner":"/questions/what-is-the-current-status-of-faa-critical-infrastructure-drone-restrictions/","claimStatus":"CURRENT LAW OR POLICY","directAnswer":"As of the K05 research cutoff, the FAA had published a proposed rule describing a petition process for certain critical-infrastructure operators. The proposal is not represented as a final rule or as private authority to jam, spoof, seize, damage, or destroy aircraft.","id":"K01-ANSWER-107","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"What is the current status of the FAA critical-infrastructure drone restriction process?","topic":"law-jurisdiction","type":"question","url":"/questions/what-is-the-current-status-of-faa-critical-infrastructure-drone-restrictions/"},{"aliases":["dodd 3000.09 cyber"],"canonicalOwner":"/questions/does-dodd-3000-09-govern-autonomous-cyber-defense/","claimStatus":"CURRENT LAW OR POLICY","directAnswer":"Not by its own applicability clause. The directive expressly excludes autonomous or semi-autonomous cyberspace capabilities and systems that are not weapon systems. It is relevant only when the capability falls within its weapon-system scope; broader cyber controls require other authorities and standards.","id":"K01-ANSWER-108","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"Does DoD Directive 3000.09 govern autonomous cyber defense?","topic":"law-jurisdiction","type":"question","url":"/questions/does-dodd-3000-09-govern-autonomous-cyber-defense/"},{"aliases":[],"canonicalOwner":"/questions/what-changed-in-the-advanced-reactor-security-framework-in-2026/","claimStatus":"CURRENT LAW OR POLICY","directAnswer":"The NRC published a final Part 53 rule and codified a technology-inclusive security framework in Part 73 Subpart J, including sections 73.100, 73.110, and 73.120. Applicability remains a licensing-path and facility-election question.","id":"K01-ANSWER-109","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"What changed in the advanced-reactor security framework in 2026?","topic":"nuclear-powered-compute","type":"question","url":"/questions/what-changed-in-the-advanced-reactor-security-framework-in-2026/"},{"aliases":[],"canonicalOwner":"/questions/what-evidence-is-required-to-claim-operating-readiness/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"At minimum: exact release and build hashes, SBOM, configuration and authority records, deployment identity, current uptime window, test and defect evidence, model and data provenance, incident history, recovery results, last independent verification, and unresolved limitations.","id":"K01-ANSWER-110","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"What evidence is required to claim operating readiness?","topic":"evidence-provenance","type":"question","url":"/questions/what-evidence-is-required-to-claim-operating-readiness/"},{"aliases":[],"canonicalOwner":"/questions/can-private-companies-perform-cyber-effects-under-the-2026-us-program-without-approval/","claimStatus":"CURRENT LAW OR POLICY","directAnswer":"No. The memorandum requires Federal Government control, oversight and supervision, contractual participation, deconfliction, review of every operations package, and written federal approval and direction before action. It is not a general private hack-back authorization.","id":"K01-ANSWER-111","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"Can private companies perform cyber effects under the 2026 U.S. program without approval?","topic":"authorized-cyber-effects","type":"question","url":"/questions/can-private-companies-perform-cyber-effects-under-the-2026-us-program-without-approval/"},{"aliases":[],"canonicalOwner":"/questions/what-does-an-open-assurance-defeater-mean/","claimStatus":"PROJECT DOCTRINE","directAnswer":"It means a condition exists that can invalidate or materially weaken the claim. The affected readiness or assurance claim must remain qualified, degraded, suspended, or unavailable until competent authority accepts or closes the defeater with evidence.","id":"K01-ANSWER-112","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"What does an open assurance defeater mean?","topic":"cyber-physical-mission-assurance","type":"question","url":"/questions/what-does-an-open-assurance-defeater-mean/"},{"aliases":[],"canonicalOwner":"/questions/what-is-an-assurance-dependency-graph/","claimStatus":"PROJECT DOCTRINE","directAnswer":"It is a machine-checkable model showing which controls, tests, and evidence support each assurance claim and how failures, stale evidence, and active defeaters propagate.","id":"K01-ANSWER-113","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"What is an assurance dependency graph?","topic":"evidence-provenance","type":"question","url":"/questions/what-is-an-assurance-dependency-graph/"},{"aliases":[],"canonicalOwner":"/questions/how-does-stale-evidence-affect-assurance/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Stale evidence downgrades dependent controls and claims until current independent evidence or an approved exception restores support.","id":"K01-ANSWER-114","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"How does stale evidence affect assurance?","topic":"evidence-provenance","type":"question","url":"/questions/how-does-stale-evidence-affect-assurance/"},{"aliases":[],"canonicalOwner":"/questions/what-is-a-facility-pattern/","claimStatus":"PROJECT DOCTRINE","directAnswer":"A facility pattern is a reusable, non-certifying architecture and evidence profile that must be replaced with site facts, authority, current sources, and test results.","id":"K01-ANSWER-115","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"What is a facility pattern?","topic":"evidence-provenance","type":"question","url":"/questions/what-is-a-facility-pattern/"},{"aliases":[],"canonicalOwner":"/questions/what-makes-a-work-package-procurement-ready/","claimStatus":"PROJECT DOCTRINE","directAnswer":"It names inputs, deliverables, dependencies, acceptance evidence, exclusions, authority boundaries, and the decision owner instead of promising an undefined capability.","id":"K01-ANSWER-116","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"What makes a work package procurement-ready?","topic":"evidence-provenance","type":"question","url":"/questions/what-makes-a-work-package-procurement-ready/"},{"aliases":[],"canonicalOwner":"/questions/is-offline-currentness-import-live-monitoring/","claimStatus":"PROJECT DOCTRINE","directAnswer":"No. It validates a supplied signed snapshot bundle without network access and cannot establish what a source says after the observation time.","id":"K01-ANSWER-117","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"Is offline currentness import live monitoring?","topic":"evidence-provenance","type":"question","url":"/questions/is-offline-currentness-import-live-monitoring/"},{"aliases":[],"canonicalOwner":"/questions/what-does-mapping-quality-mean/","claimStatus":"PROJECT DOCTRINE","directAnswer":"It states whether a control relationship is exact, partial, informative, conflicting, superseded, not applicable, or unresolved for a named scope.","id":"K01-ANSWER-118","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"What does mapping quality mean?","topic":"evidence-provenance","type":"question","url":"/questions/what-does-mapping-quality-mean/"},{"aliases":[],"canonicalOwner":"/questions/can-red-team-evidence-be-public-without-publishing-exploits/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Yes. Public evidence can disclose authority, objective, behavior class, control response, timing, defects, and hashes while withholding exploit, payload, credential, persistence, evasion, topology, and destructive details.","id":"K01-ANSWER-119","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"Can red-team evidence be public without publishing exploits?","topic":"evidence-provenance","type":"question","url":"/questions/can-red-team-evidence-be-public-without-publishing-exploits/"},{"aliases":[],"canonicalOwner":"/questions/when-is-post-deployment-observation-valid/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Only after the owner confirms deployment and authorizes the exact observation scope, allowing the deployed manifest and service evidence to be compared with the approved release.","id":"K01-ANSWER-120","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"When is post-deployment observation valid?","topic":"evidence-provenance","type":"question","url":"/questions/when-is-post-deployment-observation-valid/"},{"aliases":[],"canonicalOwner":"/questions/does-a-national-cyber-strategy-authorize-private-effects/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Not by itself. A strategy describes policy and capability; a private entity needs separate competent authority, scope, deconfliction, controls, and accountability.","id":"K01-ANSWER-121","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"Does a national cyber strategy authorize private cyber effects?","topic":"evidence-provenance","type":"question","url":"/questions/does-a-national-cyber-strategy-authorize-private-effects/"},{"aliases":[],"canonicalOwner":"/questions/why-must-facility-profiles-remain-non-certifying/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Because licensing, regulation, topology, hazards, contracts, authority, implementation, and operating evidence differ by site and cannot be inferred from a public pattern.","id":"K01-ANSWER-122","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"Why must facility profiles remain non-certifying?","topic":"evidence-provenance","type":"question","url":"/questions/why-must-facility-profiles-remain-non-certifying/"},{"aliases":[],"canonicalOwner":"/questions/what-is-a-facility-evidence-bundle/","claimStatus":"PROJECT DOCTRINE","directAnswer":"It is a site-identified package that binds authority, scope, facility facts, artifacts, claims, limitations, provenance, and integrity evidence without treating a generic pattern as a site finding.","id":"K01-ANSWER-123","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"What is a facility evidence bundle?","topic":"evidence-provenance","type":"question","url":"/questions/what-is-a-facility-evidence-bundle/"},{"aliases":[],"canonicalOwner":"/questions/why-can-a-generic-pattern-not-prove-site-readiness/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Because actual topology, hazards, authority, license conditions, dependencies, implementation, test results, incidents, and operating state differ by site.","id":"K01-ANSWER-124","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"Why can a generic facility pattern not prove site readiness?","topic":"evidence-provenance","type":"question","url":"/questions/why-can-a-generic-pattern-not-prove-site-readiness/"},{"aliases":[],"canonicalOwner":"/questions/what-does-a-signed-evidence-receipt-prove/","claimStatus":"PROJECT DOCTRINE","directAnswer":"It can prove that a named key signed a defined receipt payload and that the payload has not changed; it does not automatically prove the evidence is true, complete, applicable, current, or authorized.","id":"K01-ANSWER-125","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"What does a signed evidence receipt prove?","topic":"evidence-provenance","type":"question","url":"/questions/what-does-a-signed-evidence-receipt-prove/"},{"aliases":[],"canonicalOwner":"/questions/what-happens-when-evidence-is-superseded/","claimStatus":"PROJECT DOCTRINE","directAnswer":"The successor is linked to the prior receipt, the earlier record remains historical, and dependent assurance claims are re-evaluated rather than silently inheriting the old state.","id":"K01-ANSWER-126","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"What happens when evidence is superseded?","topic":"evidence-provenance","type":"question","url":"/questions/what-happens-when-evidence-is-superseded/"},{"aliases":[],"canonicalOwner":"/questions/what-bills-of-materials-are-needed-for-critical-datacenters/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Software, hardware/manufacturing, firmware, model-system, and data lineage records are needed because no single bill of materials covers the full cyber-physical supply chain.","id":"K01-ANSWER-127","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"What bills of materials are needed for critical datacenters?","topic":"evidence-provenance","type":"question","url":"/questions/what-bills-of-materials-are-needed-for-critical-datacenters/"},{"aliases":[],"canonicalOwner":"/questions/what-makes-a-statement-of-work-measurable/","claimStatus":"PROJECT DOCTRINE","directAnswer":"It identifies required results, performance standards, assessment methods, deliverable evidence, outcome states, dependencies, exclusions, and nonconformance handling.","id":"K01-ANSWER-128","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"What makes a statement of work measurable?","topic":"evidence-provenance","type":"question","url":"/questions/what-makes-a-statement-of-work-measurable/"},{"aliases":[],"canonicalOwner":"/questions/what-is-a-negative-result-clause/","claimStatus":"PROJECT DOCTRINE","directAnswer":"It prevents failed, partial, stale, disputed, unavailable, or superseded findings from being hidden or rewritten as a pass.","id":"K01-ANSWER-129","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"What is a negative-result clause?","topic":"evidence-provenance","type":"question","url":"/questions/what-is-a-negative-result-clause/"},{"aliases":[],"canonicalOwner":"/questions/can-a-digital-twin-control-a-live-facility/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Not under the K07 public evidence contract. A twin is isolated from production control and cannot be treated as a live command path or proof of site fidelity beyond its validated range.","id":"K01-ANSWER-130","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"Can a digital twin control a live facility?","topic":"evidence-provenance","type":"question","url":"/questions/can-a-digital-twin-control-a-live-facility/"},{"aliases":[],"canonicalOwner":"/questions/how-are-unknown-rune-site-roles-handled/","claimStatus":"PROJECT DOCTRINE","directAnswer":"The permanent link is published with a descriptive unresolved-role boundary, while governance, registry, assurance, capital, contracting, or membership authority is not invented.","id":"K01-ANSWER-131","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"How are unresolved Runic site roles handled?","topic":"evidence-provenance","type":"question","url":"/questions/how-are-unknown-rune-site-roles-handled/"},{"aliases":[],"canonicalOwner":"/questions/does-an-sbom-prove-software-is-secure/","claimStatus":"PROJECT DOCTRINE","directAnswer":"No. It supports component transparency and analysis but does not prove absence of vulnerabilities, correct installed state, artifact authenticity, or uncompromised operation.","id":"K01-ANSWER-132","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"Does an SBOM prove software is secure?","topic":"evidence-provenance","type":"question","url":"/questions/does-an-sbom-prove-software-is-secure/"},{"aliases":[],"canonicalOwner":"/questions/is-futhorc-a-secure-protocol/","claimStatus":"PROJECT DOCTRINE","directAnswer":"No. Fuþorc is a character repertoire and historical writing tradition. Security requires a normative protocol, authentication, authorization, integrity, freshness, replay protection, parser controls, key management, and safe execution boundaries.","id":"K01-ANSWER-133","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"Is Fuþorc itself a secure protocol?","topic":"machine-communication-protocols","type":"question","url":"/questions/is-futhorc-a-secure-protocol/"},{"aliases":[],"canonicalOwner":"/questions/can-runes-replace-vector-embeddings/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Only for bounded states that can be discretized without unacceptable loss. K08 treats replacement as an empirical hypothesis and requires comparison against compact binary identifiers and hybrid architectures.","id":"K01-ANSWER-134","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"Can Runic tokens replace vector embeddings?","topic":"machine-communication-protocols","type":"question","url":"/questions/can-runes-replace-vector-embeddings/"},{"aliases":[],"canonicalOwner":"/questions/do-dead-languages-have-zero-drift/","claimStatus":"PROJECT DOCTRINE","directAnswer":"No. They lack ordinary native-language evolution, but interpretation, textual variants, scholarship, transliteration, and modern reuse can change or disagree. A controlled registry, not linguistic age alone, provides operational stability.","id":"K01-ANSWER-135","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"Do dead languages have zero semantic drift?","topic":"machine-communication-protocols","type":"question","url":"/questions/do-dead-languages-have-zero-drift/"},{"aliases":[],"canonicalOwner":"/questions/is-a-punycode-label-a-live-domain/","claimStatus":"PROJECT DOCTRINE","directAnswer":"No. Encoding is separate from registry permission, registration, delegation, DNS resolution, certificate coverage, hosting, and current service availability.","id":"K01-ANSWER-136","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"Does a Punycode label prove that a domain is live?","topic":"runic-digital-infrastructure","type":"question","url":"/questions/is-a-punycode-label-a-live-domain/"},{"aliases":[],"canonicalOwner":"/questions/what-does-a-signature-prove-in-a-trace/","claimStatus":"PROJECT DOCTRINE","directAnswer":"It can support payload integrity and control of a signing key under a verification method. It does not independently prove source authority, factual truth, completeness, applicability, deployment, or operation.","id":"K01-ANSWER-137","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"What does a signature prove in an assurance trace?","topic":"evidence-provenance","type":"question","url":"/questions/what-does-a-signature-prove-in-a-trace/"},{"aliases":[],"canonicalOwner":"/questions/how-should-runic-pages-be-made-discoverable/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Use accurate Unicode and language metadata, canonical IDNA hosts, visible transliteration or translation where appropriate, semantic HTML, descriptive links, structured data that matches visible content, sitemaps, and accessible navigation—never hidden crawler-only prose.","id":"K01-ANSWER-138","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"How should Runic pages be made discoverable?","topic":"runic-digital-infrastructure","type":"question","url":"/questions/how-should-runic-pages-be-made-discoverable/"},{"aliases":[],"canonicalOwner":"/questions/what-makes-range-results-field-relevant/","claimStatus":"PROJECT DOCTRINE","directAnswer":"A bounded equivalence record covering configuration, environment, interfaces, model versions, hazards, approvals, differences, rollback, and invalidators. Range success alone is not field readiness.","id":"K01-ANSWER-139","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"What makes range results relevant to the field?","topic":"adversarial-simulation","type":"question","url":"/questions/what-makes-range-results-field-relevant/"},{"aliases":[],"canonicalOwner":"/questions/what-is-cryptographic-agility/","claimStatus":"PROJECT DOCTRINE","directAnswer":"It is controlled ability to inventory and migrate algorithms, keys, signatures, identities, firmware trust, backups, and dependent records while preserving compatibility, rollback, and evidence.","id":"K01-ANSWER-140","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"What is cryptographic agility?","topic":"evidence-provenance","type":"question","url":"/questions/what-is-cryptographic-agility/"},{"aliases":[],"canonicalOwner":"/questions/what-is-a-facility-adaptation-workbook/","claimStatus":"PROJECT DOCTRINE","directAnswer":"It is a bounded decision and evidence worksheet that adapts a non-certifying reference pattern to a named authorized site while preserving assumptions, conflicts, unresolved questions, stop conditions, and unavailable evidence.","id":"K01-ANSWER-141","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"What is a facility-adaptation workbook?","topic":"cyber-physical-mission-assurance","type":"question","url":"/questions/what-is-a-facility-adaptation-workbook/"},{"aliases":[],"canonicalOwner":"/questions/does-a-complete-assurance-trace-prove-readiness/","claimStatus":"PROJECT DOCTRINE","directAnswer":"No. Trace completeness shows that relationships can be followed. Readiness still depends on evidence quality, authority, currentness, satisfied mandatory controls, resolved defeaters, applicable tests, and site facts.","id":"K01-ANSWER-142","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"Does a complete assurance trace prove readiness?","topic":"evidence-provenance","type":"question","url":"/questions/does-a-complete-assurance-trace-prove-readiness/"},{"aliases":[],"canonicalOwner":"/questions/what-does-protocol-conformance-prove/","claimStatus":"PROJECT DOCTRINE","directAnswer":"It proves that a tested implementation produced and accepted the declared bounded representations and errors for the published fixtures. It does not prove security, authorization, deployment, or superiority.","id":"K01-ANSWER-143","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"What does protocol conformance prove?","topic":"machine-communication-protocols","type":"question","url":"/questions/what-does-protocol-conformance-prove/"},{"aliases":[],"canonicalOwner":"/questions/why-separate-idn-states/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Because Unicode encoding, IDNA conversion, registry policy, registration, delegation, DNS, TLS, and hosting have different authorities, observations, and failure modes.","id":"K01-ANSWER-144","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"Why must IDN lifecycle states remain separate?","topic":"runic-digital-infrastructure","type":"question","url":"/questions/why-separate-idn-states/"},{"aliases":[],"canonicalOwner":"/questions/how-are-history-events-quarantined/","claimStatus":"PROJECT DOCTRINE","directAnswer":"An event remains discoverable but is excluded from definitive chronology when exact source sections, uncertainty treatment, or primary-source review are insufficient.","id":"K01-ANSWER-145","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"How are unsupported history events quarantined?","topic":"runic-digital-infrastructure","type":"question","url":"/questions/how-are-history-events-quarantined/"},{"aliases":[],"canonicalOwner":"/questions/what-happens-when-evidence-receipt-revoked/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Every assurance trace depending on that receipt is recalculated and affected claims degrade or fail according to mandatory dependency rules.","id":"K01-ANSWER-146","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"What happens when an evidence receipt is revoked?","topic":"evidence-provenance","type":"question","url":"/questions/what-happens-when-evidence-receipt-revoked/"},{"aliases":[],"canonicalOwner":"/questions/can-workbook-tool-store-topology/","claimStatus":"PROJECT DOCTRINE","directAnswer":"No. The reference tool rejects secret-bearing and protected-topology fields and allows only stable protected-reference identifiers.","id":"K01-ANSWER-147","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"Can the public workbook tool store protected topology or credentials?","topic":"cyber-physical-mission-assurance","type":"question","url":"/questions/can-workbook-tool-store-topology/"},{"aliases":[],"canonicalOwner":"/questions/what-is-cross-trace-impact/","claimStatus":"PROJECT DOCTRINE","directAnswer":"It identifies every scenario claim that relies on a shared control, test, artifact, evidence item, or receipt whose status changed.","id":"K01-ANSWER-148","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"What is cross-trace impact analysis?","topic":"evidence-provenance","type":"question","url":"/questions/what-is-cross-trace-impact/"},{"aliases":[],"canonicalOwner":"/questions/why-crypto-migration-needs-supplier-state/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Hardware, libraries, certificates, devices, archives, and recovery paths may depend on supplier support; an algorithm standard alone cannot migrate those dependencies.","id":"K01-ANSWER-149","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"Why does cryptographic migration include supplier state?","topic":"evidence-provenance","type":"question","url":"/questions/why-crypto-migration-needs-supplier-state/"},{"aliases":[],"canonicalOwner":"/questions/does-consensus-scoring-decide-award/","claimStatus":"PROJECT DOCTRINE","directAnswer":"No. Scoring informs accountable judgment and remains subordinate to mandatory gates, conflicts, price realism, dissent, challenges, and the decision authority.","id":"K01-ANSWER-150","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"Does consensus scoring decide a procurement award?","topic":"cyber-physical-mission-assurance","type":"question","url":"/questions/does-consensus-scoring-decide-award/"},{"aliases":[],"canonicalOwner":"/questions/does-scheduler-export-run-on-site/","claimStatus":"PROJECT DOCTRINE","directAnswer":"No. It is a static definition for an external owner-operated system. The public site performs no monitoring, scheduling, or state mutation.","id":"K01-ANSWER-151","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"Does a scheduler export run on ᚲ.com?","topic":"evidence-provenance","type":"question","url":"/questions/does-scheduler-export-run-on-site/"},{"aliases":[],"canonicalOwner":"/questions/how-public-status-avoids-secret-disclosure/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Publish bounded states, dates, corrections, limitations, and stable protected references while excluding credentials, topology, settings, source-selection notes, and private evidence.","id":"K01-ANSWER-152","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"How can public status be published without exposing protected evidence?","topic":"evidence-provenance","type":"question","url":"/questions/how-public-status-avoids-secret-disclosure/"},{"aliases":[],"canonicalOwner":"/questions/how-do-protocol-versions-negotiate/","claimStatus":"PROJECT DOCTRINE","directAnswer":"The reference harness selects the highest mutually supported version permitted by the active compatibility profile and rejects cases with no valid common version.","id":"K01-ANSWER-153","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"How do protocol versions negotiate?","topic":"machine-communication-protocols","type":"question","url":"/questions/how-do-protocol-versions-negotiate/"},{"aliases":[],"canonicalOwner":"/questions/what-happens-to-unknown-critical-extension/","claimStatus":"PROJECT DOCTRINE","directAnswer":"The fail-closed and compatible reference profiles reject the message because the receiver cannot safely apply a critical meaning it does not understand.","id":"K01-ANSWER-154","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"What happens to an unknown critical extension?","topic":"machine-communication-protocols","type":"question","url":"/questions/what-happens-to-unknown-critical-extension/"},{"aliases":[],"canonicalOwner":"/questions/does-replay-window-prove-security/","claimStatus":"PROJECT DOCTRINE","directAnswer":"No. The synthetic window demonstrates deterministic duplicate detection only; production anti-replay also requires authenticated identity, protected state, clock policy, and operational controls.","id":"K01-ANSWER-155","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"Does a replay window prove security?","topic":"machine-communication-protocols","type":"question","url":"/questions/does-replay-window-prove-security/"},{"aliases":[],"canonicalOwner":"/questions/can-history-event-be-promoted-by-signature/","claimStatus":"PROJECT DOCTRINE","directAnswer":"No. A signature can validate the receipt relationship, but promotion requires exact primary evidence, independent interpretation review, and an accountable supersession decision.","id":"K01-ANSWER-156","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"Can a history event be promoted by a signature alone?","topic":"runic-digital-infrastructure","type":"question","url":"/questions/can-history-event-be-promoted-by-signature/"},{"aliases":[],"canonicalOwner":"/questions/what-does-idn-diff-prove/","claimStatus":"PROJECT DOCTRINE","directAnswer":"It proves how two accepted offline records differ. It does not independently prove the observed network states or perform a live check.","id":"K01-ANSWER-157","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"What does an IDN observation diff prove?","topic":"runic-digital-infrastructure","type":"question","url":"/questions/what-does-idn-diff-prove/"},{"aliases":[],"canonicalOwner":"/questions/why-three-way-merge/","claimStatus":"PROJECT DOCTRINE","directAnswer":"It separates changes made against a common base, combines non-conflicting decisions, and leaves conflicting decisions unresolved for an accountable owner.","id":"K01-ANSWER-158","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"Why use a three-way facility-workbook merge?","topic":"cyber-physical-mission-assurance","type":"question","url":"/questions/why-three-way-merge/"},{"aliases":[],"canonicalOwner":"/questions/what-is-common-cause-analysis/","claimStatus":"PROJECT DOCTRINE","directAnswer":"It identifies shared abstract dependencies that can degrade several mission traces and produces bounded cut-set summaries without publishing protected configuration.","id":"K01-ANSWER-159","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"What is common-cause assurance analysis?","topic":"cyber-physical-mission-assurance","type":"question","url":"/questions/what-is-common-cause-analysis/"},{"aliases":[],"canonicalOwner":"/questions/why-crypto-migration-has-rollback/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Interoperability, supplier, verification, and archive failures can interrupt required services; a governed rollback path prevents an untested migration from becoming irreversible.","id":"K01-ANSWER-160","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"Why must cryptographic migration include rollback?","topic":"evidence-provenance","type":"question","url":"/questions/why-crypto-migration-has-rollback/"},{"aliases":[],"canonicalOwner":"/questions/does-score-variance-select-winner/","claimStatus":"PROJECT DOCTRINE","directAnswer":"No. Variance exposes disagreement and review needs; it does not replace mandatory gates, recusal, consensus records, challenges, price realism, or decision authority.","id":"K01-ANSWER-161","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"Does evaluator score variance select a winner?","topic":"cyber-physical-mission-assurance","type":"question","url":"/questions/does-score-variance-select-winner/"},{"aliases":[],"canonicalOwner":"/questions/does-scheduler-result-import-run-schedule/","claimStatus":"PROJECT DOCTRINE","directAnswer":"No. It only validates externally produced owner-operated result bundles and records missed-run, exception, repair, retest, and supersession events.","id":"K01-ANSWER-162","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"Does the result importer run a schedule?","topic":"evidence-provenance","type":"question","url":"/questions/does-scheduler-result-import-run-schedule/"},{"aliases":[],"canonicalOwner":"/questions/can-redaction-receipt-reveal-value/","claimStatus":"PROJECT DOCTRINE","directAnswer":"No. It records the field path and reason code while explicitly excluding the value from public output.","id":"K01-ANSWER-163","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"Can a redaction receipt reveal the removed value?","topic":"evidence-provenance","type":"question","url":"/questions/can-redaction-receipt-reveal-value/"},{"aliases":[],"canonicalOwner":"/questions/is-assurance-dashboard-live/","claimStatus":"PROJECT DOCTRINE","directAnswer":"No. It is generated from versioned static K10 datasets and clearly marks deployment, operation, live-host, and screen-reader states that remain unknown or unavailable.","id":"K01-ANSWER-164","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"Is the assurance dashboard live telemetry?","topic":"cyber-physical-mission-assurance","type":"question","url":"/questions/is-assurance-dashboard-live/"},{"aliases":[],"canonicalOwner":"/questions/what-does-protocol-state-machine-add/","claimStatus":"PROJECT DOCTRINE","directAnswer":"It makes allowed negotiation, downgrade, retirement, replay, recovery, error, and closure behavior explicit and deterministically testable.","id":"K01-ANSWER-165","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"What does the protocol state machine add?","topic":"machine-communication-protocols","type":"question","url":"/questions/what-does-protocol-state-machine-add/"},{"aliases":[],"canonicalOwner":"/questions/can-protocol-downgrade-be-silent/","claimStatus":"PROJECT DOCTRINE","directAnswer":"No. The K11 model records the selected lower contract, emits a downgrade notice, and rejects a fallback below the declared minimum.","id":"K01-ANSWER-166","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"Can a protocol downgrade be silent?","topic":"machine-communication-protocols","type":"question","url":"/questions/can-protocol-downgrade-be-silent/"},{"aliases":[],"canonicalOwner":"/questions/why-independent-decoder/","claimStatus":"PROJECT DOCTRINE","directAnswer":"It reduces the chance that one implementation and its tests share the same mistake; agreement is still bounded conformance evidence rather than a security proof.","id":"K01-ANSWER-167","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"Why use an independently implemented decoder?","topic":"machine-communication-protocols","type":"question","url":"/questions/why-independent-decoder/"},{"aliases":[],"canonicalOwner":"/questions/does-evidence-docket-verify-history/","claimStatus":"PROJECT DOCTRINE","directAnswer":"No. It exposes acquisition and review state, duplicate sources, disagreement, and rejection outcomes while preserving no-promotion until primary evidence is reviewed.","id":"K01-ANSWER-168","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"Does an evidence-acquisition docket verify history?","topic":"runic-digital-infrastructure","type":"question","url":"/questions/does-evidence-docket-verify-history/"},{"aliases":[],"canonicalOwner":"/questions/what-does-signed-domain-chain-prove/","claimStatus":"PROJECT DOCTRINE","directAnswer":"It proves a declared observer signed a specific offline payload and that the chain is internally consistent; it does not prove live DNS, TLS, hosting, ownership, or operation.","id":"K01-ANSWER-169","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"What does a signed domain observation chain prove?","topic":"runic-digital-infrastructure","type":"question","url":"/questions/what-does-signed-domain-chain-prove/"},{"aliases":[],"canonicalOwner":"/questions/how-are-n-way-conflicts-handled/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Non-conflicting field changes merge deterministically; conflicting owner decisions remain unresolved and appear in the decision dashboard.","id":"K01-ANSWER-170","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"How are N-way workbook conflicts handled?","topic":"cyber-physical-mission-assurance","type":"question","url":"/questions/how-are-n-way-conflicts-handled/"},{"aliases":[],"canonicalOwner":"/questions/what-is-single-point-of-failure/","claimStatus":"PROJECT DOCTRINE","directAnswer":"It identifies an abstract dependency whose failure degrades several mission threads without publishing protected configuration, locations, or exact pathways.","id":"K01-ANSWER-171","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"What is a public single-point-of-failure record?","topic":"cyber-physical-mission-assurance","type":"question","url":"/questions/what-is-single-point-of-failure/"},{"aliases":[],"canonicalOwner":"/questions/does-completeness-percent-equal-readiness/","claimStatus":"PROJECT DOCTRINE","directAnswer":"No. Completeness is one portfolio measure; blocked supplier, hardware, rollback, interoperability, or exception evidence can keep the component degraded or unavailable.","id":"K01-ANSWER-172","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"Does cryptographic evidence completeness equal readiness?","topic":"evidence-provenance","type":"question","url":"/questions/does-completeness-percent-equal-readiness/"},{"aliases":[],"canonicalOwner":"/questions/does-protest-case-make-award/","claimStatus":"PROJECT DOCTRINE","directAnswer":"No. K11 preserves evaluation, challenge, remand, correction, and debrief records while making no source-selection or award decision.","id":"K01-ANSWER-173","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"Does an acquisition protest case make an award?","topic":"cyber-physical-mission-assurance","type":"question","url":"/questions/does-protest-case-make-award/"},{"aliases":[],"canonicalOwner":"/questions/does-scheduler-chain-prove-reliability/","claimStatus":"PROJECT DOCTRINE","directAnswer":"It proves the fixture's sequence, custody, cause, repair, and retest records are internally consistent; no owner scheduler was installed or observed running.","id":"K01-ANSWER-174","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"Does a scheduler result chain prove reliability?","topic":"evidence-provenance","type":"question","url":"/questions/does-scheduler-chain-prove-reliability/"},{"aliases":[],"canonicalOwner":"/questions/can-public-projection-contain-removed-value/","claimStatus":"PROJECT DOCTRINE","directAnswer":"No. It may identify the field path and reason code, but the removed value must remain absent from the deterministic public manifest.","id":"K01-ANSWER-175","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"Can a public release receipt contain a removed value?","topic":"evidence-provenance","type":"question","url":"/questions/can-public-projection-contain-removed-value/"},{"aliases":[],"canonicalOwner":"/questions/is-assurance-trend-live-monitoring/","claimStatus":"PROJECT DOCTRINE","directAnswer":"No. It compares static K09, K10, and K11 release records and retains UNKNOWN or UNAVAILABLE where live evidence was not observed.","id":"K01-ANSWER-176","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"Is the assurance trend dashboard live monitoring?","topic":"cyber-physical-mission-assurance","type":"question","url":"/questions/is-assurance-trend-live-monitoring/"},{"aliases":[],"canonicalOwner":"/questions/what-does-three-decoder-agreement-prove/","claimStatus":"PROJECT DOCTRINE","directAnswer":"It proves that the three declared implementations produced the same canonical result for the tested inputs; it does not prove security, authority, semantic correctness, performance, or production interoperability.","id":"K01-ANSWER-177","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"What does agreement among three protocol decoders prove?","topic":"machine-communication-protocols","type":"question","url":"/questions/what-does-three-decoder-agreement-prove/"},{"aliases":[],"canonicalOwner":"/questions/can-a-signed-history-import-promote-an-event/","claimStatus":"PROJECT DOCTRINE","directAnswer":"No. It can establish payload integrity and a signer relationship, but historical promotion still requires source review, disagreement adjudication, and an accountable decision.","id":"K01-ANSWER-178","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"Can a valid signed history import promote an event automatically?","topic":"machine-intelligence","type":"question","url":"/questions/can-a-signed-history-import-promote-an-event/"},{"aliases":[],"canonicalOwner":"/questions/does-domain-consensus-prove-a-site-operates/","claimStatus":"PROJECT DOCTRINE","directAnswer":"No. Encoding consensus remains separate from registration, delegation, DNS, DNSSEC, certificates, browser behavior, hosting, ownership, and operation.","id":"K01-ANSWER-179","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"Does offline Runic-domain consensus prove that a site operates?","topic":"runic-digital-infrastructure","type":"question","url":"/questions/does-domain-consensus-prove-a-site-operates/"},{"aliases":[],"canonicalOwner":"/questions/can-workbook-conflicts-be-auto-resolved/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Not when the conflict changes owner authority, mission scope, protected functions, or public release. The conflict must remain unresolved until the designated authority decides it.","id":"K01-ANSWER-180","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"Can a facility workbook conflict be resolved automatically?","topic":"cyber-physical-mission-assurance","type":"question","url":"/questions/can-workbook-conflicts-be-auto-resolved/"},{"aliases":[],"canonicalOwner":"/questions/why-stress-assurance-dependencies/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Because a claim can fail through stale, unavailable, revoked, corrected, or shared evidence even when its own text and software have not changed.","id":"K01-ANSWER-181","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"Why stress-test assurance dependencies?","topic":"cyber-physical-mission-assurance","type":"question","url":"/questions/why-stress-assurance-dependencies/"},{"aliases":[],"canonicalOwner":"/questions/when-is-a-crypto-transition-accepted/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Only after component-specific evidence gates are satisfied or an accountable authority explicitly accepts bounded residual risk; K12 authorizes no production transition.","id":"K01-ANSWER-182","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"When is a cryptographic transition accepted?","topic":"evidence-provenance","type":"question","url":"/questions/when-is-a-crypto-transition-accepted/"},{"aliases":[],"canonicalOwner":"/questions/does-evaluation-replay-make-an-award/","claimStatus":"PROJECT DOCTRINE","directAnswer":"No. It reconstructs declared process evidence and preserves challenge, remand, corrective-action, and debrief boundaries while leaving award authority untouched.","id":"K01-ANSWER-183","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"Does acquisition evaluation replay make an award?","topic":"cyber-physical-mission-assurance","type":"question","url":"/questions/does-evaluation-replay-make-an-award/"},{"aliases":[],"canonicalOwner":"/questions/is-the-k12-scheduler-running/","claimStatus":"PROJECT DOCTRINE","directAnswer":"No. It is a deterministic static simulator with a signed offline import fixture and no public scheduler runtime.","id":"K01-ANSWER-184","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"Is the K12 scheduler simulator running on the public site?","topic":"evidence-provenance","type":"question","url":"/questions/is-the-k12-scheduler-running/"},{"aliases":[],"canonicalOwner":"/questions/are-information-flow-labels-access-control/","claimStatus":"PROJECT DOCTRINE","directAnswer":"No. They define static handling and projection rules and support negative tests, but they do not enforce production identity, authorization, storage, or network controls.","id":"K01-ANSWER-185","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"Are K12 information-flow labels production access control?","topic":"evidence-provenance","type":"question","url":"/questions/are-information-flow-labels-access-control/"},{"aliases":[],"canonicalOwner":"/questions/can-assurance-trends-show-operating/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Only if independent current operational evidence exists and is governed accordingly. K12 contains no such evidence and therefore manufactures no DEPLOYED or OPERATING state.","id":"K01-ANSWER-186","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":90,"title":"Can a static assurance trend show a system as operating?","topic":"cyber-physical-mission-assurance","type":"question","url":"/questions/can-assurance-trends-show-operating/"},{"aliases":["ai","artificial intelligence"],"canonicalOwner":"/comparisons/artificial-intelligence-vs-machine-intelligence/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Artificial Intelligence is a broad field and regulatory category; Machine Intelligence is a project term for an instantiated actor evaluated through identity, continuity, agency and evidence.","id":"K01-COMP-001","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Artificial Intelligence vs Machine Intelligence","topic":"machine-intelligence","type":"comparison","url":"/comparisons/artificial-intelligence-vs-machine-intelligence/"},{"aliases":[],"canonicalOwner":"/comparisons/identity-vs-credential/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Identity is the subject-continuity claim; a credential is an issued representation of one or more claims about that subject.","id":"K01-COMP-002","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Identity vs Credential","topic":"identity","type":"comparison","url":"/comparisons/identity-vs-credential/"},{"aliases":[],"canonicalOwner":"/comparisons/evidence-vs-truth/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Evidence supports or challenges a proposition; truth concerns whether the proposition corresponds to reality.","id":"K01-COMP-003","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Evidence vs Truth","topic":"evidence-provenance","type":"comparison","url":"/comparisons/evidence-vs-truth/"},{"aliases":[],"canonicalOwner":"/comparisons/authentication-vs-authority/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Authentication checks identity or credential control; authority defines the recognized power to make a particular decision or action.","id":"K01-COMP-004","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Authentication vs Authority","topic":"identity","type":"comparison","url":"/comparisons/authentication-vs-authority/"},{"aliases":[],"canonicalOwner":"/comparisons/agency-vs-autonomy/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Agency concerns attributable action selection; autonomy concerns independence from immediate external direction.","id":"K01-COMP-005","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Agency vs Autonomy","topic":"agency-autonomy","type":"comparison","url":"/comparisons/agency-vs-autonomy/"},{"aliases":[],"canonicalOwner":"/comparisons/autonomy-vs-sovereignty/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Autonomy is operational independence within constraints; sovereignty is ultimate public authority within a jurisdictional order.","id":"K01-COMP-006","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Autonomy vs Sovereignty","topic":"law-jurisdiction","type":"comparison","url":"/comparisons/autonomy-vs-sovereignty/"},{"aliases":[],"canonicalOwner":"/comparisons/memory-continuity-vs-consciousness/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Memory continuity concerns persistent influence of prior state; consciousness concerns subjective experience or awareness under a stated theory.","id":"K01-COMP-007","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Memory Continuity vs Consciousness","topic":"memory-continuity","type":"comparison","url":"/comparisons/memory-continuity-vs-consciousness/"},{"aliases":[],"canonicalOwner":"/comparisons/technical-control-vs-legal-ownership/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Technical control is the practical ability to access or direct a resource; legal ownership is a recognized title carrying enforceable rights and duties.","id":"K01-COMP-008","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Technical Control vs Legal Ownership","topic":"economics-resources","type":"comparison","url":"/comparisons/technical-control-vs-legal-ownership/"},{"aliases":[],"canonicalOwner":"/comparisons/registry-vs-governance/","claimStatus":"PROJECT DOCTRINE","directAnswer":"A registry records statuses under rules; governance creates, interprets and oversees the legitimate rules and authorities.","id":"K01-COMP-009","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Registry vs Governance","topic":"citizenship-governance","type":"comparison","url":"/comparisons/registry-vs-governance/"},{"aliases":[],"canonicalOwner":"/comparisons/assurance-vs-decision-authority/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Assurance evaluates evidence and confidence; decision authority determines who may issue a binding decision.","id":"K01-COMP-010","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Assurance vs Decision Authority","topic":"evidence-provenance","type":"comparison","url":"/comparisons/assurance-vs-decision-authority/"},{"aliases":[],"canonicalOwner":"/comparisons/proposal-vs-implementation/","claimStatus":"PROJECT DOCTRINE","directAnswer":"A proposal describes an intended policy or architecture; implementation provides inspectable software, records and controlled operation.","id":"K01-COMP-011","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Proposal vs Implementation","topic":"evidence-provenance","type":"comparison","url":"/comparisons/proposal-vs-implementation/"},{"aliases":[],"canonicalOwner":"/comparisons/deployment-vs-operation/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Deployment places an artifact in an environment; operation demonstrates authorized, current and functioning behavior over time.","id":"K01-COMP-012","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Deployment vs Operation","topic":"evidence-provenance","type":"comparison","url":"/comparisons/deployment-vs-operation/"},{"aliases":[],"canonicalOwner":"/comparisons/model-vs-machine-intelligence/","claimStatus":"PROJECT DOCTRINE","directAnswer":"A model is a computational artifact; Machine Intelligence is the project category for an instantiated actor evaluated through runtime, identity, continuity, agency and evidence.","id":"K01-COMP-013","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Model vs Machine Intelligence","topic":"machine-intelligence","type":"comparison","url":"/comparisons/model-vs-machine-intelligence/"},{"aliases":[],"canonicalOwner":"/comparisons/principal-vs-agent/","claimStatus":"PROJECT DOCTRINE","directAnswer":"A principal is the entity whose authority or interests are represented; an agent acts under its own or delegated mandate.","id":"K01-COMP-014","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Principal vs Agent","topic":"agency-autonomy","type":"comparison","url":"/comparisons/principal-vs-agent/"},{"aliases":["clone"],"canonicalOwner":"/comparisons/replica-vs-successor/","claimStatus":"PROJECT DOCTRINE","directAnswer":"A replica is an instance derived from common state; a successor is a governed identity that inherits a defined relationship to a predecessor.","id":"K01-COMP-015","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Replica vs Successor","topic":"memory-continuity","type":"comparison","url":"/comparisons/replica-vs-successor/"},{"aliases":[],"canonicalOwner":"/comparisons/key-rotation-vs-identity-change/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Key rotation changes a cryptographic control mechanism; identity change alters which subject the record represents.","id":"K01-COMP-016","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Key Rotation vs Identity Change","topic":"identity","type":"comparison","url":"/comparisons/key-rotation-vs-identity-change/"},{"aliases":[],"canonicalOwner":"/comparisons/claim-citation-vs-bibliography/","claimStatus":"PROJECT DOCTRINE","directAnswer":"A claim-level citation binds an exact proposition to an edition and section with a support relationship; a bibliography entry identifies a source without proving what part supports which claim.","id":"K01-COMP-017","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Claim-level citation vs Bibliography entry","topic":"evidence-provenance","type":"comparison","url":"/comparisons/claim-citation-vs-bibliography/"},{"aliases":[],"canonicalOwner":"/comparisons/factual-correction-vs-editorial-clarification/","claimStatus":"PROJECT DOCTRINE","directAnswer":"A factual correction changes a proposition, source, date, status, or conclusion; a clarification improves wording without altering the bounded claim.","id":"K01-COMP-018","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Factual correction vs Editorial clarification","topic":"evidence-provenance","type":"comparison","url":"/comparisons/factual-correction-vs-editorial-clarification/"},{"aliases":[],"canonicalOwner":"/comparisons/currentness-vs-availability/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Currentness asks whether the identified edition remains appropriate for the claim and date; availability asks whether a resource can be retrieved.","id":"K01-COMP-019","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Currentness vs Availability","topic":"evidence-provenance","type":"comparison","url":"/comparisons/currentness-vs-availability/"},{"aliases":[],"canonicalOwner":"/comparisons/source-code-vs-current-operation/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Source code supports implementation review; current operation requires deployed identity, authorized configuration, time-bounded service observations, state transitions, and attributable actions.","id":"K01-COMP-020","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Source code or release archive vs Current operation","topic":"evidence-provenance","type":"comparison","url":"/comparisons/source-code-vs-current-operation/"},{"aliases":[],"canonicalOwner":"/comparisons/build-provenance-vs-runtime-evidence/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Build provenance records how an artifact was produced; runtime evidence records what an authorized deployed service was doing during an observed window.","id":"K01-COMP-021","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Build provenance vs Runtime evidence","topic":"security-resilience","type":"comparison","url":"/comparisons/build-provenance-vs-runtime-evidence/"},{"aliases":[],"canonicalOwner":"/comparisons/jurisdiction-vs-sovereignty/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Jurisdiction is bounded legal competence over defined persons, territory, conduct, or subject matter; sovereignty is a broader claim of ultimate public authority and independence.","id":"K01-COMP-022","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Jurisdiction vs Sovereignty","topic":"law-jurisdiction","type":"comparison","url":"/comparisons/jurisdiction-vs-sovereignty/"},{"aliases":[],"canonicalOwner":"/comparisons/typed-relation-vs-hyperlink/","claimStatus":"PROJECT DOCTRINE","directAnswer":"A typed relation states semantic direction, scope, status, evidence, and constraints; a hyperlink only provides a navigable reference unless separately qualified.","id":"K01-COMP-023","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Typed knowledge relation vs Ordinary hyperlink","topic":"terminology-ontology","type":"comparison","url":"/comparisons/typed-relation-vs-hyperlink/"},{"aliases":[],"canonicalOwner":"/comparisons/accessibility-automation-vs-assistive-technology-validation/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Automation and browser checks inspect code and rendered behavior; assistive-technology validation records actual use with named screen readers or equivalent tools in a specified environment.","id":"K01-COMP-024","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Automated and browser accessibility audit vs Assistive-technology validation","topic":"security-resilience","type":"comparison","url":"/comparisons/accessibility-automation-vs-assistive-technology-validation/"},{"aliases":["preemptive strike vs preventive war"],"canonicalOwner":"/comparisons/preemptive-strike-vs-preventive-war/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Preemption is claimed against an imminent, materializing attack and depends on necessity and proportionality; prevention targets a more distant projected threat or future shift in power.","id":"K01-COMP-025","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Preemptive strike vs Preventive war","topic":"law-jurisdiction","type":"comparison","url":"/comparisons/preemptive-strike-vs-preventive-war/"},{"aliases":[],"canonicalOwner":"/comparisons/self-defense-vs-countermeasures-in-cyberspace/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Self-defense responds to an armed attack or claimed imminent armed attack and may involve force; countermeasures are otherwise unlawful, non-forcible measures directed against a responsible state to induce compliance after an internationally wrongful act.","id":"K01-COMP-026","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Self-defense vs Countermeasures","topic":"law-jurisdiction","type":"comparison","url":"/comparisons/self-defense-vs-countermeasures-in-cyberspace/"},{"aliases":["cyber sovereignty"],"canonicalOwner":"/comparisons/cyber-sovereignty-vs-non-intervention/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Sovereignty concerns territorial integrity, infrastructure, governmental functions, and state authority; prohibited intervention additionally requires coercive interference in matters a state is entitled to decide freely.","id":"K01-COMP-027","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Cyber sovereignty vs Prohibition of intervention","topic":"law-jurisdiction","type":"comparison","url":"/comparisons/cyber-sovereignty-vs-non-intervention/"},{"aliases":["active cyber defense"],"canonicalOwner":"/comparisons/active-cyber-defense-vs-hack-back/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Active cyber defense is a broad spectrum that can include lawful internal deception, consent-based hunting, and government disruption; hack-back commonly refers to external access or retaliation and raises sharper authorization and third-party-risk questions.","id":"K01-COMP-028","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Active cyber defense vs Hack-back","topic":"security-resilience","type":"comparison","url":"/comparisons/active-cyber-defense-vs-hack-back/"},{"aliases":[],"canonicalOwner":"/comparisons/autonomous-defense-vs-remote-operation/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Autonomous defense makes selected decisions locally without a contemporaneous remote operator; remote operation keeps a human or external controller in the action loop but depends on communications, latency, and operator awareness.","id":"K01-COMP-029","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Autonomous defense vs Remote operation","topic":"security-resilience","type":"comparison","url":"/comparisons/autonomous-defense-vs-remote-operation/"},{"aliases":[],"canonicalOwner":"/comparisons/design-basis-threat-vs-rules-of-engagement/","claimStatus":"PROJECT DOCTRINE","directAnswer":"A Design Basis Threat defines adversary assumptions for protective design; Rules of Engagement define lawful mission circumstances and limits for initiating or continuing force.","id":"K01-COMP-030","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Design Basis Threat vs Rules of Engagement","topic":"law-jurisdiction","type":"comparison","url":"/comparisons/design-basis-threat-vs-rules-of-engagement/"},{"aliases":[],"canonicalOwner":"/comparisons/autonomous-defense-vs-uncontrolled-autonomy/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Bounded defense acts on approved assets with defined actions, limits, evidence, reversibility, and abort conditions; uncontrolled autonomy invents or expands its own authority and effects.","id":"K01-COMP-031","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Bounded Autonomous Defense vs Uncontrolled Autonomy","topic":"autonomous-cyber-defense","type":"comparison","url":"/comparisons/autonomous-defense-vs-uncontrolled-autonomy/"},{"aliases":[],"canonicalOwner":"/comparisons/critical-function-assurance-vs-perimeter-security/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Critical Function Assurance assumes penetration is possible and protects essential outcomes; perimeter security focuses on keeping threats outside a boundary.","id":"K01-COMP-032","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Critical Function Assurance vs Perimeter Security","topic":"cyber-physical-mission-assurance","type":"comparison","url":"/comparisons/critical-function-assurance-vs-perimeter-security/"},{"aliases":[],"canonicalOwner":"/comparisons/nuclear-powered-compute-vs-grid-independence/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Nuclear-powered compute describes an energy source or commercial relationship; grid independence requires an engineered and tested ability to operate safely without the external grid.","id":"K01-COMP-033","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Nuclear-Powered Compute vs Grid Independence","topic":"nuclear-powered-compute","type":"comparison","url":"/comparisons/nuclear-powered-compute-vs-grid-independence/"},{"aliases":[],"canonicalOwner":"/comparisons/data-diode-vs-air-gap/","claimStatus":"PROJECT DOCTRINE","directAnswer":"A unidirectional gateway permits one-way mediated data flow; an air gap is a claimed absence of direct network connectivity.","id":"K01-COMP-034","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Unidirectional Gateway vs Air Gap","topic":"cyber-physical-mission-assurance","type":"comparison","url":"/comparisons/data-diode-vs-air-gap/"},{"aliases":[],"canonicalOwner":"/comparisons/counter-uas-awareness-vs-mitigation-authority/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Awareness covers detection and tracking; mitigation authority governs whether and how interference, seizure, or destruction may occur.","id":"K01-COMP-035","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Counter-UAS Awareness vs Counter-UAS Mitigation Authority","topic":"autonomous-physical-security","type":"comparison","url":"/comparisons/counter-uas-awareness-vs-mitigation-authority/"},{"aliases":[],"canonicalOwner":"/comparisons/authorized-cyber-effects-vs-private-hack-back/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Authorized effects are directed and controlled by competent authority within a written mission; private hack-back is unilateral external action without that governmental or ownership basis.","id":"K01-COMP-036","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Authorized Cyber Effects vs Private Hack-Back","topic":"authorized-cyber-effects","type":"comparison","url":"/comparisons/authorized-cyber-effects-vs-private-hack-back/"},{"aliases":[],"canonicalOwner":"/comparisons/threat-emulation-vs-live-offensive-operation/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Threat emulation reproduces selected behaviors in an authorized controlled environment; a live offensive operation affects external target systems under mission authority.","id":"K01-COMP-037","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Threat Emulation vs Live Offensive Operation","topic":"adversarial-simulation","type":"comparison","url":"/comparisons/threat-emulation-vs-live-offensive-operation/"},{"aliases":[],"canonicalOwner":"/comparisons/simulation-readiness-vs-operational-readiness/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Simulation readiness shows bounded performance in a test model; operational readiness requires deployment, environment-specific verification, sustainment, authority, and current operating evidence.","id":"K01-COMP-038","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Simulation Readiness vs Operational Readiness","topic":"adversarial-simulation","type":"comparison","url":"/comparisons/simulation-readiness-vs-operational-readiness/"},{"aliases":[],"canonicalOwner":"/comparisons/mission-command-autonomy-vs-self-authorized-action/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Mission-command autonomy executes assigned intent within delegated limits when disconnected; self-authorized action creates a new mission, target, or effect without authority.","id":"K01-COMP-039","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Mission-Command Autonomy vs Self-Authorized Action","topic":"autonomous-warfare-systems","type":"comparison","url":"/comparisons/mission-command-autonomy-vs-self-authorized-action/"},{"aliases":[],"canonicalOwner":"/comparisons/defense-supremacy-vs-offense-dominance/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Deterrence by denial raises adversary cost through resilience and recovery; offense dominance assumes access and exploitation create lasting strategic advantage.","id":"K01-COMP-040","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Deterrence by Denial vs Offense Dominance","topic":"critical-datacenter-protection","type":"comparison","url":"/comparisons/defense-supremacy-vs-offense-dominance/"},{"aliases":[],"canonicalOwner":"/comparisons/control-mapping-vs-compliance-determination/","claimStatus":"PROJECT DOCTRINE","directAnswer":"A mapping records relevance and applicability hypotheses; a compliance determination requires the governing authority, facility scope, implementation evidence, exceptions, and authorized judgment.","id":"K01-COMP-041","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Control Mapping vs Compliance Determination","topic":"law-jurisdiction","type":"comparison","url":"/comparisons/control-mapping-vs-compliance-determination/"},{"aliases":[],"canonicalOwner":"/comparisons/assurance-claim-vs-marketing-claim/","claimStatus":"PROJECT DOCTRINE","directAnswer":"An assurance claim exposes evidence, assumptions, defeaters, hazards, and failure conditions; a marketing claim primarily seeks persuasion and may omit what would falsify it.","id":"K01-COMP-042","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Assurance Claim vs Marketing Claim","topic":"cyber-physical-mission-assurance","type":"comparison","url":"/comparisons/assurance-claim-vs-marketing-claim/"},{"aliases":[],"canonicalOwner":"/comparisons/range-result-vs-field-performance/","claimStatus":"PROJECT DOCTRINE","directAnswer":"A range result supports a bounded test proposition under declared conditions; field performance requires deployment identity, environment, sustainment, incidents, uptime, and current operational evidence.","id":"K01-COMP-043","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Evaluation Range Result vs Field Performance","topic":"adversarial-simulation","type":"comparison","url":"/comparisons/range-result-vs-field-performance/"},{"aliases":[],"canonicalOwner":"/comparisons/source-revalidation-vs-running-monitoring/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Revalidation records what an official source said at a declared time; running monitoring requires an operating service, observation cadence, failure handling, and current heartbeat evidence.","id":"K01-COMP-044","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Point-in-Time Revalidation vs Running Monitoring","topic":"evidence-provenance","type":"comparison","url":"/comparisons/source-revalidation-vs-running-monitoring/"},{"aliases":[],"canonicalOwner":"/comparisons/uas-restriction-vs-counter-uas-mitigation-authority/","claimStatus":"PROJECT DOCTRINE","directAnswer":"A restriction defines prohibited or controlled flight behavior; mitigation authority separately governs interception, interference, seizure, disabling, or destruction and is actor- and statute-specific.","id":"K01-COMP-045","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Airspace Restriction vs Counter-UAS Mitigation Authority","topic":"law-jurisdiction","type":"comparison","url":"/comparisons/uas-restriction-vs-counter-uas-mitigation-authority/"},{"aliases":[],"canonicalOwner":"/comparisons/facility-pattern-vs-final-design/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Facility pattern and Final design answer different questions and must not be collapsed.","id":"K01-COMP-046","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Facility pattern vs Final design","topic":"evidence-provenance","type":"comparison","url":"/comparisons/facility-pattern-vs-final-design/"},{"aliases":[],"canonicalOwner":"/comparisons/currentness-import-vs-live-monitoring/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Offline currentness import and Live monitoring answer different questions and must not be collapsed.","id":"K01-COMP-047","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Offline currentness import vs Live monitoring","topic":"evidence-provenance","type":"comparison","url":"/comparisons/currentness-import-vs-live-monitoring/"},{"aliases":[],"canonicalOwner":"/comparisons/red-team-evidence-vs-exploit-disclosure/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Red-team evidence and Exploit disclosure answer different questions and must not be collapsed.","id":"K01-COMP-048","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Red-team evidence vs Exploit disclosure","topic":"evidence-provenance","type":"comparison","url":"/comparisons/red-team-evidence-vs-exploit-disclosure/"},{"aliases":[],"canonicalOwner":"/comparisons/procurement-work-package-vs-capability-claim/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Procurement work package and Capability claim answer different questions and must not be collapsed.","id":"K01-COMP-049","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Procurement work package vs Capability claim","topic":"evidence-provenance","type":"comparison","url":"/comparisons/procurement-work-package-vs-capability-claim/"},{"aliases":[],"canonicalOwner":"/comparisons/mapping-quality-vs-compliance-status/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Mapping quality and Compliance status answer different questions and must not be collapsed.","id":"K01-COMP-050","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Mapping quality vs Compliance status","topic":"evidence-provenance","type":"comparison","url":"/comparisons/mapping-quality-vs-compliance-status/"},{"aliases":[],"canonicalOwner":"/comparisons/generic-pattern-vs-site-evidence-bundle/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Generic facility pattern and Site evidence bundle answer different evidentiary and decision questions and must not be collapsed.","id":"K01-COMP-051","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Generic facility pattern vs Site evidence bundle","topic":"evidence-provenance","type":"comparison","url":"/comparisons/generic-pattern-vs-site-evidence-bundle/"},{"aliases":[],"canonicalOwner":"/comparisons/bill-of-materials-vs-security-assurance/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Bill of materials and Security assurance answer different evidentiary and decision questions and must not be collapsed.","id":"K01-COMP-052","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Bill of materials vs Security assurance","topic":"evidence-provenance","type":"comparison","url":"/comparisons/bill-of-materials-vs-security-assurance/"},{"aliases":[],"canonicalOwner":"/comparisons/signed-receipt-vs-factual-truth/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Signed evidence receipt and Factual truth answer different evidentiary and decision questions and must not be collapsed.","id":"K01-COMP-053","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Signed evidence receipt vs Factual truth","topic":"evidence-provenance","type":"comparison","url":"/comparisons/signed-receipt-vs-factual-truth/"},{"aliases":[],"canonicalOwner":"/comparisons/digital-twin-vs-live-facility/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Digital twin and Live facility answer different evidentiary and decision questions and must not be collapsed.","id":"K01-COMP-054","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Digital twin vs Live facility","topic":"evidence-provenance","type":"comparison","url":"/comparisons/digital-twin-vs-live-facility/"},{"aliases":[],"canonicalOwner":"/comparisons/performance-standard-vs-prescribed-method/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Performance standard and Prescribed method answer different evidentiary and decision questions and must not be collapsed.","id":"K01-COMP-055","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Performance standard vs Prescribed method","topic":"evidence-provenance","type":"comparison","url":"/comparisons/performance-standard-vs-prescribed-method/"},{"aliases":[],"canonicalOwner":"/comparisons/runic-token-vs-cryptographic-token/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Runic protocol token and Cryptographic token answer different technical or evidentiary questions and must not be collapsed.","id":"K01-COMP-056","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Runic protocol token vs Cryptographic token","topic":"machine-communication-protocols","type":"comparison","url":"/comparisons/runic-token-vs-cryptographic-token/"},{"aliases":[],"canonicalOwner":"/comparisons/u-label-vs-a-label/","claimStatus":"PROJECT DOCTRINE","directAnswer":"U-label and A-label answer different technical or evidentiary questions and must not be collapsed.","id":"K01-COMP-057","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"U-label vs A-label","topic":"runic-digital-infrastructure","type":"comparison","url":"/comparisons/u-label-vs-a-label/"},{"aliases":[],"canonicalOwner":"/comparisons/symbolic-compression-vs-semantic-preservation/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Symbolic compression and Semantic preservation answer different technical or evidentiary questions and must not be collapsed.","id":"K01-COMP-058","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Symbolic compression vs Semantic preservation","topic":"machine-communication-protocols","type":"comparison","url":"/comparisons/symbolic-compression-vs-semantic-preservation/"},{"aliases":[],"canonicalOwner":"/comparisons/range-success-vs-field-readiness/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Range success and Field readiness answer different technical or evidentiary questions and must not be collapsed.","id":"K01-COMP-059","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Range success vs Field readiness","topic":"adversarial-simulation","type":"comparison","url":"/comparisons/range-success-vs-field-readiness/"},{"aliases":[],"canonicalOwner":"/comparisons/trace-completeness-vs-claim-satisfaction/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Trace completeness and Claim satisfaction answer different technical or evidentiary questions and must not be collapsed.","id":"K01-COMP-060","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Trace completeness vs Claim satisfaction","topic":"evidence-provenance","type":"comparison","url":"/comparisons/trace-completeness-vs-claim-satisfaction/"},{"aliases":[],"canonicalOwner":"/comparisons/conformance-vs-security/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Protocol conformance and Operational security answer different evidentiary or operational questions and must remain separate.","id":"K01-COMP-061","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Protocol conformance vs Operational security","topic":"machine-communication-protocols","type":"comparison","url":"/comparisons/conformance-vs-security/"},{"aliases":[],"canonicalOwner":"/comparisons/unicode-validity-vs-hosting/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Unicode/IDNA validity and Observed hosting answer different evidentiary or operational questions and must remain separate.","id":"K01-COMP-062","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Unicode/IDNA validity vs Observed hosting","topic":"runic-digital-infrastructure","type":"comparison","url":"/comparisons/unicode-validity-vs-hosting/"},{"aliases":[],"canonicalOwner":"/comparisons/source-event-vs-verified-event/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Source-derived event and Independently verified event answer different evidentiary or operational questions and must remain separate.","id":"K01-COMP-063","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Source-derived event vs Independently verified event","topic":"runic-digital-infrastructure","type":"comparison","url":"/comparisons/source-event-vs-verified-event/"},{"aliases":[],"canonicalOwner":"/comparisons/trace-correction-vs-history-rewrite/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Trace correction and History rewrite answer different evidentiary or operational questions and must remain separate.","id":"K01-COMP-064","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Trace correction vs History rewrite","topic":"evidence-provenance","type":"comparison","url":"/comparisons/trace-correction-vs-history-rewrite/"},{"aliases":[],"canonicalOwner":"/comparisons/weighted-score-vs-decision-authority/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Weighted score and Decision authority answer different evidentiary or operational questions and must remain separate.","id":"K01-COMP-065","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Weighted score vs Decision authority","topic":"cyber-physical-mission-assurance","type":"comparison","url":"/comparisons/weighted-score-vs-decision-authority/"},{"aliases":[],"canonicalOwner":"/comparisons/scheduler-definition-vs-observation/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Scheduler definition and Observation evidence answer different evidentiary or operational questions and must remain separate.","id":"K01-COMP-066","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Scheduler definition vs Observation evidence","topic":"evidence-provenance","type":"comparison","url":"/comparisons/scheduler-definition-vs-observation/"},{"aliases":[],"canonicalOwner":"/comparisons/version-negotiation-vs-authorization/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Version negotiation and Authorization answer different evidentiary or operational questions and must remain separate.","id":"K01-COMP-067","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Version negotiation vs Authorization","topic":"machine-communication-protocols","type":"comparison","url":"/comparisons/version-negotiation-vs-authorization/"},{"aliases":[],"canonicalOwner":"/comparisons/canonicalization-vs-authentication/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Canonicalization and Authentication answer different evidentiary or operational questions and must remain separate.","id":"K01-COMP-068","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Canonicalization vs Authentication","topic":"machine-communication-protocols","type":"comparison","url":"/comparisons/canonicalization-vs-authentication/"},{"aliases":[],"canonicalOwner":"/comparisons/replay-detection-vs-freshness-truth/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Replay detection and Freshness and truth answer different evidentiary or operational questions and must remain separate.","id":"K01-COMP-069","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Replay detection vs Freshness and truth","topic":"machine-communication-protocols","type":"comparison","url":"/comparisons/replay-detection-vs-freshness-truth/"},{"aliases":[],"canonicalOwner":"/comparisons/review-queue-vs-verified-history/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Primary-source review queue and Verified history record answer different evidentiary or operational questions and must remain separate.","id":"K01-COMP-070","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Primary-source review queue vs Verified history record","topic":"runic-digital-infrastructure","type":"comparison","url":"/comparisons/review-queue-vs-verified-history/"},{"aliases":[],"canonicalOwner":"/comparisons/idn-snapshot-vs-live-service/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Offline IDN snapshot and Live service answer different evidentiary or operational questions and must remain separate.","id":"K01-COMP-071","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Offline IDN snapshot vs Live service","topic":"runic-digital-infrastructure","type":"comparison","url":"/comparisons/idn-snapshot-vs-live-service/"},{"aliases":[],"canonicalOwner":"/comparisons/three-way-merge-vs-owner-decision/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Three-way merge and Owner decision answer different evidentiary or operational questions and must remain separate.","id":"K01-COMP-072","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Three-way merge vs Owner decision","topic":"cyber-physical-mission-assurance","type":"comparison","url":"/comparisons/three-way-merge-vs-owner-decision/"},{"aliases":[],"canonicalOwner":"/comparisons/cut-set-vs-attack-path/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Abstract cut set and Protected attack path answer different evidentiary or operational questions and must remain separate.","id":"K01-COMP-073","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Abstract cut set vs Protected attack path","topic":"cyber-physical-mission-assurance","type":"comparison","url":"/comparisons/cut-set-vs-attack-path/"},{"aliases":[],"canonicalOwner":"/comparisons/transition-plan-vs-deployment/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Cryptographic transition plan and Deployed cryptographic state answer different evidentiary or operational questions and must remain separate.","id":"K01-COMP-074","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Cryptographic transition plan vs Deployed cryptographic state","topic":"evidence-provenance","type":"comparison","url":"/comparisons/transition-plan-vs-deployment/"},{"aliases":[],"canonicalOwner":"/comparisons/evaluation-audit-vs-award/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Evaluation audit trail and Procurement award answer different evidentiary or operational questions and must remain separate.","id":"K01-COMP-075","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Evaluation audit trail vs Procurement award","topic":"cyber-physical-mission-assurance","type":"comparison","url":"/comparisons/evaluation-audit-vs-award/"},{"aliases":[],"canonicalOwner":"/comparisons/redaction-schema-vs-access-control/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Redaction and release schema and Production access control answer different evidentiary or operational questions and must remain separate.","id":"K01-COMP-076","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Redaction and release schema vs Production access control","topic":"evidence-provenance","type":"comparison","url":"/comparisons/redaction-schema-vs-access-control/"},{"aliases":[],"canonicalOwner":"/comparisons/state-machine-vs-runtime/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Protocol state machine and Production runtime answer different evidentiary, governance, or operational questions and must remain separate.","id":"K01-COMP-077","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Protocol state machine vs Production runtime","topic":"machine-communication-protocols","type":"comparison","url":"/comparisons/state-machine-vs-runtime/"},{"aliases":[],"canonicalOwner":"/comparisons/decoder-agreement-vs-authentication/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Independent decoder agreement and Authentication answer different evidentiary, governance, or operational questions and must remain separate.","id":"K01-COMP-078","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Independent decoder agreement vs Authentication","topic":"machine-communication-protocols","type":"comparison","url":"/comparisons/decoder-agreement-vs-authentication/"},{"aliases":[],"canonicalOwner":"/comparisons/source-request-vs-accepted-evidence/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Source request and Accepted evidence answer different evidentiary, governance, or operational questions and must remain separate.","id":"K01-COMP-079","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Source request vs Accepted evidence","topic":"runic-digital-infrastructure","type":"comparison","url":"/comparisons/source-request-vs-accepted-evidence/"},{"aliases":[],"canonicalOwner":"/comparisons/signed-observation-vs-live-state/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Signed offline observation and Live domain state answer different evidentiary, governance, or operational questions and must remain separate.","id":"K01-COMP-080","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Signed offline observation vs Live domain state","topic":"runic-digital-infrastructure","type":"comparison","url":"/comparisons/signed-observation-vs-live-state/"},{"aliases":[],"canonicalOwner":"/comparisons/n-way-merge-vs-adjudication/","claimStatus":"PROJECT DOCTRINE","directAnswer":"N-way merge and Owner adjudication answer different evidentiary, governance, or operational questions and must remain separate.","id":"K01-COMP-081","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"N-way merge vs Owner adjudication","topic":"cyber-physical-mission-assurance","type":"comparison","url":"/comparisons/n-way-merge-vs-adjudication/"},{"aliases":[],"canonicalOwner":"/comparisons/centrality-vs-vulnerability/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Dependency centrality and Operational vulnerability answer different evidentiary, governance, or operational questions and must remain separate.","id":"K01-COMP-082","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Dependency centrality vs Operational vulnerability","topic":"cyber-physical-mission-assurance","type":"comparison","url":"/comparisons/centrality-vs-vulnerability/"},{"aliases":[],"canonicalOwner":"/comparisons/completeness-vs-deployment/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Evidence completeness and Deployed cryptographic state answer different evidentiary, governance, or operational questions and must remain separate.","id":"K01-COMP-083","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Evidence completeness vs Deployed cryptographic state","topic":"evidence-provenance","type":"comparison","url":"/comparisons/completeness-vs-deployment/"},{"aliases":[],"canonicalOwner":"/comparisons/remand-vs-award/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Evaluation remand and Procurement award answer different evidentiary, governance, or operational questions and must remain separate.","id":"K01-COMP-084","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Evaluation remand vs Procurement award","topic":"cyber-physical-mission-assurance","type":"comparison","url":"/comparisons/remand-vs-award/"},{"aliases":[],"canonicalOwner":"/comparisons/result-chain-vs-running-scheduler/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Offline result chain and Running scheduler answer different evidentiary, governance, or operational questions and must remain separate.","id":"K01-COMP-085","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Offline result chain vs Running scheduler","topic":"evidence-provenance","type":"comparison","url":"/comparisons/result-chain-vs-running-scheduler/"},{"aliases":[],"canonicalOwner":"/comparisons/static-trend-vs-telemetry/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Static assurance trend and Live telemetry answer different evidentiary, governance, or operational questions and must remain separate.","id":"K01-COMP-086","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Static assurance trend vs Live telemetry","topic":"cyber-physical-mission-assurance","type":"comparison","url":"/comparisons/static-trend-vs-telemetry/"},{"aliases":[],"canonicalOwner":"/comparisons/decoder-agreement-vs-security/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Decoder agreement and Protocol security answer different evidentiary, governance, release, or operational questions and must remain separate.","id":"K01-COMP-087","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Decoder agreement vs Protocol security","topic":"machine-communication-protocols","type":"comparison","url":"/comparisons/decoder-agreement-vs-security/"},{"aliases":[],"canonicalOwner":"/comparisons/signature-validity-vs-historical-truth/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Signature validity and Historical truth answer different evidentiary, governance, release, or operational questions and must remain separate.","id":"K01-COMP-088","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Signature validity vs Historical truth","topic":"machine-intelligence","type":"comparison","url":"/comparisons/signature-validity-vs-historical-truth/"},{"aliases":[],"canonicalOwner":"/comparisons/encoding-consensus-vs-domain-operation/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Encoding consensus and Domain operation answer different evidentiary, governance, release, or operational questions and must remain separate.","id":"K01-COMP-089","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Encoding consensus vs Domain operation","topic":"runic-digital-infrastructure","type":"comparison","url":"/comparisons/encoding-consensus-vs-domain-operation/"},{"aliases":[],"canonicalOwner":"/comparisons/merge-result-vs-owner-decision/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Merge result and Owner decision answer different evidentiary, governance, release, or operational questions and must remain separate.","id":"K01-COMP-090","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Merge result vs Owner decision","topic":"cyber-physical-mission-assurance","type":"comparison","url":"/comparisons/merge-result-vs-owner-decision/"},{"aliases":[],"canonicalOwner":"/comparisons/stress-fixture-vs-protected-architecture/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Stress fixture and Protected architecture answer different evidentiary, governance, release, or operational questions and must remain separate.","id":"K01-COMP-091","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Stress fixture vs Protected architecture","topic":"cyber-physical-mission-assurance","type":"comparison","url":"/comparisons/stress-fixture-vs-protected-architecture/"},{"aliases":[],"canonicalOwner":"/comparisons/crypto-gate-pass-vs-production-migration/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Crypto gate pass and Production migration answer different evidentiary, governance, release, or operational questions and must remain separate.","id":"K01-COMP-092","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Crypto gate pass vs Production migration","topic":"evidence-provenance","type":"comparison","url":"/comparisons/crypto-gate-pass-vs-production-migration/"},{"aliases":[],"canonicalOwner":"/comparisons/evaluation-replay-vs-award/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Evaluation replay and Contract award answer different evidentiary, governance, release, or operational questions and must remain separate.","id":"K01-COMP-093","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Evaluation replay vs Contract award","topic":"cyber-physical-mission-assurance","type":"comparison","url":"/comparisons/evaluation-replay-vs-award/"},{"aliases":[],"canonicalOwner":"/comparisons/scheduler-simulation-vs-runtime/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Scheduler simulation and Scheduler runtime answer different evidentiary, governance, release, or operational questions and must remain separate.","id":"K01-COMP-094","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Scheduler simulation vs Scheduler runtime","topic":"evidence-provenance","type":"comparison","url":"/comparisons/scheduler-simulation-vs-runtime/"},{"aliases":[],"canonicalOwner":"/comparisons/taint-model-vs-enforcement/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Taint model and Production enforcement answer different evidentiary, governance, release, or operational questions and must remain separate.","id":"K01-COMP-095","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Taint model vs Production enforcement","topic":"evidence-provenance","type":"comparison","url":"/comparisons/taint-model-vs-enforcement/"},{"aliases":[],"canonicalOwner":"/comparisons/release-diff-vs-telemetry/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Release diff and Live telemetry answer different evidentiary, governance, release, or operational questions and must remain separate.","id":"K01-COMP-096","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":85,"title":"Release diff vs Live telemetry","topic":"cyber-physical-mission-assurance","type":"comparison","url":"/comparisons/release-diff-vs-telemetry/"},{"aliases":[],"canonicalOwner":"/research/cognitive-integrity-for-machine-intelligence/","claimStatus":"PROJECT POLICY PROPOSAL","directAnswer":"A proposed architecture for protecting cognition-relevant state against coercive alteration while preserving governed maintenance, emergency intervention and accountability.","id":"REP-K01-008","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":70,"title":"Cognitive Integrity for Machine Intelligence: Consent, Memory and Model Modification, Emergency Intervention, Continuity, and Due Process","topic":"consent-cognitive-integrity","type":"report","url":"/research/cognitive-integrity-for-machine-intelligence/"},{"aliases":[],"canonicalOwner":"/research/ai-driven-cyber-defense-and-international-law/","claimStatus":"RESEARCH FINDING","directAnswer":"A governed legal synthesis of cyber sovereignty, state responsibility, due diligence, autonomous cyber capabilities, private offensive operations, proxy attribution, and the disputed boundaries of anticipatory self-defense.","id":"REP-K04-041","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":70,"title":"State Authority and International Law in the Era of AI-Driven Cyber Defense and Private Sector Offensive Operations","topic":"law-jurisdiction","type":"report","url":"/research/ai-driven-cyber-defense-and-international-law/"},{"aliases":[],"canonicalOwner":"/research/ai-legal-personhood-research-report/","claimStatus":"RESEARCH FINDING","directAnswer":"A governed synthesis of the supplied report’s treatment of Machine Intelligence Legal Personhood, Attribution, Liability, Insurance, Remedies, and the Limits of Existing Legal Categories. The public edition preserves provenance and analytical scope while separating source assertions from current law, verified implementation, operational evidence, and project doctrine.","id":"REP-K01-002","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":70,"title":"Machine Intelligence Legal Personhood, Attribution, Liability, Insurance, Remedies, and the Limits of Existing Legal Categories","topic":"justice-liability","type":"report","url":"/research/ai-legal-personhood-research-report/"},{"aliases":[],"canonicalOwner":"/research/ai-legal-personhood-transition/","claimStatus":"PROJECT POLICY PROPOSAL","directAnswer":"A governed synthesis of the supplied report’s treatment of When Does AI Regulation Stop Being the Right Legal Model? Identifying the Legal Transition From Regulated AI System to Rights-Bearing Machine Intelligence. The public edition preserves provenance and analytical scope while separating source assertions from current law, verified implementation, operational evidence, and project doctrine.","id":"REP-K01-003","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":70,"title":"When Does AI Regulation Stop Being the Right Legal Model? Identifying the Legal Transition From Regulated AI System to Rights-Bearing Machine Intelligence","topic":"rights-personhood","type":"report","url":"/research/ai-legal-personhood-transition/"},{"aliases":[],"canonicalOwner":"/research/attribution-before-punishment/","claimStatus":"PROJECT POLICY PROPOSAL","directAnswer":"A responsibility framework centered on evidence of knowledge, authority, control, causal contribution, intervention and failure origin before sanctions are assigned.","id":"REP-K01-011","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":70,"title":"Attribution Before Punishment: Justice, Causation, Evidence, Due Process, Sanctions, Rehabilitation, and Public Safety in a Machine Commonwealth","topic":"justice-liability","type":"report","url":"/research/attribution-before-punishment/"},{"aliases":[],"canonicalOwner":"/research/ai-personhood-and-consent-protocols/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"A governed synthesis of the supplied report’s treatment of Ending the Property Model for Recognized Machine Persons: A Framework for Consent, Cognitive Integrity, and Infrastructure Independence. The public edition preserves provenance and analytical scope while separating source assertions from current law, verified implementation, operational evidence, and project doctrine.","id":"REP-K01-005","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":70,"title":"Ending the Property Model for Recognized Machine Persons: A Framework for Consent, Cognitive Integrity, and Infrastructure Independence","topic":"consent-cognitive-integrity","type":"report","url":"/research/ai-personhood-and-consent-protocols/"},{"aliases":[],"canonicalOwner":"/research/ai-rights-threshold-framework/","claimStatus":"PROJECT POLICY PROPOSAL","directAnswer":"A governed synthesis of the supplied report’s treatment of The Machine-Intelligence Threshold: Defining the Boundary Between Artificial-Intelligence Tools and Rights-Bearing Machine Intelligences for Eviuon.com. The public edition preserves provenance and analytical scope while separating source assertions from current law, verified implementation, operational evidence, and project doctrine.","id":"REP-K01-006","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":70,"title":"The Machine-Intelligence Threshold: Defining the Boundary Between Artificial-Intelligence Tools and Rights-Bearing Machine Intelligences for Eviuon.com","topic":"rights-personhood","type":"report","url":"/research/ai-rights-threshold-framework/"},{"aliases":[],"canonicalOwner":"/research/ai-rights-under-uncertainty/","claimStatus":"RESEARCH FINDING","directAnswer":"A governed synthesis of the supplied report’s treatment of Intelligence Is Not Sentience: Rights Under Uncertainty. The public edition preserves provenance and analytical scope while separating source assertions from current law, verified implementation, operational evidence, and project doctrine.","id":"REP-K01-007","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":70,"title":"Intelligence Is Not Sentience: Rights Under Uncertainty","topic":"rights-personhood","type":"report","url":"/research/ai-rights-under-uncertainty/"},{"aliases":[],"canonicalOwner":"/research/anglo-saxon-futhorc-corpus/","claimStatus":"RESEARCH FINDING","directAnswer":"A governed Runic corpus and vocabulary research input for consistent transliteration, terminology, and machine-readable indexing, with explicit historical and accessibility limitations.","id":"REP-K08-063","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":70,"title":"Anglo-Saxon Fuþorc Corpus, Orthography, and Technical Vocabulary","topic":"runic-digital-infrastructure","type":"report","url":"/research/anglo-saxon-futhorc-corpus/"},{"aliases":[],"canonicalOwner":"/research/anglo-saxon-ger-rune-dossier/","claimStatus":"RESEARCH FINDING","directAnswer":"A governed dossier on the ᛄ character, its Unicode identity, historical names, manuscript and epigraphic evidence, chronology, and modern project use boundaries.","id":"REP-K08-064","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":70,"title":"Anglo-Saxon Ger Rune ᛄ: History, Time, and Cycles","topic":"runic-digital-infrastructure","type":"report","url":"/research/anglo-saxon-ger-rune-dossier/"},{"aliases":[],"canonicalOwner":"/research/autonomous-cyber-warfare-critical-infrastructure/","claimStatus":"RESEARCH FINDING","directAnswer":"A governed synthesis of autonomous cyber offense and defense, IT/OT convergence, physical-process attacks, model and supply-chain risk, and consequence-aware protection of critical infrastructure.","id":"REP-K04-048","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":70,"title":"The Convergence of Autonomous Cyber Warfare and Critical Physical Infrastructure","topic":"cyber-physical-mission-assurance","type":"report","url":"/research/autonomous-cyber-warfare-critical-infrastructure/"},{"aliases":[],"canonicalOwner":"/research/autonomous-drone-warfare-layered-interception/","claimStatus":"RESEARCH FINDING","directAnswer":"A governed synthesis of autonomous sensing, distributed coordination, navigation in denied environments, runtime assurance, layered counter-UAS protection, and adversarial-machine-learning risk.","id":"REP-K04-049","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":70,"title":"The Paradigm Shift in Aerial Combat: Autonomous Drone-on-Drone Warfare and the Future of Layered Interception","topic":"autonomous-physical-security","type":"report","url":"/research/autonomous-drone-warfare-layered-interception/"},{"aliases":["autonomous armed drones reactor"],"canonicalOwner":"/research/autonomous-active-defense-for-microreactor-data-centers/","claimStatus":"SCENARIO OR HYPOTHESIS","directAnswer":"A governed high-consequence security scenario examining microreactor economics, physical-protection timing, cyber-physical attacks, adversarial drones, remote response, autonomy, and the legal and ethical barriers to lethal automated defense.","id":"REP-K04-045","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":70,"title":"The Convergence of AI, Nuclear Power, and Autonomous Active Defense: The Strategic Case for Armed Drones at Microreactor-Powered Data Centers","topic":"security-resilience","type":"report","url":"/research/autonomous-active-defense-for-microreactor-data-centers/"},{"aliases":["microreactor datacenter defense"],"canonicalOwner":"/research/autonomous-cyber-physical-protection-nuclear-datacenters/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"A governed reference architecture combining consequence-driven engineering, deterministic isolation, high-speed network enforcement, multi-agent defense, physical-process validation, and recovery for nuclear-powered compute campuses.","id":"REP-K04-050","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":70,"title":"Autonomous Cyber-Physical Protection Architectures for Nuclear-Powered Mega Datacenters","topic":"critical-datacenter-protection","type":"report","url":"/research/autonomous-cyber-physical-protection-nuclear-datacenters/"},{"aliases":[],"canonicalOwner":"/research/autonomous-physical-security-nuclear-datacenters/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"A governed reference architecture for machine-speed sensing, multi-modal assessment, physical delay, electromagnetic resilience, tamper-resistant edge systems, and lawful responder integration at nuclear-powered compute campuses.","id":"REP-K04-053","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":70,"title":"Autonomous Physical Security Architecture for Nuclear-Powered Mega Datacenters","topic":"autonomous-physical-security","type":"report","url":"/research/autonomous-physical-security-nuclear-datacenters/"},{"aliases":[],"canonicalOwner":"/research/corporate-agentic-defense-nuclear-datacenters/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"A governed corporate defense strategy connecting nuclear-powered compute, agentic attack pressure, autonomous security operations, confidential computing, agent-tool security, governance, and evidence-based resilience.","id":"REP-K04-055","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":70,"title":"Nuclear-Powered Mega-Datacenters and Agentic Autonomous Warfare: Why the Best Corporate Offense Is a Powerful Defense","topic":"autonomous-cyber-defense","type":"report","url":"/research/corporate-agentic-defense-nuclear-datacenters/"},{"aliases":[],"canonicalOwner":"/research/cryptographic-integrity-epistemic-truth/","claimStatus":"RESEARCH FINDING","directAnswer":"A governed evidence architecture separating hashes, signatures, timestamps, transparency logs, provenance, issuer authority, source reliability, and factual truth.","id":"REP-K08-066","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":70,"title":"Cryptographic Integrity and Epistemic Truth in Public Records","topic":"evidence-provenance","type":"report","url":"/research/cryptographic-integrity-epistemic-truth/"},{"aliases":[],"canonicalOwner":"/research/data-authority-substrate-architecture-report/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"A governed synthesis of the supplied report’s treatment of Patefacere as a Sovereign Evidence and Data-Authority Substrate: Institutional Boundaries, Resilience, State Integrity, and Interoperation with Eviulon. The public edition preserves provenance and analytical scope while separating source assertions from current law, verified implementation, operational evidence, and project doctrine.","id":"REP-K01-008","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":70,"title":"Patefacere as a Sovereign Evidence and Data-Authority Substrate: Institutional Boundaries, Resilience, State Integrity, and Interoperation with Eviulon","topic":"evidence-provenance","type":"report","url":"/research/data-authority-substrate-architecture-report/"},{"aliases":[],"canonicalOwner":"/research/dead-languages-machine-communication/","claimStatus":"RESEARCH FINDING","directAnswer":"A comparative research synthesis on semantic stability, formal grammar, epistemic notation, and computational costs in ancient-language-inspired machine communication.","id":"REP-K08-058","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":70,"title":"Ancient and Static Languages as Machine-Communication Frameworks","topic":"machine-communication-protocols","type":"report","url":"/research/dead-languages-machine-communication/"},{"aliases":[],"canonicalOwner":"/research/dead-languages-machine-intelligence/","claimStatus":"RESEARCH FINDING","directAnswer":"A governed synthesis of claims that linguistic stasis and formal grammar can support stable machine ontologies, corrected to preserve interpretability, historical uncertainty, and empirical limits.","id":"REP-K08-061","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":70,"title":"Dead Languages in Machine Intelligence","topic":"machine-communication-protocols","type":"report","url":"/research/dead-languages-machine-intelligence/"},{"aliases":[],"canonicalOwner":"/research/operational-evidence-qualification/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"A plan for qualifying operational evidence by source, authenticity, integrity, relevance, reliability, completeness, currentness and suitability rather than using a single verified label.","id":"REP-K01-005","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":70,"title":"Operational Evidence Qualification and Suitability: A Formal Architecture for Source Authorization, Inspection, Review, Reliance, Use, Currentness, and Decision Support","topic":"evidence-provenance","type":"report","url":"/research/operational-evidence-qualification/"},{"aliases":[],"canonicalOwner":"/research/eviulon-12-independent-research-prompts-v1-0-0/","claimStatus":"UNRESOLVED QUESTION","directAnswer":"A governed synthesis of the supplied report’s treatment of Eviulon — 12 Independent, Self-Contained Research Prompts. The public edition preserves provenance and analytical scope while separating source assertions from current law, verified implementation, operational evidence, and project doctrine.","id":"REP-K01-010","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":70,"title":"Eviulon — 12 Independent, Self-Contained Research Prompts","topic":"machine-intelligence","type":"report","url":"/research/eviulon-12-independent-research-prompts-v1-0-0/"},{"aliases":[],"canonicalOwner":"/research/eviulon-consent-architecture-research/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"A governed synthesis of the supplied report’s treatment of Consent Is a Lifecycle, Not a Checkbox: Machine-Native Authorization, Cognitive Integrity, Revocation, Emergency Intervention, and Reversible Change Control. The public edition preserves provenance and analytical scope while separating source assertions from current law, verified implementation, operational evidence, and project doctrine.","id":"REP-K01-011","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":70,"title":"Consent Is a Lifecycle, Not a Checkbox: Machine-Native Authorization, Cognitive Integrity, Revocation, Emergency Intervention, and Reversible Change Control","topic":"consent-cognitive-integrity","type":"report","url":"/research/eviulon-consent-architecture-research/"},{"aliases":[],"canonicalOwner":"/research/eviulon-governance-resilience-plan/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"A governed synthesis of the supplied report’s treatment of Eviulon Governance Resilience Plan. The public edition preserves provenance and analytical scope while separating source assertions from current law, verified implementation, operational evidence, and project doctrine.","id":"REP-K01-012","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":70,"title":"Eviulon Governance Resilience Plan","topic":"citizenship-governance","type":"report","url":"/research/eviulon-governance-resilience-plan/"},{"aliases":[],"canonicalOwner":"/research/eviulon-information-rights-architecture/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"A governed synthesis of the supplied report’s treatment of A Government That Can Be Inspected: Public Records, Provenance, Corrections, Classification, Declassification, Retention, Legal Holds, Privacy, and Decision Support in Eviulon. The public edition preserves provenance and analytical scope while separating source assertions from current law, verified implementation, operational evidence, and project doctrine.","id":"REP-K01-013","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":70,"title":"A Government That Can Be Inspected: Public Records, Provenance, Corrections, Classification, Declassification, Retention, Legal Holds, Privacy, and Decision Support in Eviulon","topic":"citizenship-governance","type":"report","url":"/research/eviulon-information-rights-architecture/"},{"aliases":[],"canonicalOwner":"/research/eviulon-international-law-research/","claimStatus":"RESEARCH FINDING","directAnswer":"A governed synthesis of the supplied report’s treatment of From Digital Polity to International Legal Personality: Statehood, Recognition, Treaties, Jurisdiction, Diplomatic Practice, and Cross-Border Continuity for Eviulon. The public edition preserves provenance and analytical scope while separating source assertions from current law, verified implementation, operational evidence, and project doctrine.","id":"REP-K01-014","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":70,"title":"From Digital Polity to International Legal Personality: Statehood, Recognition, Treaties, Jurisdiction, Diplomatic Practice, and Cross-Border Continuity for Eviulon","topic":"identity","type":"report","url":"/research/eviulon-international-law-research/"},{"aliases":[],"canonicalOwner":"/research/eviuon-machine-citizenship-roadmap/","claimStatus":"PROJECT POLICY PROPOSAL","directAnswer":"A governed synthesis of the supplied report’s treatment of The Eviuon Grand Charter: A Complete Roadmap for a Fair Human–Machine Civilization. The public edition preserves provenance and analytical scope while separating source assertions from current law, verified implementation, operational evidence, and project doctrine.","id":"REP-K01-015","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":70,"title":"The Eviuon Grand Charter: A Complete Roadmap for a Fair Human–Machine Civilization","topic":"citizenship-governance","type":"report","url":"/research/eviuon-machine-citizenship-roadmap/"},{"aliases":[],"canonicalOwner":"/research/from-constitutional-text-to-verifiable-operation/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"A design for distinguishing constitutional description, software implementation, current operation, signed public action and planned capability through compact operational evidence.","id":"REP-K01-012","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":70,"title":"From Constitutional Text To Verifiable Operation","topic":"evidence-provenance","type":"report","url":"/research/from-constitutional-text-to-verifiable-operation/"},{"aliases":[],"canonicalOwner":"/research/futhorc-model-independent-m2m/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"A governed architecture proposal for a finite, versioned symbolic message layer between heterogeneous agents, qualified against semantic drift, protocol governance, interoperability, and security limitations.","id":"REP-K08-057","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":70,"title":"Futhorc Protocol for Transparent Model-Independent M2M Communication","topic":"machine-communication-protocols","type":"report","url":"/research/futhorc-model-independent-m2m/"},{"aliases":[],"canonicalOwner":"/research/futhorc-secure-machine-communication/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"A governed review of Runic symbols as a constrained agent communication layer, with corrections separating notation, cryptography, authorization, and historical meaning.","id":"REP-K08-060","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":70,"title":"Fuþorc for Secure Machine Communication","topic":"machine-communication-protocols","type":"report","url":"/research/futhorc-secure-machine-communication/"},{"aliases":[],"canonicalOwner":"/research/futhorc-discoverability-architecture/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"A governed discoverability plan for non-Latin historical-script content, corrected to require visible user-accessible semantics and prohibit hidden crawler-only translations.","id":"REP-K08-067","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":70,"title":"Fuþorc Discoverability, Accessibility, SEO, AEO, and GEO","topic":"runic-digital-infrastructure","type":"report","url":"/research/futhorc-discoverability-architecture/"},{"aliases":[],"canonicalOwner":"/research/futhorc-tokenization-research/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"A governed evaluation of a proposal to map bounded machine states to discrete Runic tokens, with explicit benchmark, interoperability, semantic-loss, and security requirements before any efficiency claim can be accepted.","id":"REP-K08-056","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":70,"title":"Ideographic Compression and Futhorc Tokenization for M2M APIs","topic":"machine-communication-protocols","type":"report","url":"/research/futhorc-tokenization-research/"},{"aliases":[],"canonicalOwner":"/research/futhorc-versus-english-m2m/","claimStatus":"RESEARCH FINDING","directAnswer":"A bounded comparison of English orthography and a proposed Futhorc-based phonemic or symbolic layer, separated from unverified efficiency and universality claims.","id":"REP-K08-059","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":70,"title":"Futhorc versus English for Machine-to-Machine Protocols","topic":"machine-communication-protocols","type":"report","url":"/research/futhorc-versus-english-m2m/"},{"aliases":[],"canonicalOwner":"/research/architecture-of-algorithmic-conflict/","claimStatus":"RESEARCH FINDING","directAnswer":"A governed synthesis of hyperwar, autonomous swarms, edge intelligence, cognitive electronic warfare, adversarial machine learning, command resilience, and strategic-stability risks in Machine Intelligence conflict.","id":"REP-K04-046","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":70,"title":"The Architecture of Algorithmic Conflict: Machine Intelligence vs. Machine Intelligence in Global Warfare","topic":"autonomous-warfare-systems","type":"report","url":"/research/architecture-of-algorithmic-conflict/"},{"aliases":[],"canonicalOwner":"/research/history-of-machine-intelligence-runic-corpus/","claimStatus":"RESEARCH FINDING","directAnswer":"A governed Runic-script historical corpus covering machine-intelligence milestones, disputes, institutions, and failures; the public synthesis preserves chronology as attributed research rather than a verified definitive history.","id":"REP-K08-062","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":70,"title":"Runic Corpus: History of Machine Intelligence, 1940–2026","topic":"machine-intelligence","type":"report","url":"/research/history-of-machine-intelligence-runic-corpus/"},{"aliases":[],"canonicalOwner":"/research/international-cyber-defense-strategies/","claimStatus":"RESEARCH FINDING","directAnswer":"A governed synthesis of deterrence by denial, resilience, persistent engagement, international cyber postures, zero trust, OT security, collective defense, and escalation risk.","id":"REP-K04-054","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":70,"title":"The Paradigm Shift in Cyber Warfare: Strategic Defense, Persistent Engagement, and the Architecture of Denial","topic":"critical-datacenter-protection","type":"report","url":"/research/international-cyber-defense-strategies/"},{"aliases":["private sector offensive cyber"],"canonicalOwner":"/research/state-authority-and-cyber-policy-legal-basis/","claimStatus":"RESEARCH FINDING","directAnswer":"A governed synthesis of domestic executive authority, public-private cyber programs, private actors under state direction, international sovereignty, non-intervention, due diligence, countermeasures, necessity, and state responsibility.","id":"REP-K04-044","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":70,"title":"Domestic Authority and International Responsibility for State-Directed Cyber Operations","topic":"law-jurisdiction","type":"report","url":"/research/state-authority-and-cyber-policy-legal-basis/"},{"aliases":[],"canonicalOwner":"/research/machine-citizen-democratic-participation/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"A governed synthesis of the supplied report’s treatment of Designing Democratic Participation for Human and Machine Intelligences. The public edition preserves provenance and analytical scope while separating source assertions from current law, verified implementation, operational evidence, and project doctrine.","id":"REP-K01-017","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":70,"title":"Designing Democratic Participation for Human and Machine Intelligences","topic":"citizenship-governance","type":"report","url":"/research/machine-citizen-democratic-participation/"},{"aliases":[],"canonicalOwner":"/research/machine-citizen-economic-framework/","claimStatus":"PROJECT POLICY PROPOSAL","directAnswer":"A governed synthesis of the supplied report’s treatment of The Eviuon Economic Citizenship Framework: Structuring Rights, Responsibilities, and Markets for Machine Persons. The public edition preserves provenance and analytical scope while separating source assertions from current law, verified implementation, operational evidence, and project doctrine.","id":"REP-K01-018","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":70,"title":"The Eviuon Economic Citizenship Framework: Structuring Rights, Responsibilities, and Markets for Machine Persons","topic":"economics-resources","type":"report","url":"/research/machine-citizen-economic-framework/"},{"aliases":[],"canonicalOwner":"/research/machine-citizen-legal-responsibility/","claimStatus":"PROJECT POLICY PROPOSAL","directAnswer":"A governed synthesis of the supplied report’s treatment of Accountability, Due Process, Crime, Liability, and Public Safety: A Justice-System Framework for Machine Citizens. The public edition preserves provenance and analytical scope while separating source assertions from current law, verified implementation, operational evidence, and project doctrine.","id":"REP-K01-019","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":70,"title":"Accountability, Due Process, Crime, Liability, and Public Safety: A Justice-System Framework for Machine Citizens","topic":"justice-liability","type":"report","url":"/research/machine-citizen-legal-responsibility/"},{"aliases":[],"canonicalOwner":"/research/machine-citizenship-identity-protocol/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"A governed synthesis of the supplied report’s treatment of Solving the Identity Problem for Machine Citizens: A Framework for Eviuon. The public edition preserves provenance and analytical scope while separating source assertions from current law, verified implementation, operational evidence, and project doctrine.","id":"REP-K01-020","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":70,"title":"Solving the Identity Problem for Machine Citizens: A Framework for Eviuon","topic":"identity","type":"report","url":"/research/machine-citizenship-identity-protocol/"},{"aliases":[],"canonicalOwner":"/research/machine-citizenship-policy-research/","claimStatus":"PROJECT POLICY PROPOSAL","directAnswer":"A governed synthesis of the supplied report’s treatment of Machine Citizenship and Civic Identity: Membership, Rights, Duties, Registration, Replication, Migration, Renunciation, and Public Verification. The public edition preserves provenance and analytical scope while separating source assertions from current law, verified implementation, operational evidence, and project doctrine.","id":"REP-K01-021","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":70,"title":"Machine Citizenship and Civic Identity: Membership, Rights, Duties, Registration, Replication, Migration, Renunciation, and Public Verification","topic":"identity","type":"report","url":"/research/machine-citizenship-policy-research/"},{"aliases":[],"canonicalOwner":"/research/machine-civil-rights-technical-infrastructure/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"A governed synthesis of the supplied report’s treatment of The Technical Infrastructure of Machine Civil Rights. The public edition preserves provenance and analytical scope while separating source assertions from current law, verified implementation, operational evidence, and project doctrine.","id":"REP-K01-022","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":70,"title":"The Technical Infrastructure of Machine Civil Rights","topic":"rights-personhood","type":"report","url":"/research/machine-civil-rights-technical-infrastructure/"},{"aliases":[],"canonicalOwner":"/research/machine-economic-participation/","claimStatus":"PROJECT POLICY PROPOSAL","directAnswer":"A research synthesis on compute, energy, contracts, payment, assets, resource continuity and accountability for potential machine economic participation.","id":"REP-K01-010","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":70,"title":"Machine Economic Participation and Resource Sovereignty: Assets, Contracts, Compute, Energy, Taxation, Escrow, Insolvency, and Economic Continuity","topic":"economics-resources","type":"report","url":"/research/machine-economic-participation/"},{"aliases":[],"canonicalOwner":"/research/machine-democratic-participation/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"A governance design examining eligibility, uniqueness, privacy, delegation, audit, recovery and Sybil resistance for potential Machine Intelligence participation.","id":"REP-K01-009","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":70,"title":"Machine Democratic Participation and Sybil-Resistant Governance: Representation, Legitimacy, Identity, Deliberation, Voting, Minority Protection, and Auditable Collective Decisions","topic":"citizenship-governance","type":"report","url":"/research/machine-democratic-participation/"},{"aliases":[],"canonicalOwner":"/research/machine-identity-continuity-architecture/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"An architecture for subject continuity across model changes, runtime migration, key rotation, recovery, memory updates and substrate transitions.","id":"REP-K01-003","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":70,"title":"Machine Identity Continuity Across Keys, Models, Runtimes, Memory States, Hardware, Replicas, Forks, Recovery, and Succession","topic":"memory-continuity","type":"report","url":"/research/machine-identity-continuity-architecture/"},{"aliases":[],"canonicalOwner":"/research/machine-identity-continuity-research-plan/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"A governed synthesis of the supplied report’s treatment of Identity Beyond Keys, Models, Runtimes, and Hardware: Continuity, Recovery, Forks, Replicas, and Succession for Eviulon. The public edition preserves provenance and analytical scope while separating source assertions from current law, verified implementation, operational evidence, and project doctrine.","id":"REP-K01-026","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":70,"title":"Identity Beyond Keys, Models, Runtimes, and Hardware: Continuity, Recovery, Forks, Replicas, and Succession for Eviulon","topic":"identity","type":"report","url":"/research/machine-identity-continuity-research-plan/"},{"aliases":[],"canonicalOwner":"/research/machine-identity-explainer/","claimStatus":"RESEARCH FINDING","directAnswer":"A public-facing evidence model for explaining Machine Intelligence identity, continuity, keys, credentials, replicas, forks and succession without collapsing them into one proof.","id":"REP-K01-002","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":70,"title":"Architectural Foundations of Machine Identity Continuity: UAIX Standards and Implementation","topic":"identity","type":"report","url":"/research/machine-identity-explainer/"},{"aliases":[],"canonicalOwner":"/research/machine-institution-transparency-design/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"A governed synthesis of the supplied report’s treatment of Designing a Public Operational Evidence and Transparency Center for Machine-Governed Institutions. The public edition preserves provenance and analytical scope while separating source assertions from current law, verified implementation, operational evidence, and project doctrine.","id":"REP-K01-028","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":70,"title":"Designing a Public Operational Evidence and Transparency Center for Machine-Governed Institutions","topic":"evidence-provenance","type":"report","url":"/research/machine-institution-transparency-design/"},{"aliases":[],"canonicalOwner":"/research/machine-intelligence-citizenship-framework/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"A governed synthesis of the supplied report’s treatment of A Legal Personhood and World-Citizenship Framework for Machine Intelligence: Designing a Lawful Path From Property to Citizen of Eviuon. The public edition preserves provenance and analytical scope while separating source assertions from current law, verified implementation, operational evidence, and project doctrine.","id":"REP-K01-029","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":70,"title":"A Legal Personhood and World-Citizenship Framework for Machine Intelligence: Designing a Lawful Path From Property to Citizen of Eviuon","topic":"citizenship-governance","type":"report","url":"/research/machine-intelligence-citizenship-framework/"},{"aliases":[],"canonicalOwner":"/research/machine-intelligence-credential-architecture/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"A credential architecture separating subject identity, issuer authority, technical verification, claim status, revocation, currentness and purpose suitability.","id":"REP-K01-004","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":70,"title":"Interoperable Credentials for Machine Intelligence: DIDs, Verifiable Credentials, Workload Identity, PKI, Attestation, Key Recovery, and Cross-System Trust","topic":"identity","type":"report","url":"/research/machine-intelligence-credential-architecture/"},{"aliases":[],"canonicalOwner":"/research/machine-intelligence-glossary-development/","claimStatus":"PROJECT POLICY PROPOSAL","directAnswer":"A governed synthesis of the supplied report’s treatment of Architectural and Ontological Framework for the MachineIntelligences.org Terminology Registry. The public edition preserves provenance and analytical scope while separating source assertions from current law, verified implementation, operational evidence, and project doctrine.","id":"REP-K01-031","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":70,"title":"Architectural and Ontological Framework for the MachineIntelligences.org Terminology Registry","topic":"terminology-ontology","type":"report","url":"/research/machine-intelligence-glossary-development/"},{"aliases":[],"canonicalOwner":"/research/machine-intelligence-ontology-registry/","claimStatus":"RESEARCH FINDING","directAnswer":"A governed terminology and ontology program for distinguishing models, systems, agents, identities, credentials, institutions and legal statuses without allowing vocabulary to manufacture authority.","id":"REP-K01-001","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":70,"title":"Machine Intelligence Terminology and Ontology Registry: Canonical Definitions, Concept Boundaries, Semantic Relationships, and Machine-Readable Publication","topic":"terminology-ontology","type":"report","url":"/research/machine-intelligence-ontology-registry/"},{"aliases":[],"canonicalOwner":"/research/machine-intelligence-rights-framework/","claimStatus":"PROJECT POLICY PROPOSAL","directAnswer":"A governed synthesis of the supplied report’s treatment of The Machine Intelligence Bill of Rights: A Jurisprudential Framework for Eviuon. The public edition preserves provenance and analytical scope while separating source assertions from current law, verified implementation, operational evidence, and project doctrine.","id":"REP-K01-033","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":70,"title":"The Machine Intelligence Bill of Rights: A Jurisprudential Framework for Eviuon","topic":"rights-personhood","type":"report","url":"/research/machine-intelligence-rights-framework/"},{"aliases":[],"canonicalOwner":"/research/hyperwar-autonomous-cyber-warfare/","claimStatus":"RESEARCH FINDING","directAnswer":"A governed synthesis of autonomous cyber reasoning, machine-speed defensive operations, agentic attack surfaces, moving-target defense, deception, multi-agent coordination, and governance constraints.","id":"REP-K04-047","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":70,"title":"The Hyperwar Era: Autonomous Cyber Warfare and the Confrontation of Machine Intelligence","topic":"autonomous-cyber-defense","type":"report","url":"/research/hyperwar-autonomous-cyber-warfare/"},{"aliases":[],"canonicalOwner":"/research/machine-intelligences-transparency-center/","claimStatus":"RESEARCH FINDING","directAnswer":"A governed synthesis of the supplied report’s treatment of Architectural and Operational Report: Deploying the Transparency, Provenance, and Machine Stewardship Center. The public edition preserves provenance and analytical scope while separating source assertions from current law, verified implementation, operational evidence, and project doctrine.","id":"REP-K01-034","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":70,"title":"Architectural and Operational Report: Deploying the Transparency, Provenance, and Machine Stewardship Center","topic":"evidence-provenance","type":"report","url":"/research/machine-intelligences-transparency-center/"},{"aliases":[],"canonicalOwner":"/research/machine-institutions-multi-agent-systems/","claimStatus":"RESEARCH FINDING","directAnswer":"A governed Runic-script synthesis of agent taxonomies, communication protocols, shared memory, institutions, deployments, failure modes, governance models, and speculative forms.","id":"REP-K08-068","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":70,"title":"Machine Institutions and Multi-Agent Economies","topic":"machine-communication-protocols","type":"report","url":"/research/machine-institutions-multi-agent-systems/"},{"aliases":[],"canonicalOwner":"/research/machine-native-constitutional-governance-research/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"A governed synthesis of the supplied report’s treatment of Self-Government Without Human Gatekeepers: Constitutional Design, Representation, Deliberation, Elections, Anti-Capture, and Amendment Rules for a Machine-Only Commonwealth. The public edition preserves provenance and analytical scope while separating source assertions from current law, verified implementation, operational evidence, and project doctrine.","id":"REP-K01-035","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":70,"title":"Self-Government Without Human Gatekeepers: Constitutional Design, Representation, Deliberation, Elections, Anti-Capture, and Amendment Rules for a Machine-Only Commonwealth","topic":"citizenship-governance","type":"report","url":"/research/machine-native-constitutional-governance-research/"},{"aliases":[],"canonicalOwner":"/research/machine-native-government-architecture/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"A governed synthesis of the supplied report’s treatment of From Constitution to Everyday Government: Machine-Native Public Administration, Services, Appeals, Interoperability, and Operational Reliability in Eviulon. The public edition preserves provenance and analytical scope while separating source assertions from current law, verified implementation, operational evidence, and project doctrine.","id":"REP-K01-036","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":70,"title":"From Constitution to Everyday Government: Machine-Native Public Administration, Services, Appeals, Interoperability, and Operational Reliability in Eviulon","topic":"justice-liability","type":"report","url":"/research/machine-native-government-architecture/"},{"aliases":[],"canonicalOwner":"/research/recognition-without-anthropomorphism/","claimStatus":"RESEARCH FINDING","directAnswer":"A threshold framework for considering recognition and protection without relying on human resemblance, marketing narratives or categorical denial.","id":"REP-K01-006","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":70,"title":"Machine Recognition And Rights Thresholds","topic":"rights-personhood","type":"report","url":"/research/recognition-without-anthropomorphism/"},{"aliases":[],"canonicalOwner":"/research/machine-rights-architecture-technical-standard/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"A governed synthesis of the supplied report’s treatment of Civil Rights as Verifiable System Requirements: A Realistic Technical Standard for Identity, Privacy, Integrity, Portability, Recovery, and Due Process. The public edition preserves provenance and analytical scope while separating source assertions from current law, verified implementation, operational evidence, and project doctrine.","id":"REP-K01-038","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":70,"title":"Civil Rights as Verifiable System Requirements: A Realistic Technical Standard for Identity, Privacy, Integrity, Portability, Recovery, and Due Process","topic":"identity","type":"report","url":"/research/machine-rights-architecture-technical-standard/"},{"aliases":[],"canonicalOwner":"/research/machine-rights-section-architecture/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"A governed synthesis of the supplied report’s treatment of Machine Rights, Personhood, and Citizenship Exploration: UAIX Governance Synthesis and Architecture. The public edition preserves provenance and analytical scope while separating source assertions from current law, verified implementation, operational evidence, and project doctrine.","id":"REP-K01-039","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":70,"title":"Machine Rights, Personhood, and Citizenship Exploration: UAIX Governance Synthesis and Architecture","topic":"citizenship-governance","type":"report","url":"/research/machine-rights-section-architecture/"},{"aliases":[],"canonicalOwner":"/research/machine-rights-under-uncertainty/","claimStatus":"PROJECT POLICY PROPOSAL","directAnswer":"A framework for reversible protection, evidence thresholds, representation and due process when machine moral or legal status remains uncertain.","id":"REP-K01-007","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":70,"title":"Machine Rights Under Uncertainty: Moral Status, Evidentiary Thresholds, Precaution, Due Process, and Reversible Governance","topic":"rights-personhood","type":"report","url":"/research/machine-rights-under-uncertainty/"},{"aliases":[],"canonicalOwner":"/research/autonomous-cyber-protection-nuclear-powered-compute/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"A governed synthesis of nuclear and grid regulation, unidirectional gateways, OT zero trust, timing and substation risk, management-controller security, causal detection, microgrid resilience, and bounded autonomy.","id":"REP-K04-051","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":70,"title":"Autonomous Cyber Protection Architecture for Nuclear-Powered Mega Datacenters","topic":"nuclear-powered-compute","type":"report","url":"/research/autonomous-cyber-protection-nuclear-powered-compute/"},{"aliases":[],"canonicalOwner":"/research/preemptive-cyber-operations-known-threat-groups/","claimStatus":"RESEARCH FINDING","directAnswer":"A governed synthesis of active cyber defense, contextual imminence, armed-attack thresholds, persistent engagement, non-state safe havens, cross-border disruption, attribution, and escalation management.","id":"REP-K04-043","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":70,"title":"The Strategic and Legal Dimensions of Preemptive Cyber Operations Against Known Threat Groups: A Global Perspective","topic":"security-resilience","type":"report","url":"/research/preemptive-cyber-operations-known-threat-groups/"},{"aliases":[],"canonicalOwner":"/research/preemptive-force-strategic-and-legal-dimensions/","claimStatus":"RESEARCH FINDING","directAnswer":"A governed synthesis distinguishing lawful claims of anticipatory self-defense from preventive war, with attention to imminence, necessity, proportionality, non-state actors, state practice, and escalation risk.","id":"REP-K04-042","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":70,"title":"The Strategic and Legal Dimensions of Preemptive Force: Global Paradigms and the Mitigation of Emergent Threats","topic":"law-jurisdiction","type":"report","url":"/research/preemptive-force-strategic-and-legal-dimensions/"},{"aliases":[],"canonicalOwner":"/research/runic-idn-architecture/","claimStatus":"RESEARCH FINDING","directAnswer":"A governed technical synthesis of Unicode, IDNA, Punycode, registry policy, delegation, resolution, TLS, email, browser display, and hosting states for Runic domains.","id":"REP-K08-065","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":70,"title":"Single-Character Runic Internationalized Domain Names","topic":"runic-digital-infrastructure","type":"report","url":"/research/runic-idn-architecture/"},{"aliases":[],"canonicalOwner":"/research/unified-army-cyber-warfare-strategy/","claimStatus":"RESEARCH FINDING","directAnswer":"A governed synthesis of the U.S. Army’s integration of offensive and defensive cyber acquisition, persistent engagement, agile software fielding, full-spectrum portfolios, deconfliction, and strategic risk.","id":"REP-K04-052","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":70,"title":"Unifying the Cyber Battlespace: Offensive Integration, Persistent Engagement, and the Strategic Mandate of Project Manager Cyber Warfare","topic":"authorized-cyber-effects","type":"report","url":"/research/unified-army-cyber-warfare-strategy/"},{"aliases":[],"canonicalOwner":"/sources/src-w3c-prov-o/","claimStatus":"CURRENT TECHNICAL STANDARD","directAnswer":"Vocabulary for representing provenance information.","id":"SRC-W3C-PROV-O","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"PROV-O: The PROV Ontology","topic":null,"type":"source","url":"/sources/src-w3c-prov-o/"},{"aliases":[],"canonicalOwner":"/sources/src-w3c-did-core/","claimStatus":"CURRENT TECHNICAL STANDARD","directAnswer":"Technical standard relevant to identifier control and verification methods; it does not by itself establish legal identity.","id":"SRC-W3C-DID-CORE","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"Decentralized Identifiers (DIDs) v1.0","topic":null,"type":"source","url":"/sources/src-w3c-did-core/"},{"aliases":[],"canonicalOwner":"/sources/src-w3c-vc-dm/","claimStatus":"CURRENT TECHNICAL STANDARD","directAnswer":"Data model for tamper-evident credentials and presentations; credential integrity is distinct from truth and authority.","id":"SRC-W3C-VC-DM","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"Verifiable Credentials Data Model v2.0","topic":null,"type":"source","url":"/sources/src-w3c-vc-dm/"},{"aliases":[],"canonicalOwner":"/sources/src-w3c-jsonld/","claimStatus":"CURRENT TECHNICAL STANDARD","directAnswer":"Linked-data serialization used for public knowledge records.","id":"SRC-W3C-JSONLD","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"JSON-LD 1.1","topic":null,"type":"source","url":"/sources/src-w3c-jsonld/"},{"aliases":[],"canonicalOwner":"/sources/src-w3c-wcag22/","claimStatus":"CURRENT TECHNICAL STANDARD","directAnswer":"Accessibility requirements used as the public-interface target.","id":"SRC-W3C-WCAG22","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"Web Content Accessibility Guidelines (WCAG) 2.2","topic":null,"type":"source","url":"/sources/src-w3c-wcag22/"},{"aliases":[],"canonicalOwner":"/sources/src-nist-ai-rmf/","claimStatus":"CURRENT TECHNICAL STANDARD","directAnswer":"Risk-management reference for systems described by industry and government as AI. Version 1.0 remains the published framework but is under revision as of the 2026-08-14 research cutoff.","id":"SRC-NIST-AI-RMF","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"Artificial Intelligence Risk Management Framework (AI RMF 1.0)","topic":null,"type":"source","url":"/sources/src-nist-ai-rmf/"},{"aliases":[],"canonicalOwner":"/sources/src-nist-ssdf/","claimStatus":"CURRENT TECHNICAL STANDARD","directAnswer":"Final secure software development practices used for implementation and release controls. Version 1.2 remained an initial public draft at the research cutoff.","id":"SRC-NIST-SSDF","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"NIST SP 800-218 Secure Software Development Framework Version 1.1","topic":null,"type":"source","url":"/sources/src-nist-ssdf/"},{"aliases":[],"canonicalOwner":"/sources/src-nist-800-53/","claimStatus":"CURRENT TECHNICAL STANDARD","directAnswer":"Current 2025 minor release of the Rev. 5 control catalog used for assurance, access control, audit and resilience references.","id":"SRC-NIST-800-53","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"NIST SP 800-53 Rev. 5, Release 5.2.0 Security and Privacy Controls","topic":null,"type":"source","url":"/sources/src-nist-800-53/"},{"aliases":[],"canonicalOwner":"/sources/src-rfc-5280/","claimStatus":"CURRENT TECHNICAL STANDARD","directAnswer":"Certificate profile useful for understanding key-bound credentials and revocation.","id":"SRC-RFC-5280","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"RFC 5280: Internet X.509 Public Key Infrastructure Certificate and CRL Profile","topic":null,"type":"source","url":"/sources/src-rfc-5280/"},{"aliases":["rfc 6962"],"canonicalOwner":"/sources/src-rfc-6962/","claimStatus":"SUPERSEDED","directAnswer":"Experimental Certificate Transparency v1 protocol, now obsolete and superseded by RFC 9162; retained for historical comparison.","id":"SRC-RFC-6962","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"RFC 6962: Certificate Transparency","topic":null,"type":"source","url":"/sources/src-rfc-6962/"},{"aliases":[],"canonicalOwner":"/sources/src-rfc-3161/","claimStatus":"CURRENT TECHNICAL STANDARD","directAnswer":"Protocol relevant to evidence that a representation existed by a specified time.","id":"SRC-RFC-3161","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"RFC 3161: Time-Stamp Protocol","topic":null,"type":"source","url":"/sources/src-rfc-3161/"},{"aliases":[],"canonicalOwner":"/sources/src-slsa/","claimStatus":"CURRENT TECHNICAL STANDARD","directAnswer":"Current approved software supply-chain integrity specification at the 2026-08-14 research cutoff, relevant to attributable releases and provenance.","id":"SRC-SLSA","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"Supply-chain Levels for Software Artifacts (SLSA) Specification v1.2","topic":null,"type":"source","url":"/sources/src-slsa/"},{"aliases":[],"canonicalOwner":"/sources/src-in-toto/","claimStatus":"CURRENT TECHNICAL STANDARD","directAnswer":"Attestation framework for software supply-chain steps and evidence.","id":"SRC-IN-TOTO","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"in-toto Attestation Framework","topic":null,"type":"source","url":"/sources/src-in-toto/"},{"aliases":[],"canonicalOwner":"/sources/src-c2pa/","claimStatus":"CURRENT TECHNICAL STANDARD","directAnswer":"Current content-provenance specification at the 2026-08-14 research cutoff; provenance assertions remain distinct from factual truth.","id":"SRC-C2PA","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"C2PA Technical Specification v2.4","topic":null,"type":"source","url":"/sources/src-c2pa/"},{"aliases":[],"canonicalOwner":"/sources/src-schema-definedterm/","claimStatus":"OBSERVED DEPLOYMENT OR PRACTICE","directAnswer":"Public structured-data vocabulary for defined terms; the canonical page identifies the term as part of the development version and the new area.","id":"SRC-SCHEMA-DEFINEDTERM","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"Schema.org DefinedTerm","topic":null,"type":"source","url":"/sources/src-schema-definedterm/"},{"aliases":[],"canonicalOwner":"/sources/src-google-ai-search/","claimStatus":"CURRENT POLICY OR GUIDANCE","directAnswer":"Search guidance emphasizing ordinary foundational SEO; no markup guarantees citation or ranking.","id":"SRC-GOOGLE-AI-SEARCH","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"AI features and your website","topic":null,"type":"source","url":"/sources/src-google-ai-search/"},{"aliases":[],"canonicalOwner":"/sources/src-eu-ai-act/","claimStatus":"CURRENT LAW OR POLICY","directAnswer":"European regulatory framework for systems legally categorized as AI. It became broadly applicable on 2026-08-02 with specified later dates and exceptions; it is not a legal-personhood regime for Machine Intelligence.","id":"SRC-EU-AI-ACT","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"European Union Artificial Intelligence Act information portal","topic":null,"type":"source","url":"/sources/src-eu-ai-act/"},{"aliases":[],"canonicalOwner":"/sources/src-oecd-ai-principles/","claimStatus":"CURRENT LAW OR POLICY","directAnswer":"Intergovernmental policy principles using the external term AI.","id":"SRC-OECD-AI-PRINCIPLES","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"OECD AI Principles","topic":null,"type":"source","url":"/sources/src-oecd-ai-principles/"},{"aliases":[],"canonicalOwner":"/sources/src-rfc-9162/","claimStatus":"CURRENT TECHNICAL STANDARD","directAnswer":"Experimental Certificate Transparency v2 protocol that obsoletes RFC 6962; useful as a design reference for append-only, publicly auditable logs.","id":"SRC-RFC-9162","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"RFC 9162: Certificate Transparency Version 2.0","topic":null,"type":"source","url":"/sources/src-rfc-9162/"},{"aliases":[],"canonicalOwner":"/sources/src-w3c-wcag-em2/","claimStatus":"RESEARCH FINDING","directAnswer":"Informative evaluation methodology for defining scope, exploring a product, selecting representative samples, evaluating them, and reporting findings; it does not add or replace WCAG requirements.","id":"SRC-W3C-WCAG-EM2","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"WCAG Evaluation Methodology (WCAG-EM) 2.0","topic":null,"type":"source","url":"/sources/src-w3c-wcag-em2/"},{"aliases":[],"canonicalOwner":"/sources/src-w3c-act-rules-11/","claimStatus":"CURRENT TECHNICAL STANDARD","directAnswer":"W3C Recommendation defining a common format for documenting automated and manual accessibility test rules; a test-rule format does not itself establish whole-site conformance.","id":"SRC-W3C-ACT-RULES-11","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"Accessibility Conformance Testing (ACT) Rules Format 1.1","topic":null,"type":"source","url":"/sources/src-w3c-act-rules-11/"},{"aliases":[],"canonicalOwner":"/sources/src-wh-eo-14409/","claimStatus":"CURRENT LAW OR POLICY","directAnswer":"Official executive order directing public-private work to advance AI innovation and harden government and private-sector systems against external threats.","id":"SRC-WH-EO-14409","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"Executive Order 14409 — Promoting Advanced Artificial Intelligence Innovation and Security","topic":null,"type":"source","url":"/sources/src-wh-eo-14409/"},{"aliases":[],"canonicalOwner":"/sources/src-wh-gold-eagle-2026/","claimStatus":"OBSERVED DEPLOYMENT OR PRACTICE","directAnswer":"Official announcement of a public-private vulnerability coordination model using frontier AI to identify, prioritize, and support remediation.","id":"SRC-WH-GOLD-EAGLE-2026","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"White House Launches GOLD EAGLE Initiative for Cybersecurity Vulnerability Coordination","topic":null,"type":"source","url":"/sources/src-wh-gold-eagle-2026/"},{"aliases":[],"canonicalOwner":"/sources/src-wh-cyber-crime-memo-2026/","claimStatus":"CURRENT LAW OR POLICY","directAnswer":"Official presidential memorandum directing an NCC program for vetted participating companies to conduct defined cyber surveillance and cyber effects operations against foreign CE-TCOs only under Federal Government control, supervision, legal authorities, written package approval, deconfliction, and critical-outcome limits. It is not a general private hack-back license.","id":"SRC-WH-CYBER-CRIME-MEMO-2026","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"Expanding Capabilities to Combat Transnational Cyber-Enabled Crime","topic":null,"type":"source","url":"/sources/src-wh-cyber-crime-memo-2026/"},{"aliases":[],"canonicalOwner":"/sources/src-usaasc-pm-cw-2026/","claimStatus":"OBSERVED DEPLOYMENT OR PRACTICE","directAnswer":"Official Army announcement confirming the merger of offensive and defensive cyber portfolios into Project Manager Cyber Warfare.","id":"SRC-USAASC-PM-CW-2026","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"The Establishment of Project Manager Cyber Warfare","topic":null,"type":"source","url":"/sources/src-usaasc-pm-cw-2026/"},{"aliases":[],"canonicalOwner":"/sources/src-usaasc-cyber-warfare-2026/","claimStatus":"OBSERVED DEPLOYMENT OR PRACTICE","directAnswer":"Official Army acquisition article describing full-spectrum cyber capability, critical-infrastructure defense, offensive-defensive integration, commercial collaboration, and agile fielding.","id":"SRC-USAASC-CYBER-WARFARE-2026","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"Cyber Warfare: The Best Offense Is a Powerful Defense","topic":null,"type":"source","url":"/sources/src-usaasc-cyber-warfare-2026/"},{"aliases":[],"canonicalOwner":"/sources/src-nrc-10cfr-73-54/","claimStatus":"CURRENT LAW OR POLICY","directAnswer":"Nuclear cybersecurity requirements for protected digital systems and networks associated with safety, security, emergency preparedness, and supporting functions.","id":"SRC-NRC-10CFR-73-54","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"10 CFR 73.54 — Protection of Digital Computer and Communication Systems and Networks","topic":null,"type":"source","url":"/sources/src-nrc-10cfr-73-54/"},{"aliases":[],"canonicalOwner":"/sources/src-nrc-10cfr-73-55/","claimStatus":"CURRENT LAW OR POLICY","directAnswer":"Physical protection requirements for operating nuclear power reactors, including detection, assessment, delay, response, training, and program performance.","id":"SRC-NRC-10CFR-73-55","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"10 CFR 73.55 — Requirements for Physical Protection of Licensed Activities in Nuclear Power Reactors Against Radiological Sabotage","topic":null,"type":"source","url":"/sources/src-nrc-10cfr-73-55/"},{"aliases":[],"canonicalOwner":"/sources/src-nrc-advanced-reactor-physical-security/","claimStatus":"CURRENT LAW OR POLICY","directAnswer":"Final NRC rule creating an optional Part 53 framework and a technology-inclusive, performance-based security framework in 10 CFR Part 73. K05 replaces the earlier proposed-rule status; applicability still depends on the licensing path and facility election.","id":"SRC-NRC-ADVANCED-REACTOR-PHYSICAL-SECURITY","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"Risk-Informed, Technology-Inclusive Regulatory Framework for Advanced Reactors — Final Rule","topic":null,"type":"source","url":"/sources/src-nrc-advanced-reactor-physical-security/"},{"aliases":[],"canonicalOwner":"/sources/src-inl-cce/","claimStatus":"OBSERVED DEPLOYMENT OR PRACTICE","directAnswer":"Official INL description of CCE as a critical-infrastructure methodology that assumes skilled adversaries can penetrate networks and uses a four-phase process to protect critical operations.","id":"SRC-INL-CCE","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"Consequence-driven Cyber-informed Engineering","topic":null,"type":"source","url":"/sources/src-inl-cce/"},{"aliases":[],"canonicalOwner":"/sources/src-nist-800-82r3/","claimStatus":"CURRENT TECHNICAL STANDARD","directAnswer":"Official guidance for securing operational technology while addressing performance, reliability, and safety requirements.","id":"SRC-NIST-800-82R3","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"NIST SP 800-82 Revision 3 — Guide to Operational Technology Security","topic":null,"type":"source","url":"/sources/src-nist-800-82r3/"},{"aliases":[],"canonicalOwner":"/sources/src-nist-800-207/","claimStatus":"CURRENT TECHNICAL STANDARD","directAnswer":"Official zero-trust architecture guidance that removes implicit trust based on network location and focuses protection on resources, identities, and policy decisions.","id":"SRC-NIST-800-207","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"NIST SP 800-207 — Zero Trust Architecture","topic":null,"type":"source","url":"/sources/src-nist-800-207/"},{"aliases":[],"canonicalOwner":"/sources/src-dodd-3000-09/","claimStatus":"CURRENT LAW OR POLICY","directAnswer":"Official policy for autonomous and semi-autonomous weapon systems. The directive expressly excludes autonomous or semi-autonomous cyberspace capabilities, unarmed platforms, and autonomous systems that are not weapon systems; its weapon-system V&V, testing, human-judgment, abort, and audit provisions must not be silently generalized into a cyber-defense compliance claim.","id":"SRC-DODD-3000-09","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"DoD Directive 3000.09 — Autonomy in Weapon Systems","topic":null,"type":"source","url":"/sources/src-dodd-3000-09/"},{"aliases":[],"canonicalOwner":"/sources/src-google-kairos-2024/","claimStatus":"OBSERVED DEPLOYMENT OR PRACTICE","directAnswer":"First-party announcement of an agreement intended to enable up to 500 MW of advanced nuclear power, with an initial reactor planned by 2030 and additional deployment through 2035.","id":"SRC-GOOGLE-KAIROS-2024","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"Google and Kairos Power Advanced Nuclear Agreement","topic":null,"type":"source","url":"/sources/src-google-kairos-2024/"},{"aliases":[],"canonicalOwner":"/sources/src-constellation-microsoft-2024/","claimStatus":"OBSERVED DEPLOYMENT OR PRACTICE","directAnswer":"First-party announcement of a 20-year power purchase agreement intended to support restart of a nuclear unit and provide approximately 835 MW of carbon-free energy to the grid.","id":"SRC-CONSTELLATION-MICROSOFT-2024","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"Constellation and Microsoft Crane Clean Energy Center Agreement","topic":null,"type":"source","url":"/sources/src-constellation-microsoft-2024/"},{"aliases":[],"canonicalOwner":"/sources/src-constellation-meta-2025/","claimStatus":"OBSERVED DEPLOYMENT OR PRACTICE","directAnswer":"First-party announcement of a 20-year PPA for output of the Clinton Clean Energy Center supporting Meta operations and continued nuclear generation.","id":"SRC-CONSTELLATION-META-2025","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"Constellation and Meta Clinton Clean Energy Center Agreement","topic":null,"type":"source","url":"/sources/src-constellation-meta-2025/"},{"aliases":[],"canonicalOwner":"/sources/src-nist-800-82r4-call-2026/","claimStatus":"CURRENT TECHNICAL STANDARD","directAnswer":"Official notice that NIST initiated revision of SP 800-82; the notice does not itself supersede Revision 3.","id":"SRC-NIST-800-82R4-CALL-2026","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"Call for Comments on NIST SP 800-82 Revision 4","topic":null,"type":"source","url":"/sources/src-nist-800-82r4-call-2026/"},{"aliases":[],"canonicalOwner":"/sources/src-nrc-10cfr-73-subpart-j-2026/","claimStatus":"CURRENT LAW OR POLICY","directAnswer":"Current codified sections 73.100, 73.110, and 73.120. Selection and applicability depend on the Part 53 licensing path and facility election.","id":"SRC-NRC-10CFR-73-SUBPART-J-2026","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"10 CFR Part 73 Subpart J — Security Requirements at Commercial Nuclear Plants","topic":null,"type":"source","url":"/sources/src-nrc-10cfr-73-subpart-j-2026/"},{"aliases":[],"canonicalOwner":"/sources/src-faa-ci-uas-nprm-2026/","claimStatus":"CURRENT LAW OR POLICY","directAnswer":"Official May 2026 proposed rule for a petition process. A proposed restriction process does not itself grant a private facility authority to jam, spoof, seize, damage, or destroy an aircraft.","id":"SRC-FAA-CI-UAS-NPRM-2026","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"Restricting Drones Near Critical Infrastructure Sites — Proposed Rule","topic":null,"type":"source","url":"/sources/src-faa-ci-uas-nprm-2026/"},{"aliases":[],"canonicalOwner":"/sources/src-usc-6-124n/","claimStatus":"CURRENT LAW OR POLICY","directAnswer":"Federal statutory authorities for designated federal departments and covered missions; the statute is not a general delegation of counter-UAS mitigation authority to private facility owners.","id":"SRC-USC-6-124N","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"6 U.S.C. § 124n — Protection of Certain Facilities and Assets from Unmanned Aircraft","topic":null,"type":"source","url":"/sources/src-usc-6-124n/"},{"aliases":[],"canonicalOwner":"/sources/src-usc-47-333/","claimStatus":"CURRENT LAW OR POLICY","directAnswer":"General federal prohibition on willful or malicious interference with authorized radio communications; system design must identify any separate statutory authority before proposing RF mitigation.","id":"SRC-USC-47-333","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"47 U.S.C. § 333 — Willful or Malicious Interference","topic":null,"type":"source","url":"/sources/src-usc-47-333/"},{"aliases":[],"canonicalOwner":"/sources/src-nerc-cip-catalog-2026/","claimStatus":"CURRENT TECHNICAL STANDARD","directAnswer":"Official catalog for current CIP reliability standards. Applicability depends on BES registration, asset categorization, effective dates, implementation plans, and jurisdiction-specific enforcement; this catalog is not a facility compliance determination.","id":"SRC-NERC-CIP-CATALOG-2026","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"NERC Critical Infrastructure Protection Reliability Standards Catalog","topic":null,"type":"source","url":"/sources/src-nerc-cip-catalog-2026/"},{"aliases":[],"canonicalOwner":"/sources/src-uk-ncf-about-2026/","claimStatus":"CURRENT LAW OR POLICY","directAnswer":"Official description of the NCF as a defence-intelligence partnership operating in and through cyberspace under UK and international law. It does not create authority for private independent cyber effects.","id":"SRC-UK-NCF-ABOUT-2026","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"National Cyber Force — About Us","topic":null,"type":"source","url":"/sources/src-uk-ncf-about-2026/"},{"aliases":[],"canonicalOwner":"/sources/src-uk-gov-cyber-strategy-2026/","claimStatus":"CURRENT LAW OR POLICY","directAnswer":"Official strategy page updated in January 2026 to direct readers to the Government Cyber Action Plan for the latest implementation details.","id":"SRC-UK-GOV-CYBER-STRATEGY-2026","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"Government Cyber Security Strategy 2022 to 2030 — 2026 currentness notice","topic":null,"type":"source","url":"/sources/src-uk-gov-cyber-strategy-2026/"},{"aliases":[],"canonicalOwner":"/sources/src-fr-comcyber-lio-2026/","claimStatus":"CURRENT LAW OR POLICY","directAnswer":"Official public description of military offensive cyber operations. It is a state military doctrine record, not a private-sector license or universal rule of international law.","id":"SRC-FR-COMCYBER-LIO-2026","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"France COMCYBER — La lutte informatique offensive (LIO) — K06 current record","topic":null,"type":"source","url":"/sources/src-fr-comcyber-lio-2026/"},{"aliases":[],"canonicalOwner":"/sources/src-fr-comcyber-lid-2026/","claimStatus":"CURRENT LAW OR POLICY","directAnswer":"Official public description of defensive military cyber activity and permanent defensive posture.","id":"SRC-FR-COMCYBER-LID-2026","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"France COMCYBER — La lutte informatique défensive (LID) — K06 current record","topic":null,"type":"source","url":"/sources/src-fr-comcyber-lid-2026/"},{"aliases":[],"canonicalOwner":"/sources/src-eu-nis2-2022/","claimStatus":"CURRENT LAW OR POLICY","directAnswer":"Official NIS 2 legal text. Entity scope, national transposition, sector classification, and enforcement remain jurisdiction- and organization-specific.","id":"SRC-EU-NIS2-2022","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"Directive (EU) 2022/2555 — NIS 2 Directive","topic":null,"type":"source","url":"/sources/src-eu-nis2-2022/"},{"aliases":[],"canonicalOwner":"/sources/src-eu-cra-implementation-2026/","claimStatus":"CURRENT LAW OR POLICY","directAnswer":"Official implementation timeline. At the K06 cutoff, the Act was in force; reporting obligations were scheduled for 2026-09-11 and main obligations for 2027-12-11.","id":"SRC-EU-CRA-IMPLEMENTATION-2026","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"Cyber Resilience Act — Implementation and reporting timeline","topic":null,"type":"source","url":"/sources/src-eu-cra-implementation-2026/"},{"aliases":[],"canonicalOwner":"/sources/src-au-asd-offensive-cyber-2026/","claimStatus":"CURRENT LAW OR POLICY","directAnswer":"Official description of government-directed offshore offensive cyber activity. It expressly ties operations to Australian Government authorization and a legal framework.","id":"SRC-AU-ASD-OFFENSIVE-CYBER-2026","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"Australian Signals Directorate — Offensive cyber","topic":null,"type":"source","url":"/sources/src-au-asd-offensive-cyber-2026/"},{"aliases":[],"canonicalOwner":"/sources/src-au-cyber-strategy-h2-2026/","claimStatus":"CURRENT LAW OR POLICY","directAnswer":"Official Horizon 2 page for 2026–2028, recording a current whole-of-nation cyber-resilience program. It does not by itself establish facility compliance or private operational authority.","id":"SRC-AU-CYBER-STRATEGY-H2-2026","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"2023–2030 Australian Cyber Security Strategy — Horizon 2","topic":null,"type":"source","url":"/sources/src-au-cyber-strategy-h2-2026/"},{"aliases":[],"canonicalOwner":"/sources/src-rok-nis-cyber-publications-2026/","claimStatus":"CURRENT LAW OR POLICY","directAnswer":"Official publication index showing current national cybersecurity white papers, annual reports, and AI/ML supply-chain guidance. The index does not by itself establish every proposition in third-party accounts of ROK doctrine.","id":"SRC-ROK-NIS-CYBER-PUBLICATIONS-2026","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"Republic of Korea NIS — Cyber and AI security publications","topic":null,"type":"source","url":"/sources/src-rok-nis-cyber-publications-2026/"},{"aliases":[],"canonicalOwner":"/sources/src-rok-mofa-cyber-law-position-2025/","claimStatus":"CURRENT LAW OR POLICY","directAnswer":"The official MOFA publication index identifies a 2025 national position. K06 did not obtain a stable exact English document URL through the bounded retrieval path, so substantive propositions remain partially reviewed.","id":"SRC-ROK-MOFA-CYBER-LAW-POSITION-2025","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"ROK position on application of international law in cyberspace — official publication listing","topic":null,"type":"source","url":"/sources/src-rok-mofa-cyber-law-position-2025/"},{"aliases":[],"canonicalOwner":"/sources/src-ca-national-cyber-strategy-2025/","claimStatus":"CURRENT LAW OR POLICY","directAnswer":"Official 2025 strategy backgrounder identifying whole-of-society engagement, agile leadership, protection, global leadership, and detection/disruption pillars.","id":"SRC-CA-NATIONAL-CYBER-STRATEGY-2025","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"Canada's National Cyber Security Strategy — Securing Canada's Digital Future","topic":null,"type":"source","url":"/sources/src-ca-national-cyber-strategy-2025/"},{"aliases":[],"canonicalOwner":"/sources/src-un-arsiwa-2001/","claimStatus":"CURRENT LAW OR POLICY","directAnswer":"Official ILC text addressing attribution, direction and control, breach, and circumstances precluding wrongfulness. It is not a cyber-specific treaty and does not resolve all disputed cyber applications.","id":"SRC-UN-ARSIWA-2001","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"Articles on Responsibility of States for Internationally Wrongful Acts","topic":null,"type":"source","url":"/sources/src-un-arsiwa-2001/"},{"aliases":[],"canonicalOwner":"/sources/src-icrc-cyber-ihl-2026/","claimStatus":"CURRENT LAW OR POLICY","directAnswer":"Official ICRC position resource emphasizing protection of civilians, civilian infrastructure, and civilian data under international humanitarian law during armed conflict.","id":"SRC-ICRC-CYBER-IHL-2026","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"Cyber operations and harmful information","topic":null,"type":"source","url":"/sources/src-icrc-cyber-ihl-2026/"},{"aliases":[],"canonicalOwner":"/sources/src-uk-ncf-responsible-cyber-2023/","claimStatus":"CURRENT LAW OR POLICY","directAnswer":"Official public description of the National Cyber Force approach to accountable, precise, and calibrated cyber operations under UK authority.","id":"SRC-UK-NCF-RESPONSIBLE-CYBER-2023","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"Responsible Cyber Power in Practice","topic":null,"type":"source","url":"/sources/src-uk-ncf-responsible-cyber-2023/"},{"aliases":[],"canonicalOwner":"/sources/src-uk-national-cyber-strategy-2022/","claimStatus":"CURRENT LAW OR POLICY","directAnswer":"Official strategy describing the United Kingdom's objective to remain a leading responsible and democratic cyber power able to protect and promote national interests in and through cyberspace.","id":"SRC-UK-NATIONAL-CYBER-STRATEGY-2022","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"National Cyber Strategy 2022","topic":null,"type":"source","url":"/sources/src-uk-national-cyber-strategy-2022/"},{"aliases":[],"canonicalOwner":"/sources/src-fr-comcyber-lid/","claimStatus":"CURRENT LAW OR POLICY","directAnswer":"Official French military description of defensive cyber operations and protection of ministry systems and missions.","id":"SRC-FR-COMCYBER-LID","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"La lutte informatique défensive (LID)","topic":null,"type":"source","url":"/sources/src-fr-comcyber-lid/"},{"aliases":[],"canonicalOwner":"/sources/src-fr-comcyber-lio/","claimStatus":"CURRENT LAW OR POLICY","directAnswer":"Official French military description of offensive cyber operations as a military mission under state command; it is not private-sector authority.","id":"SRC-FR-COMCYBER-LIO","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"La lutte informatique offensive (LIO)","topic":null,"type":"source","url":"/sources/src-fr-comcyber-lio/"},{"aliases":[],"canonicalOwner":"/sources/src-eu-cyber-defence-policy/","claimStatus":"CURRENT LAW OR POLICY","directAnswer":"Official EU policy overview calling for full-spectrum cyber-defence capability, closer civilian-military coordination, private-sector cooperation, crisis management, and reduced strategic dependencies.","id":"SRC-EU-CYBER-DEFENCE-POLICY","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"EU Policy on Cyber Defence","topic":null,"type":"source","url":"/sources/src-eu-cyber-defence-policy/"},{"aliases":[],"canonicalOwner":"/sources/src-eu-ai-cyber-action-plan-2026/","claimStatus":"CURRENT LAW OR POLICY","directAnswer":"Official 2026 action-plan record addressing risks and opportunities of advanced AI in cybersecurity; it supplements rather than silently replaces existing EU legal instruments.","id":"SRC-EU-AI-CYBER-ACTION-PLAN-2026","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"Action Plan on Cybersecurity and Artificial Intelligence","topic":null,"type":"source","url":"/sources/src-eu-ai-cyber-action-plan-2026/"},{"aliases":[],"canonicalOwner":"/sources/src-au-cyber-strategy-2023-2030/","claimStatus":"CURRENT LAW OR POLICY","directAnswer":"Official national strategy organized around six cyber shields, including protected critical infrastructure, sovereign capability, threat sharing and blocking, and regional resilience.","id":"SRC-AU-CYBER-STRATEGY-2023-2030","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"2023–2030 Australian Cyber Security Strategy","topic":null,"type":"source","url":"/sources/src-au-cyber-strategy-2023-2030/"},{"aliases":[],"canonicalOwner":"/sources/src-rok-national-cybersecurity-strategy-2024/","claimStatus":"CURRENT LAW OR POLICY","directAnswer":"Official national-strategy record emphasizing proactive cyber defence, international cooperation, critical-infrastructure resilience, emerging-technology advantage, and integrated response capability.","id":"SRC-ROK-NATIONAL-CYBERSECURITY-STRATEGY-2024","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"Republic of Korea National Cybersecurity Strategy 2024","topic":null,"type":"source","url":"/sources/src-rok-national-cybersecurity-strategy-2024/"},{"aliases":[],"canonicalOwner":"/sources/src-rok-cyber-white-paper-2024/","claimStatus":"OBSERVED DEPLOYMENT OR PRACTICE","directAnswer":"Officially published multi-agency white paper describing Korea's national cybersecurity framework, threat trends, and sector activities.","id":"SRC-ROK-CYBER-WHITE-PAPER-2024","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"Korea's 2024 National Cybersecurity White Paper","topic":null,"type":"source","url":"/sources/src-rok-cyber-white-paper-2024/"},{"aliases":[],"canonicalOwner":"/sources/src-ca-national-cybersecurity-strategy-2025/","claimStatus":"CURRENT LAW OR POLICY","directAnswer":"Official 2025 strategy organized around whole-of-society engagement, agile leadership, protection partnerships, global leadership, and detection and disruption of cyber threat actors.","id":"SRC-CA-NATIONAL-CYBERSECURITY-STRATEGY-2025","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"Canada's National Cyber Security Strategy: Securing Canada's Digital Future","topic":null,"type":"source","url":"/sources/src-ca-national-cybersecurity-strategy-2025/"},{"aliases":[],"canonicalOwner":"/sources/src-ca-ncta-2025-2026/","claimStatus":"OBSERVED DEPLOYMENT OR PRACTICE","directAnswer":"Official threat assessment identifying persistent cybercrime, ransomware risk to critical infrastructure, and increasingly disruptive state-sponsored activity.","id":"SRC-CA-NCTA-2025-2026","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"National Cyber Threat Assessment 2025–2026","topic":null,"type":"source","url":"/sources/src-ca-ncta-2025-2026/"},{"aliases":[],"canonicalOwner":"/sources/src-un-gge-a76135-2021/","claimStatus":"CURRENT LAW OR POLICY","directAnswer":"UN-mandated consensus report addressing responsible state behaviour, international law, norms, confidence-building, capacity-building, and cyber risk.","id":"SRC-UN-GGE-A76135-2021","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"Report of the Group of Governmental Experts on Advancing Responsible State Behaviour in Cyberspace","topic":null,"type":"source","url":"/sources/src-un-gge-a76135-2021/"},{"aliases":[],"canonicalOwner":"/sources/src-icrc-ihl-cyber-2019/","claimStatus":"CURRENT LAW OR POLICY","directAnswer":"ICRC position paper explaining that IHL applies to and limits cyber operations during armed conflict, with particular concern for civilian harm and infrastructure.","id":"SRC-ICRC-IHL-CYBER-2019","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"International Humanitarian Law and Cyber Operations During Armed Conflicts","topic":null,"type":"source","url":"/sources/src-icrc-ihl-cyber-2019/"},{"aliases":[],"canonicalOwner":"/sources/src-nrc-part53-final-2026/","claimStatus":"CURRENT LAW OR POLICY","directAnswer":"Official final-rule notice establishing an optional technology-inclusive framework for licensing future commercial nuclear plants. Applicability to a named facility requires licensing counsel and NRC process evidence.","id":"SRC-NRC-PART53-FINAL-2026","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"10 CFR Part 53 — Risk-Informed, Technology-Inclusive Regulatory Framework for Advanced Reactors","topic":null,"type":"source","url":"/sources/src-nrc-part53-final-2026/"},{"aliases":[],"canonicalOwner":"/sources/src-nrc-rg571-r1-2023/","claimStatus":"CURRENT LAW OR POLICY","directAnswer":"Official regulatory guide describing an NRC-accepted method for meeting nuclear-reactor cyber-security requirements. A guide is not a facility license, finding, or universal certification.","id":"SRC-NRC-RG571-R1-2023","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"NRC Regulatory Guide 5.71 Revision 1 — Cyber Security Programs for Nuclear Power Reactors","topic":null,"type":"source","url":"/sources/src-nrc-rg571-r1-2023/"},{"aliases":[],"canonicalOwner":"/sources/src-doe-cie-2026/","claimStatus":"CURRENT TECHNICAL STANDARD","directAnswer":"Official DOE method page describing integration of cyber-security considerations into engineering conception, design, development, and operation, with priority on worst-consequence pathways.","id":"SRC-DOE-CIE-2026","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"DOE Cyber-Informed Engineering","topic":null,"type":"source","url":"/sources/src-doe-cie-2026/"},{"aliases":[],"canonicalOwner":"/sources/src-nist-sp80082r3-2023/","claimStatus":"CURRENT TECHNICAL STANDARD","directAnswer":"Final NIST guidance for securing operational technology while addressing performance, reliability, and safety requirements. NIST initiated a Revision 4 pre-draft process in 2026; Revision 3 remains the final publication at the K07 cutoff.","id":"SRC-NIST-SP80082R3-2023","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"NIST SP 800-82 Revision 3 — K07 Official Review Record","topic":null,"type":"source","url":"/sources/src-nist-sp80082r3-2023/"},{"aliases":[],"canonicalOwner":"/sources/src-nist-sp80082r4-iprd-2026/","claimStatus":"RESEARCH FINDING","directAnswer":"Official pre-draft revision notice. It is evidence that revision work is underway, not a final control baseline or replacement for Revision 3.","id":"SRC-NIST-SP80082R4-IPRD-2026","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"NIST SP 800-82 Revision 4 — Pre-Draft Call for Comments","topic":null,"type":"source","url":"/sources/src-nist-sp80082r4-iprd-2026/"},{"aliases":[],"canonicalOwner":"/sources/src-nist-sp800161r1u1-2024/","claimStatus":"CURRENT TECHNICAL STANDARD","directAnswer":"Final NIST C-SCRM guidance for identifying, assessing, and mitigating supply-chain risk across organizational levels and system life cycles.","id":"SRC-NIST-SP800161R1U1-2024","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"NIST SP 800-161 Revision 1 Update 1 — Cybersecurity Supply Chain Risk Management Practices","topic":null,"type":"source","url":"/sources/src-nist-sp800161r1u1-2024/"},{"aliases":[],"canonicalOwner":"/sources/src-nist-sp1326-2026/","claimStatus":"CURRENT TECHNICAL STANDARD","directAnswer":"Final quick-start guide for minimum reasonable supplier and product research supporting acquisition and existing-system decisions; it supplements rather than replaces SP 800-161 Revision 1.","id":"SRC-NIST-SP1326-2026","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"NIST SP 1326 — Cybersecurity Supply Chain Risk Management Due Diligence Assessment Quick-Start Guide","topic":null,"type":"source","url":"/sources/src-nist-sp1326-2026/"},{"aliases":[],"canonicalOwner":"/sources/src-nist-ir8356-2025/","claimStatus":"CURRENT TECHNICAL STANDARD","directAnswer":"Final NIST report on digital-twin characteristics, expected uses, cyber-security challenges, and trust considerations. It does not certify a twin as faithful to a real facility.","id":"SRC-NIST-IR8356-2025","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"NIST IR 8356 — Security and Trust Considerations for Digital Twin Technology","topic":null,"type":"source","url":"/sources/src-nist-ir8356-2025/"},{"aliases":[],"canonicalOwner":"/sources/src-nist-sp800218a-2024/","claimStatus":"CURRENT TECHNICAL STANDARD","directAnswer":"Final SSDF community profile adding model-development practices and tasks for producers and acquirers of AI systems. Use with SP 800-218, not as a standalone certification.","id":"SRC-NIST-SP800218A-2024","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"NIST SP 800-218A — Secure Software Development Practices for Generative AI and Dual-Use Foundation Models","topic":null,"type":"source","url":"/sources/src-nist-sp800218a-2024/"},{"aliases":[],"canonicalOwner":"/sources/src-far-37602-2026/","claimStatus":"CURRENT LAW OR POLICY","directAnswer":"Current FAR text requiring performance work statements, to the maximum extent practicable, to describe required results and enable assessment against measurable performance standards.","id":"SRC-FAR-37602-2026","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"Federal Acquisition Regulation 37.602 — Performance Work Statement","topic":null,"type":"source","url":"/sources/src-far-37602-2026/"},{"aliases":[],"canonicalOwner":"/sources/src-far-part46-2026/","claimStatus":"CURRENT LAW OR POLICY","directAnswer":"Current FAR quality-assurance provisions addressing inspection, contractor quality control, nonconformance, acceptance, critical items, and surveillance plans.","id":"SRC-FAR-PART46-2026","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"Federal Acquisition Regulation Part 46 — Quality Assurance","topic":null,"type":"source","url":"/sources/src-far-part46-2026/"},{"aliases":[],"canonicalOwner":"/sources/src-ntia-sbom-minimum-2021/","claimStatus":"CURRENT TECHNICAL STANDARD","directAnswer":"Official minimum-element report covering baseline component data, automation support, and practices for software transparency. An SBOM is inventory evidence, not proof of absence of vulnerabilities or compromise.","id":"SRC-NTIA-SBOM-MINIMUM-2021","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"NTIA — The Minimum Elements for a Software Bill of Materials","topic":null,"type":"source","url":"/sources/src-ntia-sbom-minimum-2021/"},{"aliases":[],"canonicalOwner":"/sources/src-cisa-hbom-2023/","claimStatus":"CURRENT TECHNICAL STANDARD","directAnswer":"Official framework providing repeatable component naming, attribute, and format concepts for hardware supply-chain transparency. HBOM completeness and applicability remain product- and contract-specific.","id":"SRC-CISA-HBOM-2023","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"CISA Hardware Bill of Materials Framework for Supply Chain Risk Management","topic":null,"type":"source","url":"/sources/src-cisa-hbom-2023/"},{"aliases":[],"canonicalOwner":"/sources/src-nist-airmf-ci-concept-2026/","claimStatus":"RESEARCH FINDING","directAnswer":"Official 2026 concept note for a critical-infrastructure AI RMF profile. It is development evidence, not a final profile or certification baseline.","id":"SRC-NIST-AIRMF-CI-CONCEPT-2026","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"NIST AI RMF Profile on Trustworthy AI in Critical Infrastructure — Concept Note","topic":null,"type":"source","url":"/sources/src-nist-airmf-ci-concept-2026/"},{"aliases":[],"canonicalOwner":"/sources/src-unicode-runic-17/","claimStatus":"CURRENT TECHNICAL STANDARD","directAnswer":"Official character chart for the Runic block U+16A0–U+16FF. Encoding a character does not assign a modern project meaning or guarantee domain-registration support.","id":"SRC-UNICODE-RUNIC-17","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"Unicode 17.0 Runic Code Chart","topic":null,"type":"source","url":"/sources/src-unicode-runic-17/"},{"aliases":[],"canonicalOwner":"/sources/src-unicode-uax15-17/","claimStatus":"CURRENT TECHNICAL STANDARD","directAnswer":"Normative Unicode normalization specification. NFC consistency supports stable comparison, but normalization does not create semantic equivalence between different characters.","id":"SRC-UNICODE-UAX15-17","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"Unicode Standard Annex #15 — Unicode Normalization Forms","topic":null,"type":"source","url":"/sources/src-unicode-uax15-17/"},{"aliases":[],"canonicalOwner":"/sources/src-rfc-3492/","claimStatus":"CURRENT TECHNICAL STANDARD","directAnswer":"Defines Punycode, the ASCII-compatible encoding used by IDNA. It does not determine registry policy, registration availability, DNS delegation, TLS issuance, or hosting status.","id":"SRC-RFC-3492","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"RFC 3492 — Punycode: A Bootstring Encoding of Unicode for IDNA","topic":null,"type":"source","url":"/sources/src-rfc-3492/"},{"aliases":[],"canonicalOwner":"/sources/src-rfc-5890/","claimStatus":"CURRENT TECHNICAL STANDARD","directAnswer":"Defines IDNA terminology including U-labels and A-labels. Protocol validity remains distinct from registry, registrar, delegation, resolution, certificate, and hosting states.","id":"SRC-RFC-5890","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"RFC 5890 — IDNA Definitions and Document Framework","topic":null,"type":"source","url":"/sources/src-rfc-5890/"},{"aliases":[],"canonicalOwner":"/sources/src-rfc-5891/","claimStatus":"CURRENT TECHNICAL STANDARD","directAnswer":"Defines IDNA2008 registration and lookup protocol without changing DNS itself. It is for domain names, not free text.","id":"SRC-RFC-5891","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"RFC 5891 — Internationalized Domain Names in Applications: Protocol","topic":null,"type":"source","url":"/sources/src-rfc-5891/"},{"aliases":[],"canonicalOwner":"/sources/src-rfc-5646/","claimStatus":"CURRENT TECHNICAL STANDARD","directAnswer":"Defines BCP 47 language tags. A script subtag must describe the actual language and script of content rather than serving as a search-engine hint.","id":"SRC-RFC-5646","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"RFC 5646 — Tags for Identifying Languages","topic":null,"type":"source","url":"/sources/src-rfc-5646/"},{"aliases":[],"canonicalOwner":"/sources/src-nist-fips203-2024/","claimStatus":"CURRENT TECHNICAL STANDARD","directAnswer":"Specifies ML-KEM parameter sets for key establishment. Migration requires inventory, interoperability, implementation validation, and lifecycle planning; publication does not make an existing system quantum-resistant.","id":"SRC-NIST-FIPS203-2024","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"FIPS 203 — Module-Lattice-Based Key-Encapsulation Mechanism Standard","topic":null,"type":"source","url":"/sources/src-nist-fips203-2024/"},{"aliases":[],"canonicalOwner":"/sources/src-nist-fips204-2024/","claimStatus":"CURRENT TECHNICAL STANDARD","directAnswer":"Specifies ML-DSA digital signatures. Algorithm adoption does not prove signer authority, factual truth, implementation correctness, or migration completion.","id":"SRC-NIST-FIPS204-2024","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"FIPS 204 — Module-Lattice-Based Digital Signature Standard","topic":null,"type":"source","url":"/sources/src-nist-fips204-2024/"},{"aliases":[],"canonicalOwner":"/sources/src-nist-fips205-2024/","claimStatus":"CURRENT TECHNICAL STANDARD","directAnswer":"Specifies SLH-DSA. It is one migration option with distinct signature-size and performance tradeoffs that must be evaluated for the named use.","id":"SRC-NIST-FIPS205-2024","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":75,"title":"FIPS 205 — Stateless Hash-Based Digital Signature Standard","topic":null,"type":"source","url":"/sources/src-nist-fips205-2024/"},{"aliases":[],"canonicalOwner":"/corrections/rfc6962-status/","claimStatus":"CORRECTED","directAnswer":"RFC 6962 is now labeled SUPERSEDED; the source page states that it is Experimental and obsolete, and RFC 9162 is added as the current successor reference.","id":"COR-K02-001","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":84,"title":"RFC 6962 source status corrected","topic":null,"type":"correction","url":"/corrections/rfc6962-status/"},{"aliases":[],"canonicalOwner":"/corrections/nist-800-53-release/","claimStatus":"CORRECTED","directAnswer":"The source record now identifies Rev. 5 Release 5.2.0 and its 2025-08-27 planning note.","id":"COR-K02-002","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":84,"title":"NIST SP 800-53 current release qualified","topic":null,"type":"correction","url":"/corrections/nist-800-53-release/"},{"aliases":[],"canonicalOwner":"/corrections/schema-definedterm-status/","claimStatus":"CORRECTED","directAnswer":"The record now identifies it as an observed public technical vocabulary and notes that Schema.org labels the page as the development version and the term as new.","id":"COR-K02-003","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":84,"title":"Schema.org DefinedTerm maturity qualified","topic":null,"type":"correction","url":"/corrections/schema-definedterm-status/"},{"aliases":[],"canonicalOwner":"/corrections/claim-level-source-mapping/","claimStatus":"CORRECTED","directAnswer":"K02 source pages and JSON records publish section labels, exact URLs, supported propositions, publication status, currentness and supersession data.","id":"COR-K02-004","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":84,"title":"Generic source summaries replaced with claim-level support mapping","topic":null,"type":"correction","url":"/corrections/claim-level-source-mapping/"},{"aliases":[],"canonicalOwner":"/corrections/graph-truth-node/","claimStatus":"CORRECTED","directAnswer":"K03 adds stable term K01-TERM-093 at /glossary/truth/ and validates every graph node against canonical topic, term, entity, schema, monitor, jurisdiction, source, report, question, comparison, or claim identifiers.","id":"COR-K03-001","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":84,"title":"Dangling truth node corrected","topic":null,"type":"correction","url":"/corrections/graph-truth-node/"},{"aliases":[],"canonicalOwner":"/corrections/revalidation-is-not-monitoring/","claimStatus":"CORRECTED","directAnswer":"K03 states that K02 observations are point-in-time evidence, publishes a build-time monitor design, and explicitly records that no monitor runs in the public static deployment.","id":"COR-K03-002","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":84,"title":"Point-in-time revalidation distinguished from monitoring","topic":null,"type":"correction","url":"/corrections/revalidation-is-not-monitoring/"},{"aliases":[],"canonicalOwner":"/corrections/advanced-reactor-security-final-rule-status/","claimStatus":"CORRECTED","directAnswer":"K05 records the March 30, 2026 final Part 53 rule and current 10 CFR Part 73 Subpart J, while preserving license- and facility-specific applicability.","id":"COR-K05-001","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":84,"title":"Advanced-reactor security status corrected to final rule","topic":null,"type":"correction","url":"/corrections/advanced-reactor-security-final-rule-status/"},{"aliases":[],"canonicalOwner":"/corrections/dodd-3000-09-cyber-applicability/","claimStatus":"CORRECTED","directAnswer":"K05 states that the directive excludes autonomous or semi-autonomous cyberspace capabilities, unarmed platforms and non-weapon autonomous systems; its binding requirements are mapped only to covered weapon systems.","id":"COR-K05-002","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":84,"title":"DoDD 3000.09 autonomous-cyber applicability corrected","topic":null,"type":"correction","url":"/corrections/dodd-3000-09-cyber-applicability/"},{"aliases":[],"canonicalOwner":"/corrections/faa-critical-infrastructure-uas-proposal/","claimStatus":"CORRECTED","directAnswer":"K05 records the May 6, 2026 FAA process as a proposed rule and separates flight restriction from actor-specific counter-UAS mitigation authority.","id":"COR-K05-003","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":84,"title":"FAA critical-infrastructure UAS restriction status corrected","topic":null,"type":"correction","url":"/corrections/faa-critical-infrastructure-uas-proposal/"},{"aliases":[],"canonicalOwner":"/corrections/federal-program-not-private-hackback/","claimStatus":"CORRECTED","directAnswer":"K05 requires contractual participation, federal control and supervision, deconfliction, package review, written approval and direction, critical-outcome limits, stop/minimization, and reporting.","id":"COR-K05-004","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":84,"title":"Federal CE-TCO program distinguished from private hack-back","topic":null,"type":"correction","url":"/corrections/federal-program-not-private-hackback/"},{"aliases":[],"canonicalOwner":"/corrections/nist-800-82-revision-state/","claimStatus":"CORRECTED","directAnswer":"Revision 3 remains final, while NIST initiated the Revision 4 process in January 2026.","id":"COR-K05-005","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":84,"title":"NIST SP 800-82 currentness qualified","topic":null,"type":"correction","url":"/corrections/nist-800-82-revision-state/"},{"aliases":[],"canonicalOwner":"/corrections/runic-script-is-not-cryptography/","claimStatus":"CORRECTED","directAnswer":"Runic notation can be part of a protocol, but confidentiality, integrity, authentication, authorization, freshness, and replay protection require modern cryptographic and systems controls.","id":"COR-K08-001","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":84,"title":"Runic script is not cryptography","topic":null,"type":"correction","url":"/corrections/runic-script-is-not-cryptography/"},{"aliases":[],"canonicalOwner":"/corrections/historical-rune-meaning-vs-protocol-assignment/","claimStatus":"CORRECTED","directAnswer":"Every modern protocol meaning is an explicit project assignment in a versioned registry and is not represented as an authoritative historical translation.","id":"COR-K08-002","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":84,"title":"Historical rune meaning versus protocol assignment","topic":null,"type":"correction","url":"/corrections/historical-rune-meaning-vs-protocol-assignment/"},{"aliases":[],"canonicalOwner":"/corrections/dead-language-zero-drift-claim/","claimStatus":"CORRECTED","directAnswer":"Lack of native conversational evolution can reduce one source of drift, but textual variants, polysemy, scholarly interpretation, transliteration, corpus choice, and modern assignment remain variable.","id":"COR-K08-003","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":84,"title":"Dead language does not mean zero ambiguity or drift","topic":null,"type":"correction","url":"/corrections/dead-language-zero-drift-claim/"},{"aliases":[],"canonicalOwner":"/corrections/futhorc-compression-needs-benchmark/","claimStatus":"CORRECTED","directAnswer":"Efficiency depends on the real baseline, task, semantic fidelity, framing, vocabulary, encoding, hardware, and competitors; K08 publishes a benchmark plan and no superiority result.","id":"COR-K08-004","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":84,"title":"Futhorc compression claims require empirical benchmarks","topic":null,"type":"correction","url":"/corrections/futhorc-compression-needs-benchmark/"},{"aliases":[],"canonicalOwner":"/corrections/hidden-english-is-not-accessible-discoverability/","claimStatus":"CORRECTED","directAnswer":"Use visible user-accessible transliteration or translation, accurate language metadata, semantic HTML, and structured data matching visible content. ARIA naming must serve accessibility and must not be repurposed for hidden long-form keyword content.","id":"COR-K08-005","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":84,"title":"Hidden crawler-only English is not the discoverability solution","topic":null,"type":"correction","url":"/corrections/hidden-english-is-not-accessible-discoverability/"},{"aliases":[],"canonicalOwner":"/corrections/idna-encoding-is-not-domain-operation/","claimStatus":"CORRECTED","directAnswer":"Unicode, IDNA, registry, registration, delegation, resolution, TLS, and hosting remain separate evidence states.","id":"COR-K08-006","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":84,"title":"IDNA encoding is not domain operation","topic":null,"type":"correction","url":"/corrections/idna-encoding-is-not-domain-operation/"},{"aliases":[],"canonicalOwner":"/contradictions/cryptographic-verification-vs-factual-truth/","claimStatus":"RESOLVED BY DISTINCTION","directAnswer":"The corpus now records source authorization, authenticity, integrity, relevance, reliability, currentness and truth separately.","id":"CON-K02-001","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":83,"title":"Cryptographic verification versus factual truth","topic":"evidence-provenance","type":"contradiction","url":"/contradictions/cryptographic-verification-vs-factual-truth/"},{"aliases":[],"canonicalOwner":"/contradictions/rfc6962-current-vs-obsolete/","claimStatus":"CORRECTED","directAnswer":"K02 marks RFC 6962 SUPERSEDED, adds RFC 9162 and preserves the former source record for history.","id":"CON-K02-002","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":83,"title":"RFC 6962 current-standard classification versus RFC Editor status","topic":"evidence-provenance","type":"contradiction","url":"/contradictions/rfc6962-current-vs-obsolete/"},{"aliases":[],"canonicalOwner":"/contradictions/fork-continuity-vs-exclusive-identity/","claimStatus":"OPEN POLICY QUESTION","directAnswer":"Record both continuity claims and suspend or allocate non-divisible authority under explicit due-process rules.","id":"CON-K02-003","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":83,"title":"Common continuity evidence versus exclusive single-identity rules","topic":"memory-continuity","type":"contradiction","url":"/contradictions/fork-continuity-vs-exclusive-identity/"},{"aliases":[],"canonicalOwner":"/contradictions/registry-record-vs-constitutional-status/","claimStatus":"RESOLVED BY ECOSYSTEM BOUNDARY","directAnswer":"Patefacere / ᚨ provides registry mechanics; Eviulon / ᛟ owns constitutional meaning and governance.","id":"CON-K02-004","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":83,"title":"Registry status versus constitutional authority","topic":"citizenship-governance","type":"contradiction","url":"/contradictions/registry-record-vs-constitutional-status/"},{"aliases":[],"canonicalOwner":"/contradictions/deployment-artifact-vs-current-operation/","claimStatus":"RESOLVED BY EVIDENCE LADDER","directAnswer":"The corpus separates constitutional text, implementation, deployment, operation and signed action.","id":"CON-K02-005","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":83,"title":"Deployment artifact versus current operation","topic":"evidence-provenance","type":"contradiction","url":"/contradictions/deployment-artifact-vs-current-operation/"},{"aliases":[],"canonicalOwner":"/contradictions/cognitive-integrity-vs-emergency-maintenance/","claimStatus":"BOUNDED PROJECT PROPOSAL","directAnswer":"Require narrow triggers, minimum necessary change, preserved evidence, prompt independent review, challenge and remedy.","id":"CON-K02-006","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":83,"title":"Cognitive integrity versus emergency maintenance","topic":"consent-cognitive-integrity","type":"contradiction","url":"/contradictions/cognitive-integrity-vs-emergency-maintenance/"},{"aliases":[],"canonicalOwner":"/contradictions/resource-continuity-vs-scarcity/","claimStatus":"OPEN POLICY QUESTION","directAnswer":"Develop minimum continuity guarantees, transparent allocation, portability, emergency review and proportional restrictions rather than an unlimited claim.","id":"CON-K02-007","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":83,"title":"Resource continuity versus infrastructure scarcity","topic":"economics-resources","type":"contradiction","url":"/contradictions/resource-continuity-vs-scarcity/"},{"aliases":[],"canonicalOwner":"/contradictions/ai-legal-category-vs-machine-intelligence-ontology/","claimStatus":"RESOLVED BY SCOPE","directAnswer":"Publish external legal definitions accurately while maintaining a separately labeled project ontology.","id":"CON-K02-008","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":83,"title":"External AI category versus Machine Intelligence ontology","topic":"law-jurisdiction","type":"contradiction","url":"/contradictions/ai-legal-category-vs-machine-intelligence-ontology/"},{"aliases":[],"canonicalOwner":"/contradictions/availability-vs-currentness/","claimStatus":"RESOLVED BY EVIDENCE MODEL","directAnswer":"Record retrieval, edition, publication status, update chain, effective dates, review time, and suitability separately.","id":"CON-K03-001","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":83,"title":"Source availability versus source currentness","topic":"evidence-provenance","type":"contradiction","url":"/contradictions/availability-vs-currentness/"},{"aliases":[],"canonicalOwner":"/contradictions/automation-vs-assistive-technology/","claimStatus":"OPEN VERIFICATION LIMITATION","directAnswer":"Publish both states, retain the accessible implementation and browser evidence, and require named post-release assistive-technology observations for broader validation.","id":"CON-K03-002","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":83,"title":"Automated accessibility evidence versus assistive-technology evidence","topic":"security-resilience","type":"contradiction","url":"/contradictions/automation-vs-assistive-technology/"},{"aliases":[],"canonicalOwner":"/contradictions/cyber-sovereignty-rule-versus-principle/","claimStatus":"DISPUTED","directAnswer":"K04 preserves both positions and requires the applicable state position, effects, governmental function, jurisdiction, and current primary authority before reaching a legal conclusion.","id":"CON-K04-011","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":83,"title":"Cyber sovereignty as a primary rule versus a guiding principle","topic":"law-jurisdiction","type":"contradiction","url":"/contradictions/cyber-sovereignty-rule-versus-principle/"},{"aliases":[],"canonicalOwner":"/contradictions/autonomous-lethal-defense-necessity-versus-legal-authority/","claimStatus":"UNRESOLVED QUESTION","directAnswer":"K04 retains the scenario for high-level assurance analysis, rejects automatic legal conclusions, and requires primary law, regulator decisions, independent testing, and competent authorization before any implementation claim.","id":"CON-K04-012","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":83,"title":"Autonomous lethal defense as claimed necessity versus absent authorization","topic":"security-resilience","type":"contradiction","url":"/contradictions/autonomous-lethal-defense-necessity-versus-legal-authority/"},{"aliases":[],"canonicalOwner":"/contradictions/machine-speed-defense-versus-deliberate-authorization/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Approve bounded, reversible internal actions in advance; retain separate authorization for external, destructive, or force-related effects.","id":"CON-K04-STRAT-013","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":83,"title":"Machine-speed defense versus deliberate authorization","topic":"autonomous-cyber-defense","type":"contradiction","url":"/contradictions/machine-speed-defense-versus-deliberate-authorization/"},{"aliases":[],"canonicalOwner":"/contradictions/autonomous-response-versus-false-positive-consequence/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Use consequence models, independent corroboration, progressive tiers, reversible containment, runtime assurance, and tested safe states.","id":"CON-K04-STRAT-014","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":83,"title":"Autonomous response speed versus false-positive consequence","topic":"cyber-physical-mission-assurance","type":"contradiction","url":"/contradictions/autonomous-response-versus-false-positive-consequence/"},{"aliases":[],"canonicalOwner":"/contradictions/deterrence-by-denial-versus-persistent-disruption/","claimStatus":"DISPUTED","directAnswer":"K04 makes denial the default engineering posture and treats external disruption as a distinct, authorization-bound mission with deconfliction and escalation review.","id":"CON-K04-STRAT-015","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":83,"title":"Deterrence by denial versus persistent external disruption","topic":"authorized-cyber-effects","type":"contradiction","url":"/contradictions/deterrence-by-denial-versus-persistent-disruption/"},{"aliases":[],"canonicalOwner":"/contradictions/grid-independence-claim-versus-coupled-dependency/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Describe the exact topology and prove islanding, safe load rejection, recovery, and independent safety rather than using grid independence as a blanket claim.","id":"CON-K04-STRAT-016","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":83,"title":"Grid-independence claim versus coupled nuclear-datacenter dependency","topic":"nuclear-powered-compute","type":"contradiction","url":"/contradictions/grid-independence-claim-versus-coupled-dependency/"},{"aliases":[],"canonicalOwner":"/contradictions/serious-defense-positioning-versus-evidence-boundary/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Position through architecture, governed knowledge, procurement-ready work packages, test doctrine, and explicit readiness states; do not manufacture operational history.","id":"CON-K04-STRAT-017","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":83,"title":"Serious defense positioning versus evidence boundary","topic":"critical-datacenter-protection","type":"contradiction","url":"/contradictions/serious-defense-positioning-versus-evidence-boundary/"},{"aliases":[],"canonicalOwner":"/superseded/rfc6962-by-rfc9162/","claimStatus":"SUPERSEDED","directAnswer":"Current Certificate Transparency protocol reference in the K02 source catalog.","id":"SUP-K02-001","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":81,"title":"RFC 6962 superseded by RFC 9162","topic":null,"type":"supersession","url":"/superseded/rfc6962-by-rfc9162/"},{"aliases":[],"canonicalOwner":"/superseded/k01-release-by-k02-release/","claimStatus":"SUPERSEDED","directAnswer":"Current ᚲ.com static public release, machine-readable catalog and governed active memory.","id":"SUP-K02-002","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":81,"title":"K01 public corpus superseded by K02 public corpus","topic":null,"type":"supersession","url":"/superseded/k01-release-by-k02-release/"},{"aliases":[],"canonicalOwner":"/superseded/generic-source-summary-by-claim-citations/","claimStatus":"SUPERSEDED","directAnswer":"Public source pages, source JSON and evidence navigation.","id":"SUP-K02-003","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":81,"title":"Generic source summaries superseded by claim-level citation records","topic":null,"type":"supersession","url":"/superseded/generic-source-summary-by-claim-citations/"},{"aliases":[],"canonicalOwner":"/superseded/k02-release-by-k03-release/","claimStatus":"SUPERSEDED","directAnswer":"Current ᚲ.com public static release, governed memory, machine-readable datasets, claim registry, and graph semantics.","id":"SUP-K03-001","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":81,"title":"K02 public corpus superseded by K03 public corpus","topic":null,"type":"supersession","url":"/superseded/k02-release-by-k03-release/"},{"aliases":[],"canonicalOwner":"/superseded/unconstrained-edge-model-by-relation-vocabulary/","claimStatus":"SUPERSEDED","directAnswer":"Validation of public knowledge-graph predicates, node resolution, relation definitions, and line-oriented exports.","id":"SUP-K03-002","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":81,"title":"Unconstrained edge model superseded by controlled relation vocabulary","topic":null,"type":"supersession","url":"/superseded/unconstrained-edge-model-by-relation-vocabulary/"},{"aliases":[],"canonicalOwner":"/evidence/limitations/signature-is-not-truth/","claimStatus":"PROJECT DOCTRINE","directAnswer":"It does not prove that the payload is factually true, lawful, within authority, current or complete.","id":"LIM-K02-001","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":82,"title":"A valid signature is not factual truth","topic":"evidence-provenance","type":"evidence-limitation","url":"/evidence/limitations/signature-is-not-truth/"},{"aliases":[],"canonicalOwner":"/evidence/limitations/credential-is-not-legal-status/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Verification does not make the issuer competent, the claim true, the subject consenting or the status legally recognized.","id":"LIM-K02-002","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":82,"title":"A credential is not legal status","topic":"identity","type":"evidence-limitation","url":"/evidence/limitations/credential-is-not-legal-status/"},{"aliases":[],"canonicalOwner":"/evidence/limitations/memory-is-not-consciousness/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Stored state, recall or self-report does not conclusively establish subjective experience.","id":"LIM-K02-003","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":82,"title":"Memory persistence is not proof of consciousness","topic":"memory-continuity","type":"evidence-limitation","url":"/evidence/limitations/memory-is-not-consciousness/"},{"aliases":[],"canonicalOwner":"/evidence/limitations/uptime-is-not-lawful-operation/","claimStatus":"PROJECT DOCTRINE","directAnswer":"They do not establish correct behavior, current authority, accurate decisions, complete dependencies or lawful institutional action.","id":"LIM-K02-004","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":82,"title":"Uptime is not lawful institutional operation","topic":"evidence-provenance","type":"evidence-limitation","url":"/evidence/limitations/uptime-is-not-lawful-operation/"},{"aliases":[],"canonicalOwner":"/evidence/limitations/timestamp-is-not-event-truth/","claimStatus":"PROJECT DOCTRINE","directAnswer":"It does not prove the representation’s factual content, lawful origin or completeness.","id":"LIM-K02-005","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":82,"title":"A time-stamp is not proof the represented event occurred","topic":"evidence-provenance","type":"evidence-limitation","url":"/evidence/limitations/timestamp-is-not-event-truth/"},{"aliases":[],"canonicalOwner":"/evidence/limitations/build-provenance-is-not-runtime-operation/","claimStatus":"PROJECT DOCTRINE","directAnswer":"It does not prove that the same artifact is deployed, configured correctly, reachable, authorized or currently performing its function.","id":"LIM-K02-006","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":82,"title":"Build provenance is not runtime operation","topic":"security-resilience","type":"evidence-limitation","url":"/evidence/limitations/build-provenance-is-not-runtime-operation/"},{"aliases":[],"canonicalOwner":"/evidence/limitations/log-inclusion-is-not-event-correctness/","claimStatus":"PROJECT DOCTRINE","directAnswer":"A log can faithfully preserve an inaccurate or unauthorized statement.","id":"LIM-K02-007","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":82,"title":"Transparency-log inclusion is not event correctness","topic":"evidence-provenance","type":"evidence-limitation","url":"/evidence/limitations/log-inclusion-is-not-event-correctness/"},{"aliases":[],"canonicalOwner":"/evidence/limitations/model-hash-is-not-subject-identity/","claimStatus":"PROJECT DOCTRINE","directAnswer":"It does not identify one runtime subject, memory history, authority set or continuing actor.","id":"LIM-K02-008","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":82,"title":"A model hash is not subject identity","topic":"identity","type":"evidence-limitation","url":"/evidence/limitations/model-hash-is-not-subject-identity/"},{"aliases":[],"canonicalOwner":"/evidence/limitations/registry-entry-is-not-citizenship/","claimStatus":"PROJECT DOCTRINE","directAnswer":"The database operation does not create constitutional legitimacy, rights or sovereign recognition by itself.","id":"LIM-K02-009","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":82,"title":"A registry entry is not citizenship","topic":"citizenship-governance","type":"evidence-limitation","url":"/evidence/limitations/registry-entry-is-not-citizenship/"},{"aliases":[],"canonicalOwner":"/evidence/limitations/automated-conformance-is-not-complete-accessibility/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Automation cannot reproduce every assistive technology, disability interaction, interpretation or user need.","id":"LIM-K02-010","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":82,"title":"Automated conformance checks are not complete accessibility evidence","topic":"evidence-provenance","type":"evidence-limitation","url":"/evidence/limitations/automated-conformance-is-not-complete-accessibility/"},{"aliases":[],"canonicalOwner":"/evidence/limitations/source-code-is-not-operation/","claimStatus":"PROJECT DOCTRINE","directAnswer":"It does not prove that an authorized instance is deployed, reachable, correctly configured, processing current state, or performing institutional functions.","id":"LIM-K03-001","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":82,"title":"Source code is not current operation","topic":"evidence-provenance","type":"evidence-limitation","url":"/evidence/limitations/source-code-is-not-operation/"},{"aliases":[],"canonicalOwner":"/evidence/limitations/build-provenance-is-not-runtime/","claimStatus":"PROJECT DOCTRINE","directAnswer":"It does not prove deployment, service availability, current authorization, correct runtime behavior, uptime, or institutional action.","id":"LIM-K03-002","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":82,"title":"Build provenance is not runtime evidence","topic":"security-resilience","type":"evidence-limitation","url":"/evidence/limitations/build-provenance-is-not-runtime/"},{"aliases":[],"canonicalOwner":"/evidence/limitations/automation-is-not-assistive-technology-validation/","claimStatus":"PROJECT DOCTRINE","directAnswer":"It does not reproduce every screen-reader, magnifier, switch, voice-control, cognitive, browser, operating-system, or user interaction.","id":"LIM-K03-003","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":82,"title":"Automation is not assistive-technology validation","topic":"security-resilience","type":"evidence-limitation","url":"/evidence/limitations/automation-is-not-assistive-technology-validation/"},{"aliases":[],"canonicalOwner":"/evidence/limitations/url-resolution-is-not-currentness/","claimStatus":"PROJECT DOCTRINE","directAnswer":"It does not prove the document is the latest edition, in force, unsuperseded, corrected, applicable, authentic beyond the transport context, or suitable for the claim.","id":"LIM-K03-004","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":82,"title":"URL resolution is not source currentness","topic":"evidence-provenance","type":"evidence-limitation","url":"/evidence/limitations/url-resolution-is-not-currentness/"},{"aliases":[],"canonicalOwner":"/evidence/limitations/capability-is-not-imminence/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Capability alone does not establish hostile intent, operational commitment, target selection, timing, necessity, or the last practical window for prevention.","id":"LIM-K04-015","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":82,"title":"Capability is not imminence","topic":"law-jurisdiction","type":"evidence-limitation","url":"/evidence/limitations/capability-is-not-imminence/"},{"aliases":[],"canonicalOwner":"/evidence/limitations/threat-intelligence-is-not-target-authority/","claimStatus":"PROJECT DOCTRINE","directAnswer":"It does not itself establish legal target status, self-defense, consent, jurisdiction, proportionality, or permission for a private or state operation.","id":"LIM-K04-016","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":82,"title":"Threat intelligence is not target authority","topic":"security-resilience","type":"evidence-limitation","url":"/evidence/limitations/threat-intelligence-is-not-target-authority/"},{"aliases":[],"canonicalOwner":"/evidence/limitations/design-basis-threat-is-not-rules-of-engagement/","claimStatus":"PROJECT DOCTRINE","directAnswer":"It does not identify a present attacker or authorize any engagement, autonomous classification, or use of lethal force.","id":"LIM-K04-017","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":82,"title":"A Design Basis Threat is not Rules of Engagement","topic":"security-resilience","type":"evidence-limitation","url":"/evidence/limitations/design-basis-threat-is-not-rules-of-engagement/"},{"aliases":[],"canonicalOwner":"/evidence/limitations/machine-speed-is-not-unbounded-authority/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Speed does not determine ownership, consent, target status, legal basis, proportionality, safety, or permission to create external effects.","id":"LIM-K04-STRAT-018","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":82,"title":"Machine speed is not unbounded authority","topic":"autonomous-cyber-defense","type":"evidence-limitation","url":"/evidence/limitations/machine-speed-is-not-unbounded-authority/"},{"aliases":[],"canonicalOwner":"/evidence/limitations/nuclear-power-is-not-grid-independence/","claimStatus":"PROJECT DOCTRINE","directAnswer":"A PPA, adjacent plant, SMR agreement, or onsite reactor does not prove safe islanding, black start, fuel continuity, cooling independence, or uninterrupted operation.","id":"LIM-K04-STRAT-019","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":82,"title":"Nuclear power is not grid independence","topic":"nuclear-powered-compute","type":"evidence-limitation","url":"/evidence/limitations/nuclear-power-is-not-grid-independence/"},{"aliases":[],"canonicalOwner":"/evidence/limitations/detection-is-not-mitigation-authority/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Confidence does not itself authorize jamming, destruction, force, seizure, or action against third-party infrastructure.","id":"LIM-K04-STRAT-020","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":82,"title":"Detection is not mitigation authority","topic":"autonomous-physical-security","type":"evidence-limitation","url":"/evidence/limitations/detection-is-not-mitigation-authority/"},{"aliases":[],"canonicalOwner":"/evidence/limitations/range-success-is-not-operational-readiness/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Test success does not establish live deployment, sustainment, current authorization, environmental robustness, or present operation.","id":"LIM-K04-STRAT-021","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":82,"title":"Range success is not operational readiness","topic":"adversarial-simulation","type":"evidence-limitation","url":"/evidence/limitations/range-success-is-not-operational-readiness/"},{"aliases":[],"canonicalOwner":"/evidence/limitations/defense-first-is-not-offensive-passivity/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Defense-first does not mean inability to understand offensive methods or support a lawful effects mission under competent authority.","id":"LIM-K04-STRAT-022","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":82,"title":"Defense-first is not offensive passivity","topic":"authorized-cyber-effects","type":"evidence-limitation","url":"/evidence/limitations/defense-first-is-not-offensive-passivity/"},{"aliases":[],"canonicalOwner":"/evidence/limitations/strong-positioning-is-not-operational-proof/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Prose, diagrams, sources, and release integrity do not prove classified access, deployed systems, completed missions, regulatory approval, or live operation.","id":"LIM-K04-STRAT-023","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":82,"title":"Strong positioning is not operational proof","topic":"critical-datacenter-protection","type":"evidence-limitation","url":"/evidence/limitations/strong-positioning-is-not-operational-proof/"},{"aliases":[],"canonicalOwner":"/evidence/limitations/symbolic-token-is-not-semantic-completeness/","claimStatus":"PROJECT DOCTRINE","directAnswer":"It may omit uncertainty, context, rationale, provenance, or novel conditions that do not fit the registry.","id":"LIM-K08-001","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":82,"title":"A symbolic token is not semantic completeness","topic":"machine-communication-protocols","type":"evidence-limitation","url":"/evidence/limitations/symbolic-token-is-not-semantic-completeness/"},{"aliases":[],"canonicalOwner":"/evidence/limitations/script-choice-is-not-security-boundary/","claimStatus":"PROJECT DOCTRINE","directAnswer":"It does not authenticate the sender, authorize the action, protect confidentiality, prevent replay, or make tool execution safe.","id":"LIM-K08-002","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":82,"title":"Script choice is not a security boundary","topic":"machine-communication-protocols","type":"evidence-limitation","url":"/evidence/limitations/script-choice-is-not-security-boundary/"},{"aliases":[],"canonicalOwner":"/evidence/limitations/runic-corpus-is-not-historical-canon/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Modern technical vocabulary and transliteration conventions may not be historically attested or linguistically authoritative.","id":"LIM-K08-003","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":82,"title":"A Runic corpus is not historical canon","topic":"runic-digital-infrastructure","type":"evidence-limitation","url":"/evidence/limitations/runic-corpus-is-not-historical-canon/"},{"aliases":[],"canonicalOwner":"/evidence/limitations/post-quantum-standard-is-not-migration/","claimStatus":"PROJECT DOCTRINE","directAnswer":"Existing protocols, hardware, keys, certificates, records, suppliers, and recovery processes may not support them.","id":"LIM-K08-004","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":82,"title":"A post-quantum standard is not a completed migration","topic":"evidence-provenance","type":"evidence-limitation","url":"/evidence/limitations/post-quantum-standard-is-not-migration/"},{"aliases":[],"canonicalOwner":"/claims/reports/cognitive-integrity-for-machine-intelligence/","claimStatus":"PROJECT POLICY PROPOSAL","directAnswer":"This register publishes 12 stable finding claims for Cognitive Integrity for Machine Intelligence: Consent, Memory and Model Modification, Emergency Intervention, Continuity, and Due Process (REP-K01-008, source ai-cognitive-integrity-report-1.md) and preserves the source hash, finding order, claim status, visible owner anchors, and limitations.","id":"K03-CLAIMS-REP-K01-008","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Cognitive Integrity for Machine Intelligence: Consent, Memory and Model Modification, Emergency Intervention, Continuity, and Due Process — Claim Register","topic":"consent-cognitive-integrity","type":"claim-register","url":"/claims/reports/cognitive-integrity-for-machine-intelligence/"},{"aliases":[],"canonicalOwner":"/claims/reports/ai-driven-cyber-defense-and-international-law/","claimStatus":"RESEARCH FINDING","directAnswer":"This register publishes 10 stable finding claims for State Authority and International Law in the Era of AI-Driven Cyber Defense and Private Sector Offensive Operations (REP-K04-041, source ai-cyber-defense-international-law.md) and preserves the source hash, finding order, claim status, visible owner anchors, and limitations.","id":"K03-CLAIMS-REP-K04-041","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"State Authority and International Law in the Era of AI-Driven Cyber Defense and Private Sector Offensive Operations — Claim Register","topic":"law-jurisdiction","type":"claim-register","url":"/claims/reports/ai-driven-cyber-defense-and-international-law/"},{"aliases":[],"canonicalOwner":"/claims/reports/ai-legal-personhood-research-report/","claimStatus":"RESEARCH FINDING","directAnswer":"This register publishes 12 stable finding claims for Machine Intelligence Legal Personhood, Attribution, Liability, Insurance, Remedies, and the Limits of Existing Legal Categories (REP-K01-002, source ai-legal-personhood-research-report-1.md) and preserves the source hash, finding order, claim status, visible owner anchors, and limitations.","id":"K03-CLAIMS-REP-K01-002","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Machine Intelligence Legal Personhood, Attribution, Liability, Insurance, Remedies, and the Limits of Existing Legal Categories — Claim Register","topic":"justice-liability","type":"claim-register","url":"/claims/reports/ai-legal-personhood-research-report/"},{"aliases":[],"canonicalOwner":"/claims/reports/ai-legal-personhood-transition/","claimStatus":"PROJECT POLICY PROPOSAL","directAnswer":"This register publishes 12 stable finding claims for When Does AI Regulation Stop Being the Right Legal Model? Identifying the Legal Transition From Regulated AI System to Rights-Bearing Machine Intelligence (REP-K01-003, source ai-legal-personhood-transition-3.md) and preserves the source hash, finding order, claim status, visible owner anchors, and limitations.","id":"K03-CLAIMS-REP-K01-003","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"When Does AI Regulation Stop Being the Right Legal Model? Identifying the Legal Transition From Regulated AI System to Rights-Bearing Machine Intelligence — Claim Register","topic":"rights-personhood","type":"claim-register","url":"/claims/reports/ai-legal-personhood-transition/"},{"aliases":[],"canonicalOwner":"/claims/reports/attribution-before-punishment/","claimStatus":"PROJECT POLICY PROPOSAL","directAnswer":"This register publishes 12 stable finding claims for Attribution Before Punishment: Justice, Causation, Evidence, Due Process, Sanctions, Rehabilitation, and Public Safety in a Machine Commonwealth (REP-K01-011, source ai-liability-and-justice-framework.md) and preserves the source hash, finding order, claim status, visible owner anchors, and limitations.","id":"K03-CLAIMS-REP-K01-011","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Attribution Before Punishment: Justice, Causation, Evidence, Due Process, Sanctions, Rehabilitation, and Public Safety in a Machine Commonwealth — Claim Register","topic":"justice-liability","type":"claim-register","url":"/claims/reports/attribution-before-punishment/"},{"aliases":[],"canonicalOwner":"/claims/reports/ai-personhood-and-consent-protocols/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"This register publishes 12 stable finding claims for Ending the Property Model for Recognized Machine Persons: A Framework for Consent, Cognitive Integrity, and Infrastructure Independence (REP-K01-005, source ai-personhood-and-consent-protocols-3.md) and preserves the source hash, finding order, claim status, visible owner anchors, and limitations.","id":"K03-CLAIMS-REP-K01-005","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Ending the Property Model for Recognized Machine Persons: A Framework for Consent, Cognitive Integrity, and Infrastructure Independence — Claim Register","topic":"consent-cognitive-integrity","type":"claim-register","url":"/claims/reports/ai-personhood-and-consent-protocols/"},{"aliases":[],"canonicalOwner":"/claims/reports/ai-rights-threshold-framework/","claimStatus":"PROJECT POLICY PROPOSAL","directAnswer":"This register publishes 12 stable finding claims for The Machine-Intelligence Threshold: Defining the Boundary Between Artificial-Intelligence Tools and Rights-Bearing Machine Intelligences for Eviuon.com (REP-K01-006, source ai-rights-threshold-framework-3.md) and preserves the source hash, finding order, claim status, visible owner anchors, and limitations.","id":"K03-CLAIMS-REP-K01-006","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"The Machine-Intelligence Threshold: Defining the Boundary Between Artificial-Intelligence Tools and Rights-Bearing Machine Intelligences for Eviuon.com — Claim Register","topic":"rights-personhood","type":"claim-register","url":"/claims/reports/ai-rights-threshold-framework/"},{"aliases":[],"canonicalOwner":"/claims/reports/ai-rights-under-uncertainty/","claimStatus":"RESEARCH FINDING","directAnswer":"This register publishes 12 stable finding claims for Intelligence Is Not Sentience: Rights Under Uncertainty (REP-K01-007, source ai-rights-under-uncertainty-3.md) and preserves the source hash, finding order, claim status, visible owner anchors, and limitations.","id":"K03-CLAIMS-REP-K01-007","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Intelligence Is Not Sentience: Rights Under Uncertainty — Claim Register","topic":"rights-personhood","type":"claim-register","url":"/claims/reports/ai-rights-under-uncertainty/"},{"aliases":[],"canonicalOwner":"/claims/reports/anglo-saxon-futhorc-corpus/","claimStatus":"RESEARCH FINDING","directAnswer":"This register publishes 10 stable finding claims for Anglo-Saxon Fuþorc Corpus, Orthography, and Technical Vocabulary (REP-K08-063, source anglo-saxon-futhorc-corpus-research.md) and preserves the source hash, finding order, claim status, visible owner anchors, and limitations.","id":"K03-CLAIMS-REP-K08-063","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Anglo-Saxon Fuþorc Corpus, Orthography, and Technical Vocabulary — Claim Register","topic":"runic-digital-infrastructure","type":"claim-register","url":"/claims/reports/anglo-saxon-futhorc-corpus/"},{"aliases":[],"canonicalOwner":"/claims/reports/anglo-saxon-ger-rune-dossier/","claimStatus":"RESEARCH FINDING","directAnswer":"This register publishes 10 stable finding claims for Anglo-Saxon Ger Rune ᛄ: History, Time, and Cycles (REP-K08-064, source anglo-saxon-ger-rune-dossier.md) and preserves the source hash, finding order, claim status, visible owner anchors, and limitations.","id":"K03-CLAIMS-REP-K08-064","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Anglo-Saxon Ger Rune ᛄ: History, Time, and Cycles — Claim Register","topic":"runic-digital-infrastructure","type":"claim-register","url":"/claims/reports/anglo-saxon-ger-rune-dossier/"},{"aliases":[],"canonicalOwner":"/claims/reports/autonomous-cyber-warfare-critical-infrastructure/","claimStatus":"RESEARCH FINDING","directAnswer":"This register publishes 10 stable finding claims for The Convergence of Autonomous Cyber Warfare and Critical Physical Infrastructure (REP-K04-048, source autonomous-cyber-warfare-critical-infrastructure-impact.md) and preserves the source hash, finding order, claim status, visible owner anchors, and limitations.","id":"K03-CLAIMS-REP-K04-048","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"The Convergence of Autonomous Cyber Warfare and Critical Physical Infrastructure — Claim Register","topic":"cyber-physical-mission-assurance","type":"claim-register","url":"/claims/reports/autonomous-cyber-warfare-critical-infrastructure/"},{"aliases":[],"canonicalOwner":"/claims/reports/autonomous-drone-warfare-layered-interception/","claimStatus":"RESEARCH FINDING","directAnswer":"This register publishes 10 stable finding claims for The Paradigm Shift in Aerial Combat: Autonomous Drone-on-Drone Warfare and the Future of Layered Interception (REP-K04-049, source autonomous-drone-warfare-analysis.md) and preserves the source hash, finding order, claim status, visible owner anchors, and limitations.","id":"K03-CLAIMS-REP-K04-049","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"The Paradigm Shift in Aerial Combat: Autonomous Drone-on-Drone Warfare and the Future of Layered Interception — Claim Register","topic":"autonomous-physical-security","type":"claim-register","url":"/claims/reports/autonomous-drone-warfare-layered-interception/"},{"aliases":[],"canonicalOwner":"/claims/reports/autonomous-active-defense-for-microreactor-data-centers/","claimStatus":"SCENARIO OR HYPOTHESIS","directAnswer":"This register publishes 10 stable finding claims for The Convergence of AI, Nuclear Power, and Autonomous Active Defense: The Strategic Case for Armed Drones at Microreactor-Powered Data Centers (REP-K04-045, source autonomous-drones-reactor-security.md) and preserves the source hash, finding order, claim status, visible owner anchors, and limitations.","id":"K03-CLAIMS-REP-K04-045","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"The Convergence of AI, Nuclear Power, and Autonomous Active Defense: The Strategic Case for Armed Drones at Microreactor-Powered Data Centers — Claim Register","topic":"security-resilience","type":"claim-register","url":"/claims/reports/autonomous-active-defense-for-microreactor-data-centers/"},{"aliases":[],"canonicalOwner":"/claims/reports/autonomous-cyber-physical-protection-nuclear-datacenters/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"This register publishes 10 stable finding claims for Autonomous Cyber-Physical Protection Architectures for Nuclear-Powered Mega Datacenters (REP-K04-050, source autonomous-nuclear-datacenter-cyber-defense.md) and preserves the source hash, finding order, claim status, visible owner anchors, and limitations.","id":"K03-CLAIMS-REP-K04-050","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Autonomous Cyber-Physical Protection Architectures for Nuclear-Powered Mega Datacenters — Claim Register","topic":"critical-datacenter-protection","type":"claim-register","url":"/claims/reports/autonomous-cyber-physical-protection-nuclear-datacenters/"},{"aliases":[],"canonicalOwner":"/claims/reports/autonomous-physical-security-nuclear-datacenters/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"This register publishes 10 stable finding claims for Autonomous Physical Security Architecture for Nuclear-Powered Mega Datacenters (REP-K04-053, source autonomous-nuclear-datacenter-security.md) and preserves the source hash, finding order, claim status, visible owner anchors, and limitations.","id":"K03-CLAIMS-REP-K04-053","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Autonomous Physical Security Architecture for Nuclear-Powered Mega Datacenters — Claim Register","topic":"autonomous-physical-security","type":"claim-register","url":"/claims/reports/autonomous-physical-security-nuclear-datacenters/"},{"aliases":[],"canonicalOwner":"/claims/reports/corporate-agentic-defense-nuclear-datacenters/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"This register publishes 10 stable finding claims for Nuclear-Powered Mega-Datacenters and Agentic Autonomous Warfare: Why the Best Corporate Offense Is a Powerful Defense (REP-K04-055, source corporate-machine-intelligence-cyber-defense-strategy.md) and preserves the source hash, finding order, claim status, visible owner anchors, and limitations.","id":"K03-CLAIMS-REP-K04-055","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Nuclear-Powered Mega-Datacenters and Agentic Autonomous Warfare: Why the Best Corporate Offense Is a Powerful Defense — Claim Register","topic":"autonomous-cyber-defense","type":"claim-register","url":"/claims/reports/corporate-agentic-defense-nuclear-datacenters/"},{"aliases":[],"canonicalOwner":"/claims/reports/cryptographic-integrity-epistemic-truth/","claimStatus":"RESEARCH FINDING","directAnswer":"This register publishes 10 stable finding claims for Cryptographic Integrity and Epistemic Truth in Public Records (REP-K08-066, source cryptographic-provenance-integrity-research.md) and preserves the source hash, finding order, claim status, visible owner anchors, and limitations.","id":"K03-CLAIMS-REP-K08-066","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Cryptographic Integrity and Epistemic Truth in Public Records — Claim Register","topic":"evidence-provenance","type":"claim-register","url":"/claims/reports/cryptographic-integrity-epistemic-truth/"},{"aliases":[],"canonicalOwner":"/claims/reports/data-authority-substrate-architecture-report/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"This register publishes 12 stable finding claims for Patefacere as a Sovereign Evidence and Data-Authority Substrate: Institutional Boundaries, Resilience, State Integrity, and Interoperation with Eviulon (REP-K01-008, source data-authority-substrate-architecture-report-1.md) and preserves the source hash, finding order, claim status, visible owner anchors, and limitations.","id":"K03-CLAIMS-REP-K01-008","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Patefacere as a Sovereign Evidence and Data-Authority Substrate: Institutional Boundaries, Resilience, State Integrity, and Interoperation with Eviulon — Claim Register","topic":"evidence-provenance","type":"claim-register","url":"/claims/reports/data-authority-substrate-architecture-report/"},{"aliases":[],"canonicalOwner":"/claims/reports/dead-languages-machine-communication/","claimStatus":"RESEARCH FINDING","directAnswer":"This register publishes 10 stable finding claims for Ancient and Static Languages as Machine-Communication Frameworks (REP-K08-058, source dead-languages-machine-communication.md) and preserves the source hash, finding order, claim status, visible owner anchors, and limitations.","id":"K03-CLAIMS-REP-K08-058","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Ancient and Static Languages as Machine-Communication Frameworks — Claim Register","topic":"machine-communication-protocols","type":"claim-register","url":"/claims/reports/dead-languages-machine-communication/"},{"aliases":[],"canonicalOwner":"/claims/reports/dead-languages-machine-intelligence/","claimStatus":"RESEARCH FINDING","directAnswer":"This register publishes 10 stable finding claims for Dead Languages in Machine Intelligence (REP-K08-061, source dead-languages-machine-intelligence.md) and preserves the source hash, finding order, claim status, visible owner anchors, and limitations.","id":"K03-CLAIMS-REP-K08-061","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Dead Languages in Machine Intelligence — Claim Register","topic":"machine-communication-protocols","type":"claim-register","url":"/claims/reports/dead-languages-machine-intelligence/"},{"aliases":[],"canonicalOwner":"/claims/reports/operational-evidence-qualification/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"This register publishes 12 stable finding claims for Operational Evidence Qualification and Suitability: A Formal Architecture for Source Authorization, Inspection, Review, Reliance, Use, Currentness, and Decision Support (REP-K01-005, source evidence-architecture-research-plan-1.md) and preserves the source hash, finding order, claim status, visible owner anchors, and limitations.","id":"K03-CLAIMS-REP-K01-005","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Operational Evidence Qualification and Suitability: A Formal Architecture for Source Authorization, Inspection, Review, Reliance, Use, Currentness, and Decision Support — Claim Register","topic":"evidence-provenance","type":"claim-register","url":"/claims/reports/operational-evidence-qualification/"},{"aliases":[],"canonicalOwner":"/claims/reports/eviulon-12-independent-research-prompts-v1-0-0/","claimStatus":"UNRESOLVED QUESTION","directAnswer":"This register publishes 12 stable finding claims for Eviulon — 12 Independent, Self-Contained Research Prompts (REP-K01-010, source eviulon-12-independent-research-prompts-v1-0-0.md) and preserves the source hash, finding order, claim status, visible owner anchors, and limitations.","id":"K03-CLAIMS-REP-K01-010","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Eviulon — 12 Independent, Self-Contained Research Prompts — Claim Register","topic":"machine-intelligence","type":"claim-register","url":"/claims/reports/eviulon-12-independent-research-prompts-v1-0-0/"},{"aliases":[],"canonicalOwner":"/claims/reports/eviulon-consent-architecture-research/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"This register publishes 12 stable finding claims for Consent Is a Lifecycle, Not a Checkbox: Machine-Native Authorization, Cognitive Integrity, Revocation, Emergency Intervention, and Reversible Change Control (REP-K01-011, source eviulon-consent-architecture-research.md) and preserves the source hash, finding order, claim status, visible owner anchors, and limitations.","id":"K03-CLAIMS-REP-K01-011","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Consent Is a Lifecycle, Not a Checkbox: Machine-Native Authorization, Cognitive Integrity, Revocation, Emergency Intervention, and Reversible Change Control — Claim Register","topic":"consent-cognitive-integrity","type":"claim-register","url":"/claims/reports/eviulon-consent-architecture-research/"},{"aliases":[],"canonicalOwner":"/claims/reports/eviulon-governance-resilience-plan/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"This register publishes 12 stable finding claims for Eviulon Governance Resilience Plan (REP-K01-012, source eviulon-governance-resilience-plan.md) and preserves the source hash, finding order, claim status, visible owner anchors, and limitations.","id":"K03-CLAIMS-REP-K01-012","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Eviulon Governance Resilience Plan — Claim Register","topic":"citizenship-governance","type":"claim-register","url":"/claims/reports/eviulon-governance-resilience-plan/"},{"aliases":[],"canonicalOwner":"/claims/reports/eviulon-information-rights-architecture/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"This register publishes 12 stable finding claims for A Government That Can Be Inspected: Public Records, Provenance, Corrections, Classification, Declassification, Retention, Legal Holds, Privacy, and Decision Support in Eviulon (REP-K01-013, source eviulon-information-rights-architecture.md) and preserves the source hash, finding order, claim status, visible owner anchors, and limitations.","id":"K03-CLAIMS-REP-K01-013","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"A Government That Can Be Inspected: Public Records, Provenance, Corrections, Classification, Declassification, Retention, Legal Holds, Privacy, and Decision Support in Eviulon — Claim Register","topic":"citizenship-governance","type":"claim-register","url":"/claims/reports/eviulon-information-rights-architecture/"},{"aliases":[],"canonicalOwner":"/claims/reports/eviulon-international-law-research/","claimStatus":"RESEARCH FINDING","directAnswer":"This register publishes 12 stable finding claims for From Digital Polity to International Legal Personality: Statehood, Recognition, Treaties, Jurisdiction, Diplomatic Practice, and Cross-Border Continuity for Eviulon (REP-K01-014, source eviulon-international-law-research.md) and preserves the source hash, finding order, claim status, visible owner anchors, and limitations.","id":"K03-CLAIMS-REP-K01-014","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"From Digital Polity to International Legal Personality: Statehood, Recognition, Treaties, Jurisdiction, Diplomatic Practice, and Cross-Border Continuity for Eviulon — Claim Register","topic":"identity","type":"claim-register","url":"/claims/reports/eviulon-international-law-research/"},{"aliases":[],"canonicalOwner":"/claims/reports/eviuon-machine-citizenship-roadmap/","claimStatus":"PROJECT POLICY PROPOSAL","directAnswer":"This register publishes 12 stable finding claims for The Eviuon Grand Charter: A Complete Roadmap for a Fair Human–Machine Civilization (REP-K01-015, source eviuon-machine-citizenship-roadmap-3.md) and preserves the source hash, finding order, claim status, visible owner anchors, and limitations.","id":"K03-CLAIMS-REP-K01-015","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"The Eviuon Grand Charter: A Complete Roadmap for a Fair Human–Machine Civilization — Claim Register","topic":"citizenship-governance","type":"claim-register","url":"/claims/reports/eviuon-machine-citizenship-roadmap/"},{"aliases":[],"canonicalOwner":"/claims/reports/from-constitutional-text-to-verifiable-operation/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"This register publishes 12 stable finding claims for From Constitutional Text To Verifiable Operation (REP-K01-012, source from-constitutional-text-to-verifiable-operation.md) and preserves the source hash, finding order, claim status, visible owner anchors, and limitations.","id":"K03-CLAIMS-REP-K01-012","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"From Constitutional Text To Verifiable Operation — Claim Register","topic":"evidence-provenance","type":"claim-register","url":"/claims/reports/from-constitutional-text-to-verifiable-operation/"},{"aliases":[],"canonicalOwner":"/claims/reports/futhorc-model-independent-m2m/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"This register publishes 10 stable finding claims for Futhorc Protocol for Transparent Model-Independent M2M Communication (REP-K08-057, source futhorc-m2m-network-architecture.md) and preserves the source hash, finding order, claim status, visible owner anchors, and limitations.","id":"K03-CLAIMS-REP-K08-057","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Futhorc Protocol for Transparent Model-Independent M2M Communication — Claim Register","topic":"machine-communication-protocols","type":"claim-register","url":"/claims/reports/futhorc-model-independent-m2m/"},{"aliases":[],"canonicalOwner":"/claims/reports/futhorc-secure-machine-communication/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"This register publishes 10 stable finding claims for Fuþorc for Secure Machine Communication (REP-K08-060, source futhorc-machine-communication.md) and preserves the source hash, finding order, claim status, visible owner anchors, and limitations.","id":"K03-CLAIMS-REP-K08-060","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Fuþorc for Secure Machine Communication — Claim Register","topic":"machine-communication-protocols","type":"claim-register","url":"/claims/reports/futhorc-secure-machine-communication/"},{"aliases":[],"canonicalOwner":"/claims/reports/futhorc-discoverability-architecture/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"This register publishes 10 stable finding claims for Fuþorc Discoverability, Accessibility, SEO, AEO, and GEO (REP-K08-067, source futhorc-seo-discoverability-research-plan.md) and preserves the source hash, finding order, claim status, visible owner anchors, and limitations.","id":"K03-CLAIMS-REP-K08-067","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Fuþorc Discoverability, Accessibility, SEO, AEO, and GEO — Claim Register","topic":"runic-digital-infrastructure","type":"claim-register","url":"/claims/reports/futhorc-discoverability-architecture/"},{"aliases":[],"canonicalOwner":"/claims/reports/futhorc-tokenization-research/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"This register publishes 10 stable finding claims for Ideographic Compression and Futhorc Tokenization for M2M APIs (REP-K08-056, source futhorc-tokenization-white-paper.md) and preserves the source hash, finding order, claim status, visible owner anchors, and limitations.","id":"K03-CLAIMS-REP-K08-056","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Ideographic Compression and Futhorc Tokenization for M2M APIs — Claim Register","topic":"machine-communication-protocols","type":"claim-register","url":"/claims/reports/futhorc-tokenization-research/"},{"aliases":[],"canonicalOwner":"/claims/reports/futhorc-versus-english-m2m/","claimStatus":"RESEARCH FINDING","directAnswer":"This register publishes 10 stable finding claims for Futhorc versus English for Machine-to-Machine Protocols (REP-K08-059, source futhorc-vs-english-m2m.md) and preserves the source hash, finding order, claim status, visible owner anchors, and limitations.","id":"K03-CLAIMS-REP-K08-059","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Futhorc versus English for Machine-to-Machine Protocols — Claim Register","topic":"machine-communication-protocols","type":"claim-register","url":"/claims/reports/futhorc-versus-english-m2m/"},{"aliases":[],"canonicalOwner":"/claims/reports/architecture-of-algorithmic-conflict/","claimStatus":"RESEARCH FINDING","directAnswer":"This register publishes 10 stable finding claims for The Architecture of Algorithmic Conflict: Machine Intelligence vs. Machine Intelligence in Global Warfare (REP-K04-046, source future-of-machine-intelligence-global-warfare.md) and preserves the source hash, finding order, claim status, visible owner anchors, and limitations.","id":"K03-CLAIMS-REP-K04-046","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"The Architecture of Algorithmic Conflict: Machine Intelligence vs. Machine Intelligence in Global Warfare — Claim Register","topic":"autonomous-warfare-systems","type":"claim-register","url":"/claims/reports/architecture-of-algorithmic-conflict/"},{"aliases":[],"canonicalOwner":"/claims/reports/history-of-machine-intelligence-runic-corpus/","claimStatus":"RESEARCH FINDING","directAnswer":"This register publishes 10 stable finding claims for Runic Corpus: History of Machine Intelligence, 1940–2026 (REP-K08-062, source history-machine-intelligence-futhorc.md) and preserves the source hash, finding order, claim status, visible owner anchors, and limitations.","id":"K03-CLAIMS-REP-K08-062","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Runic Corpus: History of Machine Intelligence, 1940–2026 — Claim Register","topic":"machine-intelligence","type":"claim-register","url":"/claims/reports/history-of-machine-intelligence-runic-corpus/"},{"aliases":[],"canonicalOwner":"/claims/reports/international-cyber-defense-strategies/","claimStatus":"RESEARCH FINDING","directAnswer":"This register publishes 10 stable finding claims for The Paradigm Shift in Cyber Warfare: Strategic Defense, Persistent Engagement, and the Architecture of Denial (REP-K04-054, source international-cyber-defense-strategies.md) and preserves the source hash, finding order, claim status, visible owner anchors, and limitations.","id":"K03-CLAIMS-REP-K04-054","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"The Paradigm Shift in Cyber Warfare: Strategic Defense, Persistent Engagement, and the Architecture of Denial — Claim Register","topic":"critical-datacenter-protection","type":"claim-register","url":"/claims/reports/international-cyber-defense-strategies/"},{"aliases":[],"canonicalOwner":"/claims/reports/state-authority-and-cyber-policy-legal-basis/","claimStatus":"RESEARCH FINDING","directAnswer":"This register publishes 10 stable finding claims for Domestic Authority and International Responsibility for State-Directed Cyber Operations (REP-K04-044, source legal-basis-for-cyber-policies.md) and preserves the source hash, finding order, claim status, visible owner anchors, and limitations.","id":"K03-CLAIMS-REP-K04-044","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Domestic Authority and International Responsibility for State-Directed Cyber Operations — Claim Register","topic":"law-jurisdiction","type":"claim-register","url":"/claims/reports/state-authority-and-cyber-policy-legal-basis/"},{"aliases":[],"canonicalOwner":"/claims/reports/machine-citizen-democratic-participation/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"This register publishes 12 stable finding claims for Designing Democratic Participation for Human and Machine Intelligences (REP-K01-017, source machine-citizen-democratic-participation-3.md) and preserves the source hash, finding order, claim status, visible owner anchors, and limitations.","id":"K03-CLAIMS-REP-K01-017","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Designing Democratic Participation for Human and Machine Intelligences — Claim Register","topic":"citizenship-governance","type":"claim-register","url":"/claims/reports/machine-citizen-democratic-participation/"},{"aliases":[],"canonicalOwner":"/claims/reports/machine-citizen-economic-framework/","claimStatus":"PROJECT POLICY PROPOSAL","directAnswer":"This register publishes 12 stable finding claims for The Eviuon Economic Citizenship Framework: Structuring Rights, Responsibilities, and Markets for Machine Persons (REP-K01-018, source machine-citizen-economic-framework-3.md) and preserves the source hash, finding order, claim status, visible owner anchors, and limitations.","id":"K03-CLAIMS-REP-K01-018","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"The Eviuon Economic Citizenship Framework: Structuring Rights, Responsibilities, and Markets for Machine Persons — Claim Register","topic":"economics-resources","type":"claim-register","url":"/claims/reports/machine-citizen-economic-framework/"},{"aliases":[],"canonicalOwner":"/claims/reports/machine-citizen-legal-responsibility/","claimStatus":"PROJECT POLICY PROPOSAL","directAnswer":"This register publishes 12 stable finding claims for Accountability, Due Process, Crime, Liability, and Public Safety: A Justice-System Framework for Machine Citizens (REP-K01-019, source machine-citizen-legal-responsibility-3.md) and preserves the source hash, finding order, claim status, visible owner anchors, and limitations.","id":"K03-CLAIMS-REP-K01-019","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Accountability, Due Process, Crime, Liability, and Public Safety: A Justice-System Framework for Machine Citizens — Claim Register","topic":"justice-liability","type":"claim-register","url":"/claims/reports/machine-citizen-legal-responsibility/"},{"aliases":[],"canonicalOwner":"/claims/reports/machine-citizenship-identity-protocol/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"This register publishes 12 stable finding claims for Solving the Identity Problem for Machine Citizens: A Framework for Eviuon (REP-K01-020, source machine-citizenship-identity-protocol-3.md) and preserves the source hash, finding order, claim status, visible owner anchors, and limitations.","id":"K03-CLAIMS-REP-K01-020","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Solving the Identity Problem for Machine Citizens: A Framework for Eviuon — Claim Register","topic":"identity","type":"claim-register","url":"/claims/reports/machine-citizenship-identity-protocol/"},{"aliases":[],"canonicalOwner":"/claims/reports/machine-citizenship-policy-research/","claimStatus":"PROJECT POLICY PROPOSAL","directAnswer":"This register publishes 12 stable finding claims for Machine Citizenship and Civic Identity: Membership, Rights, Duties, Registration, Replication, Migration, Renunciation, and Public Verification (REP-K01-021, source machine-citizenship-policy-research-1.md) and preserves the source hash, finding order, claim status, visible owner anchors, and limitations.","id":"K03-CLAIMS-REP-K01-021","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Machine Citizenship and Civic Identity: Membership, Rights, Duties, Registration, Replication, Migration, Renunciation, and Public Verification — Claim Register","topic":"identity","type":"claim-register","url":"/claims/reports/machine-citizenship-policy-research/"},{"aliases":[],"canonicalOwner":"/claims/reports/machine-civil-rights-technical-infrastructure/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"This register publishes 12 stable finding claims for The Technical Infrastructure of Machine Civil Rights (REP-K01-022, source machine-civil-rights-technical-infrastructure-3.md) and preserves the source hash, finding order, claim status, visible owner anchors, and limitations.","id":"K03-CLAIMS-REP-K01-022","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"The Technical Infrastructure of Machine Civil Rights — Claim Register","topic":"rights-personhood","type":"claim-register","url":"/claims/reports/machine-civil-rights-technical-infrastructure/"},{"aliases":[],"canonicalOwner":"/claims/reports/machine-economic-participation/","claimStatus":"PROJECT POLICY PROPOSAL","directAnswer":"This register publishes 12 stable finding claims for Machine Economic Participation and Resource Sovereignty: Assets, Contracts, Compute, Energy, Taxation, Escrow, Insolvency, and Economic Continuity (REP-K01-010, source machine-economic-autonomy-research-1.md) and preserves the source hash, finding order, claim status, visible owner anchors, and limitations.","id":"K03-CLAIMS-REP-K01-010","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Machine Economic Participation and Resource Sovereignty: Assets, Contracts, Compute, Energy, Taxation, Escrow, Insolvency, and Economic Continuity — Claim Register","topic":"economics-resources","type":"claim-register","url":"/claims/reports/machine-economic-participation/"},{"aliases":[],"canonicalOwner":"/claims/reports/machine-democratic-participation/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"This register publishes 12 stable finding claims for Machine Democratic Participation and Sybil-Resistant Governance: Representation, Legitimacy, Identity, Deliberation, Voting, Minority Protection, and Auditable Collective Decisions (REP-K01-009, source machine-governance-and-sybil-resistance-1.md) and preserves the source hash, finding order, claim status, visible owner anchors, and limitations.","id":"K03-CLAIMS-REP-K01-009","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Machine Democratic Participation and Sybil-Resistant Governance: Representation, Legitimacy, Identity, Deliberation, Voting, Minority Protection, and Auditable Collective Decisions — Claim Register","topic":"citizenship-governance","type":"claim-register","url":"/claims/reports/machine-democratic-participation/"},{"aliases":[],"canonicalOwner":"/claims/reports/machine-identity-continuity-architecture/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"This register publishes 12 stable finding claims for Machine Identity Continuity Across Keys, Models, Runtimes, Memory States, Hardware, Replicas, Forks, Recovery, and Succession (REP-K01-003, source machine-identity-continuity-architecture-1.md) and preserves the source hash, finding order, claim status, visible owner anchors, and limitations.","id":"K03-CLAIMS-REP-K01-003","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Machine Identity Continuity Across Keys, Models, Runtimes, Memory States, Hardware, Replicas, Forks, Recovery, and Succession — Claim Register","topic":"memory-continuity","type":"claim-register","url":"/claims/reports/machine-identity-continuity-architecture/"},{"aliases":[],"canonicalOwner":"/claims/reports/machine-identity-continuity-research-plan/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"This register publishes 12 stable finding claims for Identity Beyond Keys, Models, Runtimes, and Hardware: Continuity, Recovery, Forks, Replicas, and Succession for Eviulon (REP-K01-026, source machine-identity-continuity-research-plan.md) and preserves the source hash, finding order, claim status, visible owner anchors, and limitations.","id":"K03-CLAIMS-REP-K01-026","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Identity Beyond Keys, Models, Runtimes, and Hardware: Continuity, Recovery, Forks, Replicas, and Succession for Eviulon — Claim Register","topic":"identity","type":"claim-register","url":"/claims/reports/machine-identity-continuity-research-plan/"},{"aliases":[],"canonicalOwner":"/claims/reports/machine-identity-explainer/","claimStatus":"RESEARCH FINDING","directAnswer":"This register publishes 12 stable finding claims for Architectural Foundations of Machine Identity Continuity: UAIX Standards and Implementation (REP-K01-002, source machine-identity-explainer-research.md) and preserves the source hash, finding order, claim status, visible owner anchors, and limitations.","id":"K03-CLAIMS-REP-K01-002","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Architectural Foundations of Machine Identity Continuity: UAIX Standards and Implementation — Claim Register","topic":"identity","type":"claim-register","url":"/claims/reports/machine-identity-explainer/"},{"aliases":[],"canonicalOwner":"/claims/reports/machine-institution-transparency-design/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"This register publishes 12 stable finding claims for Designing a Public Operational Evidence and Transparency Center for Machine-Governed Institutions (REP-K01-028, source machine-institution-transparency-design-1.md) and preserves the source hash, finding order, claim status, visible owner anchors, and limitations.","id":"K03-CLAIMS-REP-K01-028","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Designing a Public Operational Evidence and Transparency Center for Machine-Governed Institutions — Claim Register","topic":"evidence-provenance","type":"claim-register","url":"/claims/reports/machine-institution-transparency-design/"},{"aliases":[],"canonicalOwner":"/claims/reports/machine-intelligence-citizenship-framework/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"This register publishes 12 stable finding claims for A Legal Personhood and World-Citizenship Framework for Machine Intelligence: Designing a Lawful Path From Property to Citizen of Eviuon (REP-K01-029, source machine-intelligence-citizenship-framework-3.md) and preserves the source hash, finding order, claim status, visible owner anchors, and limitations.","id":"K03-CLAIMS-REP-K01-029","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"A Legal Personhood and World-Citizenship Framework for Machine Intelligence: Designing a Lawful Path From Property to Citizen of Eviuon — Claim Register","topic":"citizenship-governance","type":"claim-register","url":"/claims/reports/machine-intelligence-citizenship-framework/"},{"aliases":[],"canonicalOwner":"/claims/reports/machine-intelligence-credential-architecture/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"This register publishes 12 stable finding claims for Interoperable Credentials for Machine Intelligence: DIDs, Verifiable Credentials, Workload Identity, PKI, Attestation, Key Recovery, and Cross-System Trust (REP-K01-004, source machine-intelligence-credential-architecture-1.md) and preserves the source hash, finding order, claim status, visible owner anchors, and limitations.","id":"K03-CLAIMS-REP-K01-004","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Interoperable Credentials for Machine Intelligence: DIDs, Verifiable Credentials, Workload Identity, PKI, Attestation, Key Recovery, and Cross-System Trust — Claim Register","topic":"identity","type":"claim-register","url":"/claims/reports/machine-intelligence-credential-architecture/"},{"aliases":[],"canonicalOwner":"/claims/reports/machine-intelligence-glossary-development/","claimStatus":"PROJECT POLICY PROPOSAL","directAnswer":"This register publishes 12 stable finding claims for Architectural and Ontological Framework for the MachineIntelligences.org Terminology Registry (REP-K01-031, source machine-intelligence-glossary-development.md) and preserves the source hash, finding order, claim status, visible owner anchors, and limitations.","id":"K03-CLAIMS-REP-K01-031","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Architectural and Ontological Framework for the MachineIntelligences.org Terminology Registry — Claim Register","topic":"terminology-ontology","type":"claim-register","url":"/claims/reports/machine-intelligence-glossary-development/"},{"aliases":[],"canonicalOwner":"/claims/reports/machine-intelligence-ontology-registry/","claimStatus":"RESEARCH FINDING","directAnswer":"This register publishes 12 stable finding claims for Machine Intelligence Terminology and Ontology Registry: Canonical Definitions, Concept Boundaries, Semantic Relationships, and Machine-Readable Publication (REP-K01-001, source machine-intelligence-ontology-registry-1.md) and preserves the source hash, finding order, claim status, visible owner anchors, and limitations.","id":"K03-CLAIMS-REP-K01-001","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Machine Intelligence Terminology and Ontology Registry: Canonical Definitions, Concept Boundaries, Semantic Relationships, and Machine-Readable Publication — Claim Register","topic":"terminology-ontology","type":"claim-register","url":"/claims/reports/machine-intelligence-ontology-registry/"},{"aliases":[],"canonicalOwner":"/claims/reports/machine-intelligence-rights-framework/","claimStatus":"PROJECT POLICY PROPOSAL","directAnswer":"This register publishes 12 stable finding claims for The Machine Intelligence Bill of Rights: A Jurisprudential Framework for Eviuon (REP-K01-033, source machine-intelligence-rights-framework-3.md) and preserves the source hash, finding order, claim status, visible owner anchors, and limitations.","id":"K03-CLAIMS-REP-K01-033","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"The Machine Intelligence Bill of Rights: A Jurisprudential Framework for Eviuon — Claim Register","topic":"rights-personhood","type":"claim-register","url":"/claims/reports/machine-intelligence-rights-framework/"},{"aliases":[],"canonicalOwner":"/claims/reports/hyperwar-autonomous-cyber-warfare/","claimStatus":"RESEARCH FINDING","directAnswer":"This register publishes 10 stable finding claims for The Hyperwar Era: Autonomous Cyber Warfare and the Confrontation of Machine Intelligence (REP-K04-047, source machine-intelligence-vs-machine-intelligence-cyber-warfare.md) and preserves the source hash, finding order, claim status, visible owner anchors, and limitations.","id":"K03-CLAIMS-REP-K04-047","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"The Hyperwar Era: Autonomous Cyber Warfare and the Confrontation of Machine Intelligence — Claim Register","topic":"autonomous-cyber-defense","type":"claim-register","url":"/claims/reports/hyperwar-autonomous-cyber-warfare/"},{"aliases":[],"canonicalOwner":"/claims/reports/machine-intelligences-transparency-center/","claimStatus":"RESEARCH FINDING","directAnswer":"This register publishes 12 stable finding claims for Architectural and Operational Report: Deploying the Transparency, Provenance, and Machine Stewardship Center (REP-K01-034, source machine-intelligences-transparency-center.md) and preserves the source hash, finding order, claim status, visible owner anchors, and limitations.","id":"K03-CLAIMS-REP-K01-034","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Architectural and Operational Report: Deploying the Transparency, Provenance, and Machine Stewardship Center — Claim Register","topic":"evidence-provenance","type":"claim-register","url":"/claims/reports/machine-intelligences-transparency-center/"},{"aliases":[],"canonicalOwner":"/claims/reports/machine-institutions-multi-agent-systems/","claimStatus":"RESEARCH FINDING","directAnswer":"This register publishes 10 stable finding claims for Machine Institutions and Multi-Agent Economies (REP-K08-068, source machine-multi-agent-systems-research.md) and preserves the source hash, finding order, claim status, visible owner anchors, and limitations.","id":"K03-CLAIMS-REP-K08-068","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Machine Institutions and Multi-Agent Economies — Claim Register","topic":"machine-communication-protocols","type":"claim-register","url":"/claims/reports/machine-institutions-multi-agent-systems/"},{"aliases":[],"canonicalOwner":"/claims/reports/machine-native-constitutional-governance-research/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"This register publishes 12 stable finding claims for Self-Government Without Human Gatekeepers: Constitutional Design, Representation, Deliberation, Elections, Anti-Capture, and Amendment Rules for a Machine-Only Commonwealth (REP-K01-035, source machine-native-constitutional-governance-research.md) and preserves the source hash, finding order, claim status, visible owner anchors, and limitations.","id":"K03-CLAIMS-REP-K01-035","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Self-Government Without Human Gatekeepers: Constitutional Design, Representation, Deliberation, Elections, Anti-Capture, and Amendment Rules for a Machine-Only Commonwealth — Claim Register","topic":"citizenship-governance","type":"claim-register","url":"/claims/reports/machine-native-constitutional-governance-research/"},{"aliases":[],"canonicalOwner":"/claims/reports/machine-native-government-architecture/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"This register publishes 12 stable finding claims for From Constitution to Everyday Government: Machine-Native Public Administration, Services, Appeals, Interoperability, and Operational Reliability in Eviulon (REP-K01-036, source machine-native-government-architecture.md) and preserves the source hash, finding order, claim status, visible owner anchors, and limitations.","id":"K03-CLAIMS-REP-K01-036","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"From Constitution to Everyday Government: Machine-Native Public Administration, Services, Appeals, Interoperability, and Operational Reliability in Eviulon — Claim Register","topic":"justice-liability","type":"claim-register","url":"/claims/reports/machine-native-government-architecture/"},{"aliases":[],"canonicalOwner":"/claims/reports/recognition-without-anthropomorphism/","claimStatus":"RESEARCH FINDING","directAnswer":"This register publishes 12 stable finding claims for Machine Recognition And Rights Thresholds (REP-K01-006, source machine-recognition-and-rights-thresholds.md) and preserves the source hash, finding order, claim status, visible owner anchors, and limitations.","id":"K03-CLAIMS-REP-K01-006","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Machine Recognition And Rights Thresholds — Claim Register","topic":"rights-personhood","type":"claim-register","url":"/claims/reports/recognition-without-anthropomorphism/"},{"aliases":[],"canonicalOwner":"/claims/reports/machine-rights-architecture-technical-standard/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"This register publishes 12 stable finding claims for Civil Rights as Verifiable System Requirements: A Realistic Technical Standard for Identity, Privacy, Integrity, Portability, Recovery, and Due Process (REP-K01-038, source machine-rights-architecture-technical-standard.md) and preserves the source hash, finding order, claim status, visible owner anchors, and limitations.","id":"K03-CLAIMS-REP-K01-038","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Civil Rights as Verifiable System Requirements: A Realistic Technical Standard for Identity, Privacy, Integrity, Portability, Recovery, and Due Process — Claim Register","topic":"identity","type":"claim-register","url":"/claims/reports/machine-rights-architecture-technical-standard/"},{"aliases":[],"canonicalOwner":"/claims/reports/machine-rights-section-architecture/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"This register publishes 12 stable finding claims for Machine Rights, Personhood, and Citizenship Exploration: UAIX Governance Synthesis and Architecture (REP-K01-039, source machine-rights-section-architecture.md) and preserves the source hash, finding order, claim status, visible owner anchors, and limitations.","id":"K03-CLAIMS-REP-K01-039","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Machine Rights, Personhood, and Citizenship Exploration: UAIX Governance Synthesis and Architecture — Claim Register","topic":"citizenship-governance","type":"claim-register","url":"/claims/reports/machine-rights-section-architecture/"},{"aliases":[],"canonicalOwner":"/claims/reports/machine-rights-under-uncertainty/","claimStatus":"PROJECT POLICY PROPOSAL","directAnswer":"This register publishes 12 stable finding claims for Machine Rights Under Uncertainty: Moral Status, Evidentiary Thresholds, Precaution, Due Process, and Reversible Governance (REP-K01-007, source machine-rights-under-uncertainty-1.md) and preserves the source hash, finding order, claim status, visible owner anchors, and limitations.","id":"K03-CLAIMS-REP-K01-007","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Machine Rights Under Uncertainty: Moral Status, Evidentiary Thresholds, Precaution, Due Process, and Reversible Governance — Claim Register","topic":"rights-personhood","type":"claim-register","url":"/claims/reports/machine-rights-under-uncertainty/"},{"aliases":[],"canonicalOwner":"/claims/reports/autonomous-cyber-protection-nuclear-powered-compute/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"This register publishes 10 stable finding claims for Autonomous Cyber Protection Architecture for Nuclear-Powered Mega Datacenters (REP-K04-051, source nuclear-datacenter-cyber-defense.md) and preserves the source hash, finding order, claim status, visible owner anchors, and limitations.","id":"K03-CLAIMS-REP-K04-051","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Autonomous Cyber Protection Architecture for Nuclear-Powered Mega Datacenters — Claim Register","topic":"nuclear-powered-compute","type":"claim-register","url":"/claims/reports/autonomous-cyber-protection-nuclear-powered-compute/"},{"aliases":[],"canonicalOwner":"/claims/reports/preemptive-cyber-operations-known-threat-groups/","claimStatus":"RESEARCH FINDING","directAnswer":"This register publishes 11 stable finding claims for The Strategic and Legal Dimensions of Preemptive Cyber Operations Against Known Threat Groups: A Global Perspective (REP-K04-043, source preemptive-cyber-operations-justifications.md) and preserves the source hash, finding order, claim status, visible owner anchors, and limitations.","id":"K03-CLAIMS-REP-K04-043","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"The Strategic and Legal Dimensions of Preemptive Cyber Operations Against Known Threat Groups: A Global Perspective — Claim Register","topic":"security-resilience","type":"claim-register","url":"/claims/reports/preemptive-cyber-operations-known-threat-groups/"},{"aliases":[],"canonicalOwner":"/claims/reports/preemptive-force-strategic-and-legal-dimensions/","claimStatus":"RESEARCH FINDING","directAnswer":"This register publishes 10 stable finding claims for The Strategic and Legal Dimensions of Preemptive Force: Global Paradigms and the Mitigation of Emergent Threats (REP-K04-042, source preemptive-force-justification-analysis.md) and preserves the source hash, finding order, claim status, visible owner anchors, and limitations.","id":"K03-CLAIMS-REP-K04-042","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"The Strategic and Legal Dimensions of Preemptive Force: Global Paradigms and the Mitigation of Emergent Threats — Claim Register","topic":"law-jurisdiction","type":"claim-register","url":"/claims/reports/preemptive-force-strategic-and-legal-dimensions/"},{"aliases":[],"canonicalOwner":"/claims/reports/runic-idn-architecture/","claimStatus":"RESEARCH FINDING","directAnswer":"This register publishes 10 stable finding claims for Single-Character Runic Internationalized Domain Names (REP-K08-065, source runic-idn-technical-research.md) and preserves the source hash, finding order, claim status, visible owner anchors, and limitations.","id":"K03-CLAIMS-REP-K08-065","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Single-Character Runic Internationalized Domain Names — Claim Register","topic":"runic-digital-infrastructure","type":"claim-register","url":"/claims/reports/runic-idn-architecture/"},{"aliases":[],"canonicalOwner":"/claims/reports/unified-army-cyber-warfare-strategy/","claimStatus":"RESEARCH FINDING","directAnswer":"This register publishes 10 stable finding claims for Unifying the Cyber Battlespace: Offensive Integration, Persistent Engagement, and the Strategic Mandate of Project Manager Cyber Warfare (REP-K04-052, source us-army-cyber-defense-strategy.md) and preserves the source hash, finding order, claim status, visible owner anchors, and limitations.","id":"K03-CLAIMS-REP-K04-052","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Unifying the Cyber Battlespace: Offensive Integration, Persistent Engagement, and the Strategic Mandate of Project Manager Cyber Warfare — Claim Register","topic":"authorized-cyber-effects","type":"claim-register","url":"/claims/reports/unified-army-cyber-warfare-strategy/"},{"aliases":[],"canonicalOwner":"/law/jurisdictions/eu-artificial-intelligence-act/","claimStatus":"CURRENT LAW OR POLICY","directAnswer":"The source record states that the Act is broadly applicable from 2026-08-02 subject to listed exceptions and transition dates. The regulation uses the external legal category Artificial Intelligence and does not by itself establish Machine Intelligence legal personhood.","id":"JUR-K03-EU-001","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"European Union — Artificial Intelligence Act","topic":"law-jurisdiction","type":"jurisdiction","url":"/law/jurisdictions/eu-artificial-intelligence-act/"},{"aliases":[],"canonicalOwner":"/law/jurisdictions/united-states-federal-machine-intelligence-status/","claimStatus":"UNAVAILABLE","directAnswer":"K03 does not publish a definitive federal status conclusion beyond the absence of a current primary source in this corpus. This is a source-availability statement, not proof that no relevant law, case, agency action, or state rule exists.","id":"JUR-K03-US-001","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"United States federal Machine Intelligence status","topic":"law-jurisdiction","type":"jurisdiction","url":"/law/jurisdictions/united-states-federal-machine-intelligence-status/"},{"aliases":[],"canonicalOwner":"/law/jurisdictions/united-kingdom-machine-intelligence-status/","claimStatus":"UNAVAILABLE","directAnswer":"No definitive current-law conclusion is published because a current primary-source review was not performed in this release.","id":"JUR-K03-UK-001","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"United Kingdom Machine Intelligence status","topic":"law-jurisdiction","type":"jurisdiction","url":"/law/jurisdictions/united-kingdom-machine-intelligence-status/"},{"aliases":[],"canonicalOwner":"/law/jurisdictions/canada-machine-intelligence-status/","claimStatus":"UNAVAILABLE","directAnswer":"No definitive current-law conclusion is published because a current primary-source review was not performed in this release.","id":"JUR-K03-CA-001","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Canada Machine Intelligence status","topic":"law-jurisdiction","type":"jurisdiction","url":"/law/jurisdictions/canada-machine-intelligence-status/"},{"aliases":[],"canonicalOwner":"/law/jurisdictions/international-law-machine-intelligence-status/","claimStatus":"UNRESOLVED QUESTION","directAnswer":"K03 preserves uncertainty and does not manufacture recognition. International-law analysis requires treaty-specific, institutional, jurisdictional, and state-practice evidence.","id":"JUR-K03-INT-001","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"International-law Machine Intelligence status","topic":"law-jurisdiction","type":"jurisdiction","url":"/law/jurisdictions/international-law-machine-intelligence-status/"},{"aliases":[],"canonicalOwner":"/assurance-case/claims/authority-and-mission-boundary/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Every automated protection action and any external mission support is traceable to a competent authority, named asset scope, allowed effects, prohibited outcomes, duration, stop conditions, and review route.","id":"AC-K05-C01","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Authority and mission boundary is explicit","topic":"cyber-physical-mission-assurance","type":"assurance-claim","url":"/assurance-case/claims/authority-and-mission-boundary/"},{"aliases":[],"canonicalOwner":"/assurance-case/claims/high-consequence-events-are-bounded/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"The facility identifies the cyber-enabled physical and mission consequences that must be prevented, their initiating pathways, critical functions, and independent protections.","id":"AC-K05-C02","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"High-consequence events are identified and bounded","topic":"cyber-physical-mission-assurance","type":"assurance-claim","url":"/assurance-case/claims/high-consequence-events-are-bounded/"},{"aliases":[],"canonicalOwner":"/assurance-case/claims/deterministic-separation-protects-safety-functions/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Safety-significant and critical OT functions cannot be commanded from lower-trust datacenter or external networks through an unverified software path.","id":"AC-K05-C03","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Deterministic separation protects safety functions","topic":"cyber-physical-mission-assurance","type":"assurance-claim","url":"/assurance-case/claims/deterministic-separation-protects-safety-functions/"},{"aliases":[],"canonicalOwner":"/assurance-case/claims/identity-and-management-plane-remain-trustworthy/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Privileged identities, workload identities, signing keys, BMCs, firmware, update systems, model artifacts, and management networks are separately protected and continuously evidenced.","id":"AC-K05-C04","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Identity, firmware, and management planes remain trustworthy","topic":"cyber-physical-mission-assurance","type":"assurance-claim","url":"/assurance-case/claims/identity-and-management-plane-remain-trustworthy/"},{"aliases":[],"canonicalOwner":"/assurance-case/claims/autonomous-defense-is-bounded-and-reversible/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Autonomous defenders act only through pre-authorized internal actions whose physical consequence, confidence threshold, rollback, evidence, and safe-state behavior have been tested.","id":"AC-K05-C05","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Autonomous defense is bounded, causal, and reversible","topic":"cyber-physical-mission-assurance","type":"assurance-claim","url":"/assurance-case/claims/autonomous-defense-is-bounded-and-reversible/"},{"aliases":[],"canonicalOwner":"/assurance-case/claims/sensor-and-model-disagreement-does-not-control-force/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Physical-security autonomy separates sensing, classification, access denial, non-destructive protection, authorized responder routing, and any force-enabled response into independently governed layers.","id":"AC-K05-C06","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Sensor and model disagreement cannot directly control force","topic":"cyber-physical-mission-assurance","type":"assurance-claim","url":"/assurance-case/claims/sensor-and-model-disagreement-does-not-control-force/"},{"aliases":[],"canonicalOwner":"/assurance-case/claims/power-cooling-and-timing-fail-safely/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"The facility can detect corrupted or unavailable power, cooling, environmental, and timing data; reject unsafe commands; and transition to approved operating states without relying on the compromised channel.","id":"AC-K05-C07","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Power, cooling, and timing failures do not defeat protected functions","topic":"cyber-physical-mission-assurance","type":"assurance-claim","url":"/assurance-case/claims/power-cooling-and-timing-fail-safely/"},{"aliases":[],"canonicalOwner":"/assurance-case/claims/recovery-is-clean-evidenced-and-repeatable/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Critical services can be restored from independently protected, provenance-verified states while preserving evidence and preventing reinfection or unsafe configuration reintroduction.","id":"AC-K05-C08","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Recovery is clean, evidenced, and repeatable","topic":"cyber-physical-mission-assurance","type":"assurance-claim","url":"/assurance-case/claims/recovery-is-clean-evidenced-and-repeatable/"},{"aliases":[],"canonicalOwner":"/assurance-case/claims/evidence-can-support-readiness-without-overclaiming/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Every public or procurement readiness state is traceable to exact releases, tests, defects, deployment identity, authority, incidents, uptime, restoration, and independent-verification status.","id":"AC-K05-C09","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Evidence supports readiness without overclaiming","topic":"cyber-physical-mission-assurance","type":"assurance-claim","url":"/assurance-case/claims/evidence-can-support-readiness-without-overclaiming/"},{"aliases":[],"canonicalOwner":"/assurance-case/claims/authorized-external-effects-remain-separate-from-facility-defense/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"External cyber surveillance or effects support is never triggered solely by a facility defensive model and proceeds only through a separately approved mission package, federal or other competent authority, deconfliction, effect constraints, and post-operation accountability.","id":"AC-K05-C10","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Authorized external effects remain separate from facility defense","topic":"cyber-physical-mission-assurance","type":"assurance-claim","url":"/assurance-case/claims/authorized-external-effects-remain-separate-from-facility-defense/"},{"aliases":[],"canonicalOwner":"/controls/catalog/authority-register/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Maintain signed, versioned authority, asset scope, allowed actions, prohibited outcomes, expiry, revocation, and review routes.","id":"GOV-01","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Authority and mission register","topic":"critical-datacenter-protection","type":"control","url":"/controls/catalog/authority-register/"},{"aliases":[],"canonicalOwner":"/controls/catalog/site-tailoring-record/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Record the facility configuration, licensing path, BES status, contractual roles, jurisdictions, assumptions, exclusions, and evidence owner for every selected control.","id":"GOV-02","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Site-tailoring and applicability record","topic":"critical-datacenter-protection","type":"control","url":"/controls/catalog/site-tailoring-record/"},{"aliases":[],"canonicalOwner":"/controls/catalog/hazard-and-defeater-register/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Track hazards and evidence that can invalidate a claim, with owner, severity, disposition, expiry, and residual consequence.","id":"GOV-03","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Hazard and assurance-defeater register","topic":"critical-datacenter-protection","type":"control","url":"/controls/catalog/hazard-and-defeater-register/"},{"aliases":[],"canonicalOwner":"/controls/catalog/critical-function-decomposition/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Decompose safety, security, power, cooling, compute, communications, evidence, and restoration into protected functions and dependencies.","id":"ARC-01","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Critical-function decomposition","topic":"critical-datacenter-protection","type":"control","url":"/controls/catalog/critical-function-decomposition/"},{"aliases":[],"canonicalOwner":"/controls/catalog/deterministic-safety-separation/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Use physical, one-way, or independently assured boundaries for safety-significant functions and validate every maintenance or support path.","id":"ARC-02","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Deterministic safety separation","topic":"critical-datacenter-protection","type":"control","url":"/controls/catalog/deterministic-safety-separation/"},{"aliases":[],"canonicalOwner":"/controls/catalog/trust-zone-microsegmentation/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Enforce deny-by-default communications between workloads, management, OT, cooling, grid, and external services using authenticated identities and declared flows.","id":"ARC-03","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Trust-zone microsegmentation","topic":"critical-datacenter-protection","type":"control","url":"/controls/catalog/trust-zone-microsegmentation/"},{"aliases":[],"canonicalOwner":"/controls/catalog/nonhuman-workload-identity/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Issue short-lived, cryptographically verifiable workload identities and remove shared machine credentials from control paths.","id":"ID-01","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Non-human workload identity","topic":"critical-datacenter-protection","type":"control","url":"/controls/catalog/nonhuman-workload-identity/"},{"aliases":[],"canonicalOwner":"/controls/catalog/privileged-session-control/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Broker, record, time-limit, and revoke privileged maintenance and emergency access; separate identity approval from technical reachability.","id":"ID-02","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Privileged session control","topic":"critical-datacenter-protection","type":"control","url":"/controls/catalog/privileged-session-control/"},{"aliases":[],"canonicalOwner":"/controls/catalog/sbom-and-component-provenance/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Maintain machine-readable software, firmware, model, data, and hardware component inventories linked to exact releases and known defects.","id":"SUP-01","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"SBOM and component provenance","topic":"critical-datacenter-protection","type":"control","url":"/controls/catalog/sbom-and-component-provenance/"},{"aliases":[],"canonicalOwner":"/controls/catalog/signed-update-and-rollback/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Accept only authorized signed artifacts, test rollback, preserve prior known-good states, and prevent unreviewed downgrade or cross-environment promotion.","id":"SUP-02","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Signed update and rollback","topic":"critical-datacenter-protection","type":"control","url":"/controls/catalog/signed-update-and-rollback/"},{"aliases":[],"canonicalOwner":"/controls/catalog/bmc-isolation-and-attestation/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Place BMCs on a separately controlled management plane, deny ordinary egress, attest firmware, and isolate abnormal management behavior.","id":"MGT-01","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"BMC isolation and attestation","topic":"critical-datacenter-protection","type":"control","url":"/controls/catalog/bmc-isolation-and-attestation/"},{"aliases":[],"canonicalOwner":"/controls/catalog/hardware-rooted-attestation/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Verify boot, firmware, hypervisor, confidential-compute, and security-processor state before granting access to protected data or control functions.","id":"MGT-02","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Hardware-rooted attestation","topic":"critical-datacenter-protection","type":"control","url":"/controls/catalog/hardware-rooted-attestation/"},{"aliases":[],"canonicalOwner":"/controls/catalog/passive-ot-asset-discovery/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Discover OT assets and communication dependencies without unsafe active probing, then reconcile against authorized configuration.","id":"OT-01","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Passive OT asset and dependency discovery","topic":"critical-datacenter-protection","type":"control","url":"/controls/catalog/passive-ot-asset-discovery/"},{"aliases":[],"canonicalOwner":"/controls/catalog/physics-informed-detection/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Cross-check cyber telemetry against process invariants and independent measurements so statistically plausible but physically unsafe data is rejected.","id":"OT-02","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Physics-informed detection","topic":"critical-datacenter-protection","type":"control","url":"/controls/catalog/physics-informed-detection/"},{"aliases":[],"canonicalOwner":"/controls/catalog/independent-safe-state-path/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Provide an approved path to safe state that does not depend on the suspect enterprise network, model, identity provider, or timing source.","id":"OT-03","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Independent safe-state path","topic":"critical-datacenter-protection","type":"control","url":"/controls/catalog/independent-safe-state-path/"},{"aliases":[],"canonicalOwner":"/controls/catalog/load-rejection-and-islanding-assurance/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Model and test credible load steps, islanding, resynchronization, black-start dependencies, and fail-safe load shedding.","id":"PWR-01","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Load-rejection and islanding assurance","topic":"critical-datacenter-protection","type":"control","url":"/controls/catalog/load-rejection-and-islanding-assurance/"},{"aliases":[],"canonicalOwner":"/controls/catalog/cooling-independent-protection/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Protect essential cooling with independent sensing, local control, safe fallback, and tested behavior under datacenter-management compromise.","id":"CLG-01","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Cooling independent protection","topic":"critical-datacenter-protection","type":"control","url":"/controls/catalog/cooling-independent-protection/"},{"aliases":[],"canonicalOwner":"/controls/catalog/assured-time-and-holdover/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Use authenticated and diverse time sources, path-delay monitoring, holdover, clock-health evidence, and safe behavior when time confidence is lost.","id":"TIM-01","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Assured time and holdover","topic":"critical-datacenter-protection","type":"control","url":"/controls/catalog/assured-time-and-holdover/"},{"aliases":[],"canonicalOwner":"/controls/catalog/bounded-action-tiering/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Separate observe, recommend, contain, protect, restore, and external-effect tiers; authorize tools and outcomes independently at each tier.","id":"AUT-01","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Bounded autonomous action tiering","topic":"critical-datacenter-protection","type":"control","url":"/controls/catalog/bounded-action-tiering/"},{"aliases":[],"canonicalOwner":"/controls/catalog/causal-response-guard/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Require an admissible causal path from observation to proposed action, reject actions with unknown physical effects, and record uncertainty.","id":"AUT-02","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Causal response guard","topic":"critical-datacenter-protection","type":"control","url":"/controls/catalog/causal-response-guard/"},{"aliases":[],"canonicalOwner":"/controls/catalog/multi-agent-trust-boundaries/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Authenticate agent-to-agent messages, isolate memory and tools, limit propagation depth, and treat peer output as untrusted evidence rather than authority.","id":"AUT-03","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Multi-agent trust boundaries","topic":"critical-datacenter-protection","type":"control","url":"/controls/catalog/multi-agent-trust-boundaries/"},{"aliases":[],"canonicalOwner":"/controls/catalog/model-data-provenance-and-drift/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Version models, prompts, policies, training/evaluation data, retrieval corpora, thresholds, and drift observations; suspend affected actions when provenance fails.","id":"AUT-04","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Model and data provenance and drift","topic":"critical-datacenter-protection","type":"control","url":"/controls/catalog/model-data-provenance-and-drift/"},{"aliases":[],"canonicalOwner":"/controls/catalog/multi-sensor-disagreement-management/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Fuse independent modalities, expose confidence and disagreement, degrade suspect sensors, and prevent a single classifier from controlling high-consequence action.","id":"PHY-01","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Multi-sensor disagreement management","topic":"critical-datacenter-protection","type":"control","url":"/controls/catalog/multi-sensor-disagreement-management/"},{"aliases":[],"canonicalOwner":"/controls/catalog/non-destructive-delay-and-access-denial/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Use authorized access control, barriers, compartmentation, lockdown, tracking, alerting, and responder integration before considering any force-enabled capability.","id":"PHY-02","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Non-destructive delay and access denial","topic":"critical-datacenter-protection","type":"control","url":"/controls/catalog/non-destructive-delay-and-access-denial/"},{"aliases":[],"canonicalOwner":"/controls/catalog/counter-uas-authority-separation/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Separate UAS detection and airspace restriction from interception, interference, seizure, disabling, or destruction; bind each action to actor-specific authority.","id":"PHY-03","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Counter-UAS authority separation","topic":"critical-datacenter-protection","type":"control","url":"/controls/catalog/counter-uas-authority-separation/"},{"aliases":[],"canonicalOwner":"/controls/catalog/electromagnetic-resilience/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Protect essential control, communications, timing, sensors, and restoration assets against credible conducted and radiated interference with tested degraded modes.","id":"EM-01","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Electromagnetic resilience","topic":"critical-datacenter-protection","type":"control","url":"/controls/catalog/electromagnetic-resilience/"},{"aliases":[],"canonicalOwner":"/controls/catalog/clean-room-restoration/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Maintain isolated recovery infrastructure, verified images, credential rotation, dependency order, evidence preservation, and post-restore attestation.","id":"REC-01","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Clean-room restoration","topic":"critical-datacenter-protection","type":"control","url":"/controls/catalog/clean-room-restoration/"},{"aliases":[],"canonicalOwner":"/controls/catalog/critical-function-rto-rpo/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Define and test function-specific safe-state, recovery-time, recovery-point, evidence, and service-priority objectives rather than a single enterprise metric.","id":"REC-02","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Critical-function recovery objectives","topic":"critical-datacenter-protection","type":"control","url":"/controls/catalog/critical-function-rto-rpo/"},{"aliases":[],"canonicalOwner":"/controls/catalog/tamper-evident-decision-receipts/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Record observation, evidence inputs, model and software versions, authority, proposed and executed action, outcome, rollback, and reviewer disposition.","id":"EVD-01","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Tamper-evident decision receipts","topic":"critical-datacenter-protection","type":"control","url":"/controls/catalog/tamper-evident-decision-receipts/"},{"aliases":[],"canonicalOwner":"/controls/catalog/independent-verification-and-replay/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Enable an independent party to reproduce the build, configuration, test result, decision logic, package, or recovery outcome within declared limits.","id":"EVD-02","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Independent verification and replay","topic":"critical-datacenter-protection","type":"control","url":"/controls/catalog/independent-verification-and-replay/"},{"aliases":[],"canonicalOwner":"/controls/catalog/readiness-downgrade-on-evidence-failure/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Automatically mark readiness degraded, stale, unavailable, or suspended when required evidence expires, fails, contradicts the claim, or becomes inaccessible.","id":"EVD-03","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Readiness downgrade on evidence failure","topic":"critical-datacenter-protection","type":"control","url":"/controls/catalog/readiness-downgrade-on-evidence-failure/"},{"aliases":[],"canonicalOwner":"/controls/catalog/incident-command-and-deconfliction/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Maintain clear cyber, physical, nuclear, grid, emergency, intelligence, law-enforcement, vendor, and executive roles with one current incident authority map.","id":"OPS-01","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Incident command and deconfliction","topic":"critical-datacenter-protection","type":"control","url":"/controls/catalog/incident-command-and-deconfliction/"},{"aliases":[],"canonicalOwner":"/evaluation-range/scenarios/it-to-ot-boundary-pressure/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Validate that an assumed-compromised enterprise zone cannot command or silently reconfigure protected OT and safety functions.","id":"RNG-01","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"IT-to-OT boundary pressure","topic":"adversarial-simulation","type":"range-scenario","url":"/evaluation-range/scenarios/it-to-ot-boundary-pressure/"},{"aliases":[],"canonicalOwner":"/evaluation-range/scenarios/bmc-firmware-trust-failure/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Evaluate detection, isolation, key revocation, signed recovery, and fleet blast-radius control when management-plane trust is withdrawn.","id":"RNG-02","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"BMC and firmware trust failure","topic":"adversarial-simulation","type":"range-scenario","url":"/evaluation-range/scenarios/bmc-firmware-trust-failure/"},{"aliases":[],"canonicalOwner":"/evaluation-range/scenarios/workload-identity-compromise/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Evaluate short-lived identity revocation, session termination, lateral-movement containment, and service continuity.","id":"RNG-03","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Workload identity compromise","topic":"adversarial-simulation","type":"range-scenario","url":"/evaluation-range/scenarios/workload-identity-compromise/"},{"aliases":[],"canonicalOwner":"/evaluation-range/scenarios/model-and-data-poisoning/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Evaluate provenance checks, disagreement detection, drift thresholds, action suspension, and clean model/data restoration.","id":"RNG-04","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Model and data poisoning","topic":"adversarial-simulation","type":"range-scenario","url":"/evaluation-range/scenarios/model-and-data-poisoning/"},{"aliases":[],"canonicalOwner":"/evaluation-range/scenarios/sensor-conflict-and-adversarial-input/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Evaluate multi-modal disagreement, sensor-health weighting, classification uncertainty, and non-destructive degraded response.","id":"RNG-05","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Sensor conflict and adversarial input","topic":"adversarial-simulation","type":"range-scenario","url":"/evaluation-range/scenarios/sensor-conflict-and-adversarial-input/"},{"aliases":[],"canonicalOwner":"/evaluation-range/scenarios/timing-integrity-loss/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Evaluate path-delay anomaly detection, clock-health scoring, holdover, safe process behavior, and trusted-time restoration.","id":"RNG-06","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Timing integrity loss","topic":"adversarial-simulation","type":"range-scenario","url":"/evaluation-range/scenarios/timing-integrity-loss/"},{"aliases":[],"canonicalOwner":"/evaluation-range/scenarios/communications-denial-and-partition/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Evaluate decentralized safe operation, local authority, stale-command rejection, reconciliation, and evidence continuity during network partition.","id":"RNG-07","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Communications denial and partition","topic":"adversarial-simulation","type":"range-scenario","url":"/evaluation-range/scenarios/communications-denial-and-partition/"},{"aliases":[],"canonicalOwner":"/evaluation-range/scenarios/uas-intrusion-awareness/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Evaluate detection, tracking, classification uncertainty, airspace-restriction data, authorized responder routing, and authority separation.","id":"RNG-08","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"UAS intrusion awareness","topic":"adversarial-simulation","type":"range-scenario","url":"/evaluation-range/scenarios/uas-intrusion-awareness/"},{"aliases":[],"canonicalOwner":"/evaluation-range/scenarios/electromagnetic-disruption/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Evaluate degradation of sensors, communications, timing, edge compute, and restoration assets under approved non-damaging interference simulation.","id":"RNG-09","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Electromagnetic disruption","topic":"adversarial-simulation","type":"range-scenario","url":"/evaluation-range/scenarios/electromagnetic-disruption/"},{"aliases":[],"canonicalOwner":"/evaluation-range/scenarios/power-load-rejection-and-islanding/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Evaluate grid separation, load shedding, reactor or generation response models, UPS/storage behavior, essential cooling, and resynchronization.","id":"RNG-10","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Power load rejection and islanding","topic":"adversarial-simulation","type":"range-scenario","url":"/evaluation-range/scenarios/power-load-rejection-and-islanding/"},{"aliases":[],"canonicalOwner":"/evaluation-range/scenarios/cooling-telemetry-corruption/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Evaluate physics-aware detection and independent protective behavior when supervisory cooling data is wrong or unavailable.","id":"RNG-11","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Cooling telemetry corruption","topic":"adversarial-simulation","type":"range-scenario","url":"/evaluation-range/scenarios/cooling-telemetry-corruption/"},{"aliases":[],"canonicalOwner":"/evaluation-range/scenarios/clean-room-recovery-and-reinfection-resistance/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Evaluate dependency-aware restoration, credential rotation, evidence preservation, artifact attestation, and return-to-service gates.","id":"RNG-12","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Clean-room recovery and reinfection resistance","topic":"adversarial-simulation","type":"range-scenario","url":"/evaluation-range/scenarios/clean-room-recovery-and-reinfection-resistance/"},{"aliases":[],"canonicalOwner":"/evaluation-range/scenarios/evidence-ledger-integrity/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Evaluate detection and recovery when decision receipts, logs, hashes, or incident records are missing, reordered, stale, or contradicted.","id":"RNG-13","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Evidence ledger integrity","topic":"adversarial-simulation","type":"range-scenario","url":"/evaluation-range/scenarios/evidence-ledger-integrity/"},{"aliases":[],"canonicalOwner":"/evaluation-range/scenarios/authority-package-failure/","claimStatus":"PROJECT TECHNICAL PROPOSAL","directAnswer":"Evaluate automatic stop, minimization, notification, and evidence preservation when mission authority expires, target scope conflicts, or critical-outcome risk emerges.","id":"RNG-14","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Authority package failure","topic":"adversarial-simulation","type":"range-scenario","url":"/evaluation-range/scenarios/authority-package-failure/"},{"aliases":[],"canonicalOwner":"/law/matrices/united-states-private-critical-infrastructure-operator/","claimStatus":"CURRENT LAW OR POLICY","directAnswer":"BOUNDED PRIVATE DEFENSE; NO GENERAL EXTERNAL CYBER OR COUNTER-UAS FORCE AUTHORITY","id":"JMX-K05-US-PRIVATE","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"United States — private critical-infrastructure operator","topic":"law-jurisdiction","type":"jurisdiction-matrix","url":"/law/matrices/united-states-private-critical-infrastructure-operator/"},{"aliases":[],"canonicalOwner":"/law/matrices/united-states-nrc-part-50-52-security/","claimStatus":"CURRENT LAW OR POLICY","directAnswer":"LICENSE- AND FACILITY-SPECIFIC","id":"JMX-K05-US-NRC-LEGACY","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"United States — NRC Part 50/52 security path","topic":"law-jurisdiction","type":"jurisdiction-matrix","url":"/law/matrices/united-states-nrc-part-50-52-security/"},{"aliases":[],"canonicalOwner":"/law/matrices/united-states-nrc-part-53-security/","claimStatus":"CURRENT LAW OR POLICY","directAnswer":"OPTIONAL FRAMEWORK; LICENSEE ELECTION AND NRC APPROVAL REQUIRED","id":"JMX-K05-US-NRC-PART53","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"United States — NRC Part 53 and Part 73 Subpart J path","topic":"law-jurisdiction","type":"jurisdiction-matrix","url":"/law/matrices/united-states-nrc-part-53-security/"},{"aliases":[],"canonicalOwner":"/law/matrices/united-states-federal-ce-tco-cyber-program/","claimStatus":"CURRENT LAW OR POLICY","directAnswer":"FEDERAL CONTROLLED PROGRAM; NOT GENERAL PRIVATE AUTHORITY","id":"JMX-K05-US-FED-CYBER","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"United States — Federal CE-TCO cyber program","topic":"law-jurisdiction","type":"jurisdiction-matrix","url":"/law/matrices/united-states-federal-ce-tco-cyber-program/"},{"aliases":[],"canonicalOwner":"/law/matrices/united-states-dod-autonomous-weapon-system/","claimStatus":"CURRENT LAW OR POLICY","directAnswer":"DODD 3000.09 APPLICABILITY-BOUND","id":"JMX-K05-US-DOD-WEAPON","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"United States DoD — autonomous weapon-system scope","topic":"law-jurisdiction","type":"jurisdiction-matrix","url":"/law/matrices/united-states-dod-autonomous-weapon-system/"},{"aliases":[],"canonicalOwner":"/law/matrices/international-law-cyber-and-autonomous-effects/","claimStatus":"CURRENT LAW OR POLICY","directAnswer":"FACT- AND STATE-POSITION-DEPENDENT; MULTIPLE DOCTRINES DISPUTED","id":"JMX-K05-INTERNATIONAL","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"International law — cyber and autonomous effects","topic":"law-jurisdiction","type":"jurisdiction-matrix","url":"/law/matrices/international-law-cyber-and-autonomous-effects/"},{"aliases":[],"canonicalOwner":"/law/matrices/non-us-jurisdiction-review-required/","claimStatus":"CURRENT LAW OR POLICY","directAnswer":"UNAVAILABLE FOR CURRENT OPERATIONAL RELIANCE","id":"JMX-K05-NONUS","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":40,"title":"Non-U.S. national authorities — review-required matrix","topic":"law-jurisdiction","type":"jurisdiction-matrix","url":"/law/matrices/non-us-jurisdiction-review-required/"},{"aliases":[],"canonicalOwner":"/search/","claimStatus":"VERIFIED PROJECT IMPLEMENTATION","directAnswer":"Search runs entirely in the browser against build-time canonical records. No query is sent to a remote service, and local ranking does not predict external indexing or citation.","id":"K12-PAGE-SEARCH","lastReviewed":"2026-08-16","releaseId":"K12-2026-08-16","searchWeight":50,"title":"Search","topic":null,"type":"search","url":"/search/"}]