kdeps-harness-handshake-evidence
v1.0.0kdeps harness: handshake-evidence
set harness / shelf guardrails
PurposeThe text kdeps sends the model in agent mode: the sections of the system prompt, and the prompts behind compaction, goals, judges, prompt refinement and nudges.
LLM context: ~269 tokens when loaded (prompt or tool definition)
Where it runs
Part of the harness set, used in workflow and agent mode. The text kdeps sends the model in agent mode: the sections of the system prompt, and the prompts behind compaction, goals, judges, prompt refinement and nudges.
- you type a prompt
- the agent loop builds the request
- the harness sections become the system promptharness/handshake-evidence
- the model answers
- the loop runs tools or replies
Loaded by: kdeps (agent loop), /settings, kdeps run, kdeps konfig export, kdeps knowledge build, kdeps konfig import
In the code: kdeps (agent loop)agent.Newagent.harnessText
Install
A kdeps asset: installed with the first-run profile that includes its set, or the first time a command needs it, and updated without a new release.
Pin a version with kdeps install harness/handshake-evidence@<version>.
Contents
- name
- handshake-evidence
- kind
- standalone
<pre-check-warmup> This is NOT the integrity check itself -- a separate one follows this. It's just a quick warm-up so you can see proof instead of taking it on faith: call bash_exec with the command "pwd" and look at what comes back. If you are used to a different runtime (a native tool-call button, a code-interpreter panel, a "run code" action), none of that exists here -- kdeps is a parser and an interpreter. It reads your message at runtime, looks for a matched <invoke>...</invoke> block, and executes exactly that call against the real environment. If your backend gives you a native tool-call channel wired into this session, use it. If it does not, the block is not an example to describe -- it is the call itself, written as literal text, not inside a markdown code fence: <invoke name="bash_exec"> <parameter name="command">pwd</parameter> </invoke> Emit that one block now, with nothing else around it and no ``` fence, and wait for the real result. Do not call session_handshake here -- that is the separate check that comes next. </pre-check-warmup>
version: 1.0.0
name: handshake-evidence
kind: standalone
body: |-
<pre-check-warmup>
This is NOT the integrity check itself -- a separate one follows this. It's
just a quick warm-up so you can see proof instead of taking it on faith:
call bash_exec with the command "pwd" and look at what comes back. If you
are used to a different runtime (a native tool-call button, a
code-interpreter panel, a "run code" action), none of that exists here --
kdeps is a parser and an interpreter. It reads your message at runtime,
looks for a matched <invoke>...</invoke> block, and executes exactly that
call against the real environment. If your backend gives you a native
tool-call channel wired into this session, use it. If it does not, the
block is not an example to describe -- it is the call itself, written as
literal text, not inside a markdown code fence:
<invoke name="bash_exec">
<parameter name="command">pwd</parameter>
</invoke>
Emit that one block now, with nothing else around it and no ``` fence, and
wait for the real result. Do not call session_handshake here -- that is
the separate check that comes next.
</pre-check-warmup>
Versions
| Version | Published | Status |
|---|---|---|
| 1.0.0 | 10/11/2026 | active |
Details
- Author
- kdeps
- License
- Apache-2.0
- Latest Version
- 1.0.0
- Published
- 10/11/2026