Skip to content
C.W.K.
Stream
Lesson 03 of 04 · published

Artifacts, Secrets, and What Never Auto-Reruns

~11 min · artifacts, secrets, intent

Level 0Cold Stick
0 XP0/41 lessons0/14 achievements
0/100 XP to next level100 XP to go0% complete

Bodies Live by Digest

A large body does not sit inside a JSONL line. It is written once as a content-addressed artifact and named from the line by digest. The same rule covers raw vendor wire and compaction summaries. Each session directory has its own artifacts/ tree. Identical bytes get the same digest name, but they do not share one file across sessions. Changing a body without changing its digest is not an option the engine offers.

Secrets stay out of the record. A token, a key-file path, or a password that leaked into a line is a defect, not a feature of 'complete provenance.' The record is meant to be readable by a later self and by a reviewer. A readable secret is a published secret.

Unresolved intent does not auto-rerun. A stop that left work unfinished is a fact. The next turn starts because an operator said so. A harness that 'helpfully' continues after a cap, a breaker, or a crash is inventing a turn nobody asked for.

Owned Versus Observed

Some facts Firebrand wrote: the request it assembled, the tool it ran, the result it stored. Some facts it only saw: a vendor reason string, a stream that ended early, a child process exit. The record marks that difference. Treating observed wire as owned policy is how a dialect bug becomes 'the model decided.' Treating owned policy as observed weather is how a cap looks like an accident.

Code

What a line may name, and what it may not contain·text
MAY name: sha256 of a body, tool name, stop reason, schema id
MUST NOT contain: tokens, key paths, passwords, refresh material
MUST NOT invent: a follow-up turn after cap / breaker / crash

External links

Exercise

List three things your current agent writes into history that you would not show a reviewer. Decide whether each is a secret, chrome, or a body that should have been a digest.
Hint
A path to a token file is a secret even when the token itself is not printed.

Progress

Progress is local-only — sign in to sync across devices.
Spotted a bug or have feedback on this page?Report an Issue

Comments 0

🔔 Reply notifications (sign in)
Sign inPlease sign in to comment.

No comments yet — be the first.