This page documents what import coverage means on Portfolio Terminal, where the review boundary sits, and which failure cases still require user judgment.
It is written as a published operating note, not a marketing add-on. The point is to make the import model inspectable before anyone relies on it.
Summary
Broker guides
10 public pages
Input families
5
Review gate
Manual verification before write
Last updated
March 10, 2026
Scope
A broker guide is counted as covered when the route is public, the import flow is explained, and the expected source families are stated clearly enough for users to compare their export with the documented workflow.
File support refers to parser intake and review preparation. It does not imply that every row is automatically ready for a portfolio write without inspection.
The hub currently exposes 10 public broker pages. Each page carries broker-specific notes, tutorial steps, and routing back to the import hub.
Review boundary
The methodology is built around a review boundary. Parsing is allowed to be probabilistic. Writing to the portfolio is not.
Parse the source into candidate rows for symbols, quantities, prices, and dates.
Present the interpreted rows in a review interface before any write occurs.
Require the user to choose the import mode intentionally before apply.
Failure cases
Failure cases are not edge decoration. They are part of the operating note because they shape how users should interpret parser output in practice.
Guide index
A method note only matters if readers can inspect the public pages that sit behind the coverage claim.
Use the product