Ivan KotovAI Systems Architect

Publication bridge · v0.1 · DOI role unresolved

Beacon Profile v0.1 — Inter-Entity Recognition for Sovereign Digital Entities

DOI-safe discovery and publication metadata for the historical profile. This additive route does not alter or supersede the historical bytes.

Publication record

Published identifier, bounded role

Author: Ivan Kotov · ORCID 0009-0009-6002-9845

Document version: v0.1 · Document date: 2026-03-09 (not asserted as the Zenodo publication date)

Published DOI: 10.5281/zenodo.18933553 · DOI role: unresolved pending authoritative relation metadata

Version DOI: not asserted · Concept DOI: unresolved; no neighboring DOI is inferred · Zenodo record

Repository source after finalization: 20cfd66e602c9d5d65f952a433217d104a264318 · immutable publication bridge

Zenodo metadata and file inventory have not been ingested into this site package. Exact Zenodo ↔ GitHub byte identity is not claimed.

Status ceiling

Informative profile, local requirements

Published DOI-linked informative synthesis profile containing normative-style local requirements. It is not a standards-track specification, not a certification regime, and not a completed cryptographic conformance package.

MUST / SHOULD language expresses the profile's local design requirements but does not by itself establish independent interoperability.

Historical bytes and metadata

Direct local resources

Living source: main. Historical immutable source: commit 15695853223c798379538aad69dc573730e1ee96.

Public implementation evidence

Structural reference classifier and persistence sidecar.

Implementation module · Implementation tests

Currently demonstrates: Beacon bundle data structures; Slot A / Slot B classification flow; fail-closed downgrade; class-to-privilege mapping; local persistence of bundles and decisions; default rejection of raw-memory disclosure.

Does not currently demonstrate: recomputation of payload hashes; cryptographic signature verification; Ed25519 verification; key resolution; key rotation or revocation proof; witness-reference resolution; challenge execution; independent interoperability; production deployment conformance.

Protocol boundary

Recognition, evidence, transfer and authority remain distinct

  • Beacon owns recognition semantics.
  • VXCX owns bounded visual-experience capsule structure and transfer.
  • L4 Witness owns challengeable evidence and consequence-bearing resolution.
  • Valid VXCX evidence cannot independently raise Beacon class.
  • Beacon recognition cannot independently prove VXCX content truth.
  • Authority remains a separate local policy decision.

Bridge discipline

Publication boundaries without theory duplication

Explicit bridge coverage remains in canonical section 16. The two hidden bridges remain Ashby/requisite variety and bounded information-theoretic disclosure. Engineering/anatomical grounding remains in canonical section 17. This site route adds publication and implementation boundaries only.

Citation

Suggested citation

Kotov, Ivan. Beacon Profile v0.1 — Inter-Entity Recognition for Sovereign Digital Entities. v0.1, document dated 2026-03-09. Published DOI: 10.5281/zenodo.18933553.

Non-claims

What publication and recognition do not establish

  • No proof of consciousness, sentience or personhood.
  • No legal identity or civil status.
  • No universal identity oracle.
  • No provider-independent deployment certificate.
  • No cryptographic conformance claim.
  • No claim that API-key possession equals entity identity.
  • No claim that access authority equals continuity identity.