# check_stampable

<table class=".origin_table">
    <tr>
        <td style="text-align: left; border-style: hidden">*function*  of [dascore.core._spool_inventory](`dascore.core._spool_inventory`)</td>
        <td style="text-align: right; border-style: hidden">[source](https://github.com/DASDAE/dascore/blob/dev/dascore/core/_spool_inventory.py#L404-L426)</td>
    </tr>
</table>

:::{.padded_bottom_10pt}

:::{.def_block}


<b>check_stampable</b>(<br>
    &nbsp;&nbsp;&nbsp;&nbsp;name: str
,<br>
    &nbsp;&nbsp;&nbsp;&nbsp;rows: DataFrame
,<br>
)-> 'None'


:::

:::
Refuse a stamp which would overwrite the plan's own bookkeeping.

An annotation group may be named anything the inventory does not
reserve, and the stamp is assigned onto the outputs — so a group
called `output_id` would replace the column binding each output to
its members, and one called `time_min` an envelope. Overwriting a
carried attr is fine and is how re-splitting restamps; these are not
attrs.

