Contributors

Lyrasing contributors should treat the docs as protocol-design infrastructure, not as marketing collateral. Every claim about AVSs, LRTs, slashing, collateral policy, or insurance must be precise enough for a future implementation review.

Contribution posture

Useful contributions improve reviewability. They should make source accuracy, risk boundaries, and product limits easier to audit without adding live-product claims.

Area	Good contribution
Source accuracy updates	Refreshing primary source links, access dates, and claim wording when protocol docs change.
AVS-risk methodology tightening	Clarifying observable inputs, exposure labels, slashability timing, stale-input treatment, and conservative policy responses.
LRT collateral review checklists	Separating backing, redemption, liquidity, oracle, operator, discretion, and slash-surface facts from assumptions.
Slashing-insurance language	Making coverage scope, capacity, trigger evidence, payout order, exclusions, and unresolved evidence more auditable.
Loop / liquidation risk-envelope review	Checking recursive exposure, unwind posture, cap compression, no-loop states, and liquidation-path assumptions.
Comparison pages	Explaining adjacent primitives and risk ownership without slogans, rankings, or integration claims.
Editorial polish	Tightening prose while preserving builder register, technical vocabulary, and product-boundary discipline.

Review packet

Every meaningful docs or research change should be reviewable from a compact packet:

Field	Include
Changed pages	The MDX page or pages that changed.
Changed claim	The claim being added, removed, narrowed, or rephrased.
Primary sources	URLs and access date when protocol mechanics, slash behavior, collateral mechanics, or market primitives are involved.
Risk surface affected	AVS exposure, LRT collateral, slashing insurance, loop policy, oracle input, liquidation, comparison framing, or editorial-only.
Product-boundary check	Confirmation that the change does not imply a live market, active integration, supported collateral, token/governance process, wallet/app flow, or public support intake.
Local verification	Commands run and the relevant output summary, including build, export, link, scan, or content checks when applicable.

The same packet can be written as documentation-only YAML for review. This is not a runtime schema, public application form, ticket queue, Discord intake, or active contributor program:


review_packet:
  changed_pages:
    - "content/avs-risk-methodology/example.mdx"
  changed_claim: "Narrowed slashability timing language to match the source."
  primary_sources:
    - url: "https://docs.example.invalid/slashing"
      accessed: "YYYY-MM-DD"
      supports: "operator-set slashability timing"
  risk_surface: "avs_exposure"
  product_boundary_check:
    live_market_claim: false
    active_integration_claim: false
    supported_collateral_claim: false
    wallet_or_app_flow: false
  local_verification:
    - "python scripts/quality_gate.py"

Source standards

Prefer primary sources for protocol facts:

EigenLayer / EigenCloud docs for EigenLayer AVS, operator-set, slashing, redistribution, safety-delay, and EigenCloud terminology claims.
Symbiotic docs for network, vault, operator, slasher, veto, epoch, withdrawal, and burner-routing mechanics.
Aave docs for reserve, collateral-status, health-factor, liquidation, and parameter concepts.
Morpho docs for isolated market, LLTV, oracle, IRM, vault, cap, queue, and curator concepts.
Lido, ether.fi, or another LRT issuer’s own docs for token mechanics, withdrawal behavior, wrapper behavior, and redemption language.

Third-party dashboards can help discover a question, but they should not be the final source for protocol mechanics. If a primary source changes, disappears, or no longer supports the sentence, downgrade the sentence to a review question or remove it.

Boundaries

This repository is not a support desk, hiring page, investor page, governance forum, token plan, or application backend. Contributions should not add:

wallet or app support flows;
token or governance proposal intake;
APY, TVL, or live-market claims;
supported-collateral additions without a future explicit supported-list session;
on-chain implementation, contracts, deploy scripts, oracle implementation, runtime HTTP calls, or external integrations.

When a contribution needs one of those things to make sense, the content is probably outside this docs repository or outside the current phase.