Auction Observation and Bidder-Profile Intake
Implemented local intake, limited by the scope of observations provided.
A local command-line workflow for recording observed bids or visible Last-9 sequences and examining bidder persistence, rotation and repeat co-bidding.
- Why
- I needed observations across time instead of making conclusions from a single screenshot.
How I built it
- I added a local observation store for manually entered public auction events.
- I created commands to record an individual observation or one visible Last-9 sequence.
- I built summaries, bidder profiles and rotation metrics from the collected events.
- I connected the reviewed observations to the conservative risk screen.
- To copy it you need
- Make a small CSV of manually observed or fictional events and reproduce one summary before attempting longer tracking.
Try it yourself
Copy this prompt and paste it into ChatGPT or Claude to try it yourself.
I want to copy the observation log from Jovan Diaz's What Are We Building? profile. He built a small command-line tool that records the bids he can see, or one visible Last-9 sequence, and then summarizes who keeps bidding, who takes turns and who bids together repeatedly. He wanted trends over time instead of conclusions from one screenshot. His limit: a partial sequence can't show the full history of an auction. Help me make a starter version with a small CSV of fictional events, and reproduce one summary before we try anything longer. Start by asking what I want to track. Ask me for anything you need.
Tools I used for this project
ChatGPT: I used ChatGPT to draft, test, critique or work through the workflow.
Codex: I used Codex to help build or revise repository files and tests.
Python: I used Python scripts or validation tools to process and check structured outputs.
GitHub: GitHub holds all of my repositories: code, instructions, changes and review history.
