Skip to content

Add bounty transparency lineage schema#1

Open
Jorel97 wants to merge 1 commit into
Tiinex:masterfrom
Jorel97:codex/bounty-transparency-lineage
Open

Add bounty transparency lineage schema#1
Jorel97 wants to merge 1 commit into
Tiinex:masterfrom
Jorel97:codex/bounty-transparency-lineage

Conversation

@Jorel97
Copy link
Copy Markdown

@Jorel97 Jorel97 commented May 29, 2026

Submission for the public AI lineage schema challenge:
https://www.reddit.com/r/aiagents/comments/1tr0a6j/open_challenge_build_a_traceable_ai_lineage/

Summary

  • Adds tiinex.bounty-transparency.v1, a schema extending tiinex.evidence.v1 for public bounty commitments, submissions, judging decisions, and payout evidence.
  • Adds a proof-of-use trace artifact for the same 1000 SEK challenge so the schema is exercised by a concrete record, not just described.
  • Adds a small standard-library validator that checks required sections, commitment fields, funding totals, submission rows, decision status, and payout status.

Proof of use

python tools/validate_bounty_transparency.py .topics/bounty-transparency/001.trace.md

Expected/observed output:

OK bounty transparency artifact valid
commitments: 1000 SEK
submissions: 3
decision: pending
payout: pending

Why this fits the challenge

The challenge prompt suggested a bounty/funding transparency schema as a useful candidate. This PR makes that candidate concrete and lineage-compatible: promised funds, submitted artifacts, judging decisions, and payout evidence are separated into distinct traceable lanes.

@Tiinusen
Copy link
Copy Markdown
Contributor

You are the first and only competitor, so if you are lucky you might receive the bounty with not much of an effort.

I myself I won't compete, but I will not make it easy for everyone so I will grab all the easy apples as soon as I get to them :P that includes a validator
(which I am working on right now aswell, but it is going meh, prehaps tomorrow when I stop responding Reddit posts and create meme pictures)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants