Skip to content
Signet Docs

Harnesses

AI platform integrations and harness configuration.

How Harness Sync Works

Section titled “How Harness Sync Works”

When you change $SIGNET_WORKSPACE/AGENTS.md:

  1. The Daemon file watcher detects the change (within 2 seconds)
  2. The daemon reads the new content
  3. It prepends an auto-generated header identifying the source
  4. It writes the result to each configured harness location

The header looks like this:

CLAUDE.md
# ============================================================================
# AUTO-GENERATED from $SIGNET_WORKSPACE/AGENTS.md by Signet
# Generated: 2025-02-17T18:00:00.000Z
# DO NOT EDIT THIS FILE - changes will be overwritten
# Edit the source file instead: $SIGNET_WORKSPACE/AGENTS.md
# Related documents:
#   - $SIGNET_WORKSPACE/SOUL.md (Personality & tone)
#   - $SIGNET_WORKSPACE/MEMORY.md (Working memory context)
#   - $SIGNET_WORKSPACE/agent.yaml (Configuration & settings)
# Memory commands: /remember <content> | /recall <query>
# ============================================================================

You can also trigger a manual re-sync:

Terminal window
curl -X POST http://localhost:3850/api/harnesses/regenerate

Lossless Working Memory Fidelity (Closure Wave)

Section titled “Lossless Working Memory Fidelity (Closure Wave)”

This matrix is the source of truth for closure-wave fidelity and degraded mode expectations across harness paths.

Harness path Prompt retrieval order Thread-head continuity Compaction artifact persistence Forced post-event MEMORY refresh
TS daemon (primary) entity current-view injection; transcripts via explicit session_search yes yes yes (session-summary + compaction-complete)

Degraded mode rules:

  • When a harness/runtime path cannot emit every lifecycle event, Signet must document the missing surface explicitly instead of implying full parity.
  • Compaction/session-summary forced-refresh guarantees are full in the TS daemon.
  • Watcher-driven harness identity sync (batched AGENTS.md / USER.md / MEMORY.md propagation, queued reruns during active sync, and generated SIGNET-ARCHITECTURE.md refresh) is full in the TS daemon.
  • Prompt-time anti-bleed scoping remains mandatory across all paths.

In this section

Section titled “In this section”