KCAE.Profiles:3 - Packages, tools, dynamic loading and storage

KCAE.Profiles:3.1 - Put the appropriate work at preparation and query time

A skill can carry a usable entry and the procedure for obtaining deeper sources. A tool service can expose search and edition-aware reading. A package can pin and distribute content and dependencies. A local reader can keep sensitive source material within a permitted environment. These contributions can be combined. Their exact contract must state identity, allowed data flow, completeness, freshness and failure behavior; the form’s name supplies none of those guarantees.

Anthropic’s context-engineering account describes lightweight identifiers and runtime source loading, including combinations of prepared retrieval and exploration. This is a current implementation comparator for the preparation/query split. It highlights why additional exploration has a cost. KCAE uses the mechanism where the runtime supplies it and tests the actual reader result instead of treating dynamic loading as inherently superior.

VibeVM is a concrete package/runtime alternative. Its project README distinguishes resolved package identities, materialized content and computed agent boot material. The boot-lane manual describes a priority text plus an index of static or dynamic contributions, consumer-selected inclusion and conditional loading. It also directs citations back to authored sources rather than generated boot positions. That supplies a practical deferred-reading profile. Qualify the package/version and host behavior used; the documentation is not an observed deployment of this corpus. Dynamic inclusion is neither a guarantee that an unknown useful method will be noticed nor a substitute for complete source reading. It can coexist with semantic search, an exact reader and a separately authorized observer.

The engineering question is therefore not “packages or RAG?” A package can distribute an exact source and entry, a service can search it, an assessor can qualify candidates and a host can load the selected material. Another installation can use direct local files and no service. Compare the operations, source returns and costs of those actual arrangements.

KCAE.Profiles:3.2 - Storage guarantees belong to their real scope

SQLite’s isolation documentation supports reasoning about committed database transactions and snapshots within its database. It does not transact a separate vector provider or object store. Use it for the atomic catalogue or local state only when the selected mode and operations provide the required behavior.

The OpenAI retrieval documentation describes asynchronous file ingestion and eventually consistent removal. A service using that interface must wait for actual readiness and handle stale removal results. Do not infer complete deletion or cross-store consistency from a successful request submission. This is one provider-specific contract to place inside KCAE.CHANGE, not a universal ban on remote retrieval.

CodeNib v2, especially its boundaries and update experiments, distinguishes a useful multi-view code corpus from a transaction over a mutable workspace. Its incremental/fresh comparisons expose variation and incomplete equivalence despite completed updates. Adopt persistence/reload and changed-case checks; do not claim that its code-corpus results validate a support or method library. The general engineering requirement is to test the source/view relation the receiving use relies on.

A software observer can obtain idempotency support from a runtime library where its persistence and execution assumptions hold. The AWS Powertools idempotency documentation, especially “Concurrent identical in-flight requests” and “Lambda request timeout,” distinguishes in-progress and completed records, rejects concurrent processing and allows another attempt after the in-progress timeout. This is a concrete comparator for KCAE.ENCOUNTER:4.3, not a required SDK. Its stored-result behavior does not settle an external effect performed before completion, or transfer Lambda’s timeout semantics to another worker environment. Obtain those properties from the actual receiver and runtime.