Learn

A precise operating vocabulary makes capital easier to govern.

Capital systems become ambiguous when the same words are used for observation, intention and outcome. Neptlium uses explicit state language so users can reason about what is known, what is proposed, what has been reviewed and what has actually become consequential.

These definitions describe the product model. They do not imply that every capability, provider or financial action is available in every environment.

Foundations

Ten concepts for keeping capital state legible.

01Capital context: The relationships that explain where capital stands, what role it serves, what constraints apply and which evidence supports the current view.
02Portfolio state: A representation of composition and related portfolio context at a point or period, with source and authority retained where known.
03Treasury context: Liquidity, reserves, funding requirements and readiness considered alongside the portfolio activity and obligations they support.
04Allocation intent: A proposed way to organize or position capital. Intent can be modeled and reviewed without becoming an instruction, authorization or outcome.
05Provider evidence: Information reported by an external provider or consequential system. Its provenance matters and should not be silently rewritten as another kind of state.
06Modeled state: A calculated, hypothetical or proposed representation used to reason about what may change. It is not evidence that capital has moved.
07Authoritative state: State supported by the system or evidence designated to establish that fact for the relevant operating purpose. Authority is contextual, not decorative.
08Review: The deliberate examination of evidence, assumptions, constraints and proposed work before an authorization boundary is crossed.
09Authorization: The identity, permission and policy boundary that permits a sensitive operation to proceed. Authorization does not itself prove execution or settlement.
10Financial consequence: A state in which an action has produced or is producing a real financial effect. Requested, approved, submitted, settled and reconciled remain different lifecycle states.

Working principle

Observed is not modeled. Proposed is not approved. Authorized is not settled.

The operating model is designed to preserve these distinctions because financial information becomes less trustworthy when lifecycle states inherit authority from one another without evidence.

Continue from vocabulary to system architecture.

Platform Products Trust

Explore the operating model

Apply the vocabulary to a real decision.

The point of precise financial language is practical: understanding what you have, what you intend to do and which facts are still missing.

Read liquidity and portfolio information together

Liquidity describes access to resources; a valuation describes an estimated or observed amount at a particular time. A valuable holding may be difficult to sell, and proceeds may not be immediately available. Consider both the source of value and the terms of access.

Trace a payment through its lifecycle

A request records intent. Approval permits the relevant next step. Submission sends an instruction. Later evidence may establish settlement, and reconciliation checks that records agree. A delay or timeout can leave the outcome unknown rather than failed.

Questions and next steps

Is diversification the same as holding many positions?: Not necessarily. Several positions can depend on similar risks. Consider the relationships between exposures rather than relying only on the number of holdings.
Are these definitions financial advice?: No. They are general educational explanations. Your objectives, circumstances and applicable professional advice matter when making a financial decision.