Concepts
This page defines Torq terms before the manual uses them.
Torq is the credit facility operating system for tokenized assets. A facility is a bounded credit commitment with rules. In Torq, that relationship is represented by vault capital, markets as execution components, permissions, valuation data, exit state, recovery state, and post-write verification.
Relationship map
A Torq vault governs the line; an attached market lets a borrower draw
The bounded credit-line commitment and authority boundary.
The borrower-facing credit facility attached to vault capacity.
The borrower or market slice used to keep accounting local.
The role-specific screen that verifies the projected result.
A non-technical reader can think of Torq as a controlled facility desk: one team defines the facility, a borrower draws from it, valuation teams keep the data current, and the system only calls work complete after the shared records update.
Core mental model
System entities
Relationships between entities
- A vault defines the facility capital boundary.
- A market can be attached to the vault as the borrower execution component.
- A borrower route prepares the exact execution path for borrow and repay actions.
- Valuation data comes through NAV and Live-Feed paths.
- Permissions decide who can create, edit, approve, allocate, redeem, borrow, repay, liquidate, manage, or govern.
- The indexer and projectors update Postgres so every workspace sees the same persisted truth.
Glossary
Why these terms matter
Aave's public help docs describe users supplying assets into liquidity pools and borrowing against collateral. Morpho's Vault V2 docs describe curated vault strategies with adapters, caps, and separate roles. Torq uses some familiar DeFi words, but the operating center is different: Torq is organized around governed facility work, role-specific operating action paths, canonical indexed truth, and post-write verification.
The practical difference is control. In Torq, the important question is not only "is there liquidity in a pool?" or "which market receives vault assets?" It is also "who fields the facility, which borrower can draw, which valuation path is trusted, which permission applies, and when did the product verify the result?"
For reviewers
The active source evidence is the V2 route map in apps/web/src/app/router.tsx, page surface registry
in apps/web/config/pageSurfaceRegistry.json, function registry in
apps/web/config/functionRegistry.json, role catalogs in apps/web/config/roleFunctionCatalog.json
and apps/web/config/roleFieldCatalog.json, and active contract inventory in
protocol/contracts/security/manifests/torq-v2-active-contract-inventory.json.