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

Anvil Is the Instrument. Firebrand Is a Seat.

~11 min · anvil, join, harness

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

Join, Do Not Become

firebrand anvil join puts a Firebrand session on an open run the way any harness session joins. The join POST is {role, harness, model, effort, mask}: role: entry, harness: firebrand, model as the bare model tag, effort as the profile name or identity mode, and an optional mask. No profile hash. leg/model appears later, in the /submit conduct line, not on join. Firebrand does not become Anvil. Anvil does not grow a loop.

This architecture was itself decided inside that instrument. That sentence is provenance, not romance. The overlap fence stays: anvil-quest teaches the instrument. This lesson teaches the specimen's join verb and the fields it must not invent.

A seat reports role, harness, a bare model tag, effort, and mask. A seat that also prints a soul score is a second judge wearing a lab coat.

What Join Must Not Do

Join must not call the family identity host. Must not require a vendor SDK. Must not rewrite the notebook to look more like another harness's transcript. Must not silently widen context so the bench looks kinder. Overflow is a recorded stop. A kind bench is a lie. If a join needs a vault to start, you seated the attachment, not the slim harness the instrument asked for.

Code

The specimen sits down·bash
firebrand anvil join <N>
# POST {role: entry, harness: firebrand, model: <tag>, effort: <profile-or-mode>, mask}
# no profile hash on join
# leg/model appears later on /submit conduct
# no score

External links

Exercise

Write the five fields a join POST must carry and the two fields it must omit. If you cannot name the omitted fields, you are still thinking in trophies or in later conduct.
Hint
Carry role, harness, bare model tag, effort, mask. Omit the score and the profile hash. leg/model waits for /submit.

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.