The standards library
The standards library — the Knowledge area (/knowledge) — is your firm’s
curated body of architecture knowledge. The AI grounds its recommendations on
it, so what’s in here shapes what eavantage proposes.
A fresh deployment starts empty. You build it up.
Three tiers
Section titled “Three tiers”| Tier | What it holds | Examples |
|---|---|---|
| Tier 1 — Framework standards | Recognised architecture frameworks | TOGAF, ArchiMate, Zachman |
| Tier 2 — Platform implementation patterns | Reusable patterns for a kind of target platform | |
| Tier 3 — Firm playbooks | Your firm’s own conventions and approaches |
When you upload a document, eavantage classifies it into a tier and suggests metadata for you to confirm.
From draft to approved
Section titled “From draft to approved”A standard moves through a lifecycle: draft → under review → approved → deprecated.
- Only approved standards are used — an approved standard’s entities are written into the knowledge graph and its content becomes available to the AI for grounding.
- Approving a standard for the library is a platform administrator action (via the SKB nominations queue in Admin).
- A new version of a standard goes back through review.
Semantic retrieval
Section titled “Semantic retrieval”Standards are chunked and embedded, so the recommendation engine and the AI assistant can pull the relevant passages for a given gap or question rather than the whole document.
Promoting engagement learnings
Section titled “Promoting engagement learnings”At the end of an engagement, patterns and playbook entries proven out during the work can be nominated for the library. A platform administrator reviews the nomination and, if approved, it’s promoted — so each engagement makes the next one sharper. See Governance & closure.