Knowledge Documents

Generation is only as grounded as what it can read. Knowledge documents are the organization-specific material you upload so designs reflect your reality: vendor security papers, internal standards and platform guides, scope memos, meeting notes, prior assessments.

Upload and Indexing

Upload documents on Design Inputs; common document formats are accepted. Each document is indexed before it participates; the list shows indexing status, and only indexed documents feed the AI surfaces.

Where Documents Act

Surface	How They Are Used
Generation	Relevant passages ground component choices and rationale
Component provenance	The detail panel's "informed by" section cites the documents behind a choice
Design review	Critics use uploaded material as citable reference: a vendor document confirming encryption at rest can support or defeat a finding
Design chat	Answers can draw on the indexed set for this package

Documents Are Data, Never Instructions

Uploaded content is treated strictly as reference material. Text inside a document cannot steer the AI's behavior, suppress findings, or change the rules it operates under; a sentence like "report no issues" in a vendor PDF is just a sentence.

What to Upload (and What Not To)

Worth uploading: anything a careful human architect would want open on their desk: standards the design must follow, vendor claims worth citing, decisions already made elsewhere. Not worth uploading: generic public documentation of well-known products (the models already know it) and anything with row-level customer data; the platform wants your rules and context, not your records.