Template Library¶
Template Library
Turn engineering work into durable evidence.
The Template Library is the Engineering Artifact Library of the ETIS Engineering Platform. It provides reusable, stage-aligned templates that help teams capture decisions, requirements, risks, reviews, verification, operations, monitoring, and stewardship evidence.
Engineering question¶
How do we consistently transform engineering decisions, reviews, risks, and outcomes into durable, reviewable, reusable engineering evidence?
Templates answer this question by giving engineering work a repeatable structure. They reduce the cost of disciplined engineering, but they do not replace engineering judgment.
Recommended navigation path¶
The Template Library works best when users move through it intentionally.
Engineering Stage
↓
Artifact Map
↓
Template Family
↓
Specific Template
↓
docs/project-workspace/
↓
Review and readiness gateStart with the Artifact Map
Use the map when you are working from an Engineering Stage and need the right template family.
02Use the Artifact Catalog
Use the catalog when you know the artifact name and need the exact template quickly.
03Complete Evidence in the Workspace
Copy templates into docs/project-workspace/, then complete them for your system.
What this library is¶
The Template Library is not a folder of blank forms. It is the artifact system that supports the ETIS lifecycle.
Each template exists to help teams capture a specific kind of engineering evidence. That evidence becomes useful only when it is completed with project-specific information, reviewed, accepted, and stored in the project workspace.
Stage-aligned
Most templates align directly to Engineering Stages ES-101 through ES-114 and support the evidence expected by those stages.
Evidence-centered
Templates help preserve requirements, decisions, reviews, risks, defects, release judgments, incidents, feedback, and lessons.
Reusable
Templates remain reusable source artifacts. Copy them into docs/project-workspace/ before completing them.
Reviewable
Completed artifacts should support readiness gates, downstream stages, governance review, and future stewardship.
How templates become evidence¶
Engineering question
↓
Template selection
↓
Project-specific completion
↓
Review and revision
↓
Acceptance or correction
↓
Project workspace evidence
↓
Downstream engineering useA template is only a starting structure. It becomes evidence when it supports a real engineering claim.
Do not treat a filled template as proof. Evidence must be accurate, project-specific, reviewed, and connected to the engineering decision it supports.
Recommended workflow¶
1. Start with the Engineering Stage
Use the current Engineering Stage to understand the question, activities, evidence expectations, outputs, and readiness gate.
2. Select the template family
Use the Artifact Map to identify the correct family for the stage, such as requirements, architecture, testing, release, or stewardship.
3. Open the specific template
Use the family folder or Artifact Catalog to locate the specific artifact you need.
4. Copy into the project workspace
Do not edit the reusable template directly. Copy it into the matching evidence family under docs/project-workspace/.
5. Complete and review honestly
Record project-specific information, assumptions, gaps, risks, and unresolved questions clearly.
6. Use it downstream
Good evidence is reused by later stages for design, testing, release, operations, monitoring, and stewardship.
Template families¶
Vision
Intent, problem, scope, stakeholders, assumptions, and success metrics.
ES-102Requirements
Requirements, constraints, use cases, traceability, and readiness.
ES-103Planning
Work breakdown, milestones, roles, dependencies, estimates, and risks.
ES-104Architecture
System context, components, decisions, evidence flow, quality strategy, and AI controls.
ES-105Design
Interfaces, workflows, data, access control, AI interaction, exceptions, and design review.
ES-106/107Implementation
Readiness, AI-use planning, work items, logs, guardrails, evidence, and verification notes.
ES-108Integration
Code review, pull request review, guardrail review, findings, traceability, and integration decisions.
ES-109Testing
Test strategy, test plan, test cases, verification matrix, defects, guardrails, AI, and regression.
ES-110Release
Release candidate, evidence index, risk assessment, guardrail review, AI review, decision, and conditions.
ES-111Operations
Operational scope, support model, monitoring plan, incident response, rollback, user transition, and risks.
ES-112Deployment
Deployment scope, plan, environment readiness, execution, communication, access, data, rollback, and checks.
ES-113Monitoring
Monitoring logs, operational events, incidents, access, data, guardrails, AI, feedback, and risk updates.
ES-114Stewardship
Learning, evidence review, lessons, incidents, feedback, guardrails, AI, backlog, plan, and next cycle.
SHAREDCross-cutting
Decision records, evidence records, issues, assumptions, action items, meeting notes, and reviews.
GOVGovernance
AI governance, evidence governance, release governance, risk, exceptions, and stewardship controls.
CATALOGArtifact Catalog
Find templates by artifact name, lifecycle area, purpose, and repository location.
Choosing the right template¶
| Need | Start Here |
|---|---|
| Define system intent | vision/ |
| Capture requirements or constraints | requirements/ |
| Plan work and responsibilities | planning/ |
| Define system structure | architecture/ |
| Specify detailed behavior | design/ |
| Prepare or record implementation | implementation/ |
| Review and integrate code | integration/ |
| Verify behavior and guardrails | testing/ |
| Decide release readiness | release/ |
| Prepare operation | operations/ |
| Deploy or transition | deployment/ |
| Monitor running use | monitoring/ |
| Learn after release | stewardship/ |
| Record cross-stage decisions or logs | shared/ |
| Manage AI, evidence, risk, release, or stewardship controls | governance/ |
Library guides¶
Artifact Map
Start here when you are working from an Engineering Stage and need to know which template family supports it.
02Artifact Catalog
Use the catalog when you know the artifact you need and want to find its template quickly.
Templates standardize engineering structure. Evidence comes from completed engineering work. Trust comes from engineering judgment.
Start with the stage, then choose the template.
The safest path is to begin from the Engineering Platform stage guidance and use templates only when they support the evidence required by that stage.
Begin ES-100 →