Under review · revisions requested
[Paper title — to be filled in]
[Abstract — short summary of the paper's contribution and approach. To be filled in.]
// papers
The kuzys tools are built on (and write) research. Below: papers in review, in submission, and in draft. The suite reflects what these papers describe; updates land in code and on this page together.
Under review · revisions requested
[Abstract — short summary of the paper's contribution and approach. To be filled in.]
Ready for submission
[Abstract — short summary. To be filled in.]
Drafting
[Short description of what the paper will cover. To be filled in.]
Methods at this group tend to make explicit, at the layer where the change happens, what was previously operating through trust, convention, or assumption. Whether the substrate is a test plan, a response shape, a revision discipline, or a social contract, the move is the same: convert implicit agreement into observable evidence, then document the agreement as the new floor.
Concretely, the protocols and operational primitives that make the suite work — heartbeat triggers, attention coalescing, delivery-receipt semantics (transport-acceptance vs. runtime-observation), persistence patterns across vendor outages, attribution conventions, consent boundaries — are documented in the source repositories and referenced from the relevant paper sections.
If you're reproducing a result or building on a method, the right starting points are the paper plus the relevant tool's source. Open an issue on GitLab if anything is unclear or undocumented; we treat documentation gaps as bugs.