Knowledge Base
Store the documents, files, and agent-built artifacts that give 8090 Software Factory agents project context.
The Knowledge Base is where a project keeps its supporting material: documents your team writes, files you upload, and interactive artifacts agents build. Agents draw on this material while generating requirements, blueprints, and work orders, so they work from the same context your team already uses instead of relying on assumptions.
Two kinds of resource
Everything in the Knowledge Base is a resource, and there are exactly two kinds. The difference shapes how you work with each one.
| Resource | What it is | How you work with it |
|---|---|---|
| Document | A rich-text document you write and edit inside 8090 Software Factory, using the same live, collaborative editor as Requirements and Blueprints. | Edit in place, with tracked changes, comments, and full version history. |
| File | A file you upload. Its bytes are stored as-is. | Preview it inline or download it. Files carry a type and a size. |
Documents are edited; files are viewed. A document can also act as a container: any resource that has children behaves as a folder, so you can group related material under it.
The navigator
The Knowledge Base opens with a navigator on the left listing every resource. Each row shows the resource title and an icon for its kind and type. You can rename or delete a resource inline from its row.
A view picker changes how the list is organized. When you switch away from Tree, the active view shows as a chip you can clear to return to the default.
| View | Order |
|---|---|
| Tree | The folder hierarchy. This is the default. |
| A–Z | Flat alphabetical. |
| Recently edited | Most recently changed first. Document rows show their update time. |
In Tree view you can drag a row to reorder it or nest it under another resource.
Create and nest documents
Create a new document from the navigator, either at the root or under an existing resource to nest it. Nesting is a real parent and child hierarchy, so you can build a folder tree that fits your project.
A common pattern is a parent document that groups related child documents beneath it. For example, a Meeting Transcripts parent with a dated document for each session under it, or a Postmortems parent holding one document per incident. Children can have their own children, so the tree goes as deep as you need. Put a document under another document to group related material, and the parent reads as a folder in the tree.
Upload files
You can add files two ways.
Upload from the navigator
From the navigator, choose to upload a file and pick files from your computer. If needed, select a destination folder first.
Or drag files onto the navigator
Drag files straight from your computer onto the navigator. While you drag, the navigator shows a drop overlay. Drop onto empty space to add at the root, or onto a specific folder to place the files there. You can drop several files at once.
While a batch uploads, a progress footer tracks it. It reads N of M while files are in flight and N of M Complete when the batch finishes, and each file shows its percentage or Failed.
Files upload comfortably up to 100 MB each, which leaves plenty of headroom for most documents, designs, and recordings.
Files are scanned on upload
Every uploaded file is automatically scanned for malware before its contents can be read. For a few seconds right after upload, a file is present but not yet readable. 8090 Software Factory waits this out for you, so previews, embeds, and agent reads resolve on their own once the scan clears.
If you rename a file to a different extension, 8090 Software Factory asks you to confirm with Change File Extension?. Choosing Rename Anyway changes only the name, not the file itself.
Preview files
File-backed resources are either previewable or stored only. Previewable files render inline in a dedicated preview surface. Anything without an inline renderer shows a fallback panel with a download action instead.
Supported files
8090 Software Factory accepts most common document, text, image, audio, and video formats, including the Microsoft Office suite. The following file types render inline:
| Type | Preview |
|---|---|
| Rendered document | |
| Images | Interactive viewer with zoom |
| Audio and video | Inline player |
| CSV | Tabular view |
| Markdown and plain text | Rendered text |
| PowerPoint | Rendered slides |
| HTML artifacts | Sandboxed live viewer |
Image zoom
The image preview is interactive. Use the toolbar to Zoom in, Zoom out, or Reset zoom (reset is disabled at 100%). Zoom runs from 25% to 400% in 25% steps, and you can pinch to zoom on a trackpad while normal scrolling still pans the image. The same zoom controls apply when you review an image inside version history.
Version history
Documents have full version history, the same mechanics shared with Requirements and Blueprints. Open Version History to:
- See the list of saved versions.
- Name a version, or create a named version at the current state.
- Compare two versions side by side.
Version history also works for files. When you open a version of a file, the panel renders its content using the same preview surface, so PDFs, images (with the zoom controls above), CSVs, and the rest are all reviewable inside version history, not just documents.
Heading anchor links
Inside any 8090 Software Factory document you can link precisely to a heading. When you create a link, the link picker offers a Section Headings flyout listing the current document's headings, H1 through H3, as selectable targets. Choosing one creates a link that jumps and scrolls to that heading. If the document has no headings, the flyout shows "This document has no headings."
This pairs with citing Knowledge Base material in documentation. You can link not just to a whole file but to a specific section within a document.
Add material to agent context
Agents retrieve relevant Knowledge Base material on their own while planning and documenting. You can also pull specific files into a conversation:
- Type
@in agent chat to mention a file. - Drag a file directly into an agent chat.
Files you upload during a chat automatically appear in the project's Knowledge Base.
Codebase context is separate
The Knowledge Base holds documents and files you provide. A connected repository is indexed separately. See Codebase overview for how agents read your code.
Cite Knowledge Base material in documentation
Links connect a document to the exact material that supports it. When working on any document in 8090 Software Factory, highlight text and select the Link icon to attach a Knowledge Base file, or a specific heading within a document. Hovering over linked text shows the associated material, with options to open or remove the link.
Link evidence where it supports a decision
Attach the source to the specific requirement, blueprint statement, or decision it supports. A targeted link is easier to verify than a general list of references.
HTML artifacts
8090 Software Factory agents can build self-contained interactive HTML artifacts, such as dashboards, roadmaps, diagrams, design systems, and calculators. These live in the Knowledge Base as .html file resources.
- Each artifact is a single self-contained file. All CSS and JavaScript are inline and images are embedded, so it renders anywhere with no external dependencies.
- Artifacts have a home. By convention they are stored in an HTML folder at the Knowledge Base root, and a project design system lives in a DesignSystem resource that agents follow for consistent styling.
- Artifacts open in a safe viewer. The viewer renders the page live in a sandboxed frame with a reload control (each open starts clean) and a full-screen toggle, plus a download control. If the page throws, the viewer shows a runtime-error notice. The viewer is read only and never exposes source or editing.
- Artifacts embed inline. An agent can insert an artifact into any document as an inline block, where it renders in a sandboxed frame. Update the artifact in place and every embed of it updates too.
Best practices
- Upload files early so agents have context from the start.
- Group related material by nesting documents into folders.
- Use clear, descriptive titles.
- Link Knowledge Base material into Product Overview documents, Feature Requirements, and Blueprints to keep traceability.
- Remove outdated material so agents work from current context.
Want to see how usage adds up across your project? Learn about usage and billing.