Ivan Kotov AI Systems Architect

Living corpus entry

Start here

This page is the shortest route into the public corpus. It starts from one rule - no status elevation without admissible evidence - and shows how the programme separates definition, implementation, testing, reproduction, validation, authority, continuity, and public claims.

  • BaselineB0
  • Last verified2026-07-19
  • Deltas through2026-07-20

Architecture

Architecture in 90 seconds

The corpus is easiest to read as a control system rather than as a publication timeline. The central rule is that a weaker state must not be described or used as a stronger one until evidence supports the transition. A definition does not become an implementation; an implementation does not become a tested system; a test by the same operator does not become independent reproduction; a public page does not become external validation.

In `c = a + b`, `c` names the governed candidate entity layer, `a` names the accountable human anchor, and `b` names bounded procedures, memory, models, tools, routes, witnesses, and execution surfaces. The `+` is not arithmetic addition. It is a governed binding: a rule for when human authority, procedural substrate, evidence, and witness records may be combined without laundering one status into another.

L3 and L4 are the bridge between rules and consequence. L3 contains classifications, permissions, procedures, review conditions, and admissibility rules. L4 is the physical and operational boundary: time, energy, cost, latency, hardware, custody, irreversible outcomes, and failure. A witness record connects the two by saying what was attempted, under which authority, with which evidence, and what happened.

The current B0 projection is intentionally conservative. It identifies 60 load-bearing artifacts across 17 families, maps 17 protocol families, records 24 open problems, and lists 18 failure or non-confirmation records. It reports zero adequately evidenced runtime failure events in the selected B0 set, and it keeps independent reproduction, external validation, and strict matched profile-control as not identified.

Term boundary

L3 means rules, classifications, permission paths, and admissibility controls. L4 means physical, temporal, energetic, operational, and irreversible consequence. Witness means the record that connects an L3 decision to an L4 result. A capable model, agent harness, memory store, or cloud assistant is not automatically c.

Diagram

Architecture diagram

Living corpus architecture from rule to consequence Models, agents, memory, and tools belong to the governed substrate `b`. They may be replaced or delegated. The continuing participant represented by `c` carries the history of commitments, authority boundaries, witness, and consequence under governed binding. The diagram labels `c` as a continuity-bearing participant locus. No status elevation without admissible evidence a accountable human anchor permission and responsibility b bounded substrate Agents / tools replaceable bounded instruments + c governed candidate layer continuity-bearing participant locus L3 rules and admissibility Witness record of transition L4 real consequence boundary Status changes only through evidence, transition conditions, and reviewable records.

Bridge

From rule to consequence

The corpus treats governance as a transition chain, not as a slogan.

Rule

A status claim starts as a bounded statement with a declared class and evidence requirement.

Witness

A transition needs a reviewable record of authority, scope, action, result, and limitation.

Consequence

The result must survive physical, operational, and custody constraints before stronger wording is allowed.

Status

Current programme state

60 B0 artifact rows

Verified Step 2 classification.

17 Protocol families

Verified Step 3 protocol map.

24 Open problems

Critical, High, and Medium records.

0 Runtime failure events

Adequately evidenced events in the selected B0 set.

Independent reproduction, external validation, and strict matched profile-control are recorded as not identified. That boundary is part of the status, not a footnote.

Depth

Choose your depth

Overview

Architecture, current status, source controls, and claim boundary.

Open

Protocol map

Seventeen protocol-family transitions and the risks each blocks.

Open

Current state

B0 status matrix, counts, implementation surfaces, and publication deltas.

Open

Open problems

Twenty-four unresolved questions, priorities, drafting effects, and next evidence needs.

Open

Failures

Eighteen failure or non-confirmation records, with no invented runtime failures.

Open

Changes

Public-surface changes since B0, without status elevation.

Open

Audience

Choose your route

Policy readers

Article 50 transparency -> Evidence -> Open problems

Start

Engineers

CGAM -> L4 -> SER -> Current state

Start

Researchers

Glossary -> Distinctions -> Protocol map -> Failures

Start by separating the execution instrument from the continuity-bearing participant: agents act under bounded delegation; c carries the continuing relation.

Start Distinctions c = a + b Current state Publications

Independent reviewers

Current state -> JSON endpoints -> Open problems

Start

Protocols

Protocol-map preview

Six examples from the 17 verified protocol-family records.

PM-001 - Corpus control and canonical routing

Unrouted or duplicated source -> claim-scoped canonical reading route and ownership boundary.

PM-002 - Claims, maturity, and non-claims control

Unbounded statement -> typed claim class, maturity vector, explicit non-claim, or narrowed disposition.

PM-003 - c = a + b, theoretical core, and c-calculus

Human anchor plus procedural substrate -> bounded governed-binding or c-candidate architecture claim.

PM-004 - SER continuity and sovereign recursion

Stored state or transition history -> bounded classification as continuation, replay, archive, fork, or successor.

PM-005 - L4 Witness and claim ceilings

Event, transition, or outcome -> typed witness record, evidence level, and bounded claim ceiling.

PM-006 - ARQ bounded adaptation

Deviation or anomaly -> suppress, quarantine, review, retain, recalibrate, or safely degrade under declared rules.

Open the full protocol map

Deltas

Changes since B0

2026-07-17 - Cleanroom ARM-P open verification release v1.0.1 surfaced publicly

No B0 status elevation. Independent reproduction and external validation remain not identified in the living corpus status map.

2026-07-19 - ESTHER-RP-001 v0.8.1 publication surface added

No scientific or validation status is raised by the publication page. The release remains bounded by its own reproducibility package and review call.

2026-07-19 - Living Corpus Entry Layer v62 added to the website

Adds public navigation, status projection, and JSON receipts. It does not alter the frozen B0 classification or any source protocol.

2026-07-20 - Agent instrument / c participant distinction

Clarifies the architectural separation between delegated agent work and the continuity-bearing participant role of c. No Baseline B0, Theoretical Core, protocol, implementation, reproduction, validation, empirical, legal, personhood, or entity-classification status is elevated.

2026-07-20 - Vision living authorial layer v0.1 published

Adds a living, future-facing authorial page and machine-readable route surfaces. It does not alter Baseline B0, Theoretical Core, protocol, implementation, test, replication, validation, empirical, legal, consciousness, personhood, or entity-classification status.

Problems

What remains unresolved

Open all 24 open problems

Sources

Canonical sources

Optional self-check
  1. What is the central rule?
  2. Which evidence would be needed before a definition becomes an implementation claim?
  3. Which page lists the 24 unresolved problems?
  4. What is explicitly not being claimed?
  5. What is the difference between an agent and c?
    Start here callout Distinctions anchor

Boundary

Claim boundary

This living corpus projection is a reader-facing status map. It does not assert scientific consensus, external validation, independent reproduction, operational deployment, legal certification, sentience, personhood, consciousness, or proof of AGI.

It is a public navigation and status-control layer over verified B0 consolidation registers. It does not modify the frozen source packages or the reference extraction.