Output: Artifact Design from Assessment Input
Criterion. Continue to structure participant responses into meaningful outputs. Evidence required. Documentation describing artifact structure and the generation process; sample artifacts produced from assessment inputs.
What the artifact is
A learner answers 45 prompts across the nine module assignments. The artifact turns those answers into one business playbook they can keep and send: a single designed document, with the programme's structure as its spine, that opens in any browser and prints to PDF.
Try it: https://edifysystemsgroup.com/playbook — enter an answer, then use Download your playbook document or Print or save as PDF.
Sample: a completed playbook for an invented venture
Structure
| Part | What it carries |
|---|---|
| Cover | the programme, the date, and how much is answered, counted in prompts |
| Module section | the module number and name, then the assignment's framing paragraph |
| Prompt | the question as a heading, then the learner's answer |
| Table prompt | the learner's grid, with its row and column labels intact |
| Unanswered prompt | marked as unanswered rather than silently dropped |
Coaching copy is suppressed. The worksheet's hints are written to the learner; a document sent to a funder is not addressed to them.
Generation
Entirely in the learner's browser, from answers already held in their own local storage. Nothing is uploaded, nothing is stored, and the document makes no network request either while it is generated or when it is later opened. That is not a claim: the browser probe opens the downloaded file from file:// in a context that has never visited the site and asserts it attempts no request at all.
The composer is lib/playbook/artifact.ts. It walks the nine assignments in order and renders each prompt through the same escaping used by the Andamio paste path, so there is exactly one place in the codebase where a learner's text is escaped.
Styles are inline and there is no external asset, which is what makes the file self-contained. Print rules set page size and margins, break between modules, keep a prompt or a table row from splitting across a page, and repeat a table's header on each page. The layout reads with background graphics off, which is the browser default when printing.
The sample
Built from a saved playbook in the Builder's own backup format:
- Answers:
sample-playbook-backup.json - Document:
sample-playbook.html
The venture is invented. Publishing a real learner's playbook would contradict the promise the whole design exists to keep, that their answers never leave their browser.
Module 800 is deliberately left unanswered, so the sample shows an honest mid-programme playbook and the unanswered marker doing its job.
To regenerate it, restore the backup file in the Builder and use Download your playbook document. The answers file is the source; the document is derived from it, so a design change is a re-export rather than a rewrite.