> For the complete documentation index, see [llms.txt](https://docs.kpk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kpk.io/funds/infrastructure/architecture/onchain-accounting/concepts.md). # Concepts Cross-cutting models: position identity and the stale-price / sequencer reliability signals. Cross-cutting models that apply across the NAV Calculator, price feeds, and balance adapters: how positions are **identified** in a stable, machine-readable way, and how a reading signals that it is **unreliable** (stale prices, an unhealthy quote asset, or a down L2 sequencer).
Position identityThe 3-level protocol taxonomy, the positionId / positionKind / isLocked fields, decode schemas, and the reconciliation key.Position identity
Stale prices & sequencerStale-feed handling, the quote-asset fallback, and the L2 sequencer uptime check.Stale prices & sequencer
--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.kpk.io/funds/infrastructure/architecture/onchain-accounting/concepts.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.