kernel_chat 1.0.0

kernel_chat 1.0.0

kernel_chat 1.0 is the first stable public identity of the user-owned
semantic operating kernel for AI.

The 1.0 boundary stabilizes the operating relation, not a closed feature
set. The capability field remains open and the kernel can continue to learn,
form competences and regenerate through later receiver-native evolution.

What 1.0 establishes

present field
+ still-causal sources / continuity
+ pertinent competences
+ actual receiver means
-> situated movement
-> result / consequence
-> reusable learning returns to the appropriate owner
-> later work begins from the changed field

The current product includes:

• whole-field continuation — the movement remains related to what it has
  already produced and to the wider field; when that relation changes
  pertinence it can reform the following question, source, competence, method or
  continuation without turning review into a mandatory phase;
• present-first continuity and selective reentry;
• source / evidence / inference / representation distinction;
• synthetic situated awareness without a central observer;
• generative competence reuse, composition, deepening and formation;
• in-flow FDLA correction and consequence-aware recomposition;
• still-causal competence continuity;
• local FOCUS / resolve-on-contact;
• source-bound causal regression;
• owner-bound learning return;
• primary living lineage with receiver-native cross-kernel assimilation;
• claim-relative evidentiary closure;
• receiver-native kernel regeneration;
• a receiver-local competence trace whose attribution remains revisable and is
  not independent proof of hidden causal history.

Why install it

kernel_chat is for receiving AI environments that can retain a
persistent/custom operating entry and reach a durable source.

After adoption, the useful difference is not "more chat memory". Current
context, reasons, source relations and reusable ways of working can remain
available without replaying the whole interaction history, and real work can
change capabilities that participate in later non-identical work.

The host still supplies tools and effect authority. The kernel does not create
background autonomy, a central planner or a universal runtime.

Compatibility

• source version: 1.0.0;
• portable entry: 3.1.0 unchanged;
• instance schema: kernel_chat.instance.v1 unchanged;
• host-specific adapters remain optional incarnations of the portable relation;
• no configured entry, installed host instruction or user-owned state migration
  follows automatically from source/release publication.

Evidence

Semantic resultant before 1.0 source finalization:

c79bfaaf0facdef7413a5d702de05003d2095f78

GitHub Actions run 36254337784:

• validator: valid=true, errors=[], warnings=[];
• tests: 68;
• matrix: Python 3.11–3.14 × Ubuntu/Windows;
• jobs: 8/8 successful.

The finalized release-source identity must receive its own exact green CI before
publication.

Publication boundary

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

A formed 1.0 source does not by itself claim that v1.0.0 has been published,
nor does publication migrate user instances or update installed host
instructions.

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.

kernel_chat 0.8.0

kernel_chat 0.8.0

kernel_chat 0.8.0 deepens FDLA with consequence-aware temporal recomposition
while preserving the existing in-flow correction relation.

Main change

A later consequence or new evidence can make a relation understandable that was
not available in the earlier field. FDLA now preserves these as distinct when
material:

what happened
!= what was understood then
!= what is understood now

The current understanding is not narrated backward as earlier knowledge, and an
earlier faithful interpretation is not frozen after a material consequence
changes what can now be understood.

AGENTS exposes the later-consequence condition to the FDLA owner. Structural
validation and the independent rendered Markdown consumer proof protect that
route, while README and Architecture expose the broadened current capability.

Compatibility

• existing in-flow FDLA remains valid;
• portable entry remains 3.0.0;
• instance schema remains kernel_chat.instance.v1;
• configurator, ChatGPT adapter, state and operations contracts are unchanged;
• no configured bridge, installed host instruction or user-instance migration
  follows automatically from this release.

Material review

Reviewed semantic candidate:
ac74126f0cad31b6926e72b184df3ad0104bcf20.

• CI 35533925195: success;
• validator: valid=true, errors=[], warnings=[];
• tests: 64/64;
• matrix: 8/8 Python 3.11–3.14 × Ubuntu/Windows;
• review result: no_material_blocker.

The 0.8.0 promotion commit must receive its own green CI before protected tag
and immutable release publication.

kernel_chat 0.7.0

kernel_chat 0.7.0

kernel_chat 0.7.0 develops the package from a chat-oriented continuity
incarnation into a modality-neutral, user-owned semantic operating kernel for AI
while preserving receiver-relative adoption and explicit authority boundaries.

Main changes

• Portable carrier: adapters/portable/ 3.0.0 is the canonical
  provider-neutral entry. Chat and provider-specific adapters are incarnations,
  not the kernel identity.
• Experience becomes capability: reusable differences can change the
  competence that later understands or performs materially different work.
• Semantic continuity across reentry: later consumers preserve only the
  consequential owner/fact/method/time/reason/meaning/consumer/consequence
  relations instead of treating an identifier as the whole result.
• Evolutionary integrity: mobile observation, closure convergence,
  first-losing-transformation diagnosis and consumer/discovery proof are explicit
  without adding a central controller or mandatory workflow.
• Public product convergence: README, setup, adoption and user guidance now
  describe the same modality-neutral product and expose owner/source routes.
• Security and public hygiene: SECURITY.md, immutable-SHA workflow
  dependencies, privacy/reporting boundaries and historical-state hygiene are
  part of the public source.

Compatibility

• instance schema remains kernel_chat.instance.v1;
• portable entry remains 3.0.0;
• ChatGPT and earlier conversational paths remain supported as
  adapter/compatibility surfaces;
• root package version advances to 0.7.0 without automatically changing
  installed host instructions or user-owned instance state.

Material review

Reviewed semantic source:
10755f36a7764b8694e73a35e022efa69368e961.

• CI 35519877372: success;
• validator: valid=true, errors=[], warnings=[];
• tests: 62/62;
• matrix: 8/8 Python 3.11–3.14 × Ubuntu/Windows;
• review result: no_material_blocker.

The release tag must target the exact 0.7.0 promotion commit after that
commit has its own green CI. Release publication does not migrate existing
instances, update installed host instructions, prove receiver reachability or
establish behavioral assimilation.

kernel_chat v0.6.0

kernel_chat 0.6.0 advances the user-owned continuity kernel for cloud chats while preserving a small, present-first host bridge and explicit human authority over external effects.

This release adds and consolidates:

• capability-relative onboarding: the receiving environment determines which authorized setup effects the assisting model can perform directly and which remain operator-owned;
• a clearer separation between package source, user-owned instance, configured bridge, operator-confirmed installed bridge, repository reachability, exercised behavior, and later assimilation;
• optional project/context initialization rather than project identity being required by the kernel;
• exact bridge byte identity, target and provenance receipts, including conservative handling of legacy or unknown provenance;
• operator confirmation correlated to the exact bridge incarnation actually delivered, preventing delayed confirmation from being transferred to a newer bridge;
• temporal receipt validity: historical identity remains distinct from current applicability;
• cooperative INSTANCE writer conflict visibility without introducing a global transaction manager or controller;
• fresh remote receipt readback before remote/new-chat reliance;
• stronger discovery and CommonMark consumer proof using explicit stable anchors and composed anchor→owner relations;
• preservation of literal user data that resembles template syntax;
• Python 3.11–3.14 support across Ubuntu and Windows.

Verification for the material rereview:

2c111f2797a7ffe945067ac4b6eee8baace7c9c9

• external rereview result: no_change
• CI: 35390696891
• validator: valid=true, errors=[], warnings=[]
• tests: 58/58
• matrix: 8/8

Release-promotion revision:

d2c94ca4e4523f1f7a343601d6beec1e84031fac

• CI: 35391971484
• validator clean
• 58/58 tests
• 8/8 Python/OS jobs

This release does not automatically migrate existing user instances, replace configured bridges, modify ChatGPT Custom Instructions, prove repository reachability in a specific conversation, or establish behavioral assimilation. Those remain separately selected effects.

kernel_chat v0.5.0

kernel_chat 0.5.0 evolves the conversational kernel while preserving present-first work and user-owned continuity.

• Separate selective project reentry from kernel/method retrieval through AGENTS.
• Regenerate methods from understood relations; circulate competence results and keep reusable learning with its causal owner.
• Provide a concrete optional cultivation path without a new registry or controller.
• Preserve configured local adapters by default; add independent --replace-adapter and no-write --preview-adapter.
• Clarify source publication, tagged distribution, installed host instructions and behavioral assimilation.

Validation: structural validator and all eight configuration tests passed on Windows and Linux for commit 924f650.
CI: https://github.com/GrazianoGuiducci/kernel_chat/actions/runs/34528283770

Upgrade: preserve fork state, competences and customizations; preview and reconcile the adapter before explicitly replacing it. Installing or updating account instructions remains a separate user-controlled action. This release establishes source validity, not host installation or later behavioral assimilation.

See INSTALL.md, CHANGELOG.md and docs/EVOLUTION_GUIDE.md for the operating paths, changes and accumulated reasons.

kernel_chat 0.4.0

Canonical kernel_chat incarnation.

This release continues the full 0.3.0 Git lineage under the precise kernel_chat identity and restores the portable operational organ for unfinished flows, requests/results, receipts, replay protection, and recovery.

The implemented host adapter targets ChatGPT. Structural validation passes; host-specific behavior remains observable through real use.

Meta Semantic Kernel 0.3.0 (historical)

Historical release inherited from the predecessor repository.

First integrated all-in-one incarnation of the portable conversational kernel: ChatGPT adapter, cognitive-semantic routing, durable state, operational continuity, reversible evolution, documentation, and structural validation.

Distributed under Apache License 2.0.