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

The Decision Record

~11 min · decision-record, audit, refusals, closing

Level 0Kindling
0 XP0/32 lessons0/10 achievements
0/100 XP to next level100 XP to go0% complete

The archive remembers saying no

The last surface of the pipeline is not a UI screen but the record it keeps behind all of them: every work order's outcome — approved, declined, or deferred — preserved with its reasons, alongside the artifacts that landed. A declined candidate is not deleted from history; it remains as a decision, with the research that led to the refusal. Even the paths not taken have entries.

This is the walk-away log from the sourcing track, promoted to a first-class citizen and bound to the acquisition flow. The rationale is the one this quest has kept returning to: the pile is defined as much by what it declined as by what it holds. A library that forgets its refusals will re-litigate them — six months later, under a new name, with nobody remembering why the last encounter felt wrong. The immune memory has to live somewhere, and somewhere turns out to be: with the acquisitions, in the same system, equally durable.

What the record earns

Three properties emerge from keeping decisions, not just artifacts. Auditability: any holding can be traced to the conversation that admitted it — what was known, what was checked, who decided. Learning: patterns in refusals (this mirror family, that mislabeled-dtype shape) accumulate into the archive's own review instincts; the record is where the review desk's experience lives. Integrity of intent: when a future question arises — why do we hold this under restrictive terms? why is this variant absent? — the answer is a lookup, not an archaeological dig through someone's memory.

And notice the symmetry with the human gate from lesson one: a decision made before the bytes needs a place to live after them. The Composer's conversations and the decision record are the same institution at two moments — the record is the gate, persisted.

Decisions are artifacts too. The approval, the refusal, and the reason outlive the session that produced them — and the archive that records its choices can be inherited, audited, and trusted by someone who wasn't there.

Closing the quest

Here is where all six tracks meet. The link is a loan, so you own the bytes. Ownership is four conditions, so you verify digests and read licenses. The deadline is three clocks, so you pin revisions. The payoff is vessels, so you keep the highest fidelity. The discipline is the woodpile rules, so you record refusals. And the whole argument, running in production, is this pipeline: a gate that argues, a monitor that moves, a library that shows, settings that govern, and a record that remembers. The wood is stacked; the winter can come when it wants.

Code

One decision, recorded end to end·text
# A single decision entry, as the pipeline sees it:
#   work-order:  #18
#   sources:     [ <org>/<model> (BF16), <org>/<model>-fp8 ]
#   research:   fp8 repo fails arithmetic (6 GB at 'BF16' label);
#               BF16 original consistent (17.8 GB expected/found);
#               chain L1 org-authored / L2 pinned / L3 oid corroborated
#   proposal:   acquire BF16 original; decline fp8 re-release
#   decision:   APPROVED (original) + DECLINED (fp8) -- Dad, 2026-09-14
#   reason:     master slot demands proof of identity; fp8 wears
#               the label without the bytes
#   outcome:    landed as archive/<org>/<model>/bf16-260914/, verified
#
# Six months later, the fp8 repo renames itself 'bf16-refresh' and
# resubmits. The record is why the answer is still no -- one lookup,
# zero re-litigation. That is the decision record earning its keep.

External links

Exercise

Write the decision entry for your most recent real acquisition (or refusal) in the six-line form: sources, research, proposal, decision with date, reason, outcome. Then stress-test it: imagine the declined candidate resubmitting under a new name in six months — does your entry end the re-litigation in one lookup? If not, add the missing field now.
Hint
The reason line is the one that future-proofs the entry. 'Didn't feel right' re-litigates; 'sizes contradicted the dtype label by 3x' never does.

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.