History and the saved decision
History
Section titled “History”node dist/cli.js history --data-dir .boardroom/examplenode dist/cli.js history --json --data-dir .boardroom/exampleHistory lists saved playback events and export operations from one consistent read. Events carry a global sequence and timestamp, and reference the saved meeting, message and position, or the export operation. They never include source or transcript bodies. Reading history never retries an export.
The saved decision
Section titled “The saved decision”node dist/cli.js decision --data-dir .boardroom/examplenode dist/cli.js decision --json --data-dir .boardroom/exampleThe decision view shows the saved context, both proposal versions and each adviser’s view of the version it judged. Two approvals keep the remaining INSUFFICIENT_EVIDENCE, and the human decision stays pending.
Field-by-field contracts for both commands are in the JSON output reference.
For a live project, history --project PROJECT_ID shows its events and export receipts; meeting-decision --project PROJECT_ID --id MEETING_ID inspects the current live decision and its versioned history. Live decisions and exports document the distinct contracts and pending real-account qualification.
Was this page helpful? Tell us on GitHub