Knowledge Base.
Reusable architecture, security, and compliance entries.
The Knowledge Base is a workspace-scoped library of reusable spec fragments. Everything a project would otherwise have to re-author from scratch — a known compliance posture, a deployment topology, a partner integration shape — can live here and be pulled into a new project as a seed.
Three kinds of entries #
| Type | What it is | When you'd use one |
|---|---|---|
spec | A finished SpecGraph spec from a previous project, archived for reuse | New project that's a "v2" or sibling of a shipped one |
brownfield | A description of an existing system, captured as a spec-shaped document | Building on top of a system you didn't originally spec |
template | A scaffold with phase content pre-filled — e.g. "FedRAMP-Moderate web service" | Repeated work in regulated verticals |
Templates are the most common reason teams adopt the KB. The other two are essentially "a complete spec, frozen."
Verticals and classification #
Every KB entry has two facets baked into the schema:
- Vertical —
federal,state-local,healthcare,finance,education,energy,defense,enterprise, orpublic-safety. - Classification —
public,internal,sensitive, orcui(controlled unclassified information).
Classification controls who can read the entry. Anything sensitive or cui requires the viewer to have an explicit grant on the entry, even if they're an editor on the workspace. This is intentional — KB entries are how compliance posture leaks across teams, and the system is conservative.
Seeding a project from the KB #
In the New Project wizard, the "Seed from knowledge base" picker shows every entry the current user is allowed to read. Picking one copies its content into the new project as a starting point — the original is untouched. Edit freely; nothing flows back to the KB unless someone explicitly publishes the result.
You can also pull a single phase from a KB entry mid-project, via the phase header menu (More → Pull from KB).
When to add an entry #
The right time to write a KB entry is the second time someone re-authors the same content. The first time, you're discovering what the right shape is. The second time, you're paying for the lack of an entry. The third time, you're embarrassed.
Entries can be added by any workspace editor; sensitive/CUI entries require an admin to publish.