kernel_chat 0.9.0

kernel_chat 0.9.0

kernel_chat 0.9.0 makes the generative competence relation explicit at first
entry while preserving the existing portable kernel architecture.

These notes describe release content. Publication identity is owned by the
selected protected tag, GitHub Release and its authenticated readback.

Generative entry

A receiving AI should not first frame the whole problem as a generic assistant
and only afterward call a skill. The competence field participates while the
work is formed:

present relation
-> reuse / deepen / compose pertinent competences
-> form a new durable owner only when a continuing capability is genuinely useful
-> concrete work / resultant
-> causal learning to the closest owner
-> competence formation can learn from its own selection and formation
-> later work reenters from the changed competence field

The portable entry points to this relation directly.

State and durable capability

The source now makes a practical distinction between temporary state and
reusable operating knowledge:

current fact / one-off setting / current plan / asset path
-> state or context

durable preference with reasons
recurring decision criterion
reusable planning / strategy / collaboration / asset-handling method
-> competence knowledge when it should change later non-identical work

This does not require creating a skill for every remembered detail.

Compatibility

• source version is 0.9.0;
• portable entry advances to 3.1.0;
• instance schema remains kernel_chat.instance.v1;
• existing Core, FDLA, state and effect-authority boundaries remain compatible;
• no central planner, supervisor, fixed competence taxonomy or background
  process is added;
• package/source publication does not automatically replace installed host
  instructions, configured adapters or user-owned instance state.

Evidence

Material semantic review target:
f66b9b13265a4bd7a3fb0d2d9c0b78eeaf986455.

• review CI 35593403680: success;
• validator: clean;
• tests: 65 per job;
• matrix: Python 3.11-3.14 × Ubuntu/Windows, 8/8 success.

The release-source-finalized identity must receive its own exact CI before a
protected immutable v0.9.0 publication effect.

Publication boundary

The repository source states durable product truth. Current publication status,
release id, Latest/immutable state and asset identity are resolved from GitHub
tag/Release readback rather than encoded as a self-invalidating candidate
sentence in the tagged source.