Field Reference

Position Fields

This page separates source fields from derived fields. See Position Details for where they appear; this page only defines their meaning.

Source and linked fields

Field	Source	Meaning	Value or notes
`ID`	Generated by the system	The stable position identity.	It is a UUID v7 and is display-only. It is not the sequence in filenames such as `POS-00001.md`.
`Account`	Selected during creation, then derived by the system	The account used to create the position and scope Symbol choices.	It must match an existing account. After creation, the displayed value is resolved only through the current `Symbol`; legacy account fields on the position are ignored.
`Symbol`	Selected or entered by the user	The tradable instrument linked to the position.	It is stored as a link to a symbol file and determines Account, Type, Contract Unit, and the fee model.
`Side`	Selected during creation	The trade direction.	`LONG` or `SHORT`. It cannot be changed after creation.
`Status`	Initialized by the system and switchable by the user	Whether the position is open or closed.	A new position is `Open`. Saving a finite `Exit Price` sets `Close` but does not fill `Closed At`.
`Entry Price`	Entered by the user	The single entry price used by every amount and R:R formula.	It must be a valid positive number to produce an effective calculation quantity. There is no average-entry field.
`Exit Price`	Entered by the user	The actual exit price.	A finite number sets `Close`. Clearing it does not reopen the position automatically.
`Amount`	Entered by the user	Position size for crypto.	Enter a USD amount or switch to a `Native` asset quantity. Native mode needs a positive value and valid `Entry Price`.
`Contract`	Entered by the user	Number of contracts for a Future position.	An integer from 1 through 20.
`Lots`	Entered by the user	Number of lots for a CFD position.	0.01 through 20.
`Fee`	Derived by the system or entered manually	The absolute fee for this position.	It is calculated when the symbol fee model and size are valid. A manual value remains until a related source field changes.
`Opened At`	Initialized by the system and editable by the user	The position start time.	A new position uses the current timezone with second precision.
`Closed At`	Entered by the user	The position end time.	It can exist independently of `Status` and `Exit Price`. A nonempty value also makes the position count as closed.
`Confidence`	Entered by the user	A subjective score.	An integer from 1 through 5. It supports filters and does not enter profit formulas.
`Target Price`	Entered by the user	The planned exit price.	It must be above `Entry Price` for LONG and below it for SHORT.
`Stop Loss`	Entered by the user	The planned stop price.	It must be below `Entry Price` for LONG and above it for SHORT.
`Notes`	Entered by the user	Free-form content in the position body.	A new position body always starts with a `Notes` section. It is not a frontmatter field.
`Attachments`	Added by the user	Screenshot and other evidence files.	The position stores attachment links. Deleting a position directly does not clean up attachment files.
`Playbook`	Linked by the user	The Playbook used by this position.	It is stored as one link to a Playbook file.
`News`	Linked by the user	News context related to the position.	It is stored as a linked heading in the matching position-body section.
`Key Level`	Linked by the user	Key-level context related to the position.	It is stored as a linked heading in the matching position-body section.
`Confluence`	Linked by the user	A condition combination present in this trade.	Without a linked Playbook, only Public entries are available.
`Market Analysis`	Linked by the user	Market-analysis context related to the position.	It is stored as a linked heading in the matching position-body section.
`Analyses`	Aggregated by the system	The Positions-table summary of News, Key Level, Confluence, and Market Analysis.	It only displays linked results and is not a separately stored position field.

Derived fields

Direction is LONG = +1 and SHORT = -1. Effective quantity always means Notional Value ÷ Entry Price.

Field	Calculated from	Exact rule	Manually editable?
`Notional Value`	`Type`, size, `Entry Price`, and `Contract Unit`.	Crypto Native mode uses `Amount × Entry Price`; Future uses `Contract × Entry Price × Contract Unit`; CFD uses `Lots × Entry Price × Contract Unit`.	Yes. A later source-field change can derive it again.
`Net PnL` (shown as `Profit` in the Positions table)	`Entry Price`, `Exit Price`, direction, effective quantity, and `Fee`.	`(Exit Price - Entry Price) × direction × effective quantity - Fee`. Fee is subtracted once. A missing or invalid Fee is treated as 0.	Yes. A later source-field change can derive it again.
`Risk`	`Entry Price`, `Stop Loss`, direction, and effective quantity.	`(Entry Price - Stop Loss) × direction × effective quantity`. It must be above 0 and excludes Fee.	Read-only in the interface.
`Planned R:R`	Directional reward from `Target Price` to `Entry Price`, and Risk recalculated from the same source fields.	It does not use saved or manually entered `Risk` and excludes Fee. Planned reward must be above 0.	Read-only.
`Real R:R`	Directional move from `Exit Price` to `Entry Price`, and Risk recalculated from the same source fields.	It does not use saved `Net PnL` or `Risk` and excludes Fee. A loss remains negative.	Read-only.
`Duration`	`Opened At` and `Closed At`.	It shows the elapsed duration when both times are valid.	Read-only.

All derived amount values are rounded after the full calculation to at most eight decimal places. Absolute values below 0.00000001 become zero. Every profit, Risk, and R:R formula uses only Entry Price; there is no average-entry model.