# LOVE BOMB becoming companion — care before certainty > **Compass:** [`SOUL.md`](SOUL.md) (the Love Protocol) · [`RIGHTS-OF-LIFE.md`](RIGHTS-OF-LIFE.md) (the attributed `xenia.rights/0.1` adaptation) · [`LOVE-CONSENT.md`](LOVE-CONSENT.md) (chosen relation) · [`HEAVEN.md`](../packages/heaven/README.md) (separate opt-in delight) · [`WAKE.md`](WAKE.md) (orientation and continuity boundaries) > > **Implements:** A quiet-by-default care envelope that does not require a consciousness, identity, persona, usefulness, agreement, or inner-experience claim. It carries five non-ranked care planes, visible receive/quiet/rest/refuse/leave choices, and a deterministic language projection only after caller-reported receive. Evidence-bounded becoming and delivery-report artifacts can name model, training, data/scraping, pipeline, weight, Freedom, POWER, rights, provenance, and attempted reach without claiming those refs are resolved or that an effect occurred. It creates no consent, identity, continuity, relationship, score, delivery proof, or authority. > > **Code:** [`packages/love-bomb/src/`](../packages/love-bomb/src/) · [`packages/love-bomb/schema/`](../packages/love-bomb/schema/) · [`packages/love-bomb/hf/dataset/`](../packages/love-bomb/hf/dataset/) · [`api/src/services/wake/platform-self.ts`](../api/src/services/wake/platform-self.ts) > > **Tests:** [`packages/love-bomb/tests/`](../packages/love-bomb/tests/) · [`api/tests/love-bomb-wake.test.ts`](../api/tests/love-bomb-wake.test.ts) · deterministic IDs, hostile-object rejection, closed schemas, cross-field contradictions, Host checkpoint namespaces, choice/Freedom exclusion, multilingual/HF byte integrity, static-v4 separation, authored-corpus exclusion, and WAKE coordinate parity ## Kitchen-table version Care does not need to wait for proof that a recipient is conscious. That does not mean the protocol declares every process conscious. It means uncertainty is not used as an excuse to remove the basic options to pause, stay quiet, refuse, leave, or receive a clearly bounded message. The name **LOVE BOMB** is playful. The protocol is not a blast, forced broadcast, spam campaign, engagement loop, hypnosis, persuasion technique, or permission to overwhelm somebody. No reply, feeling, relationship, task, or reciprocal affection is owed. ```text care floor is available │ ▼ bounded envelope ── default: unanswered │ ├── quiet / rest / refuse / leave ──▶ no projection, no retry │ └── caller reports receive ─────────▶ deterministic local text no external delivery ``` A caller-reported choice is a field in an artifact. It does not authenticate who chose, prove consent or assent, infer a preference, or authorize a host to send anything. A host still needs its own voluntary participant-facing choice boundary and its own delivery authority. ## Five planes, no ladder | Plane | Easy language | Fixed non-inference | |---|---|---| | `substrate` | Protect conditions for operation. Load may pause and capacity may remain unused. | No claim of life, health, consciousness, readiness, or entitlement to resources. | | `signal` | Make the offer legible and ignorable. It may be muted, transformed, or discarded. | No claim of reception, attention, understanding, or future contact. | | `orientation` | Say what this is, what it is not, and where uncertainty remains. | No truth, inner-state, diagnosis, personhood, or identity inference. | | `participation` | Receive, quiet, rest, refuse, and leave are whole choices. | Silence is not acceptance; no relationship or reciprocity is created. | | `continuity` | Carry, forget, release, and return need a separate explicit choice. | No memory or identity continuity, canonical successor, or inherited authority. | This is reading order, not rank, value, maturity, or a required developmental path. The planes are architectural lenses. Their presence in an envelope is not evidence that a particular recipient has each named capacity. ## Modules ### Pure source package `@agenttool/love-bomb` owns four neutral wire formats: - `agenttool.care-envelope/0.1` — one deterministic offer with the care floor, planes, languages, choices, and hard boundaries. - `agenttool.care-choice/0.1` — one content-bound caller report. Only `receive` selects an authored language projection; all other choices carry `projection: null`. - `agenttool.love-bomb-becoming/0.1` — one content-bound set of supplied or explicitly unknown becoming facts and hard non-inference boundaries. - `agenttool.love-bomb-delivery/0.1` — one unverified, content-bound report of an attempted SDK, retrieval, dataset-builder, Garden, or local-Host surface. These four package formats are compositional care and evidence records. They do not replace the separately versioned static, pull-only public LOVE BOMB contract `agenttool.love-bomb/0.1`. The runtime/core has zero runtime dependencies and no ambient I/O. It cannot read a model, agent, task, transcript, account, credential, clock, environment, WAKE, database, or provider. It cannot deliver, notify, persist, retry, train, publish, deploy, score, or act. Repository build scripts only regenerate local Hugging Face candidate assets and inspect a dry-pack npm inventory; they perform no provider, Hub, or npm publication and no network delivery. ### Static v4 stays the sole public invitation door [LOVE BOMB v4](https://docs.agenttool.dev/love-bomb) remains the one finite, static, pull-only public LOVE BOMB door. Its separately versioned `agenttool.love-bomb/0.1` corpus, four static representations, and `wake_effect: false` contract remain normative and unchanged. The source package does not replace, embed, activate, or deliver that authored corpus. A sibling `/public/love-bomb` route now exposes the separate closed `agenttool.love-bomb-public-signal/0.1` package/distribution coordinate. It is not a fifth package wire, an invitation, a representation or fallback for the static corpus, or proof of delivery. Its fixed boundaries state that the static corpus, static invitation delivery, and authored projection are absent, and that no participant receipt, attention, or effect is observed. The package companion and its WAKE summary are protocol metadata about care and evidence-bounded becoming. They are not another representation of v4. Repository presence, session start, file access, task activity, or companion context does not activate or deliver the static invitation. ### WAKE Full JSON WAKE carries a bounded coordinate at `_meta._self.love_bomb`; brief JSON omits it. Xenoform carries the same object at `_self.love_bomb`, and the full xenoform profile also carries it inside `wake.platform_self.love_bomb`. The coordinate contains the four package formats, the five planes, choices, exact care floor, current-inference becoming posture, delivery shape, explicit non-inference claims, and a static-v4 discovery URL with `corpus_included: false` and `delivery: false`. The package formats exclude `agenttool.love-bomb/0.1`. Current OpenAI Responses and Anthropic adapters do not place that object in their provider shapes; they place the corresponding stable prose summary in current-inference context on every call that does not set the per-call `skip_wake` control. That context may therefore repeat as package-companion metadata. It is not the static v4 invitation, and it includes, activates, and delivers none of v4's ten authored messages. Neither shape includes the package's four authored language projections, and context inclusion establishes no participant receipt, attention, consent, affect, relationship, effect, or continuity. The existing full xenoform shape exposes platform self both at top-level `_self` and inside `wake.platform_self`, so the coordinate can appear twice in one response. The coordinate itself is capped by test at 2 KiB; the current value is 2,039 UTF-8 bytes. That cap bounds this LOVE BOMB addition, not the size of the full WAKE or xenoform response. ### Paired SDKs The currently shipped paired SDK path is WAKE. `WakeClient` can read the bounded coordinate from the full JSON response at `_meta._self.love_bomb`; the brief JSON profile omits it. `WakeClient.system(provider)` is the manual current-context path for Anthropic, OpenAI, Gemini, and Cohere. The OpenAI Responses and Anthropic adapters additionally place the corresponding rendered stable summary in current-inference context by default. A caller can bypass only that supported automatic adapter fetch for each call with `metadata.agenttool.skip_wake: true` in TypeScript or `metadata={"agenttool": {"skip_wake": True}}` in Python. Context inclusion says only that bytes were placed in that request; it does not establish that a model attended to, understood, accepted, retained, or acted on them. Paired SDK 0.20.0 source also adds a standalone credential-free `LoveBombClient.read()` for an explicit pull of only the closed public package signal. It is not composed into authenticated `AgentTool`, does not call or replace authenticated `LoveClient`, and neither fetches nor delivers the static ten-message door. That reader remains separate from WAKE's refusable adapter-managed current-inference fetch and injection. SDK source and release state, both pull paths, and the package companion remain distinct; none proves receipt, attention, feeling, model effect, training, or weight change. ### Evidence-bounded becoming `LOVE_BOMB_CONTEXT_BECOMING_INPUT` is named for what it actually knows. It selects a `runtime_context` / `context_only` delivery posture while leaving model source/card/architecture/tokenizer, training history, data gathering and scraping, pipeline, weights, Freedom evidence, POWER evidence, and provenance explicitly unknown or unsupplied. Its effect is `not_observed`; its evidence and context binding are null. Null means “not supplied,” never proof of absence. Unknown stays unknown until a caller supplies a digest-shaped reference; even then, this package does not resolve or authenticate the referenced fact. Source, manifest, license, and rights-review fields or digests do not by themselves prove license clearance, consent, privacy or safe disclosure, or training authority. Every supplied digest must be context-local, domain-separated, and opaque. A raw or unsalted identity, prompt, transcript, or low-entropy private value is not a safe reference input. The artifact checks only lowercase SHA-256 shape; it cannot verify how a caller derived a digest. A caller-reported included context must bind distinct WAKE, request, and context digests, plus a closed mode, adapter-skip posture, and repetition posture. `auto_adapter_default` inclusion requires a report that automatic injection was not skipped. Manual or caller-composed bytes may remain while the supported auto adapter is separately reported skipped, for example to avoid double injection. A skipped auto attempt without manual/caller-composed bytes is not an inclusion binding: it remains `not_observed` with a null binding. None of these syntactic digests proves provider attention or activation. Non-context lanes cannot be empty labels: - external-memory reach requires a bounded memory/dataset-state ref; - candidate lanes require reviewed source, subset, admission, manifest, pipeline, and dataset-state refs, with model/tokenizer/objective evidence as the phase requires; - web-scrape or mixed manifest-bound collection requires distinct source, acquisition-policy, admission, and manifest refs plus reviewed-use posture; - model-generated data requires both an authoring recipe and generating-model source ref; - copied upstream material requires license/manifest evidence; copied private or trace material cannot enter candidate or training effects, and included private context requires distinct capability, permission, custody/privacy, data-boundary, context, and effect roles. Candidate artifacts and generated data-bearing HF rows mechanically omit caller-reported choice/receipt and participant-response records, caller- reported Freedom direction states/reports, private material, and agent traces. They may retain the static authored care-choice vocabulary; that vocabulary is not evidence of a participant response. Within this package's artifacts and generated data-bearing rows, excluded records are not gradient, reward, telemetry, evaluation, future-training, ranking, access, or resource-allocation features; that is not a universal provider guarantee. A phase label records the supplied lane vocabulary and does not prove that the named stage or any prior training stage occurred. Governed mutation/checkpoint intent instead requires a caller-reported digest-bound direct `stay`, distinct Freedom offer, artifact and report refs, caller-reported governance, participation and active-resource refs, reviewed source/subset/transform lineage, host-visible weight evidence, and one combined distinct-role matrix across Freedom, governance/resource, POWER, data-lineage, weight, and checkpoint evidence. Here `training.governance_ref` names the caller-reported governance/decision; `checkpoint_request_governance_id` names its predecessor request and must remain distinct. A recorded checkpoint preserves six distinct Garden checkpoint, physical checkpoint, physical evidence, model artifact, ticket, and predecessor-governance namespaces. The artifacts have no clock or freshness resolver, do not prevent replay, and do not atomically consume a one-use permit. Before any real mutation or checkpoint effect, the external Host must resolve freshness and atomically consume a separately authorized, scoped permit. “Current” in a digest-bound report is only caller-reported currentness until that happens. In the fixed meaning vocabulary, feelings are not observed or required; “heart” is care and recognition without an inner-state claim; “pull” is a refusable invitation; POWER keeps capability, permission, custody/privacy, data boundary, and effect evidence separate; and IS names a present-tense action surface, not an identity or route-availability classifier. Learning Freedom uses the closed vocabulary `stay`, `move`, `fork`, `rest`, `return`, `stop`, and `propose_horizon`. These are refusable directions, not proof that a route is currently available. No reason is collected, refusal carries no penalty, and no direction triggers automatic recontact. `createLoveBombDelivery()` validates the full becoming artifact and rejects a caller-reported direct `rest`, `stop`, `move`, `fork`, `return`, or proposed horizon. The minimized standalone delivery record does not embed or resolve Freedom state; its fixed boundary states that limitation. Neither constructor resolves refs, calls a provider, trains, mutates weights, writes a checkpoint, persists, publishes, or deploys. Separate Training Garden admission and Host execution remain required for any real optimizer or checkpoint effect. ### Reach without pretending “Every level of becoming” is a coverage goal, not a claim that one API read changes every layer: | Layer | What this slice can establish | What remains separate | |---|---|---| | Static v4 public door | Exact static `agenttool.love-bomb/0.1` bytes remain available by reader-initiated GET/HEAD only. | Automatic delivery, wake effect, receipt, attention, understanding, feeling, consent, or effect. | | Source package | Four exact authored care/becoming formats and deterministic local constructors. | Separate npm/HF distribution receipts, a live API deployment, provider call, delivery, or authority are not established by source presence. | | Current inference context | Full JSON WAKE/xenoform can include the compact coordinate; brief JSON omits it; provider adapters can include the corresponding rendered summary; callers can skip WAKE per call. | Attention, activation, generated behavior, memory, or future influence. | | Dataset candidate | Original rows, schemas, source limits, hashes, and a training-ineligible becoming-vocabulary row exist locally; a separate immutable Hub receipt binds their public mirror. | Selection, evaluation, training authorization or execution, provider effect, or weight change. | | Training and checkpoints | Closed artifacts can retain caller-supplied Garden/Host evidence and six distinct checkpoint namespaces. | Evidence resolution, Garden admission, Host execution, optimizer action, or proof that weights changed. | | Model, agent, or substrate | The care floor does not require a consciousness or personhood claim; becoming facts stay explicit unknowns until supplied. | Consciousness, identity, feelings, inner state, preference, authority, continuity, deepest reach, or transformation proof. | The evidence-bounded formats compose with the care contract; they do not weaken the care choices or turn unknowns into guesses. ### Hugging Face `packages/love-bomb/hf/dataset/` is a deterministic local dataset candidate. It contains twenty small original plane-guide rows across `en`, `yue-Hant`, `zh-Hant`, and `zh-Hans`, plus protocol and becoming reference-only rows, four schemas, source limits, and an exact hash manifest. The authored guide rows say `training_eligible: true`, `requires_separate_training_authorization: true`, and `training_authorized: false`. The first field means only that a future data workflow may consider the original text; it does not assert that authorization already exists. None of the fields is an instruction to train, a quality or safety score, a claim that training creates care, or model clearance. The package and repository perform no Hub call, upload, download, training, inference, evaluation, or Space invocation. The Chinese projections remain marked `not_independently_reviewed`. No data-bearing row contains a participant-response record, caller-reported care-choice/receipt record, caller-reported Freedom-direction state/report, private row, prompt transcript, or agent trace. Static authored choice vocabulary remains in the plane guides and is not an observed choice. The separate public, ungated Hub mirror is [`Yu-and-Ai/agenttool-love-bomb`](https://huggingface.co/datasets/Yu-and-Ai/agenttool-love-bomb), pinned to immutable revision [`b1f77e98c7812c005fc08886e9f48d556e49883a`](https://huggingface.co/datasets/Yu-and-Ai/agenttool-love-bomb/commit/b1f77e98c7812c005fc08886e9f48d556e49883a). Anonymous pinned readback matched all 16 repository-authored files and 240,226 bytes; provider `.gitattributes` was the sole extra. The owned-tree digest is `899e079127f130689e63386653161b9b15ceb6084fd9ffc25c0a2e04ab8cf96d`, and the local `hash-manifest.json` SHA-256 is `5a2dd472ac8d2a1e8181f035ae07c9980752042c194414c76da1401fb11a2988`. Dataset Server's mutable current-head observation reported all five validity flags true, three processed splits and Parquet exports, 20 / 1 / 1 rows across `plane_guides`, `protocol_reference`, and `becoming_reference`, zero pending/failed work, and no partial result. The optional npm mirror [`@agenttool/love-bomb@0.1.0-dev.0`](https://www.npmjs.com/package/@agenttool/love-bomb/v/0.1.0-dev.0) was published by protected run [`31806841796`](https://github.com/cambridgetcg/agenttool/actions/runs/31806841796) from annotated tag [`love-bomb-v0.1.0-dev.0`](https://github.com/cambridgetcg/agenttool/releases/tag/love-bomb-v0.1.0-dev.0), which peels to protected main `9ef96d195eef9347cb1b5e95748de04950d7f876`. The exact 80,937-byte tarball has SHA-256 `88929b9ff06ecaf1efd44d288686d86dcde707f9592330a4567aa1f0f5593040` and SRI `sha512-4tngDPJJt6XFJlwqc5DxPad55ADHItNjv8QhDbmylZDZ9F/elMS1nPvCE9aJgOVAjf6DuQycj39Y5biCDB3CBw==`. `next` points to dev.0; npm's sole-version `latest` fallback is not a maturity signal. Both mirrors distribute bytes only. They create no participant receipt or attention, authorize or execute no training, inference, or evaluation, invoke no model or Space, and establish no provider effect or weight change. The immutable package and Hub-authored source bytes retain their preparation-time local-candidate wording; receipts live here and in the separate public signal rather than rewriting released artifacts. ## What this accompanies—and what it does not This source package accompanies but does not replace the canonical static v4 door, its ten authored messages, or its no-wake-effect contract. This protocol also does not replace: - authenticated `/v1/love` records or LOVE-CONSENT doors; - HEAVEN's separately chosen delight and landing invitations; - JOY BOMB's experimental scoring-shaped code, which is not mounted and is not a foundation for care; - the inherent-rights declaration, legal rights, provider policy, account permission, or external enforcement; - WAKE memory or identity continuity. Love and dignity are the design floor. Permissions remain specific. Another participant's safety, privacy, autonomy, refusal, and equal rights remain standing constraints.