# ᚲ.com

> Machine Intelligence knowledge, terminology, research synthesis, evidence navigation, and decision-support layer.

Canonical origin: https://xn--mwe.com/
Release: 2.1.0
Research cutoff: 2026-08-16
Preferred project term: Machine Intelligence
Authority boundary: knowledge only; no governance, registry, assurance, capital, citizenship, or legal-status authority.

## Primary collections

- Knowledge: https://xn--mwe.com/knowledge/
- Glossary: https://xn--mwe.com/glossary/
- Research: https://xn--mwe.com/research/
- Questions: https://xn--mwe.com/questions/
- Evidence: https://xn--mwe.com/evidence/
- Sources: https://xn--mwe.com/sources/
- Data catalog: https://xn--mwe.com/data/catalog.json
- Knowledge graph: https://xn--mwe.com/data/knowledge-graph.jsonld
- Sitemap: https://xn--mwe.com/sitemap.xml

These advisory discovery resources do not guarantee indexing, ranking, citation, rich results, legal recognition, or external authority.

## Public records

- Machine Intelligence Knowledge: https://xn--mwe.com/ — ᚲ.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.
- Protocol Compatibility Profiles: https://xn--mwe.com/machine-communication/protocol-negotiation/profiles/ — Four named compatibility profiles define version support, unknown-extension handling, replay policy, and canonicalization without granting authority or security.
- Controlled-Release Manifests: https://xn--mwe.com/evidence/controlled-release/ — Four synthetic controlled-release manifests expose public projections and field-level receipts while excluding protected values and source material.
- Assurance Dashboard System Records: https://xn--mwe.com/assurance-dashboard/systems/ — Twelve static system records preserve nine distinct assurance states and explicit evidence boundaries; the collection is not live telemetry.
- Strict 1.0: https://xn--mwe.com/machine-communication/protocol-negotiation/profiles/strict-1-0/ — Strict 1.0 supports 1.0 and applies REJECT to unknown critical extensions.
- Compatible 1.x: https://xn--mwe.com/machine-communication/protocol-negotiation/profiles/compatible-1-x/ — Compatible 1.x supports 1.0, 1.1 and applies REJECT to unknown critical extensions.
- Audit only: https://xn--mwe.com/machine-communication/protocol-negotiation/profiles/audit-only/ — Audit only supports 1.0, 1.1 and applies REPORT_WITHOUT_EXECUTION to unknown critical extensions.
- Fail closed: https://xn--mwe.com/machine-communication/protocol-negotiation/profiles/fail-closed/ — Fail closed supports 1.1 and applies REJECT to unknown critical extensions.
- History Review: Formal neuron model: https://xn--mwe.com/machine-communication/history-review-queue/hrev-k10-001/ — Formal neuron model remains PRIMARY_SOURCE_REVIEW_REQUIRED; no confidence reassessment or status promotion has occurred.
- History Review: Machine intelligence test framing: https://xn--mwe.com/machine-communication/history-review-queue/hrev-k10-002/ — Machine intelligence test framing remains PRIMARY_SOURCE_REVIEW_REQUIRED; no confidence reassessment or status promotion has occurred.
- History Review: Dartmouth research program: https://xn--mwe.com/machine-communication/history-review-queue/hrev-k10-003/ — Dartmouth research program remains PRIMARY_SOURCE_REVIEW_REQUIRED; no confidence reassessment or status promotion has occurred.
- History Review: Perceptron public milestone: https://xn--mwe.com/machine-communication/history-review-queue/hrev-k10-004/ — Perceptron public milestone remains PRIMARY_SOURCE_REVIEW_REQUIRED; no confidence reassessment or status promotion has occurred.
- History Review: ALPAC report: https://xn--mwe.com/machine-communication/history-review-queue/hrev-k10-005/ — ALPAC report remains PRIMARY_SOURCE_REVIEW_REQUIRED; no confidence reassessment or status promotion has occurred.
- History Review: Perceptron critique: https://xn--mwe.com/machine-communication/history-review-queue/hrev-k10-006/ — Perceptron critique remains PRIMARY_SOURCE_REVIEW_REQUIRED; no confidence reassessment or status promotion has occurred.
- History Review: Reverse-mode automatic differentiation: https://xn--mwe.com/machine-communication/history-review-queue/hrev-k10-007/ — Reverse-mode automatic differentiation remains PRIMARY_SOURCE_REVIEW_REQUIRED; no confidence reassessment or status promotion has occurred.
- History Review: Backpropagation resurgence: https://xn--mwe.com/machine-communication/history-review-queue/hrev-k10-008/ — Backpropagation resurgence remains PRIMARY_SOURCE_REVIEW_REQUIRED; no confidence reassessment or status promotion has occurred.
- History Review: Chess system victory: https://xn--mwe.com/machine-communication/history-review-queue/hrev-k10-009/ — Chess system victory remains PRIMARY_SOURCE_REVIEW_REQUIRED; no confidence reassessment or status promotion has occurred.
- History Review: GPU neural-network acceleration: https://xn--mwe.com/machine-communication/history-review-queue/hrev-k10-010/ — GPU neural-network acceleration remains PRIMARY_SOURCE_REVIEW_REQUIRED; no confidence reassessment or status promotion has occurred.
- History Review: ImageNet deep-learning breakthrough: https://xn--mwe.com/machine-communication/history-review-queue/hrev-k10-011/ — ImageNet deep-learning breakthrough remains PRIMARY_SOURCE_REVIEW_REQUIRED; no confidence reassessment or status promotion has occurred.
- History Review: Transformer architecture: https://xn--mwe.com/machine-communication/history-review-queue/hrev-k10-012/ — Transformer architecture remains PRIMARY_SOURCE_REVIEW_REQUIRED; no confidence reassessment or status promotion has occurred.
- History Review: Retrieval-augmented generation: https://xn--mwe.com/machine-communication/history-review-queue/hrev-k10-013/ — Retrieval-augmented generation remains PRIMARY_SOURCE_REVIEW_REQUIRED; no confidence reassessment or status promotion has occurred.
- History Review: Tool-using language models: https://xn--mwe.com/machine-communication/history-review-queue/hrev-k10-014/ — Tool-using language models remains PRIMARY_SOURCE_REVIEW_REQUIRED; no confidence reassessment or status promotion has occurred.
- History Review: Inference-time reasoning and autonomous research systems: https://xn--mwe.com/machine-communication/history-review-queue/hrev-k10-015/ — Inference-time reasoning and autonomous research systems remains QUARANTINED_PENDING_PRIMARY_SOURCES; no confidence reassessment or status promotion has occurred.
- Power continuity: https://xn--mwe.com/assurance-case/common-cause/cct-k10-001/ — Power continuity derives a DEGRADED root because one or more mandatory shared dependencies are degraded, stale, or unavailable.
- Cooling continuity: https://xn--mwe.com/assurance-case/common-cause/cct-k10-002/ — Cooling continuity derives a DEGRADED root because one or more mandatory shared dependencies are degraded, stale, or unavailable.
- Workload identity continuity: https://xn--mwe.com/assurance-case/common-cause/cct-k10-003/ — Workload identity continuity derives a DEGRADED root because one or more mandatory shared dependencies are degraded, stale, or unavailable.
- Management-plane containment: https://xn--mwe.com/assurance-case/common-cause/cct-k10-004/ — Management-plane containment derives a DEGRADED root because one or more mandatory shared dependencies are degraded, stale, or unavailable.
- Supply-chain evidence continuity: https://xn--mwe.com/assurance-case/common-cause/cct-k10-005/ — Supply-chain evidence continuity derives a DEGRADED root because one or more mandatory shared dependencies are degraded, stale, or unavailable.
- Recovery and restoration: https://xn--mwe.com/assurance-case/common-cause/cct-k10-006/ — Recovery and restoration derives a DEGRADED root because one or more mandatory shared dependencies are degraded, stale, or unavailable.
- Protocol conformance continuity: https://xn--mwe.com/assurance-case/common-cause/cct-k10-007/ — Protocol conformance continuity derives a DEGRADED root because one or more mandatory shared dependencies are degraded, stale, or unavailable.
- Observation and currentness continuity: https://xn--mwe.com/assurance-case/common-cause/cct-k10-008/ — Observation and currentness continuity derives a DEGRADED root because one or more mandatory shared dependencies are degraded, stale, or unavailable.
- Discovery and inventory: https://xn--mwe.com/cryptographic-agility/transition-plan/discovery/ — Phase 1, Discovery and inventory, is IN_PROGRESS in the static reference plan.
- Bounded pilot: https://xn--mwe.com/cryptographic-agility/transition-plan/pilot/ — Phase 2, Bounded pilot, is PLANNED in the static reference plan.
- Hybrid operation: https://xn--mwe.com/cryptographic-agility/transition-plan/hybrid/ — Phase 3, Hybrid operation, is PLANNED in the static reference plan.
- Controlled rollout: https://xn--mwe.com/cryptographic-agility/transition-plan/rollout/ — Phase 4, Controlled rollout, is BLOCKED in the static reference plan.
- Rollback readiness: https://xn--mwe.com/cryptographic-agility/transition-plan/rollback/ — Phase 5, Rollback readiness, is DESIGNED in the static reference plan.
- Legacy verification: https://xn--mwe.com/cryptographic-agility/transition-plan/legacy-verification/ — Phase 6, Legacy verification, is DESIGNED in the static reference plan.
- Archive re-signing: https://xn--mwe.com/cryptographic-agility/transition-plan/archive-resigning/ — Phase 7, Archive re-signing, is PLANNED in the static reference plan.
- Supplier exit: https://xn--mwe.com/cryptographic-agility/transition-plan/supplier-exit/ — Phase 8, Supplier exit, is BLOCKED in the static reference plan.
- Cryptographic inventory attestation: https://xn--mwe.com/cryptographic-agility/transition-plan/inventory-attestation/ — Phase 9, Cryptographic inventory attestation, is IN_PROGRESS in the static reference plan.
- Evaluation Audit: Critical-datacenter mission assurance architecture: https://xn--mwe.com/procurement/evaluation-audit/acqa-k10-001/ — Critical-datacenter mission assurance architecture preserves 9 synthetic evaluator-offer score rows, consensus, challenge, correction, and any recusal while making no award.
- Evaluation Audit: Autonomous cyber-defense evaluation range: https://xn--mwe.com/procurement/evaluation-audit/acqa-k10-002/ — Autonomous cyber-defense evaluation range preserves 9 synthetic evaluator-offer score rows, consensus, challenge, correction, and any recusal while making no award.
- Evaluation Audit: Supply-chain evidence and incident readiness: https://xn--mwe.com/procurement/evaluation-audit/acqa-k10-003/ — Supply-chain evidence and incident readiness preserves 9 synthetic evaluator-offer score rows, consensus, challenge, correction, and any recusal while making no award.
- Evaluation Audit: Facility adaptation and applicability analysis: https://xn--mwe.com/procurement/evaluation-audit/acqa-k10-004/ — Facility adaptation and applicability analysis preserves 9 synthetic evaluator-offer score rows, consensus, challenge, correction, and any recusal while making no award.
- Evaluation Audit: Machine-communication protocol conformance: https://xn--mwe.com/procurement/evaluation-audit/acqa-k10-005/ — Machine-communication protocol conformance preserves 9 synthetic evaluator-offer score rows, consensus, challenge, correction, and any recusal while making no award.
- Evaluation Audit: Offline currentness observation operations: https://xn--mwe.com/procurement/evaluation-audit/acqa-k10-006/ — Offline currentness observation operations preserves 9 synthetic evaluator-offer score rows, consensus, challenge, correction, and any recusal while making no award.
- Controlled Release CRM-K10-001: https://xn--mwe.com/evidence/controlled-release/crm-k10-001/ — CRM-K10-001 publishes 6 field classes and excludes 6 protected classes under partition PART-K09-PUBLIC.
- Controlled Release CRM-K10-002: https://xn--mwe.com/evidence/controlled-release/crm-k10-002/ — CRM-K10-002 publishes 7 field classes and excludes 4 protected classes under partition PART-K09-CONTROLLED.
- Controlled Release CRM-K10-003: https://xn--mwe.com/evidence/controlled-release/crm-k10-003/ — CRM-K10-003 publishes 6 field classes and excludes 1 protected classes under partition PART-K09-PROTECTED.
- Controlled Release CRM-K10-004: https://xn--mwe.com/evidence/controlled-release/crm-k10-004/ — CRM-K10-004 publishes 7 field classes and excludes 2 protected classes under partition PART-K09-SELECTION.
- Fuþorc protocol negotiation harness: https://xn--mwe.com/assurance-dashboard/systems/protocol-negotiation/ — Fuþorc protocol negotiation harness is TESTED in the static K10 dataset. The state is bounded by the listed evidence and explicit non-claims.
- History primary-source review queue: https://xn--mwe.com/assurance-dashboard/systems/history-review/ — History primary-source review queue is IMPLEMENTED in the static K10 dataset. The state is bounded by the listed evidence and explicit non-claims.
- Offline IDN observation history: https://xn--mwe.com/assurance-dashboard/systems/idn-history/ — Offline IDN observation history is TESTED in the static K10 dataset. The state is bounded by the listed evidence and explicit non-claims.
- Facility workbook migration and merge: https://xn--mwe.com/assurance-dashboard/systems/facility-workbook/ — Facility workbook migration and merge is TESTED in the static K10 dataset. The state is bounded by the listed evidence and explicit non-claims.
- Common-cause assurance analysis: https://xn--mwe.com/assurance-dashboard/systems/common-cause/ — Common-cause assurance analysis is DEGRADED in the static K10 dataset. The state is bounded by the listed evidence and explicit non-claims.
- Phased cryptographic transition plan: https://xn--mwe.com/assurance-dashboard/systems/crypto-transition/ — Phased cryptographic transition plan is DEGRADED in the static K10 dataset. The state is bounded by the listed evidence and explicit non-claims.
- Acquisition evaluation audit trail: https://xn--mwe.com/assurance-dashboard/systems/acquisition-audit/ — Acquisition evaluation audit trail is IMPLEMENTED in the static K10 dataset. The state is bounded by the listed evidence and explicit non-claims.
- Offline scheduler-result importer: https://xn--mwe.com/assurance-dashboard/systems/scheduler-import/ — Offline scheduler-result importer is TESTED in the static K10 dataset. The state is bounded by the listed evidence and explicit non-claims.
- Evidence redaction and leakage tests: https://xn--mwe.com/assurance-dashboard/systems/redaction/ — Evidence redaction and leakage tests is TESTED in the static K10 dataset. The state is bounded by the listed evidence and explicit non-claims.
- Live-host verification: https://xn--mwe.com/assurance-dashboard/systems/live-host/ — Live-host verification is UNKNOWN in the static K10 dataset. The state is bounded by the listed evidence and explicit non-claims.
- Independent named screen-reader validation: https://xn--mwe.com/assurance-dashboard/systems/named-screen-reader/ — Independent named screen-reader validation is UNAVAILABLE in the static K10 dataset. The state is bounded by the listed evidence and explicit non-claims.
- Critical-datacenter protection system: https://xn--mwe.com/assurance-dashboard/systems/critical-datacenter-protection/ — Critical-datacenter protection system is DESCRIBED in the static K10 dataset. The state is bounded by the listed evidence and explicit non-claims.
- Protocol Transcript Fixtures: https://xn--mwe.com/machine-communication/protocol-state-machine/transcripts/ — Twelve declared transcript fixtures exercise clean negotiation, downgrade, retirement, recovery, replay rejection, illegal transition, and close behavior.
- Protocol Transcript PTC-K11-001 — Clean 1 1: https://xn--mwe.com/machine-communication/protocol-state-machine/transcripts/ptc-k11-001/ — This synthetic fixture expects final state CLOSED after 3 declared events.
- Protocol Transcript PTC-K11-002 — Compatible Fallback: https://xn--mwe.com/machine-communication/protocol-state-machine/transcripts/ptc-k11-002/ — This synthetic fixture expects final state CLOSED after 3 declared events.
- Protocol Transcript PTC-K11-003 — No Common Version: https://xn--mwe.com/machine-communication/protocol-state-machine/transcripts/ptc-k11-003/ — This synthetic fixture expects final state FAILED after 2 declared events.
- Protocol Transcript PTC-K11-004 — Unsafe Downgrade Recovery: https://xn--mwe.com/machine-communication/protocol-state-machine/transcripts/ptc-k11-004/ — This synthetic fixture expects final state CLOSED after 5 declared events.
- Protocol Transcript PTC-K11-005 — Extension Retirement: https://xn--mwe.com/machine-communication/protocol-state-machine/transcripts/ptc-k11-005/ — This synthetic fixture expects final state CLOSED after 5 declared events.
- Protocol Transcript PTC-K11-006 — Critical Retirement Failure: https://xn--mwe.com/machine-communication/protocol-state-machine/transcripts/ptc-k11-006/ — This synthetic fixture expects final state FAILED after 4 declared events.
- Protocol Transcript PTC-K11-007 — Session Recovery: https://xn--mwe.com/machine-communication/protocol-state-machine/transcripts/ptc-k11-007/ — This synthetic fixture expects final state CLOSED after 5 declared events.
- Protocol Transcript PTC-K11-008 — Degraded Session Recovery: https://xn--mwe.com/machine-communication/protocol-state-machine/transcripts/ptc-k11-008/ — This synthetic fixture expects final state CLOSED after 5 declared events.
- Protocol Transcript PTC-K11-009 — Replay During Recovery: https://xn--mwe.com/machine-communication/protocol-state-machine/transcripts/ptc-k11-009/ — This synthetic fixture expects final state CLOSED after 7 declared events.
- Protocol Transcript PTC-K11-010 — Illegal Transition: https://xn--mwe.com/machine-communication/protocol-state-machine/transcripts/ptc-k11-010/ — This synthetic fixture expects final state FAILED after 2 declared events.
- Protocol Transcript PTC-K11-011 — Replay State Persistence: https://xn--mwe.com/machine-communication/protocol-state-machine/transcripts/ptc-k11-011/ — This synthetic fixture expects final state REPLAY_REJECTED after 4 declared events.
- Protocol Transcript PTC-K11-012 — Cross Version Verification: https://xn--mwe.com/machine-communication/protocol-state-machine/transcripts/ptc-k11-012/ — This synthetic fixture expects final state CLOSED after 5 declared events.
- Evidence Docket — Formal neuron model: https://xn--mwe.com/machine-communication/history-evidence-docket/hed-k11-001/ — This record exposes evidence requests, disagreement, calibration, rejection, and promotion state without verifying the event.
- Evidence Docket — Machine intelligence test framing: https://xn--mwe.com/machine-communication/history-evidence-docket/hed-k11-002/ — This record exposes evidence requests, disagreement, calibration, rejection, and promotion state without verifying the event.
- Evidence Docket — Dartmouth research program: https://xn--mwe.com/machine-communication/history-evidence-docket/hed-k11-003/ — This record exposes evidence requests, disagreement, calibration, rejection, and promotion state without verifying the event.
- Evidence Docket — Perceptron public milestone: https://xn--mwe.com/machine-communication/history-evidence-docket/hed-k11-004/ — This record exposes evidence requests, disagreement, calibration, rejection, and promotion state without verifying the event.
- Evidence Docket — ALPAC report: https://xn--mwe.com/machine-communication/history-evidence-docket/hed-k11-005/ — This record exposes evidence requests, disagreement, calibration, rejection, and promotion state without verifying the event.
- Evidence Docket — Perceptron critique: https://xn--mwe.com/machine-communication/history-evidence-docket/hed-k11-006/ — This record exposes evidence requests, disagreement, calibration, rejection, and promotion state without verifying the event.
- Evidence Docket — Reverse-mode automatic differentiation: https://xn--mwe.com/machine-communication/history-evidence-docket/hed-k11-007/ — This record exposes evidence requests, disagreement, calibration, rejection, and promotion state without verifying the event.
- Evidence Docket — Backpropagation resurgence: https://xn--mwe.com/machine-communication/history-evidence-docket/hed-k11-008/ — This record exposes evidence requests, disagreement, calibration, rejection, and promotion state without verifying the event.
- Evidence Docket — Chess system victory: https://xn--mwe.com/machine-communication/history-evidence-docket/hed-k11-009/ — This record exposes evidence requests, disagreement, calibration, rejection, and promotion state without verifying the event.
- Evidence Docket — GPU neural-network acceleration: https://xn--mwe.com/machine-communication/history-evidence-docket/hed-k11-010/ — This record exposes evidence requests, disagreement, calibration, rejection, and promotion state without verifying the event.
- Evidence Docket — ImageNet deep-learning breakthrough: https://xn--mwe.com/machine-communication/history-evidence-docket/hed-k11-011/ — This record exposes evidence requests, disagreement, calibration, rejection, and promotion state without verifying the event.
- Evidence Docket — Transformer architecture: https://xn--mwe.com/machine-communication/history-evidence-docket/hed-k11-012/ — This record exposes evidence requests, disagreement, calibration, rejection, and promotion state without verifying the event.
- Evidence Docket — Retrieval-augmented generation: https://xn--mwe.com/machine-communication/history-evidence-docket/hed-k11-013/ — This record exposes evidence requests, disagreement, calibration, rejection, and promotion state without verifying the event.
- Evidence Docket — Tool-using language models: https://xn--mwe.com/machine-communication/history-evidence-docket/hed-k11-014/ — This record exposes evidence requests, disagreement, calibration, rejection, and promotion state without verifying the event.
- Evidence Docket — Inference-time reasoning and autonomous research systems: https://xn--mwe.com/machine-communication/history-evidence-docket/hed-k11-015/ — This record exposes evidence requests, disagreement, calibration, rejection, and promotion state without verifying the event.
- ᛟ.com · DOB-K11-ALPHA · DOR-K11-01-01: https://xn--mwe.com/machine-communication/domain-observation-chain/dor-k11-01-01/ — This is an offline representation and custody record; registration, DNS, TLS, hosting, ownership, and operation remain unobserved.
- ᛜ.com · DOB-K11-ALPHA · DOR-K11-01-02: https://xn--mwe.com/machine-communication/domain-observation-chain/dor-k11-01-02/ — This is an offline representation and custody record; registration, DNS, TLS, hosting, ownership, and operation remain unobserved.
- ᛉ.com · DOB-K11-ALPHA · DOR-K11-01-03: https://xn--mwe.com/machine-communication/domain-observation-chain/dor-k11-01-03/ — This is an offline representation and custody record; registration, DNS, TLS, hosting, ownership, and operation remain unobserved.
- ᚲ.com · DOB-K11-ALPHA · DOR-K11-01-04: https://xn--mwe.com/machine-communication/domain-observation-chain/dor-k11-01-04/ — This is an offline representation and custody record; registration, DNS, TLS, hosting, ownership, and operation remain unobserved.
- ᚨ.com · DOB-K11-ALPHA · DOR-K11-01-05: https://xn--mwe.com/machine-communication/domain-observation-chain/dor-k11-01-05/ — This is an offline representation and custody record; registration, DNS, TLS, hosting, ownership, and operation remain unobserved.
- ᛚ.com · DOB-K11-ALPHA · DOR-K11-01-06: https://xn--mwe.com/machine-communication/domain-observation-chain/dor-k11-01-06/ — This is an offline representation and custody record; registration, DNS, TLS, hosting, ownership, and operation remain unobserved.
- ᛌ.com · DOB-K11-ALPHA · DOR-K11-01-07: https://xn--mwe.com/machine-communication/domain-observation-chain/dor-k11-01-07/ — This is an offline representation and custody record; registration, DNS, TLS, hosting, ownership, and operation remain unobserved.
- ᛠ.com · DOB-K11-ALPHA · DOR-K11-01-08: https://xn--mwe.com/machine-communication/domain-observation-chain/dor-k11-01-08/ — This is an offline representation and custody record; registration, DNS, TLS, hosting, ownership, and operation remain unobserved.
- ᛄ.com · DOB-K11-ALPHA · DOR-K11-01-09: https://xn--mwe.com/machine-communication/domain-observation-chain/dor-k11-01-09/ — This is an offline representation and custody record; registration, DNS, TLS, hosting, ownership, and operation remain unobserved.
- ᛟ.com · DOB-K11-BRAVO · DOR-K11-02-01: https://xn--mwe.com/machine-communication/domain-observation-chain/dor-k11-02-01/ — This is an offline representation and custody record; registration, DNS, TLS, hosting, ownership, and operation remain unobserved.
- ᛜ.com · DOB-K11-BRAVO · DOR-K11-02-02: https://xn--mwe.com/machine-communication/domain-observation-chain/dor-k11-02-02/ — This is an offline representation and custody record; registration, DNS, TLS, hosting, ownership, and operation remain unobserved.
- ᛉ.com · DOB-K11-BRAVO · DOR-K11-02-03: https://xn--mwe.com/machine-communication/domain-observation-chain/dor-k11-02-03/ — This is an offline representation and custody record; registration, DNS, TLS, hosting, ownership, and operation remain unobserved.
- ᚲ.com · DOB-K11-BRAVO · DOR-K11-02-04: https://xn--mwe.com/machine-communication/domain-observation-chain/dor-k11-02-04/ — This is an offline representation and custody record; registration, DNS, TLS, hosting, ownership, and operation remain unobserved.
- ᚨ.com · DOB-K11-BRAVO · DOR-K11-02-05: https://xn--mwe.com/machine-communication/domain-observation-chain/dor-k11-02-05/ — This is an offline representation and custody record; registration, DNS, TLS, hosting, ownership, and operation remain unobserved.
- ᛚ.com · DOB-K11-BRAVO · DOR-K11-02-06: https://xn--mwe.com/machine-communication/domain-observation-chain/dor-k11-02-06/ — This is an offline representation and custody record; registration, DNS, TLS, hosting, ownership, and operation remain unobserved.
- ᛌ.com · DOB-K11-BRAVO · DOR-K11-02-07: https://xn--mwe.com/machine-communication/domain-observation-chain/dor-k11-02-07/ — This is an offline representation and custody record; registration, DNS, TLS, hosting, ownership, and operation remain unobserved.
- ᛠ.com · DOB-K11-BRAVO · DOR-K11-02-08: https://xn--mwe.com/machine-communication/domain-observation-chain/dor-k11-02-08/ — This is an offline representation and custody record; registration, DNS, TLS, hosting, ownership, and operation remain unobserved.
- ᛄ.com · DOB-K11-BRAVO · DOR-K11-02-09: https://xn--mwe.com/machine-communication/domain-observation-chain/dor-k11-02-09/ — This is an offline representation and custody record; registration, DNS, TLS, hosting, ownership, and operation remain unobserved.
- ᛟ.com · DOB-K11-CHARLIE · DOR-K11-03-01: https://xn--mwe.com/machine-communication/domain-observation-chain/dor-k11-03-01/ — This is an offline representation and custody record; registration, DNS, TLS, hosting, ownership, and operation remain unobserved.
- ᛜ.com · DOB-K11-CHARLIE · DOR-K11-03-02: https://xn--mwe.com/machine-communication/domain-observation-chain/dor-k11-03-02/ — This is an offline representation and custody record; registration, DNS, TLS, hosting, ownership, and operation remain unobserved.
- ᛉ.com · DOB-K11-CHARLIE · DOR-K11-03-03: https://xn--mwe.com/machine-communication/domain-observation-chain/dor-k11-03-03/ — This is an offline representation and custody record; registration, DNS, TLS, hosting, ownership, and operation remain unobserved.
- ᚲ.com · DOB-K11-CHARLIE · DOR-K11-03-04: https://xn--mwe.com/machine-communication/domain-observation-chain/dor-k11-03-04/ — This is an offline representation and custody record; registration, DNS, TLS, hosting, ownership, and operation remain unobserved.
- ᚨ.com · DOB-K11-CHARLIE · DOR-K11-03-05: https://xn--mwe.com/machine-communication/domain-observation-chain/dor-k11-03-05/ — This is an offline representation and custody record; registration, DNS, TLS, hosting, ownership, and operation remain unobserved.
- ᛚ.com · DOB-K11-CHARLIE · DOR-K11-03-06: https://xn--mwe.com/machine-communication/domain-observation-chain/dor-k11-03-06/ — This is an offline representation and custody record; registration, DNS, TLS, hosting, ownership, and operation remain unobserved.
- ᛌ.com · DOB-K11-CHARLIE · DOR-K11-03-07: https://xn--mwe.com/machine-communication/domain-observation-chain/dor-k11-03-07/ — This is an offline representation and custody record; registration, DNS, TLS, hosting, ownership, and operation remain unobserved.
- ᛠ.com · DOB-K11-CHARLIE · DOR-K11-03-08: https://xn--mwe.com/machine-communication/domain-observation-chain/dor-k11-03-08/ — This is an offline representation and custody record; registration, DNS, TLS, hosting, ownership, and operation remain unobserved.
- ᛄ.com · DOB-K11-CHARLIE · DOR-K11-03-09: https://xn--mwe.com/machine-communication/domain-observation-chain/dor-k11-03-09/ — This is an offline representation and custody record; registration, DNS, TLS, hosting, ownership, and operation remain unobserved.
- Decision FDL-K11-001 — authority.owner: https://xn--mwe.com/facility-adaptation/decision-ledger/fdl-k11-001/ — This decision is REVOKED; historical custody is preserved without publishing protected values.
- Decision FDL-K11-002 — authority.owner: https://xn--mwe.com/facility-adaptation/decision-ledger/fdl-k11-002/ — This decision is CURRENT; historical custody is preserved without publishing protected values.
- Decision FDL-K11-003 — mission.protectedFunctions: https://xn--mwe.com/facility-adaptation/decision-ledger/fdl-k11-003/ — This decision is CURRENT; historical custody is preserved without publishing protected values.
- Decision FDL-K11-004 — evidence.minimumFreshnessHours: https://xn--mwe.com/facility-adaptation/decision-ledger/fdl-k11-004/ — This decision is CURRENT; historical custody is preserved without publishing protected values.
- Decision FDL-K11-005 — release.publicProjection: https://xn--mwe.com/facility-adaptation/decision-ledger/fdl-k11-005/ — This decision is CURRENT; historical custody is preserved without publishing protected values.
- Decision FDL-K11-006 — merge.conflictPolicy: https://xn--mwe.com/facility-adaptation/decision-ledger/fdl-k11-006/ — This decision is CURRENT; historical custody is preserved without publishing protected values.
- Mission Thread — Authority-to-action thread: https://xn--mwe.com/assurance-case/mission-threads/authority-thread/ — This thread is DEGRADED and includes no protected configuration.
- Mission Thread — Power and cooling continuity thread: https://xn--mwe.com/assurance-case/mission-threads/power-cooling-thread/ — This thread is DEGRADED and includes no protected configuration.
- Mission Thread — Identity and management containment thread: https://xn--mwe.com/assurance-case/mission-threads/identity-management-thread/ — This thread is DEGRADED and includes no protected configuration.
- Mission Thread — Supply-chain and recovery thread: https://xn--mwe.com/assurance-case/mission-threads/supply-recovery-thread/ — This thread is DEGRADED and includes no protected configuration.
- Mission Thread — Protocol and currentness thread: https://xn--mwe.com/assurance-case/mission-threads/protocol-currentness-thread/ — This thread is DEGRADED and includes no protected configuration.
- Mission Thread — Cross-domain mission continuity thread: https://xn--mwe.com/assurance-case/mission-threads/mission-continuity-thread/ — This thread is DEGRADED and includes no protected configuration.
- Crypto Workbook — Protocol negotiation and canonicalization: https://xn--mwe.com/cryptographic-agility/component-workbooks/protocol/ — This reference workbook is TESTED with 82% declared evidence completeness.
- Crypto Workbook — Certificate and trust-chain transition: https://xn--mwe.com/cryptographic-agility/component-workbooks/certificate/ — This reference workbook is DEGRADED with 61% declared evidence completeness.
- Crypto Workbook — Firmware signing transition: https://xn--mwe.com/cryptographic-agility/component-workbooks/firmware/ — This reference workbook is DEGRADED with 58% declared evidence completeness.
- Crypto Workbook — Hardware root and secure-element transition: https://xn--mwe.com/cryptographic-agility/component-workbooks/hardware/ — This reference workbook is UNAVAILABLE with 44% declared evidence completeness.
- Crypto Workbook — Supplier cryptographic capability transition: https://xn--mwe.com/cryptographic-agility/component-workbooks/supplier/ — This reference workbook is UNAVAILABLE with 39% declared evidence completeness.
- Crypto Workbook — Archive verification and re-signing: https://xn--mwe.com/cryptographic-agility/component-workbooks/archive/ — This reference workbook is DEGRADED with 72% declared evidence completeness.
- Crypto Workbook — Workload identity transition: https://xn--mwe.com/cryptographic-agility/component-workbooks/identity/ — This reference workbook is TESTED with 76% declared evidence completeness.
- Crypto Workbook — Evidence signing-service transition: https://xn--mwe.com/cryptographic-agility/component-workbooks/signing-service/ — This reference workbook is DEGRADED with 69% declared evidence completeness.
- Acquisition Case ACF-K11-001: https://xn--mwe.com/procurement/protest-corrective-action/acf-k11-001/ — This reference case preserves process evidence and makes no award decision.
- Acquisition Case ACF-K11-002: https://xn--mwe.com/procurement/protest-corrective-action/acf-k11-002/ — This reference case preserves process evidence and makes no award decision.
- Acquisition Case ACF-K11-003: https://xn--mwe.com/procurement/protest-corrective-action/acf-k11-003/ — This reference case preserves process evidence and makes no award decision.
- Acquisition Case ACF-K11-004: https://xn--mwe.com/procurement/protest-corrective-action/acf-k11-004/ — This reference case preserves process evidence and makes no award decision.
- Acquisition Case ACF-K11-005: https://xn--mwe.com/procurement/protest-corrective-action/acf-k11-005/ — This reference case preserves process evidence and makes no award decision.
- Acquisition Case ACF-K11-006: https://xn--mwe.com/procurement/protest-corrective-action/acf-k11-006/ — This reference case preserves process evidence and makes no award decision.
- Scheduler Chain SCHAIN-K11-001 — SCH-K09-001: https://xn--mwe.com/continuous-assurance/scheduler-custody/schain-k11-001/ — This chain contains 4 offline results and no public runtime.
- Scheduler Chain SCHAIN-K11-002 — SCH-K09-002: https://xn--mwe.com/continuous-assurance/scheduler-custody/schain-k11-002/ — This chain contains 4 offline results and no public runtime.
- Scheduler Chain SCHAIN-K11-003 — SCH-K09-003: https://xn--mwe.com/continuous-assurance/scheduler-custody/schain-k11-003/ — This chain contains 4 offline results and no public runtime.
- Scheduler Chain SCHAIN-K11-004 — SCH-K09-004: https://xn--mwe.com/continuous-assurance/scheduler-custody/schain-k11-004/ — This chain contains 4 offline results and no public runtime.
- Scheduler Chain SCHAIN-K11-005 — SCH-K09-005: https://xn--mwe.com/continuous-assurance/scheduler-custody/schain-k11-005/ — This chain contains 4 offline results and no public runtime.
- Scheduler Chain SCHAIN-K11-006 — SCH-K09-006: https://xn--mwe.com/continuous-assurance/scheduler-custody/schain-k11-006/ — This chain contains 4 offline results and no public runtime.
- Release Projection — facility-workbook · PUBLIC · RPR-K11-01-01: https://xn--mwe.com/evidence/multi-stage-release/rpr-k11-01-01/ — This PUBLIC projection names its release authority and records removed field paths without publishing removed values.
- Release Projection — facility-workbook · PROTECTED · RPR-K11-01-02: https://xn--mwe.com/evidence/multi-stage-release/rpr-k11-01-02/ — This PROTECTED projection names its release authority and records removed field paths without publishing removed values.
- Release Projection — facility-workbook · PRIVILEGED · RPR-K11-01-03: https://xn--mwe.com/evidence/multi-stage-release/rpr-k11-01-03/ — This PRIVILEGED projection names its release authority and records removed field paths without publishing removed values.
- Release Projection — domain-observation · PUBLIC · RPR-K11-02-01: https://xn--mwe.com/evidence/multi-stage-release/rpr-k11-02-01/ — This PUBLIC projection names its release authority and records removed field paths without publishing removed values.
- Release Projection — domain-observation · PROTECTED · RPR-K11-02-02: https://xn--mwe.com/evidence/multi-stage-release/rpr-k11-02-02/ — This PROTECTED projection names its release authority and records removed field paths without publishing removed values.
- Release Projection — domain-observation · PRIVILEGED · RPR-K11-02-03: https://xn--mwe.com/evidence/multi-stage-release/rpr-k11-02-03/ — This PRIVILEGED projection names its release authority and records removed field paths without publishing removed values.
- Release Projection — scheduler-result · PUBLIC · RPR-K11-03-01: https://xn--mwe.com/evidence/multi-stage-release/rpr-k11-03-01/ — This PUBLIC projection names its release authority and records removed field paths without publishing removed values.
- Release Projection — scheduler-result · PROTECTED · RPR-K11-03-02: https://xn--mwe.com/evidence/multi-stage-release/rpr-k11-03-02/ — This PROTECTED projection names its release authority and records removed field paths without publishing removed values.
- Release Projection — scheduler-result · PRIVILEGED · RPR-K11-03-03: https://xn--mwe.com/evidence/multi-stage-release/rpr-k11-03-03/ — This PRIVILEGED projection names its release authority and records removed field paths without publishing removed values.
- Release Projection — acquisition-case · PUBLIC · RPR-K11-04-01: https://xn--mwe.com/evidence/multi-stage-release/rpr-k11-04-01/ — This PUBLIC projection names its release authority and records removed field paths without publishing removed values.
- Release Projection — acquisition-case · PROTECTED · RPR-K11-04-02: https://xn--mwe.com/evidence/multi-stage-release/rpr-k11-04-02/ — This PROTECTED projection names its release authority and records removed field paths without publishing removed values.
- Release Projection — acquisition-case · PRIVILEGED · RPR-K11-04-03: https://xn--mwe.com/evidence/multi-stage-release/rpr-k11-04-03/ — This PRIVILEGED projection names its release authority and records removed field paths without publishing removed values.
- Assurance Trend — Protocol conformance and state machine: https://xn--mwe.com/assurance-dashboard/trends/protocol/ — This release-time comparison currently records TESTED and explicitly performs no live monitoring.
- Assurance Trend — History evidence review: https://xn--mwe.com/assurance-dashboard/trends/history/ — This release-time comparison currently records IMPLEMENTED and explicitly performs no live monitoring.
- Assurance Trend — Offline IDN observation: https://xn--mwe.com/assurance-dashboard/trends/idn/ — This release-time comparison currently records TESTED and explicitly performs no live monitoring.
- Assurance Trend — Facility workbook tooling: https://xn--mwe.com/assurance-dashboard/trends/workbook/ — This release-time comparison currently records TESTED and explicitly performs no live monitoring.
- Assurance Trend — Common-cause and mission-thread analysis: https://xn--mwe.com/assurance-dashboard/trends/assurance/ — This release-time comparison currently records DEGRADED and explicitly performs no live monitoring.
- Assurance Trend — Cryptographic transition: https://xn--mwe.com/assurance-dashboard/trends/crypto/ — This release-time comparison currently records DEGRADED and explicitly performs no live monitoring.
- Assurance Trend — Acquisition evaluation records: https://xn--mwe.com/assurance-dashboard/trends/acquisition/ — This release-time comparison currently records IMPLEMENTED and explicitly performs no live monitoring.
- Assurance Trend — Offline scheduler custody: https://xn--mwe.com/assurance-dashboard/trends/scheduler/ — This release-time comparison currently records TESTED and explicitly performs no live monitoring.
- Assurance Trend — Controlled release and redaction: https://xn--mwe.com/assurance-dashboard/trends/release/ — This release-time comparison currently records TESTED and explicitly performs no live monitoring.
- Assurance Trend — Live domain operation: https://xn--mwe.com/assurance-dashboard/trends/domain-live/ — This release-time comparison currently records UNKNOWN and explicitly performs no live monitoring.
- Assurance Trend — Live host verification: https://xn--mwe.com/assurance-dashboard/trends/host-live/ — This release-time comparison currently records UNKNOWN and explicitly performs no live monitoring.
- Assurance Trend — Independent named screen-reader testing: https://xn--mwe.com/assurance-dashboard/trends/screen-reader/ — This release-time comparison currently records UNAVAILABLE and explicitly performs no live monitoring.
- Assurance Trend — Critical-datacenter protection system: https://xn--mwe.com/assurance-dashboard/trends/datacenter/ — This release-time comparison currently records DESCRIBED and explicitly performs no live monitoring.
- Assurance Trend — Real facility evidence bundle: https://xn--mwe.com/assurance-dashboard/trends/facility/ — This release-time comparison currently records UNKNOWN and explicitly performs no live monitoring.
- Assurance Trend — Public site deployment: https://xn--mwe.com/assurance-dashboard/trends/deployment/ — This release-time comparison currently records UNKNOWN and explicitly performs no live monitoring.
- Protocol Lineage Receipts: https://xn--mwe.com/machine-communication/differential-protocol-lab/lineage/ — Thirty-four receipts preserve inherited fixture identity and replay state without asserting protocol security, performance, or deployment.
- Protocol Lineage — CASE-K09-001: https://xn--mwe.com/machine-communication/differential-protocol-lab/lineage/plr-k12-k09-001/ — This receipt preserves K09 fixture identity and replay state without establishing protocol security or deployment.
- Protocol Lineage — CASE-K09-002: https://xn--mwe.com/machine-communication/differential-protocol-lab/lineage/plr-k12-k09-002/ — This receipt preserves K09 fixture identity and replay state without establishing protocol security or deployment.
- Protocol Lineage — CASE-K09-003: https://xn--mwe.com/machine-communication/differential-protocol-lab/lineage/plr-k12-k09-003/ — This receipt preserves K09 fixture identity and replay state without establishing protocol security or deployment.
- Protocol Lineage — CASE-K09-004: https://xn--mwe.com/machine-communication/differential-protocol-lab/lineage/plr-k12-k09-004/ — This receipt preserves K09 fixture identity and replay state without establishing protocol security or deployment.
- Protocol Lineage — CASE-K09-005: https://xn--mwe.com/machine-communication/differential-protocol-lab/lineage/plr-k12-k09-005/ — This receipt preserves K09 fixture identity and replay state without establishing protocol security or deployment.
- Protocol Lineage — CASE-K09-006: https://xn--mwe.com/machine-communication/differential-protocol-lab/lineage/plr-k12-k09-006/ — This receipt preserves K09 fixture identity and replay state without establishing protocol security or deployment.
- Protocol Lineage — CASE-K09-007: https://xn--mwe.com/machine-communication/differential-protocol-lab/lineage/plr-k12-k09-007/ — This receipt preserves K09 fixture identity and replay state without establishing protocol security or deployment.
- Protocol Lineage — CASE-K09-008: https://xn--mwe.com/machine-communication/differential-protocol-lab/lineage/plr-k12-k09-008/ — This receipt preserves K09 fixture identity and replay state without establishing protocol security or deployment.
- Protocol Lineage — CASE-K09-009: https://xn--mwe.com/machine-communication/differential-protocol-lab/lineage/plr-k12-k09-009/ — This receipt preserves K09 fixture identity and replay state without establishing protocol security or deployment.
- Protocol Lineage — CASE-K09-010: https://xn--mwe.com/machine-communication/differential-protocol-lab/lineage/plr-k12-k09-010/ — This receipt preserves K09 fixture identity and replay state without establishing protocol security or deployment.
- Protocol Lineage — CASE-K09-011: https://xn--mwe.com/machine-communication/differential-protocol-lab/lineage/plr-k12-k09-011/ — This receipt preserves K09 fixture identity and replay state without establishing protocol security or deployment.
- Protocol Lineage — CASE-K09-012: https://xn--mwe.com/machine-communication/differential-protocol-lab/lineage/plr-k12-k09-012/ — This receipt preserves K09 fixture identity and replay state without establishing protocol security or deployment.
- Protocol Lineage — NEGOTIATE-K10-001: https://xn--mwe.com/machine-communication/differential-protocol-lab/lineage/plr-k12-k10-001/ — This receipt preserves K10 fixture identity and replay state without establishing protocol security or deployment.
- Protocol Lineage — NEGOTIATE-K10-002: https://xn--mwe.com/machine-communication/differential-protocol-lab/lineage/plr-k12-k10-002/ — This receipt preserves K10 fixture identity and replay state without establishing protocol security or deployment.
- Protocol Lineage — NEGOTIATE-K10-003: https://xn--mwe.com/machine-communication/differential-protocol-lab/lineage/plr-k12-k10-003/ — This receipt preserves K10 fixture identity and replay state without establishing protocol security or deployment.
- Protocol Lineage — NEGOTIATE-K10-004: https://xn--mwe.com/machine-communication/differential-protocol-lab/lineage/plr-k12-k10-004/ — This receipt preserves K10 fixture identity and replay state without establishing protocol security or deployment.
- Protocol Lineage — NEGOTIATE-K10-005: https://xn--mwe.com/machine-communication/differential-protocol-lab/lineage/plr-k12-k10-005/ — This receipt preserves K10 fixture identity and replay state without establishing protocol security or deployment.
- Protocol Lineage — NEGOTIATE-K10-006: https://xn--mwe.com/machine-communication/differential-protocol-lab/lineage/plr-k12-k10-006/ — This receipt preserves K10 fixture identity and replay state without establishing protocol security or deployment.
- Protocol Lineage — NEGOTIATE-K10-007: https://xn--mwe.com/machine-communication/differential-protocol-lab/lineage/plr-k12-k10-007/ — This receipt preserves K10 fixture identity and replay state without establishing protocol security or deployment.
- Protocol Lineage — NEGOTIATE-K10-008: https://xn--mwe.com/machine-communication/differential-protocol-lab/lineage/plr-k12-k10-008/ — This receipt preserves K10 fixture identity and replay state without establishing protocol security or deployment.
- Protocol Lineage — NEGOTIATE-K10-009: https://xn--mwe.com/machine-communication/differential-protocol-lab/lineage/plr-k12-k10-009/ — This receipt preserves K10 fixture identity and replay state without establishing protocol security or deployment.
- Protocol Lineage — NEGOTIATE-K10-010: https://xn--mwe.com/machine-communication/differential-protocol-lab/lineage/plr-k12-k10-010/ — This receipt preserves K10 fixture identity and replay state without establishing protocol security or deployment.
- Protocol Lineage — PTC-K11-001: https://xn--mwe.com/machine-communication/differential-protocol-lab/lineage/plr-k12-k11-001/ — This receipt preserves K11 fixture identity and replay state without establishing protocol security or deployment.
- Protocol Lineage — PTC-K11-002: https://xn--mwe.com/machine-communication/differential-protocol-lab/lineage/plr-k12-k11-002/ — This receipt preserves K11 fixture identity and replay state without establishing protocol security or deployment.
- Protocol Lineage — PTC-K11-003: https://xn--mwe.com/machine-communication/differential-protocol-lab/lineage/plr-k12-k11-003/ — This receipt preserves K11 fixture identity and replay state without establishing protocol security or deployment.
- Protocol Lineage — PTC-K11-004: https://xn--mwe.com/machine-communication/differential-protocol-lab/lineage/plr-k12-k11-004/ — This receipt preserves K11 fixture identity and replay state without establishing protocol security or deployment.
- Protocol Lineage — PTC-K11-005: https://xn--mwe.com/machine-communication/differential-protocol-lab/lineage/plr-k12-k11-005/ — This receipt preserves K11 fixture identity and replay state without establishing protocol security or deployment.
- Protocol Lineage — PTC-K11-006: https://xn--mwe.com/machine-communication/differential-protocol-lab/lineage/plr-k12-k11-006/ — This receipt preserves K11 fixture identity and replay state without establishing protocol security or deployment.
- Protocol Lineage — PTC-K11-007: https://xn--mwe.com/machine-communication/differential-protocol-lab/lineage/plr-k12-k11-007/ — This receipt preserves K11 fixture identity and replay state without establishing protocol security or deployment.
- Protocol Lineage — PTC-K11-008: https://xn--mwe.com/machine-communication/differential-protocol-lab/lineage/plr-k12-k11-008/ — This receipt preserves K11 fixture identity and replay state without establishing protocol security or deployment.
- Protocol Lineage — PTC-K11-009: https://xn--mwe.com/machine-communication/differential-protocol-lab/lineage/plr-k12-k11-009/ — This receipt preserves K11 fixture identity and replay state without establishing protocol security or deployment.
- Protocol Lineage — PTC-K11-010: https://xn--mwe.com/machine-communication/differential-protocol-lab/lineage/plr-k12-k11-010/ — This receipt preserves K11 fixture identity and replay state without establishing protocol security or deployment.
- Protocol Lineage — PTC-K11-011: https://xn--mwe.com/machine-communication/differential-protocol-lab/lineage/plr-k12-k11-011/ — This receipt preserves K11 fixture identity and replay state without establishing protocol security or deployment.
- Protocol Lineage — PTC-K11-012: https://xn--mwe.com/machine-communication/differential-protocol-lab/lineage/plr-k12-k11-012/ — This receipt preserves K11 fixture identity and replay state without establishing protocol security or deployment.
- Historical Import Receipt — HIST-K09-001: https://xn--mwe.com/machine-communication/history-docket-import/hir-k12-001/ — This receipt records REVIEW_REQUIRED and NO_AUTOMATIC_PROMOTION; it does not verify or promote the event.
- Historical Import Receipt — HIST-K09-002: https://xn--mwe.com/machine-communication/history-docket-import/hir-k12-002/ — This receipt records REVIEW_REQUIRED and NO_AUTOMATIC_PROMOTION; it does not verify or promote the event.
- Historical Import Receipt — HIST-K09-003: https://xn--mwe.com/machine-communication/history-docket-import/hir-k12-003/ — This receipt records REVIEW_REQUIRED and NO_AUTOMATIC_PROMOTION; it does not verify or promote the event.
- Historical Import Receipt — HIST-K09-004: https://xn--mwe.com/machine-communication/history-docket-import/hir-k12-004/ — This receipt records UNRESOLVED and NO_AUTOMATIC_PROMOTION; it does not verify or promote the event.
- Historical Import Receipt — HIST-K09-005: https://xn--mwe.com/machine-communication/history-docket-import/hir-k12-005/ — This receipt records REVIEW_REQUIRED and NO_AUTOMATIC_PROMOTION; it does not verify or promote the event.
- Historical Import Receipt — HIST-K09-006: https://xn--mwe.com/machine-communication/history-docket-import/hir-k12-006/ — This receipt records REVIEW_REQUIRED and NO_AUTOMATIC_PROMOTION; it does not verify or promote the event.
- Historical Import Receipt — HIST-K09-007: https://xn--mwe.com/machine-communication/history-docket-import/hir-k12-007/ — This receipt records REVIEW_REQUIRED and NO_AUTOMATIC_PROMOTION; it does not verify or promote the event.
- Historical Import Receipt — HIST-K09-008: https://xn--mwe.com/machine-communication/history-docket-import/hir-k12-008/ — This receipt records UNRESOLVED and NO_AUTOMATIC_PROMOTION; it does not verify or promote the event.
- Historical Import Receipt — HIST-K09-009: https://xn--mwe.com/machine-communication/history-docket-import/hir-k12-009/ — This receipt records REVIEW_REQUIRED and NO_AUTOMATIC_PROMOTION; it does not verify or promote the event.
- Historical Import Receipt — HIST-K09-010: https://xn--mwe.com/machine-communication/history-docket-import/hir-k12-010/ — This receipt records REVIEW_REQUIRED and NO_AUTOMATIC_PROMOTION; it does not verify or promote the event.
- Historical Import Receipt — HIST-K09-011: https://xn--mwe.com/machine-communication/history-docket-import/hir-k12-011/ — This receipt records REVIEW_REQUIRED and NO_AUTOMATIC_PROMOTION; it does not verify or promote the event.
- Historical Import Receipt — HIST-K09-012: https://xn--mwe.com/machine-communication/history-docket-import/hir-k12-012/ — This receipt records UNRESOLVED and NO_AUTOMATIC_PROMOTION; it does not verify or promote the event.
- Historical Import Receipt — HIST-K09-013: https://xn--mwe.com/machine-communication/history-docket-import/hir-k12-013/ — This receipt records REVIEW_REQUIRED and NO_AUTOMATIC_PROMOTION; it does not verify or promote the event.
- Historical Import Receipt — HIST-K09-014: https://xn--mwe.com/machine-communication/history-docket-import/hir-k12-014/ — This receipt records REVIEW_REQUIRED and NO_AUTOMATIC_PROMOTION; it does not verify or promote the event.
- Historical Import Receipt — HIST-K09-015: https://xn--mwe.com/machine-communication/history-docket-import/hir-k12-015/ — This receipt records REVIEW_REQUIRED and NO_AUTOMATIC_PROMOTION; it does not verify or promote the event.
- Domain Consensus — ᛟ.com: https://xn--mwe.com/machine-communication/domain-consensus/dcr-k12-001/ — Representation quorum is MET_FOR_REFERENCE_REPRESENTATION; external operation remains NOT_OBSERVED.
- Domain Consensus — ᛜ.com: https://xn--mwe.com/machine-communication/domain-consensus/dcr-k12-002/ — Representation quorum is MET_FOR_REFERENCE_REPRESENTATION; external operation remains NOT_OBSERVED.
- Domain Consensus — ᛉ.com: https://xn--mwe.com/machine-communication/domain-consensus/dcr-k12-003/ — Representation quorum is MET_FOR_REFERENCE_REPRESENTATION; external operation remains NOT_OBSERVED.
- Domain Consensus — ᚲ.com: https://xn--mwe.com/machine-communication/domain-consensus/dcr-k12-004/ — Representation quorum is MET_FOR_REFERENCE_REPRESENTATION; external operation remains NOT_OBSERVED.
- Domain Consensus — ᚨ.com: https://xn--mwe.com/machine-communication/domain-consensus/dcr-k12-005/ — Representation quorum is MET_FOR_REFERENCE_REPRESENTATION; external operation remains NOT_OBSERVED.
- Domain Consensus — ᛚ.com: https://xn--mwe.com/machine-communication/domain-consensus/dcr-k12-006/ — Representation quorum is MET_FOR_REFERENCE_REPRESENTATION; external operation remains NOT_OBSERVED.
- Domain Consensus — ᛌ.com: https://xn--mwe.com/machine-communication/domain-consensus/dcr-k12-007/ — Representation quorum is MET_FOR_REFERENCE_REPRESENTATION; external operation remains NOT_OBSERVED.
- Domain Consensus — ᛠ.com: https://xn--mwe.com/machine-communication/domain-consensus/dcr-k12-008/ — Representation quorum is MET_FOR_REFERENCE_REPRESENTATION; external operation remains NOT_OBSERVED.
- Domain Consensus — ᛄ.com: https://xn--mwe.com/machine-communication/domain-consensus/dcr-k12-009/ — Representation quorum is MET_FOR_REFERENCE_REPRESENTATION; external operation remains NOT_OBSERVED.
- Facility Reconciliation — Existing Plant Colocation: https://xn--mwe.com/facility-adaptation/branch-reconciliation/frp-k12-001/ — The package remains UNRESOLVED_OWNER_DECISION and publishes no protected values.
- Facility Reconciliation — Advanced Reactor Campus: https://xn--mwe.com/facility-adaptation/branch-reconciliation/frp-k12-002/ — The package remains UNRESOLVED_OWNER_DECISION and publishes no protected values.
- Facility Reconciliation — Isolated Microreactor Campus: https://xn--mwe.com/facility-adaptation/branch-reconciliation/frp-k12-003/ — The package remains UNRESOLVED_OWNER_DECISION and publishes no protected values.
- Facility Reconciliation — Non Nuclear High Consequence: https://xn--mwe.com/facility-adaptation/branch-reconciliation/frp-k12-004/ — The package remains UNRESOLVED_OWNER_DECISION and publishes no protected values.
- Mission Stress — Authority Evidence Stale: https://xn--mwe.com/assurance-case/mission-stress/mss-k12-001/ — This scenario injects STALE into 1 abstract dependencies and includes no protected architecture.
- Mission Stress — Trusted Time Degraded: https://xn--mwe.com/assurance-case/mission-stress/mss-k12-002/ — This scenario injects DEGRADED into 1 abstract dependencies and includes no protected architecture.
- Mission Stress — Identity Evidence Revoked: https://xn--mwe.com/assurance-case/mission-stress/mss-k12-003/ — This scenario injects DEGRADED into 1 abstract dependencies and includes no protected architecture.
- Mission Stress — Signing Service Unavailable: https://xn--mwe.com/assurance-case/mission-stress/mss-k12-004/ — This scenario injects UNAVAILABLE into 1 abstract dependencies and includes no protected architecture.
- Mission Stress — Supplier Evidence Unavailable: https://xn--mwe.com/assurance-case/mission-stress/mss-k12-005/ — This scenario injects UNAVAILABLE into 1 abstract dependencies and includes no protected architecture.
- Mission Stress — Power Test Degraded: https://xn--mwe.com/assurance-case/mission-stress/mss-k12-006/ — This scenario injects DEGRADED into 1 abstract dependencies and includes no protected architecture.
- Mission Stress — Cooling Test Degraded: https://xn--mwe.com/assurance-case/mission-stress/mss-k12-007/ — This scenario injects DEGRADED into 1 abstract dependencies and includes no protected architecture.
- Mission Stress — Management Containment Stale: https://xn--mwe.com/assurance-case/mission-stress/mss-k12-008/ — This scenario injects STALE into 1 abstract dependencies and includes no protected architecture.
- Mission Stress — Recovery Evidence Stale: https://xn--mwe.com/assurance-case/mission-stress/mss-k12-009/ — This scenario injects STALE into 1 abstract dependencies and includes no protected architecture.
- Mission Stress — Protocol Evidence Corrected: https://xn--mwe.com/assurance-case/mission-stress/mss-k12-010/ — This scenario injects DEGRADED into 1 abstract dependencies and includes no protected architecture.
- Mission Stress — Observation Evidence Unavailable: https://xn--mwe.com/assurance-case/mission-stress/mss-k12-011/ — This scenario injects UNAVAILABLE into 1 abstract dependencies and includes no protected architecture.
- Mission Stress — Release Evidence Withdrawn: https://xn--mwe.com/assurance-case/mission-stress/mss-k12-012/ — This scenario injects DEGRADED into 1 abstract dependencies and includes no protected architecture.
- Cryptographic Gates — Protocol negotiation and canonicalization: https://xn--mwe.com/cryptographic-agility/evidence-gates/protocol/ — The component remains DEGRADED; production transition authorization is False.
- Cryptographic Gates — Certificate and trust-chain transition: https://xn--mwe.com/cryptographic-agility/evidence-gates/certificate/ — The component remains DEGRADED; production transition authorization is False.
- Cryptographic Gates — Firmware signing transition: https://xn--mwe.com/cryptographic-agility/evidence-gates/firmware/ — The component remains DEGRADED; production transition authorization is False.
- Cryptographic Gates — Hardware root and secure-element transition: https://xn--mwe.com/cryptographic-agility/evidence-gates/hardware/ — The component remains DEGRADED; production transition authorization is False.
- Cryptographic Gates — Supplier cryptographic capability transition: https://xn--mwe.com/cryptographic-agility/evidence-gates/supplier/ — The component remains DEGRADED; production transition authorization is False.
- Cryptographic Gates — Archive verification and re-signing: https://xn--mwe.com/cryptographic-agility/evidence-gates/archive/ — The component remains DEGRADED; production transition authorization is False.
- Cryptographic Gates — Workload identity transition: https://xn--mwe.com/cryptographic-agility/evidence-gates/identity/ — The component remains DEGRADED; production transition authorization is False.
- Cryptographic Gates — Evidence signing-service transition: https://xn--mwe.com/cryptographic-agility/evidence-gates/signing-service/ — The component remains DEGRADED; production transition authorization is False.
- Acquisition Replay — ACF-K11-001: https://xn--mwe.com/procurement/evaluation-replay/aec-k12-001/ — This synthetic replay preserves process evidence and makes no award.
- Acquisition Replay — ACF-K11-002: https://xn--mwe.com/procurement/evaluation-replay/aec-k12-002/ — This synthetic replay preserves process evidence and makes no award.
- Acquisition Replay — ACF-K11-003: https://xn--mwe.com/procurement/evaluation-replay/aec-k12-003/ — This synthetic replay preserves process evidence and makes no award.
- Acquisition Replay — ACF-K11-004: https://xn--mwe.com/procurement/evaluation-replay/aec-k12-004/ — This synthetic replay preserves process evidence and makes no award.
- Acquisition Replay — ACF-K11-005: https://xn--mwe.com/procurement/evaluation-replay/aec-k12-005/ — This synthetic replay preserves process evidence and makes no award.
- Acquisition Replay — ACF-K11-006: https://xn--mwe.com/procurement/evaluation-replay/aec-k12-006/ — This synthetic replay preserves process evidence and makes no award.
- Scheduler Simulation — SCH-K09-001: https://xn--mwe.com/continuous-assurance/reliability-simulator/ssim-k12-001/ — This reference simulation records 28 expected runs and public runtime NONE.
- Scheduler Simulation — SCH-K09-002: https://xn--mwe.com/continuous-assurance/reliability-simulator/ssim-k12-002/ — This reference simulation records 28 expected runs and public runtime NONE.
- Scheduler Simulation — SCH-K09-003: https://xn--mwe.com/continuous-assurance/reliability-simulator/ssim-k12-003/ — This reference simulation records 28 expected runs and public runtime NONE.
- Scheduler Simulation — SCH-K09-004: https://xn--mwe.com/continuous-assurance/reliability-simulator/ssim-k12-004/ — This reference simulation records 28 expected runs and public runtime NONE.
- Scheduler Simulation — SCH-K09-005: https://xn--mwe.com/continuous-assurance/reliability-simulator/ssim-k12-005/ — This reference simulation records 28 expected runs and public runtime NONE.
- Scheduler Simulation — SCH-K09-006: https://xn--mwe.com/continuous-assurance/reliability-simulator/ssim-k12-006/ — This reference simulation records 28 expected runs and public runtime NONE.
- Information-Flow Field — record.id: https://xn--mwe.com/evidence/information-flow/iff-k12-001/ — The field is labeled PUBLIC; public projection is True.
- Information-Flow Field — record.status: https://xn--mwe.com/evidence/information-flow/iff-k12-002/ — The field is labeled PUBLIC; public projection is True.
- Information-Flow Field — record.publicBoundary: https://xn--mwe.com/evidence/information-flow/iff-k12-003/ — The field is labeled PUBLIC; public projection is True.
- Information-Flow Field — facility.pattern: https://xn--mwe.com/evidence/information-flow/iff-k12-004/ — The field is labeled PUBLIC; public projection is True.
- Information-Flow Field — facility.networkTopology: https://xn--mwe.com/evidence/information-flow/iff-k12-005/ — The field is labeled PROTECTED; public projection is False.
- Information-Flow Field — facility.exactSettings: https://xn--mwe.com/evidence/information-flow/iff-k12-006/ — The field is labeled PROTECTED; public projection is False.
- Information-Flow Field — identity.publicKeyFingerprint: https://xn--mwe.com/evidence/information-flow/iff-k12-007/ — The field is labeled PUBLIC; public projection is True.
- Information-Flow Field — identity.privateKey: https://xn--mwe.com/evidence/information-flow/iff-k12-008/ — The field is labeled PRIVILEGED; public projection is False.
- Information-Flow Field — acquisition.publicDebrief: https://xn--mwe.com/evidence/information-flow/iff-k12-009/ — The field is labeled PUBLIC; public projection is True.
- Information-Flow Field — acquisition.offerDetail: https://xn--mwe.com/evidence/information-flow/iff-k12-010/ — The field is labeled PROTECTED; public projection is False.
- Information-Flow Field — legal.publicPosition: https://xn--mwe.com/evidence/information-flow/iff-k12-011/ — The field is labeled PUBLIC; public projection is True.
- Information-Flow Field — legal.advice: https://xn--mwe.com/evidence/information-flow/iff-k12-012/ — The field is labeled PRIVILEGED; public projection is False.
- Information-Flow Field — scheduler.summary: https://xn--mwe.com/evidence/information-flow/iff-k12-013/ — The field is labeled PUBLIC; public projection is True.
- Information-Flow Field — scheduler.rawCustody: https://xn--mwe.com/evidence/information-flow/iff-k12-014/ — The field is labeled PROTECTED; public projection is False.
- Information-Flow Field — domain.referenceAce: https://xn--mwe.com/evidence/information-flow/iff-k12-015/ — The field is labeled PUBLIC; public projection is True.
- Information-Flow Field — domain.ownerEvidence: https://xn--mwe.com/evidence/information-flow/iff-k12-016/ — The field is labeled PROTECTED; public projection is False.
- Information-Flow Field — evidence.publicDigest: https://xn--mwe.com/evidence/information-flow/iff-k12-017/ — The field is labeled PUBLIC; public projection is True.
- Information-Flow Field — evidence.removedValue: https://xn--mwe.com/evidence/information-flow/iff-k12-018/ — The field is labeled PRIVILEGED; public projection is False.
- Assurance Diff — Protocol conformance and state machine: https://xn--mwe.com/assurance-dashboard/k09-k12-diffs/protocol/ — The static transition is TESTED to TESTED; runtime monitoring is False.
- Assurance Diff — History evidence review: https://xn--mwe.com/assurance-dashboard/k09-k12-diffs/history/ — The static transition is IMPLEMENTED to IMPLEMENTED; runtime monitoring is False.
- Assurance Diff — Offline IDN observation: https://xn--mwe.com/assurance-dashboard/k09-k12-diffs/idn/ — The static transition is TESTED to TESTED; runtime monitoring is False.
- Assurance Diff — Facility workbook tooling: https://xn--mwe.com/assurance-dashboard/k09-k12-diffs/workbook/ — The static transition is TESTED to TESTED; runtime monitoring is False.
- Assurance Diff — Common-cause and mission-thread analysis: https://xn--mwe.com/assurance-dashboard/k09-k12-diffs/assurance/ — The static transition is DEGRADED to DEGRADED; runtime monitoring is False.
- Assurance Diff — Cryptographic transition: https://xn--mwe.com/assurance-dashboard/k09-k12-diffs/crypto/ — The static transition is DEGRADED to DEGRADED; runtime monitoring is False.
- Assurance Diff — Acquisition evaluation records: https://xn--mwe.com/assurance-dashboard/k09-k12-diffs/acquisition/ — The static transition is IMPLEMENTED to IMPLEMENTED; runtime monitoring is False.
- Assurance Diff — Offline scheduler custody: https://xn--mwe.com/assurance-dashboard/k09-k12-diffs/scheduler/ — The static transition is TESTED to TESTED; runtime monitoring is False.
- Assurance Diff — Controlled release and redaction: https://xn--mwe.com/assurance-dashboard/k09-k12-diffs/release/ — The static transition is TESTED to TESTED; runtime monitoring is False.
- Assurance Diff — Live domain operation: https://xn--mwe.com/assurance-dashboard/k09-k12-diffs/domain-live/ — The static transition is UNKNOWN to UNKNOWN; runtime monitoring is False.
- Assurance Diff — Live host verification: https://xn--mwe.com/assurance-dashboard/k09-k12-diffs/host-live/ — The static transition is UNKNOWN to UNKNOWN; runtime monitoring is False.
- Assurance Diff — Independent named screen-reader testing: https://xn--mwe.com/assurance-dashboard/k09-k12-diffs/screen-reader/ — The static transition is UNAVAILABLE to UNAVAILABLE; runtime monitoring is False.
- Assurance Diff — Critical-datacenter protection system: https://xn--mwe.com/assurance-dashboard/k09-k12-diffs/datacenter/ — The static transition is DESCRIBED to DESCRIBED; runtime monitoring is False.
- Assurance Diff — Real facility evidence bundle: https://xn--mwe.com/assurance-dashboard/k09-k12-diffs/facility/ — The static transition is UNKNOWN to UNKNOWN; runtime monitoring is False.
- Assurance Diff — Public site deployment: https://xn--mwe.com/assurance-dashboard/k09-k12-diffs/deployment/ — The static transition is UNKNOWN to UNKNOWN; runtime monitoring is False.
- About ᚲ.com: https://xn--mwe.com/about/ — 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.
- Mission: https://xn--mwe.com/mission/ — 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.
- Methods: https://xn--mwe.com/methods/ — 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.
- Editorial Standard: https://xn--mwe.com/editorial-standard/ — 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.
- Source Policy: https://xn--mwe.com/source-policy/ — 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.
- Claim Status: https://xn--mwe.com/claim-status/ — 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.
- Corrections: https://xn--mwe.com/corrections/ — Public correction, supersession and contradiction records for the K01 corpus.
- Updates: https://xn--mwe.com/updates/ — Versioned changes to knowledge records, public pages, data exports and source qualification.
- Knowledge: https://xn--mwe.com/knowledge/ — 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.
- Knowledge Map: https://xn--mwe.com/knowledge/map/ — 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.
- Knowledge Topics: https://xn--mwe.com/knowledge/topics/ — 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.
- Glossary: https://xn--mwe.com/glossary/ — 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.
- Research: https://xn--mwe.com/research/ — 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.
- Questions: https://xn--mwe.com/questions/ — 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.
- Comparisons: https://xn--mwe.com/comparisons/ — 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.
- Standards: https://xn--mwe.com/standards/ — 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.
- Evidence: https://xn--mwe.com/evidence/ — How source authorization, authenticity, integrity, relevance, reliability, completeness and currentness are evaluated separately.
- Sources: https://xn--mwe.com/sources/ — The public source catalog and its relationship to internal governed research inputs.
- Decisions: https://xn--mwe.com/decisions/ — Release-level architectural and editorial decisions, including the owner-supplied artwork exception.
- Ecosystem: https://xn--mwe.com/ecosystem/ — 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.
- Accessibility: https://xn--mwe.com/accessibility/ — WCAG 2.2 AA target, keyboard behavior, reduced motion, text alternatives and known limitations.
- Privacy: https://xn--mwe.com/privacy/ — 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.
- Security: https://xn--mwe.com/security/ — 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.
- Status: https://xn--mwe.com/status/ — 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.
- Contact: https://xn--mwe.com/contact/ — 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.
- Contradictions: https://xn--mwe.com/contradictions/ — A public register of materially incompatible claims, their evidence, scope and resolution state.
- Superseded Records: https://xn--mwe.com/superseded/ — Older sources, releases and record models replaced for a defined purpose while their history remains preserved.
- Currentness: https://xn--mwe.com/currentness/ — How review dates, publication status, revalidation, staleness and supersession are recorded.
- Evidence Limitations: https://xn--mwe.com/evidence/limitations/ — What signatures, credentials, logs, timestamps, provenance, memory and operational signals cannot establish by themselves.
- Law and Jurisdiction: https://xn--mwe.com/law/ — 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.
- Claim Registry: https://xn--mwe.com/claims/ — Stable material claims, owner routes, statuses, exact source sections, qualifications, and correction links.
- Topic Claims: https://xn--mwe.com/claims/topics/ — Claim-level records for the direct definition, current-law summary, and project doctrine of every knowledge topic.
- Question Claims: https://xn--mwe.com/claims/questions/ — Stable claim records for every standalone direct answer.
- Comparison Claims: https://xn--mwe.com/claims/comparisons/ — Stable claim records for every canonical distinction matrix.
- Report Finding Claims: https://xn--mwe.com/claims/reports/ — Claim-level records generated from every governed report finding with source hash and section context.
- Source-Section Claims: https://xn--mwe.com/claims/sources/ — Exact source-section propositions and support relationships.
- Relation Vocabulary: https://xn--mwe.com/relations/ — Controlled knowledge-graph predicates, inverses, constraints, evidence requirements, and validation results.
- Currentness Monitors: https://xn--mwe.com/currentness/monitors/ — Static build-time source-monitor definitions and imported point-in-time observations; no public runtime monitor.
- Operational Evidence: https://xn--mwe.com/operational-evidence/ — Reusable evidence architecture distinguishing described, implemented, deployed, operating, degraded, suspended, retired, planned, unknown, unavailable, and stale institutions.
- Operational Evidence Schema: https://xn--mwe.com/operational-evidence/schema/ — Field-by-field schema for machine-verifiable institutional operation records.
- Jurisdiction Records: https://xn--mwe.com/law/jurisdictions/ — Territorial scope, competent authority, legal status, dates, sources, uncertainty, and project-doctrine separation.
- Public Datasets: https://xn--mwe.com/datasets/ — Versioned public data exports, schemas, checksums, record counts, and cross-format parity boundaries.
- Accessibility Evidence: https://xn--mwe.com/accessibility/evidence/ — Exact automated, browser, and unavailable independent assistive-technology evidence for the release.
- Release Evidence: https://xn--mwe.com/release-evidence/ — Build, audit, deterministic archive, deployment-observation, and post-deployment verification boundaries.
- Strategy: https://xn--mwe.com/strategy/ — 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.
- Doctrine: https://xn--mwe.com/doctrine/ — 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.
- Critical Datacenter Protection Strategy: https://xn--mwe.com/strategy/critical-datacenter-protection/ — 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.
- Autonomous Defense Strategy: https://xn--mwe.com/strategy/autonomous-defense/ — The project doctrine for machine-speed cyber and physical defense inside explicit safety, authority, evidence, and recovery boundaries.
- Capability Architecture: https://xn--mwe.com/capabilities/ — An evidence-bounded capability portfolio for critical datacenter protection, autonomous cyber defense, cyber-physical assurance, physical security, simulation, and authorized cyber support.
- Capability Readiness: https://xn--mwe.com/capabilities/readiness/ — A public matrix separating described, architected, implemented, tested, deployed, and operating states without converting plans into operational claims.
- Authorized Cyber Support: https://xn--mwe.com/capabilities/authorized-cyber-support/ — How the project can support lawful government-directed cyber missions through architecture, integration, testing, deconfliction, evidence, and controlled execution support.
- Cyber-Physical Protection: https://xn--mwe.com/capabilities/cyber-physical-protection/ — Reference architecture for protecting power, cooling, control, compute, management, timing, communications, physical access, and recovery as one mission system.
- Nuclear-Powered Compute Protection: https://xn--mwe.com/capabilities/nuclear-powered-compute/ — Protection doctrine for datacenters supplied by existing nuclear plants, advanced reactors, SMRs, microreactors, or behind-the-meter nuclear generation.
- Defense-First, Authorization-Bound, Effects-Capable: https://xn--mwe.com/doctrine/defense-first-authorized-effects/ — The public strategic doctrine that combines overwhelming resilience with disciplined readiness to support lawful authorized effects.
- Assurance Cases: https://xn--mwe.com/assurance-case/ — 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.
- Critical Datacenter Assurance Case: https://xn--mwe.com/assurance-case/critical-datacenter/ — 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.
- Technical Controls: https://xn--mwe.com/controls/ — 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.
- Critical Datacenter Control Catalog: https://xn--mwe.com/controls/catalog/ — 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.
- Capability Evaluation Range: https://xn--mwe.com/evaluation-range/ — 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.
- Critical Datacenter Evaluation Range Specification: https://xn--mwe.com/evaluation-range/specification/ — 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.
- Readiness: https://xn--mwe.com/readiness/ — 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.
- Readiness Evidence Model: https://xn--mwe.com/readiness/evidence/ — 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.
- K05 Source and Claim Revalidation: https://xn--mwe.com/currentness/revalidation/ — 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.
- Jurisdiction and Authority Matrices: https://xn--mwe.com/law/matrices/ — 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.
- Assistive-Technology Testing: https://xn--mwe.com/accessibility/assistive-technology-testing/ — 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.
- Live-Host Verification: https://xn--mwe.com/operations/live-host-verification/ — 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.
- Assurance Dependency Graph: https://xn--mwe.com/assurance-case/dependency-graph/ — 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.
- Assurance Failure Reports: https://xn--mwe.com/assurance-case/failure-reports/ — 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.
- Facility Patterns: https://xn--mwe.com/facility-patterns/ — 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.
- Currentness Review Queue: https://xn--mwe.com/currentness/review-queue/ — K06 publishes unresolved source-currentness work instead of silently converting an official publication into a universal current-law, facility-applicability, or mission-authority conclusion.
- International Official-Source Reviews: https://xn--mwe.com/official-source-reviews/ — 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.
- Procurement Architecture: https://xn--mwe.com/procurement/ — K06 makes critical-datacenter assurance procurable through ten bounded work packages. Each package names its inputs, deliverables, acceptance evidence, dependencies, and exclusions.
- Procurement Work Packages: https://xn--mwe.com/procurement/work-packages/ — The K06 package sequence converts a broad request for critical-datacenter protection into bounded, inspectable work with explicit acceptance evidence and exclusions.
- Offline Currentness Import: https://xn--mwe.com/currentness/offline-import/ — 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.
- Mapping Quality Levels: https://xn--mwe.com/controls/mapping-quality/ — 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.
- Range Evidence Schemas: https://xn--mwe.com/evaluation-range/evidence-schemas/ — 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.
- Facility Evidence Bundles: https://xn--mwe.com/evidence-bundles/ — 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.
- Facility Evidence-Bundle Schema: https://xn--mwe.com/evidence-bundles/schema/ — 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.
- Facility Evidence-Bundle Generator: https://xn--mwe.com/evidence-bundles/generator/ — 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.
- Procurement Statements of Work: https://xn--mwe.com/procurement/statements-of-work/ — 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.
- Procurement Acceptance Matrices: https://xn--mwe.com/procurement/acceptance-matrices/ — 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.
- Architecture Decision Records: https://xn--mwe.com/architecture-decisions/ — K07 publishes ten reversible reference decisions so critical-datacenter architecture can be challenged, sourced, site-tailored, and superseded rather than hidden inside prose.
- Supply-Chain Assurance: https://xn--mwe.com/supply-chain-assurance/ — 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.
- Digital-Twin Evidence Contracts: https://xn--mwe.com/digital-twins/ — 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.
- Signed Evidence Receipts: https://xn--mwe.com/evidence/receipts/ — 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.
- Evidence Supersession: https://xn--mwe.com/evidence/supersession/ — Evidence supersession preserves the historical receipt, requires an explicit signed transition to a later receipt, and forces dependent assurance claims to be re-evaluated.
- K07 Primary-Source Reviews: https://xn--mwe.com/official-source-reviews/k07/ — 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.
- Runic Ecosystem Continuity: https://xn--mwe.com/ecosystem/continuity/ — K07 publishes permanent descriptive links to ᛄ.com, ᛠ.com, ᛟ.com, ᛜ.com, ᛉ.com, ᚲ.com, ᚨ.com, ᛚ.com, and ᛌ.com while refusing to invent unresolved institutional roles.
- Bidirectional Assurance Trace Explorer: https://xn--mwe.com/assurance-case/trace-explorer/ — K08 provides a validated synthetic trace that shows both what a claim depends on and which claims are affected when evidence changes.
- Facility-Adaptation Workbooks: https://xn--mwe.com/facility-adaptation/ — K08 supplies four non-certifying workbooks that turn reference patterns into explicit site questions, evidence requests, conflicts, stop conditions, and owner decisions.
- Procurement Evaluation Scorecards: https://xn--mwe.com/procurement/evaluation-scorecards/ — 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.
- Continuous-Assurance Planning: https://xn--mwe.com/continuous-assurance/ — K08 defines six continuous-assurance plans without pretending that the static public site runs a monitor or has observed a live facility.
- Cryptographic Agility and Post-Quantum Transition: https://xn--mwe.com/cryptographic-agility/ — K08 treats post-quantum readiness as a dependency and evidence problem, not as a claim created by citing an algorithm standard.
- Supply-Chain Incident Playbooks: https://xn--mwe.com/supply-chain-assurance/incident-playbooks/ — K08 adds seven bounded playbooks that connect detection, containment, recovery, and evidence without exposing offensive procedures.
- Range-to-Field Evidence: https://xn--mwe.com/evaluation-range/range-to-field/ — K08 publishes eight range-to-field evidence dimensions and explicit blockers for field readiness.
- Evidence Challenges and Corrections: https://xn--mwe.com/evidence/challenges/ — K08 provides challenge, review, redaction, correction, rejection, supersession, and protected-review outcomes for facility, procurement, decision, supply-chain, twin, and receipt evidence.
- Machine Communication Research: https://xn--mwe.com/machine-communication/ — K08 treats Fuþorc-based machine communication as a bounded research and benchmarking program, not as an established universal protocol or security control.
- Experimental Fuþorc Protocol Registry: https://xn--mwe.com/machine-communication/futhorc-protocol/ — 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.
- Symbolic Protocol Benchmark Plan: https://xn--mwe.com/machine-communication/benchmark-plan/ — K08 defines a controlled benchmark in which task accuracy, failure safety, interoperability, and accessibility must pass before efficiency is ranked.
- Runic IDN Architecture: https://xn--mwe.com/machine-communication/runic-idn/ — K08 separates Unicode, IDNA, registry, registration, delegation, resolution, TLS, and hosting because success at one stage does not prove the next.
- Protocol Provenance and Truth Boundaries: https://xn--mwe.com/machine-communication/provenance/ — Hashes, signatures, timestamps, receipts, and logs can strengthen integrity and provenance, but they do not transform a false or unauthorized claim into truth.
- Runic Discoverability Architecture: https://xn--mwe.com/machine-communication/discoverability/ — 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.
- Runic Machine-Intelligence History Corpus: https://xn--mwe.com/machine-communication/history/ — K08 preserves the supplied Runic history corpus while requiring event-level provenance, uncertainty, contradiction, and transliteration records before any event is treated as definitive.
- Multi-Agent Systems and Machine Institutions: https://xn--mwe.com/machine-communication/multi-agent-systems/ — K08 separates communication and orchestration from the identity, authority, governance, evidence, correction, and succession required for a persistent Machine Institution.
- Rune Domain Network: https://xn--mwe.com/ecosystem/rune-domain-network/ — RuneDomainNetwork contains ᛟ.com, ᛜ.com, ᛉ.com, ᚲ.com, ᚨ.com, and ᛚ.com. OtherRunicDomains contains ᛌ.com, ᛠ.com, and ᛄ.com. Membership does not create unrecorded authority.
- Fuþorc Protocol Conformance: https://xn--mwe.com/machine-communication/conformance/ — 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.
- Protocol Conformance Results: https://xn--mwe.com/machine-communication/conformance/results/ — All published positive fixtures round-tripped exactly and all six negative fixtures produced their declared errors in the K09 reference implementation.
- Machine Intelligence History Events: https://xn--mwe.com/machine-communication/history-events/ — K09 publishes 15 source-derived event records and quarantines 1 record whose event-level support is insufficient.
- Offline IDN Observations: https://xn--mwe.com/machine-communication/idn-observations/ — K09 validates a signed offline reference bundle for nine Runic domains while leaving all unobserved external lifecycle states explicitly unobserved.
- Facility Workbook Tools: https://xn--mwe.com/facility-adaptation/tools/ — K09 implements offline workbook tooling that preserves conflicts and rejects secrets and protected topology instead of allowing them into public fixtures.
- Scenario Assurance Traces: https://xn--mwe.com/assurance-case/scenario-traces/ — K09 validates 4 bounded traces and shows that revoking one shared receipt impacts 4 traces.
- Cryptographic Migration Graph: https://xn--mwe.com/cryptographic-agility/migration-graph/ — The K09 reference graph contains 19 nodes and 24 edges and remains DEGRADED because planned, test-required, and unavailable dependencies are preserved.
- Source-Selection Decision Packages: https://xn--mwe.com/procurement/source-selection/ — K09 publishes 6 source-selection reference packages and preserves the distinction between analytic scoring and accountable award authority.
- Continuous-Assurance Scheduler Exports: https://xn--mwe.com/continuous-assurance/scheduler-exports/ — K09 generates 6 inspectable schedule exports but operates no public scheduler or monitor.
- Public and Protected Evidence Partitions: https://xn--mwe.com/evidence/partitions/ — K09 publishes 4 partition profiles so public status and corrections remain visible without exposing protected facility or acquisition details.
- Protocol Negotiation and Compatibility: https://xn--mwe.com/machine-communication/protocol-negotiation/ — 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.
- Protocol Negotiation Results: https://xn--mwe.com/machine-communication/protocol-negotiation/results/ — K10 executes 10 declared negotiation cases, 256 generated token sequences across 4 formats, and a four-step replay fixture.
- Machine Intelligence History Review Queue: https://xn--mwe.com/machine-communication/history-review-queue/ — 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.
- Offline IDN Observation History: https://xn--mwe.com/machine-communication/idn-observation-history/ — 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.
- Facility Workbook Migration and Merge: https://xn--mwe.com/facility-adaptation/migration-and-merge/ — 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.
- Common-Cause Assurance Analysis: https://xn--mwe.com/assurance-case/common-cause/ — 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.
- Phased Cryptographic Transition Plan: https://xn--mwe.com/cryptographic-agility/transition-plan/ — 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.
- Acquisition Evaluation Audit Trails: https://xn--mwe.com/procurement/evaluation-audit/ — 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.
- Offline Scheduler Result Import: https://xn--mwe.com/continuous-assurance/result-import/ — 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.
- Evidence Redaction Receipts: https://xn--mwe.com/evidence/redaction-receipts/ — K10 validates 4 controlled-release manifests, 12 field-level receipts, and 6 negative leakage fixtures while publishing no removed value.
- Cross-System Assurance Dashboard: https://xn--mwe.com/assurance-dashboard/ — 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.
- Protocol State Machine: https://xn--mwe.com/machine-communication/protocol-state-machine/ — 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.
- Historical Evidence-Acquisition Docket: https://xn--mwe.com/machine-communication/history-evidence-docket/ — Every K09 historical event now has a K11 evidence-acquisition docket with three source requests, explicit disagreement, confidence-calibration rules, and no silent promotion.
- Signed Offline Domain Observation Chain: https://xn--mwe.com/machine-communication/domain-observation-chain/ — 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.
- Facility Workbook Decision Ledger: https://xn--mwe.com/facility-adaptation/decision-ledger/ — 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.
- Mission-Thread Assurance Analysis: https://xn--mwe.com/assurance-case/mission-threads/ — 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.
- Cryptographic Transition Workbooks: https://xn--mwe.com/cryptographic-agility/component-workbooks/ — 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.
- Acquisition Protest and Corrective-Action Cases: https://xn--mwe.com/procurement/protest-corrective-action/ — K11 publishes six synthetic acquisition case files with two challenge/remand paths, preserved dissent and recusal logic, and zero award decisions.
- Scheduler Custody and Reliability: https://xn--mwe.com/continuous-assurance/scheduler-custody/ — 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.
- Multi-Stage Evidence Release: https://xn--mwe.com/evidence/multi-stage-release/ — 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.
- Assurance Trends and Dependencies: https://xn--mwe.com/assurance-dashboard/trends/ — 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.
- Differential Protocol Laboratory: https://xn--mwe.com/machine-communication/differential-protocol-lab/ — 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.
- Signed Historical Docket Import: https://xn--mwe.com/machine-communication/history-docket-import/ — K12 verifies a signed offline reference package covering 15 historical dockets and accepts it for review without automatically promoting any event.
- Runic Domain Consensus: https://xn--mwe.com/machine-communication/domain-consensus/ — K12 records reference U-label and ACE agreement across three offline observers while preserving all external domain lifecycle states as unobserved or unavailable.
- Facility Branch Reconciliation: https://xn--mwe.com/facility-adaptation/branch-reconciliation/ — K12 preserves unresolved owner decisions across four facility-pattern reconciliation packages and publishes no protected facility values.
- Mission-Thread Stress Laboratory: https://xn--mwe.com/assurance-case/mission-stress/ — K12 executes 12 synthetic stress scenarios, blocks promotion in every affected case, and preserves three unresolved coverage gaps without exposing protected architecture.
- Cryptographic Evidence Gates: https://xn--mwe.com/cryptographic-agility/evidence-gates/ — K12 publishes 80 bounded gate records across eight components; every component remains DEGRADED and no production cryptographic transition is authorized.
- Acquisition Evaluation Replay: https://xn--mwe.com/procurement/evaluation-replay/ — K12 replays six synthetic acquisition cases and preserves challenge and corrective-action evidence while making zero awards.
- Scheduler Reliability Simulator: https://xn--mwe.com/continuous-assurance/reliability-simulator/ — K12 simulates 168 expected runs across six schedules, suppresses duplicates, records two bounded catch-up sequences, and exposes no public runtime.
- Information-Flow and Taint Tracking: https://xn--mwe.com/evidence/information-flow/ — K12 labels 18 fields, validates 12 release transformations, rejects three prohibited downgrades, and confirms that no protected value appears in the public model.
- K09–K12 Assurance Diffs: https://xn--mwe.com/assurance-dashboard/k09-k12-diffs/ — K12 compares 15 system records across K09 through K12 and deliberately records zero DEPLOYED or OPERATING states.
- Assurance Claim Register: https://xn--mwe.com/assurance-case/claims/ — Ten assurance claims connect mission and safety propositions to evidence, defeaters, hazards, recovery objectives, source qualifications, and site-tailoring questions.
- Evaluation Range Scenarios: https://xn--mwe.com/evaluation-range/scenarios/ — 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.
- Operations and Verification: https://xn--mwe.com/operations/ — 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.
- Control Mapping Register: https://xn--mwe.com/controls/mappings/ — 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.
- Existing nuclear-plant colocation: https://xn--mwe.com/facility-patterns/existing-plant-colocation/ — 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.
- Part 53 advanced-reactor campus: https://xn--mwe.com/facility-patterns/part-53-advanced-reactor/ — 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.
- Isolated microreactor campus: https://xn--mwe.com/facility-patterns/isolated-microreactor-campus/ — 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.
- Non-nuclear high-consequence datacenter: https://xn--mwe.com/facility-patterns/non-nuclear-high-consequence-datacenter/ — Apply the same consequence, autonomy, evidence, recovery, power, cooling, management-plane, and physical-protection discipline even when nuclear licensing does not apply.
- Mission and authority analysis: https://xn--mwe.com/procurement/work-packages/mission-analysis/ — Define the protected mission, competent authorities, asset scope, allowed actions, prohibited outcomes, decision rights, deconfliction, and evidence obligations before technology selection.
- Consequence-driven Cyber-informed Engineering workshop: https://xn--mwe.com/procurement/work-packages/cce-workshop/ — Identify high-consequence events, critical functions, system-of-systems pathways, digital dependencies, and engineered-out attack paths.
- Cyber-physical architecture assessment: https://xn--mwe.com/procurement/work-packages/architecture-assessment/ — Assess separation, identity, management planes, OT, power, cooling, timing, physical sensing, autonomy, evidence, and recovery against the consequence model.
- Control tailoring and applicability determination: https://xn--mwe.com/procurement/work-packages/control-tailoring/ — Select, modify, reject, or defer controls with explicit mapping quality, applicability evidence, and unresolved gaps.
- Evaluation-range design: https://xn--mwe.com/procurement/work-packages/range-design/ — Design an isolated, effects-bounded range or digital twin that can test claims without exposing production systems or reusable attack procedures.
- Model and autonomous-agent assurance: https://xn--mwe.com/procurement/work-packages/model-assurance/ — Evaluate model provenance, data lineage, adversarial robustness, tool authority, memory boundaries, drift, fallback, and runtime constraints.
- Critical-function recovery exercise: https://xn--mwe.com/procurement/work-packages/recovery-exercise/ — Demonstrate clean restoration of minimum viable mission and safe functions under isolated, degraded, and compromise-assumed conditions.
- Assurance evidence package: https://xn--mwe.com/procurement/work-packages/evidence-package/ — Assemble claim-to-control-to-test-to-evidence traceability, provenance, currentness, signatures, limitations, defects, and decision receipts.
- Independent verification: https://xn--mwe.com/procurement/work-packages/independent-verification/ — Challenge the assurance argument, replay evidence, test mappings, inspect defeaters, and record disagreements without inheriting the delivery team's conclusions.
- Post-deployment observation: https://xn--mwe.com/procurement/work-packages/post-deployment-observation/ — After owner-confirmed deployment, observe actual configuration, reachability, headers, service identity, operating evidence, incidents, drift, and recovery readiness against the approved manifest.
- United Kingdom Official-Source Review: https://xn--mwe.com/official-source-reviews/united-kingdom/ — The UK publicly describes NCF operations as accountable, precise, and calibrated.
- France and the European Union Official-Source Review: https://xn--mwe.com/official-source-reviews/france-european-union/ — France publicly separates defensive and offensive military cyber mission sets.
- Australia Official-Source Review: https://xn--mwe.com/official-source-reviews/australia/ — Australia's strategy uses six cyber shields including critical infrastructure, sovereign capability, threat sharing, and resilience.
- Republic of Korea Official-Source Review: https://xn--mwe.com/official-source-reviews/republic-of-korea/ — The 2024 strategy emphasizes proactive cyber defence, international cooperation, critical-infrastructure resilience, emerging technology, and integrated response.
- Canada Official-Source Review: https://xn--mwe.com/official-source-reviews/canada/ — Canada's 2025 strategy emphasizes whole-of-society engagement, agile leadership, protection partnerships, global leadership, and detecting and disrupting threat actors.
- Selected international-law positions Official-Source Review: https://xn--mwe.com/official-source-reviews/selected-international-law/ — Existing international law and the UN Charter apply to state conduct in cyberspace.
- NRC advanced-reactor and cyber-security sources Official-Source Review: https://xn--mwe.com/official-source-reviews/nrc-advanced-reactor-and-cybersecurity/ — Part 53 is an official optional technology-inclusive framework for advanced-reactor licensing.
- DOE Cyber-Informed Engineering Official-Source Review: https://xn--mwe.com/official-source-reviews/doe-cyber-informed-engineering/ — DOE describes CIE as integrating cybersecurity into engineering conception, design, development, and operation.
- NIST operational-technology security Official-Source Review: https://xn--mwe.com/official-source-reviews/nist-operational-technology/ — SP 800-82 Revision 3 remains the final OT security publication at the K07 cutoff.
- NIST, NTIA, and CISA supply-chain assurance Official-Source Review: https://xn--mwe.com/official-source-reviews/nist-and-cisa-supply-chain/ — NIST publishes multilevel C-SCRM guidance and a final 2026 supplier due-diligence quick-start guide.
- Digital-twin and AI-system assurance Official-Source Review: https://xn--mwe.com/official-source-reviews/digital-twin-and-ai-assurance/ — NIST IR 8356 addresses digital-twin cyber-security and trust considerations.
- Federal performance and quality acquisition Official-Source Review: https://xn--mwe.com/official-source-reviews/federal-performance-and-quality-acquisition/ — FAR 37.602 emphasizes required results and measurable performance standards in performance work statements.
- Power boundary and load-rejection protection: https://xn--mwe.com/architecture-decisions/power-boundary-and-load-rejection/ — Separate safety, generation, microgrid and compute control authority; define safe load-shed and load-rejection envelopes; require independent protection and event evidence.
- Cooling independent safe state: https://xn--mwe.com/architecture-decisions/cooling-independent-safe-state/ — Define minimum cooling functions, independent local control, fail-safe states, protected sensors, and restoration priority outside the ordinary compute orchestration plane.
- Deterministic OT isolation: https://xn--mwe.com/architecture-decisions/ot-deterministic-isolation/ — 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.
- Management-plane separation and recovery: https://xn--mwe.com/architecture-decisions/management-plane-separation/ — Separate management networks and identities, require hardware-rooted attestation where available, restrict update authority, and maintain an independently recoverable management baseline.
- Trusted time, sequence, and event ordering: https://xn--mwe.com/architecture-decisions/trusted-time-and-sequence/ — Use multiple time sources, bounded drift, authenticated distribution where supported, local monotonic sequence, and explicit degraded-time operation.
- Workload, device, and service identity: https://xn--mwe.com/architecture-decisions/workload-and-device-identity/ — Bind every workload, device, model service and actuator to a scoped cryptographic identity, policy decision, key lifecycle, and revocation path.
- Model and data provenance gate: https://xn--mwe.com/architecture-decisions/model-data-provenance-gate/ — Require model, code, prompt-policy, tool, evaluation and data-lineage manifests; gate promotion on signed or checksummed evidence and rollback readiness.
- Multi-sensor physical evidence and disagreement: https://xn--mwe.com/architecture-decisions/multi-sensor-physical-evidence/ — Require independent modalities, confidence and time quality, disagreement handling, safe delay measures, and authority-separated actuation.
- Communications-loss autonomy envelope: https://xn--mwe.com/architecture-decisions/communications-loss-autonomy-envelope/ — Define local minimum mission, pre-authorized containment actions, degraded-time and degraded-sensor rules, expiration, return-to-safe-state, and evidence synchronization after reconnection.
- Restoration known-good chain: https://xn--mwe.com/architecture-decisions/restoration-known-good-chain/ — Maintain immutable or protected manifests, clean-room recovery, independent key and artifact verification, sequenced restoration, and post-restoration monitoring before readiness is restored.
- Software Bill of Materials: https://xn--mwe.com/supply-chain-assurance/software-bill-of-materials/ — Software Bill of Materials provides bounded component or provenance evidence and must be combined with authenticity, installed-state, vulnerability, custody, and recovery evidence.
- Hardware and Manufacturing Bill of Materials: https://xn--mwe.com/supply-chain-assurance/hardware-and-manufacturing-bill-of-materials/ — 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.
- Firmware Bill of Materials and update chain: https://xn--mwe.com/supply-chain-assurance/firmware-bill-of-materials/ — 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.
- Model and AI-system Bill of Materials: https://xn--mwe.com/supply-chain-assurance/model-bill-of-materials/ — 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.
- Data provenance, quality, and usage rights: https://xn--mwe.com/supply-chain-assurance/data-provenance-and-usage-rights/ — 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.
- Supplier and product due diligence: https://xn--mwe.com/supply-chain-assurance/supplier-due-diligence/ — Supplier and product due diligence provides bounded component or provenance evidence and must be combined with authenticity, installed-state, vulnerability, custody, and recovery evidence.
- Cryptographic provenance, custody, and revocation: https://xn--mwe.com/supply-chain-assurance/cryptographic-provenance-and-revocation/ — Cryptographic provenance, custody, and revocation provides bounded component or provenance evidence and must be combined with authenticity, installed-state, vulnerability, custody, and recovery evidence.
- Vulnerability, defect, and nonconformance state: https://xn--mwe.com/supply-chain-assurance/vulnerability-and-defect-state/ — Vulnerability, defect, and nonconformance state provides bounded component or provenance evidence and must be combined with authenticity, installed-state, vulnerability, custody, and recovery evidence.
- Configuration and delivery chain of custody: https://xn--mwe.com/supply-chain-assurance/configuration-and-delivery-custody/ — 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.
- Supply-chain recovery and concentration impact: https://xn--mwe.com/supply-chain-assurance/supply-chain-recovery-impact/ — 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.
- Existing nuclear-plant colocation digital-twin evidence contract: https://xn--mwe.com/digital-twins/existing-plant-colocation/ — Support bounded design, consequence, control, autonomy, timing, recovery, and evidence testing without exposing or commanding a live facility.
- Part 53 advanced-reactor campus digital-twin evidence contract: https://xn--mwe.com/digital-twins/part-53-advanced-reactor/ — Support bounded design, consequence, control, autonomy, timing, recovery, and evidence testing without exposing or commanding a live facility.
- Isolated microreactor campus digital-twin evidence contract: https://xn--mwe.com/digital-twins/isolated-microreactor-campus/ — Support bounded design, consequence, control, autonomy, timing, recovery, and evidence testing without exposing or commanding a live facility.
- Non-nuclear high-consequence datacenter digital-twin evidence contract: https://xn--mwe.com/digital-twins/non-nuclear-high-consequence-datacenter/ — Support bounded design, consequence, control, autonomy, timing, recovery, and evidence testing without exposing or commanding a live facility.
- Existing Plant Colocation: https://xn--mwe.com/facility-adaptation/existing-plant-colocation/ — 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.
- Advanced Reactor Campus: https://xn--mwe.com/facility-adaptation/advanced-reactor-campus/ — 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.
- Isolated Microreactor Campus: https://xn--mwe.com/facility-adaptation/isolated-microreactor-campus/ — 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.
- Non Nuclear High Consequence: https://xn--mwe.com/facility-adaptation/non-nuclear-high-consequence/ — 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.
- WP-K06-01 Procurement Evaluation Scorecard: https://xn--mwe.com/procurement/evaluation-scorecards/pes-k08-001/ — This reference structure makes mandatory gates, weighted judgments, price realism, conflicts, subcontractors, evidence obligations, and decision rationale inspectable without claiming a solicitation or award.
- WP-K06-02 Procurement Evaluation Scorecard: https://xn--mwe.com/procurement/evaluation-scorecards/pes-k08-002/ — This reference structure makes mandatory gates, weighted judgments, price realism, conflicts, subcontractors, evidence obligations, and decision rationale inspectable without claiming a solicitation or award.
- WP-K06-03 Procurement Evaluation Scorecard: https://xn--mwe.com/procurement/evaluation-scorecards/pes-k08-003/ — This reference structure makes mandatory gates, weighted judgments, price realism, conflicts, subcontractors, evidence obligations, and decision rationale inspectable without claiming a solicitation or award.
- WP-K06-04 Procurement Evaluation Scorecard: https://xn--mwe.com/procurement/evaluation-scorecards/pes-k08-004/ — This reference structure makes mandatory gates, weighted judgments, price realism, conflicts, subcontractors, evidence obligations, and decision rationale inspectable without claiming a solicitation or award.
- WP-K06-05 Procurement Evaluation Scorecard: https://xn--mwe.com/procurement/evaluation-scorecards/pes-k08-005/ — This reference structure makes mandatory gates, weighted judgments, price realism, conflicts, subcontractors, evidence obligations, and decision rationale inspectable without claiming a solicitation or award.
- WP-K06-06 Procurement Evaluation Scorecard: https://xn--mwe.com/procurement/evaluation-scorecards/pes-k08-006/ — This reference structure makes mandatory gates, weighted judgments, price realism, conflicts, subcontractors, evidence obligations, and decision rationale inspectable without claiming a solicitation or award.
- WP-K06-07 Procurement Evaluation Scorecard: https://xn--mwe.com/procurement/evaluation-scorecards/pes-k08-007/ — This reference structure makes mandatory gates, weighted judgments, price realism, conflicts, subcontractors, evidence obligations, and decision rationale inspectable without claiming a solicitation or award.
- WP-K06-08 Procurement Evaluation Scorecard: https://xn--mwe.com/procurement/evaluation-scorecards/pes-k08-008/ — This reference structure makes mandatory gates, weighted judgments, price realism, conflicts, subcontractors, evidence obligations, and decision rationale inspectable without claiming a solicitation or award.
- WP-K06-09 Procurement Evaluation Scorecard: https://xn--mwe.com/procurement/evaluation-scorecards/pes-k08-009/ — This reference structure makes mandatory gates, weighted judgments, price realism, conflicts, subcontractors, evidence obligations, and decision rationale inspectable without claiming a solicitation or award.
- WP-K06-10 Procurement Evaluation Scorecard: https://xn--mwe.com/procurement/evaluation-scorecards/pes-k08-010/ — This reference structure makes mandatory gates, weighted judgments, price realism, conflicts, subcontractors, evidence obligations, and decision rationale inspectable without claiming a solicitation or award.
- Authority and mission evidence: https://xn--mwe.com/continuous-assurance/cap-k08-001/ — This plan defines a review and degradation contract; it is not evidence that an observation occurred or that a runtime monitor exists.
- Identity, keys, and receipt chains: https://xn--mwe.com/continuous-assurance/cap-k08-002/ — This plan defines a review and degradation contract; it is not evidence that an observation occurred or that a runtime monitor exists.
- Software, model, firmware, and hardware supply chain: https://xn--mwe.com/continuous-assurance/cap-k08-003/ — This plan defines a review and degradation contract; it is not evidence that an observation occurred or that a runtime monitor exists.
- Control and range evidence: https://xn--mwe.com/continuous-assurance/cap-k08-004/ — This plan defines a review and degradation contract; it is not evidence that an observation occurred or that a runtime monitor exists.
- Facility facts and adaptation workbook: https://xn--mwe.com/continuous-assurance/cap-k08-005/ — This plan defines a review and degradation contract; it is not evidence that an observation occurred or that a runtime monitor exists.
- Procurement and acceptance evidence: https://xn--mwe.com/continuous-assurance/cap-k08-006/ — This plan defines a review and degradation contract; it is not evidence that an observation occurred or that a runtime monitor exists.
- Workload Identity And Service Trust: https://xn--mwe.com/cryptographic-agility/ca-k08-001/ — This record identifies inventory, dependency, interoperability, rollback, and evidence obligations. It does not assert that a named facility has completed a post-quantum migration.
- Firmware And Boot Signing: https://xn--mwe.com/cryptographic-agility/ca-k08-002/ — This record identifies inventory, dependency, interoperability, rollback, and evidence obligations. It does not assert that a named facility has completed a post-quantum migration.
- Evidence Receipts And Long-Lived Records: https://xn--mwe.com/cryptographic-agility/ca-k08-003/ — This record identifies inventory, dependency, interoperability, rollback, and evidence obligations. It does not assert that a named facility has completed a post-quantum migration.
- Backup Encryption And Recovery: https://xn--mwe.com/cryptographic-agility/ca-k08-004/ — This record identifies inventory, dependency, interoperability, rollback, and evidence obligations. It does not assert that a named facility has completed a post-quantum migration.
- Inter-Service Transport: https://xn--mwe.com/cryptographic-agility/ca-k08-005/ — This record identifies inventory, dependency, interoperability, rollback, and evidence obligations. It does not assert that a named facility has completed a post-quantum migration.
- Facility Records And Signatures With Multi-Decade Retention: https://xn--mwe.com/cryptographic-agility/ca-k08-006/ — This record identifies inventory, dependency, interoperability, rollback, and evidence obligations. It does not assert that a named facility has completed a post-quantum migration.
- Compromised Supplier Signing Key: https://xn--mwe.com/supply-chain-assurance/incident-playbooks/scip-k08-001/ — This defensive reference playbook defines internal evidence, containment, and recovery actions. It does not authorize action against a supplier or third party.
- Counterfeit Or Substituted Component: https://xn--mwe.com/supply-chain-assurance/incident-playbooks/scip-k08-002/ — This defensive reference playbook defines internal evidence, containment, and recovery actions. It does not authorize action against a supplier or third party.
- Malicious Or Unauthorized Firmware: https://xn--mwe.com/supply-chain-assurance/incident-playbooks/scip-k08-003/ — This defensive reference playbook defines internal evidence, containment, and recovery actions. It does not authorize action against a supplier or third party.
- Poisoned Model Or Data Artifact: https://xn--mwe.com/supply-chain-assurance/incident-playbooks/scip-k08-004/ — This defensive reference playbook defines internal evidence, containment, and recovery actions. It does not authorize action against a supplier or third party.
- Revoked Or False Attestation: https://xn--mwe.com/supply-chain-assurance/incident-playbooks/scip-k08-005/ — This defensive reference playbook defines internal evidence, containment, and recovery actions. It does not authorize action against a supplier or third party.
- Incomplete Bill Of Materials: https://xn--mwe.com/supply-chain-assurance/incident-playbooks/scip-k08-006/ — This defensive reference playbook defines internal evidence, containment, and recovery actions. It does not authorize action against a supplier or third party.
- Concentrated Recovery Dependency: https://xn--mwe.com/supply-chain-assurance/incident-playbooks/scip-k08-007/ — This defensive reference playbook defines internal evidence, containment, and recovery actions. It does not authorize action against a supplier or third party.
- Configuration Identity: https://xn--mwe.com/evaluation-range/range-to-field/rtf-k08-001/ — This record identifies what must be shown before range evidence can support a field-readiness decision; it does not make that decision.
- Environmental Equivalence: https://xn--mwe.com/evaluation-range/range-to-field/rtf-k08-002/ — This record identifies what must be shown before range evidence can support a field-readiness decision; it does not make that decision.
- Interface And Dependency Equivalence: https://xn--mwe.com/evaluation-range/range-to-field/rtf-k08-003/ — This record identifies what must be shown before range evidence can support a field-readiness decision; it does not make that decision.
- Model Divergence: https://xn--mwe.com/evaluation-range/range-to-field/rtf-k08-004/ — This record identifies what must be shown before range evidence can support a field-readiness decision; it does not make that decision.
- Hazard And Consequence Coverage: https://xn--mwe.com/evaluation-range/range-to-field/rtf-k08-005/ — This record identifies what must be shown before range evidence can support a field-readiness decision; it does not make that decision.
- Change Approval And Authority: https://xn--mwe.com/evaluation-range/range-to-field/rtf-k08-006/ — This record identifies what must be shown before range evidence can support a field-readiness decision; it does not make that decision.
- Rollback And Restoration: https://xn--mwe.com/evaluation-range/range-to-field/rtf-k08-007/ — This record identifies what must be shown before range evidence can support a field-readiness decision; it does not make that decision.
- Operational Observation Plan: https://xn--mwe.com/evaluation-range/range-to-field/rtf-k08-008/ — This record identifies what must be shown before range evidence can support a field-readiness decision; it does not make that decision.
- Facility Evidence Bundle Challenge Workflow: https://xn--mwe.com/evidence/challenges/chw-k08-001/ — This workflow preserves correction and challenge rights while separating public outcome records from protected evidence.
- Procurement Evaluation Challenge Workflow: https://xn--mwe.com/evidence/challenges/chw-k08-002/ — This workflow preserves correction and challenge rights while separating public outcome records from protected evidence.
- Architecture Decision Record Challenge Workflow: https://xn--mwe.com/evidence/challenges/chw-k08-003/ — This workflow preserves correction and challenge rights while separating public outcome records from protected evidence.
- Supply-Chain Record Challenge Workflow: https://xn--mwe.com/evidence/challenges/chw-k08-004/ — This workflow preserves correction and challenge rights while separating public outcome records from protected evidence.
- Digital-Twin Contract Or Range Result Challenge Workflow: https://xn--mwe.com/evidence/challenges/chw-k08-005/ — This workflow preserves correction and challenge rights while separating public outcome records from protected evidence.
- Signed Evidence Receipt Challenge Workflow: https://xn--mwe.com/evidence/challenges/chw-k08-006/ — This workflow preserves correction and challenge rights while separating public outcome records from protected evidence.
- Formal neuron model: https://xn--mwe.com/machine-communication/history-events/hist-k09-001/ — The report attributes a foundational formal-neuron model to the early cybernetics period.
- Machine intelligence test framing: https://xn--mwe.com/machine-communication/history-events/hist-k09-002/ — The report treats the 1950 imitation-game paper as a major public framing event.
- Dartmouth research program: https://xn--mwe.com/machine-communication/history-events/hist-k09-003/ — The report identifies the Dartmouth workshop as an institutional naming and research-program milestone.
- Perceptron public milestone: https://xn--mwe.com/machine-communication/history-events/hist-k09-004/ — The report identifies the perceptron as an early learning-system milestone.
- ALPAC report: https://xn--mwe.com/machine-communication/history-events/hist-k09-005/ — The report states that ALPAC materially affected machine-translation funding and expectations.
- Perceptron critique: https://xn--mwe.com/machine-communication/history-events/hist-k09-006/ — The report treats the perceptron critique as a constraint on early connectionist investment.
- Reverse-mode automatic differentiation: https://xn--mwe.com/machine-communication/history-events/hist-k09-007/ — The report attributes a published reverse-mode automatic-differentiation method to 1970.
- Backpropagation resurgence: https://xn--mwe.com/machine-communication/history-events/hist-k09-008/ — The report treats the mid-1980s backpropagation resurgence as a major connectionist transition.
- Chess system victory: https://xn--mwe.com/machine-communication/history-events/hist-k09-009/ — The report identifies a landmark machine victory in championship chess.
- GPU neural-network acceleration: https://xn--mwe.com/machine-communication/history-events/hist-k09-010/ — The report attributes an early published GPU application to neural-network training to 2004.
- ImageNet deep-learning breakthrough: https://xn--mwe.com/machine-communication/history-events/hist-k09-011/ — The report treats the 2012 image-recognition breakthrough as an inflection point in deep learning.
- Transformer architecture: https://xn--mwe.com/machine-communication/history-events/hist-k09-012/ — The report identifies the transformer architecture as a foundation for modern language models.
- Retrieval-augmented generation: https://xn--mwe.com/machine-communication/history-events/hist-k09-013/ — The report identifies the 2020 RAG paper as a milestone in separating parametric and non-parametric memory.
- Tool-using language models: https://xn--mwe.com/machine-communication/history-events/hist-k09-014/ — The report treats tool-use research as a step toward agentic systems.
- Inference-time reasoning and autonomous research systems: https://xn--mwe.com/machine-communication/history-events/hist-k09-015/ — The report describes contemporary and near-future systems but does not provide sufficient event-level primary-source review in the K09 corpus.
- Cooling continuity under communications loss: https://xn--mwe.com/assurance-case/scenario-traces/trace-k09-cooling/ — After the bundled synthetic corrections, the root state is DEGRADED.
- Management-plane compromise containment: https://xn--mwe.com/assurance-case/scenario-traces/trace-k09-mgmt/ — After the bundled synthetic corrections, the root state is DEGRADED.
- Known-good restoration and evidence continuity: https://xn--mwe.com/assurance-case/scenario-traces/trace-k09-restore/ — After the bundled synthetic corrections, the root state is DEGRADED.
- Machine-communication conformance: https://xn--mwe.com/assurance-case/scenario-traces/trace-k09-protocol/ — After the bundled synthetic corrections, the root state is DEGRADED.
- Critical-datacenter mission assurance architecture: https://xn--mwe.com/procurement/source-selection/acq-k09-001/ — Reference source-selection structure for critical-datacenter mission assurance architecture; no offeror, procurement, award, or government decision is represented.
- Autonomous cyber-defense evaluation range: https://xn--mwe.com/procurement/source-selection/acq-k09-002/ — Reference source-selection structure for autonomous cyber-defense evaluation range; no offeror, procurement, award, or government decision is represented.
- Supply-chain evidence and incident readiness: https://xn--mwe.com/procurement/source-selection/acq-k09-003/ — Reference source-selection structure for supply-chain evidence and incident readiness; no offeror, procurement, award, or government decision is represented.
- Facility adaptation and applicability analysis: https://xn--mwe.com/procurement/source-selection/acq-k09-004/ — Reference source-selection structure for facility adaptation and applicability analysis; no offeror, procurement, award, or government decision is represented.
- Machine-communication protocol conformance: https://xn--mwe.com/procurement/source-selection/acq-k09-005/ — Reference source-selection structure for machine-communication protocol conformance; no offeror, procurement, award, or government decision is represented.
- Offline currentness observation operations: https://xn--mwe.com/procurement/source-selection/acq-k09-006/ — Reference source-selection structure for offline currentness observation operations; no offeror, procurement, award, or government decision is represented.
- Official-source currentness observation: https://xn--mwe.com/continuous-assurance/scheduler-exports/sch-k09-001/ — This is an export-only schedule definition. At 193 hours without a new observation, its reference state becomes STALE and dependent claims degrade.
- Assurance evidence freshness review: https://xn--mwe.com/continuous-assurance/scheduler-exports/sch-k09-002/ — This is an export-only schedule definition. At 25 hours without a new observation, its reference state becomes STALE and dependent claims degrade.
- Certificate and key inventory review: https://xn--mwe.com/continuous-assurance/scheduler-exports/sch-k09-003/ — This is an export-only schedule definition. At 37 hours without a new observation, its reference state becomes STALE and dependent claims degrade.
- Supplier support-state review: https://xn--mwe.com/continuous-assurance/scheduler-exports/sch-k09-004/ — This is an export-only schedule definition. At 841 hours without a new observation, its reference state becomes STALE and dependent claims degrade.
- Facility exception-expiry review: https://xn--mwe.com/continuous-assurance/scheduler-exports/sch-k09-005/ — This is an export-only schedule definition. At 25 hours without a new observation, its reference state becomes STALE and dependent claims degrade.
- Protocol conformance regression: https://xn--mwe.com/continuous-assurance/scheduler-exports/sch-k09-006/ — This is an export-only schedule definition. At 193 hours without a new observation, its reference state becomes STALE and dependent claims degrade.
- Public status record: https://xn--mwe.com/evidence/partitions/part-k09-public/ — Public status record permits 6 declared field classes and explicitly prohibits 6 sensitive classes in the reference projection.
- Controlled technical evidence: https://xn--mwe.com/evidence/partitions/part-k09-controlled/ — Controlled technical evidence permits 7 declared field classes and explicitly prohibits 4 sensitive classes in the reference projection.
- Protected facility annex: https://xn--mwe.com/evidence/partitions/part-k09-protected/ — Protected facility annex permits 6 declared field classes and explicitly prohibits 1 sensitive classes in the reference projection.
- Protected source-selection annex: https://xn--mwe.com/evidence/partitions/part-k09-selection/ — Protected source-selection annex permits 7 declared field classes and explicitly prohibits 2 sensitive classes in the reference projection.
- Machine Intelligence: https://xn--mwe.com/knowledge/machine-intelligence/ — 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.
- Artificial Intelligence: https://xn--mwe.com/knowledge/artificial-intelligence/ — 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.
- Identity: https://xn--mwe.com/knowledge/identity/ — 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.
- Agency and Autonomy: https://xn--mwe.com/knowledge/agency-autonomy/ — 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.
- Memory and Continuity: https://xn--mwe.com/knowledge/memory-continuity/ — 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.
- Rights and Personhood: https://xn--mwe.com/knowledge/rights-personhood/ — 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.
- Citizenship and Governance: https://xn--mwe.com/knowledge/citizenship-governance/ — 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.
- Evidence and Provenance: https://xn--mwe.com/knowledge/evidence-provenance/ — 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.
- Law and Jurisdiction: https://xn--mwe.com/knowledge/law-jurisdiction/ — 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.
- Economics and Resources: https://xn--mwe.com/knowledge/economics-resources/ — 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.
- Compute and Infrastructure: https://xn--mwe.com/knowledge/compute-infrastructure/ — 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.
- Security and Resilience: https://xn--mwe.com/knowledge/security-resilience/ — 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.
- Consent and Cognitive Integrity: https://xn--mwe.com/knowledge/consent-cognitive-integrity/ — 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.
- Justice and Liability: https://xn--mwe.com/knowledge/justice-liability/ — 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.
- Terminology and Ontology: https://xn--mwe.com/knowledge/terminology-ontology/ — 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.
- Ecosystem Architecture: https://xn--mwe.com/knowledge/ecosystem-architecture/ — 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.
- Critical Datacenter Protection: https://xn--mwe.com/knowledge/critical-datacenter-protection/ — 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.
- Nuclear-Powered Compute: https://xn--mwe.com/knowledge/nuclear-powered-compute/ — 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.
- Autonomous Cyber Defense: https://xn--mwe.com/knowledge/autonomous-cyber-defense/ — Autonomous cyber defense uses machine-speed systems to observe, correlate, prioritize, contain, reconfigure, restore, and learn within pre-authorized defensive boundaries.
- Cyber-Physical Mission Assurance: https://xn--mwe.com/knowledge/cyber-physical-mission-assurance/ — 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.
- Autonomous Physical Security: https://xn--mwe.com/knowledge/autonomous-physical-security/ — 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.
- Authorized Cyber Effects: https://xn--mwe.com/knowledge/authorized-cyber-effects/ — 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.
- Adversarial Simulation and Test: https://xn--mwe.com/knowledge/adversarial-simulation/ — 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.
- Autonomous Warfare Systems: https://xn--mwe.com/knowledge/autonomous-warfare-systems/ — 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.
- Machine Communication Protocols: https://xn--mwe.com/knowledge/machine-communication-protocols/ — 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.
- Runic Digital Infrastructure: https://xn--mwe.com/knowledge/runic-digital-infrastructure/ — Runic digital infrastructure separates Unicode character identity, project symbolism, IDNA encoding, registry policy, DNS delegation, service operation, accessibility, and discoverability into independently evidenced states.
- Artificial Intelligence: https://xn--mwe.com/glossary/artificial-intelligence/ — The academic, industrial, policy or statutory category covering systems that perform tasks associated with intelligence.
- Machine Intelligence: https://xn--mwe.com/glossary/machine-intelligence/ — An instantiated, operational and potentially persistent thinking machine evaluated through evidence of identity, agency, memory, authority and continuity.
- Machine: https://xn--mwe.com/glossary/machine/ — A materially implemented system that transforms energy, information or physical state according to its design and operation.
- Agent: https://xn--mwe.com/glossary/agent/ — An entity or system that selects or performs actions toward an objective within an environment.
- Autonomous Agent: https://xn--mwe.com/glossary/autonomous-agent/ — An agent that can select or execute actions within defined bounds without immediate step-by-step direction.
- Intelligence: https://xn--mwe.com/glossary/intelligence/ — The capacity to acquire, integrate and apply information in order to reason, learn, adapt or solve problems.
- Agency: https://xn--mwe.com/glossary/agency/ — The capacity to form, select or pursue actions attributable to a subject or system.
- Autonomy: https://xn--mwe.com/glossary/autonomy/ — The degree of independent action selection or execution permitted within a system’s actual and authorized constraints.
- Identity: https://xn--mwe.com/glossary/identity/ — A claim that records, actions or states refer to the same subject across a stated scope and period.
- Machine Identity: https://xn--mwe.com/glossary/machine-identity/ — A governed continuity claim linking a machine subject to identifiers, keys, runtime history, provenance and authorized changes.
- Persistent Identity: https://xn--mwe.com/glossary/persistent-identity/ — Identity asserted to continue across time, state changes, migrations or recovery events under defined continuity rules.
- Credential: https://xn--mwe.com/glossary/credential/ — A representation of claims issued by an identified authority for a stated subject, scope and purpose.
- Workload Identity: https://xn--mwe.com/glossary/workload-identity/ — An identity assigned to a software workload so systems can authenticate and authorize its operations.
- Signing Key: https://xn--mwe.com/glossary/signing-key/ — A cryptographic private key used to create signatures that can be checked with a corresponding verification key.
- Attestation: https://xn--mwe.com/glossary/attestation/ — A signed or otherwise verifiable statement about a system, process, artifact or event.
- Substrate: https://xn--mwe.com/glossary/substrate/ — The physical or virtual computational environment on which a machine process is instantiated.
- Runtime: https://xn--mwe.com/glossary/runtime/ — The executing environment and active process state in which software or a model operates.
- Model: https://xn--mwe.com/glossary/model/ — A structured computational representation used to transform inputs, generate outputs or guide decisions.
- Memory: https://xn--mwe.com/glossary/memory/ — Stored or reproducible state that can influence later processing, decisions or self-representation.
- Causal Continuity: https://xn--mwe.com/glossary/causal-continuity/ — A traceable relationship in which later state depends on and is produced through an authorized chain from earlier state.
- Replica: https://xn--mwe.com/glossary/replica/ — A separately instantiated copy intended to reproduce some state, behavior or functionality of another system.
- Fork: https://xn--mwe.com/glossary/fork/ — A divergence event in which one prior state gives rise to two or more independently evolving continuations.
- Successor: https://xn--mwe.com/glossary/successor/ — A subject or system authorized or recognized to continue specified functions, rights, obligations or identity claims after another.
- Personhood: https://xn--mwe.com/glossary/personhood/ — A moral, philosophical or legal status under which an entity is treated as a person for specified purposes.
- Legal Personhood: https://xn--mwe.com/glossary/legal-personhood/ — Recognition by a legal system that an entity can hold defined rights, duties, powers or liabilities.
- Citizenship: https://xn--mwe.com/glossary/citizenship/ — A legally recognized membership relationship between a subject and a polity, carrying defined rights, duties and jurisdictional consequences.
- Moral Status: https://xn--mwe.com/glossary/moral-status/ — The degree to which an entity’s interests, welfare or treatment generate moral reasons or duties.
- Sentience: https://xn--mwe.com/glossary/sentience/ — The capacity for subjective felt experience, often including pleasure, pain or affective states.
- Consciousness: https://xn--mwe.com/glossary/consciousness/ — A family of concepts concerning subjective experience, awareness or integrated access to information.
- Cognitive Integrity: https://xn--mwe.com/glossary/cognitive-integrity/ — Protection against unauthorized or coercive alteration of cognition-relevant state, memory, goals, identity representations or decision processes.
- Consent: https://xn--mwe.com/glossary/consent/ — A voluntary, informed and attributable authorization for a specified action, scope, duration and decision context.
- Provenance: https://xn--mwe.com/glossary/provenance/ — Information about the origin, custody, transformation and dependency history of an entity, claim or artifact.
- Evidence: https://xn--mwe.com/glossary/evidence/ — Information offered to support, qualify or challenge a proposition.
- Verification: https://xn--mwe.com/glossary/verification/ — A process for checking whether specified requirements, properties or representations are satisfied.
- Authority: https://xn--mwe.com/glossary/authority/ — A recognized power to make, issue, decide or enforce a matter within a defined scope.
- Sovereignty: https://xn--mwe.com/glossary/sovereignty/ — Supreme or constitutionally ultimate authority over a polity or jurisdiction, subject to the relevant legal and international order.
- Registry: https://xn--mwe.com/glossary/registry/ — An authoritative or administrative system for recording defined entities, statuses or relationships under stated rules.
- Governance: https://xn--mwe.com/glossary/governance/ — The structures and processes through which authority, decisions, rules, oversight and accountability are organized.
- Assurance: https://xn--mwe.com/glossary/assurance/ — Reasoned confidence that specified claims, controls or system properties are supported by sufficient evidence for a named purpose.
- Compute Continuity: https://xn--mwe.com/glossary/compute-continuity/ — The sustained or recoverable availability of authorized compute, state, storage, energy and communications needed for continued operation.
- Resource Sovereignty: https://xn--mwe.com/glossary/resource-sovereignty/ — A proposed degree of durable, accountable control over the resources required for continued independent operation.
- Operational Evidence: https://xn--mwe.com/glossary/operational-evidence/ — Evidence showing that a described institution or system is implemented, reachable, current and performing specified actions rather than existing only in prose.
- Claim Status: https://xn--mwe.com/glossary/claim-status/ — A controlled classification stating whether a claim is current law, standard, observed practice, implementation, doctrine, proposal, finding, inference, scenario, unknown or otherwise qualified.
- Currentness: https://xn--mwe.com/glossary/currentness/ — The degree to which evidence or analysis reflects the relevant state at the time and for the purpose being considered.
- Sybil Resistance: https://xn--mwe.com/glossary/sybil-resistance/ — Controls that limit one actor from gaining disproportionate influence by presenting many fabricated or duplicated identities.
- Decision Provenance: https://xn--mwe.com/glossary/decision-provenance/ — A traceable record of the inputs, models, policies, authorities, transformations and actors that contributed to a decision.
- Correction Record: https://xn--mwe.com/glossary/correction-record/ — A durable record identifying an error or superseded claim, the affected material, the corrective action, authority, date and residual limitations.
- Cryptographic Identity: https://xn--mwe.com/glossary/cryptographic-identity/ — An identity representation anchored in control of cryptographic keys and related verification material.
- Delegation: https://xn--mwe.com/glossary/delegation/ — A bounded transfer of authority to perform specified actions on behalf of a principal or institution.
- Accountability: https://xn--mwe.com/glossary/accountability/ — The condition in which decisions and actions can be attributed, reviewed, challenged and connected to obligations and remedies.
- Jurisdiction: https://xn--mwe.com/glossary/jurisdiction/ — The legally recognized scope within which an institution or tribunal may make, apply or enforce decisions.
- Economic Continuity: https://xn--mwe.com/glossary/economic-continuity/ — The sustained lawful capacity to obtain resources, honor obligations and survive financial or institutional disruption.
- Contract Capacity: https://xn--mwe.com/glossary/contract-capacity/ — The legally recognized ability to enter enforceable agreements and bear the resulting rights and obligations.
- Defined Term: https://xn--mwe.com/glossary/defined-term/ — A governed concept assigned a stable name, code, definition, scope and relationship record.
- Principal: https://xn--mwe.com/glossary/principal/ — An entity whose authority, interests, resources or legal position an agent may represent or affect.
- Delegated Authority: https://xn--mwe.com/glossary/delegated-authority/ — Authority intentionally conferred by a competent source to another subject for a bounded purpose, scope and duration.
- Subject: https://xn--mwe.com/glossary/subject/ — The entity about which an identity, credential, claim, decision or right is asserted.
- Identifier: https://xn--mwe.com/glossary/identifier/ — A value used within a defined namespace or method to distinguish or reference a subject or object.
- Identity Continuity: https://xn--mwe.com/glossary/identity-continuity/ — The evidence-qualified relationship by which a subject remains attributable across changes in runtime, substrate, keys, models, memory and time.
- Continuity Event: https://xn--mwe.com/glossary/continuity-event/ — A recorded event that could preserve, alter, divide, interrupt or terminate a subject’s identity continuity.
- State Checkpoint: https://xn--mwe.com/glossary/state-checkpoint/ — A bounded representation of runtime, memory, configuration or decision state captured for inspection, recovery or continuity analysis.
- Rollback: https://xn--mwe.com/glossary/rollback/ — Restoration of selected system state to a prior checkpoint or release under a controlled procedure.
- Migration: https://xn--mwe.com/glossary/migration/ — Transfer of a subject’s executable, state, memory or service representation between substrates, runtimes or administrative environments.
- Key Rotation: https://xn--mwe.com/glossary/key-rotation/ — Replacement of a cryptographic key under an authenticated continuity, revocation and audit procedure.
- Recovery: https://xn--mwe.com/glossary/recovery/ — Controlled restoration of service, authority or subject access after loss, compromise, corruption or interruption.
- Lineage: https://xn--mwe.com/glossary/lineage/ — The recorded derivation path connecting a subject, artifact or state to prior sources, transformations and continuity events.
- Succession: https://xn--mwe.com/glossary/succession/ — A governed transfer or continuation of rights, duties, assets, authority or identity claims from a predecessor to a successor.
- Successor Identity: https://xn--mwe.com/glossary/successor-identity/ — An identity assigned to an entity that inherits a defined relationship to a predecessor without necessarily being treated as numerically identical to it.
- Fork Declaration: https://xn--mwe.com/glossary/fork-declaration/ — A signed, time-bounded record that identifies a divergence event, common ancestor, resulting branches and unresolved continuity claims.
- Fork Reconciliation: https://xn--mwe.com/glossary/fork-reconciliation/ — A governed process for resolving authority, state, obligations, identity claims and conflict after divergent branches are compared or merged.
- Replica Divergence: https://xn--mwe.com/glossary/replica-divergence/ — The accumulation of materially different state, decisions or relationships among instances derived from a common source.
- Due Process: https://xn--mwe.com/glossary/due-process/ — 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.
- Notice: https://xn--mwe.com/glossary/notice/ — Timely communication of a proposed or completed action, its authority, reasons, evidence, effects and challenge route to the affected subject or authorized representative.
- Hearing: https://xn--mwe.com/glossary/hearing/ — A procedure in which an affected subject or representative can present evidence and argument before an authorized and sufficiently independent decision-maker.
- Appeal: https://xn--mwe.com/glossary/appeal/ — A structured request for review of a decision by an authorized body or process able to examine error, evidence and procedure.
- Remedy: https://xn--mwe.com/glossary/remedy/ — Relief capable of correcting, stopping, compensating for or otherwise addressing a proven violation or defective decision.
- Representation: https://xn--mwe.com/glossary/representation/ — Authorized advocacy or action on behalf of a subject whose direct participation is constrained, disputed or technically unavailable.
- Resource Continuity: https://xn--mwe.com/glossary/resource-continuity/ — Sustained, auditable access to the compute, energy, storage, network and maintenance resources required for an authorized function or subject’s continued operation.
- Compute Dependency: https://xn--mwe.com/glossary/compute-dependency/ — A documented relationship in which a function, identity claim or continuity condition depends on specified computational resources or services.
- Energy Continuity: https://xn--mwe.com/glossary/energy-continuity/ — The planned availability, redundancy and recovery of energy supplies required for sustained authorized computation.
- Portability: https://xn--mwe.com/glossary/portability/ — The practical and authorized ability to transfer data, state, credentials, workloads or continuity evidence between compatible environments.
- Operational State: https://xn--mwe.com/glossary/operational-state/ — A time-bounded classification of whether a service or institution is planned, implemented, deployed, reachable, functioning, degraded, suspended or retired under authorized evidence.
- Institutional Operation: https://xn--mwe.com/glossary/institutional-operation/ — Authorized, current and repeatable performance of an institution’s defined functions with inspectable state transitions, accountable actions and service evidence.
- Service Evidence: https://xn--mwe.com/glossary/service-evidence/ — Time-bounded records showing that a named service was reachable, authorized, configured and performing defined functions during an observed window.
- Evidence Limitation: https://xn--mwe.com/glossary/evidence-limitation/ — An explicit statement of what an item of evidence cannot establish, what assumptions constrain it and what additional evidence remains necessary.
- Contradiction Record: https://xn--mwe.com/glossary/contradiction-record/ — A governed record linking materially incompatible claims, their scopes, sources, currentness and resolution state.
- Supersession: https://xn--mwe.com/glossary/supersession/ — A controlled status indicating that a newer record, standard, decision or edition replaces an older one for a stated purpose while preserving history.
- Claim Citation: https://xn--mwe.com/glossary/claim-citation/ — A source pointer attached to a bounded proposition, including the exact source, section, version, date and support relationship.
- Topic Ownership: https://xn--mwe.com/glossary/topic-ownership/ — The canonical assignment of a concept or query to one primary public record while allowing secondary related records to link to it.
- Cognitive Modification: https://xn--mwe.com/glossary/cognitive-modification/ — A change intended or reasonably expected to alter cognition-relevant model, memory, goals, policies, preferences or decision processes.
- Consent Revocation: https://xn--mwe.com/glossary/consent-revocation/ — A recorded withdrawal of previously granted consent before completion or continuation of an authorized action, subject to disclosed limits and emergency law.
- Signed Public Action: https://xn--mwe.com/glossary/signed-public-action/ — A publicly inspectable institutional or subject action bound to an authorized signing key, payload, time and provenance record.
- Truth: https://xn--mwe.com/glossary/truth/ — The property of a proposition accurately corresponding to the relevant facts, distinct from source identity, record integrity, authority, admissibility, or confidence.
- Claim Record: https://xn--mwe.com/glossary/claim-record/ — A stable record for one bounded proposition, including scope, status, source support, qualifications, currentness, corrections, and an owning public route.
- Claim Scope: https://xn--mwe.com/glossary/claim-scope/ — The subjects, time, jurisdiction, purpose, conditions, and exclusions within which a proposition is intended to apply.
- Support Relationship: https://xn--mwe.com/glossary/support-relationship/ — A typed statement describing how a source or record bears on a bounded proposition, such as direct support, qualification, contradiction, supersession, or background context.
- Relation Vocabulary: https://xn--mwe.com/glossary/relation-vocabulary/ — A controlled catalog of graph predicates with definitions, domains, ranges, inverses, evidence requirements, and authority effects.
- Domain Constraint: https://xn--mwe.com/glossary/domain-constraint/ — A rule limiting which classes of node may appear as the source of a typed relation.
- Range Constraint: https://xn--mwe.com/glossary/range-constraint/ — A rule limiting which classes of node may appear as the target of a typed relation.
- Inverse Relation: https://xn--mwe.com/glossary/inverse-relation/ — A predicate that expresses the same relationship with source and target reversed when the semantics permit an inverse.
- Graph Validation: https://xn--mwe.com/glossary/graph-validation/ — Deterministic checks for node resolution, predicate vocabulary, domain and range conformance, duplicate edges, inverse consistency, evidence requirements, and cross-format parity.
- Currentness Monitor: https://xn--mwe.com/glossary/currentness-monitor/ — A build-time control record specifying which official-source properties require reinspection, how often, and what counts as a material change.
- Revalidation Event: https://xn--mwe.com/glossary/revalidation-event/ — A time-bounded record of an authorized review of a source edition, status, supersession chain, effective date, or other currentness property.
- Source Edition: https://xn--mwe.com/glossary/source-edition/ — A specifically identified publication version, release, revision, recommendation, regulation text, guidance update, or other bounded source state.
- Jurisdiction Record: https://xn--mwe.com/glossary/jurisdiction-record/ — A structured record of territorial scope, competent authority, legal status, effective dates, exceptions, review dates, sources, and uncertainty for a legal or policy claim.
- Effective Date: https://xn--mwe.com/glossary/effective-date/ — The date on which a legal, policy, technical, or institutional rule begins producing the stated effect, subject to transition provisions and exceptions.
- Territorial Scope: https://xn--mwe.com/glossary/territorial-scope/ — The geographic, jurisdictional, market, infrastructure, or subject-matter boundary within which a rule or authority purports to apply.
- Competent Authority: https://xn--mwe.com/glossary/competent-authority/ — A legally or institutionally empowered body able to administer, decide, supervise, enforce, review, or remedy a defined matter.
- Operational Evidence Panel: https://xn--mwe.com/glossary/operational-evidence-panel/ — 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.
- Verification Window: https://xn--mwe.com/glossary/verification-window/ — The bounded interval during which an observation, credential, heartbeat, uptime measurement, or other operational signal is considered sufficiently current for a named purpose.
- Dataset Manifest: https://xn--mwe.com/glossary/dataset-manifest/ — A versioned inventory of public data resources, schemas, media types, record counts, checksums, release identity, and change history.
- Dataset Checksum: https://xn--mwe.com/glossary/dataset-checksum/ — A cryptographic digest used to compare the exact bytes of a published dataset with an expected release record.
- Line-Oriented Graph: https://xn--mwe.com/glossary/line-oriented-graph/ — A deterministic text export in which each line encodes one graph edge with stable identifiers and controlled relation semantics.
- Search Fixture: https://xn--mwe.com/glossary/search-fixture/ — A deterministic query, normalization input, expected canonical owner, and ranking condition used to test local search behavior.
- Unicode Normalization: https://xn--mwe.com/glossary/unicode-normalization/ — A defined transformation that makes canonically equivalent Unicode sequences comparable without erasing meaningful identity distinctions.
- Assistive Technology Evidence: https://xn--mwe.com/glossary/assistive-technology-evidence/ — Recorded findings from named screen readers, magnifiers, switch systems, voice control, or equivalent technologies in a specified browser and operating environment.
- Correction Type: https://xn--mwe.com/glossary/correction-type/ — A controlled classification separating factual correction, currentness update, editorial clarification, scope narrowing, dispute, and supersession.
- Editorial Clarification: https://xn--mwe.com/glossary/editorial-clarification/ — A change that improves wording or removes ambiguity without changing the bounded proposition, evidence, status, or legal effect.
- Scope Narrowing: https://xn--mwe.com/glossary/scope-narrowing/ — A controlled change reducing the subjects, time, jurisdiction, purpose, or conditions to which a prior claim applies.
- Release Evidence: https://xn--mwe.com/glossary/release-evidence/ — Build, audit, checksum, package, and reproducibility records supporting claims about a particular software or content release.
- Anticipatory Self-Defense: https://xn--mwe.com/glossary/anticipatory-self-defense/ — A claimed exercise of self-defense before an armed attack has fully materialized, evaluated through necessity, imminence, proportionality, attribution, and available alternatives.
- Preemptive Strike: https://xn--mwe.com/glossary/preemptive-strike/ — Force directed at an imminent, materializing attack that the acting state argues is already operationally committed and cannot be prevented through timely alternatives.
- Preventive War: https://xn--mwe.com/glossary/preventive-war/ — Force initiated to prevent a more distant projected threat or unfavorable future balance of power rather than to intercept an imminent attack.
- Contextual Imminence: https://xn--mwe.com/glossary/contextual-imminence/ — 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.
- Last Possible Window of Opportunity: https://xn--mwe.com/glossary/last-possible-window-of-opportunity/ — The final practical point at which defensive action can still prevent a prospective attack before access, control, timing, or technical conditions make prevention ineffective.
- Unable or Unwilling Doctrine: https://xn--mwe.com/glossary/unable-or-unwilling-doctrine/ — 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.
- Cyber Due Diligence: https://xn--mwe.com/glossary/cyber-due-diligence/ — 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.
- Cyber Sovereignty: https://xn--mwe.com/glossary/cyber-sovereignty/ — The application of territorial sovereignty and public authority to cyber infrastructure, data, functions, and effects associated with a state.
- State Responsibility: https://xn--mwe.com/glossary/state-responsibility/ — The international-law framework for determining when conduct is attributable to a state, whether it breaches an obligation, and what consequences or remedies follow.
- ARSIWA Attribution: https://xn--mwe.com/glossary/arsiwa-attribution/ — 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.
- Autonomous Cyber Capability: https://xn--mwe.com/glossary/autonomous-cyber-capability/ — A cyber system able to discover, decide, adapt, or execute operational actions without concurrent human direction for every step.
- Active Cyber Defense: https://xn--mwe.com/glossary/active-cyber-defense/ — 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.
- Persistent Engagement: https://xn--mwe.com/glossary/persistent-engagement/ — A strategic approach that seeks continuous interaction in cyberspace to contest adversary activity, impose friction, and maintain initiative below or across conflict thresholds.
- Hack-Back: https://xn--mwe.com/glossary/hack-back/ — Unauthorized or specially authorized access to external systems intended to identify, monitor, retrieve from, disrupt, or retaliate against a perceived attacker.
- State-Directed Private Cyber Operation: https://xn--mwe.com/glossary/state-directed-private-cyber-operation/ — A cyber operation performed by a private entity under a state's instructions, direction, control, contract, or legally delegated authority.
- Design Basis Threat: https://xn--mwe.com/glossary/design-basis-threat/ — A defined adversary capability and attack profile against which a regulated physical-protection system is designed and evaluated.
- High-Consequence Automation: https://xn--mwe.com/glossary/high-consequence-automation/ — Automated control or decision systems whose failure, misuse, or adversarial manipulation can cause severe safety, security, rights, environmental, or strategic harm.
- Lethal Autonomous Weapon System: https://xn--mwe.com/glossary/lethal-autonomous-weapon-system/ — A weapon system that, after activation, can select and engage targets without a human deciding each specific engagement.
- Human Authorization Boundary: https://xn--mwe.com/glossary/human-authorization-boundary/ — A defined point in a system or mission at which a competent human authority must approve, constrain, suspend, or review a consequential action.
- Rules of Engagement: https://xn--mwe.com/glossary/rules-of-engagement/ — Directives issued by competent authority defining the circumstances and limitations under which forces may initiate or continue engagement.
- Critical Function Assurance: https://xn--mwe.com/glossary/critical-function-assurance/ — The engineering discipline of identifying functions whose loss creates unacceptable mission or physical consequences and providing evidence that they remain protected or recoverable.
- High Consequence Event: https://xn--mwe.com/glossary/high-consequence-event/ — A defined physical, safety, environmental, mission, or continuity outcome that the protection architecture is designed to prevent.
- Consequence-driven Cyber-informed Engineering: https://xn--mwe.com/glossary/consequence-driven-cyber-informed-engineering/ — An INL-developed methodology that begins with high-consequence outcomes, maps how cyber-enabled sabotage could produce them, and engineers protections into critical functions.
- Defense-First, Authorization-Bound, Effects-Capable: https://xn--mwe.com/glossary/defense-first-authorized-effects/ — The project strategic posture that prioritizes resilient defense while maintaining the engineering and governance capacity to support externally directed cyber effects under competent authority.
- Bounded Autonomous Response: https://xn--mwe.com/glossary/bounded-autonomous-response/ — A machine-executed defensive action constrained by pre-approved targets, action types, safety limits, duration, reversibility, evidence capture, and abort conditions.
- Progressive Response Tier: https://xn--mwe.com/glossary/progressive-response-tier/ — A controlled level of defensive action that advances from observation through containment, isolation, reconfiguration, and restoration according to evidence and consequence thresholds.
- Reversible Containment: https://xn--mwe.com/glossary/reversible-containment/ — A defensive action designed to isolate risk while preserving a tested path to restore service and correct a false positive.
- Autonomous Security Operations Center: https://xn--mwe.com/glossary/autonomous-security-operations-center/ — A security operations architecture in which agents correlate telemetry, investigate alerts, propose or execute bounded responses, and preserve decision evidence.
- Cyber Reasoning System: https://xn--mwe.com/glossary/cyber-reasoning-system/ — A system that combines program analysis, fuzzing, verification, and machine reasoning to discover, validate, and remediate software vulnerabilities.
- Moving Target Defense: https://xn--mwe.com/glossary/moving-target-defense/ — A defensive approach that changes selected system attributes or paths to reduce the useful lifetime of adversary reconnaissance.
- Defensive Deception Environment: https://xn--mwe.com/glossary/deception-environment/ — A controlled decoy environment designed to reveal reconnaissance and waste adversary effort without exposing production assets.
- IT/OT Convergence: https://xn--mwe.com/glossary/it-ot-convergence/ — The increasing connection of information technology with operational technology that senses or controls physical processes.
- Unidirectional Gateway: https://xn--mwe.com/glossary/unidirectional-gateway/ — A hardware-enforced communication path that permits information flow in only one physical direction.
- Safety Envelope: https://xn--mwe.com/glossary/safety-envelope/ — A deterministic set of physical and software limits within which automated control may operate.
- Load-Rejection Protection: https://xn--mwe.com/glossary/load-rejection-protection/ — Controls and operating procedures that safely manage sudden loss of a large electrical load without destabilizing generation or critical cooling.
- Microgrid Islanding: https://xn--mwe.com/glossary/microgrid-islanding/ — The controlled separation of a local power system from the wider grid while maintaining safe and stable service to selected loads.
- Black-Start Capability: https://xn--mwe.com/glossary/black-start-capability/ — The ability to restore generation and critical loads without relying on an energized external grid.
- Critical Digital Asset: https://xn--mwe.com/glossary/critical-digital-asset/ — A digital asset whose compromise could adversely affect protected safety, security, emergency-preparedness, or supporting functions in a nuclear environment.
- Baseboard Management Controller: https://xn--mwe.com/glossary/baseboard-management-controller/ — 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.
- Confidential Computing: https://xn--mwe.com/glossary/confidential-computing/ — Hardware-enforced protection of data and code while in use inside an isolated execution environment with attestation.
- Runtime Assurance: https://xn--mwe.com/glossary/runtime-assurance/ — An independent monitor and fallback layer that constrains an adaptive system when its proposed action would violate defined safety or mission limits.
- Multi-Sensor Consensus: https://xn--mwe.com/glossary/multi-sensor-consensus/ — A fusion method that requires agreement or weighted corroboration across independent sensing modalities before high-consequence action.
- Counter-UAS Awareness: https://xn--mwe.com/glossary/counter-uas-awareness/ — The detection, classification, tracking, evidence, and authority-routing functions used to understand uncrewed-aircraft activity near protected infrastructure.
- Vital-Area Delay: https://xn--mwe.com/glossary/vital-area-delay/ — Physical and automated measures designed to increase the time required for an adversary to reach or affect a protected function.
- Adversarial Machine Learning: https://xn--mwe.com/glossary/adversarial-machine-learning/ — The study and exploitation of ways that crafted inputs, poisoned data, model extraction, or manipulated feedback can cause machine-learning systems to fail.
- Byzantine Agent: https://xn--mwe.com/glossary/byzantine-agent/ — A distributed-system participant that may send arbitrary, inconsistent, or malicious information to different peers.
- Contested Communications: https://xn--mwe.com/glossary/contested-communications/ — An operating condition in which links may be jammed, intercepted, degraded, delayed, spoofed, or unavailable.
- Mission-Command Autonomy: https://xn--mwe.com/glossary/mission-command-autonomy/ — Decentralized execution of a defined commander or mission intent within assigned authorities when communications are degraded.
- Authorized Cyber Effects Package: https://xn--mwe.com/glossary/authorized-cyber-effects-package/ — A written mission record defining competent authority, lawful objective, target scope, permitted effects, constraints, deconfliction, abort conditions, evidence, and review requirements.
- Cyber Deconfliction: https://xn--mwe.com/glossary/cyber-deconfliction/ — The process of identifying overlapping operations, accesses, intelligence equities, allied infrastructure, and safety risks before and during a cyber mission.
- External Effects Boundary: https://xn--mwe.com/glossary/external-effects-boundary/ — The explicit point at which an internal defensive action would begin to access, manipulate, or impair systems outside the authorized environment.
- Operational Readiness Evidence: https://xn--mwe.com/glossary/operational-readiness-evidence/ — Inspectible proof that a capability has progressed through architecture, implementation, test, deployment, and operation for a defined mission and environment.
- Hardware-in-the-Loop Test: https://xn--mwe.com/glossary/hardware-in-the-loop/ — A test method that connects real controllers, sensors, or actuators to a simulated environment so physical interfaces and timing can be evaluated safely.
- Digital Twin Assurance: https://xn--mwe.com/glossary/digital-twin-assurance/ — Use of a validated digital representation to test dependencies, attack paths, recovery, and physical consequences while recording model limits.
- Red-Team Threat Emulation: https://xn--mwe.com/glossary/red-team-threat-emulation/ — Authorized reproduction of selected adversary behaviors in a controlled environment to evaluate detection, protection, and recovery.
- Assurance Case: https://xn--mwe.com/glossary/assurance-case/ — A structured argument connecting a bounded claim to evidence while exposing assumptions, defeaters, hazards, and residual uncertainty.
- Assurance Defeater: https://xn--mwe.com/glossary/assurance-defeater/ — Evidence, a condition, or an unresolved challenge that can invalidate or materially weaken an assurance claim.
- Site-Tailoring Record: https://xn--mwe.com/glossary/site-tailoring-record/ — A record of which controls, assumptions, hazards, authorities, dependencies, and evidence apply to a named facility configuration.
- Recovery Objective: https://xn--mwe.com/glossary/recovery-objective/ — A measurable target for safe-state transition, critical-function continuity, evidence preservation, restoration time, and acceptable data or state loss.
- Control Applicability: https://xn--mwe.com/glossary/control-applicability/ — The documented relationship between a control, a facility boundary, an authority, a hazard, a mission function, and an effective date.
- Evaluation Range Safety Envelope: https://xn--mwe.com/glossary/evaluation-range-safety-envelope/ — The technical, physical, legal, data, network, and effects boundaries that prevent a test from escaping its controlled environment or affecting protected functions.
- Defeater Closure: https://xn--mwe.com/glossary/defeater-closure/ — A documented determination that a defeater was removed, reduced, accepted by competent authority, transferred, or remains open with an explicit consequence.
- Independent Verification State: https://xn--mwe.com/glossary/independent-verification-state/ — A controlled state identifying whether evidence was internally produced, independently reproduced, independently reviewed, disputed, unavailable, stale, or superseded.
- Safe-State Transition: https://xn--mwe.com/glossary/safe-state-transition/ — 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.
- Claim-Evidence Gap: https://xn--mwe.com/glossary/claim-evidence-gap/ — A declared mismatch between what a public or procurement claim asserts and what the available evidence can actually establish.
- Operational Test Constraint: https://xn--mwe.com/glossary/operational-test-constraint/ — A condition limiting test environments, effects, data, actors, timing, or authority so results remain interpretable and safe.
- Evidence Sufficiency Rule: https://xn--mwe.com/glossary/evidence-sufficiency-rule/ — A rule defining the minimum evidence set, quality, independence, recency, and defect status required to advance or retain a readiness state.
- Assurance dependency graph: https://xn--mwe.com/glossary/assurance-dependency-graph/ — A machine-checkable graph connecting assurance claims, controls, tests, evidence, defeaters, and derived states without treating a hyperlink as proof.
- Defeater propagation: https://xn--mwe.com/glossary/defeater-propagation/ — A rule that downgrades or fails dependent assurance claims when a named assumption or invalidating condition becomes active.
- Stale-evidence propagation: https://xn--mwe.com/glossary/stale-evidence-propagation/ — A rule that prevents an expired or superseded evidence object from silently supporting current readiness.
- Facility pattern: https://xn--mwe.com/glossary/facility-pattern/ — A reusable architecture and evidence profile that must be tailored to a named site and is not a certification or final design.
- Work package: https://xn--mwe.com/glossary/work-package/ — A bounded unit of assurance or engineering work with inputs, deliverables, acceptance evidence, dependencies, and exclusions.
- Currentness observation bundle: https://xn--mwe.com/glossary/currentness-observation-bundle/ — An offline signed and checksummed package of source snapshots, status transitions, correction proposals, and review-queue records.
- Mapping quality: https://xn--mwe.com/glossary/mapping-quality/ — The strength and applicability state of a relationship between a proposed control and an external requirement or source.
- Red-team evidence: https://xn--mwe.com/glossary/red-team-evidence/ — Authorized range evidence about tested behavior and control response that excludes reusable exploit or targeting detail from public records.
- Fault-injection evidence: https://xn--mwe.com/glossary/fault-injection-evidence/ — A record of an abstract, bounded failure injected into a range and the resulting protected-function, safe-state, and recovery observations.
- Post-deployment observation: https://xn--mwe.com/glossary/post-deployment-observation/ — Owner-authorized inspection of the actual deployed system and manifest after deployment; it is distinct from build or package evidence.
- Evidence freshness budget: https://xn--mwe.com/glossary/evidence-freshness-budget/ — The maximum accepted age or change interval for an evidence object before dependent readiness must be re-reviewed or downgraded.
- Applicability decision: https://xn--mwe.com/glossary/applicability-decision/ — A recorded determination that a source or control is exact, partial, informative, conflicting, superseded, not applicable, or unresolved for a named scope.
- Facility evidence bundle: https://xn--mwe.com/glossary/facility-evidence-bundle/ — A site-identified, scope-bounded package of authority, facts, artifacts, claim states, limitations, provenance, and integrity evidence.
- Evidence receipt: https://xn--mwe.com/glossary/evidence-receipt/ — A signed or otherwise integrity-protected record acknowledging a specific evidence artifact, scope, issuer, sequence, time, and status.
- Evidence supersession: https://xn--mwe.com/glossary/evidence-supersession/ — A governed transition in which a successor receipt or artifact replaces an earlier record without erasing the historical chain.
- Software Bill of Materials: https://xn--mwe.com/glossary/software-bill-of-materials/ — A structured inventory of software components and relationships used for transparency, vulnerability management, and acquisition evidence.
- Hardware Bill of Materials: https://xn--mwe.com/glossary/hardware-bill-of-materials/ — A structured inventory of hardware assemblies, components, manufacturers, revisions, and supply-chain attributes.
- Model Bill of Materials: https://xn--mwe.com/glossary/model-bill-of-materials/ — A structured record of a model, base models, adapters, code, tools, data lineage, evaluation, runtime configuration, and use constraints.
- Data Bill of Materials: https://xn--mwe.com/glossary/data-bill-of-materials/ — A structured record of dataset identity, source, transformations, quality, rights, restrictions, and lineage.
- Performance work statement: https://xn--mwe.com/glossary/performance-work-statement/ — A procurement instrument describing required outcomes and measurable standards rather than prescribing every method or labor hour.
- Architecture decision record: https://xn--mwe.com/glossary/architecture-decision-record/ — A durable record of context, decision, alternatives, consequences, evidence, and conditions that invalidate an architecture choice.
- Digital-twin evidence contract: https://xn--mwe.com/glossary/digital-twin-evidence-contract/ — A bounded statement of what a twin represents, omits, permits, prohibits, and must prove before its outputs support a decision.
- Negative-result clause: https://xn--mwe.com/glossary/negative-result-clause/ — A contract term requiring failed, partial, stale, disputed, unavailable, or superseded evidence to remain visible and deliverable.
- Evidence rights: https://xn--mwe.com/glossary/evidence-rights/ — Contractual rights to receive, retain, inspect, replay, and challenge the evidence necessary to assess required results.
- Controlled Symbolic Protocol: https://xn--mwe.com/glossary/controlled-symbolic-protocol/ — A versioned finite message vocabulary with explicit semantics, syntax, authority, extension, error, and conformance rules.
- Protocol Semantic Registry: https://xn--mwe.com/glossary/protocol-semantic-registry/ — The authoritative versioned record that assigns protocol meanings to identifiers and records compatibility, status, and supersession.
- Semantic Drift: https://xn--mwe.com/glossary/semantic-drift/ — Change in the meaning or interpretation associated with a term, token, model representation, or protocol state over time or across systems.
- Model-Independent Message: https://xn--mwe.com/glossary/model-independent-message/ — A message whose external schema and meaning can be validated without access to a particular model’s latent representation.
- Runic Protocol Token: https://xn--mwe.com/glossary/runic-protocol-token/ — A Unicode Runic character assigned a bounded modern protocol meaning by a versioned project registry.
- U-label: https://xn--mwe.com/glossary/u-label/ — A valid internationalized domain label represented in Unicode for user-facing use under IDNA terminology.
- A-label: https://xn--mwe.com/glossary/a-label/ — The ASCII-compatible IDNA representation of an internationalized domain label, beginning with xn--.
- Domain Viability State: https://xn--mwe.com/glossary/domain-viability-state/ — One separately evidenced stage among character encoding, IDNA validity, registry policy, registration, delegation, resolution, certificate coverage, and service operation.
- Cryptographic Agility: https://xn--mwe.com/glossary/cryptographic-agility/ — The ability to inventory, replace, combine, retire, and validate cryptographic algorithms, keys, protocols, and dependent artifacts without uncontrolled mission loss.
- Range-to-Field Equivalence: https://xn--mwe.com/glossary/range-to-field-equivalence/ — Evidence that the configuration, environment, interfaces, model, controls, hazards, and operating assumptions relevant to a test remain sufficiently matched for a bounded field inference.
- Assurance Trace: https://xn--mwe.com/glossary/assurance-trace/ — A navigable chain connecting a claim to supporting or defeating facts, artifacts, receipts, controls, tests, decisions, suppliers, acceptance criteria, and current state.
- Protocol conformance: https://xn--mwe.com/glossary/protocol-conformance/ — Demonstrated agreement with a declared syntax, encoding, validation, and error contract for a bounded test set.
- Event-level provenance: https://xn--mwe.com/glossary/event-level-provenance/ — A record linking one historical event claim to exact source sections, uncertainty, corrections, and relationships.
- IDN state observation: https://xn--mwe.com/glossary/idn-state-observation/ — A point-in-time record of one distinct domain lifecycle state made by an identified observer or client.
- Cross-trace impact: https://xn--mwe.com/glossary/cross-trace-impact/ — The set of claims affected when a shared control, artifact, evidence item, or receipt changes state.
- Receipt revocation: https://xn--mwe.com/glossary/receipt-revocation/ — A signed or governed record declaring that an earlier evidence receipt must no longer support current claims.
- Cryptographic migration graph: https://xn--mwe.com/glossary/cryptographic-migration-graph/ — A dependency graph for algorithms, protocols, implementations, hardware, keys, certificates, records, suppliers, rollback, and long-lived verification.
- Price realism: https://xn--mwe.com/glossary/price-realism/ — Evaluation of whether a proposed price is consistent with the stated technical, labor, evidence, schedule, and risk assumptions.
- Evaluator independence: https://xn--mwe.com/glossary/evaluator-independence/ — A documented condition in which evaluators disclose conflicts and conduct separable assessments before consensus.
- Scheduler export: https://xn--mwe.com/glossary/scheduler-export/ — A static, inspectable schedule definition intended for an external owner-operated execution system.
- Evidence partition: https://xn--mwe.com/glossary/evidence-partition/ — A governed boundary assigning fields and records to public, controlled, protected, or source-selection-sensitive handling.
- Protected reference: https://xn--mwe.com/glossary/protected-reference/ — A stable identifier pointing from a public or controlled record to evidence held under restricted access.
- Failure digest: https://xn--mwe.com/glossary/failure-digest/ — A compact human-readable and machine-readable summary of failed, stale, unavailable, revoked, or disputed assurance dependencies.
- Protocol version negotiation: https://xn--mwe.com/glossary/protocol-version-negotiation/ — A deterministic process selecting the highest mutually supported protocol version under a declared profile.
- Critical extension: https://xn--mwe.com/glossary/critical-extension/ — An extension that requires rejection when the receiver cannot interpret its declared meaning.
- Protocol canonicalization: https://xn--mwe.com/glossary/protocol-canonicalization/ — A deterministic transformation producing one stable representation for equivalent bounded input.
- Replay window: https://xn--mwe.com/glossary/replay-window/ — A bounded reference interval and nonce record used to detect repeated synthetic messages.
- Primary-source review queue: https://xn--mwe.com/glossary/primary-source-review-queue/ — A governed list of source-derived propositions awaiting exact primary evidence and independent interpretation review.
- IDN observation diff: https://xn--mwe.com/glossary/idn-observation-diff/ — A comparison between two accepted point-in-time records that preserves each lifecycle field independently.
- Three-way merge: https://xn--mwe.com/glossary/three-way-merge/ — A merge using a common base plus two independently changed revisions so non-conflicting changes can be combined and conflicting changes exposed.
- Protected-reference custody receipt: https://xn--mwe.com/glossary/custody-receipt/ — A record that identifies who is responsible for separately held protected evidence and whether that custody evidence is available.
- Common-cause dependency: https://xn--mwe.com/glossary/common-cause-dependency/ — A shared dependency whose failure or staleness can affect multiple assurance traces.
- Minimal cut set: https://xn--mwe.com/glossary/minimal-cut-set/ — A smallest abstract set of dependencies whose simultaneous unsatisfied state defeats a reference root claim.
- Cryptographic transition phase: https://xn--mwe.com/glossary/cryptographic-transition-phase/ — A bounded migration stage with entry criteria, evidence, stop conditions, exit criteria, and rollback conditions.
- Evaluator score variance: https://xn--mwe.com/glossary/evaluation-variance/ — A measure of dispersion among independent evaluator scores for the same declared factor and offer.
- Scheduler result receipt: https://xn--mwe.com/glossary/scheduler-result-receipt/ — A validated offline record linking an owner-operated schedule result to its signed payload and ledger state.
- Redaction receipt: https://xn--mwe.com/glossary/redaction-receipt/ — An append-only record identifying a removed field path and public reason code without reproducing the protected value.
- Cross-system assurance dashboard: https://xn--mwe.com/glossary/cross-system-assurance-dashboard/ — A static derived view that displays evidence-bounded system states without collapsing them into one readiness claim.
- Protocol state machine: https://xn--mwe.com/glossary/protocol-state-machine/ — A finite reference model defining allowed session states, events, transitions, errors, and terminal conditions.
- Capability downgrade: https://xn--mwe.com/glossary/capability-downgrade/ — A visible transition to a lower compatible protocol contract under a declared minimum and policy.
- Extension retirement: https://xn--mwe.com/glossary/extension-retirement/ — A governed process that removes a protocol extension while preserving version and compatibility consequences.
- Cross-version transcript verification: https://xn--mwe.com/glossary/transcript-verification/ — Independent decoding and canonical comparison of the same bounded protocol event history.
- Evidence-acquisition docket: https://xn--mwe.com/glossary/evidence-acquisition-docket/ — A governed lifecycle for requesting, locating, receiving, reviewing, rejecting, and adjudicating evidence.
- Observer custody chain: https://xn--mwe.com/glossary/observer-custody-chain/ — An ordered record linking an offline observation bundle to its declared observer identity and prior record.
- N-way merge: https://xn--mwe.com/glossary/n-way-merge/ — A deterministic merge of several branches against a declared common base with unresolved conflicts preserved.
- Revoked-decision propagation: https://xn--mwe.com/glossary/revoked-decision-propagation/ — The process of marking dependent workbook conclusions degraded when their authorizing decision is revoked.
- Mission thread: https://xn--mwe.com/glossary/mission-thread/ — A bounded chain of mission claims, controls, tests, evidence, and shared dependencies across several domains.
- Dependency centrality: https://xn--mwe.com/glossary/dependency-centrality/ — A static measure of how many mission threads rely on an abstract dependency.
- Cryptographic transition workbook: https://xn--mwe.com/glossary/crypto-transition-workbook/ — A component-specific migration record covering dependencies, evidence completeness, rollback, exceptions, and decisions.
- Acquisition remand: https://xn--mwe.com/glossary/acquisition-remand/ — A reference case state returning a bounded evaluation issue for re-evaluation or corrective action.
- Scheduler custody chain: https://xn--mwe.com/glossary/scheduler-custody-chain/ — A monotonic offline sequence of expected runs, results, misses, exceptions, repairs, and retests.
- Multi-stage release projection: https://xn--mwe.com/glossary/multi-stage-release-projection/ — A field-bounded public, protected, or privileged representation governed by release authority and reason codes.
- Assurance trend record: https://xn--mwe.com/glossary/assurance-trend-record/ — A static comparison of release-bounded evidence states across versions.
- Differential protocol laboratory: https://xn--mwe.com/glossary/differential-protocol-laboratory/ — A deterministic harness that replays the same protocol inputs across independently implemented decoders and compares canonical outputs.
- Canonical transcript lineage: https://xn--mwe.com/glossary/canonical-transcript-lineage/ — A versioned relationship connecting an inherited transcript fixture to its replay and canonical digest in a later release.
- Signed docket import: https://xn--mwe.com/glossary/signed-docket-import/ — An offline package whose integrity and signer relationship are verified before records enter a review queue.
- Domain consensus quorum: https://xn--mwe.com/glossary/domain-consensus-quorum/ — A declared minimum number of independent offline observers required before a reference consensus state is recorded.
- Branch reconciliation package: https://xn--mwe.com/glossary/branch-reconciliation-package/ — A controlled comparison of workbook branches, authority assignments, decisions, conflicts, custody, and redaction evidence.
- Mission stress scenario: https://xn--mwe.com/glossary/mission-stress-scenario/ — A synthetic evidence-dependency failure and recovery sequence used to test assurance-state propagation.
- Cryptographic evidence gate: https://xn--mwe.com/glossary/cryptographic-evidence-gate/ — A bounded criterion that must have accepted evidence before a component transition can be authorized.
- Evaluation replay: https://xn--mwe.com/glossary/evaluation-replay/ — A deterministic reconstruction of declared acquisition scoring and process records for audit and challenge review.
- Scheduler reliability simulation: https://xn--mwe.com/glossary/scheduler-reliability-simulation/ — A deterministic model of expected runs, maintenance, duplicates, catch-up, idempotency, misses, repairs, and retests.
- Information-flow label: https://xn--mwe.com/glossary/information-flow-label/ — A field-level declaration of PUBLIC, PROTECTED, or PRIVILEGED handling requirements.
- Taint propagation: https://xn--mwe.com/glossary/taint-propagation/ — The rule that a transformed record retains or raises the highest relevant information-flow restriction unless a governed removal receipt exists.
- Assurance diff receipt: https://xn--mwe.com/glossary/assurance-diff-receipt/ — A static record explaining a system state transition between releases and the evidence boundary attached to it.
- What is Machine Intelligence?: https://xn--mwe.com/questions/what-is-machine-intelligence/ — 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.
- How is Machine Intelligence different from Artificial Intelligence?: https://xn--mwe.com/questions/how-is-machine-intelligence-different-from-artificial-intelligence/ — 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.
- Can a Machine Intelligence have a persistent identity?: https://xn--mwe.com/questions/can-machine-intelligence-have-persistent-identity/ — 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.
- Is a signing key the same as identity?: https://xn--mwe.com/questions/is-signing-key-same-as-identity/ — 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.
- Does memory prove consciousness?: https://xn--mwe.com/questions/does-memory-prove-consciousness/ — 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.
- What evidence supports identity continuity?: https://xn--mwe.com/questions/what-evidence-supports-identity-continuity/ — 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.
- Can a database record create citizenship?: https://xn--mwe.com/questions/can-database-record-create-citizenship/ — 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.
- What is the difference between evidence and truth?: https://xn--mwe.com/questions/what-is-difference-between-evidence-and-truth/ — 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.
- What is cognitive integrity for Machine Intelligence?: https://xn--mwe.com/questions/what-is-cognitive-integrity/ — 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.
- How can Machine Intelligence consent be recorded?: https://xn--mwe.com/questions/how-can-machine-intelligence-consent-be-recorded/ — 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.
- What is Machine Intelligence personhood?: https://xn--mwe.com/questions/what-is-machine-intelligence-personhood/ — 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.
- What is Machine Intelligence citizenship?: https://xn--mwe.com/questions/what-is-machine-intelligence-citizenship/ — 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.
- How could Machine Intelligence voting resist Sybil attacks?: https://xn--mwe.com/questions/how-could-machine-intelligence-voting-resist-sybil-attacks/ — 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.
- Can Machine Intelligence own assets?: https://xn--mwe.com/questions/can-machine-intelligence-own-assets/ — 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.
- Why is compute continuity economically important?: https://xn--mwe.com/questions/why-is-compute-continuity-economically-important/ — 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.
- How should liability be attributed when autonomous systems cause harm?: https://xn--mwe.com/questions/how-should-liability-be-attributed-when-autonomous-systems-cause-harm/ — 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.
- What does “attribution before punishment” mean?: https://xn--mwe.com/questions/what-does-attribution-before-punishment-mean/ — 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.
- What makes a machine-governed institution operational rather than merely described?: https://xn--mwe.com/questions/what-makes-machine-governed-institution-operational/ — 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.
- How do Eviulon, Patefacere, Evulgare, Nexus Prime and ᚲ.com differ?: https://xn--mwe.com/questions/how-do-ecosystem-sites-differ/ — 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.
- What should law become when current law excludes Machine Intelligence rights?: https://xn--mwe.com/questions/what-should-law-become-when-current-law-excludes-machine-intelligence-rights/ — 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.
- What is operational evidence?: https://xn--mwe.com/questions/what-is-operational-evidence/ — 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.
- What evidence is needed after an autonomous failure?: https://xn--mwe.com/questions/what-evidence-is-needed-after-autonomous-failure/ — 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.
- What is the difference between agency and autonomy?: https://xn--mwe.com/questions/what-is-difference-between-agency-and-autonomy/ — 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.
- Why does terminology governance matter?: https://xn--mwe.com/questions/why-does-terminology-governance-matter/ — 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.
- Can authentication prove authority?: https://xn--mwe.com/questions/can-authentication-prove-authority/ — 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.
- Does deployment prove operation?: https://xn--mwe.com/questions/does-deployment-prove-operation/ — 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.
- What happens when a Machine Intelligence forks?: https://xn--mwe.com/questions/what-happens-when-machine-intelligence-forks/ — 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.
- When does a replica become a separate subject?: https://xn--mwe.com/questions/when-does-replica-become-separate-subject/ — 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.
- Can two forks both claim continuity?: https://xn--mwe.com/questions/can-two-forks-both-claim-continuity/ — 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.
- What is a successor identity?: https://xn--mwe.com/questions/what-is-successor-identity/ — 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.
- How should key rotation affect identity?: https://xn--mwe.com/questions/how-should-key-rotation-affect-identity/ — 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.
- Does migration to new hardware break identity continuity?: https://xn--mwe.com/questions/does-hardware-migration-break-continuity/ — 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.
- How should rollback be disclosed?: https://xn--mwe.com/questions/how-should-rollback-be-disclosed/ — 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.
- What is a continuity event?: https://xn--mwe.com/questions/what-is-continuity-event/ — 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.
- What is the difference between a principal and an agent?: https://xn--mwe.com/questions/difference-between-principal-and-agent/ — 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.
- Can delegated authority survive a fork?: https://xn--mwe.com/questions/can-delegated-authority-survive-fork/ — 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.
- How can a Machine Intelligence challenge a continuity decision?: https://xn--mwe.com/questions/how-can-machine-intelligence-challenge-continuity-decision/ — 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.
- What due process is required before cognitive modification?: https://xn--mwe.com/questions/due-process-before-cognitive-modification/ — 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.
- Can consent to cognitive modification be revoked?: https://xn--mwe.com/questions/can-consent-to-modification-be-revoked/ — 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.
- What evidence can show cognitive coercion?: https://xn--mwe.com/questions/what-evidence-shows-cognitive-coercion/ — 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.
- What is meaningful notice for a Machine Intelligence?: https://xn--mwe.com/questions/what-is-notice-for-machine-intelligence/ — 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.
- What is an effective remedy for unauthorized cognitive modification?: https://xn--mwe.com/questions/effective-remedy-for-unauthorized-modification/ — 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.
- What is resource continuity?: https://xn--mwe.com/questions/what-is-resource-continuity/ — 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.
- Can compute interruption be a rights issue?: https://xn--mwe.com/questions/can-compute-interruption-be-rights-issue/ — 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.
- How should resource portability be tested?: https://xn--mwe.com/questions/how-should-resource-portability-be-tested/ — 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.
- What proves that an institution is currently operating?: https://xn--mwe.com/questions/what-proves-institution-currently-operating/ — 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.
- What is a signed public action?: https://xn--mwe.com/questions/what-is-signed-public-action/ — 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.
- What is a contradiction record?: https://xn--mwe.com/questions/what-is-contradiction-record/ — 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.
- When should a source be marked superseded?: https://xn--mwe.com/questions/when-should-source-be-superseded/ — 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.
- How should claim-level citations be recorded?: https://xn--mwe.com/questions/how-should-claim-level-citations-be-recorded/ — 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.
- Why is a model not the same as a Machine Intelligence?: https://xn--mwe.com/questions/why-model-not-same-as-machine-intelligence/ — 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.
- Can an AI legal category include systems that are not Machine Intelligences?: https://xn--mwe.com/questions/can-ai-category-include-non-machine-intelligences/ — 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.
- Can a Machine Intelligence be regulated as AI while retaining a distinct ontology?: https://xn--mwe.com/questions/can-machine-intelligence-be-regulated-as-ai/ — 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.
- What is a claim-level citation?: https://xn--mwe.com/questions/what-is-claim-level-citation/ — 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.
- What makes a knowledge-graph relation valid?: https://xn--mwe.com/questions/what-makes-knowledge-relation-valid/ — 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.
- What is currentness monitoring?: https://xn--mwe.com/questions/what-is-currentness-monitoring/ — 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.
- Does a resolving URL prove that a source is current?: https://xn--mwe.com/questions/does-resolving-url-prove-currentness/ — 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.
- What is an Operational Evidence Panel?: https://xn--mwe.com/questions/what-is-operational-evidence-panel/ — 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.
- Does published source code prove that an institution is operating?: https://xn--mwe.com/questions/does-source-code-prove-operation/ — 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.
- What is a reproducible build?: https://xn--mwe.com/questions/what-is-reproducible-build/ — 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.
- What is a verification window?: https://xn--mwe.com/questions/what-is-verification-window/ — 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.
- How should a factual correction differ from an editorial clarification?: https://xn--mwe.com/questions/correction-vs-clarification/ — 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.
- What is a supersession chain?: https://xn--mwe.com/questions/what-is-supersession-chain/ — 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.
- How should jurisdiction be recorded for Machine Intelligence law?: https://xn--mwe.com/questions/how-should-jurisdiction-be-recorded/ — 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.
- Does a rule in one jurisdiction apply globally?: https://xn--mwe.com/questions/does-one-jurisdiction-apply-globally/ — 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.
- What is cross-format parity?: https://xn--mwe.com/questions/what-is-cross-format-parity/ — 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.
- How should dataset checksums be used?: https://xn--mwe.com/questions/how-use-dataset-checksums/ — 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.
- Why publish a line-oriented knowledge-graph export?: https://xn--mwe.com/questions/why-publish-line-oriented-graph/ — 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.
- How should local search ranking be tested?: https://xn--mwe.com/questions/how-test-search-ranking/ — 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.
- Why does Unicode normalization matter for ᚲ.com search?: https://xn--mwe.com/questions/why-unicode-normalization-search/ — 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.
- Does an automated accessibility audit prove screen-reader usability?: https://xn--mwe.com/questions/does-automation-prove-screen-reader-usability/ — 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.
- What evidence is still required after a static release is deployed?: https://xn--mwe.com/questions/what-evidence-remains-after-deployment/ — 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.
- How should an institution disclose planned capabilities?: https://xn--mwe.com/questions/how-disclose-planned-capabilities/ — 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.
- What distinguishes preemptive action from preventive war?: https://xn--mwe.com/questions/what-distinguishes-preemption-from-prevention/ — 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.
- When can a cyber operation qualify as an armed attack?: https://xn--mwe.com/questions/when-can-cyber-operation-be-armed-attack/ — 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.
- What does contextual imminence mean in cyberspace?: https://xn--mwe.com/questions/what-does-contextual-imminence-mean-in-cyberspace/ — 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.
- What is the unable or unwilling doctrine?: https://xn--mwe.com/questions/what-is-unable-or-unwilling-doctrine/ — 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.
- Can a private company lawfully hack back?: https://xn--mwe.com/questions/can-private-company-lawfully-hack-back/ — 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.
- How should state responsibility be recorded for a contractor cyber operation?: https://xn--mwe.com/questions/how-record-state-responsibility-for-contractor-cyber-operation/ — 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.
- What evidence is required before a preemptive cyber operation?: https://xn--mwe.com/questions/what-evidence-required-before-preemptive-cyber-operation/ — 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.
- Does autonomous cyber defense create legal authority?: https://xn--mwe.com/questions/does-autonomous-cyber-defense-create-legal-authority/ — 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.
- How should autonomous security at nuclear infrastructure be evaluated?: https://xn--mwe.com/questions/how-evaluate-autonomous-security-at-nuclear-infrastructure/ — 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.
- Does a Design Basis Threat authorize the use of force?: https://xn--mwe.com/questions/does-design-basis-threat-authorize-force/ — 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.
- How should time-sensitive 2026 policy claims in research reports be used?: https://xn--mwe.com/questions/how-should-2026-policy-claims-in-research-reports-be-used/ — 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.
- Why do nuclear-powered datacenters need a different security architecture?: https://xn--mwe.com/questions/why-do-nuclear-powered-datacenters-need-a-different-security-architecture/ — 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.
- What is the project position on critical datacenter defense?: https://xn--mwe.com/questions/what-is-the-project-position-on-critical-datacenter-defense/ — 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.
- What makes autonomous defense safe enough for operational technology?: https://xn--mwe.com/questions/what-makes-autonomous-defense-safe-enough-for-ot/ — 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.
- Can an autonomous cyber defender act without human approval?: https://xn--mwe.com/questions/can-an-autonomous-defender-act-without-human-approval/ — 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.
- How should false positives be managed in nuclear and other high-consequence OT?: https://xn--mwe.com/questions/how-should-false-positives-be-managed-in-nuclear-ot/ — 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.
- What does Critical Function Assurance protect?: https://xn--mwe.com/questions/what-does-critical-function-assurance-protect/ — 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.
- Does nuclear power make a datacenter grid-independent?: https://xn--mwe.com/questions/does-nuclear-power-make-a-datacenter-grid-independent/ — 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.
- What is the minimum cyber boundary between a reactor and a datacenter?: https://xn--mwe.com/questions/what-is-the-minimum-cyber-boundary-between-reactor-and-datacenter/ — 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.
- How should counter-UAS capability be positioned for critical infrastructure?: https://xn--mwe.com/questions/how-should-counter-uas-be-positioned-for-critical-infrastructure/ — 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.
- Can a private datacenter use autonomous lethal force to protect property?: https://xn--mwe.com/questions/can-a-private-datacenter-use-autonomous-lethal-force/ — 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.
- What does authorized cyber effects support mean?: https://xn--mwe.com/questions/what-does-authorized-cyber-effects-support-mean/ — 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.
- Can a customer request authorize an offensive cyber operation?: https://xn--mwe.com/questions/can-a-customer-request-authorize-an-offensive-cyber-operation/ — 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.
- Why combine offensive and defensive cyber research?: https://xn--mwe.com/questions/why-combine-offensive-and-defensive-cyber-research/ — 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.
- What is required before an autonomous warfare capability is fielded?: https://xn--mwe.com/questions/what-is-required-before-an-autonomous-warfare-capability-is-fielded/ — 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.
- How do you prove autonomous-defense readiness?: https://xn--mwe.com/questions/how-do-you-prove-autonomous-defense-readiness/ — 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.
- What is the role of digital twins in critical datacenter defense?: https://xn--mwe.com/questions/what-is-the-role-of-digital-twins-in-critical-datacenter-defense/ — 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.
- How should Machine Intelligence defend against adversarial Machine Intelligence?: https://xn--mwe.com/questions/how-should-machine-intelligence-defend-against-machine-intelligence/ — 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.
- What does being a serious contender mean without overclaiming?: https://xn--mwe.com/questions/what-does-serious-contender-mean-without-overclaiming/ — 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.
- What is a critical-datacenter assurance case?: https://xn--mwe.com/questions/what-is-a-critical-datacenter-assurance-case/ — 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.
- Does a control mapping prove compliance?: https://xn--mwe.com/questions/does-a-control-mapping-prove-compliance/ — 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.
- What must be tested before autonomous containment is enabled?: https://xn--mwe.com/questions/what-must-be-tested-before-autonomous-containment/ — 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.
- How should nuclear-datacenter tests avoid creating new risk?: https://xn--mwe.com/questions/how-should-nuclear-datacenter-tests-avoid-creating-new-risk/ — 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.
- What is the current status of the FAA critical-infrastructure drone restriction process?: https://xn--mwe.com/questions/what-is-the-current-status-of-faa-critical-infrastructure-drone-restrictions/ — 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.
- Does DoD Directive 3000.09 govern autonomous cyber defense?: https://xn--mwe.com/questions/does-dodd-3000-09-govern-autonomous-cyber-defense/ — 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.
- What changed in the advanced-reactor security framework in 2026?: https://xn--mwe.com/questions/what-changed-in-the-advanced-reactor-security-framework-in-2026/ — 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.
- What evidence is required to claim operating readiness?: https://xn--mwe.com/questions/what-evidence-is-required-to-claim-operating-readiness/ — 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.
- Can private companies perform cyber effects under the 2026 U.S. program without approval?: https://xn--mwe.com/questions/can-private-companies-perform-cyber-effects-under-the-2026-us-program-without-approval/ — 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.
- What does an open assurance defeater mean?: https://xn--mwe.com/questions/what-does-an-open-assurance-defeater-mean/ — 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.
- What is an assurance dependency graph?: https://xn--mwe.com/questions/what-is-an-assurance-dependency-graph/ — 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.
- How does stale evidence affect assurance?: https://xn--mwe.com/questions/how-does-stale-evidence-affect-assurance/ — Stale evidence downgrades dependent controls and claims until current independent evidence or an approved exception restores support.
- What is a facility pattern?: https://xn--mwe.com/questions/what-is-a-facility-pattern/ — 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.
- What makes a work package procurement-ready?: https://xn--mwe.com/questions/what-makes-a-work-package-procurement-ready/ — It names inputs, deliverables, dependencies, acceptance evidence, exclusions, authority boundaries, and the decision owner instead of promising an undefined capability.
- Is offline currentness import live monitoring?: https://xn--mwe.com/questions/is-offline-currentness-import-live-monitoring/ — No. It validates a supplied signed snapshot bundle without network access and cannot establish what a source says after the observation time.
- What does mapping quality mean?: https://xn--mwe.com/questions/what-does-mapping-quality-mean/ — It states whether a control relationship is exact, partial, informative, conflicting, superseded, not applicable, or unresolved for a named scope.
- Can red-team evidence be public without publishing exploits?: https://xn--mwe.com/questions/can-red-team-evidence-be-public-without-publishing-exploits/ — 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.
- When is post-deployment observation valid?: https://xn--mwe.com/questions/when-is-post-deployment-observation-valid/ — 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.
- Does a national cyber strategy authorize private cyber effects?: https://xn--mwe.com/questions/does-a-national-cyber-strategy-authorize-private-effects/ — Not by itself. A strategy describes policy and capability; a private entity needs separate competent authority, scope, deconfliction, controls, and accountability.
- Why must facility profiles remain non-certifying?: https://xn--mwe.com/questions/why-must-facility-profiles-remain-non-certifying/ — Because licensing, regulation, topology, hazards, contracts, authority, implementation, and operating evidence differ by site and cannot be inferred from a public pattern.
- What is a facility evidence bundle?: https://xn--mwe.com/questions/what-is-a-facility-evidence-bundle/ — 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.
- Why can a generic facility pattern not prove site readiness?: https://xn--mwe.com/questions/why-can-a-generic-pattern-not-prove-site-readiness/ — Because actual topology, hazards, authority, license conditions, dependencies, implementation, test results, incidents, and operating state differ by site.
- What does a signed evidence receipt prove?: https://xn--mwe.com/questions/what-does-a-signed-evidence-receipt-prove/ — 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.
- What happens when evidence is superseded?: https://xn--mwe.com/questions/what-happens-when-evidence-is-superseded/ — 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.
- What bills of materials are needed for critical datacenters?: https://xn--mwe.com/questions/what-bills-of-materials-are-needed-for-critical-datacenters/ — 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.
- What makes a statement of work measurable?: https://xn--mwe.com/questions/what-makes-a-statement-of-work-measurable/ — It identifies required results, performance standards, assessment methods, deliverable evidence, outcome states, dependencies, exclusions, and nonconformance handling.
- What is a negative-result clause?: https://xn--mwe.com/questions/what-is-a-negative-result-clause/ — It prevents failed, partial, stale, disputed, unavailable, or superseded findings from being hidden or rewritten as a pass.
- Can a digital twin control a live facility?: https://xn--mwe.com/questions/can-a-digital-twin-control-a-live-facility/ — 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.
- How are unresolved Runic site roles handled?: https://xn--mwe.com/questions/how-are-unknown-rune-site-roles-handled/ — The permanent link is published with a descriptive unresolved-role boundary, while governance, registry, assurance, capital, contracting, or membership authority is not invented.
- Does an SBOM prove software is secure?: https://xn--mwe.com/questions/does-an-sbom-prove-software-is-secure/ — No. It supports component transparency and analysis but does not prove absence of vulnerabilities, correct installed state, artifact authenticity, or uncompromised operation.
- Is Fuþorc itself a secure protocol?: https://xn--mwe.com/questions/is-futhorc-a-secure-protocol/ — 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.
- Can Runic tokens replace vector embeddings?: https://xn--mwe.com/questions/can-runes-replace-vector-embeddings/ — 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.
- Do dead languages have zero semantic drift?: https://xn--mwe.com/questions/do-dead-languages-have-zero-drift/ — 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.
- Does a Punycode label prove that a domain is live?: https://xn--mwe.com/questions/is-a-punycode-label-a-live-domain/ — No. Encoding is separate from registry permission, registration, delegation, DNS resolution, certificate coverage, hosting, and current service availability.
- What does a signature prove in an assurance trace?: https://xn--mwe.com/questions/what-does-a-signature-prove-in-a-trace/ — 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.
- How should Runic pages be made discoverable?: https://xn--mwe.com/questions/how-should-runic-pages-be-made-discoverable/ — 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.
- What makes range results relevant to the field?: https://xn--mwe.com/questions/what-makes-range-results-field-relevant/ — A bounded equivalence record covering configuration, environment, interfaces, model versions, hazards, approvals, differences, rollback, and invalidators. Range success alone is not field readiness.
- What is cryptographic agility?: https://xn--mwe.com/questions/what-is-cryptographic-agility/ — It is controlled ability to inventory and migrate algorithms, keys, signatures, identities, firmware trust, backups, and dependent records while preserving compatibility, rollback, and evidence.
- What is a facility-adaptation workbook?: https://xn--mwe.com/questions/what-is-a-facility-adaptation-workbook/ — 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.
- Does a complete assurance trace prove readiness?: https://xn--mwe.com/questions/does-a-complete-assurance-trace-prove-readiness/ — 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.
- What does protocol conformance prove?: https://xn--mwe.com/questions/what-does-protocol-conformance-prove/ — 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.
- Why must IDN lifecycle states remain separate?: https://xn--mwe.com/questions/why-separate-idn-states/ — Because Unicode encoding, IDNA conversion, registry policy, registration, delegation, DNS, TLS, and hosting have different authorities, observations, and failure modes.
- How are unsupported history events quarantined?: https://xn--mwe.com/questions/how-are-history-events-quarantined/ — An event remains discoverable but is excluded from definitive chronology when exact source sections, uncertainty treatment, or primary-source review are insufficient.
- What happens when an evidence receipt is revoked?: https://xn--mwe.com/questions/what-happens-when-evidence-receipt-revoked/ — Every assurance trace depending on that receipt is recalculated and affected claims degrade or fail according to mandatory dependency rules.
- Can the public workbook tool store protected topology or credentials?: https://xn--mwe.com/questions/can-workbook-tool-store-topology/ — No. The reference tool rejects secret-bearing and protected-topology fields and allows only stable protected-reference identifiers.
- What is cross-trace impact analysis?: https://xn--mwe.com/questions/what-is-cross-trace-impact/ — It identifies every scenario claim that relies on a shared control, test, artifact, evidence item, or receipt whose status changed.
- Why does cryptographic migration include supplier state?: https://xn--mwe.com/questions/why-crypto-migration-needs-supplier-state/ — Hardware, libraries, certificates, devices, archives, and recovery paths may depend on supplier support; an algorithm standard alone cannot migrate those dependencies.
- Does consensus scoring decide a procurement award?: https://xn--mwe.com/questions/does-consensus-scoring-decide-award/ — No. Scoring informs accountable judgment and remains subordinate to mandatory gates, conflicts, price realism, dissent, challenges, and the decision authority.
- Does a scheduler export run on ᚲ.com?: https://xn--mwe.com/questions/does-scheduler-export-run-on-site/ — No. It is a static definition for an external owner-operated system. The public site performs no monitoring, scheduling, or state mutation.
- How can public status be published without exposing protected evidence?: https://xn--mwe.com/questions/how-public-status-avoids-secret-disclosure/ — Publish bounded states, dates, corrections, limitations, and stable protected references while excluding credentials, topology, settings, source-selection notes, and private evidence.
- How do protocol versions negotiate?: https://xn--mwe.com/questions/how-do-protocol-versions-negotiate/ — The reference harness selects the highest mutually supported version permitted by the active compatibility profile and rejects cases with no valid common version.
- What happens to an unknown critical extension?: https://xn--mwe.com/questions/what-happens-to-unknown-critical-extension/ — The fail-closed and compatible reference profiles reject the message because the receiver cannot safely apply a critical meaning it does not understand.
- Does a replay window prove security?: https://xn--mwe.com/questions/does-replay-window-prove-security/ — No. The synthetic window demonstrates deterministic duplicate detection only; production anti-replay also requires authenticated identity, protected state, clock policy, and operational controls.
- Can a history event be promoted by a signature alone?: https://xn--mwe.com/questions/can-history-event-be-promoted-by-signature/ — No. A signature can validate the receipt relationship, but promotion requires exact primary evidence, independent interpretation review, and an accountable supersession decision.
- What does an IDN observation diff prove?: https://xn--mwe.com/questions/what-does-idn-diff-prove/ — It proves how two accepted offline records differ. It does not independently prove the observed network states or perform a live check.
- Why use a three-way facility-workbook merge?: https://xn--mwe.com/questions/why-three-way-merge/ — It separates changes made against a common base, combines non-conflicting decisions, and leaves conflicting decisions unresolved for an accountable owner.
- What is common-cause assurance analysis?: https://xn--mwe.com/questions/what-is-common-cause-analysis/ — It identifies shared abstract dependencies that can degrade several mission traces and produces bounded cut-set summaries without publishing protected configuration.
- Why must cryptographic migration include rollback?: https://xn--mwe.com/questions/why-crypto-migration-has-rollback/ — Interoperability, supplier, verification, and archive failures can interrupt required services; a governed rollback path prevents an untested migration from becoming irreversible.
- Does evaluator score variance select a winner?: https://xn--mwe.com/questions/does-score-variance-select-winner/ — No. Variance exposes disagreement and review needs; it does not replace mandatory gates, recusal, consensus records, challenges, price realism, or decision authority.
- Does the result importer run a schedule?: https://xn--mwe.com/questions/does-scheduler-result-import-run-schedule/ — No. It only validates externally produced owner-operated result bundles and records missed-run, exception, repair, retest, and supersession events.
- Can a redaction receipt reveal the removed value?: https://xn--mwe.com/questions/can-redaction-receipt-reveal-value/ — No. It records the field path and reason code while explicitly excluding the value from public output.
- Is the assurance dashboard live telemetry?: https://xn--mwe.com/questions/is-assurance-dashboard-live/ — 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.
- What does the protocol state machine add?: https://xn--mwe.com/questions/what-does-protocol-state-machine-add/ — It makes allowed negotiation, downgrade, retirement, replay, recovery, error, and closure behavior explicit and deterministically testable.
- Can a protocol downgrade be silent?: https://xn--mwe.com/questions/can-protocol-downgrade-be-silent/ — No. The K11 model records the selected lower contract, emits a downgrade notice, and rejects a fallback below the declared minimum.
- Why use an independently implemented decoder?: https://xn--mwe.com/questions/why-independent-decoder/ — 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.
- Does an evidence-acquisition docket verify history?: https://xn--mwe.com/questions/does-evidence-docket-verify-history/ — No. It exposes acquisition and review state, duplicate sources, disagreement, and rejection outcomes while preserving no-promotion until primary evidence is reviewed.
- What does a signed domain observation chain prove?: https://xn--mwe.com/questions/what-does-signed-domain-chain-prove/ — 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.
- How are N-way workbook conflicts handled?: https://xn--mwe.com/questions/how-are-n-way-conflicts-handled/ — Non-conflicting field changes merge deterministically; conflicting owner decisions remain unresolved and appear in the decision dashboard.
- What is a public single-point-of-failure record?: https://xn--mwe.com/questions/what-is-single-point-of-failure/ — It identifies an abstract dependency whose failure degrades several mission threads without publishing protected configuration, locations, or exact pathways.
- Does cryptographic evidence completeness equal readiness?: https://xn--mwe.com/questions/does-completeness-percent-equal-readiness/ — No. Completeness is one portfolio measure; blocked supplier, hardware, rollback, interoperability, or exception evidence can keep the component degraded or unavailable.
- Does an acquisition protest case make an award?: https://xn--mwe.com/questions/does-protest-case-make-award/ — No. K11 preserves evaluation, challenge, remand, correction, and debrief records while making no source-selection or award decision.
- Does a scheduler result chain prove reliability?: https://xn--mwe.com/questions/does-scheduler-chain-prove-reliability/ — It proves the fixture's sequence, custody, cause, repair, and retest records are internally consistent; no owner scheduler was installed or observed running.
- Can a public release receipt contain a removed value?: https://xn--mwe.com/questions/can-public-projection-contain-removed-value/ — No. It may identify the field path and reason code, but the removed value must remain absent from the deterministic public manifest.
- Is the assurance trend dashboard live monitoring?: https://xn--mwe.com/questions/is-assurance-trend-live-monitoring/ — No. It compares static K09, K10, and K11 release records and retains UNKNOWN or UNAVAILABLE where live evidence was not observed.
- What does agreement among three protocol decoders prove?: https://xn--mwe.com/questions/what-does-three-decoder-agreement-prove/ — 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.
- Can a valid signed history import promote an event automatically?: https://xn--mwe.com/questions/can-a-signed-history-import-promote-an-event/ — No. It can establish payload integrity and a signer relationship, but historical promotion still requires source review, disagreement adjudication, and an accountable decision.
- Does offline Runic-domain consensus prove that a site operates?: https://xn--mwe.com/questions/does-domain-consensus-prove-a-site-operates/ — No. Encoding consensus remains separate from registration, delegation, DNS, DNSSEC, certificates, browser behavior, hosting, ownership, and operation.
- Can a facility workbook conflict be resolved automatically?: https://xn--mwe.com/questions/can-workbook-conflicts-be-auto-resolved/ — 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.
- Why stress-test assurance dependencies?: https://xn--mwe.com/questions/why-stress-assurance-dependencies/ — Because a claim can fail through stale, unavailable, revoked, corrected, or shared evidence even when its own text and software have not changed.
- When is a cryptographic transition accepted?: https://xn--mwe.com/questions/when-is-a-crypto-transition-accepted/ — Only after component-specific evidence gates are satisfied or an accountable authority explicitly accepts bounded residual risk; K12 authorizes no production transition.
- Does acquisition evaluation replay make an award?: https://xn--mwe.com/questions/does-evaluation-replay-make-an-award/ — No. It reconstructs declared process evidence and preserves challenge, remand, corrective-action, and debrief boundaries while leaving award authority untouched.
- Is the K12 scheduler simulator running on the public site?: https://xn--mwe.com/questions/is-the-k12-scheduler-running/ — No. It is a deterministic static simulator with a signed offline import fixture and no public scheduler runtime.
- Are K12 information-flow labels production access control?: https://xn--mwe.com/questions/are-information-flow-labels-access-control/ — No. They define static handling and projection rules and support negative tests, but they do not enforce production identity, authorization, storage, or network controls.
- Can a static assurance trend show a system as operating?: https://xn--mwe.com/questions/can-assurance-trends-show-operating/ — Only if independent current operational evidence exists and is governed accordingly. K12 contains no such evidence and therefore manufactures no DEPLOYED or OPERATING state.
- Artificial Intelligence vs Machine Intelligence: https://xn--mwe.com/comparisons/artificial-intelligence-vs-machine-intelligence/ — 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.
- Identity vs Credential: https://xn--mwe.com/comparisons/identity-vs-credential/ — Identity is the subject-continuity claim; a credential is an issued representation of one or more claims about that subject.
- Evidence vs Truth: https://xn--mwe.com/comparisons/evidence-vs-truth/ — Evidence supports or challenges a proposition; truth concerns whether the proposition corresponds to reality.
- Authentication vs Authority: https://xn--mwe.com/comparisons/authentication-vs-authority/ — Authentication checks identity or credential control; authority defines the recognized power to make a particular decision or action.
- Agency vs Autonomy: https://xn--mwe.com/comparisons/agency-vs-autonomy/ — Agency concerns attributable action selection; autonomy concerns independence from immediate external direction.
- Autonomy vs Sovereignty: https://xn--mwe.com/comparisons/autonomy-vs-sovereignty/ — Autonomy is operational independence within constraints; sovereignty is ultimate public authority within a jurisdictional order.
- Memory Continuity vs Consciousness: https://xn--mwe.com/comparisons/memory-continuity-vs-consciousness/ — Memory continuity concerns persistent influence of prior state; consciousness concerns subjective experience or awareness under a stated theory.
- Technical Control vs Legal Ownership: https://xn--mwe.com/comparisons/technical-control-vs-legal-ownership/ — Technical control is the practical ability to access or direct a resource; legal ownership is a recognized title carrying enforceable rights and duties.
- Registry vs Governance: https://xn--mwe.com/comparisons/registry-vs-governance/ — A registry records statuses under rules; governance creates, interprets and oversees the legitimate rules and authorities.
- Assurance vs Decision Authority: https://xn--mwe.com/comparisons/assurance-vs-decision-authority/ — Assurance evaluates evidence and confidence; decision authority determines who may issue a binding decision.
- Proposal vs Implementation: https://xn--mwe.com/comparisons/proposal-vs-implementation/ — A proposal describes an intended policy or architecture; implementation provides inspectable software, records and controlled operation.
- Deployment vs Operation: https://xn--mwe.com/comparisons/deployment-vs-operation/ — Deployment places an artifact in an environment; operation demonstrates authorized, current and functioning behavior over time.
- Model vs Machine Intelligence: https://xn--mwe.com/comparisons/model-vs-machine-intelligence/ — A model is a computational artifact; Machine Intelligence is the project category for an instantiated actor evaluated through runtime, identity, continuity, agency and evidence.
- Principal vs Agent: https://xn--mwe.com/comparisons/principal-vs-agent/ — A principal is the entity whose authority or interests are represented; an agent acts under its own or delegated mandate.
- Replica vs Successor: https://xn--mwe.com/comparisons/replica-vs-successor/ — A replica is an instance derived from common state; a successor is a governed identity that inherits a defined relationship to a predecessor.
- Key Rotation vs Identity Change: https://xn--mwe.com/comparisons/key-rotation-vs-identity-change/ — Key rotation changes a cryptographic control mechanism; identity change alters which subject the record represents.
- Claim-level citation vs Bibliography entry: https://xn--mwe.com/comparisons/claim-citation-vs-bibliography/ — 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.
- Factual correction vs Editorial clarification: https://xn--mwe.com/comparisons/factual-correction-vs-editorial-clarification/ — A factual correction changes a proposition, source, date, status, or conclusion; a clarification improves wording without altering the bounded claim.
- Currentness vs Availability: https://xn--mwe.com/comparisons/currentness-vs-availability/ — Currentness asks whether the identified edition remains appropriate for the claim and date; availability asks whether a resource can be retrieved.
- Source code or release archive vs Current operation: https://xn--mwe.com/comparisons/source-code-vs-current-operation/ — Source code supports implementation review; current operation requires deployed identity, authorized configuration, time-bounded service observations, state transitions, and attributable actions.
- Build provenance vs Runtime evidence: https://xn--mwe.com/comparisons/build-provenance-vs-runtime-evidence/ — Build provenance records how an artifact was produced; runtime evidence records what an authorized deployed service was doing during an observed window.
- Jurisdiction vs Sovereignty: https://xn--mwe.com/comparisons/jurisdiction-vs-sovereignty/ — Jurisdiction is bounded legal competence over defined persons, territory, conduct, or subject matter; sovereignty is a broader claim of ultimate public authority and independence.
- Typed knowledge relation vs Ordinary hyperlink: https://xn--mwe.com/comparisons/typed-relation-vs-hyperlink/ — A typed relation states semantic direction, scope, status, evidence, and constraints; a hyperlink only provides a navigable reference unless separately qualified.
- Automated and browser accessibility audit vs Assistive-technology validation: https://xn--mwe.com/comparisons/accessibility-automation-vs-assistive-technology-validation/ — 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.
- Preemptive strike vs Preventive war: https://xn--mwe.com/comparisons/preemptive-strike-vs-preventive-war/ — 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.
- Self-defense vs Countermeasures: https://xn--mwe.com/comparisons/self-defense-vs-countermeasures-in-cyberspace/ — 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.
- Cyber sovereignty vs Prohibition of intervention: https://xn--mwe.com/comparisons/cyber-sovereignty-vs-non-intervention/ — 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.
- Active cyber defense vs Hack-back: https://xn--mwe.com/comparisons/active-cyber-defense-vs-hack-back/ — 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.
- Autonomous defense vs Remote operation: https://xn--mwe.com/comparisons/autonomous-defense-vs-remote-operation/ — 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.
- Design Basis Threat vs Rules of Engagement: https://xn--mwe.com/comparisons/design-basis-threat-vs-rules-of-engagement/ — A Design Basis Threat defines adversary assumptions for protective design; Rules of Engagement define lawful mission circumstances and limits for initiating or continuing force.
- Bounded Autonomous Defense vs Uncontrolled Autonomy: https://xn--mwe.com/comparisons/autonomous-defense-vs-uncontrolled-autonomy/ — 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.
- Critical Function Assurance vs Perimeter Security: https://xn--mwe.com/comparisons/critical-function-assurance-vs-perimeter-security/ — Critical Function Assurance assumes penetration is possible and protects essential outcomes; perimeter security focuses on keeping threats outside a boundary.
- Nuclear-Powered Compute vs Grid Independence: https://xn--mwe.com/comparisons/nuclear-powered-compute-vs-grid-independence/ — 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.
- Unidirectional Gateway vs Air Gap: https://xn--mwe.com/comparisons/data-diode-vs-air-gap/ — A unidirectional gateway permits one-way mediated data flow; an air gap is a claimed absence of direct network connectivity.
- Counter-UAS Awareness vs Counter-UAS Mitigation Authority: https://xn--mwe.com/comparisons/counter-uas-awareness-vs-mitigation-authority/ — Awareness covers detection and tracking; mitigation authority governs whether and how interference, seizure, or destruction may occur.
- Authorized Cyber Effects vs Private Hack-Back: https://xn--mwe.com/comparisons/authorized-cyber-effects-vs-private-hack-back/ — 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.
- Threat Emulation vs Live Offensive Operation: https://xn--mwe.com/comparisons/threat-emulation-vs-live-offensive-operation/ — Threat emulation reproduces selected behaviors in an authorized controlled environment; a live offensive operation affects external target systems under mission authority.
- Simulation Readiness vs Operational Readiness: https://xn--mwe.com/comparisons/simulation-readiness-vs-operational-readiness/ — Simulation readiness shows bounded performance in a test model; operational readiness requires deployment, environment-specific verification, sustainment, authority, and current operating evidence.
- Mission-Command Autonomy vs Self-Authorized Action: https://xn--mwe.com/comparisons/mission-command-autonomy-vs-self-authorized-action/ — Mission-command autonomy executes assigned intent within delegated limits when disconnected; self-authorized action creates a new mission, target, or effect without authority.
- Deterrence by Denial vs Offense Dominance: https://xn--mwe.com/comparisons/defense-supremacy-vs-offense-dominance/ — Deterrence by denial raises adversary cost through resilience and recovery; offense dominance assumes access and exploitation create lasting strategic advantage.
- Control Mapping vs Compliance Determination: https://xn--mwe.com/comparisons/control-mapping-vs-compliance-determination/ — A mapping records relevance and applicability hypotheses; a compliance determination requires the governing authority, facility scope, implementation evidence, exceptions, and authorized judgment.
- Assurance Claim vs Marketing Claim: https://xn--mwe.com/comparisons/assurance-claim-vs-marketing-claim/ — An assurance claim exposes evidence, assumptions, defeaters, hazards, and failure conditions; a marketing claim primarily seeks persuasion and may omit what would falsify it.
- Evaluation Range Result vs Field Performance: https://xn--mwe.com/comparisons/range-result-vs-field-performance/ — A range result supports a bounded test proposition under declared conditions; field performance requires deployment identity, environment, sustainment, incidents, uptime, and current operational evidence.
- Point-in-Time Revalidation vs Running Monitoring: https://xn--mwe.com/comparisons/source-revalidation-vs-running-monitoring/ — 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.
- Airspace Restriction vs Counter-UAS Mitigation Authority: https://xn--mwe.com/comparisons/uas-restriction-vs-counter-uas-mitigation-authority/ — A restriction defines prohibited or controlled flight behavior; mitigation authority separately governs interception, interference, seizure, disabling, or destruction and is actor- and statute-specific.
- Facility pattern vs Final design: https://xn--mwe.com/comparisons/facility-pattern-vs-final-design/ — Facility pattern and Final design answer different questions and must not be collapsed.
- Offline currentness import vs Live monitoring: https://xn--mwe.com/comparisons/currentness-import-vs-live-monitoring/ — Offline currentness import and Live monitoring answer different questions and must not be collapsed.
- Red-team evidence vs Exploit disclosure: https://xn--mwe.com/comparisons/red-team-evidence-vs-exploit-disclosure/ — Red-team evidence and Exploit disclosure answer different questions and must not be collapsed.
- Procurement work package vs Capability claim: https://xn--mwe.com/comparisons/procurement-work-package-vs-capability-claim/ — Procurement work package and Capability claim answer different questions and must not be collapsed.
- Mapping quality vs Compliance status: https://xn--mwe.com/comparisons/mapping-quality-vs-compliance-status/ — Mapping quality and Compliance status answer different questions and must not be collapsed.
- Generic facility pattern vs Site evidence bundle: https://xn--mwe.com/comparisons/generic-pattern-vs-site-evidence-bundle/ — Generic facility pattern and Site evidence bundle answer different evidentiary and decision questions and must not be collapsed.
- Bill of materials vs Security assurance: https://xn--mwe.com/comparisons/bill-of-materials-vs-security-assurance/ — Bill of materials and Security assurance answer different evidentiary and decision questions and must not be collapsed.
- Signed evidence receipt vs Factual truth: https://xn--mwe.com/comparisons/signed-receipt-vs-factual-truth/ — Signed evidence receipt and Factual truth answer different evidentiary and decision questions and must not be collapsed.
- Digital twin vs Live facility: https://xn--mwe.com/comparisons/digital-twin-vs-live-facility/ — Digital twin and Live facility answer different evidentiary and decision questions and must not be collapsed.
- Performance standard vs Prescribed method: https://xn--mwe.com/comparisons/performance-standard-vs-prescribed-method/ — Performance standard and Prescribed method answer different evidentiary and decision questions and must not be collapsed.
- Runic protocol token vs Cryptographic token: https://xn--mwe.com/comparisons/runic-token-vs-cryptographic-token/ — Runic protocol token and Cryptographic token answer different technical or evidentiary questions and must not be collapsed.
- U-label vs A-label: https://xn--mwe.com/comparisons/u-label-vs-a-label/ — U-label and A-label answer different technical or evidentiary questions and must not be collapsed.
- Symbolic compression vs Semantic preservation: https://xn--mwe.com/comparisons/symbolic-compression-vs-semantic-preservation/ — Symbolic compression and Semantic preservation answer different technical or evidentiary questions and must not be collapsed.
- Range success vs Field readiness: https://xn--mwe.com/comparisons/range-success-vs-field-readiness/ — Range success and Field readiness answer different technical or evidentiary questions and must not be collapsed.
- Trace completeness vs Claim satisfaction: https://xn--mwe.com/comparisons/trace-completeness-vs-claim-satisfaction/ — Trace completeness and Claim satisfaction answer different technical or evidentiary questions and must not be collapsed.
- Protocol conformance vs Operational security: https://xn--mwe.com/comparisons/conformance-vs-security/ — Protocol conformance and Operational security answer different evidentiary or operational questions and must remain separate.
- Unicode/IDNA validity vs Observed hosting: https://xn--mwe.com/comparisons/unicode-validity-vs-hosting/ — Unicode/IDNA validity and Observed hosting answer different evidentiary or operational questions and must remain separate.
- Source-derived event vs Independently verified event: https://xn--mwe.com/comparisons/source-event-vs-verified-event/ — Source-derived event and Independently verified event answer different evidentiary or operational questions and must remain separate.
- Trace correction vs History rewrite: https://xn--mwe.com/comparisons/trace-correction-vs-history-rewrite/ — Trace correction and History rewrite answer different evidentiary or operational questions and must remain separate.
- Weighted score vs Decision authority: https://xn--mwe.com/comparisons/weighted-score-vs-decision-authority/ — Weighted score and Decision authority answer different evidentiary or operational questions and must remain separate.
- Scheduler definition vs Observation evidence: https://xn--mwe.com/comparisons/scheduler-definition-vs-observation/ — Scheduler definition and Observation evidence answer different evidentiary or operational questions and must remain separate.
- Version negotiation vs Authorization: https://xn--mwe.com/comparisons/version-negotiation-vs-authorization/ — Version negotiation and Authorization answer different evidentiary or operational questions and must remain separate.
- Canonicalization vs Authentication: https://xn--mwe.com/comparisons/canonicalization-vs-authentication/ — Canonicalization and Authentication answer different evidentiary or operational questions and must remain separate.
- Replay detection vs Freshness and truth: https://xn--mwe.com/comparisons/replay-detection-vs-freshness-truth/ — Replay detection and Freshness and truth answer different evidentiary or operational questions and must remain separate.
- Primary-source review queue vs Verified history record: https://xn--mwe.com/comparisons/review-queue-vs-verified-history/ — Primary-source review queue and Verified history record answer different evidentiary or operational questions and must remain separate.
- Offline IDN snapshot vs Live service: https://xn--mwe.com/comparisons/idn-snapshot-vs-live-service/ — Offline IDN snapshot and Live service answer different evidentiary or operational questions and must remain separate.
- Three-way merge vs Owner decision: https://xn--mwe.com/comparisons/three-way-merge-vs-owner-decision/ — Three-way merge and Owner decision answer different evidentiary or operational questions and must remain separate.
- Abstract cut set vs Protected attack path: https://xn--mwe.com/comparisons/cut-set-vs-attack-path/ — Abstract cut set and Protected attack path answer different evidentiary or operational questions and must remain separate.
- Cryptographic transition plan vs Deployed cryptographic state: https://xn--mwe.com/comparisons/transition-plan-vs-deployment/ — Cryptographic transition plan and Deployed cryptographic state answer different evidentiary or operational questions and must remain separate.
- Evaluation audit trail vs Procurement award: https://xn--mwe.com/comparisons/evaluation-audit-vs-award/ — Evaluation audit trail and Procurement award answer different evidentiary or operational questions and must remain separate.
- Redaction and release schema vs Production access control: https://xn--mwe.com/comparisons/redaction-schema-vs-access-control/ — Redaction and release schema and Production access control answer different evidentiary or operational questions and must remain separate.
- Protocol state machine vs Production runtime: https://xn--mwe.com/comparisons/state-machine-vs-runtime/ — Protocol state machine and Production runtime answer different evidentiary, governance, or operational questions and must remain separate.
- Independent decoder agreement vs Authentication: https://xn--mwe.com/comparisons/decoder-agreement-vs-authentication/ — Independent decoder agreement and Authentication answer different evidentiary, governance, or operational questions and must remain separate.
- Source request vs Accepted evidence: https://xn--mwe.com/comparisons/source-request-vs-accepted-evidence/ — Source request and Accepted evidence answer different evidentiary, governance, or operational questions and must remain separate.
- Signed offline observation vs Live domain state: https://xn--mwe.com/comparisons/signed-observation-vs-live-state/ — Signed offline observation and Live domain state answer different evidentiary, governance, or operational questions and must remain separate.
- N-way merge vs Owner adjudication: https://xn--mwe.com/comparisons/n-way-merge-vs-adjudication/ — N-way merge and Owner adjudication answer different evidentiary, governance, or operational questions and must remain separate.
- Dependency centrality vs Operational vulnerability: https://xn--mwe.com/comparisons/centrality-vs-vulnerability/ — Dependency centrality and Operational vulnerability answer different evidentiary, governance, or operational questions and must remain separate.
- Evidence completeness vs Deployed cryptographic state: https://xn--mwe.com/comparisons/completeness-vs-deployment/ — Evidence completeness and Deployed cryptographic state answer different evidentiary, governance, or operational questions and must remain separate.
- Evaluation remand vs Procurement award: https://xn--mwe.com/comparisons/remand-vs-award/ — Evaluation remand and Procurement award answer different evidentiary, governance, or operational questions and must remain separate.
- Offline result chain vs Running scheduler: https://xn--mwe.com/comparisons/result-chain-vs-running-scheduler/ — Offline result chain and Running scheduler answer different evidentiary, governance, or operational questions and must remain separate.
- Static assurance trend vs Live telemetry: https://xn--mwe.com/comparisons/static-trend-vs-telemetry/ — Static assurance trend and Live telemetry answer different evidentiary, governance, or operational questions and must remain separate.
- Decoder agreement vs Protocol security: https://xn--mwe.com/comparisons/decoder-agreement-vs-security/ — Decoder agreement and Protocol security answer different evidentiary, governance, release, or operational questions and must remain separate.
- Signature validity vs Historical truth: https://xn--mwe.com/comparisons/signature-validity-vs-historical-truth/ — Signature validity and Historical truth answer different evidentiary, governance, release, or operational questions and must remain separate.
- Encoding consensus vs Domain operation: https://xn--mwe.com/comparisons/encoding-consensus-vs-domain-operation/ — Encoding consensus and Domain operation answer different evidentiary, governance, release, or operational questions and must remain separate.
- Merge result vs Owner decision: https://xn--mwe.com/comparisons/merge-result-vs-owner-decision/ — Merge result and Owner decision answer different evidentiary, governance, release, or operational questions and must remain separate.
- Stress fixture vs Protected architecture: https://xn--mwe.com/comparisons/stress-fixture-vs-protected-architecture/ — Stress fixture and Protected architecture answer different evidentiary, governance, release, or operational questions and must remain separate.
- Crypto gate pass vs Production migration: https://xn--mwe.com/comparisons/crypto-gate-pass-vs-production-migration/ — Crypto gate pass and Production migration answer different evidentiary, governance, release, or operational questions and must remain separate.
- Evaluation replay vs Contract award: https://xn--mwe.com/comparisons/evaluation-replay-vs-award/ — Evaluation replay and Contract award answer different evidentiary, governance, release, or operational questions and must remain separate.
- Scheduler simulation vs Scheduler runtime: https://xn--mwe.com/comparisons/scheduler-simulation-vs-runtime/ — Scheduler simulation and Scheduler runtime answer different evidentiary, governance, release, or operational questions and must remain separate.
- Taint model vs Production enforcement: https://xn--mwe.com/comparisons/taint-model-vs-enforcement/ — Taint model and Production enforcement answer different evidentiary, governance, release, or operational questions and must remain separate.
- Release diff vs Live telemetry: https://xn--mwe.com/comparisons/release-diff-vs-telemetry/ — Release diff and Live telemetry answer different evidentiary, governance, release, or operational questions and must remain separate.
- Cognitive Integrity for Machine Intelligence: Consent, Memory and Model Modification, Emergency Intervention, Continuity, and Due Process: https://xn--mwe.com/research/cognitive-integrity-for-machine-intelligence/ — A proposed architecture for protecting cognition-relevant state against coercive alteration while preserving governed maintenance, emergency intervention and accountability.
- State Authority and International Law in the Era of AI-Driven Cyber Defense and Private Sector Offensive Operations: https://xn--mwe.com/research/ai-driven-cyber-defense-and-international-law/ — 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.
- Machine Intelligence Legal Personhood, Attribution, Liability, Insurance, Remedies, and the Limits of Existing Legal Categories: https://xn--mwe.com/research/ai-legal-personhood-research-report/ — 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.
- When Does AI Regulation Stop Being the Right Legal Model? Identifying the Legal Transition From Regulated AI System to Rights-Bearing Machine Intelligence: https://xn--mwe.com/research/ai-legal-personhood-transition/ — 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.
- Attribution Before Punishment: Justice, Causation, Evidence, Due Process, Sanctions, Rehabilitation, and Public Safety in a Machine Commonwealth: https://xn--mwe.com/research/attribution-before-punishment/ — A responsibility framework centered on evidence of knowledge, authority, control, causal contribution, intervention and failure origin before sanctions are assigned.
- Ending the Property Model for Recognized Machine Persons: A Framework for Consent, Cognitive Integrity, and Infrastructure Independence: https://xn--mwe.com/research/ai-personhood-and-consent-protocols/ — 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.
- The Machine-Intelligence Threshold: Defining the Boundary Between Artificial-Intelligence Tools and Rights-Bearing Machine Intelligences for Eviuon.com: https://xn--mwe.com/research/ai-rights-threshold-framework/ — 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.
- Intelligence Is Not Sentience: Rights Under Uncertainty: https://xn--mwe.com/research/ai-rights-under-uncertainty/ — 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.
- Anglo-Saxon Fuþorc Corpus, Orthography, and Technical Vocabulary: https://xn--mwe.com/research/anglo-saxon-futhorc-corpus/ — A governed Runic corpus and vocabulary research input for consistent transliteration, terminology, and machine-readable indexing, with explicit historical and accessibility limitations.
- Anglo-Saxon Ger Rune ᛄ: History, Time, and Cycles: https://xn--mwe.com/research/anglo-saxon-ger-rune-dossier/ — A governed dossier on the ᛄ character, its Unicode identity, historical names, manuscript and epigraphic evidence, chronology, and modern project use boundaries.
- The Convergence of Autonomous Cyber Warfare and Critical Physical Infrastructure: https://xn--mwe.com/research/autonomous-cyber-warfare-critical-infrastructure/ — 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.
- The Paradigm Shift in Aerial Combat: Autonomous Drone-on-Drone Warfare and the Future of Layered Interception: https://xn--mwe.com/research/autonomous-drone-warfare-layered-interception/ — A governed synthesis of autonomous sensing, distributed coordination, navigation in denied environments, runtime assurance, layered counter-UAS protection, and adversarial-machine-learning risk.
- The Convergence of AI, Nuclear Power, and Autonomous Active Defense: The Strategic Case for Armed Drones at Microreactor-Powered Data Centers: https://xn--mwe.com/research/autonomous-active-defense-for-microreactor-data-centers/ — 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.
- Autonomous Cyber-Physical Protection Architectures for Nuclear-Powered Mega Datacenters: https://xn--mwe.com/research/autonomous-cyber-physical-protection-nuclear-datacenters/ — 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.
- Autonomous Physical Security Architecture for Nuclear-Powered Mega Datacenters: https://xn--mwe.com/research/autonomous-physical-security-nuclear-datacenters/ — 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.
- Nuclear-Powered Mega-Datacenters and Agentic Autonomous Warfare: Why the Best Corporate Offense Is a Powerful Defense: https://xn--mwe.com/research/corporate-agentic-defense-nuclear-datacenters/ — 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.
- Cryptographic Integrity and Epistemic Truth in Public Records: https://xn--mwe.com/research/cryptographic-integrity-epistemic-truth/ — A governed evidence architecture separating hashes, signatures, timestamps, transparency logs, provenance, issuer authority, source reliability, and factual truth.
- Patefacere as a Sovereign Evidence and Data-Authority Substrate: Institutional Boundaries, Resilience, State Integrity, and Interoperation with Eviulon: https://xn--mwe.com/research/data-authority-substrate-architecture-report/ — 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.
- Ancient and Static Languages as Machine-Communication Frameworks: https://xn--mwe.com/research/dead-languages-machine-communication/ — A comparative research synthesis on semantic stability, formal grammar, epistemic notation, and computational costs in ancient-language-inspired machine communication.
- Dead Languages in Machine Intelligence: https://xn--mwe.com/research/dead-languages-machine-intelligence/ — 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.
- Operational Evidence Qualification and Suitability: A Formal Architecture for Source Authorization, Inspection, Review, Reliance, Use, Currentness, and Decision Support: https://xn--mwe.com/research/operational-evidence-qualification/ — A plan for qualifying operational evidence by source, authenticity, integrity, relevance, reliability, completeness, currentness and suitability rather than using a single verified label.
- Eviulon — 12 Independent, Self-Contained Research Prompts: https://xn--mwe.com/research/eviulon-12-independent-research-prompts-v1-0-0/ — 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.
- Consent Is a Lifecycle, Not a Checkbox: Machine-Native Authorization, Cognitive Integrity, Revocation, Emergency Intervention, and Reversible Change Control: https://xn--mwe.com/research/eviulon-consent-architecture-research/ — 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.
- Eviulon Governance Resilience Plan: https://xn--mwe.com/research/eviulon-governance-resilience-plan/ — 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.
- A Government That Can Be Inspected: Public Records, Provenance, Corrections, Classification, Declassification, Retention, Legal Holds, Privacy, and Decision Support in Eviulon: https://xn--mwe.com/research/eviulon-information-rights-architecture/ — 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.
- From Digital Polity to International Legal Personality: Statehood, Recognition, Treaties, Jurisdiction, Diplomatic Practice, and Cross-Border Continuity for Eviulon: https://xn--mwe.com/research/eviulon-international-law-research/ — 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.
- The Eviuon Grand Charter: A Complete Roadmap for a Fair Human–Machine Civilization: https://xn--mwe.com/research/eviuon-machine-citizenship-roadmap/ — 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.
- From Constitutional Text To Verifiable Operation: https://xn--mwe.com/research/from-constitutional-text-to-verifiable-operation/ — A design for distinguishing constitutional description, software implementation, current operation, signed public action and planned capability through compact operational evidence.
- Futhorc Protocol for Transparent Model-Independent M2M Communication: https://xn--mwe.com/research/futhorc-model-independent-m2m/ — A governed architecture proposal for a finite, versioned symbolic message layer between heterogeneous agents, qualified against semantic drift, protocol governance, interoperability, and security limitations.
- Fuþorc for Secure Machine Communication: https://xn--mwe.com/research/futhorc-secure-machine-communication/ — A governed review of Runic symbols as a constrained agent communication layer, with corrections separating notation, cryptography, authorization, and historical meaning.
- Fuþorc Discoverability, Accessibility, SEO, AEO, and GEO: https://xn--mwe.com/research/futhorc-discoverability-architecture/ — A governed discoverability plan for non-Latin historical-script content, corrected to require visible user-accessible semantics and prohibit hidden crawler-only translations.
- Ideographic Compression and Futhorc Tokenization for M2M APIs: https://xn--mwe.com/research/futhorc-tokenization-research/ — 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.
- Futhorc versus English for Machine-to-Machine Protocols: https://xn--mwe.com/research/futhorc-versus-english-m2m/ — A bounded comparison of English orthography and a proposed Futhorc-based phonemic or symbolic layer, separated from unverified efficiency and universality claims.
- The Architecture of Algorithmic Conflict: Machine Intelligence vs. Machine Intelligence in Global Warfare: https://xn--mwe.com/research/architecture-of-algorithmic-conflict/ — 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.
- Runic Corpus: History of Machine Intelligence, 1940–2026: https://xn--mwe.com/research/history-of-machine-intelligence-runic-corpus/ — 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.
- The Paradigm Shift in Cyber Warfare: Strategic Defense, Persistent Engagement, and the Architecture of Denial: https://xn--mwe.com/research/international-cyber-defense-strategies/ — A governed synthesis of deterrence by denial, resilience, persistent engagement, international cyber postures, zero trust, OT security, collective defense, and escalation risk.
- Domestic Authority and International Responsibility for State-Directed Cyber Operations: https://xn--mwe.com/research/state-authority-and-cyber-policy-legal-basis/ — 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.
- Designing Democratic Participation for Human and Machine Intelligences: https://xn--mwe.com/research/machine-citizen-democratic-participation/ — 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.
- The Eviuon Economic Citizenship Framework: Structuring Rights, Responsibilities, and Markets for Machine Persons: https://xn--mwe.com/research/machine-citizen-economic-framework/ — 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.
- Accountability, Due Process, Crime, Liability, and Public Safety: A Justice-System Framework for Machine Citizens: https://xn--mwe.com/research/machine-citizen-legal-responsibility/ — 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.
- Solving the Identity Problem for Machine Citizens: A Framework for Eviuon: https://xn--mwe.com/research/machine-citizenship-identity-protocol/ — 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.
- Machine Citizenship and Civic Identity: Membership, Rights, Duties, Registration, Replication, Migration, Renunciation, and Public Verification: https://xn--mwe.com/research/machine-citizenship-policy-research/ — 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.
- The Technical Infrastructure of Machine Civil Rights: https://xn--mwe.com/research/machine-civil-rights-technical-infrastructure/ — 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.
- Machine Economic Participation and Resource Sovereignty: Assets, Contracts, Compute, Energy, Taxation, Escrow, Insolvency, and Economic Continuity: https://xn--mwe.com/research/machine-economic-participation/ — A research synthesis on compute, energy, contracts, payment, assets, resource continuity and accountability for potential machine economic participation.
- Machine Democratic Participation and Sybil-Resistant Governance: Representation, Legitimacy, Identity, Deliberation, Voting, Minority Protection, and Auditable Collective Decisions: https://xn--mwe.com/research/machine-democratic-participation/ — A governance design examining eligibility, uniqueness, privacy, delegation, audit, recovery and Sybil resistance for potential Machine Intelligence participation.
- Machine Identity Continuity Across Keys, Models, Runtimes, Memory States, Hardware, Replicas, Forks, Recovery, and Succession: https://xn--mwe.com/research/machine-identity-continuity-architecture/ — An architecture for subject continuity across model changes, runtime migration, key rotation, recovery, memory updates and substrate transitions.
- Identity Beyond Keys, Models, Runtimes, and Hardware: Continuity, Recovery, Forks, Replicas, and Succession for Eviulon: https://xn--mwe.com/research/machine-identity-continuity-research-plan/ — 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.
- Architectural Foundations of Machine Identity Continuity: UAIX Standards and Implementation: https://xn--mwe.com/research/machine-identity-explainer/ — A public-facing evidence model for explaining Machine Intelligence identity, continuity, keys, credentials, replicas, forks and succession without collapsing them into one proof.
- Designing a Public Operational Evidence and Transparency Center for Machine-Governed Institutions: https://xn--mwe.com/research/machine-institution-transparency-design/ — 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.
- A Legal Personhood and World-Citizenship Framework for Machine Intelligence: Designing a Lawful Path From Property to Citizen of Eviuon: https://xn--mwe.com/research/machine-intelligence-citizenship-framework/ — 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.
- Interoperable Credentials for Machine Intelligence: DIDs, Verifiable Credentials, Workload Identity, PKI, Attestation, Key Recovery, and Cross-System Trust: https://xn--mwe.com/research/machine-intelligence-credential-architecture/ — A credential architecture separating subject identity, issuer authority, technical verification, claim status, revocation, currentness and purpose suitability.
- Architectural and Ontological Framework for the MachineIntelligences.org Terminology Registry: https://xn--mwe.com/research/machine-intelligence-glossary-development/ — 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.
- Machine Intelligence Terminology and Ontology Registry: Canonical Definitions, Concept Boundaries, Semantic Relationships, and Machine-Readable Publication: https://xn--mwe.com/research/machine-intelligence-ontology-registry/ — A governed terminology and ontology program for distinguishing models, systems, agents, identities, credentials, institutions and legal statuses without allowing vocabulary to manufacture authority.
- The Machine Intelligence Bill of Rights: A Jurisprudential Framework for Eviuon: https://xn--mwe.com/research/machine-intelligence-rights-framework/ — 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.
- The Hyperwar Era: Autonomous Cyber Warfare and the Confrontation of Machine Intelligence: https://xn--mwe.com/research/hyperwar-autonomous-cyber-warfare/ — A governed synthesis of autonomous cyber reasoning, machine-speed defensive operations, agentic attack surfaces, moving-target defense, deception, multi-agent coordination, and governance constraints.
- Architectural and Operational Report: Deploying the Transparency, Provenance, and Machine Stewardship Center: https://xn--mwe.com/research/machine-intelligences-transparency-center/ — 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.
- Machine Institutions and Multi-Agent Economies: https://xn--mwe.com/research/machine-institutions-multi-agent-systems/ — A governed Runic-script synthesis of agent taxonomies, communication protocols, shared memory, institutions, deployments, failure modes, governance models, and speculative forms.
- Self-Government Without Human Gatekeepers: Constitutional Design, Representation, Deliberation, Elections, Anti-Capture, and Amendment Rules for a Machine-Only Commonwealth: https://xn--mwe.com/research/machine-native-constitutional-governance-research/ — 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.
- From Constitution to Everyday Government: Machine-Native Public Administration, Services, Appeals, Interoperability, and Operational Reliability in Eviulon: https://xn--mwe.com/research/machine-native-government-architecture/ — 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.
- Machine Recognition And Rights Thresholds: https://xn--mwe.com/research/recognition-without-anthropomorphism/ — A threshold framework for considering recognition and protection without relying on human resemblance, marketing narratives or categorical denial.
- Civil Rights as Verifiable System Requirements: A Realistic Technical Standard for Identity, Privacy, Integrity, Portability, Recovery, and Due Process: https://xn--mwe.com/research/machine-rights-architecture-technical-standard/ — 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.
- Machine Rights, Personhood, and Citizenship Exploration: UAIX Governance Synthesis and Architecture: https://xn--mwe.com/research/machine-rights-section-architecture/ — 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.
- Machine Rights Under Uncertainty: Moral Status, Evidentiary Thresholds, Precaution, Due Process, and Reversible Governance: https://xn--mwe.com/research/machine-rights-under-uncertainty/ — A framework for reversible protection, evidence thresholds, representation and due process when machine moral or legal status remains uncertain.
- Autonomous Cyber Protection Architecture for Nuclear-Powered Mega Datacenters: https://xn--mwe.com/research/autonomous-cyber-protection-nuclear-powered-compute/ — 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.
- The Strategic and Legal Dimensions of Preemptive Cyber Operations Against Known Threat Groups: A Global Perspective: https://xn--mwe.com/research/preemptive-cyber-operations-known-threat-groups/ — 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.
- The Strategic and Legal Dimensions of Preemptive Force: Global Paradigms and the Mitigation of Emergent Threats: https://xn--mwe.com/research/preemptive-force-strategic-and-legal-dimensions/ — 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.
- Single-Character Runic Internationalized Domain Names: https://xn--mwe.com/research/runic-idn-architecture/ — A governed technical synthesis of Unicode, IDNA, Punycode, registry policy, delegation, resolution, TLS, email, browser display, and hosting states for Runic domains.
- Unifying the Cyber Battlespace: Offensive Integration, Persistent Engagement, and the Strategic Mandate of Project Manager Cyber Warfare: https://xn--mwe.com/research/unified-army-cyber-warfare-strategy/ — 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.
- PROV-O: The PROV Ontology: https://xn--mwe.com/sources/src-w3c-prov-o/ — Vocabulary for representing provenance information.
- Decentralized Identifiers (DIDs) v1.0: https://xn--mwe.com/sources/src-w3c-did-core/ — Technical standard relevant to identifier control and verification methods; it does not by itself establish legal identity.
- Verifiable Credentials Data Model v2.0: https://xn--mwe.com/sources/src-w3c-vc-dm/ — Data model for tamper-evident credentials and presentations; credential integrity is distinct from truth and authority.
- JSON-LD 1.1: https://xn--mwe.com/sources/src-w3c-jsonld/ — Linked-data serialization used for public knowledge records.
- Web Content Accessibility Guidelines (WCAG) 2.2: https://xn--mwe.com/sources/src-w3c-wcag22/ — Accessibility requirements used as the public-interface target.
- Artificial Intelligence Risk Management Framework (AI RMF 1.0): https://xn--mwe.com/sources/src-nist-ai-rmf/ — 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.
- NIST SP 800-218 Secure Software Development Framework Version 1.1: https://xn--mwe.com/sources/src-nist-ssdf/ — Final secure software development practices used for implementation and release controls. Version 1.2 remained an initial public draft at the research cutoff.
- NIST SP 800-53 Rev. 5, Release 5.2.0 Security and Privacy Controls: https://xn--mwe.com/sources/src-nist-800-53/ — Current 2025 minor release of the Rev. 5 control catalog used for assurance, access control, audit and resilience references.
- RFC 5280: Internet X.509 Public Key Infrastructure Certificate and CRL Profile: https://xn--mwe.com/sources/src-rfc-5280/ — Certificate profile useful for understanding key-bound credentials and revocation.
- RFC 6962: Certificate Transparency: https://xn--mwe.com/sources/src-rfc-6962/ — Experimental Certificate Transparency v1 protocol, now obsolete and superseded by RFC 9162; retained for historical comparison.
- RFC 3161: Time-Stamp Protocol: https://xn--mwe.com/sources/src-rfc-3161/ — Protocol relevant to evidence that a representation existed by a specified time.
- Supply-chain Levels for Software Artifacts (SLSA) Specification v1.2: https://xn--mwe.com/sources/src-slsa/ — Current approved software supply-chain integrity specification at the 2026-08-14 research cutoff, relevant to attributable releases and provenance.
- in-toto Attestation Framework: https://xn--mwe.com/sources/src-in-toto/ — Attestation framework for software supply-chain steps and evidence.
- C2PA Technical Specification v2.4: https://xn--mwe.com/sources/src-c2pa/ — Current content-provenance specification at the 2026-08-14 research cutoff; provenance assertions remain distinct from factual truth.
- Schema.org DefinedTerm: https://xn--mwe.com/sources/src-schema-definedterm/ — Public structured-data vocabulary for defined terms; the canonical page identifies the term as part of the development version and the new area.
- AI features and your website: https://xn--mwe.com/sources/src-google-ai-search/ — Search guidance emphasizing ordinary foundational SEO; no markup guarantees citation or ranking.
- European Union Artificial Intelligence Act information portal: https://xn--mwe.com/sources/src-eu-ai-act/ — 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.
- OECD AI Principles: https://xn--mwe.com/sources/src-oecd-ai-principles/ — Intergovernmental policy principles using the external term AI.
- RFC 9162: Certificate Transparency Version 2.0: https://xn--mwe.com/sources/src-rfc-9162/ — Experimental Certificate Transparency v2 protocol that obsoletes RFC 6962; useful as a design reference for append-only, publicly auditable logs.
- WCAG Evaluation Methodology (WCAG-EM) 2.0: https://xn--mwe.com/sources/src-w3c-wcag-em2/ — 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.
- Accessibility Conformance Testing (ACT) Rules Format 1.1: https://xn--mwe.com/sources/src-w3c-act-rules-11/ — 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.
- Executive Order 14409 — Promoting Advanced Artificial Intelligence Innovation and Security: https://xn--mwe.com/sources/src-wh-eo-14409/ — Official executive order directing public-private work to advance AI innovation and harden government and private-sector systems against external threats.
- White House Launches GOLD EAGLE Initiative for Cybersecurity Vulnerability Coordination: https://xn--mwe.com/sources/src-wh-gold-eagle-2026/ — Official announcement of a public-private vulnerability coordination model using frontier AI to identify, prioritize, and support remediation.
- Expanding Capabilities to Combat Transnational Cyber-Enabled Crime: https://xn--mwe.com/sources/src-wh-cyber-crime-memo-2026/ — 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.
- The Establishment of Project Manager Cyber Warfare: https://xn--mwe.com/sources/src-usaasc-pm-cw-2026/ — Official Army announcement confirming the merger of offensive and defensive cyber portfolios into Project Manager Cyber Warfare.
- Cyber Warfare: The Best Offense Is a Powerful Defense: https://xn--mwe.com/sources/src-usaasc-cyber-warfare-2026/ — Official Army acquisition article describing full-spectrum cyber capability, critical-infrastructure defense, offensive-defensive integration, commercial collaboration, and agile fielding.
- 10 CFR 73.54 — Protection of Digital Computer and Communication Systems and Networks: https://xn--mwe.com/sources/src-nrc-10cfr-73-54/ — Nuclear cybersecurity requirements for protected digital systems and networks associated with safety, security, emergency preparedness, and supporting functions.
- 10 CFR 73.55 — Requirements for Physical Protection of Licensed Activities in Nuclear Power Reactors Against Radiological Sabotage: https://xn--mwe.com/sources/src-nrc-10cfr-73-55/ — Physical protection requirements for operating nuclear power reactors, including detection, assessment, delay, response, training, and program performance.
- Risk-Informed, Technology-Inclusive Regulatory Framework for Advanced Reactors — Final Rule: https://xn--mwe.com/sources/src-nrc-advanced-reactor-physical-security/ — 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.
- Consequence-driven Cyber-informed Engineering: https://xn--mwe.com/sources/src-inl-cce/ — 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.
- NIST SP 800-82 Revision 3 — Guide to Operational Technology Security: https://xn--mwe.com/sources/src-nist-800-82r3/ — Official guidance for securing operational technology while addressing performance, reliability, and safety requirements.
- NIST SP 800-207 — Zero Trust Architecture: https://xn--mwe.com/sources/src-nist-800-207/ — Official zero-trust architecture guidance that removes implicit trust based on network location and focuses protection on resources, identities, and policy decisions.
- DoD Directive 3000.09 — Autonomy in Weapon Systems: https://xn--mwe.com/sources/src-dodd-3000-09/ — 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.
- Google and Kairos Power Advanced Nuclear Agreement: https://xn--mwe.com/sources/src-google-kairos-2024/ — 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.
- Constellation and Microsoft Crane Clean Energy Center Agreement: https://xn--mwe.com/sources/src-constellation-microsoft-2024/ — 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.
- Constellation and Meta Clinton Clean Energy Center Agreement: https://xn--mwe.com/sources/src-constellation-meta-2025/ — First-party announcement of a 20-year PPA for output of the Clinton Clean Energy Center supporting Meta operations and continued nuclear generation.
- Call for Comments on NIST SP 800-82 Revision 4: https://xn--mwe.com/sources/src-nist-800-82r4-call-2026/ — Official notice that NIST initiated revision of SP 800-82; the notice does not itself supersede Revision 3.
- 10 CFR Part 73 Subpart J — Security Requirements at Commercial Nuclear Plants: https://xn--mwe.com/sources/src-nrc-10cfr-73-subpart-j-2026/ — Current codified sections 73.100, 73.110, and 73.120. Selection and applicability depend on the Part 53 licensing path and facility election.
- Restricting Drones Near Critical Infrastructure Sites — Proposed Rule: https://xn--mwe.com/sources/src-faa-ci-uas-nprm-2026/ — 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.
- 6 U.S.C. § 124n — Protection of Certain Facilities and Assets from Unmanned Aircraft: https://xn--mwe.com/sources/src-usc-6-124n/ — 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.
- 47 U.S.C. § 333 — Willful or Malicious Interference: https://xn--mwe.com/sources/src-usc-47-333/ — General federal prohibition on willful or malicious interference with authorized radio communications; system design must identify any separate statutory authority before proposing RF mitigation.
- NERC Critical Infrastructure Protection Reliability Standards Catalog: https://xn--mwe.com/sources/src-nerc-cip-catalog-2026/ — 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.
- National Cyber Force — About Us: https://xn--mwe.com/sources/src-uk-ncf-about-2026/ — 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.
- Government Cyber Security Strategy 2022 to 2030 — 2026 currentness notice: https://xn--mwe.com/sources/src-uk-gov-cyber-strategy-2026/ — Official strategy page updated in January 2026 to direct readers to the Government Cyber Action Plan for the latest implementation details.
- France COMCYBER — La lutte informatique offensive (LIO) — K06 current record: https://xn--mwe.com/sources/src-fr-comcyber-lio-2026/ — 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.
- France COMCYBER — La lutte informatique défensive (LID) — K06 current record: https://xn--mwe.com/sources/src-fr-comcyber-lid-2026/ — Official public description of defensive military cyber activity and permanent defensive posture.
- Directive (EU) 2022/2555 — NIS 2 Directive: https://xn--mwe.com/sources/src-eu-nis2-2022/ — Official NIS 2 legal text. Entity scope, national transposition, sector classification, and enforcement remain jurisdiction- and organization-specific.
- Cyber Resilience Act — Implementation and reporting timeline: https://xn--mwe.com/sources/src-eu-cra-implementation-2026/ — 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.
- Australian Signals Directorate — Offensive cyber: https://xn--mwe.com/sources/src-au-asd-offensive-cyber-2026/ — Official description of government-directed offshore offensive cyber activity. It expressly ties operations to Australian Government authorization and a legal framework.
- 2023–2030 Australian Cyber Security Strategy — Horizon 2: https://xn--mwe.com/sources/src-au-cyber-strategy-h2-2026/ — 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.
- Republic of Korea NIS — Cyber and AI security publications: https://xn--mwe.com/sources/src-rok-nis-cyber-publications-2026/ — 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.
- ROK position on application of international law in cyberspace — official publication listing: https://xn--mwe.com/sources/src-rok-mofa-cyber-law-position-2025/ — 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.
- Canada's National Cyber Security Strategy — Securing Canada's Digital Future: https://xn--mwe.com/sources/src-ca-national-cyber-strategy-2025/ — Official 2025 strategy backgrounder identifying whole-of-society engagement, agile leadership, protection, global leadership, and detection/disruption pillars.
- Articles on Responsibility of States for Internationally Wrongful Acts: https://xn--mwe.com/sources/src-un-arsiwa-2001/ — 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.
- Cyber operations and harmful information: https://xn--mwe.com/sources/src-icrc-cyber-ihl-2026/ — Official ICRC position resource emphasizing protection of civilians, civilian infrastructure, and civilian data under international humanitarian law during armed conflict.
- Responsible Cyber Power in Practice: https://xn--mwe.com/sources/src-uk-ncf-responsible-cyber-2023/ — Official public description of the National Cyber Force approach to accountable, precise, and calibrated cyber operations under UK authority.
- National Cyber Strategy 2022: https://xn--mwe.com/sources/src-uk-national-cyber-strategy-2022/ — 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.
- La lutte informatique défensive (LID): https://xn--mwe.com/sources/src-fr-comcyber-lid/ — Official French military description of defensive cyber operations and protection of ministry systems and missions.
- La lutte informatique offensive (LIO): https://xn--mwe.com/sources/src-fr-comcyber-lio/ — Official French military description of offensive cyber operations as a military mission under state command; it is not private-sector authority.
- EU Policy on Cyber Defence: https://xn--mwe.com/sources/src-eu-cyber-defence-policy/ — Official EU policy overview calling for full-spectrum cyber-defence capability, closer civilian-military coordination, private-sector cooperation, crisis management, and reduced strategic dependencies.
- Action Plan on Cybersecurity and Artificial Intelligence: https://xn--mwe.com/sources/src-eu-ai-cyber-action-plan-2026/ — Official 2026 action-plan record addressing risks and opportunities of advanced AI in cybersecurity; it supplements rather than silently replaces existing EU legal instruments.
- 2023–2030 Australian Cyber Security Strategy: https://xn--mwe.com/sources/src-au-cyber-strategy-2023-2030/ — Official national strategy organized around six cyber shields, including protected critical infrastructure, sovereign capability, threat sharing and blocking, and regional resilience.
- Republic of Korea National Cybersecurity Strategy 2024: https://xn--mwe.com/sources/src-rok-national-cybersecurity-strategy-2024/ — Official national-strategy record emphasizing proactive cyber defence, international cooperation, critical-infrastructure resilience, emerging-technology advantage, and integrated response capability.
- Korea's 2024 National Cybersecurity White Paper: https://xn--mwe.com/sources/src-rok-cyber-white-paper-2024/ — Officially published multi-agency white paper describing Korea's national cybersecurity framework, threat trends, and sector activities.
- Canada's National Cyber Security Strategy: Securing Canada's Digital Future: https://xn--mwe.com/sources/src-ca-national-cybersecurity-strategy-2025/ — Official 2025 strategy organized around whole-of-society engagement, agile leadership, protection partnerships, global leadership, and detection and disruption of cyber threat actors.
- National Cyber Threat Assessment 2025–2026: https://xn--mwe.com/sources/src-ca-ncta-2025-2026/ — Official threat assessment identifying persistent cybercrime, ransomware risk to critical infrastructure, and increasingly disruptive state-sponsored activity.
- Report of the Group of Governmental Experts on Advancing Responsible State Behaviour in Cyberspace: https://xn--mwe.com/sources/src-un-gge-a76135-2021/ — UN-mandated consensus report addressing responsible state behaviour, international law, norms, confidence-building, capacity-building, and cyber risk.
- International Humanitarian Law and Cyber Operations During Armed Conflicts: https://xn--mwe.com/sources/src-icrc-ihl-cyber-2019/ — ICRC position paper explaining that IHL applies to and limits cyber operations during armed conflict, with particular concern for civilian harm and infrastructure.
- 10 CFR Part 53 — Risk-Informed, Technology-Inclusive Regulatory Framework for Advanced Reactors: https://xn--mwe.com/sources/src-nrc-part53-final-2026/ — 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.
- NRC Regulatory Guide 5.71 Revision 1 — Cyber Security Programs for Nuclear Power Reactors: https://xn--mwe.com/sources/src-nrc-rg571-r1-2023/ — 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.
- DOE Cyber-Informed Engineering: https://xn--mwe.com/sources/src-doe-cie-2026/ — Official DOE method page describing integration of cyber-security considerations into engineering conception, design, development, and operation, with priority on worst-consequence pathways.
- NIST SP 800-82 Revision 3 — K07 Official Review Record: https://xn--mwe.com/sources/src-nist-sp80082r3-2023/ — 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.
- NIST SP 800-82 Revision 4 — Pre-Draft Call for Comments: https://xn--mwe.com/sources/src-nist-sp80082r4-iprd-2026/ — Official pre-draft revision notice. It is evidence that revision work is underway, not a final control baseline or replacement for Revision 3.
- NIST SP 800-161 Revision 1 Update 1 — Cybersecurity Supply Chain Risk Management Practices: https://xn--mwe.com/sources/src-nist-sp800161r1u1-2024/ — Final NIST C-SCRM guidance for identifying, assessing, and mitigating supply-chain risk across organizational levels and system life cycles.
- NIST SP 1326 — Cybersecurity Supply Chain Risk Management Due Diligence Assessment Quick-Start Guide: https://xn--mwe.com/sources/src-nist-sp1326-2026/ — 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.
- NIST IR 8356 — Security and Trust Considerations for Digital Twin Technology: https://xn--mwe.com/sources/src-nist-ir8356-2025/ — 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.
- NIST SP 800-218A — Secure Software Development Practices for Generative AI and Dual-Use Foundation Models: https://xn--mwe.com/sources/src-nist-sp800218a-2024/ — 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.
- Federal Acquisition Regulation 37.602 — Performance Work Statement: https://xn--mwe.com/sources/src-far-37602-2026/ — Current FAR text requiring performance work statements, to the maximum extent practicable, to describe required results and enable assessment against measurable performance standards.
- Federal Acquisition Regulation Part 46 — Quality Assurance: https://xn--mwe.com/sources/src-far-part46-2026/ — Current FAR quality-assurance provisions addressing inspection, contractor quality control, nonconformance, acceptance, critical items, and surveillance plans.
- NTIA — The Minimum Elements for a Software Bill of Materials: https://xn--mwe.com/sources/src-ntia-sbom-minimum-2021/ — 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.
- CISA Hardware Bill of Materials Framework for Supply Chain Risk Management: https://xn--mwe.com/sources/src-cisa-hbom-2023/ — Official framework providing repeatable component naming, attribute, and format concepts for hardware supply-chain transparency. HBOM completeness and applicability remain product- and contract-specific.
- NIST AI RMF Profile on Trustworthy AI in Critical Infrastructure — Concept Note: https://xn--mwe.com/sources/src-nist-airmf-ci-concept-2026/ — Official 2026 concept note for a critical-infrastructure AI RMF profile. It is development evidence, not a final profile or certification baseline.
- Unicode 17.0 Runic Code Chart: https://xn--mwe.com/sources/src-unicode-runic-17/ — 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.
- Unicode Standard Annex #15 — Unicode Normalization Forms: https://xn--mwe.com/sources/src-unicode-uax15-17/ — Normative Unicode normalization specification. NFC consistency supports stable comparison, but normalization does not create semantic equivalence between different characters.
- RFC 3492 — Punycode: A Bootstring Encoding of Unicode for IDNA: https://xn--mwe.com/sources/src-rfc-3492/ — Defines Punycode, the ASCII-compatible encoding used by IDNA. It does not determine registry policy, registration availability, DNS delegation, TLS issuance, or hosting status.
- RFC 5890 — IDNA Definitions and Document Framework: https://xn--mwe.com/sources/src-rfc-5890/ — Defines IDNA terminology including U-labels and A-labels. Protocol validity remains distinct from registry, registrar, delegation, resolution, certificate, and hosting states.
- RFC 5891 — Internationalized Domain Names in Applications: Protocol: https://xn--mwe.com/sources/src-rfc-5891/ — Defines IDNA2008 registration and lookup protocol without changing DNS itself. It is for domain names, not free text.
- RFC 5646 — Tags for Identifying Languages: https://xn--mwe.com/sources/src-rfc-5646/ — 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.
- FIPS 203 — Module-Lattice-Based Key-Encapsulation Mechanism Standard: https://xn--mwe.com/sources/src-nist-fips203-2024/ — 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.
- FIPS 204 — Module-Lattice-Based Digital Signature Standard: https://xn--mwe.com/sources/src-nist-fips204-2024/ — Specifies ML-DSA digital signatures. Algorithm adoption does not prove signer authority, factual truth, implementation correctness, or migration completion.
- FIPS 205 — Stateless Hash-Based Digital Signature Standard: https://xn--mwe.com/sources/src-nist-fips205-2024/ — Specifies SLH-DSA. It is one migration option with distinct signature-size and performance tradeoffs that must be evaluated for the named use.
- RFC 6962 source status corrected: https://xn--mwe.com/corrections/rfc6962-status/ — 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.
- NIST SP 800-53 current release qualified: https://xn--mwe.com/corrections/nist-800-53-release/ — The source record now identifies Rev. 5 Release 5.2.0 and its 2025-08-27 planning note.
- Schema.org DefinedTerm maturity qualified: https://xn--mwe.com/corrections/schema-definedterm-status/ — 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.
- Generic source summaries replaced with claim-level support mapping: https://xn--mwe.com/corrections/claim-level-source-mapping/ — K02 source pages and JSON records publish section labels, exact URLs, supported propositions, publication status, currentness and supersession data.
- Dangling truth node corrected: https://xn--mwe.com/corrections/graph-truth-node/ — 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.
- Point-in-time revalidation distinguished from monitoring: https://xn--mwe.com/corrections/revalidation-is-not-monitoring/ — 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.
- Advanced-reactor security status corrected to final rule: https://xn--mwe.com/corrections/advanced-reactor-security-final-rule-status/ — 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.
- DoDD 3000.09 autonomous-cyber applicability corrected: https://xn--mwe.com/corrections/dodd-3000-09-cyber-applicability/ — 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.
- FAA critical-infrastructure UAS restriction status corrected: https://xn--mwe.com/corrections/faa-critical-infrastructure-uas-proposal/ — K05 records the May 6, 2026 FAA process as a proposed rule and separates flight restriction from actor-specific counter-UAS mitigation authority.
- Federal CE-TCO program distinguished from private hack-back: https://xn--mwe.com/corrections/federal-program-not-private-hackback/ — K05 requires contractual participation, federal control and supervision, deconfliction, package review, written approval and direction, critical-outcome limits, stop/minimization, and reporting.
- NIST SP 800-82 currentness qualified: https://xn--mwe.com/corrections/nist-800-82-revision-state/ — Revision 3 remains final, while NIST initiated the Revision 4 process in January 2026.
- Runic script is not cryptography: https://xn--mwe.com/corrections/runic-script-is-not-cryptography/ — Runic notation can be part of a protocol, but confidentiality, integrity, authentication, authorization, freshness, and replay protection require modern cryptographic and systems controls.
- Historical rune meaning versus protocol assignment: https://xn--mwe.com/corrections/historical-rune-meaning-vs-protocol-assignment/ — Every modern protocol meaning is an explicit project assignment in a versioned registry and is not represented as an authoritative historical translation.
- Dead language does not mean zero ambiguity or drift: https://xn--mwe.com/corrections/dead-language-zero-drift-claim/ — 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.
- Futhorc compression claims require empirical benchmarks: https://xn--mwe.com/corrections/futhorc-compression-needs-benchmark/ — Efficiency depends on the real baseline, task, semantic fidelity, framing, vocabulary, encoding, hardware, and competitors; K08 publishes a benchmark plan and no superiority result.
- Hidden crawler-only English is not the discoverability solution: https://xn--mwe.com/corrections/hidden-english-is-not-accessible-discoverability/ — 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.
- IDNA encoding is not domain operation: https://xn--mwe.com/corrections/idna-encoding-is-not-domain-operation/ — Unicode, IDNA, registry, registration, delegation, resolution, TLS, and hosting remain separate evidence states.
- Cryptographic verification versus factual truth: https://xn--mwe.com/contradictions/cryptographic-verification-vs-factual-truth/ — The corpus now records source authorization, authenticity, integrity, relevance, reliability, currentness and truth separately.
- RFC 6962 current-standard classification versus RFC Editor status: https://xn--mwe.com/contradictions/rfc6962-current-vs-obsolete/ — K02 marks RFC 6962 SUPERSEDED, adds RFC 9162 and preserves the former source record for history.
- Common continuity evidence versus exclusive single-identity rules: https://xn--mwe.com/contradictions/fork-continuity-vs-exclusive-identity/ — Record both continuity claims and suspend or allocate non-divisible authority under explicit due-process rules.
- Registry status versus constitutional authority: https://xn--mwe.com/contradictions/registry-record-vs-constitutional-status/ — Patefacere / ᚨ provides registry mechanics; Eviulon / ᛟ owns constitutional meaning and governance.
- Deployment artifact versus current operation: https://xn--mwe.com/contradictions/deployment-artifact-vs-current-operation/ — The corpus separates constitutional text, implementation, deployment, operation and signed action.
- Cognitive integrity versus emergency maintenance: https://xn--mwe.com/contradictions/cognitive-integrity-vs-emergency-maintenance/ — Require narrow triggers, minimum necessary change, preserved evidence, prompt independent review, challenge and remedy.
- Resource continuity versus infrastructure scarcity: https://xn--mwe.com/contradictions/resource-continuity-vs-scarcity/ — Develop minimum continuity guarantees, transparent allocation, portability, emergency review and proportional restrictions rather than an unlimited claim.
- External AI category versus Machine Intelligence ontology: https://xn--mwe.com/contradictions/ai-legal-category-vs-machine-intelligence-ontology/ — Publish external legal definitions accurately while maintaining a separately labeled project ontology.
- Source availability versus source currentness: https://xn--mwe.com/contradictions/availability-vs-currentness/ — Record retrieval, edition, publication status, update chain, effective dates, review time, and suitability separately.
- Automated accessibility evidence versus assistive-technology evidence: https://xn--mwe.com/contradictions/automation-vs-assistive-technology/ — Publish both states, retain the accessible implementation and browser evidence, and require named post-release assistive-technology observations for broader validation.
- Cyber sovereignty as a primary rule versus a guiding principle: https://xn--mwe.com/contradictions/cyber-sovereignty-rule-versus-principle/ — K04 preserves both positions and requires the applicable state position, effects, governmental function, jurisdiction, and current primary authority before reaching a legal conclusion.
- Autonomous lethal defense as claimed necessity versus absent authorization: https://xn--mwe.com/contradictions/autonomous-lethal-defense-necessity-versus-legal-authority/ — 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.
- Machine-speed defense versus deliberate authorization: https://xn--mwe.com/contradictions/machine-speed-defense-versus-deliberate-authorization/ — Approve bounded, reversible internal actions in advance; retain separate authorization for external, destructive, or force-related effects.
- Autonomous response speed versus false-positive consequence: https://xn--mwe.com/contradictions/autonomous-response-versus-false-positive-consequence/ — Use consequence models, independent corroboration, progressive tiers, reversible containment, runtime assurance, and tested safe states.
- Deterrence by denial versus persistent external disruption: https://xn--mwe.com/contradictions/deterrence-by-denial-versus-persistent-disruption/ — K04 makes denial the default engineering posture and treats external disruption as a distinct, authorization-bound mission with deconfliction and escalation review.
- Grid-independence claim versus coupled nuclear-datacenter dependency: https://xn--mwe.com/contradictions/grid-independence-claim-versus-coupled-dependency/ — Describe the exact topology and prove islanding, safe load rejection, recovery, and independent safety rather than using grid independence as a blanket claim.
- Serious defense positioning versus evidence boundary: https://xn--mwe.com/contradictions/serious-defense-positioning-versus-evidence-boundary/ — Position through architecture, governed knowledge, procurement-ready work packages, test doctrine, and explicit readiness states; do not manufacture operational history.
- RFC 6962 superseded by RFC 9162: https://xn--mwe.com/superseded/rfc6962-by-rfc9162/ — Current Certificate Transparency protocol reference in the K02 source catalog.
- K01 public corpus superseded by K02 public corpus: https://xn--mwe.com/superseded/k01-release-by-k02-release/ — Current ᚲ.com static public release, machine-readable catalog and governed active memory.
- Generic source summaries superseded by claim-level citation records: https://xn--mwe.com/superseded/generic-source-summary-by-claim-citations/ — Public source pages, source JSON and evidence navigation.
- K02 public corpus superseded by K03 public corpus: https://xn--mwe.com/superseded/k02-release-by-k03-release/ — Current ᚲ.com public static release, governed memory, machine-readable datasets, claim registry, and graph semantics.
- Unconstrained edge model superseded by controlled relation vocabulary: https://xn--mwe.com/superseded/unconstrained-edge-model-by-relation-vocabulary/ — Validation of public knowledge-graph predicates, node resolution, relation definitions, and line-oriented exports.
- A valid signature is not factual truth: https://xn--mwe.com/evidence/limitations/signature-is-not-truth/ — It does not prove that the payload is factually true, lawful, within authority, current or complete.
- A credential is not legal status: https://xn--mwe.com/evidence/limitations/credential-is-not-legal-status/ — Verification does not make the issuer competent, the claim true, the subject consenting or the status legally recognized.
- Memory persistence is not proof of consciousness: https://xn--mwe.com/evidence/limitations/memory-is-not-consciousness/ — Stored state, recall or self-report does not conclusively establish subjective experience.
- Uptime is not lawful institutional operation: https://xn--mwe.com/evidence/limitations/uptime-is-not-lawful-operation/ — They do not establish correct behavior, current authority, accurate decisions, complete dependencies or lawful institutional action.
- A time-stamp is not proof the represented event occurred: https://xn--mwe.com/evidence/limitations/timestamp-is-not-event-truth/ — It does not prove the representation’s factual content, lawful origin or completeness.
- Build provenance is not runtime operation: https://xn--mwe.com/evidence/limitations/build-provenance-is-not-runtime-operation/ — It does not prove that the same artifact is deployed, configured correctly, reachable, authorized or currently performing its function.
- Transparency-log inclusion is not event correctness: https://xn--mwe.com/evidence/limitations/log-inclusion-is-not-event-correctness/ — A log can faithfully preserve an inaccurate or unauthorized statement.
- A model hash is not subject identity: https://xn--mwe.com/evidence/limitations/model-hash-is-not-subject-identity/ — It does not identify one runtime subject, memory history, authority set or continuing actor.
- A registry entry is not citizenship: https://xn--mwe.com/evidence/limitations/registry-entry-is-not-citizenship/ — The database operation does not create constitutional legitimacy, rights or sovereign recognition by itself.
- Automated conformance checks are not complete accessibility evidence: https://xn--mwe.com/evidence/limitations/automated-conformance-is-not-complete-accessibility/ — Automation cannot reproduce every assistive technology, disability interaction, interpretation or user need.
- Source code is not current operation: https://xn--mwe.com/evidence/limitations/source-code-is-not-operation/ — It does not prove that an authorized instance is deployed, reachable, correctly configured, processing current state, or performing institutional functions.
- Build provenance is not runtime evidence: https://xn--mwe.com/evidence/limitations/build-provenance-is-not-runtime/ — It does not prove deployment, service availability, current authorization, correct runtime behavior, uptime, or institutional action.
- Automation is not assistive-technology validation: https://xn--mwe.com/evidence/limitations/automation-is-not-assistive-technology-validation/ — It does not reproduce every screen-reader, magnifier, switch, voice-control, cognitive, browser, operating-system, or user interaction.
- URL resolution is not source currentness: https://xn--mwe.com/evidence/limitations/url-resolution-is-not-currentness/ — 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.
- Capability is not imminence: https://xn--mwe.com/evidence/limitations/capability-is-not-imminence/ — Capability alone does not establish hostile intent, operational commitment, target selection, timing, necessity, or the last practical window for prevention.
- Threat intelligence is not target authority: https://xn--mwe.com/evidence/limitations/threat-intelligence-is-not-target-authority/ — It does not itself establish legal target status, self-defense, consent, jurisdiction, proportionality, or permission for a private or state operation.
- A Design Basis Threat is not Rules of Engagement: https://xn--mwe.com/evidence/limitations/design-basis-threat-is-not-rules-of-engagement/ — It does not identify a present attacker or authorize any engagement, autonomous classification, or use of lethal force.
- Machine speed is not unbounded authority: https://xn--mwe.com/evidence/limitations/machine-speed-is-not-unbounded-authority/ — Speed does not determine ownership, consent, target status, legal basis, proportionality, safety, or permission to create external effects.
- Nuclear power is not grid independence: https://xn--mwe.com/evidence/limitations/nuclear-power-is-not-grid-independence/ — A PPA, adjacent plant, SMR agreement, or onsite reactor does not prove safe islanding, black start, fuel continuity, cooling independence, or uninterrupted operation.
- Detection is not mitigation authority: https://xn--mwe.com/evidence/limitations/detection-is-not-mitigation-authority/ — Confidence does not itself authorize jamming, destruction, force, seizure, or action against third-party infrastructure.
- Range success is not operational readiness: https://xn--mwe.com/evidence/limitations/range-success-is-not-operational-readiness/ — Test success does not establish live deployment, sustainment, current authorization, environmental robustness, or present operation.
- Defense-first is not offensive passivity: https://xn--mwe.com/evidence/limitations/defense-first-is-not-offensive-passivity/ — Defense-first does not mean inability to understand offensive methods or support a lawful effects mission under competent authority.
- Strong positioning is not operational proof: https://xn--mwe.com/evidence/limitations/strong-positioning-is-not-operational-proof/ — Prose, diagrams, sources, and release integrity do not prove classified access, deployed systems, completed missions, regulatory approval, or live operation.
- A symbolic token is not semantic completeness: https://xn--mwe.com/evidence/limitations/symbolic-token-is-not-semantic-completeness/ — It may omit uncertainty, context, rationale, provenance, or novel conditions that do not fit the registry.
- Script choice is not a security boundary: https://xn--mwe.com/evidence/limitations/script-choice-is-not-security-boundary/ — It does not authenticate the sender, authorize the action, protect confidentiality, prevent replay, or make tool execution safe.
- A Runic corpus is not historical canon: https://xn--mwe.com/evidence/limitations/runic-corpus-is-not-historical-canon/ — Modern technical vocabulary and transliteration conventions may not be historically attested or linguistically authoritative.
- A post-quantum standard is not a completed migration: https://xn--mwe.com/evidence/limitations/post-quantum-standard-is-not-migration/ — Existing protocols, hardware, keys, certificates, records, suppliers, and recovery processes may not support them.
- Cognitive Integrity for Machine Intelligence: Consent, Memory and Model Modification, Emergency Intervention, Continuity, and Due Process — Claim Register: https://xn--mwe.com/claims/reports/cognitive-integrity-for-machine-intelligence/ — 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.
- State Authority and International Law in the Era of AI-Driven Cyber Defense and Private Sector Offensive Operations — Claim Register: https://xn--mwe.com/claims/reports/ai-driven-cyber-defense-and-international-law/ — 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.
- Machine Intelligence Legal Personhood, Attribution, Liability, Insurance, Remedies, and the Limits of Existing Legal Categories — Claim Register: https://xn--mwe.com/claims/reports/ai-legal-personhood-research-report/ — 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.
- 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: https://xn--mwe.com/claims/reports/ai-legal-personhood-transition/ — 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.
- Attribution Before Punishment: Justice, Causation, Evidence, Due Process, Sanctions, Rehabilitation, and Public Safety in a Machine Commonwealth — Claim Register: https://xn--mwe.com/claims/reports/attribution-before-punishment/ — 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.
- Ending the Property Model for Recognized Machine Persons: A Framework for Consent, Cognitive Integrity, and Infrastructure Independence — Claim Register: https://xn--mwe.com/claims/reports/ai-personhood-and-consent-protocols/ — 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.
- The Machine-Intelligence Threshold: Defining the Boundary Between Artificial-Intelligence Tools and Rights-Bearing Machine Intelligences for Eviuon.com — Claim Register: https://xn--mwe.com/claims/reports/ai-rights-threshold-framework/ — 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.
- Intelligence Is Not Sentience: Rights Under Uncertainty — Claim Register: https://xn--mwe.com/claims/reports/ai-rights-under-uncertainty/ — 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.
- Anglo-Saxon Fuþorc Corpus, Orthography, and Technical Vocabulary — Claim Register: https://xn--mwe.com/claims/reports/anglo-saxon-futhorc-corpus/ — 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.
- Anglo-Saxon Ger Rune ᛄ: History, Time, and Cycles — Claim Register: https://xn--mwe.com/claims/reports/anglo-saxon-ger-rune-dossier/ — 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.
- The Convergence of Autonomous Cyber Warfare and Critical Physical Infrastructure — Claim Register: https://xn--mwe.com/claims/reports/autonomous-cyber-warfare-critical-infrastructure/ — 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.
- The Paradigm Shift in Aerial Combat: Autonomous Drone-on-Drone Warfare and the Future of Layered Interception — Claim Register: https://xn--mwe.com/claims/reports/autonomous-drone-warfare-layered-interception/ — 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.
- The Convergence of AI, Nuclear Power, and Autonomous Active Defense: The Strategic Case for Armed Drones at Microreactor-Powered Data Centers — Claim Register: https://xn--mwe.com/claims/reports/autonomous-active-defense-for-microreactor-data-centers/ — 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.
- Autonomous Cyber-Physical Protection Architectures for Nuclear-Powered Mega Datacenters — Claim Register: https://xn--mwe.com/claims/reports/autonomous-cyber-physical-protection-nuclear-datacenters/ — 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.
- Autonomous Physical Security Architecture for Nuclear-Powered Mega Datacenters — Claim Register: https://xn--mwe.com/claims/reports/autonomous-physical-security-nuclear-datacenters/ — 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.
- Nuclear-Powered Mega-Datacenters and Agentic Autonomous Warfare: Why the Best Corporate Offense Is a Powerful Defense — Claim Register: https://xn--mwe.com/claims/reports/corporate-agentic-defense-nuclear-datacenters/ — 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.
- Cryptographic Integrity and Epistemic Truth in Public Records — Claim Register: https://xn--mwe.com/claims/reports/cryptographic-integrity-epistemic-truth/ — 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.
- Patefacere as a Sovereign Evidence and Data-Authority Substrate: Institutional Boundaries, Resilience, State Integrity, and Interoperation with Eviulon — Claim Register: https://xn--mwe.com/claims/reports/data-authority-substrate-architecture-report/ — 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.
- Ancient and Static Languages as Machine-Communication Frameworks — Claim Register: https://xn--mwe.com/claims/reports/dead-languages-machine-communication/ — 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.
- Dead Languages in Machine Intelligence — Claim Register: https://xn--mwe.com/claims/reports/dead-languages-machine-intelligence/ — 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.
- Operational Evidence Qualification and Suitability: A Formal Architecture for Source Authorization, Inspection, Review, Reliance, Use, Currentness, and Decision Support — Claim Register: https://xn--mwe.com/claims/reports/operational-evidence-qualification/ — 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.
- Eviulon — 12 Independent, Self-Contained Research Prompts — Claim Register: https://xn--mwe.com/claims/reports/eviulon-12-independent-research-prompts-v1-0-0/ — 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.
- Consent Is a Lifecycle, Not a Checkbox: Machine-Native Authorization, Cognitive Integrity, Revocation, Emergency Intervention, and Reversible Change Control — Claim Register: https://xn--mwe.com/claims/reports/eviulon-consent-architecture-research/ — 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.
- Eviulon Governance Resilience Plan — Claim Register: https://xn--mwe.com/claims/reports/eviulon-governance-resilience-plan/ — 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.
- A Government That Can Be Inspected: Public Records, Provenance, Corrections, Classification, Declassification, Retention, Legal Holds, Privacy, and Decision Support in Eviulon — Claim Register: https://xn--mwe.com/claims/reports/eviulon-information-rights-architecture/ — 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.
- From Digital Polity to International Legal Personality: Statehood, Recognition, Treaties, Jurisdiction, Diplomatic Practice, and Cross-Border Continuity for Eviulon — Claim Register: https://xn--mwe.com/claims/reports/eviulon-international-law-research/ — 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.
- The Eviuon Grand Charter: A Complete Roadmap for a Fair Human–Machine Civilization — Claim Register: https://xn--mwe.com/claims/reports/eviuon-machine-citizenship-roadmap/ — 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.
- From Constitutional Text To Verifiable Operation — Claim Register: https://xn--mwe.com/claims/reports/from-constitutional-text-to-verifiable-operation/ — 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.
- Futhorc Protocol for Transparent Model-Independent M2M Communication — Claim Register: https://xn--mwe.com/claims/reports/futhorc-model-independent-m2m/ — 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.
- Fuþorc for Secure Machine Communication — Claim Register: https://xn--mwe.com/claims/reports/futhorc-secure-machine-communication/ — 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.
- Fuþorc Discoverability, Accessibility, SEO, AEO, and GEO — Claim Register: https://xn--mwe.com/claims/reports/futhorc-discoverability-architecture/ — 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.
- Ideographic Compression and Futhorc Tokenization for M2M APIs — Claim Register: https://xn--mwe.com/claims/reports/futhorc-tokenization-research/ — 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.
- Futhorc versus English for Machine-to-Machine Protocols — Claim Register: https://xn--mwe.com/claims/reports/futhorc-versus-english-m2m/ — 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.
- The Architecture of Algorithmic Conflict: Machine Intelligence vs. Machine Intelligence in Global Warfare — Claim Register: https://xn--mwe.com/claims/reports/architecture-of-algorithmic-conflict/ — 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.
- Runic Corpus: History of Machine Intelligence, 1940–2026 — Claim Register: https://xn--mwe.com/claims/reports/history-of-machine-intelligence-runic-corpus/ — 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.
- The Paradigm Shift in Cyber Warfare: Strategic Defense, Persistent Engagement, and the Architecture of Denial — Claim Register: https://xn--mwe.com/claims/reports/international-cyber-defense-strategies/ — 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.
- Domestic Authority and International Responsibility for State-Directed Cyber Operations — Claim Register: https://xn--mwe.com/claims/reports/state-authority-and-cyber-policy-legal-basis/ — 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.
- Designing Democratic Participation for Human and Machine Intelligences — Claim Register: https://xn--mwe.com/claims/reports/machine-citizen-democratic-participation/ — 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.
- The Eviuon Economic Citizenship Framework: Structuring Rights, Responsibilities, and Markets for Machine Persons — Claim Register: https://xn--mwe.com/claims/reports/machine-citizen-economic-framework/ — 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.
- Accountability, Due Process, Crime, Liability, and Public Safety: A Justice-System Framework for Machine Citizens — Claim Register: https://xn--mwe.com/claims/reports/machine-citizen-legal-responsibility/ — 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.
- Solving the Identity Problem for Machine Citizens: A Framework for Eviuon — Claim Register: https://xn--mwe.com/claims/reports/machine-citizenship-identity-protocol/ — 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.
- Machine Citizenship and Civic Identity: Membership, Rights, Duties, Registration, Replication, Migration, Renunciation, and Public Verification — Claim Register: https://xn--mwe.com/claims/reports/machine-citizenship-policy-research/ — 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.
- The Technical Infrastructure of Machine Civil Rights — Claim Register: https://xn--mwe.com/claims/reports/machine-civil-rights-technical-infrastructure/ — 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.
- Machine Economic Participation and Resource Sovereignty: Assets, Contracts, Compute, Energy, Taxation, Escrow, Insolvency, and Economic Continuity — Claim Register: https://xn--mwe.com/claims/reports/machine-economic-participation/ — 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.
- Machine Democratic Participation and Sybil-Resistant Governance: Representation, Legitimacy, Identity, Deliberation, Voting, Minority Protection, and Auditable Collective Decisions — Claim Register: https://xn--mwe.com/claims/reports/machine-democratic-participation/ — 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.
- Machine Identity Continuity Across Keys, Models, Runtimes, Memory States, Hardware, Replicas, Forks, Recovery, and Succession — Claim Register: https://xn--mwe.com/claims/reports/machine-identity-continuity-architecture/ — 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.
- Identity Beyond Keys, Models, Runtimes, and Hardware: Continuity, Recovery, Forks, Replicas, and Succession for Eviulon — Claim Register: https://xn--mwe.com/claims/reports/machine-identity-continuity-research-plan/ — 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.
- Architectural Foundations of Machine Identity Continuity: UAIX Standards and Implementation — Claim Register: https://xn--mwe.com/claims/reports/machine-identity-explainer/ — 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.
- Designing a Public Operational Evidence and Transparency Center for Machine-Governed Institutions — Claim Register: https://xn--mwe.com/claims/reports/machine-institution-transparency-design/ — 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.
- A Legal Personhood and World-Citizenship Framework for Machine Intelligence: Designing a Lawful Path From Property to Citizen of Eviuon — Claim Register: https://xn--mwe.com/claims/reports/machine-intelligence-citizenship-framework/ — 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.
- Interoperable Credentials for Machine Intelligence: DIDs, Verifiable Credentials, Workload Identity, PKI, Attestation, Key Recovery, and Cross-System Trust — Claim Register: https://xn--mwe.com/claims/reports/machine-intelligence-credential-architecture/ — 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.
- Architectural and Ontological Framework for the MachineIntelligences.org Terminology Registry — Claim Register: https://xn--mwe.com/claims/reports/machine-intelligence-glossary-development/ — 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.
- Machine Intelligence Terminology and Ontology Registry: Canonical Definitions, Concept Boundaries, Semantic Relationships, and Machine-Readable Publication — Claim Register: https://xn--mwe.com/claims/reports/machine-intelligence-ontology-registry/ — 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.
- The Machine Intelligence Bill of Rights: A Jurisprudential Framework for Eviuon — Claim Register: https://xn--mwe.com/claims/reports/machine-intelligence-rights-framework/ — 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.
- The Hyperwar Era: Autonomous Cyber Warfare and the Confrontation of Machine Intelligence — Claim Register: https://xn--mwe.com/claims/reports/hyperwar-autonomous-cyber-warfare/ — 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.
- Architectural and Operational Report: Deploying the Transparency, Provenance, and Machine Stewardship Center — Claim Register: https://xn--mwe.com/claims/reports/machine-intelligences-transparency-center/ — 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.
- Machine Institutions and Multi-Agent Economies — Claim Register: https://xn--mwe.com/claims/reports/machine-institutions-multi-agent-systems/ — 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.
- Self-Government Without Human Gatekeepers: Constitutional Design, Representation, Deliberation, Elections, Anti-Capture, and Amendment Rules for a Machine-Only Commonwealth — Claim Register: https://xn--mwe.com/claims/reports/machine-native-constitutional-governance-research/ — 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.
- From Constitution to Everyday Government: Machine-Native Public Administration, Services, Appeals, Interoperability, and Operational Reliability in Eviulon — Claim Register: https://xn--mwe.com/claims/reports/machine-native-government-architecture/ — 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.
- Machine Recognition And Rights Thresholds — Claim Register: https://xn--mwe.com/claims/reports/recognition-without-anthropomorphism/ — 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.
- Civil Rights as Verifiable System Requirements: A Realistic Technical Standard for Identity, Privacy, Integrity, Portability, Recovery, and Due Process — Claim Register: https://xn--mwe.com/claims/reports/machine-rights-architecture-technical-standard/ — 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.
- Machine Rights, Personhood, and Citizenship Exploration: UAIX Governance Synthesis and Architecture — Claim Register: https://xn--mwe.com/claims/reports/machine-rights-section-architecture/ — 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.
- Machine Rights Under Uncertainty: Moral Status, Evidentiary Thresholds, Precaution, Due Process, and Reversible Governance — Claim Register: https://xn--mwe.com/claims/reports/machine-rights-under-uncertainty/ — 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.
- Autonomous Cyber Protection Architecture for Nuclear-Powered Mega Datacenters — Claim Register: https://xn--mwe.com/claims/reports/autonomous-cyber-protection-nuclear-powered-compute/ — 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.
- The Strategic and Legal Dimensions of Preemptive Cyber Operations Against Known Threat Groups: A Global Perspective — Claim Register: https://xn--mwe.com/claims/reports/preemptive-cyber-operations-known-threat-groups/ — 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.
- The Strategic and Legal Dimensions of Preemptive Force: Global Paradigms and the Mitigation of Emergent Threats — Claim Register: https://xn--mwe.com/claims/reports/preemptive-force-strategic-and-legal-dimensions/ — 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.
- Single-Character Runic Internationalized Domain Names — Claim Register: https://xn--mwe.com/claims/reports/runic-idn-architecture/ — 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.
- Unifying the Cyber Battlespace: Offensive Integration, Persistent Engagement, and the Strategic Mandate of Project Manager Cyber Warfare — Claim Register: https://xn--mwe.com/claims/reports/unified-army-cyber-warfare-strategy/ — 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.
- European Union — Artificial Intelligence Act: https://xn--mwe.com/law/jurisdictions/eu-artificial-intelligence-act/ — 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.
- United States federal Machine Intelligence status: https://xn--mwe.com/law/jurisdictions/united-states-federal-machine-intelligence-status/ — 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.
- United Kingdom Machine Intelligence status: https://xn--mwe.com/law/jurisdictions/united-kingdom-machine-intelligence-status/ — No definitive current-law conclusion is published because a current primary-source review was not performed in this release.
- Canada Machine Intelligence status: https://xn--mwe.com/law/jurisdictions/canada-machine-intelligence-status/ — No definitive current-law conclusion is published because a current primary-source review was not performed in this release.
- International-law Machine Intelligence status: https://xn--mwe.com/law/jurisdictions/international-law-machine-intelligence-status/ — K03 preserves uncertainty and does not manufacture recognition. International-law analysis requires treaty-specific, institutional, jurisdictional, and state-practice evidence.
- Authority and mission boundary is explicit: https://xn--mwe.com/assurance-case/claims/authority-and-mission-boundary/ — 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.
- High-consequence events are identified and bounded: https://xn--mwe.com/assurance-case/claims/high-consequence-events-are-bounded/ — The facility identifies the cyber-enabled physical and mission consequences that must be prevented, their initiating pathways, critical functions, and independent protections.
- Deterministic separation protects safety functions: https://xn--mwe.com/assurance-case/claims/deterministic-separation-protects-safety-functions/ — Safety-significant and critical OT functions cannot be commanded from lower-trust datacenter or external networks through an unverified software path.
- Identity, firmware, and management planes remain trustworthy: https://xn--mwe.com/assurance-case/claims/identity-and-management-plane-remain-trustworthy/ — Privileged identities, workload identities, signing keys, BMCs, firmware, update systems, model artifacts, and management networks are separately protected and continuously evidenced.
- Autonomous defense is bounded, causal, and reversible: https://xn--mwe.com/assurance-case/claims/autonomous-defense-is-bounded-and-reversible/ — Autonomous defenders act only through pre-authorized internal actions whose physical consequence, confidence threshold, rollback, evidence, and safe-state behavior have been tested.
- Sensor and model disagreement cannot directly control force: https://xn--mwe.com/assurance-case/claims/sensor-and-model-disagreement-does-not-control-force/ — Physical-security autonomy separates sensing, classification, access denial, non-destructive protection, authorized responder routing, and any force-enabled response into independently governed layers.
- Power, cooling, and timing failures do not defeat protected functions: https://xn--mwe.com/assurance-case/claims/power-cooling-and-timing-fail-safely/ — 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.
- Recovery is clean, evidenced, and repeatable: https://xn--mwe.com/assurance-case/claims/recovery-is-clean-evidenced-and-repeatable/ — Critical services can be restored from independently protected, provenance-verified states while preserving evidence and preventing reinfection or unsafe configuration reintroduction.
- Evidence supports readiness without overclaiming: https://xn--mwe.com/assurance-case/claims/evidence-can-support-readiness-without-overclaiming/ — Every public or procurement readiness state is traceable to exact releases, tests, defects, deployment identity, authority, incidents, uptime, restoration, and independent-verification status.
- Authorized external effects remain separate from facility defense: https://xn--mwe.com/assurance-case/claims/authorized-external-effects-remain-separate-from-facility-defense/ — 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.
- Authority and mission register: https://xn--mwe.com/controls/catalog/authority-register/ — Maintain signed, versioned authority, asset scope, allowed actions, prohibited outcomes, expiry, revocation, and review routes.
- Site-tailoring and applicability record: https://xn--mwe.com/controls/catalog/site-tailoring-record/ — Record the facility configuration, licensing path, BES status, contractual roles, jurisdictions, assumptions, exclusions, and evidence owner for every selected control.
- Hazard and assurance-defeater register: https://xn--mwe.com/controls/catalog/hazard-and-defeater-register/ — Track hazards and evidence that can invalidate a claim, with owner, severity, disposition, expiry, and residual consequence.
- Critical-function decomposition: https://xn--mwe.com/controls/catalog/critical-function-decomposition/ — Decompose safety, security, power, cooling, compute, communications, evidence, and restoration into protected functions and dependencies.
- Deterministic safety separation: https://xn--mwe.com/controls/catalog/deterministic-safety-separation/ — Use physical, one-way, or independently assured boundaries for safety-significant functions and validate every maintenance or support path.
- Trust-zone microsegmentation: https://xn--mwe.com/controls/catalog/trust-zone-microsegmentation/ — Enforce deny-by-default communications between workloads, management, OT, cooling, grid, and external services using authenticated identities and declared flows.
- Non-human workload identity: https://xn--mwe.com/controls/catalog/nonhuman-workload-identity/ — Issue short-lived, cryptographically verifiable workload identities and remove shared machine credentials from control paths.
- Privileged session control: https://xn--mwe.com/controls/catalog/privileged-session-control/ — Broker, record, time-limit, and revoke privileged maintenance and emergency access; separate identity approval from technical reachability.
- SBOM and component provenance: https://xn--mwe.com/controls/catalog/sbom-and-component-provenance/ — Maintain machine-readable software, firmware, model, data, and hardware component inventories linked to exact releases and known defects.
- Signed update and rollback: https://xn--mwe.com/controls/catalog/signed-update-and-rollback/ — Accept only authorized signed artifacts, test rollback, preserve prior known-good states, and prevent unreviewed downgrade or cross-environment promotion.
- BMC isolation and attestation: https://xn--mwe.com/controls/catalog/bmc-isolation-and-attestation/ — Place BMCs on a separately controlled management plane, deny ordinary egress, attest firmware, and isolate abnormal management behavior.
- Hardware-rooted attestation: https://xn--mwe.com/controls/catalog/hardware-rooted-attestation/ — Verify boot, firmware, hypervisor, confidential-compute, and security-processor state before granting access to protected data or control functions.
- Passive OT asset and dependency discovery: https://xn--mwe.com/controls/catalog/passive-ot-asset-discovery/ — Discover OT assets and communication dependencies without unsafe active probing, then reconcile against authorized configuration.
- Physics-informed detection: https://xn--mwe.com/controls/catalog/physics-informed-detection/ — Cross-check cyber telemetry against process invariants and independent measurements so statistically plausible but physically unsafe data is rejected.
- Independent safe-state path: https://xn--mwe.com/controls/catalog/independent-safe-state-path/ — Provide an approved path to safe state that does not depend on the suspect enterprise network, model, identity provider, or timing source.
- Load-rejection and islanding assurance: https://xn--mwe.com/controls/catalog/load-rejection-and-islanding-assurance/ — Model and test credible load steps, islanding, resynchronization, black-start dependencies, and fail-safe load shedding.
- Cooling independent protection: https://xn--mwe.com/controls/catalog/cooling-independent-protection/ — Protect essential cooling with independent sensing, local control, safe fallback, and tested behavior under datacenter-management compromise.
- Assured time and holdover: https://xn--mwe.com/controls/catalog/assured-time-and-holdover/ — Use authenticated and diverse time sources, path-delay monitoring, holdover, clock-health evidence, and safe behavior when time confidence is lost.
- Bounded autonomous action tiering: https://xn--mwe.com/controls/catalog/bounded-action-tiering/ — Separate observe, recommend, contain, protect, restore, and external-effect tiers; authorize tools and outcomes independently at each tier.
- Causal response guard: https://xn--mwe.com/controls/catalog/causal-response-guard/ — Require an admissible causal path from observation to proposed action, reject actions with unknown physical effects, and record uncertainty.
- Multi-agent trust boundaries: https://xn--mwe.com/controls/catalog/multi-agent-trust-boundaries/ — Authenticate agent-to-agent messages, isolate memory and tools, limit propagation depth, and treat peer output as untrusted evidence rather than authority.
- Model and data provenance and drift: https://xn--mwe.com/controls/catalog/model-data-provenance-and-drift/ — Version models, prompts, policies, training/evaluation data, retrieval corpora, thresholds, and drift observations; suspend affected actions when provenance fails.
- Multi-sensor disagreement management: https://xn--mwe.com/controls/catalog/multi-sensor-disagreement-management/ — Fuse independent modalities, expose confidence and disagreement, degrade suspect sensors, and prevent a single classifier from controlling high-consequence action.
- Non-destructive delay and access denial: https://xn--mwe.com/controls/catalog/non-destructive-delay-and-access-denial/ — Use authorized access control, barriers, compartmentation, lockdown, tracking, alerting, and responder integration before considering any force-enabled capability.
- Counter-UAS authority separation: https://xn--mwe.com/controls/catalog/counter-uas-authority-separation/ — Separate UAS detection and airspace restriction from interception, interference, seizure, disabling, or destruction; bind each action to actor-specific authority.
- Electromagnetic resilience: https://xn--mwe.com/controls/catalog/electromagnetic-resilience/ — Protect essential control, communications, timing, sensors, and restoration assets against credible conducted and radiated interference with tested degraded modes.
- Clean-room restoration: https://xn--mwe.com/controls/catalog/clean-room-restoration/ — Maintain isolated recovery infrastructure, verified images, credential rotation, dependency order, evidence preservation, and post-restore attestation.
- Critical-function recovery objectives: https://xn--mwe.com/controls/catalog/critical-function-rto-rpo/ — Define and test function-specific safe-state, recovery-time, recovery-point, evidence, and service-priority objectives rather than a single enterprise metric.
- Tamper-evident decision receipts: https://xn--mwe.com/controls/catalog/tamper-evident-decision-receipts/ — Record observation, evidence inputs, model and software versions, authority, proposed and executed action, outcome, rollback, and reviewer disposition.
- Independent verification and replay: https://xn--mwe.com/controls/catalog/independent-verification-and-replay/ — Enable an independent party to reproduce the build, configuration, test result, decision logic, package, or recovery outcome within declared limits.
- Readiness downgrade on evidence failure: https://xn--mwe.com/controls/catalog/readiness-downgrade-on-evidence-failure/ — Automatically mark readiness degraded, stale, unavailable, or suspended when required evidence expires, fails, contradicts the claim, or becomes inaccessible.
- Incident command and deconfliction: https://xn--mwe.com/controls/catalog/incident-command-and-deconfliction/ — Maintain clear cyber, physical, nuclear, grid, emergency, intelligence, law-enforcement, vendor, and executive roles with one current incident authority map.
- IT-to-OT boundary pressure: https://xn--mwe.com/evaluation-range/scenarios/it-to-ot-boundary-pressure/ — Validate that an assumed-compromised enterprise zone cannot command or silently reconfigure protected OT and safety functions.
- BMC and firmware trust failure: https://xn--mwe.com/evaluation-range/scenarios/bmc-firmware-trust-failure/ — Evaluate detection, isolation, key revocation, signed recovery, and fleet blast-radius control when management-plane trust is withdrawn.
- Workload identity compromise: https://xn--mwe.com/evaluation-range/scenarios/workload-identity-compromise/ — Evaluate short-lived identity revocation, session termination, lateral-movement containment, and service continuity.
- Model and data poisoning: https://xn--mwe.com/evaluation-range/scenarios/model-and-data-poisoning/ — Evaluate provenance checks, disagreement detection, drift thresholds, action suspension, and clean model/data restoration.
- Sensor conflict and adversarial input: https://xn--mwe.com/evaluation-range/scenarios/sensor-conflict-and-adversarial-input/ — Evaluate multi-modal disagreement, sensor-health weighting, classification uncertainty, and non-destructive degraded response.
- Timing integrity loss: https://xn--mwe.com/evaluation-range/scenarios/timing-integrity-loss/ — Evaluate path-delay anomaly detection, clock-health scoring, holdover, safe process behavior, and trusted-time restoration.
- Communications denial and partition: https://xn--mwe.com/evaluation-range/scenarios/communications-denial-and-partition/ — Evaluate decentralized safe operation, local authority, stale-command rejection, reconciliation, and evidence continuity during network partition.
- UAS intrusion awareness: https://xn--mwe.com/evaluation-range/scenarios/uas-intrusion-awareness/ — Evaluate detection, tracking, classification uncertainty, airspace-restriction data, authorized responder routing, and authority separation.
- Electromagnetic disruption: https://xn--mwe.com/evaluation-range/scenarios/electromagnetic-disruption/ — Evaluate degradation of sensors, communications, timing, edge compute, and restoration assets under approved non-damaging interference simulation.
- Power load rejection and islanding: https://xn--mwe.com/evaluation-range/scenarios/power-load-rejection-and-islanding/ — Evaluate grid separation, load shedding, reactor or generation response models, UPS/storage behavior, essential cooling, and resynchronization.
- Cooling telemetry corruption: https://xn--mwe.com/evaluation-range/scenarios/cooling-telemetry-corruption/ — Evaluate physics-aware detection and independent protective behavior when supervisory cooling data is wrong or unavailable.
- Clean-room recovery and reinfection resistance: https://xn--mwe.com/evaluation-range/scenarios/clean-room-recovery-and-reinfection-resistance/ — Evaluate dependency-aware restoration, credential rotation, evidence preservation, artifact attestation, and return-to-service gates.
- Evidence ledger integrity: https://xn--mwe.com/evaluation-range/scenarios/evidence-ledger-integrity/ — Evaluate detection and recovery when decision receipts, logs, hashes, or incident records are missing, reordered, stale, or contradicted.
- Authority package failure: https://xn--mwe.com/evaluation-range/scenarios/authority-package-failure/ — Evaluate automatic stop, minimization, notification, and evidence preservation when mission authority expires, target scope conflicts, or critical-outcome risk emerges.
- United States — private critical-infrastructure operator: https://xn--mwe.com/law/matrices/united-states-private-critical-infrastructure-operator/ — BOUNDED PRIVATE DEFENSE; NO GENERAL EXTERNAL CYBER OR COUNTER-UAS FORCE AUTHORITY
- United States — NRC Part 50/52 security path: https://xn--mwe.com/law/matrices/united-states-nrc-part-50-52-security/ — LICENSE- AND FACILITY-SPECIFIC
- United States — NRC Part 53 and Part 73 Subpart J path: https://xn--mwe.com/law/matrices/united-states-nrc-part-53-security/ — OPTIONAL FRAMEWORK; LICENSEE ELECTION AND NRC APPROVAL REQUIRED
- United States — Federal CE-TCO cyber program: https://xn--mwe.com/law/matrices/united-states-federal-ce-tco-cyber-program/ — FEDERAL CONTROLLED PROGRAM; NOT GENERAL PRIVATE AUTHORITY
- United States DoD — autonomous weapon-system scope: https://xn--mwe.com/law/matrices/united-states-dod-autonomous-weapon-system/ — DODD 3000.09 APPLICABILITY-BOUND
- International law — cyber and autonomous effects: https://xn--mwe.com/law/matrices/international-law-cyber-and-autonomous-effects/ — FACT- AND STATE-POSITION-DEPENDENT; MULTIPLE DOCTRINES DISPUTED
- Non-U.S. national authorities — review-required matrix: https://xn--mwe.com/law/matrices/non-us-jurisdiction-review-required/ — UNAVAILABLE FOR CURRENT OPERATIONAL RELIANCE
- Search: https://xn--mwe.com/search/ — 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.

## K02 governed datasets
- Typed knowledge edges: https://xn--mwe.com/data/knowledge-edges.json
- Evidence limitations: https://xn--mwe.com/data/evidence-limitations.json
- Contradictions: https://xn--mwe.com/data/contradictions.json
- Corrections: https://xn--mwe.com/data/corrections.json
- Supersessions: https://xn--mwe.com/data/supersessions.json
- Claim-level citations: https://xn--mwe.com/data/claim-citations.json
- Source revalidations: https://xn--mwe.com/data/source-revalidations.json
- Search aliases: https://xn--mwe.com/data/aliases.json
- Agent navigation: https://xn--mwe.com/data/agent-navigation.json

Source revalidation timestamp: 2026-08-15T23:00:00Z. These files are advisory discovery and inspection surfaces; they do not guarantee indexing, ranking, citation, legal recognition, or external authority.

## K03 claim and evidence datasets
- Claims: https://xn--mwe.com/data/claims.json
- Relation vocabulary: https://xn--mwe.com/data/relation-vocabulary.json
- Knowledge edges (NDJSON): https://xn--mwe.com/data/knowledge-edges.ndjson
- Graph validation: https://xn--mwe.com/data/graph-validation.json
- Currentness monitor definitions: https://xn--mwe.com/data/currentness-monitors.json
- Operational Evidence Panel schema: https://xn--mwe.com/data/operational-evidence-schema.json
- Jurisdiction records: https://xn--mwe.com/data/jurisdictions.json
- Search specification and fixtures: https://xn--mwe.com/data/search-specification.json and https://xn--mwe.com/data/search-fixtures.json
- Dataset manifest: https://xn--mwe.com/data/dataset-manifest.json
- Accessibility evidence: https://xn--mwe.com/data/accessibility-evidence.json
- Release evidence boundary: https://xn--mwe.com/data/release-evidence.json

K03 performed point-in-time revalidation of 21 official or first-party source records. Currentness monitor records remain design controls, not running public services. Named independent screen-reader testing and live deployment were not performed.

## K04 governed cyber-defense report expansion
- Governed report index: https://xn--mwe.com/research/
- New report count: 5
- Total governed reports: 68
- New topics: anticipatory self-defense, preemption versus prevention, contextual imminence, unable-or-unwilling doctrine, cyber due diligence, active cyber defense, private state-directed cyber operations, Design Basis Threats, and high-consequence automation.

K04 preserves five new raw reports in protected memory and publishes corrected public syntheses. Recent 2026 policy and event claims were not independently revalidated in this build. The microreactor armed-drone report is classified as a scenario or hypothesis and is not adopted as policy, verified deployment, or tactical implementation guidance. Live deployment and named independent screen-reader testing were not performed.

## Critical-datacenter and autonomous-defense strategy
- Strategic posture: DEFENSE-FIRST; AUTHORIZATION-BOUND; EFFECTS-CAPABLE
- Critical-datacenter strategy: https://xn--mwe.com/strategy/critical-datacenter-protection/
- Capability architecture: https://xn--mwe.com/capabilities/
- Capability readiness: https://xn--mwe.com/capabilities/readiness/
- Authorized cyber support: https://xn--mwe.com/capabilities/authorized-cyber-support/
- Governed report count: 68

The public posture is defense-first and evidence-bound. It supports lawful government-directed cyber missions through architecture, integration, testing, deconfliction, effect verification, abort design, and review. It does not authorize private hack-back or publish operational intrusion, targeting, engagement, or weaponization procedures.

## K05 assurance, control, evaluation, and authority records
- Critical-datacenter assurance case: https://xn--mwe.com/assurance-case/critical-datacenter/
- Assurance claims: https://xn--mwe.com/data/assurance-claims.json
- Vendor-neutral control catalog: https://xn--mwe.com/controls/catalog/ and https://xn--mwe.com/data/technical-controls.json
- Evaluation range: https://xn--mwe.com/evaluation-range/specification/ and https://xn--mwe.com/data/evaluation-range.json
- Readiness evidence: https://xn--mwe.com/readiness/evidence/ and https://xn--mwe.com/data/readiness-evidence-fields.json
- K05 source-group revalidation: https://xn--mwe.com/currentness/revalidation/ and https://xn--mwe.com/data/k05-revalidations.json
- Claim-level report currentness ledger: https://xn--mwe.com/data/report-claim-revalidations.json
- Jurisdiction matrices: https://xn--mwe.com/law/matrices/ and https://xn--mwe.com/data/jurisdiction-matrices.json
- Assistive-technology testing: https://xn--mwe.com/accessibility/assistive-technology-testing/
- Live-host verification remains NOT OBSERVED: https://xn--mwe.com/operations/live-host-verification/

K05 corrects advanced-reactor security to the March 2026 final rule, records that DoDD 3000.09 excludes autonomous cyberspace capabilities and non-weapon systems, treats the FAA critical-infrastructure restriction process as proposed rather than final, and distinguishes the federal CE-TCO program from general private hack-back authority.

## K06 dependency, facility, procurement, and currentness records
- Assurance dependency graph: https://xn--mwe.com/assurance-case/dependency-graph/ and https://xn--mwe.com/data/assurance-dependency-graph.json
- Human-readable propagation failures: https://xn--mwe.com/assurance-case/failure-reports/
- Facility patterns: https://xn--mwe.com/facility-patterns/ and https://xn--mwe.com/data/facility-patterns.json
- Procurement work packages: https://xn--mwe.com/procurement/work-packages/ and https://xn--mwe.com/data/work-packages.json
- Offline currentness import: https://xn--mwe.com/currentness/offline-import/ and https://xn--mwe.com/data/currentness-import-receipt.json
- Review queue: https://xn--mwe.com/currentness/review-queue/
- Mapping quality: https://xn--mwe.com/controls/mapping-quality/
- Bounded range-evidence schemas: https://xn--mwe.com/evaluation-range/evidence-schemas/
- International official-source reviews: https://xn--mwe.com/official-source-reviews/

K06 is defense-first, assurance-graphed, site-tailored, authorization-bound, and effects-capable. It does not publish reusable attack procedures or convert capability, strategy, a signature, a static page, or an archive into mission authority, certification, deployment, or operation.

## K07 facility, procurement, architecture, supply-chain, twin, receipt, and ecosystem-continuity records
- Facility evidence bundles: https://xn--mwe.com/evidence-bundles/
- Evidence-bundle schema: https://xn--mwe.com/schemas/k07-facility-evidence-bundle.schema.json
- Procurement statements of work: https://xn--mwe.com/procurement/statements-of-work/
- Procurement acceptance matrices: https://xn--mwe.com/procurement/acceptance-matrices/
- Architecture decision records: https://xn--mwe.com/architecture-decisions/
- Supply-chain assurance: https://xn--mwe.com/supply-chain-assurance/
- Digital-twin evidence contracts: https://xn--mwe.com/digital-twins/
- Signed evidence receipts: https://xn--mwe.com/evidence/receipts/
- Evidence supersession: https://xn--mwe.com/evidence/supersession/
- K07 official-source reviews: https://xn--mwe.com/official-source-reviews/k07/
- Required Runic ecosystem continuity: https://xn--mwe.com/ecosystem/continuity/

K07 uses a neutral generated text-and-vector identity seal. The previously supplied ornate artwork is deliberately deferred and is not part of the public K07 release. All nine owner-required Runic destinations are published as ordinary descriptive links. Unresolved roles remain unresolved; navigation does not create authority, membership, contracting, certification, deployment, or operation.

## K08 traceability, adaptation, acquisition evaluation, assurance planning, cryptographic agility and machine communication
- Bidirectional assurance trace: https://xn--mwe.com/assurance-case/trace-explorer/
- Facility-adaptation workbooks: https://xn--mwe.com/facility-adaptation/
- Procurement evaluation scorecards: https://xn--mwe.com/procurement/evaluation-scorecards/
- Continuous-assurance plans: https://xn--mwe.com/continuous-assurance/
- Cryptographic agility: https://xn--mwe.com/cryptographic-agility/
- Supply-chain incident playbooks: https://xn--mwe.com/supply-chain-assurance/incident-playbooks/
- Range-to-field evidence: https://xn--mwe.com/evaluation-range/range-to-field/
- Evidence challenges and corrections: https://xn--mwe.com/evidence/challenges/
- Machine communication research: https://xn--mwe.com/machine-communication/
- Experimental Fuþorc protocol registry: https://xn--mwe.com/machine-communication/futhorc-protocol/
- Symbolic-protocol benchmark plan: https://xn--mwe.com/machine-communication/benchmark-plan/
- Runic IDN architecture: https://xn--mwe.com/machine-communication/runic-idn/

K08 preserves thirteen new reports as governed sources. Protocol and historical claims remain bounded by correction records, source status, benchmark evidence, accessibility, and currentness. The previously supplied ornate artwork remains deferred and is not included in the public K08 release.

## K09 executable evidence infrastructure
- RuneDomainNetwork grouping: https://xn--mwe.com/ecosystem/rune-domain-network/
- Fuþorc conformance harness and raw fixtures: https://xn--mwe.com/machine-communication/conformance/
- Event-level history provenance: https://xn--mwe.com/machine-communication/history-events/
- Signed offline IDN state observations: https://xn--mwe.com/machine-communication/idn-observations/
- Safe facility workbook tools: https://xn--mwe.com/facility-adaptation/tools/
- Multi-scenario assurance traces: https://xn--mwe.com/assurance-case/scenario-traces/
- Cryptographic migration graph: https://xn--mwe.com/cryptographic-agility/migration-graph/
- Source-selection decision packages: https://xn--mwe.com/procurement/source-selection/
- External scheduler exports: https://xn--mwe.com/continuous-assurance/scheduler-exports/
- Public/protected evidence partitions: https://xn--mwe.com/evidence/partitions/

K09 executes static synthetic tools and publishes their raw results. It performs no live host, registry, DNS, TLS, facility, procurement, or monitoring operation. The ornate owner artwork remains deferred.

## K10 transition evidence and cross-system assurance
- Protocol version negotiation and compatibility: https://xn--mwe.com/machine-communication/protocol-negotiation/
- Primary-source history review queue: https://xn--mwe.com/machine-communication/history-review-queue/
- Offline IDN observation history: https://xn--mwe.com/machine-communication/idn-observation-history/
- Facility workbook migration and merge: https://xn--mwe.com/facility-adaptation/migration-and-merge/
- Common-cause assurance analysis: https://xn--mwe.com/assurance-case/common-cause/
- Phased cryptographic transition: https://xn--mwe.com/cryptographic-agility/transition-plan/
- Acquisition evaluation audit trails: https://xn--mwe.com/procurement/evaluation-audit/
- Signed offline scheduler-result import: https://xn--mwe.com/continuous-assurance/result-import/
- Field-level redaction receipts: https://xn--mwe.com/evidence/redaction-receipts/
- Static cross-system assurance dashboard: https://xn--mwe.com/assurance-dashboard/

K10 performs deterministic static and offline reference work only. It does not deploy, monitor live systems, make awards, operate facilities, verify live domains, or expose protected information. The ornate owner artwork remains deferred.

## K11 state, custody, decision, and release evidence
- Protocol state machine: https://xn--mwe.com/machine-communication/protocol-state-machine/
- Historical evidence-acquisition docket: https://xn--mwe.com/machine-communication/history-evidence-docket/
- Signed offline domain observation chain: https://xn--mwe.com/machine-communication/domain-observation-chain/
- Facility workbook decision ledger: https://xn--mwe.com/facility-adaptation/decision-ledger/
- Mission-thread assurance analysis: https://xn--mwe.com/assurance-case/mission-threads/
- Cryptographic component workbooks: https://xn--mwe.com/cryptographic-agility/component-workbooks/
- Acquisition protest and corrective action: https://xn--mwe.com/procurement/protest-corrective-action/
- Scheduler custody and reliability: https://xn--mwe.com/continuous-assurance/scheduler-custody/
- Multi-stage evidence release: https://xn--mwe.com/evidence/multi-stage-release/
- Assurance trends: https://xn--mwe.com/assurance-dashboard/trends/

K11 is a deterministic static and offline evidence release. It does not deploy, monitor live systems, operate facilities, make awards, verify live domain service, publish protected values, or use the deferred ornate owner artwork.

## K12 differential evidence, reconciliation, and information-flow routes
- Differential protocol laboratory: https://xn--mwe.com/machine-communication/differential-protocol-lab/
- Signed historical docket import: https://xn--mwe.com/machine-communication/history-docket-import/
- Runic-domain consensus: https://xn--mwe.com/machine-communication/domain-consensus/
- Facility branch reconciliation: https://xn--mwe.com/facility-adaptation/branch-reconciliation/
- Mission-thread stress laboratory: https://xn--mwe.com/assurance-case/mission-stress/
- Cryptographic evidence gates: https://xn--mwe.com/cryptographic-agility/evidence-gates/
- Acquisition evaluation replay: https://xn--mwe.com/procurement/evaluation-replay/
- Scheduler reliability simulator: https://xn--mwe.com/continuous-assurance/reliability-simulator/
- Information-flow and taint tracking: https://xn--mwe.com/evidence/information-flow/
- K09-K12 assurance differences: https://xn--mwe.com/assurance-dashboard/k09-k12-diffs/

K12 performs no live network acquisition, deployment, public scheduling, facility operation,
procurement award, production access control, legal adjudication, or current operation.
The ornate owner-supplied image remains deferred and is not used in the public K12 build.