UASK Engineering Hub
The UASK Engineering Hub is an open, versioned engineering knowledge base for developers and AI coding agents who build software products of different kinds.
Every rule has one source, a version, a status and evidence, so a project can pin exactly the version it follows. Unlike scattered wikis, books and ad-hoc prompt files, the same knowledge is readable by people and executable by agents.
Define once — Learn, Build, Verify, Reuse everywhere.
The standards that live here: HIF — Human Interface Framework, and SCF — System Construction Framework.
Sections
| Section | What it holds |
|---|---|
| Engineering Core | platform-independent standards and practices |
| Platform profiles | additions for one platform, extending core items |
| Playbooks | end-to-end scenarios that combine items, templates and skills |
| Learn | tutorials and explanations, without rules |
| Glossary | one term, one definition |
All items are in review: they are open for reading and comment, and may still change before the first release.
How to add an item
- Pick the section and kind: a rule set or practice goes to
content/core/<domain>/, a platform addition tocontent/profiles/<profile>/, a tutorial tocontent/learn/, a term tocontent/glossary/. - Copy
templates/knowledge-item.mdto<slug>.mdand fill in the front matter. The id is<domain prefix>.<slug>(for examplearch.adr); prefixes are listed inschemas/knowledge-item.schema.json. A new item starts at version0.1.0or1.0.0with statusdraft. - Write the body in the fixed order: Summary, Rules, Guidance, Explanation, Examples, Sources. Upper-case
MUST, SHOULD and MAY appear only under Rules, one rule per
- **Rn.**line. - Cite at least one primary source with its licence (SPDX id) and access date. Write in your own words.
Material adapted from CC BY-SA sources goes only to
content/adapted/; NC and ND sources are linked, never copied. - Run
python3 tools/validate_content.py --standardsandbash tests/run.sh, then open a pull request with statusreview.