Documents in scope
Celsus is designed to work from explicit scope.
That means the legal team should be able to see which documents are in play for a run.
Why scope matters
Scope controls help with:
- confidentiality
- relevance
- cost control
- auditability
- reducing hallucinated or over-broad analysis
Recommended approach
Before running Celsus:
- confirm the current case
- confirm the relevant issue or thread
- confirm the selected documents
- confirm whether case memory should be included
- confirm whether authority sources are allowed
Case memory
Case memory is the durable structured record of important matter context.
It should capture things like:
- key facts
- issues
- parties
- timeline events
- draft positions
- unresolved questions
How to think about case memory
Case memory is not the same as raw chat history.
Use it as:
- a persistent matter record
- a way to preserve important context across runs
- a place to keep accepted, reviewable matter knowledge
Practical rule
If something should shape later work in the matter, it should not live only in a transient answer. It should be captured in the durable case workflow.
When to be cautious
Do not rely heavily on an answer when:
- the needed document was not in scope
- parsing failed
- the answer shows limitations or missing grounding
- the question depends on a jurisdiction or authority source that was not provided