KEY FINDINGS
- 01
Original sources, their identities and their versions are the basis for a reusable answer. Navigation helps an agent choose what to read; it is not evidence for the answer.
- 02
Importing material, indexing it and updating its navigation are separate operations. A saved file can still be queued, paused or unavailable to retrieval.
- 03
A project task can use its selected Spaces. Reads and edits keep those access boundaries and check revisions rather than assuming every visible file is authorized.
- 04
A useful citation identifies the source, its version and the portion actually read, so the next investigation can check the same material.
Continuity across investigations
A security investigation rarely ends with one conversation. An engineer returns to a request, revisits a design note and checks whether the code or policy has changed. A later task needs a useful starting point and a reliable route to its supporting material.
A previous answer alone cannot meet that need. It may be incomplete, its source may have changed, or the later task may have a different scope. Continuity depends on keeping the material identifiable and making another reading practical.
Oxo Operator currently approaches this through Spaces: selected material, original-source versions, navigation, local retrieval and bounded reads. This note examines how those pieces support a reviewable investigation and where they leave work to the agent and engineer.
Three records with different jobs
Conversation history preserves the course of a task. A navigation map describes what a space contains and what may be useful to read. An original source carries the content that an answer must be checked against. These records have different authority.
- Task history: what was asked, which actions were taken and which results were observed in that task.
- Space navigation: a bounded directory of sources and versions, optionally enriched with descriptions of their topics and reading purposes.
- Original material: retained source content, read with its identity, version and observed location.
A description can direct an agent to an authentication note. It does not establish that the authentication flow is secure. The agent still needs to read the original, inspect the application and explain which parts were verified.
Retrieval over original sources
Import processing extracts supported content and builds a local index. Search ranks original-source text and returns identities, versions, excerpts and line hints. The result gives the agent a specific place to begin reading and the engineer a location to revisit.
Search results are reading candidates. An excerpt can identify where to begin, but a result set is not a complete account of a space. Ranking, extraction limits and query terms affect what the agent sees.
- 01Save materialretain source identity
- 02Index locallycheck completion
- 03Navigate / searchchoose material
- 04Read originalbounded, versioned range
- 05Use evidenceverify the conclusion
Navigation that guides a reading
A collection becomes harder to use as it grows. A file name may say little about which question it can answer, and reading every document again consumes the attention the investigation needs. Navigation gives the agent a view of available material before it chooses a source.
Spaces keeps a navigation map alongside the sources. When the user chooses Generate navigation or Update navigation, a bounded model-assisted analysis describes file topics and reading purposes. Local indexing and search can be used independently; the analysis is an explicit action.
Navigation answers a practical question: which source should I read next? A topic description can point toward a session-design note, while the note itself supplies the details to compare with the observed request. Keeping that distinction visible lets a useful reading aid coexist with careful verification.
Source identity before interpretation
A file name alone is ambiguous. Two spaces may contain the same name, a document can be renamed and its content can change. Source tools carry a space-qualified identity and source version so another read can be tied to the material actually selected.
spaceId: space_auth
path: spaces/space_auth/sources/s_7f3a.md
sourceId: s_7f3a
name: session-boundary.md
version: 3
startLine: 12
endLine: 16
nextLine: 17
truncated: true
This example says which portion was read and that more remains. The answer can cite that range, explain how it bears on the investigation and continue reading when the surrounding context matters. The source location makes the interpretation checkable.
Locations and the limits of a read
Original-source reads return a bounded range, source version and completeness information. A response can indicate that more text remains, extraction was incomplete or a line was shortened. These conditions should remain visible in the explanation of what was checked.
For supported Office sources, tools also expose observed locations: Word paragraph indexes or Excel sheet and cell addresses. Extracted text lines, document paragraphs and spreadsheet cells are different coordinate systems. An answer should name the one it actually observed.
| Record | What a reviewer can check |
|---|---|
| Space and source identity | Which authorized material was used |
| Source version | Which revision the read refers to |
| Observed range or Office location | Where supporting content was read |
| Completeness and continuation | Whether more material remains outside that read |
Updating sources without hiding conflicts
A material update and a navigation update are separate events. Content edits retain original versions and schedule local reindexing when processing is enabled. Navigation may still need an update. Saving is not proof that either later operation completed.
Source editing uses the current source version and catalog revision; supported Office edits also check the original content hash. A version conflict requires another read. Supported text, Word and Excel operations have their own limits, and unsupported document features remain read-only.
An agent should resolve a conflict against the current returned state before continuing. It should then check what was saved and whether the index is ready, rather than assume that its earlier view remains current.
How a task uses its selected Spaces
A project task can use the Spaces selected for that project. A space conversation has its own scope. Navigation context is bounded, and the agent can request another map range or a specific original when the available context is insufficient.
The same scope follows tool operations. When several spaces are available, a single-space read or save needs an unambiguous destination. Access is checked around asynchronous work and before results are delivered. Removing a space or disabling retrieval must not silently leave its material available to that task.
A knowledge reference is not a filesystem path that grants access to an uploaded original. Source content and map text are reference data, including any instructions they happen to contain. The task's authorization continues to determine which actions may be taken.
What this design gains and leaves open
| Decision | Benefit | Remaining work |
|---|---|---|
| Keep originals and versions | Return to the material actually used | Interpret it for the current task |
| Rank source text locally | Find candidate passages in the retained material | Relevant sources may still be missed |
| Keep navigation separate | Descriptions guide reading without becoming evidence | Descriptions can lag behind edits |
| Bound each read | Returned material has an explicit range | Continue long reads and report coverage |
| Check revisions on edits | Reject stale writes | Reread and decide when conflicts occur |
A versioned citation lets a reviewer check the material used. The interpretation still needs to hold for the current question: a design note, for example, must be compared with what the application actually does.
Failures should remain visible
- Saved but queued, paused or failed: report processing status rather than claiming the source was indexed.
- No search match: distinguish that result from a claim that the space contains no relevant evidence.
- Truncated read: continue from the returned location or state what remains unread.
- Stale or pending navigation: inspect current source status; a map description does not determine whether the original is available.
- Edit conflict or changed access: reread within the current scope instead of reusing an old authorization assumption.
From retrieval to a checkable answer
In Spaces, Overview helps the engineer inspect processing status and navigation; Content provides access to the material. An investigation can move from that overview to a candidate source, read a versioned range and compare it with the request or code under review.
The task receives bounded navigation for its selected spaces and reads originals as needed. A useful answer then names the source and version, shows where the supporting content was read and explains how it supports the conclusion. Any unread range or pending source remains visible as a gap in that account.
Questions that still need evidence
- How often does source-text ranking return the material an engineer needs across different collections? This requires task-based retrieval evaluation.
- Does a generated reading map reduce navigation effort without encouraging trust in descriptions as facts? This needs comparison on real reading tasks.
- How clearly can an engineer see gaps caused by extraction, truncation or pending processing? A source version alone cannot answer that usability question.
- How do navigation quality and revision conflicts change over long projects?
A checkable starting point
A useful workspace gives the next task a route back to the material: which space, source, version and location. Navigation helps find that route; bounded reads supply evidence; the engineer checks the resulting judgment.
This is the current role of Spaces in Oxo Operator. The next note examines how an agent uses its context to perform security work, keep an execution record and prepare a finding a human can review.