Tasmanian public-sector constraints we plan for

Working from Hobart means many of our clients sit near public-sector rules even when they are contractors. We do not pretend to replace legal counsel, but we do refuse briefs that assume a consumer chatbot pattern will pass unnoticed.

In practice that changes discovery in three ways. First, we document data classes early — what may leave the agency boundary, what must not. Second, we prefer architectures that keep retrieval corpora inside approved tenancies. Third, we write the first release as something a records officer can understand: inputs, outputs, retention.

If your programme ignores those constraints, the tool may dazzle in a pilot and stall at assurance. Better to spend an extra week in discovery than to explain an outbound prompt log after the fact.