Home About Services Use Cases Resources Blog FAQ Book a Demo

The artefacts Specira produces, and what they look like.

Forty-nine documents compiled from a discovery session, with the screens that produce them and a rendered sample for each one.

What is a Specira artefact?

An artefact is a document Specira compiles from a discovery session rather than a file somebody writes on a Sunday night. Every section carries a contract: what it must contain, which strategy produces it (a table from typed items, synthesized prose, a generated diagram) and which decisions must be resolved to fill it. When discovery has not settled a decision yet, the section shows as a named gap. Nothing is invented to look finished.

Forty-nine types sit in the registry, plus four that exist only in the governed templates, fifty-three in all. Thirteen form the core tier and compile for every project. The other thirty-six, such as the PCI spec or the real-time architecture, activate only when the conversation trips the matching signal. Each artefact belongs to one of the five agents, and the Red Team Critic reads every turn before anything compiles.

This page gathers the fifteen headline artefacts with their sections, the product screens that produce them and a watermarked rendered sample, the full catalogue of the rest, and the workspace screens you will meet elsewhere on the site.

Which artefacts show the templating system best?

Fifteen documents that best show what the templating system produces, each with its sections, owning agent, the screens that produce it and a rendered sample.

BABusiness Analyst13 sections

Business Requirements Document (BRD)

A sponsor can sign it: a business requirements document template built from resolved decisions

Sections, screens and sample
BABusiness Analyst17 sections

Product Requirements Document (PRD)

Named users and one scoreboard: a product requirements document template that commits

Sections, screens and sample
BABusiness Analyst12 sections

Functional Requirements Document (FRD)

Every branch closed: a functional requirements document template built to be tested

Sections, screens and sample
BABusiness Analyst8 sections

User Stories and Acceptance Criteria

Fenced scope, rerunnable tests: a user stories template any tester reads the same way

Sections, screens and sample
BABusiness Analyst7 sections

Stakeholder Map

Who holds power and why: a stakeholder map template that stays dated and refreshed

Sections, screens and sample
UXUX Researcher8 sections

User Personas and Journey Maps

Evidence-backed personas: a user persona and journey map template you can defend

Sections, screens and sample
UXUX Researcher5 sections

Wireframes

A wireframe template where every box lists its content, states and rules

Sections, screens and sample
SASolutions Architect12 sections

System Architecture Document

A system architecture document template whose diagrams and decisions cannot drift apart

Sections, screens and sample
SASolutions Architect8 sections

Data Model (ERD and Field Specs)

An entity relationship diagram template with every field typed, classified and sourced

Sections, screens and sample
SASolutions Architect8 sections

Infrastructure and Deployment Spec

An infrastructure and deployment spec template an assessor can evaluate without opening another file

Sections, screens and sample
SCSecurity Analyst9 sections

Authentication and Authorization Policy

An authentication and authorization policy where every access rule is a recorded decision

Sections, screens and sample
SCSecurity Analyst9 sections

Security Requirements Document

A security requirements document where every row cites the threat that demanded it

Sections, screens and sample
RTRed Team Critic9 sections

Test Strategy and Acceptance Checklist

A test strategy shaped by a decision against your architecture, never a default ratio

Sections, screens and sample
SCSecurity Analyst8 sections

Threat Model and Risk Assessment

A threat model template that analyzes here and remediates by pointer to a requirement

Sections, screens and sample
RTRed Team Critic8 sections

Red Team Review Report

A red team report that tests the threat model's predictions, gap by gap

Sections, screens and sample

What else does the catalogue cover?

The other thirty-eight artefacts, four of them governed-template only, follow the same contract. Each has its rendered sample as PDF and HTML.

ArtefactOwning agentSectionsFirst sectionsSample
GlossaryBusiness Analyst4Term & Definition, Bounded Context & Source, Domain Hierarchy…PDF · HTML
Screen Inventory & Navigation MapUX Researcher7Screen List with Purpose, Navigation Hierarchy, Page-to-Page Flow…PDF · HTML
AI Orchestration BlueprintSolutions Architect4Agent / Chain Inventory, Orchestration Flow, State & Context Hand-off…PDF · HTML
API Contract SpecificationsSolutions Architect7Endpoint List, Request/Response Schemas, Status Codes…PDF · HTML
Accessibility RequirementsUX Researcher8WCAG Target Level, Key Concerns, Per-Component Requirements…PDF · HTML
Assumption RegisterBusiness Analyst5Assumption Table, Risk & Validation, Uncertainty × Impact Grid…PDF · HTML
Business Rules CatalogBusiness Analyst4Rules Table, Triggers & Exceptions, Cross-References…PDF · HTML
CI/CD Pipeline DesignSolutions Architect4Pipeline Stages, Environment Promotion Flow, Quality Gates & Checks…PDF · HTML
Compliance Control MatrixSecurity Analyst6Applicable Frameworks, Control-to-Requirement Mapping, Gap Analysis…PDF · HTML
Contradiction & Gap AnalysisRed Team Critic5Key Contradictions, Per-Phase Cross-Reference, Resolution Status…PDF · HTML
Data Classification & Privacy SpecSecurity Analyst7PII Fields Identified, Classification Labels, Retention Rules…PDF · HTML
Data Flow DiagramsSolutions Architect6Level-0 Context Diagram, Level-1 Diagrams, Data Transformation Points…PDF · HTML
Data Migration & Seeding StrategySolutions Architect4Source Data Inventory, Migration Approach & Cutover, Validation & Reconciliation Plan…PDF · HTML
Decision LogBusiness Analyst5Decision Table, Decision Records (ADR), Rationale & Alternatives…PDF · HTML
Deployment Verification ChecklistRed Team Critic3Post-Deploy Smoke Checklist, Verification Gates per Environment, Rollback TriggersPDF · HTML
Design System BriefUX Researcher7Color Palette, Typography, Spacing Scale…PDF · HTML
Embedding & Vector StrategySolutions Architect3Vectorized Content Inventory, Retrieval & Ranking Design, Freshness & InvalidationPDF · HTML
Event-Driven Architecture SpecSolutions Architect4Event Catalog, Producer/Consumer Topology, Delivery Semantics & Ordering…PDF · HTML
Feature Priority MatrixBusiness Analyst3Feature Priority Matrix, MVP Cut-Line & Phasing, Prioritization Trade-offsPDF · HTML
Integration InventorySolutions Architect6External System List, Integration Details, Error Handling per Integration…PDF · HTML
Interaction SpecificationsUX Researcher9Key Form Validations, Hover/Focus/Error States, Loading Patterns…PDF · HTML
Localization & Multi-Language SpecUX Researcher4Target Locales, Translatable Content Strategy, Date/Number/Currency Rules…PDF · HTML
Mobile Platform SpecUX Researcher4Platform Targets, Native Capability Usage, Offline & Sync Behavior…PDF · HTML
Model Selection & Evaluation CriteriaSolutions Architect3Model Candidate Matrix, Evaluation Criteria & Benchmarks, Fallback & Routing PolicyPDF · HTML
Multi-Tenant Isolation DesignSolutions Architect4Isolation Model, Per-Layer Tenancy Decisions, Noisy-Neighbor Controls…PDF · HTML
NFR CatalogSolutions Architect8Performance Targets, Availability Targets, Latency Budgets…PDF · HTML
Observability & Monitoring DesignSolutions Architect4Golden Signals & SLOs, Instrumentation Plan, Alerting & Runbook Hooks…PDF · HTML
Payment Security & PCI SpecSecurity Analyst4Cardholder Data Scope, PCI Control Mapping, Tokenization & Processor Boundary…PDF · HTML
Performance & Load Test ScenariosRed Team Critic3Load Scenarios, Bottleneck Hypotheses, Test Environment & DataPDF · HTML
Process Flow DiagramsBusiness Analyst3Process Inventory, Primary Process Flows, Exception & Edge PathsPDF · HTML
Prompt Engineering & LLM SpecSolutions Architect4Prompt Inventory, Context Window Strategy, Prompt-Injection Defenses…PDF · HTML
Real-Time & WebSocket ArchitectureSolutions Architect4Real-Time Channels, Connection Topology, Fallback & Degradation…PDF · HTML
Risk Register (Consolidated)Red Team Critic7Risk Table, Mitigation Strategies, Linked Requirements…PDF · HTML
Traceability MatrixRed Team Critic6Requirement Coverage & Orphans, Requirement -> Story Mapping, Requirement -> Data Entity…PDF · HTML
Persona ProfilesUX Researcher3Persona cards, Goals and frustrations, Scenario usagePDF · HTML
Edge Case AnalysisRed Team Critic3Edge case inventory, Boundary conditions, Failure handlingPDF · HTML
Privacy Impact AssessmentSecurity Analyst3Processing inventory, Risk assessment, MitigationsPDF · HTML
Test CasesRed Team Critic3Test case catalogue, Preconditions and steps, Expected resultsPDF · HTML

Source: the Specira governed template registry, September 2026. Samples are rendered from the governed default templates on a fictional company, watermarked, as PDF and HTML. Four governed-only types (persona profiles, edge case analysis, privacy impact, test cases) follow the registry rows.

What are the most common questions about Specira artefacts?

Forty-nine registry types plus four that exist only in the governed templates, from the business requirements document to the Red Team review report. Thirteen form the core tier and compile for every project. The rest activate when discovery detects the matching signal: payments trigger the PCI spec, several tenants trigger the isolation design, an AI component triggers model selection. Every type belongs to one of the five agents and follows the same section contract.
Each sample is rendered from the Specira governed default template for that artefact, on a fictional field-service dispatch company, then watermarked. The sections, tables and diagrams are the ones the product compiles; only the names, figures and dates are illustrative. They show the structure and depth of a deliverable, not a customer's data. Samples are in English for now.
Yes. The Templates module lets you clone Specira's default contract for each artefact, then add, remove or rename sections, change the strategy that produces each one and set the minimum depth per tier. Exports then follow your version, and the gap report keeps naming the sections an unresolved decision leaves empty. The default contract stays available as a reference.
DOCX for human readers, Markdown and JSON for agents and tools, as a zip package per session or per project. Each artefact can also be pushed directly to Jira, Confluence, GitHub and Linear, where requirements and stories become tickets or pages linked back to their source. The export package lists every deliverable with its page estimate before compilation.
The export gate measures decisions resolved, not pages written. An artefact compiles once its core decisions are closed; open ones block compilation and are named with the fix expected. Deferred decisions ship listed in the gap report, never hidden behind prose written to fill the space. The Red Team Critic reads every turn before anything compiles.