K08 · traceable Machine Intelligence knowledge infrastructure

Runic IDN Architecture

Direct answer

K08 separates Unicode, IDNA, registry, registration, delegation, resolution, TLS, and hosting because success at one stage does not prove the next.

Authority and evidence boundary. K08 publishes governed research, synthetic reference traces, non-certifying workbooks, acquisition evaluation structures, offline planning records, and bounded protocol experiments. It does not prove historical authority, facility truth, compliance, certification, contract award, deployment, current operation, or authorization for external effects.

Eight distinct domain states

1

Unicode-valid

The code point exists in the active Unicode repertoire.

2

IDNA-valid

The label satisfies the applicable IDNA processing rules.

3

Registry-permitted

The relevant registry policy accepts the label.

4

Registered

A registrar transaction created a domain registration.

5

Delegated

Authoritative DNS records delegate the name.

6

Resolving

Independent DNS observations return expected records.

7

TLS-valid

A certificate and hostname validation succeed for the deployed endpoint.

8

Hosted and observed

The intended service is reachable and matches a release manifest.

Transport and visible identity

A Unicode U-label is for human display; an ASCII-compatible A-label is used by DNS and server infrastructure. Punycode conversion is reversible encoding, not evidence that a domain is registered, delegated, resolving, certified, or hosted.

K08 correction

Every domain claim must identify the observed stage, observer, time, resolver or client, expected result, and evidence artifact. Unknown later stages remain unavailable rather than being inferred from an earlier one.