Knowledge Resource
Research Summary: Humanize: Judgement Engineering for Agentic Coding
- Original authors
- Attribution requires verification
- Original source
- arXiv — Computers and Society
- Summary & Analysis prepared by
- Aziz Shuaib Ausi
- Resource type
- Research Summary / Knowledge Resource
- Resource published on AZIZ OS
- 26 October 2026
- Reading time
- 1 min
- Publication type
- Knowledge Resource
- Availability
- Open access
About this Summary & Analysis
AZIZ OS provides independently prepared summaries and analytical interpretations of externally published research and knowledge sources. The underlying works remain attributable to their original authors and rights holders. This resource is intended to improve accessibility and understanding and does not replace the original publication.
A research study introduces Humanize, a multi-agent orchestration framework designed to address the deficiency of agentic code generators acting as judges of their own work. The approach relies on judgement engineering, establishing strict boundaries between planning, execution, and evaluation through human approval, multi-vendor agent segregation, and 72 deterministic mechanical gates.
Why it matters
As generative software engineering scales, single-agent self-validation presents acute reliability and quality risks in technical operations. Implementing multi-vendor separation of duties and deterministic checkpoints provides an architectural foundation for dependable agentic automation. This structural shift moves the operational focus from pure generation capacity to verifiable execution governance.
Key insights
- Agentic code generation is cost-effective but struggles with reliable completion due to agents being poor evaluators of their own output.
- The Humanize framework implements judgement engineering to enforce explicit decisions across planning, implementation, review, and learning phases.
- Workflows require human sign-off on plan contracts, assign implementation to a builder agent, and delegate completion decisions to an independent reviewer agent from a separate vendor.
- Routing and gatekeeping are executed via deterministic hooks rather than AI models, enforcing 72 mechanical gates.
- The system mathematically models workflow progression as a Markov chain over repository states by alternating sampling between two distinct models.
Source
arXiv — Computers and Society — https://arxiv.org/abs/2610.08900
Related intelligence and resources
Previous
An ecology of participation for fusion energy development
Next
On-Chain Archaeology of Bitcoin Oracles: Evidence of Use under Limited Observability
Proceedings of the 2nd International Workshop on Low Carbon Computing (LOCO 2026)
Knowledge Resource
The Fake Friend Dilemma: Relational Trust and the Political Economy of Conversational AI
Knowledge Resource
Clinical Note Bloat Reduction for Efficient LLM Use
Knowledge Resource
Do LLMs Rewrite History? Detecting Historical Revisionism in Large Language Models
Knowledge Resource
Who Gets Flagged? The Pluralistic Evaluation Gap in AI Content Watermarking
Knowledge Resource
She Works, He Works: A Curious Exploration of Gender Bias in AI-Generated Imagery
Knowledge Resource
Citation
Cite the original work (APA 7)
The original source is authoritative for this citation. Cite the source publication directly — this attribution is pending verification. Open the original source.
Verification
This is an authenticated AZIZ OS resource record.
- Verification ID
- ASA-EXE-2026-01387
- Version
- v1.0 · r0
- Issued
- 26 October 2026
- Resource prepared by
- Aziz Shuaib Ausi
- Resource status
- Research Summary / Knowledge Resource
- Underlying work
- Humanize: Judgement Engineering for Agentic Coding
- Original authors
- Attribution requires verification
- Original source
- arXiv — Computers and Society
- Provenance status
- Attribution requires verification
- Rights
- Underlying publication rights remain with the respective copyright holder(s). Refer to the original source for authoritative publication and licensing information.
This verification confirms the AZIZ OS resource record and its documented provenance. It does not establish authorship of the underlying external work.