TEA PlatformTEA Docs
Platform Guide

Templates and argument patterns

Distinguish case creation, import and export templates from planned reusable argument patterns.

Edit on GitHub

The platform uses the word template in more than one place. A document export template controls the structure of a generated report. A case data file can carry metadata that says an element came from a pattern. The data model also reserves an argument-pattern type for Discover. These pieces do not yet amount to a browser workflow for choosing and publishing reusable argument patterns.

Start a case

On a populated dashboard, choose Create new case to open Create New Assurance Case. The empty dashboard uses New Case. Enter Name and Description, then choose Submit. The modal creates a blank case and opens /case/<id>. The current modal has no template picker. If you have an existing case JSON file, Import File is a separate route to make a case from that data. It is not a choice inside the create dialog.

There is an /api/templates route that looks for JSON files in a caseTemplates directory and returns newTemplates and defaultCase. That directory is absent at the checked commit. The route therefore returns an empty list and no default case. Do not write a training step that asks a learner to choose a starter template from the current browser dialog. The repository does include a sample pattern JSON file under public/data/patterns/, but it is not wired into that dialog.

Export templates

The case share and export dialog offers document export presets. The presets include a full report, summary and evidence list. They control which sections and rendering layout appear in an exported document; they do not add claims or evidence to a working case. Choose the preset that suits the intended reader, then review the resulting file. An evidence list is a way to present what the case already contains, not a judgement about evidence quality.

Pattern metadata and current boundary

Assurance elements have fromPattern and modifiedFromPattern flags in the data model. Import and export preserve these fields. A future reusable pattern can therefore mark where material came from and whether a user changed it. The PublishableItemType enum includes ARGUMENT_PATTERN, and Discover has a generic type badge. The schema states that only ASSURANCE_CASE is implemented for 1.0. Current case publishing creates assurance-case items, not pattern catalogue entries. There is no user-facing pattern application flow in the checked code.

Limits and code location

Use the blank case creator or JSON import for today's case setup. Use document presets only for output. components/modals/case-create-modal.tsx contains the creation form; app/api/templates/route.ts contains the unpopulated template endpoint; components/modals/_share-modal/document-export-section.tsx contains export presets. Pattern metadata is defined in prisma/schema.prisma and carried by lib/services/case-import-service.ts and lib/services/case-export-service.ts.

MIT 2026 © Alan Turing InstituteTrustworthy and Ethical Assurance Platform