Add Business Context
Upload files or write context for the organization and every selected department.
Supported Sources
You can upload files or enter written Markdown for each scope. You may switch modes while preparing the submission without losing the entries already added.
Supported file extensions are:
| Content | Extensions | Notes |
|---|---|---|
| Markdown | .md, .markdown | Preferred for owner-authored operating context |
| Plain text | .txt | Must be UTF-8 |
| Tabular | .csv | Include clear headers and explain ambiguous columns |
| Structured | .json, .yaml, .yml, .toml | Use bounded, relevant exports |
.pdf | Must contain a readable text layer |
Each source can be at most 50 MB, and filenames can be at most 240 characters.
Upload Files
Choose a scope
Start with the organization, then complete every selected department.
Add current sources
Choose files that describe stable facts, responsibilities, workflows, constraints, or authoritative systems. Split unrelated subjects into separate files so citations remain understandable.
List every evidenced business system even when it is external, manually operated, or not connected to Oblive. Include what the system is used for, who owns it, which workflow depends on it, and its role in that workflow. Onboarding compiles this meaning into Context without treating the source as proof of current connection state.
An Oblive connector is linked only when the safe current registry contains an exact key match. Similar display names are not enough. A business system may remain valid Context without a connector link, and that external system must not be reported as disconnected.
Review the source list
Remove duplicates and obsolete drafts. Use descriptive filenames such as
support-escalations.md, not notes-final-v4.md.
Complete every scope
The organization and each selected department require at least one uploaded or written source.
Write Context Directly
Written context is ideal when the needed knowledge lives with the owner rather than in an existing document. Use headings, short paragraphs, lists, and concrete names.
# Refund decisions
- Support may approve refunds up to $100 for duplicate charges.
- Larger refunds require the finance owner.
- Never promise a refund before confirming the charge in Stripe.What Happens to a PDF?
Oblive retains the original source and derives searchable Markdown from its text layer. Scanned image-only PDFs are rejected because they cannot provide reliable text evidence in the current ingestion path.
Common Upload Problems
- Unsupported extension: convert the source to Markdown, text, CSV, JSON, YAML, TOML, or a text-based PDF.
- Unreadable text: save the file as UTF-8.
- PDF has no text layer: export it again with selectable text or provide a Markdown version.
- File is too large: split it by topic or remove irrelevant embedded assets.
- Scope remains incomplete: add at least one source for that organization or department.
Expected Result
Every selected scope shows at least one retained source and the onboarding flow allows compilation to begin.
Contributors extending ingestion should read Extend Onboarding and Context.