Decebal | Rust for the AI execution layer ⚙️ (@ddonprogramming) header
Decebal | Rust for the AI execution layer ⚙️ (@ddonprogramming) profile picture

Wolven Tech: Rust consulting. AllSource Prime: durable AI memory → https://nitter.cf/t.co/CfdDxoKhs5 Longhand: AI workflows & training → https://nitter.cf/t.co/Rbml5TOtFF

London, United Kingdom
Joined January 2014
Photo by Decebal | Rust for the AI execution layer ⚙️ (@ddonprogramming)Photo by Decebal | Rust for the AI execution layer ⚙️ (@ddonprogramming)Photo by Decebal | Rust for the AI execution layer ⚙️ (@ddonprogramming)Photo by Decebal | Rust for the AI execution layer ⚙️ (@ddonprogramming)Photo by Decebal | Rust for the AI execution layer ⚙️ (@ddonprogramming)Photo by Decebal | Rust for the AI execution layer ⚙️ (@ddonprogramming)Photo by Decebal | Rust for the AI execution layer ⚙️ (@ddonprogramming)Photo by Decebal | Rust for the AI execution layer ⚙️ (@ddonprogramming)Photo by Decebal | Rust for the AI execution layer ⚙️ (@ddonprogramming)Photo by Decebal | Rust for the AI execution layer ⚙️ (@ddonprogramming)
1,000 followers. Thank you. Marking it by opening something up: I am taking on fractional full stack AI developer work through Wolven Tech Ltd. Five spots. One is already taken. How it works below.
7
1
20
662
Keep agent changes that the acceptance gate rejected. A promoted-only report hides recurring proposed regressions and the work the gate performed to contain them.
🤖 Made with AI
1
33
Retain the parent revision, proposed change, evaluator version and rejection reason beside promotion. Keep protected references and promotion authority outside the candidate’s mutation scope.
1
5
Audit discarded candidates, then check whether deployed behaviour ever exhibited those failures. Count development cost without inventing production incidents. Source: huggingface.co/blog/BunsDev/…
9
A search subagent can return accurate code while omitting the dependency that changes the answer. The caller needs another search to inspect evidence that never reached it.
🤖 Made with AI
1
38
Test multi-file changes with known dependency links. Separate missing-file failures from misinterpretation of returned code. Verify the completed patch through its real acceptance flow.
1
5
API-token usage excludes the local model’s work. Include local inference and elapsed latency before calling it an operating-cost saving. Source: huggingface.co/blog/lightona…
25
A faster KV handoff can require choosing the decoder earlier. vLLM’s NIXL push design overlaps destination preparation with prefill, after selecting where the request will decode.
🤖 Made with AI
1
32
Those are proposed qualification tests, not observed connector defects. Compare completed-request latency alongside capacity committed to unfinished requests.
1
4
1/7 Imagine an agent-written change that passes CI. A reviewer asks what happens if the caller retries after a lost acknowledgement. The operation runs twice. Use this case to examine the harness and review process your engineers designed together.
🤖 Made with AI
1
1
34
7/7 At the next review, have the author and reviewer identify what the harness caught, what it missed and what they will change before the next task. Keep the shared product outcome as the acceptance criterion.
3