Point-in-time data

Arkolith stores historical filings and can compare reported periods. It does not yet keep a complete immutable record of what Arkolith knew and served at every moment. The first capital-change brief is therefore current-only, not historical replay.

Three different clocks#

Domain-event time: when the financial position or transaction applies.
Source-publication time: when the source accepted or published the filing. Arkolith stores the SEC's exact acceptance timestamp for 13F filings.
Arkolith observation time: when Arkolith first stored a particular artifact or derived state.

Current datasets contain parts of these clocks, but not a universal observation-time version history. A filing-period archive and an observation-time archive are not interchangeable.

13F source-publication replay#

fund.holdings.as_of returns the latest eligible quarter using only filings whose exact SEC acceptedAt is on or before your as_of. Same-day amendments become eligible only at their own acceptance time. The tool refuses the query if any eligible filing lacks that clock; it never substitutes the official date-only filing date.

bash

curl -X POST https://arkolith.com/api/mcp \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "fund.holdings.as_of",
    "arguments": {
      "cik": "1067983",
      "as_of": "2024-06-30"
    }
  }
}'

A date-only input such as 2024-06-30 means the end of that UTC day. A timestamp must include Z or an explicit UTC offset. The response exposes the normalized cutoff plus both the filing date and exact acceptance timestamp of known_filing.

Source-publication time is not Arkolith observation time

This prevents look-ahead across the SEC publication clock. It does not reconstruct when Arkolith first fetched, parsed, corrected, or served every derived value. The current-only capital-change brief still rejects as_of and since rather than implying that broader observation-time contract.

Position history#

fund.position.history gives the reported shares and USD value of one security across filing periods. It may reflect the currently effective amendment state. It is not a snapshot of what Arkolith knew on each date, and a position change does not by itself prove a trade or its timing.

bash

curl -X POST https://arkolith.com/api/mcp \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "fund.position.history",
    "arguments": {
      "cik": "1067983",
      "ticker": "AAPL"
    }
  }
}'

Change sets#

fund.holdings.diff returns a quarter-over-quarter comparison of current effective filings grouped into new, added, reduced, and exited. Amendments can revise an earlier period. A first tracked filing is only a baseline and cannot establish that every position was newly initiated.

Future observation-time contract#

The 13F helper enforces as_publicly_known_at for its single source using exact SEC acceptance time. A composed multi-source query must enforce the equivalent clock on every included leg. A separate as_available_in_arkolith_at query additionally requires immutable observation versions and an observation timestamp for every material input.

Observation-time replay will preserve source timestamp precision, resolve every material input through an evidence manifest, and pass no-future-leakage fixtures for every enabled source leg. These are future requirements, not claims about the current 13F helper.

← Previous

Provenance

Cross-source signals