February 20, 2026 · Knowledge Base · Subsystem + Launch Content

Knowledge Base subsystem — in-context reference for every panel

RFC-016 lands the Knowledge Base as first-class content infrastructure, alongside launch articles for business controls, N/A overrides, security testing, action items, inbound questionnaires, and the enforceability matrix. Versioned, in-context, cross-linked to the surfaces they explain.

What changed

The Knowledge Base subsystem (RFC-016) shipped as first-class content infrastructure this month, and the initial library of articles landed alongside it. Instead of scattered help-text tooltips and broken support-doc links, the platform now has a real internal reference layer that customers hit in-context.

In-context articles
Every major panel — controls, vendor risk, findings, work management — has a learn-more hook that opens the relevant article inline rather than punting the customer to a separate site.
Versioning
Articles are versioned and dated. When an article updates because the product changes, older exports (audit packets, investor materials) still reference the correct historical version.
Launch coverage
Six articles for the concepts customers hit first: business controls, N/A overrides on inapplicable framework requirements, security testing configuration, action items, inbound questionnaire responses, and the enforceability matrix.
Cross-linking
Articles link into Diligence Rooms and the Investor Portal, so an investor reading a policy sees the article explaining the framework requirement that policy addresses.

Why it matters

vCISO Lite’s bet is that a founder or ops lead who has never run a compliance program can operate the platform without an implementation team walking them through it. That bet only holds if the platform explains itself as the customer works. Tooltip-and-a-prayer doesn’t scale; a Knowledge Base with real content in context does.

Every panel that ships from this month forward assumes the Knowledge Base is there to back it up. Written content lives next to the surface it explains, and the pieces that cross customer boundaries — Diligence Rooms and the Investor Portal — carry the same articles through, so the investor reading a policy sees the same framework context the customer saw while writing it.

Availability

Shipping today to every platform tier. The six launch articles are live on the surfaces they explain; no migration required.

Existing help-text tooltips on the covered panels now route to the inline Knowledge Base reader. Previously bookmarked support-doc URLs continue to redirect to the canonical article where one exists. Export surfaces (audit packets, investor packets) stamp the article version at the time of export so later edits don’t silently rewrite what a customer or investor already received.

Known limitations

The launch library is six articles. The next cycle extends coverage to the panels that ship on top of this foundation — assessments, scanner findings, and the policy library are queued for the following release.

Articles are reached from the surface they explain. There is no global search bar across the Knowledge Base yet; discovery is in-context by design for this iteration.

Historical version references hold for exports. Live article links always resolve to the current version — if you need an older rendering outside of an export, you have to pull it from the versioned record.