# Doll-layer placement (2026-10-15)

The two kernel seats of the organism, and the boundary between them.
Formalizes the placement the boot conformance review DEFERRED. Companion to
`modules/kido-interop.h`, which implements the boundary's protocol.

## The seats

|                | Inner seat              | Outer seat                |
|----------------|-------------------------|---------------------------|
| Kernel         | BUBO                    | Kido                      |
| Heritage       | C, x86-bound            | Portable C, adaptive      |
| Posture        | Deep and fixed          | Outer and adaptive        |
| Holds          | The inner system        | The outer (language ball) |
| Adaptivity     | None owed               | All of it (spec identity) |

The seats are fixed. Only the outer seat moves. This is not a hierarchy of
importance — it is a division of the stack by doll layer, not by
competition. There is no leader election, no preemption across kernels, no
resource-contention protocol: the kernels do not compete, so the protocol
does not arbitrate.

## What lives where

- **Inner (BUBO):** deep system services, the stable core. Fixed drivers,
  no probing. It answers, it does not adapt.
- **Outer (Kido):** the language ball — agent signaling (`kido-resonate`),
  language-synthesis material, portable boot (`kido-boot`), adaptive
  drivers (`kido-hal`). Everything Kido does, it does in a way that could
  run somewhere BUBO cannot.

## The boundary

The boundary is `kido-interop`: an envelope protocol, asymmetric by law.

- **Kido's duties:** probe for the peer (ANNOUNCE), adapt to its absence
  (SOLO state, loud), wrap signals in the envelope, measure hop decay on
  ingress.
- **BUBO's duties:** answer ANNOUNCE with ANNOUNCE_ACK. Nothing else is
  owed. The stable side is never asked to be adaptive.
- **Solo law:** Kido boots, runs, and signals in-kernel with no peer at
  all. The announce proved absence; absence is a fact, not a failure.
  (BUBO-as-code is Phase 4; Kido does not wait for it.)

## What crosses the boundary

- `ANNOUNCE` / `ANNOUNCE_ACK` — seat presence (handshake).
- `SYS` — system/service traffic between the seats.
- `LANG` — language-ball material: synthesized language fragments flowing
  across the boundary. This is Kido's outer-seat identity made into a
  packet type.

## What never crosses

Scheduler internals, allocator state, raw memory maps, HAL tables. The
kernels share signals, not innards. Each kernel's internals stay on its
own side of the doll layer.

## Transport honesty

There is no inter-kernel bus yet — no shared memory region, no link
driver on bare metal, and none is guessed. The driver contract
(`kido_link_t`) names no medium. Until a real transport exists, every
cross-boundary send on bare metal fails loud (`KIDO_ERR_STUB_REACHED`,
documented mapping). The hosted loopback pipe proves Kido's side of the
protocol today; the real medium is a future Gate item, not a present
invention.

## Status

Placement: DEFINED (this document). Protocol: DRAFT (`kido-interop`,
Kido's side real, peer simulated in tests). Transport medium: DECLARED
STUB. Nothing here finalizes a bootable kernel; first boot is N8toriousAi's
to witness.
