Back to portfolio

Platanus Hack 26 AI security

yieldOS

Repository policy checks that run before an agent changes or commits code.

yieldOS team at Platanus Hack 26
realTeam photo from Platanus Hack 26.
At a glance

What I owned

Period
Platanus Hack 26; 36-hour build
Role
Product and agent-safety workflow contributor
Team
Four-person hackathon team
Users
Developers running coding agents and reviewers approving their changes
Status
Public prototype and repository
Contribution

Contributed to product framing, the landing, and reviewable evidence UX for the four-person prototype.

Tradeoff

Run deterministic local checks quickly, then reserve slower model review for ambiguous decisions.

Evidence

Public repository, Platanus project page, team photo, and accurately labelled event context photos.

Event
Platanus Hack 26
Build time
36 hours
Enforcement
Hooks and Git gates
Source
Public repository
Executable policy evidence

The model proposes. The policy decides.

A pre-action hook classifies the requested tool action, evaluates deterministic repository policy, returns allow, review, or block, and appends a redacted tamper-evident audit event.

01

Policy at the repository boundary

Coding agents can install packages, edit files, and run commands quickly. yieldOS intercepts those actions and checks them against repository policy.

02

Deterministic checks

Claude Code hooks and Git hooks run checks for secrets, missing authorization, and unsafe changes. Most checks use local rules and return reviewable evidence.

03

Hackathon build

The four-person team produced the prototype in 36 hours and published the code.