% Generated by roxygen2: do not edit by hand
% Please edit documentation in R/snapshot.R
\name{ato_snapshot}
\alias{ato_snapshot}
\title{Pin or inspect the session snapshot date}
\usage{
ato_snapshot(date)
}
\arguments{
\item{date}{ISO \code{"YYYY-MM-DD"} character, \code{Date}, or \code{POSIXct}.
Pass \code{NULL} to clear.}
}
\value{
Invisibly, the new pinned date (as \code{Date}), or \code{NULL}.
}
\description{
Call once at the top of an analysis script to declare the vintage
of ATO data you intend to use. Every subsequent \verb{ato_*} fetch
records this date in the \code{ato_tbl} provenance header, in
\code{ato_manifest()} entries, and in \code{ato_cite()} output. Combined
with SHA-256 integrity (see \code{\link[=ato_sha256]{ato_sha256()}} and \code{\link[=ato_manifest]{ato_manifest()}}),
this gives a reproducible audit trail acceptable for PBO or
Grattan-style published work.
}
\details{
If called with no arguments, returns the current pin (or \code{NULL}
if unset).
}
\examples{
ato_snapshot("2026-04-24")
ato_snapshot()
ato_snapshot(NULL)
}
\seealso{
Other reproducibility: 
\code{\link{ato_deposit_zenodo}()},
\code{\link{ato_manifest}()},
\code{\link{ato_manifest_clear}()},
\code{\link{ato_manifest_write}()},
\code{\link{ato_sha256}()}
}
\concept{reproducibility}
