sink-s3-jsonl

Immutable S3 sink: JSONL in on stdin, one new object written under a validated bucket and prefix, native sink-result summary out on stdout.

Use when

• Findings, evidence, or audit records already exist on stdin as JSONL
• You need a repo-owned persistence step after detect-*, discover-*, view/*, or another sink-safe producer
• The target bucket already exists and should remain append-only through new objects

Do NOT use

• For bucket creation, policy changes, ACL mutation, lifecycle changes, or object deletion
• For schema migration or data rewriting inside an existing object
• As a detector, ingest normalizer, or remediation workflow by itself
• When you need to write to a system other than Amazon S3

Do NOT do