# `MishkaDocument.Note`
[🔗](https://github.com/mishka-group/mishka_document/blob/v0.0.1/lib/mishka_document/resources/note.ex#L5)

Manages documentation notes within sections.

This resource represents individual notes that contain the actual documentation content.
Each note belongs to a specific section and supports content and technical review workflows
with multiple approval states.

Notes are the core content units of the documentation system, containing the detailed
information organized within sections. The resource supports multi-language content,
SEO optimization, and comprehensive review workflows.

Multi-tenant isolation ensures notes are properly segregated between sites.

# `t`

```elixir
@type t() :: %MishkaDocument.Note{
  __lateral_join_source__: term(),
  __meta__: term(),
  __metadata__: term(),
  __order__: term(),
  aggregates: term(),
  approved_note_draft_count: term(),
  archived_at: term(),
  calculations: term(),
  change_version: term(),
  content: term(),
  content_classes: term(),
  content_components: term(),
  content_icons: term(),
  content_review_status: term(),
  content_word_count: term(),
  id: term(),
  inserted_at: term(),
  master_section: term(),
  note_drafts: term(),
  order_position: term(),
  pending_note_draft_content_review_count: term(),
  pending_note_draft_technical_review_count: term(),
  schema: term(),
  section: term(),
  section_id: term(),
  seo_tags: term(),
  site: term(),
  site_id: term(),
  technical_review_status: term(),
  title: term(),
  updated_at: term()
}
```

# `__guarded_change__`

Apply the full GuardedStruct pipeline (sanitize → validate → derive →
main_validator) to `attrs` and return either `{:ok, transformed_attrs}`
or `{:error, errors}`. Wire this into an `Ash.Resource.Change` to plug
guardedstruct rules into Ash's changeset pipeline.

The function is named `__guarded_change__` because it does more than
validate — it can also transform values (trim, downcase, slugify,
auto-fill, etc.) before they reach the data layer.

# `__guarded_field_meta__`

O(1) lookup of a field's compile-time metadata by name. Returns
`nil` for unknown fields.

# `__guarded_field_name_set__`

Compile-time-baked `MapSet` of every field name owned by the
`guardedstruct` block. Used by `GuardedStruct.AshResource.Change`
to decide, in O(1), whether a key in `changeset.atomics`
belongs to the pipeline.

# `default_short_name`

# `input`

```elixir
@spec input(values :: map() | Keyword.t()) :: map() | no_return()
```

Validates that the keys in the provided input are valid for at least one action on the resource.

Raises a KeyError error at compile time if not. This exists because generally a struct should only ever
be created by Ash as a result of a successful action. You should not be creating records manually in code,
e.g `%MyResource{value: 1, value: 2}`. Generally that is fine, but often with embedded resources it is nice
to be able to validate the keys that are being provided, e.g

```elixir
Resource
|> Ash.Changeset.for_create(:create, %{embedded: EmbeddedResource.input(foo: 1, bar: 2)})
|> Ash.create()
```

# `input`

```elixir
@spec input(values :: map() | Keyword.t(), action :: atom()) :: map() | no_return()
```

Same as `input/1`, except restricts the keys to values accepted by the action provided.

# `json_api_match_route`

# `primary_key_matches?`

---

*Consult [api-reference.md](api-reference.md) for complete listing*