Summary
A space is the fundamental organisational unit in Artefaq. It is a single container (directory) for the user's documents. Everything the user does — exploring, collecting snippets, generating artefacts — happens within the context of a space.
Simplified Model
In Artefaq, spaces and sources are merged into a single concept. There is no separate "sources" or "feeds" layer that the user needs to manage. One space = one document collection.
This is a deliberate simplification over the underlying Condelo platform (which supports spaces → sources → feeds as separate layers). Artefaq collapses this hierarchy so the user only thinks about "my space with my documents".
Document Upload
Documents enter a space via direct upload. The user selects files and uploads them into a space — this is the primary (and initially only) way data enters the system.
Supported flows:
- Upload one or more files into an existing space
- Create a new space and upload files in one action
- Drag-and-drop onto a space
Automatic Background Processing
When an upload session completes, the platform automatically handles everything behind the scenes:
- Ingestion — documents are processed, chunked, and embedded
- Feed generation — feeds are created from the document content
- Agent setup — agents are configured for the space so the user can immediately start exploring
The user does not manually configure feeds, agents, or processing pipelines. They upload documents and start asking questions. The complexity is hidden.
Multiple Spaces
Users can create multiple spaces for different projects, topics, or contexts. Examples:
- "Q4 Financial Reports" — quarterly earnings documents
- "Product Research" — competitor analyses, market reports
- "Legal Review" — contracts and compliance documents
Each space is independent — its own documents, its own explorations, its own artefacts.
Open Questions
- Naming: is "space" the right term? Alternatives: workspace, project, collection, library, vault
- Default space: should there be a default space for new users, or must they create one before uploading?
- Space-level settings: what can be configured per space? (e.g. default agent behaviour, privacy, retention)
- Cross-space exploration: can the user explore across multiple spaces in a single conversation?
- Team sharing: how do spaces relate to teams? Can a space be shared with a team, or is it always personal?
- Space limits: are there limits on the number of spaces, documents per space, or total storage?
- Space lifecycle: what happens when a space is archived or deleted? What about its artefacts?
- Upload formats: which document types are supported at launch? (PDF, DOCX, TXT, CSV, etc.)