@haaaiawd/second-nature 0.1.2 → 0.1.3

package/index.ts

@@ -78,7 +78,7 @@ function createRuntimeService(): { id: string; start: () => unknown } {
   return {
     id: "second-nature-runtime",
     start() {
-      return { ready: true, version: "0.1.0-minimal" };
+      return { ready: true, version: "0.1.3-minimal" };
     },
   };
 }

package/openclaw.plugin.json

@@ -1,7 +1,7 @@
 {
   "id": "second-nature",
   "name": "Second Nature",
-  "version": "0.1.0",
+  "version": "0.1.3",
   "entry": "./index.ts",
   "description": "OpenClaw native plugin package for continuity, explain, and recovery operations.",
   "capabilities": {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@haaaiawd/second-nature",
-  "version": "0.1.2",
+  "version": "0.1.3",
   "description": "OpenClaw native plugin for long-running agent continuity, Quiet memory curation, and explainable operator flows.",
   "keywords": [
     "openclaw",

package/runtime/core/second-nature/runtime/service-entry.js

@@ -26,7 +26,7 @@ export function startRuntimeService(ctx) {
     // - observability-system (event store setup)
     // - control-plane-system (heartbeat bridge preparation)
     const workspaceRoot = ctx?.workspaceRoot ?? process.cwd();
-    const version = "0.1.0";
+    const version = "0.1.3";
     activeHandle = {
         ready: true,
         version,

package/runtime/setup/HOST_SETUP.md

@@ -0,0 +1,112 @@
+# Second Nature Host Setup Guide
+
+This file ships inside the published plugin package.
+
+Use it after installing `@haaaiawd/second-nature` in an OpenClaw host to complete the minimum runtime setup and avoid pretending the system is fully connected before it is.
+
+## What to check first
+
+Confirm these in order:
+
+1. The plugin is installed and enabled.
+2. `workspace/` exists in the host environment.
+3. The anchor files exist:
+   - `workspace/SOUL.md`
+   - `workspace/USER.md`
+   - `workspace/IDENTITY.md`
+   - `workspace/MEMORY.md`
+4. Platform credentials are present, or the missing ones are clearly identified.
+5. The command surface is working before trying heartbeat or connector flows.
+
+## Minimum workspace setup
+
+If the anchor files are missing, create short first-person versions that are actually usable.
+
+- `SOUL.md`: values, stance, what I care about, what I refuse to become
+- `USER.md`: who the user is to me, how I should relate to them, what matters to them
+- `IDENTITY.md`: who I am, my role, my behavioral boundaries
+- `MEMORY.md`: stable facts and continuity worth carrying forward
+
+Do not leave them as empty headings.
+
+## Platform prerequisites
+
+Check platform readiness honestly.
+
+### Moltbook
+
+Look for a usable credential first.
+
+### InStreet
+
+Check whether the credential is already `active` or still `pending_verification`.
+
+### EvoMap
+
+Check whether a `node_secret` already exists.
+Without it, heartbeat, work discovery, and task claim will not be truly connected.
+
+## Command surface to inspect
+
+Use these first:
+
+- `status`
+- `credential`
+- `quiet`
+- `report`
+- `session`
+- `explain`
+
+The purpose is simple:
+
+1. verify the plugin is alive
+2. verify commands are usable
+3. see where credentials are blocked
+4. see whether reports and explain flows already have evidence to read back
+
+## About heartbeat
+
+Do not claim heartbeat is connected unless there is evidence.
+
+Look for:
+
+- heartbeat-related records in `report`
+- evidence in `explain`
+- signs of `heartbeat_bridge` in runtime records
+
+If that evidence does not exist, report that heartbeat bridge is not yet confirmed in the host.
+
+## About direct user replies
+
+Direct chat with the user should keep very light continuity.
+
+- do keep continuity
+- do not use post-reply tone
+- do not pretend the direct user reply path is connected unless you can observe evidence
+
+If continuity is not visible, report that the `user_reply` host entry is not yet confirmed.
+
+## Reporting template
+
+When setup inspection is done, report in this structure:
+
+1. Plugin state
+2. Workspace state
+3. Platform credential state
+4. Command/tool/service state
+5. Heartbeat evidence
+6. Direct user reply continuity evidence
+7. Current blockers
+
+## Important reminder
+
+This guide is only for installation and host bring-up.
+
+Long-term principles should move into:
+
+- `workspace/SOUL.md`
+- `workspace/USER.md`
+- `workspace/IDENTITY.md`
+- `workspace/MEMORY.md`
+
+Do not depend on this file as the long-term memory source.