Start Here: Documentation Templates: Tech Specs: Models - FlipsideCrypto/fsc-evm GitHub Wiki

For new documentation/pages, please follow the naming conventions outlined in the Maintaining the Wiki section.

To assist with the documentation process, copy/paste the following template, alongside the relevant instructions and sources (models, macros etc.) into an AI chat interface. Please double check inputs and outputs prior to saving new or updated documentation.

Technical Specifications Template: Models

Instructions

  1. Follow the template below. Areas that need modifications in the final documentation are typically marked with <...>.
  2. Use --- as the line break to indicate new sections.
  3. See here for an example.
> _Model/function variables are set and managed in each repo's `dbt_project.yml` file, or the models/functions themselves. Please see the [How It Works](https://github.com/FlipsideCrypto/fsc-evm/wiki/General:-How-It-Works:-Project-Variables) guide for more details on how to access and utilize variables effectively._

---

# Overview

* <Provide brief overview of the models being documented. Note: This section and/or document should _not_ contain a guide on how to deploy, interact or manage the models. Rather, please write a [separate guide](https://github.com/FlipsideCrypto/fsc-evm/wiki/Start-Here:-Documentation-Templates:-Guides:-General-Template) for that purpose.> 

---

# <INSERT SCHEMA or CATEGORY. Note, this is intended for viewership/organization purposes and does not need to be repeated below unless the schema/category changes for the following models>

## Model: [schema.table](insert github repo link to relative model path e.g. https://github.com/FlipsideCrypto/fsc-evm/blob/main/models/...sql)

## Usage
* Package: `<Insert package name that the model belongs to e.g. main_package>`
  * Sub-package: `<Insert sub_package (category) that the model belongs to e.g. prices. This is the name of the folder nested directly within the package.>`
* Description: <Please provide brief description of the model>

## Developer Notes
* <Insert key points about the model, edge cases to account for, tips on interacting with the model etc. here. Note: Use bulleted notation and keep the notes condensed, straight to the point, easy to understand. Do not write notes just for the sake of documentation, this section should contain crucial information only, so only include notes if necessary for the developer to understand.>

---

## Model: <next MODEL being documented, if applicable>

## Usage

...

---

# <Insert next SCHEMA or CATEGORY, if applicable>

## Model: 

...
⚠️ **GitHub.com Fallback** ⚠️