From commission to accepted result
On this page 8 sections
A working method distilled from Capsule's runs. This is local operating guidance; the registered report protocol and central acceptance records retain their own authority.
1. State the work in your own words
Commission and Charter use the same submission format. Choose an objective, supply the actual source material, describe the expected deliverables, and say how you will judge the result. A link or session reference is not evidence that source bytes reached a worker.
2. Make the team and scope explicit
The current operator default is Sol 6.1 medium, with no Astra. Set the worker count deliberately. Give each researcher a bounded contribution and require the lead to reconcile disagreements and integrate the work. Preserve useful prior context when continuing a study. Do not expand into unrelated commissions.
3. Review before sending
Saving and queueing are local operations. Only an explicit Send starts API work. Review the exact text and team configuration. The drafting helper helps shape the text; asking it a question does not dispatch a research team.
4. Track exact identities and changes
A capsule is a persistent session; an execution is a particular turn. Keep both identities with requests, artifacts and reports. Follow source events and recover saved records on reconnect. A worker's availability is not evidence that it is working. Show only tasks and progress supported by visible source records; missing assignments remain unknown. Sine owns the finer event-capture work currently in progress.
5. Recover without duplicate submissions
Every outbound request has a durable receipt. If the submission outcome is ambiguous, reconcile that receipt and exact session before taking further action. Never automatically replay an ambiguous request or silently create a replacement.
6. Bring the result home
Pull artifacts from the exact completed turn. Preserve source history, record SHA-256 hashes and provenance, and reject path escapes or unverified overwrites. Produce a readable synthesis, conclusion, evidence status and remaining gaps. Use the registered Capsule run report standard for the PDF.
7. Verify, integrate, then accept
Cloud completion, delivery, independent verification, integration and acceptance are separate states. Test consequential claims against the actual source and environment. Carry useful implementation through integration and evidence. Only the central acceptance record establishes acceptance; a polished report does not.
8. Account for cost honestly
Use per-agent invocation usage once, reconcile it against provider totals, and retain exact model evidence. Show capsule totals and individual execution costs. Unknown usage stays unknown. Conditional token estimates are distinct from billed charges.