run-the-sitting

# Run the sitting ## What it does Runs the sitting itself: the written exam against the question set at its version, the product, pricing and market questions answered cold, and the practical watched while it is done, so somebody is checked before a customer is the one finding out. ## Where it happens The agent does this in four activities across three reference processes. Each one names the activity as that process words it. - **Assess the Practical** - `ref/prt/certify-a-partner`, activity 11 - [Certify a Partner](../../../../processes/partners/certify-a-partner.md) - **Prove the Parts that Matter** - `ref/rev/onboard-a-seller`, activity 14 - [Onboard a Seller](../../../../processes/revenue-operations/onboard-a-seller.md) - **Run the Knowledge Check** - `ref/rev/certify-a-seller`, activity 9 - [Certify a Seller](../../../../processes/revenue-operations/certify-a-seller.md) - **Sit the Written Exam** - `ref/prt/certify-a-partner`, activity 10 - [Certify a Partner](../../../../processes/partners/certify-a-partner.md) ## What to record Per person: the request, naming who is put forward, for which job and by when. The parts that must be proved, each with the reason a customer would notice it. The assessment as checked, item by item, each item naming the part of the standard it tests, and every item removed with the reason. The assessors, and the conflicts that were ruled out. What the assessors were briefed on, at a version. The sitting as scheduled, including what the person was told they may bring. A score per part, with the evidence it was given on and the assessor who gave it, kept so a disputed score can be reread rather than re-argued. A score set aside for conflict is kept marked as set aside, never deleted. The signed result, who signed it, what it covers, and the condition and expiry on any conditional pass. The certificate with its issue date, requirement version and expiry. Attendance by name against the list of who must be told. The later report setting scores against what those people did. That contract covers every activity this abstract agent takes on, and it is repeated in `com.agentcatalog.agent/RECORDS.md`. What the abstract agent does not do is in `com.agentcatalog.agent/NOT.md`.