Freshness Checks Before Permissions in Python Retrieval for Internal Docs

A developer describes a retrieval design for internal engineering documents that checks whether content is current before applying access controls. The approach stores small, versioned chunks with stable identifiers, revision data, and access-rule references alongside each embedding. Freshness is treated as a query-time constraint, with superseded revisions kept for audit rather than overwritten. The author also filters candidates by permission before any text reaches the model, so unauthorized passages never enter the prompt. A sample Python gate shows how chunks are filtered by latest revision and principal access.