Authentication identifies a client; authorization decides which operations that identity may perform. A topic reader does not automatically need permission to publish or administer the topic. Real Kafka deployments can use TLS, SASL and authorization rules alongside group permissions and operational policy. This workspace models only a small topic-policy record so the permission boundary can be inspected. It does not validate certificates, issue credentials or enforce a complete broker authorizer. These tasks ask for the named principal and the minimum requested topic permissions. Record only those operations and compare the policy afterward. A write grant to the wrong principal is not a successful read-only handoff.
Inspect the topics, partition logs and group offsets before changing the cluster.