An 6390/llm descriptions 3 (#860)

* gov descriptions

* marinade descriptions

* cleanup

models/descriptions/columns/account_sol.md

@@ -0,0 +1,10 @@
+{% docs account_sol %}
+
+The SOL assigned to this vote account. This field tracks the amount of SOL held by the vote account, enabling balance analysis and validator stake assessment.
+
+**Data type:** DECIMAL (SOL amount)
+**Business context:** Used to track vote account balances, analyze validator stake distribution, and assess account funding.
+**Analytics use cases:** Balance tracking, stake distribution analysis, and funding assessment.
+**Example:** 100.0, 1000.0, 5000.0
+
+{% enddocs %} 

models/descriptions/columns/activation_epoch.md

@@ -0,0 +1,10 @@
+{% docs activation_epoch %}
+
+The epoch when the stake was activated. This field tracks when the stake delegation became active and started earning rewards, enabling activation analysis and timeline tracking.
+
+**Data type:** INTEGER (epoch number)
+**Business context:** Used to track stake activation timing, analyze delegation patterns, and measure stake lifecycle.
+**Analytics use cases:** Activation timing tracking, delegation pattern analysis, and lifecycle measurement.
+**Example:** 123, 456, 789
+
+{% enddocs %} 

models/descriptions/columns/active_stake.md

@@ -0,0 +1,10 @@
+{% docs active_stake %}
+
+The active stake in SOL delegated to the validator. This field represents the total amount of SOL currently staked and actively participating in consensus for the validator.
+
+**Data type:** DECIMAL (SOL amount)
+**Business context:** Used to analyze validator stake distribution, delegation patterns, and network security assessment.
+**Analytics use cases:** Validator stake distribution analysis, delegation patterns, and network security assessment.
+**Example:** 1000000.0, 500000.0
+
+{% enddocs %} 

models/descriptions/columns/admin_warning.md

@@ -0,0 +1,10 @@
+{% docs admin_warning %}
+
+Admin warning for the validator. This field contains any administrative warnings or alerts associated with the validator, enabling validator health monitoring and issue tracking.
+
+**Data type:** STRING (warning message)
+**Business context:** Used to track validator issues, monitor validator health, and identify problematic validators.
+**Analytics use cases:** Issue tracking, health monitoring, and problematic validator identification.
+**Example:** 'High commission rate', 'Frequent delinquent periods', 'Low uptime'
+
+{% enddocs %} 

models/descriptions/columns/authorized_staker.md

@@ -0,0 +1,10 @@
+{% docs authorized_staker %}
+
+The account responsible for signing stake delegations and deactivations transactions. This field identifies who has control over the stake account's delegation decisions.
+
+**Data type:** STRING (Solana address)
+**Business context:** Used to track stake authorities, analyze delegation control, and assess staking security.
+**Analytics use cases:** Stake authority tracking, delegation control analysis, and staking security assessment.
+**Example:** '9WzDXwBbmkg8ZTbNMqUxvQRAyrZzDsGYdLVL9zYtAWWM'
+
+{% enddocs %} 

models/descriptions/columns/authorized_voter.md

@@ -0,0 +1,10 @@
+{% docs authorized_voter %}
+
+The account responsible for signing vote transactions. This field identifies who has authority to cast votes on behalf of the vote account in network consensus.
+
+**Data type:** STRING (Solana address)
+**Business context:** Used to track vote authorities, analyze validator voting patterns, and monitor consensus participation.
+**Analytics use cases:** Vote authority tracking, validator voting analysis, and consensus participation monitoring.
+**Example:** '9WzDXwBbmkg8ZTbNMqUxvQRAyrZzDsGYdLVL9zYtAWWM'
+
+{% enddocs %} 

models/descriptions/columns/authorized_withdrawer.md

@@ -0,0 +1,10 @@
+{% docs authorized_withdrawer %}
+
+The account responsible for signing stake withdrawal transactions. This field identifies who has authority to withdraw stake from the vote account.
+
+**Data type:** STRING (Solana address)
+**Business context:** Used to track withdrawal authorities, analyze vote account security, and monitor withdrawal patterns.
+**Analytics use cases:** Withdrawal authority tracking, vote account security analysis, and withdrawal pattern monitoring.
+**Example:** '9WzDXwBbmkg8ZTbNMqUxvQRAyrZzDsGYdLVL9zYtAWWM'
+
+{% enddocs %} 

models/descriptions/columns/avatar_url.md

@@ -0,0 +1,10 @@
+{% docs avatar_url %}
+
+URL of the validator's avatar image. This field provides a link to the validator's profile image, enabling visual identification and branding analysis.
+
+**Data type:** STRING (URL)
+**Business context:** Used for validator branding, visual identification, and user interface display.
+**Analytics use cases:** Branding analysis, visual identification, and UI display support.
+**Example:** 'https://example.com/avatar.png', 'https://keybase.io/avatar.jpg'
+
+{% enddocs %} 

models/descriptions/columns/claim_amount.md

@@ -0,0 +1,10 @@
+{% docs claim_amount %}
+
+The amount of SOL claimed from the liquid staking protocol. This field tracks the quantity of SOL withdrawn when users claim their staking rewards or unstake, enabling claim analysis and reward tracking.
+
+**Data type:** DECIMAL (SOL amount)
+**Business context:** Used to track claim amounts, analyze reward distributions, and measure unstaking activity.
+**Analytics use cases:** Claim tracking, reward analysis, and unstaking measurement.
+**Example:** 10.5, 105.0, 1050.0
+
+{% enddocs %} 

models/descriptions/columns/claim_amount_usd.md

@@ -0,0 +1,10 @@
+{% docs claim_amount_usd %}
+
+The amount of SOL claimed in USD value. This field provides the USD equivalent of the claimed SOL, enabling financial analysis and value-based metrics.
+
+**Data type:** DECIMAL (USD amount)
+**Business context:** Used to track claim values, analyze financial metrics, and measure reward distributions.
+**Analytics use cases:** Value tracking, financial analysis, and reward measurement.
+**Example:** 105.0, 1050.0, 10500.0
+
+{% enddocs %} 

models/descriptions/columns/commission.md

@@ -0,0 +1,10 @@
+{% docs commission %}
+
+The percentage of rewards payout to the vote account. This field represents the fee rate that the validator charges on staking rewards, expressed as a decimal percentage.
+
+**Data type:** DECIMAL (percentage as decimal)
+**Business context:** Used to analyze validator fee structures, model reward distributions, and study validator economics.
+**Analytics use cases:** Validator fee analysis, reward distribution modeling, and validator economics studies.
+**Example:** 0.05, 0.10, 0.00
+
+{% enddocs %} 

models/descriptions/columns/created_at.md

@@ -0,0 +1,10 @@
+{% docs created_at %}
+
+The date when the validator was created. This field tracks when the validator first joined the network, enabling validator lifecycle analysis and network growth tracking.
+
+**Data type:** TIMESTAMP (UTC)
+**Business context:** Used to track validator lifecycle, analyze network growth patterns, and assess validator experience.
+**Analytics use cases:** Lifecycle tracking, growth pattern analysis, and experience assessment.
+**Example:** '2023-01-15 10:30:00', '2022-06-20 14:45:30'
+
+{% enddocs %} 

models/descriptions/columns/credits_observed.md

@@ -0,0 +1,10 @@
+{% docs credits_observed %}
+
+Credits observed for the validator associated with this stake account. This field tracks the voting credits earned by the validator that this stake is delegated to, enabling performance analysis and reward tracking.
+
+**Data type:** INTEGER (credit count)
+**Business context:** Used to track validator performance, analyze credit accumulation, and measure stake delegation effectiveness.
+**Analytics use cases:** Performance tracking, credit accumulation analysis, and delegation effectiveness measurement.
+**Example:** 1000, 5000, 10000
+
+{% enddocs %} 

models/descriptions/columns/data_center_host.md

@@ -0,0 +1,10 @@
+{% docs data_center_host %}
+
+Host information for the data center where the validator is hosted. This field provides details about the hosting infrastructure, enabling infrastructure analysis and performance monitoring.
+
+**Data type:** STRING (host information)
+**Business context:** Used to track hosting infrastructure, analyze performance patterns, and monitor data center health.
+**Analytics use cases:** Infrastructure tracking, performance analysis, and health monitoring.
+**Example:** 'aws.amazon.com', 'google.com', 'microsoft.com'
+
+{% enddocs %} 

models/descriptions/columns/data_center_key.md

@@ -0,0 +1,10 @@
+{% docs data_center_key %}
+
+Identifier for the data center where the validator is hosted. This field tracks the specific data center location, enabling geographic analysis and infrastructure monitoring.
+
+**Data type:** STRING (data center identifier)
+**Business context:** Used to track validator infrastructure, analyze geographic distribution, and monitor data center performance.
+**Analytics use cases:** Infrastructure tracking, geographic analysis, and performance monitoring.
+**Example:** 'DC1', 'AWS_US_EAST_1', 'GCP_US_CENTRAL_1'
+
+{% enddocs %} 

models/descriptions/columns/deactivation_epoch.md

@@ -0,0 +1,10 @@
+{% docs deactivation_epoch %}
+
+The epoch when the stake will be deactivated. This field tracks when the stake delegation will become inactive and stop earning rewards, enabling deactivation planning and timeline analysis.
+
+**Data type:** INTEGER (epoch number)
+**Business context:** Used to track stake deactivation timing, analyze delegation patterns, and plan for stake lifecycle changes.
+**Analytics use cases:** Deactivation timing tracking, delegation pattern analysis, and lifecycle planning.
+**Example:** 123, 456, 789
+
+{% enddocs %} 

models/descriptions/columns/delinquent.md

@@ -0,0 +1,10 @@
+{% docs delinquent %}
+
+A boolean flag indicating whether the validator is offline or delinquent. This field tracks the operational status of validators, enabling network health monitoring and reliability analysis.
+
+**Data type:** BOOLEAN (TRUE/FALSE)
+**Business context:** Used to monitor network health, analyze validator reliability, and track uptime performance.
+**Analytics use cases:** Network health monitoring, validator reliability analysis, and uptime tracking.
+**Example:** TRUE, FALSE
+
+{% enddocs %} 

models/descriptions/columns/deposit_amount.md

@@ -0,0 +1,10 @@
+{% docs deposit_amount %}
+
+The amount of SOL deposited into the liquid staking protocol. This field tracks the quantity of SOL being staked through Marinade Finance, enabling deposit analysis and staking volume measurement.
+
+**Data type:** DECIMAL (SOL amount)
+**Business context:** Used to track staking deposits, analyze staking volume patterns, and measure protocol usage.
+**Analytics use cases:** Deposit tracking, volume pattern analysis, and usage measurement.
+**Example:** 10.0, 100.0, 1000.0
+
+{% enddocs %} 

models/descriptions/columns/deposit_amount_usd.md

@@ -0,0 +1,10 @@
+{% docs deposit_amount_usd %}
+
+The amount of SOL deposited in USD value. This field provides the USD equivalent of the deposited SOL, enabling financial analysis and value-based metrics.
+
+**Data type:** DECIMAL (USD amount)
+**Business context:** Used to track deposit values, analyze financial metrics, and measure protocol TVL impact.
+**Analytics use cases:** Value tracking, financial analysis, and TVL impact measurement.
+**Example:** 100.0, 1000.0, 10000.0
+
+{% enddocs %} 

models/descriptions/columns/details.md

@@ -0,0 +1,10 @@
+{% docs details %}
+
+Additional details for the validator. This field contains supplementary information about the validator, enabling comprehensive validator analysis and metadata tracking.
+
+**Data type:** STRING (details text)
+**Business context:** Used to store additional validator information, track metadata, and provide comprehensive validator context.
+**Analytics use cases:** Metadata tracking, comprehensive analysis, and context provision.
+**Example:** 'Professional validator with 99.9% uptime', 'Community validator focused on decentralization'
+
+{% enddocs %} 

models/descriptions/columns/dex_platform.md

@@ -0,0 +1,10 @@
+{% docs dex_platform %}
+
+Name of the decentralized exchange used to perform the swap. This field identifies the specific DEX or aggregator platform that facilitated the swap, enabling cross-platform analysis and platform-specific comparisons.
+
+**Data type:** STRING (platform name)
+**Business context:** Used to categorize swaps by platform, analyze cross-platform trading patterns, and compare platform performance.
+**Analytics use cases:** Platform categorization, cross-platform analysis, and performance comparison.
+**Example:** 'Jupiter', 'Raydium', 'Orca', 'Meteora'
+
+{% enddocs %} 

models/descriptions/columns/end_slot.md

@@ -0,0 +1,10 @@
+{% docs end_slot %}
+
+The final slot of the epoch. This field identifies the ending slot number for the epoch, enabling epoch boundary tracking and time-based analysis.
+
+**Data type:** INTEGER (slot number)
+**Business context:** Used to track epoch boundaries, analyze time-based patterns, and provide epoch context for block production data.
+**Analytics use cases:** Epoch boundary tracking, time-based analysis, and epoch context provision.
+**Example:** 123456789, 123456800
+
+{% enddocs %} 

models/descriptions/columns/epoch_active.md

@@ -0,0 +1,10 @@
+{% docs epoch_active %}
+
+The last epoch when the vote account was active. This field tracks the most recent epoch in which the validator's vote account participated in consensus voting, enabling activity analysis and validator health assessment.
+
+**Data type:** INTEGER (epoch number)
+**Business context:** Used to track validator activity, analyze participation patterns, and assess validator health and reliability.
+**Analytics use cases:** Activity tracking, participation analysis, and health assessment.
+**Example:** 123, 456, 789
+
+{% enddocs %} 

models/descriptions/columns/epoch_credits.md

@@ -0,0 +1,10 @@
+{% docs epoch_credits %}
+
+Credits earned by the end of epochs, containing epoch/credits/previous credits. This field tracks the cumulative voting credits earned by the vote account across epochs, enabling validator performance analysis and reward calculation.
+
+**Data type:** STRING (credits data)
+**Business context:** Used to track validator voting performance, analyze credit accumulation patterns, and calculate voting rewards.
+**Analytics use cases:** Validator performance analysis, credit accumulation tracking, and voting reward calculation.
+**Example:** "123/1000/500", "456/1500/1000"
+
+{% enddocs %} 

models/descriptions/columns/governance_platform.md

@@ -0,0 +1,10 @@
+{% docs governance_platform %}
+
+The platform used for governance space and voting mechanisms. This field identifies which governance platform hosted the voting activity, enabling cross-platform analysis and platform adoption tracking.
+
+**Data type:** STRING (platform identifier)
+**Business context:** Used to identify governance platforms and analyze cross-platform governance patterns and tool adoption.
+**Analytics use cases:** Platform adoption analysis, cross-platform governance comparison, and governance tool effectiveness studies.
+**Example:** 'realms', 'tribeca'
+
+{% enddocs %} 

models/descriptions/columns/is_mnde_pool.md

@@ -0,0 +1,10 @@
+{% docs is_mnde_pool %}
+
+Whether the pool has MNDE as one of the tokens. This field indicates if the liquidity pool contains Marinade Finance governance token (MNDE) as a trading pair, enabling MNDE-specific pool filtering and analysis.
+
+**Data type:** BOOLEAN (true/false)
+**Business context:** Used to filter MNDE-related pools, analyze MNDE liquidity distribution, and track MNDE trading opportunities.
+**Analytics use cases:** MNDE pool filtering, liquidity distribution analysis, and trading opportunity tracking.
+**Example:** true, false
+
+{% enddocs %} 

models/descriptions/columns/is_msol_pool.md

@@ -0,0 +1,10 @@
+{% docs is_msol_pool %}
+
+Whether the pool has MSOL as one of the tokens. This field indicates if the liquidity pool contains Marinade Staked SOL (MSOL) as a trading pair, enabling MSOL-specific pool filtering and analysis.
+
+**Data type:** BOOLEAN (true/false)
+**Business context:** Used to filter MSOL-related pools, analyze MSOL liquidity distribution, and track MSOL trading opportunities.
+**Analytics use cases:** MSOL pool filtering, liquidity distribution analysis, and trading opportunity tracking.
+**Example:** true, false
+
+{% enddocs %} 

models/descriptions/columns/is_using_marinade_native_staking.md

@@ -0,0 +1,10 @@
+{% docs is_using_marinade_native_staking %}
+
+Whether the staking action is using Marinade Native Staking. This field indicates if the staking activity is routed through Marinade's native staking proxy service, enabling proxy service usage analysis.
+
+**Data type:** BOOLEAN (true/false)
+**Business context:** Used to track Marinade proxy service usage, analyze proxy adoption patterns, and measure service utilization.
+**Analytics use cases:** Usage tracking, adoption analysis, and utilization measurement.
+**Example:** true, false
+
+{% enddocs %} 

models/descriptions/columns/keybase_id.md

@@ -0,0 +1,10 @@
+{% docs keybase_id %}
+
+Keybase ID for the validator. This field provides the validator's Keybase identity, enabling social verification and community engagement analysis.
+
+**Data type:** STRING (Keybase username)
+**Business context:** Used for social verification, community engagement tracking, and validator identity verification.
+**Analytics use cases:** Social verification, engagement tracking, and identity verification.
+**Example:** 'validator_name', 'solana_validator', 'community_node'
+
+{% enddocs %} 

models/descriptions/columns/last_epoch_active.md

@@ -0,0 +1,10 @@
+{% docs last_epoch_active %}
+
+The last epoch when the vote account was active. This field tracks the most recent epoch in which the vote account participated in consensus voting, enabling activity analysis and validator health assessment.
+
+**Data type:** INTEGER (epoch number)
+**Business context:** Used to track vote account activity, analyze validator participation patterns, and assess validator health and reliability.
+**Analytics use cases:** Vote account activity tracking, validator participation analysis, and health assessment.
+**Example:** 123, 456, 789
+
+{% enddocs %} 

models/descriptions/columns/last_timestamp.md

@@ -0,0 +1,10 @@
+{% docs last_timestamp %}
+
+The timestamp when the last slot was voted on. This field captures the exact time when the vote account last participated in consensus voting, enabling temporal analysis and activity tracking.
+
+**Data type:** TIMESTAMP (UTC)
+**Business context:** Used to track vote account activity timing, analyze voting frequency patterns, and assess validator reliability over time.
+**Analytics use cases:** Activity timing analysis, voting frequency tracking, and reliability assessment.
+**Example:** '2024-01-15 10:30:00', '2024-01-15 14:45:30'
+
+{% enddocs %} 

models/descriptions/columns/last_timestamp_slot.md

@@ -0,0 +1,10 @@
+{% docs last_timestamp_slot %}
+
+The last slot voted on by the vote account. This field tracks the most recent slot number where the vote account participated in consensus voting, enabling activity tracking and performance analysis.
+
+**Data type:** INTEGER (slot number)
+**Business context:** Used to track vote account activity, analyze voting patterns, and assess validator participation in consensus.
+**Analytics use cases:** Vote account activity tracking, voting pattern analysis, and consensus participation assessment.
+**Example:** 123456789, 123456800
+
+{% enddocs %} 

models/descriptions/columns/latitude.md

@@ -0,0 +1,10 @@
+{% docs latitude %}
+
+Latitude coordinates of the data center where the validator is hosted. This field provides geographic location data, enabling geographic analysis and infrastructure distribution studies.
+
+**Data type:** DECIMAL (latitude degrees)
+**Business context:** Used to track geographic distribution, analyze infrastructure patterns, and study validator clustering.
+**Analytics use cases:** Geographic analysis, infrastructure pattern study, and clustering analysis.
+**Example:** 40.7128, 34.0522, 51.5074
+
+{% enddocs %} 

models/descriptions/columns/lockup.md

@@ -0,0 +1,10 @@
+{% docs lockup %}
+
+Lockup information specifying when tokens can be withdrawn from the stake account. This field contains the lockup conditions including epoch, timestamp, and custodian restrictions, enabling withdrawal analysis and lockup tracking.
+
+**Data type:** OBJECT (lockup data)
+**Business context:** Used to track withdrawal restrictions, analyze lockup conditions, and monitor stake account liquidity.
+**Analytics use cases:** Withdrawal restriction tracking, lockup condition analysis, and liquidity monitoring.
+**Example:** {'epoch': 123, 'unix_timestamp': 1642233600, 'custodian': 'CustodianAddress'}
+
+{% enddocs %} 

models/descriptions/columns/longitude.md

@@ -0,0 +1,10 @@
+{% docs longitude %}
+
+Longitude coordinates of the data center where the validator is hosted. This field provides geographic location data, enabling geographic analysis and infrastructure distribution studies.
+
+**Data type:** DECIMAL (longitude degrees)
+**Business context:** Used to track geographic distribution, analyze infrastructure patterns, and study validator clustering.
+**Analytics use cases:** Geographic analysis, infrastructure pattern study, and clustering analysis.
+**Example:** -74.0060, -118.2437, -0.1278
+
+{% enddocs %} 

models/descriptions/columns/move_amount.md

@@ -0,0 +1,10 @@
+{% docs move_amount %}
+
+The amount of SOL being moved from the stake account. This field captures the quantity of SOL involved in the staking action, enabling transaction value analysis and movement tracking.
+
+**Data type:** DECIMAL (SOL amount)
+**Business context:** Used to track SOL movements, analyze transaction values, and measure staking activity volume.
+**Analytics use cases:** Transaction value analysis, movement tracking, and staking activity volume measurement.
+**Example:** 50.0, 100.0
+
+{% enddocs %} 

models/descriptions/columns/move_destination.md

@@ -0,0 +1,10 @@
+{% docs move_destination %}
+
+The destination wallet address of the moved SOL. This field identifies where the SOL was transferred to during the staking action, enabling movement tracking and destination analysis.
+
+**Data type:** STRING (Solana address)
+**Business context:** Used to track SOL movement destinations, analyze transfer patterns, and identify stake recipients.
+**Analytics use cases:** Movement destination tracking, transfer pattern analysis, and stake recipient identification.
+**Example:** '9WzDXwBbmkg8ZTbNMqUxvQRAyrZzDsGYdLVL9zYtAWWM'
+
+{% enddocs %} 

models/descriptions/columns/msol_burned.md

@@ -0,0 +1,10 @@
+{% docs msol_burned %}
+
+The amount of MSOL (Marinade Staked SOL) burned. This field tracks the quantity of MSOL tokens destroyed when users unstake or claim rewards, enabling MSOL supply analysis.
+
+**Data type:** DECIMAL (MSOL amount)
+**Business context:** Used to track MSOL burning, analyze supply reduction, and measure unstaking activity.
+**Analytics use cases:** Burning tracking, supply analysis, and unstaking activity measurement.
+**Example:** 9.95, 99.5, 995.0
+
+{% enddocs %} 

models/descriptions/columns/msol_minted.md

@@ -0,0 +1,10 @@
+{% docs msol_minted %}
+
+The amount of MSOL (Marinade Staked SOL) minted. This field tracks the quantity of MSOL tokens created when SOL is deposited into the liquid staking protocol, enabling MSOL supply analysis.
+
+**Data type:** DECIMAL (MSOL amount)
+**Business context:** Used to track MSOL minting, analyze supply growth, and measure staking efficiency.
+**Analytics use cases:** Minting tracking, supply analysis, and efficiency measurement.
+**Example:** 9.95, 99.5, 995.0
+
+{% enddocs %} 

models/descriptions/columns/native_staking_platform.md

@@ -0,0 +1,10 @@
+{% docs native_staking_platform %}
+
+The platform of the staking account, either native or marinade native proxy. This field identifies whether the staking action is using direct native staking or Marinade's native staking proxy service, enabling platform-specific analysis.
+
+**Data type:** STRING (platform type)
+**Business context:** Used to categorize staking methods, analyze platform usage patterns, and compare native vs proxy staking.
+**Analytics use cases:** Platform categorization, usage pattern analysis, and method comparison.
+**Example:** 'native', 'marinade native proxy'
+
+{% enddocs %} 

models/descriptions/columns/node_pubkey.md

@@ -0,0 +1,10 @@
+{% docs node_pubkey %}
+
+The account for the validator node on the Solana network. This field identifies the specific validator that participates in network consensus and receives stake delegations.
+
+**Data type:** STRING (Solana address)
+**Business context:** Used to identify validators, track performance, and analyze stake delegation patterns.
+**Analytics use cases:** Validator identification, performance tracking, and stake delegation analysis.
+**Example:** '9WzDXwBbmkg8ZTbNMqUxvQRAyrZzDsGYdLVL9zYtAWWM'
+
+{% enddocs %} 

models/descriptions/columns/num_blocks_produced.md

@@ -0,0 +1,10 @@
+{% docs num_blocks_produced %}
+
+The number of blocks the validator produced in the epoch. This field tracks the actual blocks created by the validator when it was the slot leader, enabling block production analysis and validator efficiency measurement.
+
+**Data type:** INTEGER (block count)
+**Business context:** Used to analyze validator block production efficiency, track network performance, and measure validator reliability.
+**Analytics use cases:** Block production analysis, network performance tracking, and validator efficiency measurement.
+**Example:** 8, 45, 95
+
+{% enddocs %} 

models/descriptions/columns/num_leader_slots.md

@@ -0,0 +1,10 @@
+{% docs num_leader_slots %}
+
+The number of slots the validator was the leader for in the epoch. This field tracks how many times the validator was selected as the slot leader, enabling validator performance analysis and network participation measurement.
+
+**Data type:** INTEGER (slot count)
+**Business context:** Used to analyze validator performance, track network participation, and measure validator reliability.
+**Analytics use cases:** Validator performance analysis, network participation tracking, and reliability measurement.
+**Example:** 10, 50, 100
+
+{% enddocs %} 

models/descriptions/columns/num_votes.md

@@ -0,0 +1,10 @@
+{% docs num_votes %}
+
+The number of vote events that occurred within the block. This field tracks the count of voting transactions processed in a specific block, enabling consensus participation analysis and block-level voting activity measurement.
+
+**Data type:** INTEGER (vote count)
+**Business context:** Used to analyze consensus participation patterns, track voting activity by block, and measure network consensus health.
+**Analytics use cases:** Consensus participation analysis, voting activity tracking, and network consensus health measurement.
+**Example:** 5, 10, 20
+
+{% enddocs %} 

models/descriptions/columns/platform.md

@@ -0,0 +1,10 @@
+{% docs platform %}
+
+Name of the liquidity pool protocol or platform. This field identifies the DeFi protocol that hosts the liquidity pool, enabling cross-protocol analysis and platform-specific comparisons.
+
+**Data type:** STRING (platform name)
+**Business context:** Used to categorize pools by protocol, analyze cross-platform liquidity distribution, and compare platform performance.
+**Analytics use cases:** Platform categorization, cross-protocol analysis, and performance comparison.
+**Example:** 'raydium', 'orca', 'meteora'
+
+{% enddocs %} 

models/descriptions/columns/pool_name.md

@@ -0,0 +1,10 @@
+{% docs pool_name %}
+
+The name of the liquidity pool, typically formatted as a token pair (e.g., "MSOL-USDC"). This field provides a human-readable identifier for the pool, enabling easy identification and analysis of specific liquidity pools.
+
+**Data type:** STRING (pool name)
+**Business context:** Used to identify liquidity pools, analyze pool naming patterns, and provide user-friendly pool references.
+**Analytics use cases:** Pool identification, naming pattern analysis, and user interface display.
+**Example:** 'MSOL-USDC', 'MNDE-SOL', 'MSOL-RAY'
+
+{% enddocs %} 

models/descriptions/columns/post_balances.md

@@ -1,3 +1,10 @@
 {% docs post_balances %}
-An array of lamport balances for each account in 'account_keys' after the transaction is executed. The order matches the 'account_keys' array. Used to track balance changes and verify transaction effects. Value is in lamports (1 SOL = 1,000,000,000 lamports).
+
+List of post-transaction balances for different accounts. This field captures the SOL balances of all accounts involved in the transaction after execution, enabling balance change analysis and transaction impact measurement.
+
+**Data type:** ARRAY (SOL amounts)
+**Business context:** Used to track balance changes, analyze transaction impact, and measure SOL movement between accounts.
+**Analytics use cases:** Balance change analysis, transaction impact measurement, and SOL movement tracking.
+**Example:** [95.0, 55.0, 25.0]
+
 {% enddocs %} 

models/descriptions/columns/post_token_balances.md

@@ -1,3 +1,10 @@
 {% docs post_token_balances %}
-An array of SPL token balances for each token account involved in the transaction, after execution. Each entry includes the token account address, mint, and raw amount. Used to track token transfers and verify effects. See: https://spl.solana.com/token
+
+List of post-transaction token balances for different token accounts. This field captures the token balances of all token accounts involved in the transaction after execution, enabling token balance change analysis.
+
+**Data type:** ARRAY (token balance objects)
+**Business context:** Used to track token balance changes, analyze token movements, and measure token transaction impact.
+**Analytics use cases:** Token balance change analysis, token movement tracking, and token transaction impact measurement.
+**Example:** [{'mint': 'TokenMintAddress', 'amount': 900}, {'mint': 'AnotherToken', 'amount': 600}]
+
 {% enddocs %} 

models/descriptions/columns/post_tx_staked_balance.md

@@ -0,0 +1,10 @@
+{% docs post_tx_staked_balance %}
+
+The amount of Solana belonging to the stake account after the transaction. This field captures the stake balance following the staking action, enabling balance change analysis and transaction impact measurement.
+
+**Data type:** DECIMAL (SOL amount)
+**Business context:** Used to track stake balance changes, analyze transaction impact, and measure staking activity.
+**Analytics use cases:** Balance change analysis, transaction impact measurement, and staking activity tracking.
+**Example:** 100.0, 1000.0
+
+{% enddocs %} 

models/descriptions/columns/post_tx_staked_balance_usd.md

@@ -0,0 +1,10 @@
+{% docs post_tx_staked_balance_usd %}
+
+The amount of SOL belonging to the stake account after the transaction in USD value. This field provides the USD equivalent of the post-transaction stake balance, enabling financial analysis and value-based metrics.
+
+**Data type:** DECIMAL (USD amount)
+**Business context:** Used to track post-transaction values, analyze financial metrics, and measure balance changes in USD terms.
+**Analytics use cases:** Value tracking, financial analysis, and USD-based balance measurement.
+**Example:** 95.0, 1050.0, 10050.0
+
+{% enddocs %} 

models/descriptions/columns/pre_balances.md

@@ -1,3 +1,10 @@
 {% docs pre_balances %}
-An array of lamport balances for each account in 'account_keys' before the transaction is executed. The order matches the 'account_keys' array. Used to track balance changes and verify transaction effects. Value is in lamports (1 SOL = 1,000,000,000 lamports).
+
+List of pre-transaction balances for different accounts. This field captures the SOL balances of all accounts involved in the transaction before execution, enabling balance change analysis and transaction impact measurement.
+
+**Data type:** ARRAY (SOL amounts)
+**Business context:** Used to track balance changes, analyze transaction impact, and measure SOL movement between accounts.
+**Analytics use cases:** Balance change analysis, transaction impact measurement, and SOL movement tracking.
+**Example:** [100.0, 50.0, 25.0]
+
 {% enddocs %} 

models/descriptions/columns/pre_token_balances.md

@@ -1,3 +1,10 @@
 {% docs pre_token_balances %}
-An array of SPL token balances for each token account involved in the transaction, before execution. Each entry includes the token account address, mint, and raw amount. Used to track token transfers and verify effects. See: https://spl.solana.com/token
+
+List of pre-transaction token balances for different token accounts. This field captures the token balances of all token accounts involved in the transaction before execution, enabling token balance change analysis.
+
+**Data type:** ARRAY (token balance objects)
+**Business context:** Used to track token balance changes, analyze token movements, and measure token transaction impact.
+**Analytics use cases:** Token balance change analysis, token movement tracking, and token transaction impact measurement.
+**Example:** [{'mint': 'TokenMintAddress', 'amount': 1000}, {'mint': 'AnotherToken', 'amount': 500}]
+
 {% enddocs %} 

models/descriptions/columns/pre_tx_staked_balance.md

@@ -0,0 +1,10 @@
+{% docs pre_tx_staked_balance %}
+
+The amount of Solana belonging to the stake account before the transaction. This field captures the stake balance prior to the staking action, enabling balance change analysis and transaction impact measurement.
+
+**Data type:** DECIMAL (SOL amount)
+**Business context:** Used to track stake balance changes, analyze transaction impact, and measure staking activity.
+**Analytics use cases:** Balance change analysis, transaction impact measurement, and staking activity tracking.
+**Example:** 100.0, 1000.0
+
+{% enddocs %} 

models/descriptions/columns/pre_tx_staked_balance_usd.md

@@ -0,0 +1,10 @@
+{% docs pre_tx_staked_balance_usd %}
+
+The amount of SOL belonging to the stake account before the transaction in USD value. This field provides the USD equivalent of the pre-transaction stake balance, enabling financial analysis and value-based metrics.
+
+**Data type:** DECIMAL (USD amount)
+**Business context:** Used to track pre-transaction values, analyze financial metrics, and measure balance changes in USD terms.
+**Analytics use cases:** Value tracking, financial analysis, and USD-based balance measurement.
+**Example:** 100.0, 1000.0, 10000.0
+
+{% enddocs %} 

models/descriptions/columns/prior_voters.md

@@ -0,0 +1,10 @@
+{% docs prior_voters %}
+
+Prior voters for the vote account. This field tracks the historical list of voters that have been associated with this vote account, enabling voter history analysis and account ownership tracking.
+
+**Data type:** ARRAY (voter addresses)
+**Business context:** Used to track vote account ownership history, analyze voter transitions, and understand account control changes.
+**Analytics use cases:** Ownership history tracking, voter transition analysis, and account control change monitoring.
+**Example:** ['PreviousVoter1', 'PreviousVoter2'], ['OldVoterAddress']
+
+{% enddocs %} 

models/descriptions/columns/program.md

@@ -0,0 +1,10 @@
+{% docs program %}
+
+The type of account program that owns this stake account. This field identifies the Solana program that has authority over the stake account, enabling ownership analysis and program relationship tracking.
+
+**Data type:** STRING (program address)
+**Business context:** Used to track stake account ownership, analyze program relationships, and understand account control structures.
+**Analytics use cases:** Ownership tracking, program relationship analysis, and control structure understanding.
+**Example:** 'Stake111111111111111111111111111111111111111111'
+
+{% enddocs %} 

models/descriptions/columns/program_name.md

@@ -0,0 +1,10 @@
+{% docs program_name %}
+
+The name of the Solana program that processed the governance action or transaction. This field identifies which specific governance protocol or program handled the action, enabling cross-program analysis and protocol-specific filtering.
+
+**Data type:** STRING (program identifier)
+**Business context:** Used to identify governance programs and analyze cross-protocol governance patterns and adoption.
+**Analytics use cases:** Program usage analysis, cross-protocol governance comparison, and governance tool adoption tracking.
+**Example:** 'marinade', 'saber', 'realms'
+
+{% enddocs %} 

models/descriptions/columns/proposal.md

@@ -0,0 +1,10 @@
+{% docs proposal %}
+
+Address representing the proposal being voted on. This field identifies the specific proposal within the governance system, enabling proposal tracking and governance activity analysis.
+
+**Data type:** STRING (proposal address)
+**Business context:** Used to track individual proposals, analyze proposal lifecycle, and monitor governance activity.
+**Analytics use cases:** Proposal tracking, lifecycle analysis, and governance activity monitoring.
+**Example:** '9WzDXwBbmkg8ZTbNMqUxvQRAyrZzDsGYdLVL9zYtAWWM'
+
+{% enddocs %} 

models/descriptions/columns/proposal_name.md

@@ -0,0 +1,10 @@
+{% docs proposal_name %}
+
+The name of the proposal that is being submitted. This field contains the human-readable title or name of the governance proposal, enabling proposal identification and content analysis.
+
+**Data type:** STRING (proposal name)
+**Business context:** Used to identify proposals, analyze proposal content themes, and categorize governance topics.
+**Analytics use cases:** Proposal identification, content theme analysis, and topic categorization.
+**Example:** 'Increase Treasury Allocation', 'Update Protocol Parameters', 'Community Grant Proposal'
+
+{% enddocs %} 

models/descriptions/columns/proposal_writer.md

@@ -0,0 +1,10 @@
+{% docs proposal_writer %}
+
+Address of the user who is submitting the proposal for voting. This field identifies the creator of the governance proposal, enabling creator analysis and proposal attribution tracking.
+
+**Data type:** STRING (user address)
+**Business context:** Used to track proposal creators, analyze creator patterns, and attribute governance activity to specific users.
+**Analytics use cases:** Creator tracking, pattern analysis, and activity attribution.
+**Example:** '9WzDXwBbmkg8ZTbNMqUxvQRAyrZzDsGYdLVL9zYtAWWM'
+
+{% enddocs %} 

models/descriptions/columns/realms_id.md

@@ -0,0 +1,10 @@
+{% docs realms_id %}
+
+An address that is unique to the space or voting group on Realms. This field identifies the specific governance space within the Realms platform where the proposal is being created, enabling governance space analysis and proposal categorization.
+
+**Data type:** STRING (Realms address)
+**Business context:** Used to track governance spaces, analyze proposal distribution across spaces, and categorize governance activity.
+**Analytics use cases:** Governance space tracking, proposal distribution analysis, and activity categorization.
+**Example:** '9WzDXwBbmkg8ZTbNMqUxvQRAyrZzDsGYdLVL9zYtAWWM'
+
+{% enddocs %} 

models/descriptions/columns/rent_epoch.md

@@ -0,0 +1,10 @@
+{% docs rent_epoch %}
+
+The epoch at which this account will next owe rent. This field tracks when the vote account will be charged rent for storage, enabling rent management analysis and account maintenance planning.
+
+**Data type:** INTEGER (epoch number)
+**Business context:** Used to track rent obligations, analyze account maintenance costs, and plan for rent payments.
+**Analytics use cases:** Rent obligation tracking, maintenance cost analysis, and payment planning.
+**Example:** 123, 456, 789
+
+{% enddocs %} 

models/descriptions/columns/rent_exempt_reserve.md

@@ -0,0 +1,10 @@
+{% docs rent_exempt_reserve %}
+
+The minimum SOL balance that must be maintained for this account to remain rent exempt. This field tracks the required SOL amount to avoid rent charges, enabling cost analysis and account maintenance planning.
+
+**Data type:** DECIMAL (SOL amount)
+**Business context:** Used to track rent exemption requirements, analyze account maintenance costs, and plan for rent payments.
+**Analytics use cases:** Rent exemption tracking, maintenance cost analysis, and payment planning.
+**Example:** 0.00203928, 0.00144768
+
+{% enddocs %} 

models/descriptions/columns/reward_recipient_pubkey.md

@@ -0,0 +1,10 @@
+{% docs reward_recipient_pubkey %}
+
+The address receiving the fee rewards. This field identifies the account that received the fee reward, enabling reward distribution analysis and recipient tracking.
+
+**Data type:** STRING (Solana address)
+**Business context:** Used to track reward recipients, analyze reward distribution patterns, and identify fee reward beneficiaries.
+**Analytics use cases:** Reward distribution analysis, recipient tracking, and fee reward beneficiary identification.
+**Example:** '9WzDXwBbmkg8ZTbNMqUxvQRAyrZzDsGYdLVL9zYtAWWM'
+
+{% enddocs %} 

models/descriptions/columns/root_slot.md

@@ -0,0 +1,10 @@
+{% docs root_slot %}
+
+The latest slot confirmed by the vote account. This field tracks the most recent slot that the vote account has confirmed as part of the consensus process, enabling confirmation analysis and network health assessment.
+
+**Data type:** INTEGER (slot number)
+**Business context:** Used to track vote account confirmation activity, analyze consensus participation, and assess network health.
+**Analytics use cases:** Confirmation activity tracking, consensus participation analysis, and network health assessment.
+**Example:** 123456789, 123456800
+
+{% enddocs %} 

models/descriptions/columns/signers.md

@@ -1,14 +1,10 @@
 {% docs signers %}
-An array of account addresses that have signed the transaction, authorizing its execution on the Solana blockchain. Each signer is a base58-encoded public key. Signers are required for transaction validity and may include the fee payer and other accounts with write permissions. The order of signers matches their appearance in the transaction's account_keys array. For more details, see: https://docs.solana.com/developing/programming-model/accounts#signers
 
-**Example:**
-- ["3N5k...", "7G8h..."]
+List of accounts that signed the transaction. This field captures all wallet addresses that provided signatures for the transaction, enabling multi-signature analysis and transaction authority tracking.
 
-**Business Context:**
-- Used to verify transaction authorization and trace which accounts initiated or approved actions.
-- Important for analytics on user activity, multisig wallets, and program interactions.
+**Data type:** ARRAY (list of Solana addresses)
+**Business context:** Used to track transaction signers, analyze multi-signature patterns, and identify transaction authorities.
+**Analytics use cases:** Multi-signature analysis, transaction authority tracking, and signer pattern studies.
+**Example:** ['9WzDXwBbmkg8ZTbNMqUxvQRAyrZzDsGYdLVL9zYtAWWM', 'AnotherAddress...']
 
-**Relationships:**
-- Subset of the 'account_keys' array.
-- The first signer is typically the fee payer.
 {% enddocs %}

models/descriptions/columns/software_version.md

@@ -0,0 +1,10 @@
+{% docs software_version %}
+
+The Solana mainnet version running on the validator. This field tracks which software version the validator is operating, enabling network upgrade monitoring and compatibility analysis.
+
+**Data type:** STRING (version number)
+**Business context:** Used to track network upgrades, analyze version adoption patterns, and monitor compatibility across the network.
+**Analytics use cases:** Network upgrade tracking, version adoption analysis, and compatibility monitoring.
+**Example:** '1.17.0', '1.16.0'
+
+{% enddocs %} 

models/descriptions/columns/stake_account.md

@@ -1,5 +1,10 @@
 {% docs stake_account %}
 
-An account address containing balances of staked SOL.
+The address of the stake account. This field identifies the specific account that holds staked SOL and participates in the staking system.
+
+**Data type:** STRING (Solana address)
+**Business context:** Used to track stake accounts, analyze delegation patterns, and measure staking participation.
+**Analytics use cases:** Stake account tracking, delegation analysis, and staking participation measurement.
+**Example:** '9WzDXwBbmkg8ZTbNMqUxvQRAyrZzDsGYdLVL9zYtAWWM'
 
 {% enddocs %}

models/descriptions/columns/stake_account_sol.md

@@ -0,0 +1,10 @@
+{% docs stake_account_sol %}
+
+The SOL held in this stake account. This field tracks the total SOL balance in the stake account, enabling balance analysis and stake amount tracking.
+
+**Data type:** DECIMAL (SOL amount)
+**Business context:** Used to track stake account balances, analyze stake amounts, and assess account funding.
+**Analytics use cases:** Balance tracking, stake amount analysis, and funding assessment.
+**Example:** 100.0, 1000.0, 5000.0
+
+{% enddocs %} 

models/descriptions/columns/stake_active.md

@@ -0,0 +1,10 @@
+{% docs stake_active %}
+
+Whether the stake account is active. This field indicates if the stake account is currently participating in staking and earning rewards, enabling stake status analysis and active stake tracking.
+
+**Data type:** BOOLEAN (true/false)
+**Business context:** Used to track stake account status, analyze active stake patterns, and measure staking participation.
+**Analytics use cases:** Status tracking, pattern analysis, and participation measurement.
+**Example:** true, false
+
+{% enddocs %} 

models/descriptions/columns/stake_authority.md

@@ -1,5 +1,10 @@
 {% docs stake_authority %}
 
-The authority that can perform staking related actions on the stake account except for withdrawing.
+The wallet address of the user who initialized the transaction. This field identifies the account that has authority over the stake account and initiated the staking action.
+
+**Data type:** STRING (Solana address)
+**Business context:** Used to track stake authorities, analyze user staking behavior, and identify transaction initiators.
+**Analytics use cases:** Stake authority tracking, user staking behavior analysis, and transaction initiation patterns.
+**Example:** '9WzDXwBbmkg8ZTbNMqUxvQRAyrZzDsGYdLVL9zYtAWWM'
 
 {% enddocs %}

models/descriptions/columns/stake_balance.md

@@ -0,0 +1,10 @@
+{% docs stake_balance %}
+
+The amount staked in SOL. This field represents the total value of SOL currently staked in the account, enabling staking amount analysis and delegation value tracking.
+
+**Data type:** DECIMAL (SOL amount)
+**Business context:** Used to analyze staking amounts, track delegation values, and measure staking participation levels.
+**Analytics use cases:** Staking amount analysis, delegation value tracking, and staking participation measurement.
+**Example:** 100.0, 1000.0
+
+{% enddocs %} 

models/descriptions/columns/stake_type.md

@@ -0,0 +1,10 @@
+{% docs stake_type %}
+
+The status of the stake (active, inactive, activating, deactivating). This field tracks the current state of the stake in the staking lifecycle, enabling stake lifecycle analysis and behavior tracking.
+
+**Data type:** STRING (stake status)
+**Business context:** Used to analyze stake lifecycles, track activation/deactivation patterns, and monitor staking behavior.
+**Analytics use cases:** Stake lifecycle analysis, activation/deactivation patterns, and staking behavior tracking.
+**Example:** 'active', 'inactive', 'activating', 'deactivating'
+
+{% enddocs %} 

models/descriptions/columns/start_slot.md

@@ -0,0 +1,10 @@
+{% docs start_slot %}
+
+The first slot of the epoch. This field identifies the beginning slot number for the epoch, enabling epoch boundary tracking and time-based analysis.
+
+**Data type:** INTEGER (slot number)
+**Business context:** Used to track epoch boundaries, analyze time-based patterns, and provide epoch context for block production data.
+**Analytics use cases:** Epoch boundary tracking, time-based analysis, and epoch context provision.
+**Example:** 123456789, 123456800
+
+{% enddocs %} 

models/descriptions/columns/updated_at.md

@@ -0,0 +1,10 @@
+{% docs updated_at %}
+
+The last date when the validator information was updated. This field tracks when the validator's metadata was last refreshed, enabling data freshness analysis and update tracking.
+
+**Data type:** TIMESTAMP (UTC)
+**Business context:** Used to track data freshness, analyze update patterns, and ensure information currency.
+**Analytics use cases:** Freshness tracking, update pattern analysis, and currency assessment.
+**Example:** '2024-01-15 10:30:00', '2024-01-14 14:45:30'
+
+{% enddocs %} 

models/descriptions/columns/validator_epoch_credits.md

@@ -0,0 +1,10 @@
+{% docs validator_epoch_credits %}
+
+Epoch credits for the validator. This field tracks the cumulative voting credits earned by the validator across epochs, enabling performance analysis and reward calculation.
+
+**Data type:** STRING (credits data)
+**Business context:** Used to track validator voting performance, analyze credit accumulation patterns, and calculate voting rewards.
+**Analytics use cases:** Performance analysis, credit accumulation tracking, and reward calculation.
+**Example:** "123/1000/500", "456/1500/1000"
+
+{% enddocs %} 

models/descriptions/columns/validator_name.md

@@ -0,0 +1,10 @@
+{% docs validator_name %}
+
+The name of the validator. This field provides a human-readable identifier for the validator, enabling easier identification and branding analysis.
+
+**Data type:** STRING (validator name)
+**Business context:** Used to identify validators, analyze branding, and track user experience with different validators.
+**Analytics use cases:** Validator identification, branding analysis, and user experience tracking.
+**Example:** 'Solana Foundation', 'Chorus One', 'Stakefish'
+
+{% enddocs %} 

models/descriptions/columns/validator_rank.md

@@ -0,0 +1,10 @@
+{% docs validator_rank %}
+
+The rank of the validator by amount of delegated SOL. This field provides the validator's position in the network based on total stake delegation, enabling validator ranking analysis and stake distribution studies.
+
+**Data type:** INTEGER (ranking number)
+**Business context:** Used to analyze validator rankings, track stake distribution, and study validator performance by stake size.
+**Analytics use cases:** Validator ranking analysis, stake distribution studies, and performance correlation analysis.
+**Example:** 1, 10, 100
+
+{% enddocs %} 

models/descriptions/columns/vote_account_owner.md

@@ -0,0 +1,10 @@
+{% docs vote_account_owner %}
+
+The program account that owns the vote account. This field identifies the Solana program that has authority over the vote account, enabling ownership analysis and program relationship tracking.
+
+**Data type:** STRING (program address)
+**Business context:** Used to track vote account ownership, analyze program relationships, and understand account control structures.
+**Analytics use cases:** Ownership tracking, program relationship analysis, and control structure understanding.
+**Example:** 'Vote111111111111111111111111111111111111111111'
+
+{% enddocs %} 

models/descriptions/columns/vote_choice.md

@@ -0,0 +1,10 @@
+{% docs vote_choice %}
+
+The voting option selected by the user on a Realms proposal. This field captures the specific choice made by the voter, enabling voting preference analysis and outcome prediction.
+
+**Data type:** STRING (voting option)
+**Business context:** Used to track voting preferences, analyze proposal outcomes, and measure governance sentiment.
+**Analytics use cases:** Voting preference analysis, proposal outcome prediction, and governance sentiment analysis.
+**Example:** 'yes', 'no', 'abstain'
+
+{% enddocs %} 

models/descriptions/columns/vote_options.md

@@ -0,0 +1,10 @@
+{% docs vote_options %}
+
+The options that will be available to users who are voting on the proposal. This field contains the available voting choices or options for the governance proposal, enabling option analysis and voting choice tracking.
+
+**Data type:** ARRAY (vote options)
+**Business context:** Used to track voting options, analyze choice patterns, and understand proposal structure.
+**Analytics use cases:** Option tracking, choice pattern analysis, and structure understanding.
+**Example:** ['Yes', 'No'], ['Option A', 'Option B', 'Option C'], ['Approve', 'Reject', 'Abstain']
+
+{% enddocs %} 

models/descriptions/columns/vote_rank.md

@@ -0,0 +1,10 @@
+{% docs vote_rank %}
+
+The order which a user ranks their choices on a ranked vote on Realms. This field captures the preference ranking in multi-choice governance votes, enabling ranked voting analysis and preference ordering studies.
+
+**Data type:** INTEGER (ranking number)
+**Business context:** Used to analyze ranked voting patterns, preference ordering, and governance decision complexity.
+**Analytics use cases:** Ranked voting analysis, preference ordering studies, and governance decision complexity measurement.
+**Example:** 1, 2, 3
+
+{% enddocs %} 

models/descriptions/columns/vote_type.md

@@ -0,0 +1,10 @@
+{% docs vote_type %}
+
+The type of voting strategy that will be used for voting on the proposal. This field specifies the voting mechanism or strategy for the governance proposal, enabling voting analysis and strategy comparison.
+
+**Data type:** STRING (vote type)
+**Business context:** Used to track voting strategies, analyze voting mechanisms, and compare different governance approaches.
+**Analytics use cases:** Strategy tracking, mechanism analysis, and approach comparison.
+**Example:** 'Single Choice', 'Multiple Choice', 'Quadratic Voting', 'Token Weighted'
+
+{% enddocs %} 

models/descriptions/columns/vote_weight.md

@@ -0,0 +1,10 @@
+{% docs vote_weight %}
+
+The percentage of voting power put towards a voting option on Realms. This field represents the proportion of a voter's total voting power allocated to a specific choice in weighted voting systems.
+
+**Data type:** DECIMAL (percentage as decimal)
+**Business context:** Used to analyze voting power distribution, measure governance influence, and study weighted voting outcomes.
+**Analytics use cases:** Voting power distribution analysis, governance influence measurement, and weighted voting outcome studies.
+**Example:** 0.75, 1.0, 0.25
+
+{% enddocs %} 

models/descriptions/columns/voter.md

@@ -0,0 +1,10 @@
+{% docs voter %}
+
+The address of the account that cast the governance vote. This field identifies the specific wallet or account that participated in the governance decision, enabling voter analysis and participation tracking.
+
+**Data type:** STRING (Solana address)
+**Business context:** Used to track governance participation, analyze voter behavior, and identify key governance participants.
+**Analytics use cases:** Voter participation analysis, whale voting tracking, and governance participation pattern studies.
+**Example:** '9WzDXwBbmkg8ZTbNMqUxvQRAyrZzDsGYdLVL9zYtAWWM'
+
+{% enddocs %} 

models/descriptions/columns/voter_account.md

@@ -0,0 +1,10 @@
+{% docs voter_account %}
+
+The account with locked tokens linked to the NFT that determines voting power. This field identifies the specific account that holds the governance tokens and determines the voting power for the governance action.
+
+**Data type:** STRING (Solana address)
+**Business context:** Used to analyze voting power distribution, governance token holdings, and voter influence measurement.
+**Analytics use cases:** Voting power analysis, governance token distribution studies, and voter influence measurement.
+**Example:** '9WzDXwBbmkg8ZTbNMqUxvQRAyrZzDsGYdLVL9zYtAWWM'
+
+{% enddocs %} 

models/descriptions/columns/voter_nft.md

@@ -0,0 +1,10 @@
+{% docs voter_nft %}
+
+The NFT mint used in this vote on Marinade governance. This field identifies the specific NFT that was used to participate in the governance vote, enabling NFT-based voting analysis and utility measurement.
+
+**Data type:** STRING (NFT mint address)
+**Business context:** Used to track NFT-based governance participation and analyze the utility of governance NFTs.
+**Analytics use cases:** NFT-based voting analysis, governance participation tracking, and NFT utility measurement.
+**Example:** '9WzDXwBbmkg8ZTbNMqUxvQRAyrZzDsGYdLVL9zYtAWWM'
+
+{% enddocs %} 

models/descriptions/columns/votes.md

@@ -0,0 +1,10 @@
+{% docs votes %}
+
+Votes cast by the vote account during the epoch. This field tracks the voting activity of the vote account within the current epoch, enabling participation analysis and consensus contribution measurement.
+
+**Data type:** ARRAY (vote data)
+**Business context:** Used to track vote account participation, analyze voting patterns, and measure consensus contribution.
+**Analytics use cases:** Participation tracking, voting pattern analysis, and consensus contribution measurement.
+**Example:** [{'slot': 123456789, 'confirmation_count': 32}, {'slot': 123456790, 'confirmation_count': 31}]
+
+{% enddocs %} 

models/descriptions/columns/warmup_cooldown_rate.md

@@ -0,0 +1,10 @@
+{% docs warmup_cooldown_rate %}
+
+The rate at which stake can be activated or deactivated. This field tracks the speed of stake transitions between active and inactive states, enabling activation/deactivation analysis and timeline planning.
+
+**Data type:** DECIMAL (rate value)
+**Business context:** Used to track stake transition rates, analyze activation/deactivation patterns, and plan for stake changes.
+**Analytics use cases:** Transition rate tracking, pattern analysis, and change planning.
+**Example:** 0.25, 0.5, 1.0
+
+{% enddocs %} 

models/descriptions/columns/withdraw_amount.md

@@ -0,0 +1,10 @@
+{% docs withdraw_amount %}
+
+The amount of SOL withdrawn from the stake account. This field tracks the quantity of SOL removed from staking during withdrawal actions, enabling withdrawal analysis and stake reduction tracking.
+
+**Data type:** DECIMAL (SOL amount)
+**Business context:** Used to track withdrawal amounts, analyze withdrawal patterns, and measure stake reduction activity.
+**Analytics use cases:** Withdrawal tracking, pattern analysis, and reduction measurement.
+**Example:** 10.0, 100.0, 1000.0
+
+{% enddocs %} 

models/descriptions/columns/withdraw_authority.md

@@ -1,5 +1,10 @@
 {% docs withdraw_authority %}
 
-The authority that can withdraw SOL from the stake account.
+The account responsible for signing any stake withdrawal transactions. This field identifies who has authority to withdraw staked SOL from the account.
+
+**Data type:** STRING (Solana address)
+**Business context:** Used to track withdrawal authorities, analyze stake security, and monitor withdrawal patterns.
+**Analytics use cases:** Withdrawal authority tracking, stake security analysis, and withdrawal pattern monitoring.
+**Example:** '9WzDXwBbmkg8ZTbNMqUxvQRAyrZzDsGYdLVL9zYtAWWM'
 
 {% enddocs %}

models/descriptions/columns/withdraw_destination.md

@@ -0,0 +1,10 @@
+{% docs withdraw_destination %}
+
+The destination wallet address of the withdrawn SOL. This field identifies where the SOL was transferred to during withdrawal actions, enabling movement tracking and destination analysis.
+
+**Data type:** STRING (Solana address)
+**Business context:** Used to track SOL movement destinations, analyze withdrawal patterns, and identify withdrawal recipients.
+**Analytics use cases:** Movement tracking, pattern analysis, and recipient identification.
+**Example:** '9WzDXwBbmkg8ZTbNMqUxvQRAyrZzDsGYdLVL9zYtAWWM'
+
+{% enddocs %} 

models/descriptions/columns/www_url.md

@@ -0,0 +1,10 @@
+{% docs www_url %}
+
+URL for the validator's website. This field provides a link to the validator's official website, enabling branding analysis and community engagement tracking.
+
+**Data type:** STRING (URL)
+**Business context:** Used for validator branding, community engagement tracking, and official information access.
+**Analytics use cases:** Branding analysis, engagement tracking, and information access.
+**Example:** 'https://validator.com', 'https://stake.example.com', 'https://solana-validator.org'
+
+{% enddocs %} 

models/descriptions/tables/dim_epoch.md

@@ -0,0 +1,24 @@
+{% docs dim_epoch %}
+
+## Description
+This table contains epoch information for the Solana blockchain, including the block range for each epoch. It serves as a dimension table that provides epoch context for governance and staking analytics, enabling time-based analysis across different epochs and supporting epoch-level aggregations.
+
+## Key Use Cases
+- Provide epoch context for governance and staking analytics
+- Enable epoch-based filtering and grouping of blockchain data
+- Support time-series analysis across different epochs
+- Facilitate epoch-level aggregations and reporting
+- Track epoch progression and block range changes
+
+## Important Relationships
+- Links to `gov.fact_validators` via `epoch` for validator performance analysis
+- Connects to `gov.fact_proposal_votes` through epoch context for governance timeline analysis
+- References `gov.fact_rewards_staking` and `gov.fact_rewards_voting` for epoch-based reward tracking
+- Provides epoch context for `gov.fact_stake_accounts` and `gov.fact_vote_accounts`
+
+## Commonly-used Fields
+- `epoch`: The epoch number identifier
+- `start_block`: The first block number in the epoch
+- `end_block`: The last block number in the epoch
+
+{% enddocs %} 

models/descriptions/tables/ez_staking_lp_actions.md

@@ -0,0 +1,30 @@
+{% docs ez_staking_lp_actions %}
+
+## Description
+This table provides a unified view of native staking actions on the Solana blockchain using the official Stake11111111111111111111111111111111111111 program. It consolidates stake delegation, activation, deactivation, and withdrawal operations and enriches them with metadata, USD pricing, and validator information, enabling comprehensive analysis of native staking participation and validator delegation patterns.
+
+## Key Use Cases
+- Analyze native staking delegation patterns and validator selection
+- Track stake account lifecycle and balance changes with USD values
+- Monitor native staking participation and delegation trends
+- Study validator stake distribution and concentration
+- Support native staking analytics and reward distribution analysis
+
+## Important Relationships
+- Links to `gov.fact_staking_lp_actions` for detailed native staking action data
+- Connects to `price.ez_prices_hourly` for USD price conversion
+- References `core.fact_blocks` and `core.fact_transactions` for blockchain context
+- Provides unified native staking context for validator analytics
+
+## Commonly-used Fields
+- `block_timestamp`: Timestamp when the staking action occurred
+- `tx_id`: Unique transaction identifier for the staking action
+- `stake_account`: Address of the stake account
+- `vote_pubkey`: Vote account that the stake is delegated to
+- `action`: Type of staking action (e.g., 'delegate', 'deactivate', 'withdraw')
+- `amount`: Amount of SOL involved in the action
+- `amount_usd`: USD value of the action
+- `user`: Address of the user performing the action
+- `validator_name`: Name of the validator being delegated to
+
+{% enddocs %} 

models/descriptions/tables/fact_block_production.md

@@ -0,0 +1,26 @@
+{% docs fact_block_production %}
+
+## Description
+This table tracks block production events on the Solana blockchain, capturing which validators produced blocks and when. It provides insights into network performance, validator participation in consensus, and block production distribution across the validator set.
+
+## Key Use Cases
+- Analyze block production distribution across validators
+- Track validator participation in network consensus
+- Monitor network performance and block production efficiency
+- Study validator reliability and block production patterns
+- Support network health analysis and validator performance metrics
+
+## Important Relationships
+- Links to `gov.fact_validators` through `node_pubkey` for validator performance analysis
+- Connects to `gov.fact_vote_accounts` for vote account analysis
+- References `core.fact_blocks` for block context
+- Provides block production context for validator analytics
+
+## Commonly-used Fields
+- `block_timestamp`: Timestamp when the block was produced
+- `block_id`: Block number that was produced
+- `node_pubkey`: Address of the validator that produced the block
+- `vote_pubkey`: Vote account associated with the block producer
+- `epoch`: Epoch when the block was produced
+
+{% enddocs %} 

models/descriptions/tables/fact_gauges_creates.md

@@ -0,0 +1,26 @@
+{% docs fact_gauges_creates %}
+
+## Description
+This table tracks gauge creation events, particularly for Marinade Finance's gauge system. Gauge creation establishes new reward distribution mechanisms for liquidity pools or protocols, enabling decentralized control over reward allocation and liquidity incentivization strategies.
+
+## Key Use Cases
+- Track gauge creation patterns and new reward distribution mechanisms
+- Analyze gauge creation frequency and protocol adoption
+- Study gauge lifecycle from creation to voting and reward distribution
+- Monitor DeFi protocol reward strategies and incentivization
+- Support gauge analytics and reward optimization
+
+## Important Relationships
+- Links to `gov.fact_gauges_votes` through `gauge` address for complete gauge lifecycle
+- Connects to `gov.fact_gov_actions` for governance action analysis
+- References `core.fact_blocks` and `core.fact_transactions` for blockchain context
+- Provides gauge context for DeFi analytics
+
+## Commonly-used Fields
+- `block_timestamp`: Timestamp when the gauge was created
+- `tx_id`: Unique transaction identifier for the gauge creation
+- `gauge`: Address of the created gauge
+- `creator`: Address of the account that created the gauge
+- `program_name`: Name of the gauge program (e.g., 'marinade')
+
+{% enddocs %} 

models/descriptions/tables/fact_gauges_votes.md

@@ -0,0 +1,27 @@
+{% docs fact_gauges_votes %}
+
+## Description
+This table tracks gauge voting events, particularly for Marinade Finance's gauge system. Gauge voting allows users to allocate rewards to different liquidity pools or protocols, providing a mechanism for decentralized reward distribution and liquidity incentivization.
+
+## Key Use Cases
+- Analyze gauge voting patterns and reward allocation preferences
+- Track reward distribution across different protocols and pools
+- Study liquidity incentivization strategies and effectiveness
+- Monitor gauge voting participation and user behavior
+- Support DeFi analytics and reward optimization
+
+## Important Relationships
+- Links to `gov.fact_gov_actions` through governance context for comprehensive governance analysis
+- Connects to `gov.fact_gauges_creates` for gauge creation lifecycle
+- References `core.fact_blocks` and `core.fact_transactions` for blockchain context
+- Provides gauge context for DeFi analytics
+
+## Commonly-used Fields
+- `block_timestamp`: Timestamp when the gauge vote was cast
+- `tx_id`: Unique transaction identifier for the gauge vote
+- `voter`: Address of the account that cast the gauge vote
+- `gauge`: Address of the gauge being voted on
+- `vote_weight`: Weight of the vote for reward allocation
+- `program_name`: Name of the gauge program (e.g., 'marinade')
+
+{% enddocs %} 

models/descriptions/tables/fact_gov_actions.md

@@ -0,0 +1,30 @@
+{% docs fact_gov_actions %}
+
+## Description
+This table tracks all governance actions across Saber and Marinade governance platforms. It captures various governance activities such as voting, proposal creation, and administrative actions, providing a comprehensive view of decentralized governance participation and decision-making processes on Solana.
+
+## Key Use Cases
+- Analyze governance participation patterns across different protocols
+- Track voting behavior and decision-making processes
+- Monitor governance action types and their frequency
+- Study protocol governance evolution and participation trends
+- Support governance analytics and reporting for DAOs and protocols
+
+## Important Relationships
+- Links to `gov.fact_proposal_votes` through governance context for comprehensive voting analysis
+- Connects to `gov.fact_proposal_creation` for proposal lifecycle tracking
+- References `core.fact_blocks` and `core.fact_transactions` for blockchain context
+- Provides governance context for protocol-specific analytics
+
+## Commonly-used Fields
+- `block_timestamp`: Timestamp when the governance action was processed
+- `tx_id`: Unique transaction identifier for the governance action
+- `signer`: Address of the account that performed the governance action
+- `program_name`: Name of the governance program (e.g., 'saber', 'marinade')
+- `action`: Type of governance action performed
+- `amount`: Amount associated with the governance action
+- `locker_account`: Account with locked tokens for governance participation
+- `locker_nft`: NFT used for governance participation (Marinade)
+- `mint`: Token mint address associated with the governance action
+
+{% enddocs %} 

models/descriptions/tables/fact_proposal_creation.md

@@ -0,0 +1,28 @@
+{% docs fact_proposal_creation %}
+
+## Description
+This table tracks governance proposal creation events across different platforms including Realms and Tribeca. It captures the initial creation of governance proposals, including proposal details, creator information, and proposal parameters, enabling comprehensive analysis of governance proposal lifecycle and creation patterns.
+
+## Key Use Cases
+- Track governance proposal creation patterns and frequency
+- Analyze proposal creation by different governance platforms
+- Study proposal lifecycle from creation to voting
+- Monitor governance participation and proposal diversity
+- Support DAO analytics and governance reporting
+
+## Important Relationships
+- Links to `gov.fact_proposal_votes` through `proposal` address for complete proposal lifecycle
+- Connects to `gov.fact_gov_actions` for governance action analysis
+- References `core.fact_blocks` and `core.fact_transactions` for blockchain context
+- Provides proposal context for governance analytics
+
+## Commonly-used Fields
+- `block_timestamp`: Timestamp when the proposal was created
+- `tx_id`: Unique transaction identifier for the proposal creation
+- `proposal`: Address representing the created proposal
+- `creator`: Address of the account that created the proposal
+- `governance_platform`: Platform where the proposal was created
+- `program_name`: Name of the governance program
+- `realms_id`: Address representing the voting group within Realms
+
+{% enddocs %}