# UASK Engineering Hub > Open, versioned engineering knowledge for developers and AI coding agents: playbooks, practices, the UASK standards HIF and SCF, templates and agent skills, defined once and reused across projects. Maintained by UASK. Each link below is the Markdown source of a page of https://uask.pro/ (the page address with `.md`), byte for byte as in the repository. Its front matter states `status`, `version` and `authority`; the note after each link repeats the status. An entry marked "Draft — not approved" is a working draft that may change without notice: do not treat it as binding. Templates and skills carry the status of the items that list them. To use the Hub in a project, pin a release: see [Get started](https://uask.pro/knowledge/learn/get-started.md). ## Start here - [UASK Engineering Hub](https://uask.pro/knowledge/index.md): An open, versioned engineering knowledge base for developers and AI coding agents. Define once — Learn, Build, Verify, Reuse everywhere. (Draft — not approved) ## How We Do — how we work, in one document - [How We Do](https://uask.pro/knowledge/method/how-we-do.md): How we take any software work through its whole life — idea, build, release and support: who decides, how a project runs, and the rules we keep, in plain words for clients, owners and AI agents. (Draft — not approved · v0.2.0) ## Playbooks - [Playbooks](https://uask.pro/knowledge/playbooks/index.md): Step-by-step scenarios — project foundation, architecture review, quality and release — that combine core items, templates and agent skills. (Draft — not approved) - [Architecture review](https://uask.pro/knowledge/playbooks/architecture-review.md): A repeatable, evidence-based review of an existing or proposed software architecture — scope, as-is C4 views, quality scenarios, risks, ADR gaps, graded findings and tracked follow-ups. (Approved · v0.2.2) - [Deliver a release](https://uask.pro/knowledge/playbooks/deliver-a-release.md): Run one release or significant change from an approved idea to a closed release record - a release spec fixed to an appetite, gate G2, work packages built and verified, the release through the quality playbook, and a close-out - with the circuit breaker, the owner's gates and the record step. (Draft — not approved · v0.1.2) - [Operate and support](https://uask.pro/knowledge/playbooks/operate-and-support.md): Run a system in Support - take it over after the readiness review, keep a calendar of routine duties, take in work by class, handle incidents, review service levels every month and retire the system when the owner decides, without ever acting on a live system without a backup proved by restore. (Draft — not approved · v0.1.1) - [Project foundation](https://uask.pro/knowledge/playbooks/project-foundation.md): Start a new project, or re-found an existing one, with a reviewed vision, requirements, research, blueprint, decisions, roadmap and repository rules before implementation begins. (Approved · v0.4.3) - [Quality and release](https://uask.pro/knowledge/playbooks/quality-release.md): Take work from "ready" to "released and verified" — definitions of ready and done, test levels, CI gates, versioning, changelog, backup, deploy, rollback, verification and hotfixes. (Approved · v0.1.4) ## Engineering core - [Engineering Core](https://uask.pro/knowledge/core/index.md): Platform-independent engineering standards and practices — the rules every UASK project starts from. (Draft — not approved) - [Architecture decision records](https://uask.pro/knowledge/core/architecture/adr.md): Record each significant, hard-to-reverse technical decision as a short, numbered, immutable Markdown record with MADR 4 fields, an owner-level flag and a confirmation, as one file each or as a decision log. (Approved · v2.0.0) - [Architecture description (the Blueprint) and its sections](https://uask.pro/knowledge/core/architecture/architecture-description.md): A project's Blueprint is its architecture description - stakeholders, concerns, views and rationale from ISO 42010, arranged in twelve sections plus an annex, each required or optional by governance tier. (Draft — not approved · v0.1.5) - [Building blocks, boundaries and dependency rules](https://uask.pro/knowledge/core/architecture/building-blocks-and-dependencies.md): Divide a system into building blocks with a reason, an owner and a public interface for each, and state the dependency rules between them as numbered rules that a check can enforce. (Draft — not approved · v0.1.1) - [C4 model for architecture diagrams](https://uask.pro/knowledge/core/architecture/c4-model.md): Describe software architecture with C4 diagrams — system context, containers, components, and the deployment and dynamic diagrams — each with a title, a key, typed elements and labelled one-way relationships, chosen by governance tier. (Approved · v2.0.1) - [System context and external interfaces](https://uask.pro/knowledge/core/architecture/context-and-interfaces.md): Draw the system context, keep one inventory of every external interface with a contract or an owner for each, and classify every change to an interface as compatible or breaking before it ships. (Draft — not approved · v0.1.1) - [Fitness functions - architecture rules as self-testing checks](https://uask.pro/knowledge/core/architecture/fitness-functions.md): Turn each architecture rule into an automatic check that proves itself on a deliberately broken sample, record it next to the rule, and change the document, the rule and the check in one edit. (Draft — not approved · v0.1.2) - [Quality attributes, quality goals and scenarios](https://uask.pro/knowledge/core/architecture/quality-attributes.md): State a project's quality requirements in the vocabulary of ISO/IEC 25010, choose three to five quality goals, make each one testable as a scenario with a measure, and add an operability block for running the system. (Draft — not approved · v0.1.2) - [Risk register and technical debt register](https://uask.pro/knowledge/core/architecture/risks-and-technical-debt.md): Keep two short registers in section 11 of the Blueprint - risks graded by likelihood and impact, and technical debt with its principal, interest and trigger - and review them at every release. (Draft — not approved · v0.1.4) - [Commit messages (Conventional Commits)](https://uask.pro/knowledge/core/configuration-management/conventional-commits.md): Write commit messages as "type(scope): summary" by Conventional Commits 1.0.0, so history is readable and releases and changelogs can be derived from it. (Approved · v1.0.0) - [Semantic versioning](https://uask.pro/knowledge/core/configuration-management/semantic-versioning.md): Number releases MAJOR.MINOR.PATCH by SemVer 2.0.0 so that the version itself tells users whether an upgrade can break them. (Approved · v1.0.0) - [Delivery metrics](https://uask.pro/knowledge/core/management/delivery-metrics.md): Measure how a project delivers with DORA's five software delivery metrics and a few method metrics taken from records the method already writes, at the level of the application, to improve the way of working and never to rank people or agents. (Draft — not approved · v0.1.1) - [Risk-based governance tiers](https://uask.pro/knowledge/core/management/governance-tiers.md): Scale the amount of process to the risk of the project — lightweight, standard or high-assurance — and say what each tier changes in the foundation, review and release playbooks, without ever removing an owner decision. (Approved · v2.0.0) - [How we work — rules of our own practice](https://uask.pro/knowledge/core/management/how-we-work.md): The rules of our own way of working that have no other home in the Hub: borrowing methods, the owner's time, development and support, client sites, logs, cases, privacy and public material. (Draft — not approved · v0.1.1) - [Roles and decision rights](https://uask.pro/knowledge/core/management/roles-and-decision-rights.md): Seven roles - owner, technical lead, client, lead, builder, verifier and automated gate - what each does and never does, which decisions belong to the owner, and how an agent escalates a question with options and a default. (Approved · v0.3.0) - [Backups before changes and restore tests](https://uask.pro/knowledge/core/operations/backups.md): Keep 3-2-1 backups with one copy offline or immutable, take a verified backup before every risky change, and prove backups by regular restore tests. (Approved · v1.0.0) - [Incidents and postmortems](https://uask.pro/knowledge/core/operations/incidents-and-postmortems.md): Handle an unplanned failure of a supported system with one incident lead, restore first, a written log and the owner told in time; then write a blameless postmortem for the incidents that meet criteria set beforehand, and turn each escaped defect into a new check. (Draft — not approved · v0.1.2) - [Production readiness and hand-over](https://uask.pro/knowledge/core/operations/production-readiness-and-handover.md): The checklist a system passes before Support takes it over - who supports it, a runbook, backups proved by restore, access, monitoring that reaches a person, service levels, a way in for changes and a record of what was waived - decided by the lead, with the owner placing the support. (Draft — not approved · v0.1.3) - [Service levels in small form](https://uask.pro/knowledge/core/operations/service-levels.md): State what working means for a supported system in two to four indicators with targets over a window, measured from outside, with support hours and response times kept apart from the targets, and review them monthly; an agreement with a client that carries a price stays the owner's. (Draft — not approved · v0.1.3) - [Definition of Done](https://uask.pro/knowledge/core/process/definition-of-done.md): The one checklist that says when a work package may merge - criterion met with a commit and check output, the same gate green locally and in CI, checks seen red first, a verifier who did not build it, and docs, commits and the log in order. (Draft — not approved · v0.1.1) - [Definition of Ready](https://uask.pro/knowledge/core/process/definition-of-ready.md): The one checklist that says when a release, and each work package in it, may start Build - a stated goal, a checkable Done criterion, a small size, the files and checks named, access in place and the owner's decisions made. (Draft — not approved · v0.1.1) - [Knowledge and memory](https://uask.pro/knowledge/core/process/knowledge-and-memory.md): Keep what a project learns where it will be found again: four memory layers (only files in Git are normative), recall and record in every phase, one route from a lesson to a check, and no other client's personal data in recall. (Draft — not approved · v0.2.0) - [Project lifecycle, gates and change classes](https://uask.pro/knowledge/core/process/project-lifecycle.md): One lifecycle for every project - Idea, Blueprint, Spec, Build, Release, Support - with owner gates G0 to G3, three change classes, recall and record steps, and two rules for backups and live systems. (Approved · v0.2.8) - [Release spec for one release or significant change](https://uask.pro/knowledge/core/process/release-spec.md): Write one design-doc-shaped release spec for each release or significant change, with goals and non-goals, checks first, a rollback and an appetite, and approve it before Build starts. (Draft — not approved · v0.1.5) - [Work packages](https://uask.pro/knowledge/core/process/work-packages.md): Build a release as small work packages, each with a brief, its own branch, checks written first, a verifier who did not build it and a merge gate that needs the same green checks as the author saw, and report each one with a commit and the check output. (Draft — not approved · v0.1.3) - [Acceptance criteria](https://uask.pro/knowledge/core/requirements/acceptance-criteria.md): Write acceptance criteria as observable pass-or-fail checks tied to requirement ids, agree them before work starts, and record who accepted the result with what evidence. (Approved · v1.0.0) - [Product vision](https://uask.pro/knowledge/core/requirements/product-vision.md): Write a one-page product vision — positioning statement, audiences, observable outcomes and non-goals — and agree it before the requirements specification is written. (Approved · v1.0.0) - [Requirements specification (PRD or SRS)](https://uask.pro/knowledge/core/requirements/requirements-specification.md): Keep one written requirements specification per product, with stable ids, single verifiable requirements, an out-of-scope list and traceability from vision to tests. (Approved · v1.0.0) - [Scope and minimum viable product](https://uask.pro/knowledge/core/requirements/scope-and-mvp.md): State what a release includes and excludes, define the minimum viable product by what it must learn, and manage every change of scope as a recorded, approved decision. (Approved · v1.0.0) ## Learn - [Learn](https://uask.pro/knowledge/learn/index.md): Tutorials and explanations that teach the ideas behind the Engineering Core; they contain no rules. (Draft — not approved) - [Get started with the Hub in your project](https://uask.pro/knowledge/learn/get-started.md): Pin a release of the UASK Engineering Hub in a project, vendor its rules, templates and skills with hub-sync, add the Claude Code plugin and upgrade safely. (Draft — not approved · v0.1.1) ## HIF — Human Interface Framework - [Human Interface Framework (HIF)](https://uask.pro/hif/index.md): HIF is a brand-independent normative framework for designing, building, evaluating and governing human interfaces. (Draft — not approved · v0.6.0) - [HIF Accessibility and Inclusion](https://uask.pro/hif/accessibility.md): This document defines the minimum accessibility and inclusive-design contract. The accompanying Accessibility Assurance and Conformance Record defines the evidence required to claim that the contract has been met. (Draft — not approved) - [HIF Accessibility Assurance and Conformance Record](https://uask.pro/hif/accessibility-assurance-template.md): Use one record per product release or audit scope. This record preserves the evidence behind an accessibility statement, procurement response, remediation plan or bounded conformance claim. (Draft — not approved) - [HIF Web Audit Report Template](https://uask.pro/hif/audit-report-template.md): Use this template with the Web Audit Playbook and HIF Test Design. Remove guidance text in brackets before delivery. Do not remove scope, limitations or statement boundaries. (Draft — not approved) - [Brand Expression](https://uask.pro/hif/brand-expression.md): This document defines how identity may be expressed through an HIF-conforming interface without changing the truth, semantics, accessibility or agency of the product. It supports a single product, a family of products, white-label delivery and independently governed brands. (Draft — not approved) - [Brand Profile](https://uask.pro/hif/brand-profile-template.md): Use this record to state, review and release the identity of one brand or brand package: strategy, assets, colour, type, voice, imagery, white-label packaging, portfolio relationship, rights, change and measurement. It operationalises HIF-BRD-* and Brand Expression. (Draft — not approved) - [Colour and Theming](https://uask.pro/hif/color-and-theming.md): This document defines how HIF specifies, derives, implements and verifies colour systems. Colour is simultaneously light, material, perception, information, identity and an implementation value. (Draft — not approved) - [Colour System Profile](https://uask.pro/hif/colour-system-profile-template.md): Use this record to commission, generate, review and release a product colour system. Each section names the rules of HIF-COL-* and HIF-CLR-* that it records. (Draft — not approved) - [Interface Constitution](https://uask.pro/hif/constitution.md): This document defines the universal normative requirements of the Human Interface Framework. How a Product Profile relates to them, and when it may depart from them, is set by HIF-EVL-027. (Draft — not approved) - [Content and Information Architecture](https://uask.pro/hif/content-information-architecture.md): Content is part of the interface, and information architecture is part of the product model. Neither is a final layer of copy applied to completed screens. (Draft — not approved) - [Data Visualisation](https://uask.pro/hif/data-visualisation.md): This document defines how HIF turns data into inspectable representations for analysis, explanation, monitoring and decision-making. A visualisation is an interface to a data-generating process, not decoration applied to numbers. (Draft — not approved) - [Design Foundations](https://uask.pro/hif/design-foundations.md): This document defines how HIF turns perception, composition and aesthetic judgement into defensible design decisions. It concerns the expressive form of an interface without treating taste, fashion or a design-system precedent as universal law. (Draft — not approved) - [Design Process and Research](https://uask.pro/hif/design-process-and-research.md): This document defines the HIF lifecycle for discovering needs, designing interactive systems, evaluating claims and learning from operation. It applies to new products, redesigns and independent client audits. (Draft — not approved) - [Design Review and Critique](https://uask.pro/hif/design-review-critique.md): This document defines how a team examines design work, distinguishes evidence from preference, makes accountable decisions and converts findings into verifiable action. (Draft — not approved) - [Design Systems Engineering](https://uask.pro/hif/design-systems-engineering.md): This document defines how HIF knowledge becomes a maintained design system without reducing interface design to a component library. It combines lessons from major public systems with HIF's semantic and human-centred foundation. (Draft — not approved) - [HIF Evaluation and Conformance](https://uask.pro/hif/evaluation.md): How HIF evaluates an interface, by whether people achieve goals, understand state and consequences and recover from errors, and how a product claims conformance: evidence classes, methods, severity, claim format, partial conformance, release gate and exceptions. (Draft — not approved) - [Foundations and Evidence](https://uask.pro/hif/foundations-and-evidence.md): This document defines the intellectual foundations on which HIF requirements and design decisions are to be justified. It is a method for moving from knowledge about people and systems to bounded, testable claims about an interface. (Draft — not approved) - [HIF Glossary](https://uask.pro/hif/glossary.md): The terms HIF uses, each with one meaning: the vocabulary of the Constitution, of evaluation and conformance, of the rule model and the two-level profile model, and the terms that decide a verdict in the other parts, such as material, essential, key task, representative participants and high-risk. (Draft — not approved) - [HIF Imagery and Iconography](https://uask.pro/hif/imagery-iconography.md): This document governs imagery: photographs, illustrations, diagrams, maps, charts, screenshots, textures, symbols and interface icons. It covers why an image exists, what it communicates, and how its meaning, provenance, rights, accessibility and performance are verified. (Draft — not approved) - [Industry Design Systems](https://uask.pro/hif/industry-systems.md): This document compares major public design systems and platform guidance. It does not reproduce their visual styles. It extracts the transferable principles, operating practices and quality criteria that can strengthen HIF. (Draft — not approved) - [HIF Inspection Tooling and Evidence Contract](https://uask.pro/hif/inspection-tooling.md): This document defines how software may inspect an interface against HIF without turning partial automation into a false conformance claim. It covers rule registries, adapters, evidence, findings, coverage, security, reports and the hand-off to expert review and remediation. (Draft — not approved) - [HIF Interaction Model](https://uask.pro/hif/interaction-model.md): The interaction model translates the Constitution into architectural concepts. It does not prescribe a particular framework or programming language. (Draft — not approved) - [HIF Knowledge Base](https://uask.pro/hif/knowledge-base.md): The HIF Knowledge Base is a maintained body of knowledge for designing, building, evaluating and governing human interfaces: operating systems, applications, websites, services, kiosks, conversational systems, AI-mediated interaction and future interface forms. (Draft — not approved) - [Layout and Composition](https://uask.pro/hif/layout-composition.md): This document defines how HIF organises interface content in space. It applies to application windows, websites, operating-system surfaces, embedded interfaces, documents with interactive regions and spatial interfaces. (Draft — not approved) - [Legal, IP and Platform-Reference Governance](https://uask.pro/hif/legal-ip-and-platform-references.md): This document defines how an HIF product handles legal obligations, intellectual property, third-party platform references and evidence of rights before design or implementation is released. (Draft — not approved) - [Product Metrics and Experimentation](https://uask.pro/hif/metrics-experimentation.md): Measurement supports judgement; it does not replace it. A metric is a representation of an outcome under defined conditions, not the outcome itself. (Draft — not approved) - [Motion, Sound and Haptics](https://uask.pro/hif/motion-sound-haptics.md): This document defines temporal, auditory and tactile feedback in HIF. These modalities are functional channels that MAY reinforce continuity, causality, attention, orientation and consequence, but MUST NOT become a decorative tax, an accessibility dependency or a substitute for correct state. (Draft — not approved) - [Human Interface Framework](https://uask.pro/hif/overview.md): HIF is a brand-independent framework for designing, building, evaluating and governing human interfaces across operating systems, applications, websites, services, documentation, administrative tools, kiosks, terminals, conversational products and AI-mediated systems. (Draft — not approved) - [Interface Pattern Catalogue](https://uask.pro/hif/pattern-catalogue.md): A pattern is a reusable response to a recurring problem in a stated context. It is not a screenshot, component name or visual prescription. (Draft — not approved) - [HIF Philosophy](https://uask.pro/hif/philosophy.md): An interface is not a surface between a fully formed person and a fully formed machine. It is part of a wider system in which a person perceives state, forms an intention, acts, receives a response, corrects errors and interacts with other people. (Draft — not approved) - [HIF Product Profile Template](https://uask.pro/hif/product-profile-template.md): Copy this file into the documentation for a specific product as PRODUCT_INTERACTION_PROFILE.md. Each section names the rules of HIF that it records; the template adds no requirement. (Draft — not approved) - [HIF Application Profiles](https://uask.pro/hif/profiles.md): An Application Profile refines HIF for a class of interface and adds requirements to the Constitution without removing any. Four profiles are stable in HIF 1.0: Web Product, Desktop Application, Builder and Administrative, and Documentation. Eight are experimental. (Draft — not approved) - [HIF References](https://uask.pro/hif/references.md): HIF cites only traceable English-language originals. This register lists them by topic, with the link to the responsible body, paper or publisher and the date of the last check of every link. (Draft — not approved) - [Responsive and Adaptive Design](https://uask.pro/hif/responsive-adaptive-design.md): This document defines how HIF interfaces respond to changing space, capabilities, preferences and context. The target is not a catalogue of devices but a continuous, stateful interface that remains understandable and operable in every supported environment. (Draft — not approved) - [Rights Clearance and Release Record](https://uask.pro/hif/rights-clearance-template.md): Use this template with Legal, IP and Platform-Reference Governance. It records evidence and decisions; it does not replace legal advice. (Draft — not approved) - [HIF Test Design for Web Interfaces](https://uask.pro/hif/test-design.md): This document defines how an auditor derives a defensible set of tests from a large web interface. It supplements HIF Evaluation and the Web Audit Playbook. (Draft — not approved) - [HIF Typography](https://uask.pro/hif/typography.md): Typography is the system by which written language, numbers and code become perceivable, navigable and operable. It includes typeface selection, shaping, metrics, hierarchy, composition, localisation, loading, licensing and user adaptation. (Draft — not approved) - [HIF Visual Language](https://uask.pro/hif/visual-language.md): Visual language expresses a semantic model; it does not create that model. This part is an informative map from the summary of the visual language in HIF 0.6 to the rules and sections that now carry each of its statements. (Draft — not approved) - [HIF Web Audit Playbook](https://uask.pro/hif/web-audit-playbook.md): Independent, evidence-led evaluation of client websites and web applications: engagement, sampling, method stack, findings, deliverables and statement limits. (Draft — not approved) ## SCF — System Construction Framework - [System Construction Framework (SCF)](https://uask.pro/scf/index.md): The System Construction Framework (SCF) is a brand-independent normative framework for constructing, releasing, maintaining and retiring operating systems. (Draft — not approved · v0.1.0) - [System Construction Framework corpus backlog](https://uask.pro/scf/backlog.md): Known gaps in the corpus of the System Construction Framework (SCF) itself, recorded openly: each item is a defect of the standard, not of a product built with it. (Draft — not approved · v0.8.0) - [Change policy](https://uask.pro/scf/change-policy.md): How the System Construction Framework (SCF) itself changes: its public interface, the classes of change, rule identifiers, deprecation, review and records, so that a consumer knows what a pinned version protects. (Draft — not approved · v0.1.0) - [Construction Constitution](https://uask.pro/scf/constitution.md): The universal, identified requirements of SCF, grouped by subject; a profile may make them stricter but not weaken them without a registered exception and a risk assessment. (Draft — not approved · v0.1.0) - [Evaluation and conformance](https://uask.pro/scf/evaluation.md): How the System Construction Framework (SCF) evaluates a system: evidence levels, the baseline verification corpus with its check identifiers, conformance levels, the release gate and exceptions, not whether it boots or how many features it has. (Draft — not approved · v0.4.0) - [System Construction Framework glossary](https://uask.pro/scf/glossary.md): The terms the System Construction Framework (SCF) uses, each with one meaning and one home: a term is defined here once and every other document links to it. (Draft — not approved · v0.1.0) - [System Construction Framework knowledge base](https://uask.pro/scf/knowledge-base.md): The knowledge base of the System Construction Framework (SCF): the maintained body of knowledge for constructing, releasing, maintaining and retiring operating systems, with its layers, source policy and claim classes. (Draft — not approved · v0.1.0) - [System Construction Framework](https://uask.pro/scf/overview.md): Overview of the System Construction Framework (SCF), a brand-independent framework for constructing operating systems: normative hierarchy, corpus map, normative words, product process and where each statement lives. (Draft — not approved · v0.1.0) - [Platform dossiers](https://uask.pro/scf/platform-dossiers.md): Facts about the platform families the System Construction Framework (SCF) is mapped onto — tools, signing, archive pinning, privilege and limits — each with a version, a date and a primary source; informative, and never a source of obligations. (Draft — not approved · v0.1.0) - [Platform families and the portable build model](https://uask.pro/scf/platform-families.md): The portable build model of the System Construction Framework (SCF): the ten-stage construction pipeline, the portable entities, the capabilities an adapter declares and the contract an adapter satisfies to be admitted to a construction service. (Draft — not approved · v0.1.0) - [Conformance statement template](https://uask.pro/scf/product-profile-template.md): The form of a conformance statement, in which a product states for one release what it claims and what backs the claim: identification, scope, level, traceability, exceptions and approval. (Draft — not approved · v0.1.1) - [System Construction Framework profiles](https://uask.pro/scf/profiles.md): A profile narrows the System Construction Framework (SCF) for a class of system. It adds requirements and never removes them, and one product can carry several profiles. Each profile is a group of identified rules. (Draft — not approved · v0.2.0) - [References](https://uask.pro/scf/references.md): The regulatory texts and standards behind the legal and vulnerability rules of the System Construction Framework (SCF): the EU Cyber Resilience Act and the UK product-security regime as dated claims; informative, never a source of obligations. (Draft — not approved · v0.1.0) - [Release record template](https://uask.pro/scf/release-record-template.md): The controlled record of one release: its inputs, evidence, exceptions and approval, required by SCF-EVD-004 and retained for the support period (SCF-EVD-006). (Draft — not approved · v0.1.0) - [Update and lifecycle](https://uask.pro/scf/update-and-lifecycle.md): The method for SCF-LCM, SCF-UPD and the release-facing parts of SCF-VUL and SCF-ART as rules with identifiers: version identity, fixpacks, channels, advisories, support phases, branches, and atomic and image-based updates, each with its check. (Draft — not approved · v0.1.0) - [Vulnerability management](https://uask.pro/scf/vulnerability-management.md): The method for the vulnerability-handling rules of the System Construction Framework (SCF) as rules with identifiers: intake, triage, remediation and closure, coordinated disclosure, regulatory reporting duties, and the records that show each was done, each with its check. (Draft — not approved · v0.1.0) ## Templates - [Templates](https://uask.pro/knowledge/templates/index.md): Artefact templates of the UASK Engineering Hub: copy one into your project, fill it in, and check it. Every template can be downloaded as Markdown. (Draft — not approved) - [ADR](https://uask.pro/knowledge/templates/adr.md): Template for the playbook mgmt.project-foundation, stage 6; copy it and fill it in. (Template; Approved) - [ADR v1](https://uask.pro/knowledge/templates/adr-v1.md): Template; copy it and fill it in. (Template; Draft — not approved) - [AGENTS.md](https://uask.pro/knowledge/templates/agents.md): Template for the playbook mgmt.project-foundation, stage 8; copy it and fill it in. (Template; Approved) - [Architecture review report](https://uask.pro/knowledge/templates/architecture-review-report.md): Template for the playbook arch.architecture-review; copy it and fill it in. (Template; Approved) - [Architecture review scope](https://uask.pro/knowledge/templates/architecture-review-scope.md): Template for the playbook arch.architecture-review, stage 1; copy it and fill it in. (Template; Approved) - [Blueprint](https://uask.pro/knowledge/templates/blueprint.md): Template for the playbook mgmt.project-foundation, stage 5; copy it and fill it in. (Template; Approved) - [Blueprint v1](https://uask.pro/knowledge/templates/blueprint-v1.md): Template; copy it and fill it in. (Template; Draft — not approved) - [Changelog](https://uask.pro/knowledge/templates/changelog.md): Template for the playbook quality.quality-release; copy it and fill it in. (Template; Approved) - [Client brief](https://uask.pro/knowledge/templates/client-brief.md): Template for the playbook mgmt.project-foundation, stage 1; copy it and fill it in. (Template; Approved) - [Definition of done](https://uask.pro/knowledge/templates/definition-of-done.md): Template for the playbook quality.quality-release; copy it and fill it in. (Template; Draft — not approved) - [Definition of ready](https://uask.pro/knowledge/templates/definition-of-ready.md): Template for the playbook quality.quality-release; copy it and fill it in. (Template; Draft — not approved) - [Knowledge item](https://uask.pro/knowledge/templates/knowledge-item.md): Template; copy it and fill it in. (Template; Draft — not approved) - [PRD](https://uask.pro/knowledge/templates/prd.md): Template for the playbook mgmt.project-foundation, stage 3; copy it and fill it in. (Template; Approved) - [PRD v1](https://uask.pro/knowledge/templates/prd-v1.md): Template; copy it and fill it in. (Template; Draft — not approved) - [Release checklist](https://uask.pro/knowledge/templates/release-checklist.md): Template for the playbook quality.quality-release; copy it and fill it in. (Template; Approved) - [Release spec](https://uask.pro/knowledge/templates/release-spec.md): Template; copy it and fill it in. (Template; Draft — not approved) - [Roadmap](https://uask.pro/knowledge/templates/roadmap.md): Template for the playbook mgmt.project-foundation, stage 7; copy it and fill it in. (Template; Approved) - [Run record](https://uask.pro/knowledge/templates/run-record.md): Template for the playbook mgmt.project-foundation; copy it and fill it in. (Template; Approved) - [Test strategy](https://uask.pro/knowledge/templates/test-strategy.md): Template for the playbook quality.quality-release; copy it and fill it in. (Template; Approved) - [Vision](https://uask.pro/knowledge/templates/vision.md): Template for the playbook mgmt.project-foundation, stage 2; copy it and fill it in. (Template; Approved) ## Skills - [Skills](https://uask.pro/knowledge/skills/index.md): Agent Skills of the UASK Engineering Hub: step-by-step procedures that make a coding agent apply the Hub's playbooks, items and templates. (Draft — not approved) - [Architecture review (skill)](https://uask.pro/knowledge/skills/architecture-review/SKILL.md): Run an evidence-based architecture review of an existing or proposed system — own product, inherited client site, or a design before approval — following the UASK Engineering Hub playbook arch.architecture-review. Use when asked to review, audit or assess an architecture, take over an inherited… (Agent skill; Approved) - [Operate and support (skill)](https://uask.pro/knowledge/skills/operate-and-support/SKILL.md): Applies the UASK Engineering Hub playbook ops.operate-and-support. Use when a system is going live under support or already runs in Support - taking it over, keeping the calendar of routine duties, taking in a request or a defect and classing it, handling an incident, writing the monthly review,… (Agent skill; Draft — not approved) - [Project foundation (skill)](https://uask.pro/knowledge/skills/project-foundation/SKILL.md): Lay the foundation of a software project before implementation — intake, vision, requirements (PRD), research, blueprint with C4 views, architecture decision records, roadmap and issues, repository rules (AGENTS.md), owner approval — by running the UASK Engineering Hub playbook… (Agent skill; Approved) - [Quality and release (skill)](https://uask.pro/knowledge/skills/quality-release/SKILL.md): Applies the UASK Engineering Hub playbook quality.quality-release. Use when a project needs its quality baseline (Definition of Ready and Done, test strategy, CI gate, changelog), when finishing a change, when preparing, deploying, verifying or rolling back a release, or when a released version… (Agent skill; Approved) ## Optional - [Glossary](https://uask.pro/knowledge/glossary/index.md): Short definitions of engineering terms used across the Hub, one term per page. (Draft — not approved) - [ADR (architecture decision record)](https://uask.pro/knowledge/glossary/adr.md): Glossary term. An architecture decision record is a short, numbered Markdown file that records one significant decision: its context, the options considered, the choice and its consequences. (Draft — not approved · v1.0.1) - [Blueprint (architecture and plan)](https://uask.pro/knowledge/glossary/blueprint.md): Glossary term. A blueprint is a project's architecture description: the document that says how a product is built to meet its requirements, in twelve sections from goals and stakeholders to risks, plus an annex that maps requirements to sections. (Draft — not approved · v1.1.0) - [MVP (minimum viable product)](https://uask.pro/knowledge/glossary/mvp.md): Glossary term. A minimum viable product is the first version of a product that lets a team learn the most about real users with the least effort — a complete, usable slice, not a minimal one. (Draft — not approved · v1.0.0) - [PRD (product requirements document)](https://uask.pro/knowledge/glossary/prd.md): Glossary term. A product requirements document states the problem, scenarios, requirements with ids, acceptance criteria, constraints and out-of-scope items of a product in one living file. (Draft — not approved · v1.0.0) - [Release spec (design document of one release)](https://uask.pro/knowledge/glossary/release-spec.md): Glossary term. A release spec is a short design-doc-shaped document that says what one release or significant change will do, how it will be checked and how it will be undone, before it is built. (Draft — not approved · v1.0.1) - [Scope (of a release or product)](https://uask.pro/knowledge/glossary/scope.md): Glossary term. Scope is the line around what a product or release will do: the written lists of what is in, what is deferred to later and what is out for good. (Draft — not approved · v1.0.1) - [Specification (requirements specification)](https://uask.pro/knowledge/glossary/specification.md): Glossary term. A requirements specification is a systematically written collection of requirements for a system — what it must do and how well — that can be reviewed, tested against and traced. (Draft — not approved · v1.0.1) - [Vision (product vision)](https://uask.pro/knowledge/glossary/vision.md): Glossary term. A short written picture of a product once it exists: who it is for, which need it meets, what is different about it and which outcomes show it has succeeded. (Draft — not approved · v1.0.0) - [Platform profiles](https://uask.pro/knowledge/profiles/index.md): Platform profiles extend Engineering Core items with the rules that apply only to one platform, such as OpenCart or a Linux distribution. (Draft — not approved)