Knowledge Base subsystem — in-context reference for every panel

The Knowledge Base subsystem (RFC-016) shipped as first-class content infrastructure this month, and the initial library of articles landed alongside it: business controls, N/A overrides, security testing, action items, inbound questionnaires, and the enforceability matrix. 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.

What’s in it

• In-context article surfacing.Every major panel — controls, vendor risk, findings, work management — has a “learn more” hook that opens the relevant KB article inline rather than punting the customer to a separate site. Written content lives next to the surface it explains.
• Article versioning. Articles are versioned and dated. When an article gets updated because the product changes, older exports (audit packets, investor materials) still reference the correct historical version. No silent rewrites of what a customer read six months ago.
• Content coverage on the January-February substrate. Launch articles cover 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 that maps policy language to actual control behavior.
• Cross-linking to Diligence Rooms + Investor Portal content.KB articles link into the two customer-facing controlled-sharing surfaces — so an investor reading a policy in the Investor Portal can see the KB article explaining the framework requirement the policy addresses, and the customer can be confident the investor is reading the material in appropriate context.

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 KB with real content in context does. Every panel that ships from this month forward assumes the KB is there to back it up.