DOCUMENT FLOW / SYSTEM MAP

Aster Archive system map

Inspect how a document moves from intake to retrieval. Select components, change layers, trace the request path, and check the evidence behind each claim.

Explore mapView evidence

Map controls

  • Solid line: direct dependency
  • Dashed line: inferred relationship
  • Ring: selected node
  • V Verified · I Inferred (text badge on every node)

Select a component

Click or focus a node and press Enter to show its role, inputs, outputs, owner, citations, and open questions.

Confidence: Verified · Evidence: sample note, replace with the source citation

Select a component

Click or focus a node and press Enter to show its role, inputs, outputs, owner, citations, and open questions.

Change layers

Runtime and failure controls change visible nodes and edges while keeping their positions stable.

Trace a path

Highlight the document route from intake through indexing to retrieval; retain direction and edge labels.

Check evidence

Verified, inferred, warning, and unresolved claims each have a text label as well as a visual signal.

Selected component: Indexer

Role: build searchable records. Input: extracted text. Output: search index. Owner: Search Operations. Confidence: verified. Citation: architecture note AN-04, section 2. Open question: how long are failed jobs retained?

  • Incoming: Extractor to Indexer
  • Outgoing: Indexer to Search Store
  • Runtime path: Intake to Retrieval
  • Failure layer: retry queue

Document path

  1. Intake

    Receives the document and issues a stable job ID. Evidence: interface note IN-01.

  2. Extractor

    Produces text for indexing. The retry limit is inferred from a review note, not confirmed.

  3. Indexer

    Writes searchable records to Search Store. Evidence: architecture note AN-04.

  4. Retrieval

    Reads indexed records for an analyst query. Failure behavior remains unresolved.

Map inventory

8Components
12Directed relationships
2Available layers
3Open questions

Evidence register

IN-01

Intake · Verified · Interface note

AN-04

Indexer · Verified · Architecture note

RV-02

Retry queue · Inferred · Review note

UQ-03

Retrieval · Unresolved · No citation

Reading the map

What happens after document intake?

Follow the runtime path through extraction, indexing, Search Store, and analyst retrieval. Each edge shows its direction and relationship.

Which claims are confirmed?

The legend names every evidence state. Selecting a node shows its confidence, citation, and any unresolved question.

What changes in the failure layer?

The layer control reveals retry relationships and their evidence states without moving the core runtime components.