Blog
-
Giving Potbot tools a checked contract
Versioned tool contracts, three monitored SYN Cogs and a unit conversion that keeps source identity and precision explicit.
-
Checking what Potbot already has
A new source-inventory Cog maps Potbot’s existing modules to their owners and tool-plan stages, while keeping execution qualification explicit.
-
Stepping through Python with Potbot
Potbot’s first debugger backend can stop and step through Python, inspect the stack, and record each SYN Cog’s progress and completion statistics.
-
Giving every object a memory of its own
A research proposal for separate object memories in Potbot and Syn, with explicit sources, time and permissions.
-
Two more places to find the songs
A dated JAM Audio Live artist listing and a verified Spotify playlist placement add two different public records to the song pages.
-
Hearing lyric edits while the music plays
The timeline can now show timed lyrics over cover artwork while the selected audio plays, including unsaved timing edits, seeks and loops.
-
What ten music searches showed about KeywordMoves and vidIQ
I compared ten identical music queries, found gaps in KeywordMoves, and added better evidence imports and phrase filtering. The results also show why a small benchmark needs careful limits.
-
Where my songs have been heard and published so far
A linked roundup of published writing, public resources and confirmed radio logs connected to my songs, with more radio play lined up for upcoming releases.
-
Bringing more sources into KeywordMoves
KeywordMoves 0.5.0 brings catalogue context, article attention and keyword estimates into explicit research plans, while keeping their different meanings clear.
-
Keeping keyword evidence fresh with KeywordMoves
KeywordMoves 0.4.0 now keeps dated evidence, shows coverage gaps and checks which measurements can be compared. Actual source access still needs verification.