Harnax compliance layer uses a Kuzu graph database that walks code, generates an AST, and maps it to specifications defined through human conversation with agents
Discovery mechanism (Harnax Discover) walks an existing codebase to suggest/propose domains, letting you formalize and audit code against a spec without touching or needing end-to-end tests
Reflexive loop is a planned feature where counterpointed skills assess diffs/code changes for robustness, efficiency, and performance, running after each build to catch subtle misunderstandings
Parallax (possibly renamed Parallaxe) spins up parallel virtual work tracks (GDKs) that each focus on one issue/MR/feature, defined via question-answer to resolve ambiguity, enabling high throughput
Each parallel work track goes through the validation harness and iterates before being pushed up and released
Started the day split between reviewing a simple MR and testing automated processes
Hit an issue where the harness couldn’t connect to the memory server
Fixed it by hosting the memory daemon on a separate port
Agent now successfully recalls user-level learnings, captured in a screenshot
Noted a series of version tags (v1.2.0-rc1 through rc6) covering inference setup, opencode fixes, supervisor streaming, registry refactor, and PID/restart handling
ryer.io